6.53. Psmisc-22.11
ln -sv killall /bin/pidof
6.56. Sysvinit-2.86
sysvinit-2.86/src/Makefile:126
ln -sf ../sbin/killall5 $(ROOT)/bin/pidof
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the abo
On this topic, I too had a notion that what I call "Lab Notes" would have
been an improvement and perhaps call users attention to important
procedures.
I did this for my self, as the text does a good job of explaining the what
and the how,but the how is embedded in the text, and not as easily foll
On 5/27/10, JimD. wrote:
> On this topic, I too had a notion that what I call "Lab Notes" would have
> been an improvement and perhaps call users attention to important
> procedures.
>
I like that.
In the BLFS book, each package has "user notes" that link to a wiki
page if it exists. Those are not
> > make[2]: Entering directory `/usr/local/src/glibc-2.11.1/nscd'
> > make[2]: Leaving directory `/usr/local/src/glibc-2.11.1/nscd'
> > make[2]: Entering directory `/usr/local/src/glibc-2.11.1/nscd'
> >
> > gcc nscd.c -c -std=gnu99 -fgnu89-inline -O2 -O3 -Wall -Winline -Wwrite-
> > strings -fmerge
> > Have built LFS-4.1& -6.1, trying to build -6.6 on -6.1. Stage 1
> > seemed to go well. Building glibc early in Stage2 failed. I did a
> > search, saw others had a similar problem, but didn't see a relevant
> > solution. The /scripts in my $PATH is where I put my cut&pasted
> > "build scrip
On 05/27/2010 06:30 AM, xinglp wrote:
> 6.53. Psmisc-22.11
> ln -sv killall /bin/pidof
>
>
> 6.56. Sysvinit-2.86
> sysvinit-2.86/src/Makefile:126
> ln -sf ../sbin/killall5 $(ROOT)/bin/pidof
Not sure what you're trying to show about Sysvinit's instructions (some
explanat
Install sysvinit-2.86 overwrite /bin/pidof.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
On 05/27/2010 01:38 PM, xinglp wrote:
> Install sysvinit-2.86 overwrite /bin/pidof.
No it doesn't. The instruction to create a /bin/pidof symlink on the
Psmisc page is explicitly described as something to add if you *don't*
install Sysvinit...
"If Sysvinit will not be used for a particular syst
> After you get to this stoppage, try doing a paste of just these
> instructions back with modifications. To do that, you need to paste
> into vim and add backslashes to each line, change what you want (delete
> -fstack-protector) and see if you can get that one file
> (build/nscd/nscd.o) to b
Paul Rogers wrote:
> OK, I did that. It paused about one
> second, then returned a command prompt. No console messages at all.
> Ummm, waita minute! (I don't compile anything unless I'm installing
> a package--I finished being a programmer over 25 years ago.) I guess
> that means it worked, eh?
Paul Rogers wrote:
[...]
> Yes, I've seen that in some of the other distros I've gotten from LXF.
> Using SCSI emulation for IDE drives just seems WRONG somehow. I'm a
"Wrong headed" I'd say. However, if you think you do anything but
use Linux, then you're wrong. Influencing the course of it is
Thank you that was the issue. I have vmware on a imac and when I paused it
the clock didn't reset after starting back up.
I appreciate your response. I finally got to chapter 6.
Thanks
Timothy
> On Sun, May 23, 2010 at 5:30 PM, Timothy Powell wrote:
> > After a couple of hours running I sto
You are right. I found the "If Sysvinit will not be used for a
particular system, complete the
installation of Psmisc by creating the following symlink:".
And I also fount Psmisc's pidof does not work with lfs-bootscript.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://ww
On 5/27/10, Paul Rogers wrote:
[Ken Moffat]
>> getting from a .config that worked in 2.6.18 to one that works in
>> 2.6.32. Particularly, libata [ most ide drives now use libata and
>> therefore /dev/sdXn instead of hdXn ].
[Paul Rogers]
> Yes, I've seen that in some of the other distros I've go
I tried restarting the make, but it just failed with the next routine
in the list, connect.c. I expected that, it's using the same
parameter list. I did grep for -fstack-protector, and found it only
in the login & nscd directories. Then it occurred to me to check the
gcc package for that __stack
15 matches
Mail list logo