>Ok, maybe I will try the fakeroot system, maybe combined with paco, >because I wanted to install many packages at the same time and (if I >understood correctly) with only paco is not possible.
That is definitely not wise. There has been a fundamental rule in computing in the 40 odd years of my career: "Only change ONE thing at a time!" Paul Rogers ([EMAIL PROTECTED]) http://www.xprt.net/~pgrogers/ Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) ------------------------------ Message: 2 Date: Sun, 12 Aug 2007 08:56:30 +0000 From: "Cubo Aula Info" <[EMAIL PROTECTED]> Subject: Re: uninstalling To: "BLFS Support List" <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1 I forgot.. Really thanks to everybody Luca On 12/08/07, Cubo Aula Info <[EMAIL PROTECTED]> wrote: > Ok, maybe I will try the fakeroot system, maybe combined with paco, > because I wanted to install many packages at the same time and (if I > understood correctly) with only paco is not possible. > ------------------------------ Message: 3 Date: Sun, 12 Aug 2007 09:01:22 +0000 From: "Cubo Aula Info" <[EMAIL PROTECTED]> Subject: kernels To: "BLFS Support List" <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1 Hi to everybody, I have another question: are there kernels (others than linux or linux-patched) that work with a gnu system? GNU Hurd should be one. Others? thanks Luca ------------------------------ Message: 4 Date: Sun, 12 Aug 2007 11:24:51 +0200 From: Nicolas FRANCOIS <[EMAIL PROTECTED]> Subject: Re: uninstalling To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1 Le Fri, 10 Aug 2007 07:41:02 +0000 "Cubo Aula Info" <[EMAIL PROTECTED]> a ?crit : > So the questions are: > 1) does somebody use install-log and can tell me if it works ok or if > there are situation where if fails? I use this script, provided a long time ago by Gerard : -------------> /usr/bin/filelist <------------------ #!/bin/sh if [ -z $1 ] then echo "Usage: $0 outputfile" exit 1 fi clear PRUNEPATH="/old /sources /download /usr/src /proc /var/install-logs /tmp /root /home /var/run /dev /mnt /var/spool /var/lock " PRUNEREGEX=`echo $PRUNEPATH|sed -e 's,^,\\\(^,' -e 's, ,$\\\)\\\|\\\(^,g' -e 's,$,$\\\),'` echo "Collecting current files..." find / -regex "$PRUNEREGEX" -prune -o -print > /var/install-logs/before-inst echo echo "Start the installation of $1 now." echo "Press a key when you are done to continue..." read echo "Collecting new files..." find / -regex "$PRUNEREGEX" -prune -o -print > /var/install-logs/after-inst cd /var/install-logs echo "Creating difference output.." diff before-inst after-inst > $1 echo "Modifying difference output file..." sed s/"> "// $1 > $1-new mv $1-new $1 cat $1 | grep / > $1-new mv $1-new $1 echo "Removing temporary files..." rm before-inst after-inst echo "Opening output file in editor..." vi $1 echo "Done" -------------> /usr/bin/filelist <------------------ Works fine for me, no problem to understand what it does, no big dependency... When I want to uninstall something : cat /var/install-logs/toto-utl | xargs rm and I suppress by hand the few remaining directories not deleted by the command above. \bye -- Nicolas FRANCOIS http://nicolas.francois.free.fr A TRUE Klingon programmer does NOT comment his code ------------------------------ Message: 5 Date: Sun, 12 Aug 2007 15:42:39 +0530 From: "anirudh vij" <[EMAIL PROTECTED]> Subject: Re: kernels To: "BLFS Support List" <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="iso-8859-1" Xen...though it it essentially a modifies linux kernel. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://linuxfromscratch.org/pipermail/blfs-support/attachments/20070812/bccc813b/attachment-0001.html ------------------------------ Message: 6 Date: Sun, 12 Aug 2007 09:04:40 -0400 From: john q public <[EMAIL PROTECTED]> Subject: can't build PAM To: BLFS Support List <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Ive tried 2 versions of PAM and get similar errors on trying to build tst-pam_limits1.c:130: error: `RLIMIT_NICE' undeclared I think its due to trying this on an old LFS system but I'm not sure. Any idea? ------------------------------ Message: 7 Date: Sun, 12 Aug 2007 15:54:36 +0000 From: "Cubo Aula Info" <[EMAIL PROTECTED]> Subject: Re: uninstalling To: "BLFS Support List" <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1 I have looked paco, I was curious to know if this % (from man paco) % Due to LD_PRELOAD limitations, paco can't follow the trace of suid pro- % grams. % For the same reason, paco does not work with programs that statically % link libc. can create problems to a normal blfs installation and if those problems are avoided with the method suggested by Dan (fakeroot and then paco) : make DESTDIR=$dest install paco -lp+ $program "tar -C $dest -cpf- . | tar -C / -xpf-" I also tried slackware pkgtools and I have a question: why makepkg does remove all symlinks before tarring and puts them in a post-install file? ------------------------------ Message: 8 Date: Sun, 12 Aug 2007 09:23:56 -0700 From: "Dan Nicholson" <[EMAIL PROTECTED]> Subject: Re: uninstalling To: "BLFS Support List" <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1 On 8/12/07, Cubo Aula Info <[EMAIL PROTECTED]> wrote: > I have looked paco, I was curious to know if this > > % (from man paco) > % Due to LD_PRELOAD limitations, paco can't follow the trace of suid pro- > % grams. > % For the same reason, paco does not work with programs that > statically > % link libc. > > can create problems to a normal blfs installation and if those > problems are avoided with the method suggested by Dan (fakeroot and > then paco) : > > make DESTDIR=$dest install > paco -lp+ $program "tar -C $dest -cpf- . | tar -C / -xpf-" This was the original reason I started doing this, but it's rare that this is actually a problem. The only package I know of where you're using a statically linked binary during the installation is glibc. It creates it's symbolic links in /lib with a static binary (since it may replace the existing dynamic linker, wreaking havoc). This results in a few unlogged files during glibc. But if you only install glibc once at the beginning of Ch. 6 (which you probably should do since reinstalling glibc is risky), then you can just run a find on /lib. find /lib -name "*.so" | paco -lp+ glibc The DESTDIR has a lot of power, but also a lot drawbacks. It's the simplest for bundling a package since you avoid interaction with /. Also, it's nice when you want to make further adjustments such as moving files. But it causes problems when part of the installation process expects to use the files it has just installed, often when rebuilding a cache file like /etc/ld.so.cache. Since you didn't really install it to / yet, it won't work. You end up having to recreate many actions after your real installation. This is the main reason for the %post directive in rpm. Read the fakeroot hint for more details. If you just want to get started, I'd suggest just using paco on its own. The drawbacks are far outweighed by the simplicity and power. -- Dan ------------------------------ Message: 9 Date: Sun, 12 Aug 2007 16:31:30 GMT From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> Subject: Re: uninstalling To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=us-ascii >I just tried git (Guarded Installation Tool) on a gentoo box. But the >result is not good: In a broad sense, that's possible with git. It helps the sysadmin, but (s)he has to use it properly--no script is clairvoyant. >But this is not important, maybe I have to configure it... A little bit, depending on how your system is setup. >What I'd like to know is how does it work (i mean internal, not the >user-end commands) ? Vladimir gave you a brief idea. git's task is to find out what changed when you installed the package. (RPM has to be told by the spec file, and git can't make presumptions that it already knows what the system contains.) So it has to look at what WAS there before installation & what's there NOW. (Let the install process monopolize the machine so something you do in a vterm doesn't get confused with what the installation does. And watchout for cron jobs.) Personally, I _like_ the fact that it looks. It gives me some confidence that some oddball make file didn't do something that got missed, and I can use the make file as it was intended, without worrying that tricks, like fakeroot, might not work with this one. >and does it take *always* 5+11 minutes? (I tried twice and it did) It depends on how much **** you have in the directories it has to watch. Did you optimize drive access with hdparm? On a lean, clean system, (and as one builds the early steps of LFS ;-), it isn't so bad. And I, personally, can afford to take the time the one time I do the package install. Call it an "investment". Paul Rogers ([EMAIL PROTECTED]) http://www.xprt.net/~pgrogers/ Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) ------------------------------ Message: 10 Date: Sun, 12 Aug 2007 21:11:34 +0400 From: "Vladimir A. Pavlov" <[EMAIL PROTECTED]> Subject: Re: can't build PAM To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="iso-8859-1" On Sunday 12 August 2007 17:04, john q public wrote: > Ive tried 2 versions of PAM and get similar errors on trying to build > > tst-pam_limits1.c:130: error: `RLIMIT_NICE' undeclared > > I think its due to trying this on an old LFS system but I'm not sure. You're right :) This #define appeared before 2.6.18 (I don't have older versions and therefore I cannot say when exactly it appeared) and can be found in linux-<version>/include/asm-generic/resource.h. Try building and booting a new kernel (2.6.18 or later) and running the following sed right after unpacking the Linux-PAM source: sed -i 's/RLIMIT_NICE/13/' xtests/tst-pam_limits1.c The value of 13 was found in the sources of linux-2.6.18.6. You have to sed Linux-PAM sources becasue your kernel-headers are too old and they don't contain the definition. After that the testsuite should go fine. But I don't think the compiled Linux-PAM will be usable on a kernel not having RLIMIT_NICE definition in its source. IOW, the newly compiled Linux-PAM will be broken if being used with an old kernel. BTW, what kernel version do you have? -- Nothing but perfection Vladimir ------------------------------ Message: 11 Date: Sun, 12 Aug 2007 21:15:55 +0400 From: "Vladimir A. Pavlov" <[EMAIL PROTECTED]> Subject: Re: uninstalling To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="iso-8859-1" On Sunday 12 August 2007 19:54, Cubo Aula Info wrote: > I have looked paco, I was curious to know if this > > % (from man paco) > % Due to LD_PRELOAD limitations, paco can't follow the trace of suid pro- > % grams. > % For the same reason, paco does not work with programs that > statically > % link libc. > > can create problems to a normal blfs installation and if those > problems are avoided with the method suggested by Dan (fakeroot and > then paco) : Dan's method avoid such problems since the only program he uses with paco is tar which is neither SUID nor statically linked. > I also tried slackware pkgtools and I have a question: > why makepkg does remove all symlinks before tarring and puts them in a > post-install file? AFAIK it also requires tar version 1.13 exactly, no above, no below. I don't know why :( -- Nothing but perfection Vladimir ------------------------------ Message: 12 Date: Mon, 13 Aug 2007 08:30:40 +0530 From: Shayin C K <[EMAIL PROTECTED]> Subject: Detecting network card To: BLFS Support List <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed My LFS system does not detect my network card. The error message I get is Interface eth0 does not exist. The card is detected on my Fedora 7 distro without any problems. I checked the kernel config file to see if I had accidently left out networking support. Nothing like that. In /etc/sysconfig/network, networking is 'yes. Similarly, in /etc/sysconfig/network-devices/ I have four files-dhcpcd, dhclient, pppoe, ipv4. Networking is 'yes' is all of them. Am I missing something, or is it the presence of all four files causing some problems. Thanks in advance. Regards Shayin ------------------------------ Message: 13 Date: Sun, 12 Aug 2007 22:19:22 -0600 From: "Rick Shelton" <[EMAIL PROTECTED]> Subject: Re: Detecting network card To: "BLFS Support List" <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1 On 8/12/07, Shayin C K <[EMAIL PROTECTED]> wrote: > My LFS system does not detect my network card. > The error message I get is Interface eth0 does not exist. The card is > detected on my Fedora 7 distro without any problems. > I checked the kernel config file to see if I had accidently left out > networking support. Nothing like that. > In /etc/sysconfig/network, networking is 'yes. Similarly, in > /etc/sysconfig/network-devices/ I have four files-dhcpcd, dhclient, > pppoe, ipv4. Networking is 'yes' is all of them. Am I missing something, > or is it the presence of all four files causing some problems. just missing some details from the machine in question. It may be a pain, but please try to find relevant messages from the output of the dmesg command. also, what kind of card do you have and what driver is your kernel built with? i want to say that dhcpcd and dhclient are mutually exclusive. but i do not know for sure. you might want to disable startup of one or the other and see what happens. ~ ------------------------------ Message: 14 Date: Sun, 12 Aug 2007 22:52:42 -0700 From: "Dan Nicholson" <[EMAIL PROTECTED]> Subject: Re: Detecting network card To: "BLFS Support List" <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1 On 8/12/07, Rick Shelton <[EMAIL PROTECTED]> wrote: > On 8/12/07, Shayin C K <[EMAIL PROTECTED]> wrote: > > My LFS system does not detect my network card. > > The error message I get is Interface eth0 does not exist. The card is > > detected on my Fedora 7 distro without any problems. > > I checked the kernel config file to see if I had accidently left out > > networking support. Nothing like that. Most likely the issue is that you left out the driver for your network card. If you do have the driver (in kernel or as a module) it should be auto-loaded. It should be somewhere under Drivers -> Net. > > In /etc/sysconfig/network, networking is 'yes. Similarly, in > > /etc/sysconfig/network-devices/ I have four files-dhcpcd, dhclient, > > pppoe, ipv4. Networking is 'yes' is all of them. Am I missing something, > > or is it the presence of all four files causing some problems. No. Although, you will get conflicts if you try to run both dhcp clients, you're problem right now is that you're just not getting a device set up. Only the kernel and udev can control that. > i want to say that dhcpcd and dhclient are mutually exclusive. > but i do not know for sure. > you might want to disable startup of one > or the other and see what happens. You would definitely want to disable one or the other. They're both daemons that will run constantly and try to set IP addresses, gateway, etc. -- Dan ------------------------------ -- 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 1331, Issue 1 ********************************************* -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
