Content-Type: text/plain
debian-user-digest Digest Volume 2007 : Issue 2737
Today's Topics:
Re: Debian Failure Setting Password [ Raj Kiran Grandhi ]
Re: Intel Deluxe PC Camera [ John Schmidt ]
Re: how to read http mails in mutt m [ Andy Smith ]
how to read http mails in mutt mail [ hce ]
Re: fglrx upgrade to 8.42.3 [ Jonathan Kaye ]
Re: Intel Deluxe PC Camera [ Jonathan Kaye ]
Re: fglrx upgrade to 8.42.3 [ Davide Mancusi ]
sa-learn error message [ Yuriy Padlyak ]
sa-learn error message [ Yuriy Padlyak ]
Date: Sun, 04 Nov 2007 11:14:35 +0530
From: Raj Kiran Grandhi <grajkiran@gmail.com>
To: Redefined Horizons <redefined.horizons@gmail.com>
Cc: debian-user@lists.debian.org
Subject: Re: Debian Failure Setting Password
Message-ID: <472D5C43.8020109@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Redefined Horizons wrote:
> Andrew,
>
> You are probably correct. I didn't think about encryption. I'm going
> to give the system rescue cd another shot.
usermod --password would be useful in a script. If you are going to do
it manually, just use "passwd <username>" as root.
>
> Scott Huey
>
> On 11/3/07, Andrew Sackville-West <andrew@farwestbilliards.com> wrote:
>> On Sat, Nov 03, 2007 at 08:47:27PM -0700, Redefined Horizons wrote:
>>> I've run into a problem after I performed the following:
>>>
>>> [1] Changed the password for my root user with the usermod command.
>>> [2] Changed the password of a non-root user with the usermod command.
>> according to man usermod, the --password command expects an encrypted
>> password. did you supply encrypted passwords?
>>
>>> [3] Added a new user with a password using the useradd command.
>>>
>>> After making these changes I could no longer log in as the root user
>>> or the non-root user for whom I changed the password. I also could not
>>> log in as the new user. I tried this with both old and new passwords.
>>> (All user names were recognized, but Debian is telling me the
>>> passwords are incorrect.)
>>>
>>> I booted with the System Rescue CD and followed the advice at this link:
>>>
>>>
http://www.debianadmin.com/forgot-root-password-or-reset-root-password-in-debian.html
>>>
>>> When I edited the etc/shadow file I found the passwords for the root
>>> user, non-root user, and new user to be exactly as I had set them with
>>> the usermod and useradd commands. The passwords are the same ones that
>>> failed. I reset them using nano and System Rescue CD.
>> did you reset them or delete them? I think you need to delete them
>> (remove the characters between the first and second colon) because
>> they get stored in an encrypted method. You'd have to know what wacky
>> string to type so that the encrypted output matches whatever plain
>> text is in there...
>>
>> I think go back in through system rescue cd, delete the passwords, log
>> in with blank passwords and then change them using passwd.
>>> After a reboot the original passwords, the new passwords, and the
>>> passwords reset using the System Rescue CD all failed.
>>>
>>> Note: I had one existing non-root user whose password I did not
>>> modify. I can still log into my system using this user. I am know
>>> backing up that users data in case I have to reinstall.
>>>
>>> Does anyone have any idea what is going on? I'm really wishing that I
>>> wouldn't have reset that root password now. It's the last time I'll
>>> ever do that.
>> well, better to learn to do it properly than not do it at all...
>>
--
Raj Kiran Grandhi
Date: Sat, 03 Nov 2007 23:06:52 -0700
From: Marc Shapiro <mshapiro_42@yahoo.com>
To: debian-user@lists.debian.org
Subject: Re: Intel Deluxe PC Camera
Message-ID: <472D617C.1050109@yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Marc Shapiro wrote:
> I have just become the proud owner of an unused, still in box, Intel
> Deluxe PC Camera. This camera is dated 2001 and claims it requires
> Windows 98, 98SE, or Millennium Edition. Does anyone know if there
> are currently Linux drivers for this? I am running Etch with a
> 2.6.16-2-k7 stock Debian kernel and udev. This is a USB camera. I
> plugged it in and dmesg added the following lines:
>
> usb 4-1: new full speed USB device using ohci_hcd and address 2
> usb 4-1: configuration #1 chosen from 1 choice
>
> Can I assume that it has loaded any necessary drivers? What should I
> look for in the lsmod listing. In fact, here is the output from lsmod
> with the camera plugged in:
>
> :~$ lsmod
> Module Size Used by
> ipv6 218912 14
> ppdev 8324 0
> lp 10496 0
> it87 19172 0
> hwmon_vid 2432 1 it87
> i2c_isa 4608 1 it87
> i2c_core 19536 2 it87,i2c_isa
> mousedev 10496 1
> tsdev 7296 0
> snd_intel8x0 29532 3
> snd_ac97_codec 82848 1 snd_intel8x0
> snd_ac97_bus 2112 1 snd_ac97_codec
> snd_pcm_oss 44128 0
> snd_mixer_oss 15744 1 snd_pcm_oss
> snd_pcm 74504 4 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
> snd_seq_dummy 3588 0
> snd_seq_oss 27812 0
> snd_seq_midi 8096 0
> snd_rawmidi 22496 1 snd_seq_midi
> usblp 12224 0
> snd_seq_midi_event 6592 2 snd_seq_oss,snd_seq_midi
> parport_pc 31728 1
> parport 32008 3 ppdev,lp,parport_pc
> floppy 55916 0
> snd_seq 43852 6
> snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
> snd_timer 20420 3 snd_pcm,snd_seq
> snd_seq_device 8332 5
> snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
> snd 46400 14
> snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
>
> soundcore 8736 1 snd
> snd_page_alloc 9864 2 snd_intel8x0,snd_pcm
> rtc 11444 1
> shpchp 39424 0
> pci_hotplug 24308 1 shpchp
> psmouse 34504 0
> pcspkr 3012 0
> serio_raw 6532 0
> amd64_agp 11652 0
> sis_agp 8196 1
> agpgart 29296 2 amd64_agp,sis_agp
> evdev 8832 0
> ext3 117064 5
> jbd 47316 1 ext3
> mbcache 7684 1 ext3
> dm_mirror 17460 0
> dm_snapshot 15388 0
> dm_mod 48180 8 dm_mirror,dm_snapshot
> ide_generic 1216 0 [permanent]
> ide_cd 35680 0
> cdrom 32240 1 ide_cd
> ide_disk 14720 4
> sis900 20992 0
> mii 5248 1 sis900
> ehci_hcd 26952 0
> ohci_hcd 17348 0
> usbcore 111136 4 usblp,ehci_hcd,ohci_hcd
> sis5513 12108 0 [permanent]
> generic 4228 0 [permanent]
> ide_core 111536 5
> ide_generic,ide_cd,ide_disk,sis5513,generic
> thermal 13064 0
> processor 21760 1 thermal
> fan 4548 0
>
> If the drivers have been loaded, what do I need to do next? I may
> actually use this as a webcam, but my primary purpose for it is to
> capture images to be processed to allow a robot to use the data for
> navigation. I have not yet decided on a programming language for
> this, though it is likely to be C/C++ for compiled speed, unless
> someone has some other suggestions for me. Any ideas?
>
> I have libcv0.9.7-0 installed, as well as python-opencv.
>
> Does anyone have any experience with this sort of stuff?
>
It looks like the driver module that I need is spca501. There is a
source package for Etch:
spca5xx-source
What is the best way to compile this? I generally just use stock
kernels and the modules that come with them so I am unfamiliar with
compiling modules separately for a kernel that I already have. Once I
do have the module compiled, will udev/hotplug load the driver at
boot-up, or should I add it to /etc/modules?
--
Marc Shapiro
mshapiro_42@yahoo.com
Date: Sun, 4 Nov 2007 17:27:46 +1100
From: hce <webmail.hce@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: How to set up postfix logfile
Message-ID: <95455e980711032327xcea7392v4351a72e6dab825f@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On 11/4/07, Carl Fink <carl@finknetwork.com> wrote:
> On Sun, Nov 04, 2007 at 02:54:25PM +1100, hce wrote:
> > Thanks Gerard, I tried, but did not give me the informaiotn where is
> > the postfix log file. The postfix has been restarted, but I still
> > could not send mails from the mutt.
>
> The default location is /var/log/mail.log.
Thanks Carl. After reading the mail.log, I fixed the problem.
Thank you.
Jim
Date: Sun, 4 Nov 2007 00:35:45 -0600
From: John Schmidt <john.andrew.schmidt@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: Intel Deluxe PC Camera
Message-Id: <200711040035.45935.john.andrew.schmidt@gmail.com>
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On Sunday 04 November 2007, Marc Shapiro wrote:
>
> It looks like the driver module that I need is spca501. There is a
> source package for Etch:
>
> spca5xx-source
>
> What is the best way to compile this? I generally just use stock
> kernels and the modules that come with them so I am unfamiliar with
> compiling modules separately for a kernel that I already have. Once I
> do have the module compiled, will udev/hotplug load the driver at
> boot-up, or should I add it to /etc/modules?
>
> --
> Marc Shapiro
> mshapiro_42@yahoo.com
Marc,
I use module-assitant and modconf (apt-get install module-assistant modconf)
to manage modules that I have to compile.
Do this:
sudo m-a
It will put up a dialogue box, and then you need to first prepare the build by
downloading the kernel headers. Then choose select and check the
spca5xx-source, and it should download it for you. Then build it and install
it. These are all menu selectable items in module assitant.
Then I use modconf to select the modules so load.
With those two toosl, dealing with modules is really quite straightforward and
painless.
John
Date: Sat, 3 Nov 2007 23:40:07 -0700
From: Amit Uttamchandani <atu13439@csun.edu>
To: debian-user@lists.debian.org
Subject: Re: How to mount solaris from linux
Message-ID: <20071103234007.25e7064e@debian.csun.edu>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
On Sat, 3 Nov 2007 07:55:43 +0100
"abdelkader belahcene" <abelahcene@gmail.com> wrote:
> Hi,
> I ve just install the indiana in-preview version of opensolaris (Nov 1st).
>
> The installation was done correctly, in a primary partition declared
> as Solaris bf ( with linux and windows OS in same disk). ( my
> machine is an IBM i386).
> It seemed correct, but
> I have a problem to start Solaris, a solaris Pb, so I reboot whith CD1
> debian to put again the grub menu, OK.
>
> Now I want to mount the Solaris partition, but, type is
> unrecognized!!! I tried -t ufs, unsuccefully. I have declared the
> partition Solaris bf, which i s in the list recognized by linux!!!
>
> Thanks for help
> best regards
> bela
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
Hey there,
The latest version on solaris aka "project indiana" uses zfs as its default filesystem. There is no implementation of linux or any other unix (except maybe freebsd 7.0) that can read/write to zfs partitions.
Date: Sun, 4 Nov 2007 08:27:53 +0100
From: Thierry Chatelet <tchatelet@free.fr>
To: debian-user@lists.debian.org
Subject: Re: Intel Deluxe PC Camera
Message-Id: <200711040827.53604.tchatelet@free.fr>
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On Sunday 04 November 2007 07:35, John Schmidt wrote:
> On Sunday 04 November 2007, Marc Shapiro wrote:
> > It looks like the driver module that I need is spca501. There is a
> > source package for Etch:
> >
> > spca5xx-source
> >
> > What is the best way to compile this? I generally just use stock
> > kernels and the modules that come with them so I am unfamiliar with
> > compiling modules separately for a kernel that I already have. Once I
> > do have the module compiled, will udev/hotplug load the driver at
> > boot-up, or should I add it to /etc/modules?
> >
> > --
> > Marc Shapiro
> > mshapiro_42@yahoo.com
>
> Marc,
>
> I use module-assitant and modconf (apt-get install module-assistant
> modconf) to manage modules that I have to compile.
>
> Do this:
>
> sudo m-a
>
> It will put up a dialogue box, and then you need to first prepare the build
> by downloading the kernel headers. Then choose select and check the
> spca5xx-source, and it should download it for you. Then build it and
> install it. These are all menu selectable items in module assitant.
>
> Then I use modconf to select the modules so load.
>
> With those two toosl, dealing with modules is really quite straightforward
> and painless.
>
> John
Unless I am mistaking, I read somewhere that spca5xx was for kernel up to
2.6.11, for later kernel you need gspca-sources.
Thierry
Date: Sun, 4 Nov 2007 07:55:48 +0000
From: Terence <terence.john@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: How to mount solaris from linux
Message-ID: <c7e110fe0711040055o57346219vcc77c3175d71315e@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On 04/11/2007, Amit Uttamchandani <atu13439@csun.edu> wrote:
> The latest version on solaris aka "project indiana" uses zfs as its default filesystem. There is no implementation of linux or any other unix (except maybe freebsd 7.0) that can read/write to zfs partitions.
>
Answered my question before I even asked it! Awesome!
Terence
Date: Sun, 4 Nov 2007 08:40:12 +0000
From: Andy Smith <andy@lug.org.uk>
To: debian-user@lists.debian.org
Subject: Re: how to read http mails in mutt mail reader (vim)?
Message-ID: <20071104084012.GJ4325@bitfolk.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="KQ2iXOoQ638mtNze"
Content-Disposition: inline
--KQ2iXOoQ638mtNze
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Hi Jim,
On Sun, Nov 04, 2007 at 07:31:53PM +1100, hce wrote:
> I've just installed mutt in Debian, one problem is there are some
> mails from news lists with HTTP format, it was fine when I use Mozilla
> mail reader, but with mutt and vim, I could not read the HTTP format
> mails. One solution I can think of is to use lynx, but I don't know
> how to config mutt with lynx. How do you handle this issue?
If you mean HTML, there was a post to Planet Debian on this subject
just yesterday:
http://cord.de/blog/index.php?entry=3Dentry071103-141719
I do it that way too.
Cheers,
Andy
--=20
http://bitfolk.com/ -- No-nonsense VPS hosting
Encrypted mail welcome - keyid 0x604DE5DB
--KQ2iXOoQ638mtNze
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHLYVsIJm2TL8VSQsRAuHUAJ9PRZp1QI28SS9epCTl90qoss7gHgCgi1ZC
I/aRLb3W5cVPXAqrhHMus3M=
=lE+W
-----END PGP SIGNATURE-----
--KQ2iXOoQ638mtNze--
Date: Sun, 4 Nov 2007 19:31:53 +1100
From: hce <webmail.hce@gmail.com>
To: debian-user@lists.debian.org
Subject: how to read http mails in mutt mail reader (vim)?
Message-ID: <95455e980711040131l4b94754fl21f48f976a79b275@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Hi,
I've just installed mutt in Debian, one problem is there are some
mails from news lists with HTTP format, it was fine when I use Mozilla
mail reader, but with mutt and vim, I could not read the HTTP format
mails. One solution I can think of is to use lynx, but I don't know
how to config mutt with lynx. How do you handle this issue?
Thank you.
Jim
Date: Sun, 04 Nov 2007 10:51:33 +0100
From: Jonathan Kaye <jdkaye10@yahoo.es>
To: debian-user@lists.debian.org
Subject: Re: fglrx upgrade to 8.42.3
Message-ID: <fgk4n8$okj$1@ger.gmane.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Davide Mancusi wrote:
> Jonathan Kaye ha scritto:
>> Hi Davide,
>> I've installed it and it's BRILLIANT!!!! Three cheers for ATI they've =
got
>> it right!
>> fgl_glxgears ran around 380fps under 8.39. Now, under 8.42 it's over 5=
00!
>> So I'd say go for it.
>> Cheers,
>> Jonathan
>=20
> Thank you all for the feedback. I have tried to install the package
> from the ATI website but I have the same problems (Jonathan =E2=80=94 h=
ow did
> you install it? Did you ask the installer to build a Debian package?).
> Since I think I might have screwed up something with the diversions and
> with symlinks in /usr/lib, I would be very grateful if anyone with a
> working 8.42.3 installation could post the fglrx-related part of
> /var/lib/dpkg/diversions and the output of
> $ ls -l /usr/lib/libGL*
> $ ls -l /emul/ia32/usr/lib/libGL* (did I mention I'm on amd64?)
>=20
> Thanks again!
>=20
> Davide
>=20
Hi Davide,
Here's how I did it:
1. Remove all fglrx packages currently installed.
2. as root or using sudo
a. go to /usr/src/modules and rm -r fglrx
b. if you an flgrx-kernel .deb file in /usr/src, delete it.
Now to build the new driver.
1. Go to the folder where you have downloaded the
ati-driver-installer-8.42.3-x86.x86_64.run file
2. Make sure the file is executable
3. As root or using sudo
a. #./ati-driver-installer-8.42.3-x86.x86_64.run --buildpkg Debian/lenn=
y
b. dpkg -i [and at least these 2 .debs] fglrx-driver_8.42.3-1_i386.deb=20
fglrx-kernel-src_8.42.3-1_i386.deb
you can install all the debs if you like.
c. Now you use module assistant to build the modules
#m-a a-i fglrx
d. modprobe -v fglrx
e. make sure that the driver for your card is "fglrx"
You will have to stop the x-server and then restart it. In fact I had to
reboot (aaargggghhh) in order for the module to install correctly. Try
running fglrxinfo and you should see something like this:
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon 9550 / X1050 Series
OpenGL version string: 2.0.6958 Release
Then you know your driver is correctly installed. Also you can try runnin=
g
fgl_glxgears.
I tried Elimar's suggestion (using xorg's "radeon" driver) but I couldn't
get it to work with 3D acceleration.
Hope this helps.
Jonathan
--=20
Registerd Linux user #445917 at http://counter.li.org/
Date: Sun, 04 Nov 2007 11:13:48 +0100
From: Jonathan Kaye <jdkaye10@yahoo.es>
To: debian-user@lists.debian.org
Subject: Re: Intel Deluxe PC Camera
Message-ID: <fgk60v$rhg$1@ger.gmane.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
Thierry Chatelet wrote:
> Unless I am mistaking, I read somewhere that spca5xx was for kernel up to
> 2.6.11, for later kernel you need gspca-sources.
> Thierry
I'm using spca5xx-source with 2.6.22 on lenny. I needed it to build a
sn9c102 module.
Cheers,
Jonathan
--
Registerd Linux user #445917 at http://counter.li.org/
Date: Sun, 04 Nov 2007 11:08:24 +0100
From: Davide Mancusi <arekfu@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: fglrx upgrade to 8.42.3
Message-ID: <472D9A18.4070002@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Jonathan Kaye ha scritto:
> Hi Davide,
> Here's how I did it:
> 1. Remove all fglrx packages currently installed.
> 2. as root or using sudo
> a. go to /usr/src/modules and rm -r fglrx
> b. if you an flgrx-kernel .deb file in /usr/src, delete it.
> Now to build the new driver.
> 1. Go to the folder where you have downloaded the
> ati-driver-installer-8.42.3-x86.x86_64.run file
> 2. Make sure the file is executable
> 3. As root or using sudo
> a. #./ati-driver-installer-8.42.3-x86.x86_64.run --buildpkg Debian/lenny
Thanks again for this simple howto. It was more or less what I tried to
do myself, but building the package does not work. It fails like this
(long log follows):
Created directory fglrx-install.zq4758
Verifying archive integrity... All good.
Uncompressing ATI Proprietary Linux
Driver-8.42.3....................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
==================================================
ATI Technologies Linux Driver Installer/Packager
==================================================
Generating package: Debian/sid
Package build failed!
Package build utility output:
dpkg-buildpackage: source package fglrx-installer
dpkg-buildpackage: source version 8.42.3-1
dpkg-buildpackage: source changed by ATI Technologies Inc.
<http://ati.amd.com/support/driver.html>
debian/rules build
dpkg-buildpackage: host architecture amd64
dh_testdir
# move licenses away from binary dir
if [ ! -d usr/share/doc/fglrx ]; then \
mkdir -p usr/share/doc/fglrx; \
mv usr/X11R6/bin/LICENSE.* usr/share/doc/fglrx; \
fi
# set executable on user apps
find usr/X11R6/bin -type f | xargs chmod a+x
# remove exec bit from files that don't deserve it
find usr/X11R6/include \
usr/X11R6/lib \
usr/X11R6/lib64 \
usr/share usr/src -type f | xargs chmod -x
find: usr/X11R6/lib: No such file or directory
find lib -not -name "*.sh" -type f | xargs chmod -x
find lib -name "*.sh" -type f | xargs chmod +x
# set proper permissions on /etc files
if [ -d etc/ati ]; then \
chmod 755 etc/ati ; \
chmod 644 etc/ati/* ; \
chmod a+x etc/ati/*.sh ; \
fi
if [ -f debian/fglrx.default ]; then \
mv -v debian/fglrx.default debian/fglrx; \
fi
`debian/fglrx.default' -> `debian/fglrx'
# remove exec bit from 64-bit libs too
find usr/X11R6/lib64 -type f | xargs chmod -x
debian/rules binary
dh_testdir
# move licenses away from binary dir
if [ ! -d usr/share/doc/fglrx ]; then \
mkdir -p usr/share/doc/fglrx; \
mv usr/X11R6/bin/LICENSE.* usr/share/doc/fglrx; \
fi
# set executable on user apps
find usr/X11R6/bin -type f | xargs chmod a+x
# remove exec bit from files that don't deserve it
find usr/X11R6/include \
usr/X11R6/lib \
usr/X11R6/lib64 \
usr/share usr/src -type f | xargs chmod -x
find: usr/X11R6/lib: No such file or directory
find lib -not -name "*.sh" -type f | xargs chmod -x
find lib -name "*.sh" -type f | xargs chmod +x
# set proper permissions on /etc files
if [ -d etc/ati ]; then \
chmod 755 etc/ati ; \
chmod 644 etc/ati/* ; \
chmod a+x etc/ati/*.sh ; \
fi
if [ -f debian/fglrx.default ]; then \
mv -v debian/fglrx.default debian/fglrx; \
fi
# remove exec bit from 64-bit libs too
find usr/X11R6/lib64 -type f | xargs chmod -x
dh_testdir
dh_testroot
dh_clean -k
dh_installdirs
# Create the directories to install into
dh_installdirs -pfglrx-driver \
usr \
usr/lib/xorg \
usr/lib/xorg/modules \
usr/lib/dri \
usr/bin \
usr/sbin \
etc/acpi \
etc/acpi/events \
etc/default \
etc/X11/Xsession.d
# the amd64 package includes 32bit compatibility libraries
dh_installdirs -pfglrx-driver \
emul/ia32-linux/usr/lib \
emul/ia32-linux/usr/lib/xorg \
emul/ia32-linux/usr/lib/xorg/modules \
emul/ia32-linux/usr/lib/dri
dh_installdirs -pfglrx-driver-dev \
usr \
usr/include \
usr/lib
dh_installdirs -pfglrx-kernel-src \
usr/src/modules/fglrx \
usr/src/modules/fglrx/debian
dh_installdirs -A -pfglrx-amdcccle \
usr \
usr/bin \
usr/share \
usr/share/applnk \
usr/share/applications \
usr/share/icons \
usr/share/pixmaps
dh_installdirs -p \
usr/src
dh_install
dh_install -pfglrx-driver "usr/X11R6/bin/fgl*" "usr/bin"
dh_install -pfglrx-driver "usr/X11R6/bin/aticonfig" "usr/bin"
dh_install -pfglrx-driver "usr/sbin/atieventsd" "usr/sbin"
dh_installman -pfglrx-driver "usr/share/man/man8/atieventsd.8"
# amd64 needs some library redirection
dh_install -pfglrx-driver "usr/X11R6/lib64/*.so*" "usr/lib"
dh_install -pfglrx-driver "usr/X11R6/lib64/modules/dri" "usr/lib"
dh_install -pfglrx-driver "usr/X11R6/lib64/modules/linux"
"usr/lib/xorg/modules"
dh_install -pfglrx-driver "usr/X11R6/lib64/modules/drivers"
"usr/lib/xorg/modules"
dh_install -pfglrx-driver "usr/X11R6/lib64/modules/*.so"
"usr/lib/xorg/modules"
dh_install -pfglrx-driver "usr/X11R6/lib64/modules/*.a"
"usr/lib/xorg/modules"
dh_install -pfglrx-driver "usr/X11R6/lib/*.so*"
"emul/ia32-linux/usr/lib"
dh_install -pfglrx-driver "usr/X11R6/lib/modules/dri"
"emul/ia32-linux/usr/lib"
cp: cannot stat `./usr/X11R6/lib/modules/dri': No such file or directory
dh_install: command returned error code 256
make: *** [binary] Error 1
dpkg-buildpackage: failure: debian/rules binary gave error exit status 2
Removing temporary directory: fglrx-install.zq4758
Why? Is it because I am on amd64? I will try to reinstall from scratch
everything which is GL-related...
Davide
--
A tautology is a thing which is tautological.
--
Time flies like an arrow. Fruit flies like a banana.
Date: Sun, 04 Nov 2007 13:06:43 +0200
From: Yuriy Padlyak <yura@cvt.com.ua>
To: debian-user@lists.debian.org
Subject: sa-learn error message
Message-ID: <472DA7C3.60302@cvt.com.ua>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
I've got this error:
$ sa-learn --spam 1193706642.H221893P4714.tenpostadsl.lviv.farlep.net:2,S
syntax error for eval function GREYLIST_ISWHITE: greylisting("( 'dir' =>
'/var/spool/sa-exim/tuplets'; 'method' => 'dir'; 'greylistsecs' =>
'1800'; 'dontgreylistthreshold' => 11; 'connectiphdr' => ' at
/usr/share/perl5/Mail/SpamAssassin/Conf/Parser.pm line 717.
Learned tokens from 1 message(s) (1 message(s) examined)
Can anyone help me identifying the source of it?
Thank you in advance.
Yuriy
Date: Sun, 04 Nov 2007 13:06:56 +0200
From: Yuriy Padlyak <yura@cvt.com.ua>
To: debian-user@lists.debian.org
Subject: sa-learn error message
Message-ID: <472DA7D0.5020307@cvt.com.ua>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Hello
I've got this error:
$ sa-learn --spam 1193706642.H221893P4714.tenpostadsl.lviv.farlep.net:2,S
syntax error for eval function GREYLIST_ISWHITE: greylisting("( 'dir' =>
'/var/spool/sa-exim/tuplets'; 'method' => 'dir'; 'greylistsecs' =>
'1800'; 'dontgreylistthreshold' => 11; 'connectiphdr' => ' at
/usr/share/perl5/Mail/SpamAssassin/Conf/Parser.pm line 717.
Learned tokens from 1 message(s) (1 message(s) examined)
Can anyone help me identifying the source of it?
Thank you in advance.
Yuriy
End of debian-user-digest Digest V2007 Issue #2737
**************************************************
Received on Sun Nov 4 06:46:45 2007