I got similar problem with gnome 2.10. After logout the screen goes black, although it seems that gdm is working. I checked out with ps aux | less and it seemed alright. Does anyone know what's wrong ? I suspect a repaint problem, but I am a newbie and ain't so sure.
On 7/19/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Send blfs-support mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://linuxfromscratch.org/mailman/listinfo/blfs-support > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of blfs-support digest..." > > > Today's Topics: > > 1. Re: Hello everybody, I've a few basic questions (Declan Moriarty) > 2. libstdc++-libc6.1-1.so.2.bz2 (Olafsen) > 3. Re: libstdc++-libc6.1-1.so.2.bz2 (Andrew Benton) > 4. Can't set desktop background image in Gnome (Steve Brown) > 5. Re: Can't set desktop background image in Gnome (Kevin Jordan) > 6. Re: Can't set desktop background image in Gnome (Randy McMurchy) > 7. Re: Can't set desktop background image in Gnome (Steve Brown) > 8. non-existant lp and parport devices (Archaic) > 9. Re: non-existant lp and parport devices (Joern Abatz) > 10. Re: non-existant lp and parport devices (Archaic) > 11. Xorg, KDE come up to a white screen (Roberto Perpuly) > 12. Re: Xorg, KDE come up to a white screen (Chris Staub) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 18 Jul 2005 11:03:50 +0100 > From: Declan Moriarty <[EMAIL PROTECTED]> > Subject: Re: Hello everybody, I've a few basic questions > To: BLFS Support List <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=iso-8859-1 > > Recently, Somebody Somewhere wrote these words > > Hello everybody, > > I'm a newbie on the list, but completely newbie on linuxfromscratch. I > > cannot put up anymore Debian, and I don't want to use an other > > distribution. If fact, I think Debian is a good distribution, but the > > fact that packages are installed, removed, upgraded... automatically > > causes more problems than solution. So, I decided using a knoppix, > > even if it takes a lot of time, to format all my root partition and > > put LFS instead of it. > > Moreurer, I think this adventure is very interesting, I want to try, > > even if it may be long and difficult. I hope following LFS and BLFS > > books, I'll not have too problems. > > But the most important in that is I want to handle all my computer, > > what it happens, in order to know when there are mistakes where they > > are. But at the end, it's to have a system which works, easily. That's > > why I've a few questions, in order not to have bad surprises when I am > > on BLFS, so after LFS I'll install after your answers. > > My questions are enough simple: could someone tell me if it's not too > > easy to install emacs 21 by its sources (with LFS of course)? Where > > can I find sources of emacs21 and its dependent packages? Is there a > > document or something which explains how to install emacs21 building > > it by sources? > > Same questions for irssi-text, and packages such as pdftotext, catdoc, > > antiword, which are very important, so I'd like to be sure I'll find > > them without too problems after having installed LFS. > > To finish, a general questions: if when I build a software, it tells > > me that a library isn't enough new, how can I upgrade it? Because I'm > > worry with dependencies, especially when I read the book? > > > > Sorry for this long mail, I hope you'll manage to ayswer to me, it's > > very important to me, in order to go to LFS without being too worry. > > Thank you very much for your answers. > > > Here's what you do. > > Subscribe to the lfs-support mailing list, and download the lfs & blfs > books. HTML format is eastiest. > > Then build the lfs according to the book, getting support on that list. > Only when That is finished, should you worry about emacs and anything > else. The blfs (beyond lfs) html book makes a subdir; cd into it and > check for emacs with > > grep -r emacs * |less > > In each book, dependencies are listed. Don't ask, just read. Judging > from the listed optional dependencies, emacs should hardly be the first > thing you build. > > -- > > With best Regards, > > > Declan Moriarty. > > ------------------------------ > > Message: 2 > Date: Mon, 18 Jul 2005 13:47:22 +0200 > From: Olafsen, Bj?rn Ove <[EMAIL PROTECTED]> > Subject: libstdc++-libc6.1-1.so.2.bz2 > To: <[email protected]> > Message-ID: > <[EMAIL PROTECTED]> > > Content-Type: text/plain; charset="iso-8859-1" > > Hello. > > I'm trying to install Netscape 6.2.1 and Netscape 7.0 for testing purpose for > a project. Seems like I need to get libstdc++-libc6.1-1.so.2 to get it to > work. > > After doing some googling about this file I ended up finding this link: > http://linuxfromscratch.org/pipermail/blfs-support/2002-September/027593.html > which says the file in question can be downloaded from > http://www.linuxfromscratch.org/~timothy/misc/libstdc++-libc6.1-1.so.2.bz2 > <http://www.linuxfromscratch.org/~timothy/misc/libstdc++-libc6.1-1.so.2.bz2> > This link returns a Page Not Found error. > > So I'm wondering if you guys have any idea where I can download this file? > > > Regards > Bjørn Ove Olafsen > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://linuxfromscratch.org/pipermail/blfs-support/attachments/20050718/1156c0e7/attachment-0001.html > > ------------------------------ > > Message: 3 > Date: Mon, 18 Jul 2005 14:12:07 +0100 > From: Andrew Benton <[EMAIL PROTECTED]> > Subject: Re: libstdc++-libc6.1-1.so.2.bz2 > To: BLFS Support List <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-15; format=flowed > > Olafsen wrote: > > Hello. > > > > I'm trying to install Netscape 6.2.1 and Netscape 7.0 for testing purpose > > for a project. Seems like I need to get libstdc++-libc6.1-1.so.2 to get it > > to work. > > > > After doing some googling about this file I ended up finding this link: > > http://linuxfromscratch.org/pipermail/blfs-support/2002-September/027593.html > > which says the file in question can be downloaded from > > http://www.linuxfromscratch.org/~timothy/misc/libstdc++-libc6.1-1.so.2.bz2 > > <http://www.linuxfromscratch.org/~timothy/misc/libstdc++-libc6.1-1.so.2.bz2> > > This link returns a Page Not Found error. > > > > So I'm wondering if you guys have any idea where I can download this file? > > > > Why not compile it yourself? > http://archive.linuxfromscratch.org/blfs-museum/5.1/BLFS-BOOK-5.1-HTML/general/gcc2.html > > ------------------------------ > > Message: 4 > Date: Mon, 18 Jul 2005 14:09:31 -0500 > From: Steve Brown <[EMAIL PROTECTED]> > Subject: Can't set desktop background image in Gnome > To: BLFS Support List <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1 > > I've built Gnome 2.11 from sources from the ground up. I'm running > Control Center version 2.11.2 (later versions of the 2.11 series > wouldn't load any image). The gnome-backround-properties utility will > let me add wallpaper to the list of available wallpapers, but every > time it loads an image into the list of available wallpapers, it > displays the following: > > (gnome-background-properties:6572): GdkPixbuf-CRITICAL **: > gdk_pixbuf_scale_simple: assertion `dest_width > 0' failed > > (gnome-background-properties:6572): GdkPixbuf-CRITICAL **: > gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed > > (gnome-background-properties:6572): GdkPixbuf-CRITICAL **: > gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed > > (gnome-background-properties:6572): GdkPixbuf-CRITICAL **: > gdk_pixbuf_composite: assertion `src != NULL' failed > > (gnome-background-properties:6572): GLib-GObject-CRITICAL **: > g_object_unref: assertion `G_IS_OBJECT (object)' failed > > The image size is displayed as 1px x 1px, regardless of actual size. > When I click on the image to make it my desktop, it changes the > desktop color to the correct color, but it doesn't display the image. > I can set a background through some other app (e.g. firefox) just > fine. I can also view the images through an app like EOG, so I know > the images are fine. > > I tried reinstalling this version of Control Center, same thing > happens. 2.11.5 and 2.11.6 die with the following everytime I try to > add an image to the list of wallpapers: > > (gnome-background-properties:8757): GdkPixbuf-CRITICAL **: > gdk_pixbuf_composite: assertion `src != NULL' failed > > 2.10 series won't compile due to differences in 2.10 and 2.11 series > of gnome-menus packages. > > I'm sure the problem is with one of the packages I've installed (or > haven't installed). If someone could tell me which one, I'd > appreicate it. > > ------------------------------ > > Message: 5 > Date: Mon, 18 Jul 2005 14:18:09 -0500 > From: Kevin Jordan <[EMAIL PROTECTED]> > Subject: Re: Can't set desktop background image in Gnome > To: Steve Brown <[EMAIL PROTECTED]>, BLFS Support List > <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > On 7/18/05, Steve Brown <[EMAIL PROTECTED]> wrote: > > > > I've built Gnome 2.11 from sources from the ground up. I'm running > > Control Center version 2.11.2 (later versions of the 2.11 series > > wouldn't load any image). The gnome-backround-properties utility will > > let me add wallpaper to the list of available wallpapers, but every > > time it loads an image into the list of available wallpapers, it > > displays the following: > > > > (gnome-background-properties:6572): GdkPixbuf-CRITICAL **: > > gdk_pixbuf_scale_simple: assertion `dest_width > 0' failed > > > > (gnome-background-properties:6572): GdkPixbuf-CRITICAL **: > > gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed > > > > (gnome-background-properties:6572): GdkPixbuf-CRITICAL **: > > gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed > > > > (gnome-background-properties:6572): GdkPixbuf-CRITICAL **: > > gdk_pixbuf_composite: assertion `src != NULL' failed > > > > (gnome-background-properties:6572): GLib-GObject-CRITICAL **: > > g_object_unref: assertion `G_IS_OBJECT (object)' failed > > > > The image size is displayed as 1px x 1px, regardless of actual size. > > When I click on the image to make it my desktop, it changes the > > desktop color to the correct color, but it doesn't display the image. > > I can set a background through some other app (e.g. firefox) just > > fine. I can also view the images through an app like EOG, so I know > > the images are fine. > > > > I tried reinstalling this version of Control Center, same thing > > happens. 2.11.5 and 2.11.6 die with the following everytime I try to > > add an image to the list of wallpapers: > > > > (gnome-background-properties:8757): GdkPixbuf-CRITICAL **: > > gdk_pixbuf_composite: assertion `src != NULL' failed > > > > 2.10 series won't compile due to differences in 2.10 and 2.11 series > > of gnome-menus packages. > > > > I'm sure the problem is with one of the packages I've installed (or > > haven't installed). If someone could tell me which one, I'd > > appreicate it. > > -- > > http://linuxfromscratch.org/mailman/listinfo/blfs-support > > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > > Unsubscribe: See the above information page > > > > I'd go ahead and file a bug, or see if it's here at > http://bugzilla.gnome.org/reports/gnome-212-report.html. I don't see a bug > related to backgrounds under Control Center right now though. > > -- > Kevin Jordan > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://linuxfromscratch.org/pipermail/blfs-support/attachments/20050718/d219c2f0/attachment-0001.html > > ------------------------------ > > Message: 6 > Date: Mon, 18 Jul 2005 15:32:25 -0500 > From: Randy McMurchy <[EMAIL PROTECTED]> > Subject: Re: Can't set desktop background image in Gnome > To: Steve Brown <[EMAIL PROTECTED]>, BLFS Support List > <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1 > > Steve Brown wrote these words on 07/18/05 14:09 CST: > > I've built Gnome 2.11 from sources from the ground up. > > GNOME-2.11 is an unstable version. > > I'm sure the GNOME developers would love you to continue installing > and filing bug reports, but GNOME-2.11 will *always* be an unstable > version. It may compile and perform okay, but will *always* be > considered an unstable version. > > You should stick with GNOME-2.10.2 or wait until GNOME-2.12 is > released before you should count on any stability. There may be > folks here who can provide suggestions or patches, but BLFS will not > provide official support for known unstable packages. > > I suppose this explains your previous message from the 15th. I didn't > comment at the time, as I had no clue what could be the problem. The > GNOME-2.10.1 series of packages compiled easily with no issues that > I can think of. > > -- > Randy > > rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3] > [GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686] > 15:26:00 up 107 days, 14:59, 2 users, load average: 0.49, 0.14, 0.04 > > ------------------------------ > > Message: 7 > Date: Mon, 18 Jul 2005 15:42:52 -0500 > From: Steve Brown <[EMAIL PROTECTED]> > Subject: Re: Can't set desktop background image in Gnome > To: BLFS Support List <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1 > > On 7/18/05, Randy McMurchy <[EMAIL PROTECTED]> wrote: > > Steve Brown wrote these words on 07/18/05 14:09 CST: > > GNOME-2.11 is an unstable version. > > > > You should stick with GNOME-2.10.2 or wait until GNOME-2.12 is > > released before you should count on any stability. There may be > > folks here who can provide suggestions or patches, but BLFS will not > > provide official support for known unstable packages. > > Not looking for official support, just ideas as to what the problem > could be. After all, LFS is about "your distro, your rules" (to quote > the banner across the (B)LFS home page). Isn't this list for help of > blfs-users? > > > I suppose this explains your previous message from the 15th. > > No, that mas a malformed file name in the 2.11.5 package. The issue > was fixed in the 2.11.6 release. > > ------------------------------ > > Message: 8 > Date: Mon, 18 Jul 2005 17:05:08 -0600 > From: Archaic <[EMAIL PROTECTED]> > Subject: non-existant lp and parport devices > To: [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=us-ascii > > I seem to be failing miserably at my first attempt to print with a 2.6 > kernel and udev. I've tried building parport and parport_pc modularly > and non-modularly, with and without ieee1284 support and with and > without FIFO/DMA support. I've also tried forcing the base address and > IRQ. I've triple checked that the printer port is enabled in the BIOS > (as an ECP-capable port). With parport and parport_cp built > non-modularly and with no kernel args, dmesg gives: > > parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE] > parport0: irq 7 detected > parport0: Printer, HEWLETT-PACKARD OFFICEJET R80XI > > However, udev does not make any parport or lp device files. I've tried > creating both manually. Echoing anything to them gives me: > > bash: /dev/lp0: No such device or address > > I've tried lp0 to 4 and parport0 to 4. I've verified that the udev rules > have both parport and lp rules. Cups claims the URI to the printer is: > > Device URI: parallel:/dev/unknown-parallel0 > > This is the first time I've ever attempted to use a printer on this > computer, so I'm not even sure if the port is screwed up or not. I only > know that the dmesg output is confusing at best. > /proc/sys/dev/parport/parport0/irq seems to suggest that the IRQ is > wrong. So I switched to a modular parport so I could try different > options. I explicitly passed modprobe parport_pc io=0x378 irq=7 and got: > > parport0: PC-style at 0x378 (0x778), irq 7, dma 7 > [PCSPP,TRISTATE,COMPAT,ECP,DMA] > parport0: Printer, HEWLETT-PACKARD OFFICEJET R80XI > > This time /proc/sys/dev/parport/parport0/{dma,irq} show something other > than -1 so it would seem that all is good. However, after deleting the > printers and trying again I'm not even given the chance to choose the > parallel port. Trying with lpadmin gives: > > lpadmin: add-printer (set device) failed: client-error-not-possible > > So I guess my question is which part of the puzzle is responsible for > creating the devices? > > -- > Archaic > > Want control, education, and security from your operating system? > Hardened Linux From Scratch > http://www.linuxfromscratch.org/hlfs > > > ------------------------------ > > Message: 9 > Date: Tue, 19 Jul 2005 02:42:14 +0200 > From: Joern Abatz <[EMAIL PROTECTED]> > Subject: Re: non-existant lp and parport devices > To: BLFS Support List <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=us-ascii > > On Mon, Jul 18, 2005 at 05:05:08PM -0600, Archaic wrote: > > I seem to be failing miserably at my first attempt to print with a 2.6 > > kernel and udev. I've tried building parport and parport_pc modularly > > and non-modularly, with and without ieee1284 support and with and > > without FIFO/DMA support. I've also tried forcing the base address and > > IRQ. I've triple checked that the printer port is enabled in the BIOS > > (as an ECP-capable port). With parport and parport_cp built > > non-modularly and with no kernel args, dmesg gives: > > > > parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE] > > parport0: irq 7 detected > > parport0: Printer, HEWLETT-PACKARD OFFICEJET R80XI > > > > However, udev does not make any parport or lp device files. I've tried > > creating both manually. Echoing anything to them gives me: > > > > bash: /dev/lp0: No such device or address > > > > I've tried lp0 to 4 and parport0 to 4. I've verified that the udev rules > > have both parport and lp rules. Cups claims the URI to the printer is: > > > > Device URI: parallel:/dev/unknown-parallel0 > > > > This is the first time I've ever attempted to use a printer on this > > computer, so I'm not even sure if the port is screwed up or not. I only > > know that the dmesg output is confusing at best. > > /proc/sys/dev/parport/parport0/irq seems to suggest that the IRQ is > > wrong. So I switched to a modular parport so I could try different > > options. I explicitly passed modprobe parport_pc io=0x378 irq=7 and got: > > > > parport0: PC-style at 0x378 (0x778), irq 7, dma 7 > > [PCSPP,TRISTATE,COMPAT,ECP,DMA] > > parport0: Printer, HEWLETT-PACKARD OFFICEJET R80XI > > > > This time /proc/sys/dev/parport/parport0/{dma,irq} show something other > > than -1 so it would seem that all is good. However, after deleting the > > printers and trying again I'm not even given the chance to choose the > > parallel port. Trying with lpadmin gives: > > > > lpadmin: add-printer (set device) failed: client-error-not-possible > > > > So I guess my question is which part of the puzzle is responsible for > > creating the devices? > > You need both a kernel driver for parallel ports and another one for printer > support. Unfortunately they are in completely different places in the 'make > menuconfig' dialog: parallel port support is in the main menu, and printer > support is in 'device drivers/character devices'. > > 'No such file' means: /dev/lp0 is missing. 'No such device' means: the > kernel driver associated with /dev/lp0 is not answering. A list of drivers > and device files can be found in kernel/Documentation/devices.txt. > > 'lsmod' gives a list of loaded modules. 'cat /proc/devices' gives a list of > available devices in the kernel (though the corresponding files in /dev may > still not exist). > > The udev rules for /dev/lp* are in /etc/udev like: > KERNEL="lp[0-9]*", GROUP="lp" > KERNEL="parport[0-9]*", GROUP="lp" > > (I have a kernel device 'lp', but no 'parport', so maybe the parport rule > is not necessary, I don't know.) > > If you change the udev rules file, you need to call > '/etc/rc.d/init.d/udev start' once to make udev read the rules again. > > Joern > > ------------------------------ > > Message: 10 > Date: Mon, 18 Jul 2005 18:47:19 -0600 > From: Archaic <[EMAIL PROTECTED]> > Subject: Re: non-existant lp and parport devices > To: BLFS Support List <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=us-ascii > > On Tue, Jul 19, 2005 at 02:42:14AM +0200, Joern Abatz wrote: > > > > You need both a kernel driver for parallel ports and another one for printer > > support. Unfortunately they are in completely different places in the 'make > > menuconfig' dialog: parallel port support is in the main menu, and printer > > support is in 'device drivers/character devices'. > > Uggh. I can't believe I overlooked such an obvious thing. Thanks for the > cluebat. > > -- > Archaic > > Want control, education, and security from your operating system? > Hardened Linux From Scratch > http://www.linuxfromscratch.org/hlfs > > > ------------------------------ > > Message: 11 > Date: Mon, 18 Jul 2005 18:13:06 -0700 (GMT-07:00) > From: Roberto Perpuly <[EMAIL PROTECTED]> > Subject: Xorg, KDE come up to a white screen > To: [email protected] > Message-ID: > <[EMAIL PROTECTED]> > > Content-Type: text/plain; charset=us-ascii > > Hi all, > > I am having a problem with Xorg and KDE. I run startx using the following > .xinitrc file > > xterm -g 80x40+0+0 & > xclock -g 100x100-0+0 & > twm > > startx comes up to a white screen with a square in the middle, and nothing > else. I can't do anything but reboot. I reboot, then re-run Xorg > -configure, and get a gray screen with a movable mouse cursor. I copy the > xorg.conf.new to /etc/X11/xorg.conf. I re-run startx, then I get the the > xterm window and the xclock window. All good right? I close twm, then try > rerunning startx. I get the same blank white screen with a square in the > middle. > > I change the .xinitrc file to > > exec startkde > > startx comes up to a white screen with a square in the middle, and nothing > else. I reboot, then re-run Xorg -configure, and get a gray screen with a > movable mouse cursor. I copy the xorg.conf.new to /etc/X11/xorg.conf. I > re-run startx, then KDE comes up beautifully. All good right? I close KDE, > then try rerunning startx. I get the same blank white screen with a square > in the middle. > > > Can any tell me if Xorg / KDE compiled wrong, or did I miss something?? > > RP > > ------------------------------ > > Message: 12 > Date: Mon, 18 Jul 2005 22:50:06 -0400 > From: Chris Staub <[EMAIL PROTECTED]> > Subject: Re: Xorg, KDE come up to a white screen > To: Roberto Perpuly <[EMAIL PROTECTED]>, BLFS Support List > <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=us-ascii; format=flowed > > Roberto Perpuly wrote: > > Hi all, > > > > I am having a problem with Xorg and KDE. I run startx using the following > > .xinitrc file > > > > xterm -g 80x40+0+0 & > > xclock -g 100x100-0+0 & > > twm > > > > startx comes up to a white screen with a square in the middle, and nothing > > else. I can't do anything but reboot. I reboot, then re-run Xorg > > -configure, and get a gray screen with a movable mouse cursor. I copy the > > xorg.conf.new to /etc/X11/xorg.conf. I re-run startx, then I get the the > > xterm window and the xclock window. All good right? I close twm, then try > > rerunning startx. I get the same blank white screen with a square in the > > middle. > > > > I change the .xinitrc file to > > > > exec startkde > > > > startx comes up to a white screen with a square in the middle, and nothing > > else. I reboot, then re-run Xorg -configure, and get a gray screen with a > > movable mouse cursor. I copy the xorg.conf.new to /etc/X11/xorg.conf. I > > re-run startx, then KDE comes up beautifully. All good right? I close > > KDE, then try rerunning startx. I get the same blank white screen with a > > square in the middle. > > > > > > Can any tell me if Xorg / KDE compiled wrong, or did I miss something?? > > > > RP > > I've had that problem before. I'm pretty sure that the only difference > between the system that had this problem and the one that worked was > that the system with that problem didn't have gettext installed. But > then I'm not an expert and this probably isn't it, but I am sure I > installed X correctly (the same way I had done it several other times) > and just that one time, when I built lfs without gettext, it didn't work. > > ------------------------------ > > -- > http://linuxfromscratch.org/mailman/listinfo/blfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page > > End of blfs-support Digest, Vol 723, Issue 1 > ******************************************** > -- -------------------------------------------------------------------- [EMAIL PROTECTED] born to be root -------------------------------------------------------------------- -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
