[lfs-support] pstree show wrong info
I've post it to upstream, but no response yet. http://sourceforge.net/tracker/?func=detailaid=3537508group_id=15273atid=115273 It happend when lots of processes is running, such as compiling somethings. Anyone can reproduce it ? 22.16 is normal init-+-acpid |-agetty |-klogd |-ntpd |-screen-+-bash---openwrt.sh---make---sh---make---bash---make---make---make---sh | |-bash | `-bash---pstree |-sshd-+-sshd---sshd---sftp-server | `-sshd---sshd---bash---screen |-syslogd `-udevd---udevd but since 22.17 and later init-+-2*[screen-+-bash---openwrt.sh---make---sh---make---bash---make---make---make---sh] | |-bash] | `-bash---pstree] |-bash---pstree |-bash---openwrt.sh---make---sh---make---bash---make---make---make---sh |-acpid |-agetty |-klogd |-ntpd |-sshd-+-sshd---sshd---sftp-server | `-sshd---sshd---bash---screen |-syslogd `-udevd---udevd and htop can display the right things. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Cannot boot to LFS with seperate boot partition
On Mon, 25 Jun 2012 17:24:12 +0100
Yasser Zamani yasser.zam...@live.com wrote:
root@slax:~# cat /mnt/sda7/grub/grub.cfg
# Begin /boot/grub/grub.cfg
set default=0
set timeout=5
# WHEN I SELECT THIS ENTRY IT TELLS error: no argument specified BUT AFTER
KEY PRESS ENTERS TO WINDOWS SUCCESSFULLY
menuentry Windows 7 (loader) (on /dev/sda3) {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set 125c5cdd5c5cbd63
chainloader +1
}
My guess is that it's the search line that's causing the error: no
argument specified message. try removing it.
# WHEN I SELECT THIS ONE IT TELLS error: file not found BUT AFTER KEY PRESS
ENTERS TO LFS SUCCESSFULLY
menuentry GNU/Linux, Linux 3.4.1-lfs-SVN-20120617 {
insmod ext3
set root=(hd0,7)
linux /vmlinuz-3.4.1-lfs-SVN-20120617 root=/dev/sda6 ro
}
Is there an ext3.mod? I only have ext2.mod but I find that I've never
needed to insmod anything, grub always does it automatically. Try
removing the insmod line.
The way to test changes is to leave int the entries that work but make
a duplicate with the new modifications (that way you can still boot
with the original entry). Try adding this to your grub.cfg:
menuentry Windows 7 testing {
set root='(hd0,msdos3)'
chainloader +1
}
menuentry GNU/Linux testing {
set root=(hd0,7)
linux /vmlinuz-3.4.1-lfs-SVN-20120617 root=/dev/sda6 ro
}
Andy
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] Cannot boot to LFS with seperate boot partition
Date: Mon, 25 Jun 2012 23:57:45 -0600
From: e_lio...@hotmail.com
To: lfs-support@linuxfromscratch.org
Subject: Re: [lfs-support] Cannot boot to LFS with seperate boot partition
Hello,
Errors like error: no argument specified usually point to something
missing. Try:
search --no-floppy --fs-uuid --set=root 125c5cdd5c5cbd63
Notice that '--set' needs the arguement '=root' in this case.
If needed to 'trick' Windows into believing it is on the first
partition, add this line right above 'chainloader +1' :
drivemap -s (hd0) ${root}
You're both genius, Ellies! As you recommended, following menuentry sorted the
no argument specified out:
menuentry Windows 7 (loader) (on /dev/sda3) {
insmod part_msdos
insmod ntfs
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set=root 125c5cdd5c5cbd63
drivemap -s (hd0) ${root}
chainloader +1
}
Thank you very much, both Ellies specially Elly#2 ;)
Date: Tue, 26 Jun 2012 10:55:24 +0100
From: a...@benton.eu.com
To: lfs-support@linuxfromscratch.org
Subject: Re: [lfs-support] Cannot boot to LFS with seperate boot partition
Is there an ext3.mod? I only have ext2.mod but I find that I've never
needed to insmod anything, grub always does it automatically. Try
removing the insmod line.
You have eagle eyes Andy! You're right. When I formatted the boot partition
with ext3, I thought I should rewrite insmod ext2 to insmod ext3. But now,
as you suggested, rolling back the mistake sorted error: file not found out
as below:
menuentry GNU/Linux, Linux 3.4.1-lfs-SVN-20120617 {
insmod ext2
set root=(hd0,7)
linux /vmlinuz-3.4.1-lfs-SVN-20120617 root=/dev/sda6 ro
}
Thanks a lot Andy!
Andy
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [blfs-support] wget: unable to resolve host address
On Tue, 26 Jun 2012 10:55:32 +0100 Omar vic...@yahoo.com.cn wrote: Hi, all, I used wget to download and got the following prompt. http://anduin.linuxfromscratch.org/files/BLFS/svn/xorg/proto-7.7-1.md5 Resolving anduin.linuxfromscratch.org... failed: Name or service not known. wget: unable to resolve host address `anduin.linuxfromscratch.org' I doubt that my parsing of domain name is wrong. For other example I can get response from ping 192.168.x.x but can't from ping www.google.com and it tells me unknown host. Any suggestions? cat /etc/resolv.conf HERE_DOC nameserver 8.8.4.4 nameserver 8.8.8.8 HERE_DOC Andy -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] /etc/fstab
Alexander Kapshuk wrote:
I'd appreciate it if somebody could please have a look at my /etc/fstab
file shown below and let me know if it's OK. I've searched this mailing
list's archives and an example /etc/fstab I found was a bit different to
mine. I also had a look at the /etc/fstab files on a Ubuntu and Debian
systems, but they weren't as detailed as mine.
In particular, I'd like to know whether it is my /boot partition or /
partition that has to be checked by fsck. Is it OK for /boot to be ext3,
or should I have made it ext2? Googling it suggests that it's probably
better for it to be ext2, but ext3 should do fine as well.
The /boot partition is rarely written. The purpose of a journaled file
system is to recover written data in a cache that is in the journal an
not properly committed to the disk in the case of a power/system failure.
Making /boot ext3 is OK, but it really doesn't add anything significant
to the system.
:; mount
...
/dev/sda5 on /mnt/lfs/boot type ext3 (rw)
/dev/sda6 on /mnt/lfs type ext3 (rw,commit=0,commit=0)
/dev/sda7 on /mnt/lfs/opt type ext3 (rw,commit=0,commit=0)
/dev/sda8 on /mnt/lfs/usr/src type ext3 (rw,commit=0,commit=0)
/dev/sda9 on /mnt/lfs/home type ext3 (rw,commit=0,commit=0)
/dev on /mnt/lfs/dev type none (rw,bind)
devpts on /mnt/lfs/dev/pts type devpts (rw)
shm on /run/shm type tmpfs (rw)
proc on /mnt/lfs/proc type proc (rw)
sysfs on /mnt/lfs/sys type sysfs (rw)
root@hostname:~# file -s /dev/sda[5-9] | awk '{ print $1,$8 }'
/dev/sda5: UUID=64b0a82e-4500-49c0-b426-e97562ed0585
/dev/sda6: UUID=a2f6cc54-c7d7-41e9-8e00-123da318f743
/dev/sda7: UUID=140b05f2-6ca5-4cc8-b45b-52e6e6d2e164
/dev/sda8: UUID=a6563b03-a212-47b0-b6cc-7f767768852d
/dev/sda9: UUID=0901943d-ab94-423a-accb-cd425d3d13c1
An interesting alternative to dumpe2fs.
root:/# cat /etc/fstab
# Begin /etc/fstab
# file system mount point type options dump pass
UUID=64b0a82e-4500-49c0-b426-e97562ed0585 /boot ext3 defaults 0 2
UUID=a2f6cc54-c7d7-41e9-8e00-123da318f743 / ext3 defaults 0 1
UUID=140b05f2-6ca5-4cc8-b45b-52e6e6d2e164 /opt ext3 defaults 0 2
UUID=a6563b03-a212-47b0-b6cc-7f767768852d /usr/src ext3 defaults 0 2
UUID=0901943d-ab94-423a-accb-cd425d3d13c1 /home ext3 defaults 0 2
UUID=c0882b91-9df5-43f9-b5e3-d77d68b53a33 none swap sw 0 0
proc /proc proc nosuid,noexec,nodev 0 0
sysfs /sys sysfs nosuid,noexec,nodev 0 0
devpts /dev/pts devpts gid=4,mode=620 0 0
tmpfs /run tmpfs defaults 0 0
devtmpfs /dev devtmpfs mode=0755,nosuid 0 0
As Ken said, the UUIDs are meaningless until udev is started. Since
that's pretty early in the boot process, this should work fine. Note
that you cannot use UUIDs in the GRUB linux line unless you use an initrd.
My partition allocation is almost the same as yours. Unlike others, I
do like to put some things on /opt (Xorg, KDE, Qt, JDK, others).
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [blfs-support] CUPS problem: lp: Unsupported document-format text/plain.
Andrew Benton wrote: On Tue, 26 Jun 2012 11:25:12 +0100 Jeremy Henty onepo...@starurchin.org wrote: Fixed! I had to configure ghostscript-9.05 with --with-install-cups . [...] Perhaps this is worth mentioning on the BLFS Ghostscript page? Cups is an optional dependency of Ghostscript so I can't make this part of the default Ghostscript install instructions. What I can do is add a paragraph to the command explanations section mentioning this option. That would be ideal! Regards, Jeremy Henty -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] /etc/fstab
On 06/26/2012 10:18 PM, Bruce Dubbs wrote: The /boot partition is rarely written. The purpose of a journaled file system is to recover written data in a cache that is in the journal an not properly committed to the disk in the case of a power/system failure. Making /boot ext3 is OK, but it really doesn't add anything significant to the system. Understood. Thanks. As Ken said, the UUIDs are meaningless until udev is started. Since that's pretty early in the boot process, this should work fine. Note that you cannot use UUIDs in the GRUB linux line unless you use an initrd. My partition allocation is almost the same as yours. Unlike others, I do like to put some things on /opt (Xorg, KDE, Qt, JDK, others). -- Bruce Got it. Thanks. I've modified my /etc/fstab file as suggested by Ken. Compiling the kernel now. Alexander. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
[lfs-support] Error compiling Tcl 8.5.11 - Segmentation fault
Hello lfs list, I'm from Brazil and I'm new to the list, I became interested in lfs today and was testing to see if I could, but a problem arose in the covenant Tcl 8.5.11 when I run make install it returns me as follows: Installing libtcl8.5.so to / tools / lib / Installing tclsh as / tools/bin/tclsh8.5 Installing tclConfig.sh to / tools / lib Installing libtclstub8.5.a to / tools / lib Installing message catalogs segmentation fault make: *** [install-messages] Error 139 If anyone knows me explain what is happening will be grateful. thank you Fabio Mattes -- Fábio Mattes VL AgroIndustrial - Depto. T.I. 9622-5442 fabio_mat...@hotmail.com -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Error compiling Tcl 8.5.11 - Segmentation fault
Fábio Mattes wrote: Hello lfs list, I'm from Brazil and I'm new to the list, I became interested in lfs today and was testing to see if I could, but a problem arose in the covenant Tcl 8.5.11 when I run make install it returns me as follows: Installing libtcl8.5.so to / tools / lib / Installing tclsh as / tools/bin/tclsh8.5 Installing tclConfig.sh to / tools / lib Installing libtclstub8.5.a to / tools / lib Installing message catalogs segmentation fault make: *** [install-messages] Error 139 What you should see is: Installing libtclstub8.5.a to /tools/lib/ Installing message catalogs Creating msgs Making directory /tools/lib/tcl8.5/opt0.4 ... I suspect that you have done something wrong a bit earlier as that is the first time the built tcl is actually used. It looks like a compiler or library mis-match. You are not very far into the build, so I'd recommend starting over paying close attention to all the book's instructions. Make sure you have all the host requirements in section vii. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] Error compiling Tcl 8.5.11 - Segmentation fault
Ok Bruce start again I have forgotten a step. Thank you for the quick response. 2012/6/26 Bruce Dubbs bruce.du...@gmail.com Fábio Mattes wrote: Hello lfs list, I'm from Brazil and I'm new to the list, I became interested in lfs today and was testing to see if I could, but a problem arose in the covenant Tcl 8.5.11 when I run make install it returns me as follows: Installing libtcl8.5.so to / tools / lib / Installing tclsh as / tools/bin/tclsh8.5 Installing tclConfig.sh to / tools / lib Installing libtclstub8.5.a to / tools / lib Installing message catalogs segmentation fault make: *** [install-messages] Error 139 What you should see is: Installing libtclstub8.5.a to /tools/lib/ Installing message catalogs Creating msgs Making directory /tools/lib/tcl8.5/opt0.4 ... I suspect that you have done something wrong a bit earlier as that is the first time the built tcl is actually used. It looks like a compiler or library mis-match. You are not very far into the build, so I'd recommend starting over paying close attention to all the book's instructions. Make sure you have all the host requirements in section vii. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page -- Fábio Mattes VL AgroIndustrial - Depto. T.I. 9622-5442 fabio_mat...@hotmail.com -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
