Re: [lfs-support] systemd-udev

[Baho Utot]

On 08/24/2013 10:14 PM, Ken Moffat wrote:
> On Sat, Aug 24, 2013 at 08:54:02PM -0400, Walter Webb wrote:
>> My latest computer has two dvd's; only one is a writer.  I also have
>> a usb dvd writer that I occasionally use.  Pre systemd udev generated
>> /etc/udev/rules.d/70-persistent-cd.rules for the devices on the first
>> boot.  The first time I plugged in the usb device, entries were added
>> for that.  I never understood why it worked, but it did.
>>
>> For lfs-7.1, I eventually rebuilt it with pre systemd udev.  I built
>> lfs-7.2 and some of blfs, but decided to make lfs-7.3 work.
>>
>> After a lot of tries, I found that the old 70-persistent-cd.rules
>> worked after I replaced the ENV{ID_PATH} entries with ENV{ID_SERIAL}
>> entries.  With lfs-7.4, I will attemt to generate the file properly.
>>
>   That sounds odd - as if the usb writer appears ahead of, or
> between, the non-usb drives.  Do you plug it in before booting ?  If
> so, probably best not to do that (or make that change to ID_SERIAL
> to allow you to do it).  The appearance of drives connected via usb
> is random and may change across kernel versions, or across different
> kernel configs.
>
>> I had problems with my two ethernets.  Since they use different
>> drivers, I eventually found that building one driver in the kernel
>> and the other as a module kept them in consistent order.
>>
>>
>> I discovered the file /etc/sysconfig/udev_retry and added sound to
>> it.  This file must have appeared with sysstemd.
>>
>>
>> The latest problem I found a solution for was ejecting and closing
>> the dvd's.  I didn't know it was a systemd problem until I found a
>> solution on the net for similar problems.
>>
>> The file /lib/udev/rules.d/60-cdrom_id.rules has a line:
>>
>> IMPORT{program}="cdrom_id --lock-media $devnode"
>>
>> Removing "--lock-media" from this line fixed it.
>>
>   Thanks, I've got the same problem (on a built-in writer) with
> 7.4-rc1 except using eudev which now also has that same change.
> With an earlier version of eudev (back in April) eject mostly
> worked (failed once or twice over perhaps 30 uses).  I've added
> the need for a sed to fix this this on local builds to my ToDo
> list.  Seems to be a systemd problem, but I'm not surprised by that.
>
>   Does anyone else see eject failing to eject a CD/DVD with 7.3 or
> later ?  Eject is now part of util-linux so you don't need to
> install anything extra to test this, just put a CD or DVD in
> /dev/sr0.
>
> ĸen

on the latest SVN if a cd/dvd is in the drive eject works.
If no cd/dvd is in the drive eject does nothing.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] systemd-udev

[Baho Utot]

On 08/25/2013 10:44 AM, Ken Moffat wrote:
> On Sun, Aug 25, 2013 at 09:27:37AM -0400, Baho Utot wrote:
>> On 08/24/2013 10:14 PM, Ken Moffat wrote:
>>>Does anyone else see eject failing to eject a CD/DVD with 7.3 or
>>> later ?  Eject is now part of util-linux so you don't need to
>>> install anything extra to test this, just put a CD or DVD in
>>> /dev/sr0.
>> on the latest SVN if a cd/dvd is in the drive eject works.
>> If no cd/dvd is in the drive eject does nothing.
>   Odd.  As Bruce noted, it ought to let you open the drawer to load a
> CD.  My problem turns out to be different, and I'm not sure about
> the OP's problem with eject.
>
> ĸen

I have found that when there is not a cd/dvd in the drive there is no 
symlink /dev/cdrom so maybe eject then finds nothing to eject?
After a cd/dvd/ is placed into the drive /dev/cdrom  is there and eject 
works.

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] systemd-udev

[Baho Utot]

On 08/25/2013 11:36 AM, Bruce Dubbs wrote:
> Baho Utot wrote:
>> On 08/25/2013 10:44 AM, Ken Moffat wrote:
>>> On Sun, Aug 25, 2013 at 09:27:37AM -0400, Baho Utot wrote:
>>>> On 08/24/2013 10:14 PM, Ken Moffat wrote:
>>>>>  Does anyone else see eject failing to eject a CD/DVD with 7.3 or
>>>>> later ?  Eject is now part of util-linux so you don't need to
>>>>> install anything extra to test this, just put a CD or DVD in
>>>>> /dev/sr0.
>>>> on the latest SVN if a cd/dvd is in the drive eject works.
>>>> If no cd/dvd is in the drive eject does nothing.
>>> Odd.  As Bruce noted, it ought to let you open the drawer to load a
>>> CD.  My problem turns out to be different, and I'm not sure about
>>> the OP's problem with eject.
>>>
>>> ĸen
>> I have found that when there is not a cd/dvd in the drive there is no
>> symlink /dev/cdrom so maybe eject then finds nothing to eject?
>> After a cd/dvd/ is placed into the drive /dev/cdrom  is there and eject
>> works.
> What version of udev are you using?  There is nothing that I know of
> that should remove the /dev/cdrom symlink.  The symlink should be
> created when the system boots.  Is this perhaps a usb cdrom?
>
> Do you have /dev/sr0?
>
> -- Bruce

udev 204

This is on a Dell lapdog tye cd/dvd/ is internal

Yes /dev/sr0 is there

I should have a new system built with 206 sometime today as it is still 
building

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] systemd-udev

[Baho Utot]

On 08/25/2013 12:17 PM, Bruce Dubbs wrote:
> Baho Utot wrote:
>> On 08/25/2013 11:36 AM, Bruce Dubbs wrote:
>>>> I have found that when there is not a cd/dvd in the drive there is no
>>>> symlink /dev/cdrom so maybe eject then finds nothing to eject?
>>>> After a cd/dvd/ is placed into the drive /dev/cdrom  is there and eject
>>>> works.
>>> What version of udev are you using?  There is nothing that I know of
>>> that should remove the /dev/cdrom symlink.  The symlink should be
>>> created when the system boots.  Is this perhaps a usb cdrom?
>>>
>>> Do you have /dev/sr0?
>> udev 204
>>
>> This is on a Dell lapdog tye cd/dvd/ is internal
>>
>> Yes /dev/sr0 is there
>>
>> I should have a new system built with 206 sometime today as it is still
>> building
> I really don't think there should be a difference for cdroms between
> udev 204 and 206.  Try 'dmesg|grep -i cdrom'  That should indicate
> whether the kernel found the device.  When udev is started in the boot
> scripts,  it should create a symlik from

[ 1.471298] cdrom: Uniform CD-ROM driver Revision: 3.20

find / -name 60-cdrom_id.rules

/lib/udev/rules.d/60-cdrom_id.rules


>
> 60-cdrom_id.rules:
>
> KERNEL=="sr0", SYMLINK+="cdrom", OPTIONS+="link_priority=-100"

Yes it is there

>
> Note that in /etc/udev/rules.d there are a couple of cdrom related
> rules.  It should generate /etc/udev/rules.d/70-persistent-cd.rules.
>
> You might want to try to trace through that.
>
> -- Bruce
>

I have
/etc/udev/rules.d/70-persistent-net.rules
/etc/udev/rules.d/81-cdrom.rules
/etc/udev/rules.d/83-cdrom-symlinks.rules

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] systemd-udev

[Baho Utot]

On 08/25/2013 01:13 PM, Bruce Dubbs wrote:
> Baho Utot wrote:
>> On 08/25/2013 12:17 PM, Bruce Dubbs wrote:
>>> Baho Utot wrote:
>>>> On 08/25/2013 11:36 AM, Bruce Dubbs wrote:
>>>>>> I have found that when there is not a cd/dvd in the drive there is no
>>>>>> symlink /dev/cdrom so maybe eject then finds nothing to eject?
>>>>>> After a cd/dvd/ is placed into the drive /dev/cdrom  is there and eject
>>>>>> works.
>>>>> What version of udev are you using?  There is nothing that I know of
>>>>> that should remove the /dev/cdrom symlink.  The symlink should be
>>>>> created when the system boots.  Is this perhaps a usb cdrom?
>>>>>
>>>>> Do you have /dev/sr0?
>>>> udev 204
>>>>
>>>> This is on a Dell lapdog tye cd/dvd/ is internal
>>>>
>>>> Yes /dev/sr0 is there
>>>>
>>>> I should have a new system built with 206 sometime today as it is still
>>>> building
>>> I really don't think there should be a difference for cdroms between
>>> udev 204 and 206.  Try 'dmesg|grep -i cdrom'  That should indicate
>>> whether the kernel found the device.  When udev is started in the boot
>>> scripts,  it should create a symlik from
>> [ 1.471298] cdrom: Uniform CD-ROM driver Revision: 3.20
>>
>> find / -name 60-cdrom_id.rules
>>
>> /lib/udev/rules.d/60-cdrom_id.rules
>>
>>
>>> 60-cdrom_id.rules:
>>>
>>> KERNEL=="sr0", SYMLINK+="cdrom", OPTIONS+="link_priority=-100"
>> Yes it is there
>>
>>> Note that in /etc/udev/rules.d there are a couple of cdrom related
>>> rules.  It should generate /etc/udev/rules.d/70-persistent-cd.rules.
>>>
>>> You might want to try to trace through that.
>>>
>>>   -- Bruce
>>>
>> I have
>> /etc/udev/rules.d/70-persistent-net.rules
>> /etc/udev/rules.d/81-cdrom.rules
>> /etc/udev/rules.d/83-cdrom-symlinks.rules
> One thing you might try is this.  Change the bootscripts to not run
> udevd (or the retry).  The system should come up fine, but some symlinks
> or permissions may be missing/wrong.
>
> The run from the command line as root:
>
> /lib/udev/udevd --debug |tee /run/udev-debug.log
>
> You should be able to get some info about how udev perceives the cdrom.
>
> -- Bruce
>
Ok I will try that later after the current build finishes

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] systemd-udev

[Baho Utot]

On 08/25/2013 01:17 PM, Baho Utot wrote:
> On 08/25/2013 01:13 PM, Bruce Dubbs wrote:
>> Baho Utot wrote:
>>> On 08/25/2013 12:17 PM, Bruce Dubbs wrote:
>>>> Baho Utot wrote:
>>>>> On 08/25/2013 11:36 AM, Bruce Dubbs wrote:
>>>>>>> I have found that when there is not a cd/dvd in the drive there is no
>>>>>>> symlink /dev/cdrom so maybe eject then finds nothing to eject?
>>>>>>> After a cd/dvd/ is placed into the drive /dev/cdrom  is there and eject
>>>>>>> works.
>>>>>> What version of udev are you using?  There is nothing that I know of
>>>>>> that should remove the /dev/cdrom symlink.  The symlink should be
>>>>>> created when the system boots.  Is this perhaps a usb cdrom?
>>>>>>
>>>>>> Do you have /dev/sr0?
>>>>> udev 204
>>>>>
>>>>> This is on a Dell lapdog tye cd/dvd/ is internal
>>>>>
>>>>> Yes /dev/sr0 is there
>>>>>
>>>>> I should have a new system built with 206 sometime today as it is still
>>>>> building
>>>> I really don't think there should be a difference for cdroms between
>>>> udev 204 and 206.  Try 'dmesg|grep -i cdrom'  That should indicate
>>>> whether the kernel found the device.  When udev is started in the boot
>>>> scripts,  it should create a symlik from
>>> [ 1.471298] cdrom: Uniform CD-ROM driver Revision: 3.20
>>>
>>> find / -name 60-cdrom_id.rules
>>>
>>> /lib/udev/rules.d/60-cdrom_id.rules
>>>
>>>
>>>> 60-cdrom_id.rules:
>>>>
>>>> KERNEL=="sr0", SYMLINK+="cdrom", OPTIONS+="link_priority=-100"
>>> Yes it is there
>>>
>>>> Note that in /etc/udev/rules.d there are a couple of cdrom related
>>>> rules.  It should generate /etc/udev/rules.d/70-persistent-cd.rules.
>>>>
>>>> You might want to try to trace through that.
>>>>
>>>>-- Bruce
>>>>
>>> I have
>>> /etc/udev/rules.d/70-persistent-net.rules
>>> /etc/udev/rules.d/81-cdrom.rules
>>> /etc/udev/rules.d/83-cdrom-symlinks.rules
>> One thing you might try is this.  Change the bootscripts to not run
>> udevd (or the retry).  The system should come up fine, but some symlinks
>> or permissions may be missing/wrong.
>>
>> The run from the command line as root:
>>
>> /lib/udev/udevd --debug |tee /run/udev-debug.log
>>
>> You should be able to get some info about how udev perceives the cdrom.
>>
>>  -- Bruce
>>
> Ok I will try that later after the current build finishes
>
I have finished my build and I have checked it and found eject works 
like it is supposed to.

The previous build was SVN-20130624 and the current build is SVN-20130822

The only things different are a few packages glibc, udev, boot scripts 
and kernel etc.

The build was scripted and only packages differences between the two 
version was changed.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

[lfs-support] udev-206

[Baho Utot]

Can someone check the perms on /lib/udev/init-net-rules.sh
On my build it is not install with execute perms.
  This could be my fault I want to check to see if others have this.

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] udev-206

[Baho Utot]

On 08/30/2013 10:02 AM, hans kaper wrote:
> Op Fri, 30 Aug 2013 13:30:17 +0200 schreef Baho Utot 
> :
>
>> Can someone check the perms on /lib/udev/init-net-rules.sh
>> On my build it is not install with execute perms.
>>This could be my fault I want to check to see if others have this.
>>
>
> The same with me. The permissions are 644.
>
>
>
> Hans
Thanks
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

[lfs-support] tar patch

[Baho Utot]

I have just built the book after updating from svn and it doesn't have 
the tar man page patch in the wget-list nor in the md5sums files.

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] tar patch

[Baho Utot]

On 09/01/2013 09:57 AM, Bruce Dubbs wrote:
> Bruce Dubbs wrote:
>> Baho Utot wrote:
>>> I have just built the book after updating from svn and it doesn't have
>>> the tar man page patch in the wget-list nor in the md5sums files.
>> OK, thanks.  I'll investigate.
> Needed a minor change to the Makefile.  Please update and retry.  You
> should only need:
>
> make wget-list md5sums
>
> -- Bruce
>
It's OK now
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] Step 5.4.1 Installation of Cross Binutils errors

[Baho Utot]

On 11/12/2013 07:33 PM, Ken Moffat wrote:
> On Tue, Nov 12, 2013 at 11:31:56PM +, Vasco Almeida wrote:
>> "
>>
>> Where do I go from here?
>>
>>
>   Find the part of the output with the actual 'Error' message (it might
> say 'error').  It looks as if the real error was before that warning
> about makeinfo.  I haven't seen the post where 'make -k' was
> recommended (I expect it is taking a slow route to reach me), but in
> general you do NOT want to do that in LFS, except when running test
> suites.
>
>   Since you have barely started, please also check the Host System
> Requirements in section Vii of the Preface.
>
>   Actually, check the Host System Requirements _first_, then (if
> your host meets _all_ of them : newer versions *probably* work for
> binutils and gcc), repeat your attempt to compile this, after
> removing the existing binutils-2.32.2 (I'm assuming you are trying
> to build LFS-7.4) and binutils-build directories.
>
>   But this time, capture the output in a log, for example
>
> ../path/to/binutils-source/./configure ... | tee myconflog 2>&1
>
>   and then
>
> make | tee mybuildlog 2>&1
>
>   so that the error messages on stderr ('2') get mixed in.  Then look
> at the build log in 'view|vim' or 'less' and search for Error [
> '/Error' ].
>
> ĸen

If you are using bash 4.0 or greater

../path/to/binutils-source/./configure ... | tee myconflog 2>&1

becomes

../path/to/binutils-source/./configure ... |& tee myconflog

and

make | tee mybuildlog 2>&1

becomes

make |& tee mybuildlog 2>&1

 From the bash manual

3.2.2 Pipelines

A pipeline is a sequence of simple commands separated by one of the control 
operators ‘|’ or ‘|&’.

The format for a pipeline is

[time [-p]] [!] command1 [ [| or |&] command2 …]
The output of each command in the pipeline is connected via a pipe to the input 
of the next command. That is, each command reads the previous command’s output. 
This connection is performed before any redirections specified by the command.

If ‘|&’ is used, the standard error of command1 is connected to command2’s 
standard input through the pipe; it is shorthand for 2>&1 |. This implicit 
redirection of the standard error is performed after any redirections specified 
by the command.

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] Step 5.4.1 Installation of Cross Binutils errors

[Baho Utot]

On 11/13/2013 03:41 AM, Pierre Labastie wrote:
> Le 13/11/2013 02:53, Ken Moffat a écrit :
>> On Tue, Nov 12, 2013 at 07:57:30PM -0500, Baho Utot wrote:
>>> If you are using bash 4.0 or greater
>>>
>>> ../path/to/binutils-source/./configure ... | tee myconflog 2>&1
>>>
>>> becomes
>>>
>>> ../path/to/binutils-source/./configure ... |& tee myconflog
>>>
>>I would change 'becomes' to 'can be changed to' - there is no
>> *requirement* to change a following '2>&1' to a preceding '&'.
>>
>>
> but 2>&1 should be before the `|' anyway : it does not work the same as `>'.
>
> If you type the command as above, it sends the "tee" errors to stdout,
> not the "configure" errors...
>
> Regards
> Pierre
>
configure |& tee myconf.log - sends both stdout and stderr to the log

cat myconf.log
Checking for gcc...
Checking for shared library support...
Building shared library libz.so.1.2.8 with gcc.
Checking for off64_t... Yes.
Checking for fseeko... Yes.
Checking for strerror... Yes.
Checking for unistd.h... Yes.
Checking for stdarg.h... Yes.
Checking whether to use vs[n]printf() or s[n]printf()... using 
vs[n]printf().
Checking for vsnprintf() in stdio.h... Yes.
Checking for return value of vsnprintf()... Yes.
Checking for attribute(visibility) support... Yes.


./configure --pretix |& tee myconf.log
cat myconf.log
unknown option: --pretix
./configure --help for help
** ./configure aborting.

That is why I use |& as I don't need to make sure the 2>&1 is in the 
right place...It just works


-- 
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: invalid file name When Booting For the First Time

[Baho Utot]

On 11/23/2013 03:21 PM, Dan McGhee wrote:

  One of
the conclusions that I have drawn is that GRUB2 in it's current state
will not boot a kernel compiled and installed via LFS.


Nonsense grub2 will boot kernels compiled and install from LFS. I do it 
all the time.
Although I am not using UEFI.
I have ONE boot partition and I have Fedora 19, FreeBSD 9.2, LFS built 
by the book and LFS built with rpm package manager.
I also have LFS-7.2 that boots from usb drive used to correct "oh sh*t" 
problems

> Fedora,
> OpenSuse, Ubuntu and one other, seriously hack grub for their own purposes.
>
> The only way I have found to use my UEFI firmware outside of a distro is
> to use the efi stubs of the kernel.  If this is what you're trying to
> do, please respond to the list and I will post a "quick and dirty"
> howto.  I'm in the process of writing a more complete version for the
> list, but it's not ready to post.
>
> Dan
>

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] Ethernet Card Not Found

[Baho Utot]

On 11/25/2013 07:44 PM, Alan Feuerbacher wrote:

[putolin]

> ONBOOT=yes
> IFACE=p4p1
> SERVICE=ipv4-static
> IP=10.0.1.31
> GATEWAY=10.0.1.1
> PREFIX=24
> BROADCAST=192.168.0.255
>
> the problem, perhaps, would be solved.
> That helped, thank you. What finally solved the problem, though, was
> William's suggestion to look at /sys/class/net, which now contains the
> directory enp3s0. Perhaps this got created after I recompiled the kernel
> with the driver for my Realtek network device. I looked at the linux
> .config file and it now has the line "CONFIG_R8169=y" which is correct.
>
> The file that worked:
>
> ifconfig.enp3s0
> ###
> ONBOOT=yes
> IFACE=enp3s0
> SERVICE=ipv4-static
> IP=10.0.1.31
> GATEWAY=10.0.1.1
> PREFIX=24
> BROADCAST=192.168.0.255
> ###
> How does one figure out what the "BROADCAST" address is supposed to be?
> I still have no clue whether the one above is right.
The broadcast address is wrong

You need to think binary as in base 2
It should be  10.0.1.255 as your prefix is 24.
So viewing your ip address octets (base 8) left most bit of your ip is 
the "network address/lan address"  ( 10.0.1 )
The broadcast address is "all ones" or 255. So that makes the broadcast 
address network address plus all ones or
10.0.1.255

>
> I borrowed that file straight from the Fedora installation. It has:
>
> resolv.conf
> ##
> domain hsd1.nh.comcast.net.
> search hsd1.nh.comcast.net.
> nameserver 10.0.1.1

This is incorrect your resolv.conf
should have only the domain line or search line but not both.

The domain line is your domain name in this case hsd1.nh.comcast.net

The nameserver should be the address for the DNS server that provides 
name resolving for your lan, which in this case is your router 10.0.1.1.

/etc/host file

127.0.0.1localhost
127.0.0.2localhost.localdomain
10.0.1.31.hsd1.nh.comcast.net

change  to the name you gave your computer.



-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] Ethernet Card Not Found

[Baho Utot]

On 11/26/2013 03:09 AM, Simon Geard wrote:
> On Mon, 2013-11-25 at 20:12 -0500, Alan Feuerbacher wrote:
>> On 11/25/2013 11:04 AM, William Harrington wrote:
>>> Your link name is p4p1.
>> How does this name, given by Fedora, relate to the "enp3s0" that my
>> kernel assigned (see my earlier reply to Fernando).
> Looks like Fedora uses a different naming convention... they've dropped
> the "en" prefix, and appear to be counting slots from one instead of
> zero (hence 4:1 instead of 3:0).
>
> If "enp3s0" is what you see in the /sys/class/net after booting LFS,
> that's what you should be using.
>
> Simon.
>

ls /sys/class/net

lo  p33p1  wlp4s0

Want to bet which one of these I can remember?

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] Ethernet Card Not Found

[Baho Utot]

On 11/26/2013 09:23 PM, William Harrington wrote:
> On Nov 26, 2013, at 6:19 PM, Baho Utot wrote:
>
>> Want to bet which one of these I can remember?
> p33p1  for people!
Nope too many characters
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

[lfs-support] LFS-7.4

[Baho Utot]

Is it possible to build LFS-7.4 on x86_64 without the /lib64 symlink?

I have tried to do so but libstd++ in the chapter 5 tool chain dies.

I would like to build for x86_64 and have the same filesystem layout 
that i686 has ie without the lib64 directories


-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] LFS-7.4

[Baho Utot]

On 11/29/2013 07:23 PM, Ken Moffat wrote:
> On Fri, Nov 29, 2013 at 11:35:19AM -0600, Bruce Dubbs wrote:
>> Baho Utot wrote:
>>> Is it possible to build LFS-7.4 on x86_64 without the /lib64 symlink?
>>>
>>> I have tried to do so but libstd++ in the chapter 5 tool chain dies.
>>>
>>> I would like to build for x86_64 and have the same filesystem layout
>>> that i686 has ie without the lib64 directories
>> I really don't know but I can make some guesses.  uname --machine gives
>> x86_64.  I wouldn't be suprised if some packages that assume a multilib
>> system use that value to insist on /lib64  or /usr/lib64.
>>
>> -- Bruce
>   Cross-LFS has always done that for pure64.  It's a _long_ while
> since I last built clfs x86_64-64 and many things have changed, but
> the main difference is that clfs still uses a specfile - their build
> is now quite different from how LFS has evolved.
>
>   If you do something like that, then yes, a few _blfs_ packages will
> probably get confused by the absence of /lib64.  OTOH, you would get
> a nice clean system - but the build for x86_64 will be somewhat
> different from what is currently in LFS.
>
>   I've a feeling that someone, perhaps our late colleague Andy, used
> to build 64-bit LFS without the symlink - but I've no idea of the
> details about how to do it (and that was before libstdc++ and g++
> became required for building gcc, so the details would have to change
> for gcc-4.8).
>
>   This message will self-destruct in 5 seconds.
>
> ĸen

The following packages are the only ones I have found ( in Chapter 5 ) 
that either puts something into or requires /lib64

binutils-pass-1
gcc-pass-1
libstdc++
binutils-pass-2
gcc-pass-2

I have not gotten to chapter 6

I have just downloaded clfs and I am building the books now.  Once that 
completes I will have a look at that to see how the x86_64 pure 64 bit 
system is built.  It looks like ( I could be wrong ) the /lib64 and 
/usr/lib64 are not used there.



-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] LFS-7.4

[Baho Utot]

On 12/02/2013 12:10 PM, William Harrington wrote:
> On Nov 29, 2013, at 11:06 AM, Baho Utot wrote:
>
>> Is it possible to build LFS-7.4 on x86_64 without the /lib64 symlink?
>>
>> I have tried to do so but libstd++ in the chapter 5 tool chain dies.
>>
>> I would like to build for x86_64 and have the same filesystem layout
>> that i686 has ie without the lib64 directories
> Don't use --disable-multilib and remove the lib64 link, lib and lib64
> will be automatically created.
>
> The linker will search in the default paths:
>
> for x86_64-unknown-linux-gnu:
>
> SEARCH_DIR("/usr/x86_64-unknown-linux-gnu/lib64"); SEARCH_DIR("/usr/
> local/lib64"); SEARCH_DIR("/lib64"); SEARCH_DIR("/usr/lib64");
> SEARCH_DIR("/usr/x86_64-unknown-linux-gnu/lib"); SEARCH_DIR("/usr/
> local/lib"); SEARCH_DIR("/lib"); SEARCH_DIR("/usr/lib");
>
> SEARCH_DIR("/usr/x86_64-unknown-linux-gnu/libx32"); SEARCH_DIR("/usr/
> local/libx32"); SEARCH_DIR("/libx32"); SEARCH_DIR("/usr/libx32");
> SEARCH_DIR("/usr/x86_64-unknown-linux-gnu/lib"); SEARCH_DIR("/usr/
> local/lib"); SEARCH_DIR("/lib"); SEARCH_DIR("/usr/lib");
>
> for i386-unknown-linux-gnu (or i486 or i586 or i686):
>
> SEARCH_DIR("/usr/i386-unknown-linux-gnu/lib"); SEARCH_DIR("/usr/local/
> lib"); SEARCH_DIR("/lib"); SEARCH_DIR("/usr/lib");
> SEARCH_DIR("/usr/x86_64-unknown-linux-gnu/lib"); SEARCH_DIR("/usr/
> local/lib"); SEARCH_DIR("/lib"); SEARCH_DIR("/usr/lib");
>
> Since the compiler will default to 64bit with -m64, it'll build 64bit
> binaries. Some packages default with libdir to /lib or /usr/lib. Those
> you'll need to set --libdir or with glibc set slibdir in configparams.
>
> If you want a pure64 bit system with only lib, you need to disable
> multilib, adjust the gcc specs to search only in /lib and /usr/lib
> and /usr/local/lib or any other lib rather than lib64 for x86_64
> targets.  You can also set the default search path for binutils so it
> only searches in /lib:/usr/lib:/usr/local/lib rather than x32, too.
>
> You will need to read and experiment quite a bit to do this on your own.
>
> SIncerely,
>
> WIlliam Harrington

Thanks

You have given me some place to get started.

I figured it would be some what hunt and peck.

Now I have one more way to screw up my system ;)

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] LFS-7.4

[Baho Utot]

On 12/03/2013 02:17 AM, Simon Geard wrote:

On Sat, 2013-11-30 at 23:47 +1300, Simon Geard wrote:

On Fri, 2013-11-29 at 19:49 -0500, Baho Utot wrote:

The following packages are the only ones I have found ( in Chapter 5 )
that either puts something into or requires /lib64

binutils-pass-1
gcc-pass-1
libstdc++
binutils-pass-2
gcc-pass-2

By /lib64, you mean /tool/lib64, given we're talking Chapter 5? I think
it's impossible to avoid having some stuff written to that directory in
Chapter 5, because to start with, you're relying on the versions of
gcc/glibc provided by the host.

The trick is to modify those two packages when you build them in
chapters 5 and 6, to ensure they use the directory names you prefer.
Everything else should follow from them, barring a few exceptional cases
from BLFS...

I've just dug out the patches I used last time I did this... they're not
current versions, but should at least give you an idea. According to my
notes, the GCC one was applied to all three builds, but the GLIBC one
was used only in Chapter 6.

Simon.





Thanks I will see what I can do with these

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

[lfs-support] LFS-7.5 rc1

[baho utot]

As I am working on my build scripts for building LFS and adding the RPM 
package manager.
I need to check my work against some one elses builds to be sure that I 
haven't created a catastrophe for myself.

Are log files avaliable from chapter5 and chapter 6 builds?

If so can some one point me to the files.

Thanks
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

[lfs-support] /run directory: Maybe a bit off topic?

[baho utot]

I am working on RPM-LFS-7.5 which is LFS with the rpm package manager.

I would like to adhere to Filesystem Hierarchy Standard 2.3 so my linux 
systems file system layout matches/closely matches my FreeBSD systems.  
When was the /run directory introduced and what package(s) required 
moving run-time data from /var/run to /run?

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] /run directory: Maybe a bit off topic?

[baho utot]

On 03/22/2014 10:08 AM, Armin K. wrote:
> On 03/22/2014 02:59 PM, baho utot wrote:
>> I am working on RPM-LFS-7.5 which is LFS with the rpm package manager.
>>
>> I would like to adhere to Filesystem Hierarchy Standard 2.3 so my linux
>> systems file system layout matches/closely matches my FreeBSD systems.
>> When was the /run directory introduced and what package(s) required
>> moving run-time data from /var/run to /run?
>>
> It was introduced and first used by udev way before systemd merge.
>
OK thanks
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] /run directory: Maybe a bit off topic?

[baho utot]

On 03/23/2014 04:36 AM, Simon Geard wrote:
> On Sat, 2014-03-22 at 09:59 -0400, baho utot wrote:
>> I am working on RPM-LFS-7.5 which is LFS with the rpm package manager.
>>
>> I would like to adhere to Filesystem Hierarchy Standard 2.3 so my linux
>> systems file system layout matches/closely matches my FreeBSD systems.
>> When was the /run directory introduced and what package(s) required
>> moving run-time data from /var/run to /run?
>>
> Just be aware that the FHS was last updated in January 2004 - a little
> more than a decade ago - and as such is a bit out of date with regard to
> how Linux distros are doing things.
>
> In particular, it's unaware of both the /sys virtual filesystem (added
> around 2006 as I recall), and the introduction of /run (in 2011 or so).
> So while it's a useful guideline, I'd suggest not getting too hung up on
> compliance...
>
> Simon.
>

Just trying to match what I have on my unix boxes.  Even if it hasn't 
been updated doesn't mean it's not relavent.
I understand adding /sys but /run makes no sense as it could have been 
/var/run which by the way IS in the standard.


-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] /run directory: Maybe a bit off topic?

[baho utot]

On 03/23/2014 07:32 AM, Robin wrote:
> On 23 March 2014 11:22, baho utot  wrote:
>> On 03/23/2014 04:36 AM, Simon Geard wrote:
>>> On Sat, 2014-03-22 at 09:59 -0400, baho utot wrote:
>>>> I am working on RPM-LFS-7.5 which is LFS with the rpm package manager.
>>>>
>>>> I would like to adhere to Filesystem Hierarchy Standard 2.3 so my linux
>>>> systems file system layout matches/closely matches my FreeBSD systems.
>>>> When was the /run directory introduced and what package(s) required
>>>> moving run-time data from /var/run to /run?
>>>>
>>> Just be aware that the FHS was last updated in January 2004 - a little
>>> more than a decade ago - and as such is a bit out of date with regard to
>>> how Linux distros are doing things.
>>>
>>> In particular, it's unaware of both the /sys virtual filesystem (added
>>> around 2006 as I recall), and the introduction of /run (in 2011 or so).
>>> So while it's a useful guideline, I'd suggest not getting too hung up on
>>> compliance...
>>>
>>> Simon.
>>>
>> Just trying to match what I have on my unix boxes.  Even if it hasn't
>> been updated doesn't mean it's not relavent.
>> I understand adding /sys but /run makes no sense as it could have been
>> /var/run which by the way IS in the standard.
>>
>>
> Found this: http://lwn.net/Articles/436012/
>

Interesting post but /run only applies to linux as BSD doesn't use /run
I'll mark this up to another"linux only wart."

Thanks

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] /run directory: Maybe a bit off topic?

[baho utot]

On 03/23/2014 11:58 AM, Bruce Dubbs wrote:
> baho utot wrote:
>
>> Just trying to match what I have on my unix boxes.  Even if it hasn't
>> been updated doesn't mean it's not relavent.
>> I understand adding /sys but /run makes no sense as it could have been
>> /var/run which by the way IS in the standard.
> /var doesn't work if it is mounted partition.
>
> -- Bruce
>
>
>
>

I think there are not many folks that have that on a separate partition.

That's really the only problem with using /var/run.

If I had to count using my fingers how many systems I have worked on 
that have /var mounted on a separate partition I could count them even 
if I had no fingers.

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

[lfs-support] linuxfromscratch.org web site

[baho utot]

I am in the process of collecting information on usinf eudev in my rpm 
lfs builds I have found a broken link on the 
http://www.linuxfromscratch.org/hints/download.html page.
When clicking the link for Hints Tarball (Generated daily) I get

Page not found!

Perhaps you mistyped the URL?

In the case of a broken link, please contact the webmaster.

BTW Is there info on using eudev in LFS as I don't want to go down the 
init|systemd toggle path?



-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

[lfs-support] LFS-7.5 Chapter 6.61. Util-linux-2.24.1

[baho utot]

the  configure should be:

./configure --disable-nologin

as nologin was previously installed by shadow


-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] LFS-7.5 Chapter 6.61. Util-linux-2.24.1

[baho utot]

On 04/06/2014 08:33 PM, William Harrington wrote:
> On Apr 6, 2014, at 7:20 PM, baho utot wrote:
>
>> the  configure should be:
>>
>> ./configure --disable-nologin
>>
>> as nologin was previously installed by shadow
>
> Does util-linux nologin binary overwrite shadow's? If so, that is
> desired because util-linux ships a better nologin binary.

I am using rpm package manager.  It causes a conflict when a file is 
already installed by another package.
You then have to remove one of them from one of the packages.

>
> Coreutils will also overwrite groups program because it is better than
> shadow's groups binary.

There isn't a "groups" executeable installed by shadow.
I could list the files installed by shadow and coreutils here if needed


>
>
> Rather, shadow, if not wanting to install groups or nologin installed,
> could edit Makefile.in to exclude those.

On my builds I just rm the duplicate file from one of the packages 
before it is packaged up by rpm so I don't have to edit any of the 
Makefiles.

For the book the later package will over write the earlier package, and 
you will not know the over write has occurred.

>
> Sincerely,
>
> WIlliam Harrington

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] LFS-7.5 Chapter 6.61. Util-linux-2.24.1

[baho utot]

On 04/06/2014 09:09 PM, Bruce Dubbs wrote:
> baho utot wrote:
>> On 04/06/2014 08:33 PM, William Harrington wrote:
>>> On Apr 6, 2014, at 7:20 PM, baho utot wrote:
>>>
>>>> the  configure should be:
>>>>
>>>> ./configure --disable-nologin
>>>>
>>>> as nologin was previously installed by shadow
>>> Does util-linux nologin binary overwrite shadow's? If so, that is
>>> desired because util-linux ships a better nologin binary.
>> I am using rpm package manager.  It causes a conflict when a file is
>> already installed by another package.
>> You then have to remove one of them from one of the packages.
>>
>>> Coreutils will also overwrite groups program because it is better than
>>> shadow's groups binary.
>> There isn't a "groups" executeable installed by shadow.
> Yes, we do disable that.

Then why not disable nologin in shadow as well?
Why over write only one of them?

>
>>> Rather, shadow, if not wanting to install groups or nologin installed,
>>> could edit Makefile.in to exclude those.
>> On my builds I just rm the duplicate file from one of the packages
>> before it is packaged up by rpm so I don't have to edit any of the
>> Makefiles.
>>
>> For the book the later package will over write the earlier package, and
>> you will not know the over write has occurred.
> That seems like the correct behavior to me.
>
> -- Bruce

but not consistent as above


-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] LFS-7.5 Chapter 6.61. Util-linux-2.24.1

[baho utot]

On 04/07/2014 08:03 AM, Bruce Dubbs wrote:

baho utot wrote:

On 04/06/2014 09:09 PM, Bruce Dubbs wrote:

baho utot wrote:

On 04/06/2014 08:33 PM, William Harrington wrote:

On Apr 6, 2014, at 7:20 PM, baho utot wrote:


the  configure should be:

./configure --disable-nologin

as nologin was previously installed by shadow

Does util-linux nologin binary overwrite shadow's? If so, that is
desired because util-linux ships a better nologin binary.

I am using rpm package manager.  It causes a conflict when a file is
already installed by another package.
You then have to remove one of them from one of the packages.


Coreutils will also overwrite groups program because it is better than
shadow's groups binary.

There isn't a "groups" executeable installed by shadow.

Yes, we do disable that.

Then why not disable nologin in shadow as well?
Why over write only one of them?


Rather, shadow, if not wanting to install groups or nologin installed,
could edit Makefile.in to exclude those.

On my builds I just rm the duplicate file from one of the packages
before it is packaged up by rpm so I don't have to edit any of the
Makefiles.

For the book the later package will over write the earlier package, and
you will not know the over write has occurred.

That seems like the correct behavior to me.

but not consistent as above

Do you want to submit a patch?

-- Bruce




Attached is the patch

--- LFS-BOOK-7.5-NOCHUNKS.html.original	2014-04-07 17:48:50.0 -0400
+++ LFS-BOOK-7.5-NOCHUNKS.html	2014-04-07 17:57:29.986548068 -0400
@@ -17341,6 +17341,13 @@
   
 mv -v /usr/bin/passwd /bin
 
+  
+remove nologin as a better version is installed by util-linux:
+  
+  
+rm -v /sbin/nologin
+
+
 
 
   
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] LFS-7.5 Chapter 6.61. Util-linux-2.24.1

[baho utot]

On 04/07/2014 06:53 PM, Bruce Dubbs wrote:
> William Immendorf wrote:
>> On Mon, Apr 7, 2014 at 5:24 PM, Bruce Dubbs  wrote:
>>> LOL.  That's html.  The book is in xml docbook.
>>>
>>> I'll see what I can do.
>> I've looked at the patch briefly. I'm pretty sure that using rm to
>> remove an executable is a bad idea in a system that might not always
>> have package management. I'd also note that shadow will likely install
>> man pages for the executable, and the patch does not have any
>> instructions to handle that.
>>
>> Bruce, my suggestion would be to add a new sed based off the one for
>> disabling the groups executable. I'd imagine that something like this
>> would do the trick:
>>
>> sed -i 's/nologin$(EXEEXT) //' src/Makefile.in
>> find man -name Makefile.in -exec sed -i 's/nologin\.8 / /' {} \;
> Yes, I was going to do that.  Thanks for the instructions tho.  Saves me
> some time.
>
> -- Bruce
>

This works

sed -i 's/nologin$(EXEEXT)/ /' src/Makefile.in
find man -name Makefile.in -exec sed -i 's/nologin\.8 / /' {} \;


-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

lfs on mdraid

[Baho Utot]

Does LFS support mdraid?

I have an mdraid setup and I would like to run lfs from there,  does LFS
install and boot from a mdraid?

I also use jfs as a filesystem, I think I would only have to build the
jfs utilities.  Right/Wrong?

Thanks

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

5.6 linux-2.6.27.4 API Headers build error

[Baho Utot]

I am getting the following error

lfs:~/linux-2.6.27.4$ make headers_check
  CHK include/linux/version.h
  UPD include/linux/version.h
  HOSTCC  scripts/basic/fixdep
scripts/basic/fixdep.c: In function 'traps':
scripts/basic/fixdep.c:377: warning: dereferencing type-punned pointer
will break strict-aliasing rules
scripts/basic/fixdep.c:379: warning: dereferencing type-punned pointer
will break strict-aliasing rules
  HOSTCC  scripts/basic/docproc
  HOSTCC  scripts/unifdef
scripts/unifdef.c:209: error: conflicting types for 'getline'
/usr/include/stdio.h:651: note: previous declaration of 'getline' was
here
make[1]: *** [scripts/unifdef] Error 1
make: *** [__headers] Error 2

I have followed the book and I am building on an Arch linux i686 with
PAE kernel box with gcc-4.4.0  

The PATH is /tools/bin:/bin:/usr/bin

and I have set h+

lfs:~/linux-2.6.27.4$ gcc -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../gcc-4.3.2/configure --prefix=/tools
--with-local-prefix=/tools --disable-nls --disable-shared
--disable-libssp --enable-languages=c
Thread model: posix
gcc version 4.3.2 (GCC) 


Thankyou



-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: 5.6 linux-2.6.27.4 API Headers build error

[Baho Utot]

On Fri, 2009-07-24 at 07:36 -0500, William Immendorf wrote:
> On Fri, Jul 24, 2009 at 3:46 AM, Baho Utot wrote:
> > scripts/unifdef.c:209: error: conflicting types for 'getline'
> > /usr/include/stdio.h:651: note: previous declaration of 'getline' was
> Hmm... same issue as mentioned a month ago. Use the patch mentioned at
> http://linuxfromscratch.org/pipermail/lfs-support/2009-June/035912.html.
> 
> William

Thank you 

I will try the patch

I wonder if this is a Arch linux thing as I am using Arch also

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Make flags

[Baho Utot]

I have a AMD Athlon X4 810 with 8GB of ram

I am want to build an i686 system followed by  an x86_64 system

I would like to use these flags:
export CFLAGS="-march=i686 -mtune=generic -O2 -pipe"
export CXXFLAGS="-march=i686 -mtune=generic -O2 -pipe"
export MAKEFLAGS="-j3"

Is it possible to use -j3 in MAKEFLAGS ?
Coming from Arch Linux some of the package builds override the -j3 
flags, due to compile issues
Does any thing fail on LFS using that flag?

Any one see any show stoppers?

Thanks
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

LFS-6.5 Chapter 6.13 GMP-4.3.1

[Baho Utot]

Compiling GMP on an Athlon Phenom II X810
using an i686 liveCD

This is not what I wanted as I wanted to build an i686 system.
What is in the book makes it compile like this:

with march=k8 and mtune=k8

export ABI="32"
./configure --prefix=/usr --build=$CHOST --enable-cxx --enable-mpbsd

I am going to try compiling with the above (this is from arch linux 
PKGBUILD)
to see if it corrects the problem.

Is what I see in the compile correct?

If so the Book will give you a mixed system?

Thank you
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: Help

[Baho Utot]

Sam Vivacqua wrote:
> The problem is that when I type the comand  In -sv $LFS/tools /   I 
> get the output: -bash: In: comand not found
>
> On Sat, Sep 12, 2009 at 11:01 PM, Chris Staub  > wrote:
>
> On 09/12/2009 02:26 PM, Sam Vivacqua wrote:
> >
> > Hi,
> > For the comand   ln -sv $LFS/tools /in chapter 4.2,
> Creating the
> > $LFS/tools Directory, you said there are a few variations, but I
> > cannot figure out which one to use.  Can you tell me which
> will work
> > and the code that I will need to type?
> > Thanks!
> >
> >
>
> I'm not sure what you mean. The command given in the book should work
> fine. What's the problem?
> --
> http://linuxfromscratch.org/mailman/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/lfs/faq.html
> Unsubscribe: See the above information pa
>


That is because it is ln ( as in ell n) not In (as in eye n)


-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: lfs 6.4 live on usb flash

[Baho Utot]

Rodolfo Perez wrote:
> Hi
>
> I could install lfs-6.4 on my laptop and I'm really happy about my new
> lfs. 
> Now I would like to put it on my USB-Flash drive. I checked on lfs and
> was googeling but could not find a really satisfiying answer.
>
> I'd like to have a very small (max. 500Mb) lfs distro on my usb and it
> should be as lfs-live.
>
> Any help?
> Rodolfo
>
>   
I have just completed installing my LFS-6.5 (newly built) to a USB 
drive. What follows is how I was successful to make a bootable LFS USB 
drive..

I suggest you complete what Bruce suggests then:

Try this

1. prepare the USB drive by partitioning and formatting, I chose ext2 
file system.

2. mount the USB drive, example: /mnt/usb

3. copy LFS from the hard drive to the USB drive
use a live CD or another install of linux, do not try to
copy the LFS system if you are running it as /dev/ will
give you trouble

rsync -var  
or
cp  -var  

example:
rsync -var /mnt/lfs/* /mnt/usb
or
cp -var /mnt/lfs/* /mnt/usb

4. Install grub.

create menu.lst something like this and copy to /boot/grub/

# Config file for GRUB - The GNU GRand Unified Bootloader
# /boot/grub/menu.lst

timeout   5
default   0
color light-blue/black light-cyan/blue

title LFS 6.5 - USB
root (hd0,0)
kernel /boot/lfskernel-2.6.30.2 
root=/dev/disk/by-uuid/03e82132-a199-4601-a20e-106c444a2c5a ro quite
# EOF

The root (hd0,0) is correct, the USB drive will be hd0,0 at boot (you 
may have to change the last 0) if you copied LFS to a partition other 
than 1 (the first)

The kernel line should use the disk-by uuid...keeps one sane :)

to find the uuid
type at a CLI (terminal) blkid /dev/sdx - where sdx is the USB device
example from my "install":

blkid /dev/sdd1
/dev/sdd1: UUID="03e82132-a199-4601-a20e-106c444a2c5a" TYPE="ext2"

Now at a root CLI prompt 
grub
root (hdx,x)
setup (hdx)

The root line will vary according to the USB device is /dev/sdd1 is root 
(hd3,0), setup (hd3)
   
5.Fixup /etc/fstab

example:

# Begin /etc/fstab
# file system  mount-point  type   optionsdump  fsck
#
  order
/dev/disk/by-uuid/03e82132-a199-4601-a20e-106c444a2c5a / ext2 defaults 1 
1
#/dev/xxx swap swap  pri=1  0 0
proc   /procproc   defaults
0 0
sysfs  /sys sysfs  defaults
0 0
devpts /dev/pts devpts gid=4,mode=620 0 0
tmpfs  /dev/shm tmpfs  defaults
0 0
# End /etc/fstab

Again use disk/by-uuid with the uuid from the previous step
 

Reboot to the USB drive.


-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: Kernel panic - booting from USB harddisk

[Baho Utot]

Ken Moffat wrote:
> 2009/9/26 J.P.Kaper :
>   
>> Maybe somebody else can find the right suggestion to let me solve my
>> problem.
>>
>> Hans Kaper.
>> 
>
>  One of the problems with usb drives is that they can
> take a long time to appear.  I've never tried to boot
> from usb, but ISTR that there is a command-line argument
> to wait for the drive.
>
>  A quick look in the kernel's
> Documentation/kernel-parameters.txt (you can read
> it from the tarball in 'view' if you don't have the kernel
> source tree handy) suggests boot_delay= might be
> what I'm thinking of.
>
>  Perhaps try boot_delay=15 which should be a
> ridiculously long wait.  If it works like that, cut it
> down until you've reduced it too far, then back off
> a bit.
>
>  I expect you've already seen the following
> guides, but just in case:
>
> http://www.damnsmalllinux.org/wiki/index.php/USB_Booting
>  and
> http://wiki.debian.org/BootUsb
>
> ĸen
>   

I think you may be looking for rootdelay=

from Documentation/kernel-parameters.txt

rootdelay=[KNL] Delay (in seconds) to pause before attempting to
mount the root filesystem

Others to try:

boot_delay=Milliseconds to delay each printk during boot.
Values larger than 10 seconds (1) are changed to
no delay (0).
Format: integer

usb-storage.delay_use=
[UMS] The delay in seconds before a new device is
scanned for Logical Units (default 5).

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: Kernel panic - booting from USB harddisk

[Baho Utot]

J.P.Kaper wrote:
> I am building LFS from book 6.4 on an ext3 logical partition of an  
> external USB harddisk.
> My host system is SUSE 10.3 on one of my two internal harddisks.
>
> Booting from the USB disk fails with
> "[4.410067] Kernel panic - not syncing: VFS: Unable to mount
> root fs on unknown-block (2,0)"
>
>   
 From devices.txt

 2 blockFloppy disks
  0 = /dev/fd0Controller 0, drive 0, autodetect
  1 = /dev/fd1Controller 0, drive 1, autodetect
  2 = /dev/fd2Controller 0, drive 2, autodetect
  3 = /dev/fd3Controller 0, drive 3, autodetect
128 = /dev/fd4Controller 1, drive 0, autodetect
129 = /dev/fd5Controller 1, drive 1, autodetect
130 = /dev/fd6Controller 1, drive 2, autodetect
131 = /dev/fd7Controller 1, drive 3, autodetect


Some one correct me if I am wrong but
It looks to me that it is trying to boot/read/sync the floppy disk


-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: Kernel panic - booting from USB harddisk

[Baho Utot]

J.P.Kaper wrote:
> I am building LFS from book 6.4 on an ext3 logical partition of an  
> external USB harddisk.
> My host system is SUSE 10.3 on one of my two internal harddisks.
>
> Booting from the USB disk fails with
> "[4.410067] Kernel panic - not syncing: VFS: Unable to mount
> root fs on unknown-block (2,0)"
>
>   
I have done some more research on your problem.

Try this

in /etc/fstab for the USB disk

UUID=6342a6b5-25cf-4d01-a318-68309d12ab5b / ext3 defaults   1 1

change the blkid to the correct value based on
$ blkid /dev/sdxx


Are you trying to boot with grub on the USB drive?
If so try changing /boot/grub/menu.lst kernel line like this

kernel /boot/lfskernel-2.6.30.2 root=/dev/sdd1 rootdelay=15 ro quite

change the /dev/sdd1 to the correct value for your USB drive


If you have success then try to use UUID in the menu.lst file like this

kernel /boot/lfskernel-2.6.30.2 
root=UUID=6342a6b5-25cf-4d01-a318-68309d12ab5b rootdelay=15 ro quite



-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: Kernel panic - booting from USB harddisk

[Baho Utot]

Hans Kaper wrote:
> Op Thu, 01 Oct 2009 00:19:29 +0200 schreef Baho Utot  
> :
>
>   
>> J.P.Kaper wrote:
>> 
>>> I am building LFS from book 6.4 on an ext3 logical partition of an
>>> external USB harddisk.
>>> My host system is SUSE 10.3 on one of my two internal harddisks.
>>>
>>> Booting from the USB disk fails with
>>> "[4.410067] Kernel panic - not syncing: VFS: Unable to mount
>>> root fs on unknown-block (2,0)"
>>>
>>>
>>>   
>> I have done some more research on your problem.
>>
>> Try this
>>
>> in /etc/fstab for the USB disk
>>
>> UUID=6342a6b5-25cf-4d01-a318-68309d12ab5b / ext3 defaults   1 1
>>
>> change the blkid to the correct value based on
>> $ blkid /dev/sdxx
>>
>>
>> Are you trying to boot with grub on the USB drive?
>> If so try changing /boot/grub/menu.lst kernel line like this
>>
>> kernel /boot/lfskernel-2.6.30.2 root=/dev/sdd1 rootdelay=15 ro quite
>>
>> change the /dev/sdd1 to the correct value for your USB drive
>>
>>
>> If you have success then try to use UUID in the menu.lst file like this
>>
>> kernel /boot/lfskernel-2.6.30.2
>> root=UUID=6342a6b5-25cf-4d01-a318-68309d12ab5b rootdelay=15 ro quite
>>
>> 
>
> As I said in another post, I am able to boot now by way of a work-around.  
> But I am still interested to know why my former way did not work, so I  
> will try your suggestions (if the forum-moderator allows us to carry on  
> the thread).
>
>
> Hans Kaper.
>
>
>   

It looks like grub or the kernel can give the kernel panic about not 
syncing. 

I like to use UUID or LABEL  in grubs menu.lst file.

Grub can process UUID of LABELs and it makes sure that the drive/partition
that you are trying to boot doesn't change or get mixed up. ( It keeps 
me from getting mixed up
trying to keep "whos bootin from here to where ?"  straight )

But.

After you can successfully load/execute the kernel, and grubs done it's 
work
I think the kernel can not locate its root file system and barfs giving 
the kernel panic.

I have found that UUID or LABELs in /etc/fstab gives you the kernel 
panic because the kernel can not process UUID or LABELs
without using a initrd as udev has not been started.  So you need to use 
/dev/sdx there.

example:

title LFS 6.5 - USB
root (hd0,0)
kernel /boot/lfskernel-2.6.30.2 root=/dev/sdd1 rootdelay=15 ro quite

That makes the USB tied to that PC :(

If you need it to boot on another PC you need to edit the grub line from 
the menu when grubs starts up or use an initrd.

Hope this helps.

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: Uninformed Question re Kernel Configuration

[Baho Utot]

Dan McGhee wrote:
> I have a Turion Dual Core Processer.  I didn't not configure support for 
> multiprocessors when I did my new kernel and I load only one CPU.  Is a 
> dual core processor a "multiprocessor" system as far as the linux kernel 
> goes?  My friends accuse me of being "rhetoric sensitive." :)
>
> Thanks,
>
> Dan
>   
Yes, set SMP
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: build problem LFS 6.5

[Baho Utot]

stosss wrote:
> On Fri, Nov 27, 2009 at 9:24 AM, Chris Staub  wrote:
>   
>   
[putolin]

> 1st half of one of my scripts
>
>   
[putolin]

Here is my script that works

#!/tools/bin/bash -
CURRDIR=$(pwd)
SRC=/sources

tar xvf $SRC/vim-7.2.tar.bz2
cd vim72

patch -Np1 -i $SRC/vim-7.2-fixes-5.patch
echo '#define SYS_VIMRC_FILE "/etc/vimrc"' >> src/feature.h
./configure --prefix=/usr --enable-multibyte
make
make test | tee $CURRDIR/06.58.Check.log
make install | tee $CURRDIR/06.58.Install.log
ln -sv vim /usr/bin/vi
for L in  /usr/share/man/{,*/}man1/vim.1; do
ln -sv vim.1 $(dirname $L)/vi.1
done
ln -sv ../vim/vim72/doc /usr/share/doc/vim-7.2

cat > /etc/vimrc << "EOF"
" Begin /etc/vimrc

set nocompatible
set backspace=2
syntax on
if (&term == "iterm") || (&term == "putty")
  set background=dark
endif

" End /etc/vimrc
EOF

cd $CURRDIR
rm -rf vim72
echo "Completed"


Read it over and see if it helps

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: build problem LFS 6.5

[Baho Utot]

linux fan wrote:
> On 11/28/09, Baho Utot wrote:
>
>   
>> make test | tee $CURRDIR/06.58.Check.log
>> make install | tee $CURRDIR/06.58.Install.log
>> 
> Logging helps so much when things go wrong.
>
> As already mentioned
>
>   
>> Scripting an LFS build is *hard*
>> 
>
> [putolin]
> I only suggest this due to amount of time spent and it failing.
> You can debrief what jhalfs did with its scripts in
> lfs-commands/chapterXX/* and maybe detect what went wrong in handmade script.
>   
hmmm my scripts build LFS correctly every time. Spent zero time with 
them failing.
But then I am not the OP.

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

/usr/lib/libstdc++.so: could not read symbols: File in wrong format

[Baho Utot]

 From Book version 1.1.0-x86_64-multilib

Section 6.4 GCC-4.2.4

Slackware 12.2 as the build system.

I am getting this error on compiling

x86_64-unknown-linux-gnu-c++  -shared -nostdlib 
/tools/lib/../lib64/crti.o 
/cross-tools/lib/gcc/x86_64-unknown-linux-gnu/4.2.4/crtbeginS.o  
.libs/bitmap_allocator.o .libs/pool_allocator.o .libs/mt_allocator.o 
.libs/codecvt.o .libs/compatibility.o .libs/complex_io.o .libs/ctype.o 
.libs/debug.o .libs/debug_list.o .libs/functexcept.o .libs/globals_io.o 
.libs/ios.o .libs/ios_failure.o .libs/ios_init.o .libs/ios_locale.o 
.libs/limits.o .libs/list.o .libs/locale.o .libs/locale_init.o 
.libs/locale_facets.o .libs/localename.o .libs/stdexcept.o 
.libs/strstream.o .libs/tree.o .libs/allocator-inst.o 
.libs/concept-inst.o .libs/fstream-inst.o .libs/ext-inst.o 
.libs/ios-inst.o .libs/iostream-inst.o .libs/istream-inst.o 
.libs/istream.o .libs/locale-inst.o .libs/misc-inst.o 
.libs/ostream-inst.o .libs/sstream-inst.o .libs/streambuf-inst.o 
.libs/streambuf.o .libs/string-inst.o .libs/valarray-inst.o 
.libs/wlocale-inst.o .libs/wstring-inst.o .libs/atomicity.o 
.libs/codecvt_members.o .libs/collate_members.o .libs/ctype_members.o 
.libs/messages_members.o .libs/monetary_members.o 
.libs/numeric_members.o .libs/time_members.o .libs/basic_file.o 
.libs/c++locale.o -Wl,--whole-archive ../libmath/.libs/libmath.a 
../libsupc++/.libs/libsupc++convenience.a -Wl,--no-whole-archive  -lm 
../libmath/.libs/libmath.a -lm ../libsupc++/.libs/libsupc++convenience.a 
-lm -L/cross-tools/lib/gcc/x86_64-unknown-linux-gnu/4.2.4 
-L/cross-tools/lib/gcc/x86_64-unknown-linux-gnu/4.2.4/../../../../x86_64-unknown-linux-gnu/lib/../lib64
 
-L/tools/lib/../lib64 
-L/cross-tools/lib/gcc/x86_64-unknown-linux-gnu/4.2.4/../../../../x86_64-unknown-linux-gnu/lib
 
-L/tools/lib -L/usr/i486-slackware-linux/bin 
-L/usr/i486-slackware-linux/lib 
-L/usr/lib/gcc/i486-slackware-linux/4.2.4 
-L/usr/lib/gcc/i486-slackware-linux/4.2.4/../../../../i486-slackware-linux/lib 
-L/usr/lib/gcc/i486-slackware-linux/4.2.4/../../.. -lm -lm -lm -lgcc_s 
-lc -lgcc_s -lm -lgcc_s -lc -lgcc_s -lm -lgcc_s -lc -lgcc_s -lm 
/usr/lib/libstdc++.so -lm -lgcc_s -lc -lgcc_s   
/cross-tools/lib/gcc/x86_64-unknown-linux-gnu/4.2.4/crtendS.o 
/tools/lib/../lib64/crtn.o  -Wl,-O1 -Wl,-z -Wl,relro -Wl,--gc-sections 
-Wl,--version-script=libstdc++-symbols.ver -Wl,-soname 
-Wl,libstdc++.so.6 -o .libs/libstdc++.so.6.0.9
/usr/lib/libstdc++.so: could not read symbols: File in wrong format
collect2: ld returned 1 exit status
make[5]: *** [libstdc++.la] Error 1

I don't think the compile should be using/linking to  
/usr/lib/libstdc++.so at this point but I could be wrong

Is there a way to get past this?



Sorry for sending this here but I can not find the clfs support mailing 
list,
Could someone point me to the correct place?

Thanks
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: /usr/lib/libstdc++.so: could not read symbols: File in wrong format

[Baho Utot]

Simon Geard wrote:
> On Sat, 2010-02-13 at 17:32 -0500, Baho Utot wrote:
>   
>> Sorry for sending this here but I can not find the clfs support mailing 
>> list,
>> Could someone point me to the correct place?
>> 
>
> Under "Mailing Lists", off the CLFS front page.
>
> http://trac.cross-lfs.org/wiki/lists
>
> Simon.
>   
All the email where returned as failures I still can't find the correct 
address

There isn't is an address like clfs-supp...@linuxfromscratch.org (I know 
that email is not good it was returned as failure) on the page

Cut an paste would be nice



-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

LFS 6.5 6.9. Glibc-2.10.1 test error

[Baho Utot]

The system is a AMD phenom II 820 X4 Quad core with 8 GB ram
Host is Slackware 12.2 - only sees 4 GB Ram non pae kernel

Is this ok?

gcc tst-cpuclock2.c -c -std=gnu99 -fgnu89-inline -O2 -O3 -Wall -Winline 
-Wwrite-strings -fmerge-all-constants -g -march=i486 -mtune=native -pipe 
-Wstrict-prototypes -mpreferred-stack-boundary=2 -I../include 
-I/Build/glibc-build/rt -I/Build/glibc-build -I../sysdeps/i386/elf 
-I../nptl/sysdeps/unix/sysv/linux/i386/i686 
-I../nptl/sysdeps/unix/sysv/linux/i386 -I../sysdeps/unix/sysv/linux/i386 
-I../nptl/sysdeps/unix/sysv/linux -I../nptl/sysdeps/pthread 
-I../sysdeps/pthread -I../sysdeps/unix/sysv/linux -I../sysdeps/gnu 
-I../sysdeps/unix/common -I../sysdeps/unix/mman -I../sysdeps/unix/inet 
-I../sysdeps/unix/sysv/i386 -I../nptl/sysdeps/unix/sysv 
-I../sysdeps/unix/sysv -I../sysdeps/unix/i386 -I../nptl/sysdeps/unix 
-I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/i386/i686/fpu 
-I../nptl/sysdeps/i386/i686 -I../sysdeps/i386/i686 
-I../sysdeps/i386/i486 -I../nptl/sysdeps/i386/i486 -I../sysdeps/i386/fpu 
-I../nptl/sysdeps/i386 -I../sysdeps/i386 -I../sysdeps/wordsize-32 
-I../sysdeps/ieee754/ldbl-96 -I../sysdeps/ieee754/dbl-64 
-I../sysdeps/ieee754/flt-32 -I../sysdeps/ieee754 
-I../sysdeps/generic/elf -I../sysdeps/generic -I../nptl  -I.. -I../libio 
-I.  -D_LIBC_REENTRANT -include ../include/libc-symbols.h   
-DNOT_IN_libc=1-o /Build/glibc-build/rt/tst-cpuclock2.o -MD -MP -MF 
/Build/glibc-build/rt/tst-cpuclock2.o.dt -MT 
/Build/glibc-build/rt/tst-cpuclock2.o
gcc -nostdlib -nostartfiles -o /Build/glibc-build/rt/tst-cpuclock2  
-Wl,-dynamic-linker=/lib/ld-linux.so.2   -Wl,-z,combreloc -Wl,-z,relro 
-Wl,--hash-style=both /Build/glibc-build/csu/crt1.o 
/Build/glibc-build/csu/crti.o `gcc --print-file-name=crtbegin.o` 
/Build/glibc-build/rt/tst-cpuclock2.o /Build/glibc-build/rt/librt.so 
/Build/glibc-build/nptl/libpthread_nonshared.a 
/Build/glibc-build/nptl/libpthread.so  
-Wl,-rpath-link=/Build/glibc-build:/Build/glibc-build/math:/Build/glibc-build/elf:/Build/glibc-build/dlfcn:/Build/glibc-build/nss:/Build/glibc-build/nis:/Build/glibc-build/rt:/Build/glibc-build/resolv:/Build/glibc-build/crypt:/Build/glibc-build/nptl
 
/Build/glibc-build/libc.so.6 /Build/glibc-build/libc_nonshared.a -lgcc 
-Wl,--as-needed -lgcc_s  -Wl,--no-as-needed `gcc 
--print-file-name=crtend.o` /Build/glibc-build/csu/crtn.o
GCONV_PATH=/Build/glibc-build/iconvdata LC_ALL=C   
/Build/glibc-build/elf/ld-linux.so.2 --library-path 
/Build/glibc-build:/Build/glibc-build/math:/Build/glibc-build/elf:/Build/glibc-build/dlfcn:/Build/glibc-build/nss:/Build/glibc-build/nis:/Build/glibc-build/rt:/Build/glibc-build/resolv:/Build/glibc-build/crypt:/Build/glibc-build/nptl
 
/Build/glibc-build/rt/tst-cpuclock2  > 
/Build/glibc-build/rt/tst-cpuclock2.out
make[4]: *** [/Build/glibc-build/rt/tst-cpuclock2.out] Error 1

The tst-cpuclock1.o was fine

Chapter 5 was fine, I ran the test and did not see any problems there.

Did some searching on the web and I believe it is not a problem, am I 
correct?

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: LFS 6.5 6.9. Glibc-2.10.1 test error

[Baho Utot]

Bruce Dubbs wrote:
> Baho Utot wrote:
>   
>> The system is a AMD phenom II 820 X4 Quad core with 8 GB ram
>> Host is Slackware 12.2 - only sees 4 GB Ram non pae kernel
>>
>> Is this ok?
>>
>> /Build/glibc-build/rt/tst-cpuclock2  > 
>> /Build/glibc-build/rt/tst-cpuclock2.out
>> make[4]: *** [/Build/glibc-build/rt/tst-cpuclock2.out] Error 1
>> 
>
>   
>> The tst-cpuclock1.o was fine
>>
>> Chapter 5 was fine, I ran the test and did not see any problems there.
>>
>> Did some searching on the web and I believe it is not a problem, am I 
>> correct?
>> 
>
> Probably.  What aare the contents of your 
> /Build/glibc-build/rt/tst-cpuclock2.out file.  It should be only one or 
> two lines.
>
>-- Bruce
>
>   
cat /mnt/lfs/Build/glibc-build/rt/tst-cpuclock2.out
live thread clock fffdd58e resolution 0.1
live thread before sleep => 0.53078
self thread before sleep => 0.000169320
live thread after sleep => 0.501525776
self thread after sleep => 0.000186263
process before - after 500355090 outside reasonable range (501472698)

Then make bails
make[4]: [/Build/glibc-build/posix/annexc.out] Error 1 (ignored)
make[4]: *** [/Build/glibc-build/rt/tst-cpuclock2.out] Error 1
make[3]: *** [rt/tests] Error 2
make[2]: *** [check] Error 2

I ran this compile with -j4, I have tried w/o -jx and various CFLAGS, 
always result is the same

How do I know if all the tests completed (even if some failed) and it 
did not bail early?

Thanks
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: LFS 6.5 6.9. Glibc-2.10.1 test error

[Baho Utot]

William Immendorf wrote:
> On Wed, Feb 17, 2010 at 9:16 AM, Baho Utot  wrote:
>   
>> The system is a AMD phenom II 820 X4 Quad core with 8 GB ram
>> 
> This seems to be a common Phenom II problem, as Trac user ringlis got
> the same error, albeit with LFS 6.6-rc1 and Glibc-2.11.1. Of cource,
> it could be heavy system load or for other reasons, but other than
> that, I can't confirm this, as I don't have a Phenom II, but I would
> love a Phenom II 3.4GHZ, but when I do get one, I'll try it out.
>
>   

I don't understand how a quad core would be "under heavy system load", I 
suppose it is possible, I just haven't seen it.
I haven't seen mine with all 4 cores maxed out.  Even when I do a make 
-j4 it still is at about 20%-30% idle ( using top 1)  on all 4 cores.

When using cpu scaling and I have is set to run the core at 800 MHz I 
still have plenty of power as it never hits full rated speed, except on 
a build and then is goes full speed and back to idle (800 MHz) very fast.

Typical on the system with i686 system: KDE 3.5.10 with thunderbird, 
konqueror ( 6 windows ) and knode running is:

top - 15:31:19 up 9 min,  8 users,  load average: 0.08, 0.12, 0.10
Tasks: 129 total,   1 running, 128 sleeping,   0 stopped,   0 zombie
Cpu0  :  0.0%us,  0.0%sy,  0.0%ni,100.0%id,  0.0%wa,  0.0%hi,  0.0%si,  
0.0%st
Cpu1  :  0.3%us,  0.0%sy,  0.0%ni, 99.7%id,  0.0%wa,  0.0%hi,  0.0%si,  
0.0%st
Cpu2  :  0.0%us,  0.0%sy,  0.0%ni,100.0%id,  0.0%wa,  0.0%hi,  0.0%si,  
0.0%st
Cpu3  :  2.0%us,  0.0%sy,  0.0%ni, 97.7%id,  0.0%wa,  0.3%hi,  0.0%si,  
0.0%st
Mem:   3372656k total,   506432k used,  2866224k free, 1672k buffers
Swap:  1517752k total,0k used,  1517752k free,   251308k cached

Running Slamd64 (multi-lib) is about the same except it's using all 8 GB 
ram.

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: LFS 6.5 6.9. Glibc-2.10.1 test error

[Baho Utot]

Bruce Dubbs wrote:
> Baho Utot wrote:
>
>   
>> cat /mnt/lfs/Build/glibc-build/rt/tst-cpuclock2.out
>> live thread clock fffdd58e resolution 0.1
>> 
>
>   
>> live thread before sleep => 0.53078
>> self thread before sleep => 0.000169320
>> live thread after sleep => 0.501525776
>> self thread after sleep => 0.000186263
>> 
>
>   
>> process before - after 500355090 outside reasonable range (501472698)
>> 
>
> What this test is doing is checking the difference between thread times 
> and process times.  The values above are nanoseconds.  It's saying that 
> the process time is shorter than the thread time (by slightly more than 
> one millisecond).  This is a breakdown of the code:
>
> clock_gettime (process_clock, &process_before)
> clock_gettime (th_clock, &before)
> clock_gettime (my_thread_clock, &me_before)
>
> struct timespec sleeptime = { .tv_nsec = 5 };
> nanosleep (&sleeptime, NULL)
>
> clock_gettime (th_clock, &after)
> clock_gettime (process_clock, &process_after)
> clock_gettime (my_thread_clock, &me_after)
>
>
> What appears to be happening is that the main process sleeps while the 
> thread doesn't.  The thread time is thus 501525775 ns,  The limits here 
> are 1 to 6 ( .1 to .6 seconds) and it passes.
>
> The time for the my_thread_clock should be less than 0.1 second and that 
> passes.  No data is given about that though.  I added a printout and it 
> was generally about 12000 ns.
>
> Google suggests that being in chroot may be a factor.
>
> To check that out, I rebuilt glibc on my system outside of chroot.  I 
> was able to duplicate the error.
>
> live thread before sleep => 0.57951
> self thread before sleep => 0.000168869
> live thread after sleep => 0.500118785
> self thread after sleep => 0.000180958
> process before - after 499973217 outside reasonable range (500060834)
>
> And on other runs, I get:
>
> live thread clock fffc65f6 resolution 0.1
> live thread before sleep => 0.30323
> self thread before sleep => 0.000120303
> live thread after sleep => 0.500091485
> self thread after sleep => 0.000130988
> process before - after 499295588 outside reasonable range (500061162)
>
> bdu...@core2-64 [ /mnt/lfs/sources/glibc-build ]$ rt/tst-cpuclock2
> live thread clock fffc65de resolution 0.1
> live thread before sleep => 0.04984
> self thread before sleep => 0.000112728
> live thread after sleep => 0.500025515
> self thread after sleep => 0.000122332
>
> So it is intermittent timing error.  Here is another failure after I 
> modified the test to print out more data:
>
> process before sleep => 0.000141026
> live thread before sleep => 0.34383
> self thread before sleep => 0.000118320
> live thread after sleep  => 0.500092632
> process after sleep  => 0.500097116
> self thread after sleep  => 0.000130039
> process before - after 499956090 outside reasonable range (500058249)
> thread  before - after 500058249
> process before - after 499956090
> my_diff before - after 11719
>
> In this case, the timers say that the process was 102159 ns or about 
> 1/1000 second faster than the thread.  This may have some implications 
> in certain real time applications, but I don't see an issue for LFS.
>
> A pass looks like:
>
> thread  before - after 505293557
> process before - after 505305328
>
>-- Bruce
>   

Thanks for taking the time to check this out.

I have looked at CLFS glibc build and builds from arch linux and tried 
various CFLAGS to no CFLAGS and nothing seems to change the out come 
always get the same results.
So I believe it could possibly be due to the hardware?

Any way I have went ahead and installed 6.9 glibc and it came back with:

CC="gcc" /usr/bin/perl scripts/test-installation.pl /Build/glibc-build/
Your new glibc installation seems to be ok.
make[2]: Leaving directory `/Build/glibc-2.10.1'
make[1]: Leaving directory `/Build/glibc-build'

So I am thinking the build is fine.
I'll keep a look out for strange happenings later in the builds ;-)

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: LFS 6.5 6.9. Glibc-2.10.1 test error

[Baho Utot]

Bruce Dubbs wrote:
> Baho Utot wrote:
>
>   
>> I don't understand how a quad core would be "under heavy system load", 
>> 
>
> You're right.  I've done a bit of research and testing today and I'm 
> rewriting the error sections.
>
> "The nptl/tst-clock2, nptl/tst-attr3, and rt/tst-cpuclock2
> tests have been known to fail.  The reason is not completely understood, 
> but indications are that minor timing issues can trigger these failures."
>
>-- Bruce
>
>   

Wow... a light came on

nptl - threads
rt- real time

Any way Thanks


-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

LFS-6.5 8.3. Linux-2.6.30.2

[Baho Utot]

Yikes.my hand done builds and my now scripts/Makefile/Build system 
worked so far!

On i686 or x86_64 platform..

I want to boot this from a USB thumb drive.
Any pointers on what I need to set?

Also is there a "generic" config file around for i686?
Just the basic minimal needed, so I can add things as I go.

Thanks


-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: Still no USB

[Baho Utot]

Bruce Dubbs wrote:
> brown wrap wrote:
>   
>> I have been away from LFS for a few days, but now back to it. I did
>> confirm the system is up by by installing SSH and DHCP. I can bring
>> up the system, which has no keyboard access, but log into from
>> another machine. Below is the latest output of sys.log. Does anyone
>> know what the error means? I keep getting errors which say "device
>> not accepting address ..., error 110
>> 
>
> [putolin]
>   

> I don't know what this stuff is:
> [0.353143] cfg80211: Using static regulatory domain info
> [0.353216] cfg80211: Regulatory domain: US
>   
This is for wireless, it is setting the regulatory domain to US which 
sets up the wireless attachment for use in the US.
Freq/power that type of thing.  The 80211  is 802.11 protocol stack

Here is a link if you are interested-->  
http://linuxwireless.org/en/developers/Documentation/cfg80211



-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: LFS-6.5 8.3. Linux-2.6.30.2

[Baho Utot]

Simon Geard wrote:
> On Mon, 22 Feb 2010 10:58:56 -0500, Baho Utot 
> wrote:
>   
>> Yikes.my hand done builds and my now scripts/Makefile/Build system 
>> worked so far!
>>
>> On i686 or x86_64 platform..
>>
>> I want to boot this from a USB thumb drive.
>> Any pointers on what I need to set?
>> 
>
> Since you're booting off USB storage, USB support needs to be built-in, not
> compiled as a module. Conversely, anything relating to IDE/SATA support can
> be made a module, since it's no longer needed to boot. Otherwise, a flash
> drive should be fairly similar to any other system...
>
>   

Ok thanks, I would have missed the SATA/IDE as modules, I did pickup on 
that it is a good thing to have ext2/3 built in.
>> Also is there a "generic" config file around for i686?
>> Just the basic minimal needed, so I can add things as I go.
>> 
>
> Not really. X86 hardware is so varied, there's no such thing as generic,
> short of enabling every possible driver like the distros do. And that's
> certainly not what you'd call minimal. The kernel defaults are as good a
> starting point as any, but you'd still be spending half an hour or so going
> through the menus, working out what's relevant to you and what isn't.
>
> Simon.
>   
What I was hoping for is that if you look at each section separtly in 
the kernel configuration, I think there are things that need to be set 
as in BSD accounting etc that would/is required for LFS,  I understand 
that one can't get generic on the hardware.  If there was a kernel 
config that had everything that "must" be set then I could take that and 
add the hardware piece to it.

I'll try a make mrproper/make xconfig and see how it goes, first looking 
at everything but the hardware piece, save that as a start and then add 
the hardware.

Thanks


-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: LFS-6.5 8.3. Linux-2.6.30.2

[Baho Utot]

Simon Geard wrote:
> On Tue, 23 Feb 2010 08:54:35 -0500, Baho Utot 
> wrote:
>   
>> Ok thanks, I would have missed the SATA/IDE as modules, I did pickup on 
>> that it is a good thing to have ext2/3 built in.
>> 
>
> The key thing is that modules aren't available until the root filesystem is
> mounted. Therefore, anything that's required to get to that point cannot be
> a module - specifically, the hardware drivers that allow it to see the
> disk, and the filesystem driver that allows it to read the contents.
> Practically anything else can be a module, but those things cannot be
> (barring initramfs setups, which are very much an experts-only subject).
>
> Simon.
>   
I will need the initramfs later as I would like to have an encrypted 
root file system at some point.
The goal is to replace my current distro with LFS, my current setup has 
encrypted file systems on a raid 5 array, I don't know if I can get 
there...We'll see ;)
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

LFS 6.5 Boot USB

[Baho Utot]

I have finished my LFS 6.5 build

I now want to boot it from USB thumb drive.

Here is what I did

fdisk usb drive changing the partition type to 83 (linux)

mkfs.ext2 /dev/sdd1 ---/dev/sdd1 is the usb drive

mount /dev/sdd1 /media/disk

rsync -var /mnt/lfs/ /media/disk/

changed the /boot/grub/menu.lst on the sata raid array ( main storage 
system connected to the computer )
there are three drives in a raid 5 array that make the usb drive hd3 to grub
added entry
title LFS USB
root (hd3,0)
kernel /boot/lfskernel-2.6.30.2 root=/dev/sdd1 ro

changed the /etc/fstab to
# Begin /etc/fstab

# file system  mount-point  typeoptions dump  fsck
#   
 order
/dev/sdd1/ ext2 
defaults   1 1
proc   /proc   proc 
defaults   0 0
sysfs  /sys  sysfs
defaults   0 0
devpts/dev/ptsdevpts  gid=4,mode=620  0 0
tmpfs /dev/shm  tmpfs   defaults
0 0
# End /etc/fstab

Booted computer

The grub part worked as the kernel started, then failed with
Kernel panic - not syncing:VFS: Unable to mount root fs on unknown 
block(2,0)

I tried changing the fstab entry to
UUID=d6cb4887-1eb2-4180-9566-391a8b3f7b45   / 
ext2 defaults   1 1

Still barfs with the above error

The kernel has ext2 and ext3 built in and I set all the USB options

Any one have any hints or see something I missed?




-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

LFS 6.5 Boot USB

[Baho Utot]

I have finished my LFS 6.5 build

I now want to boot it from USB thumb drive.

Here is what I did

fdisk usb drive changing the partition type to 83 (linux)

mkfs.ext2 /dev/sdd1 ---/dev/sdd1 is the usb drive

mount /dev/sdd1 /media/disk

rsync -var /mnt/lfs/ /media/disk/

changed the /boot/grub/menu.lst on the sata raid array ( main storage
system connected to the computer )
there are three drives in a raid 5 array that make the usb drive hd3 to grub
added entry
title LFS USB
root (hd3,0)
kernel /boot/lfskernel-2.6.30.2 root=/dev/sdd1 ro

changed the /etc/fstab to
# Begin /etc/fstab

# file system  mount-point  typeoptions dump  fsck
#
 order
/dev/sdd1/ ext2
defaults   1 1
proc   /proc   proc
defaults   0 0
sysfs  /sys  sysfs
defaults   0 0
devpts/dev/ptsdevpts  gid=4,mode=620  0 0
tmpfs /dev/shm  tmpfs   defaults
0 0
# End /etc/fstab

Booted computer

The grub part worked as the kernel started, then failed with
Kernel panic - not syncing:VFS: Unable to mount root fs on unknown
block(2,0)

I tried changing the fstab entry to
UUID=d6cb4887-1eb2-4180-9566-391a8b3f7b45   /
ext2 defaults   1 1

Still barfs with the above error

The kernel has ext2 and ext3 built in and I set all the USB options

Any one have any hints or see something I missed?





-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: LFS 6.5 Boot USB

[Baho Utot]

Hans_2 wrote:
>> title LFS USB
>> root (hd3,0)
>> kernel /boot/lfskernel-2.6.30.2 root=/dev/sdd1 ro
>> 
>
> How about entering kerneloption rootdelay = 10? That solved my problem  
> with booting from my USB-harddisk.
>
>
> Hans.
>
>   
OK tahnks I will try that
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

LFS-6.6 booting USB grub

[Baho Utot]

I would like to boot LFS-6.5 on USB

I have it working except that when I change from my desktop computer 
which has 3 drives to my laptop that only has one drive I must edit grub 
and change the kernel line to point to the prober /dev/sdx drive

I would like to boot grub on the USB drive and have it come up without 
editing the kernel line for the drive

I have searched the web looking for fixes and tried using UUID and Labels. 

I have used e2label to set the label on the USB drive to LFS-6.5

Here is what I tried ( The first entry works the other don't )

# Begin /boot/grub/menu.lst

# By default boot the first menu entry.
default 0

# Allow 30 seconds before booting the default.
timeout 30

# Use prettier colors.
color green/black light-green/black

# The first entry is for LFS.
title LFS 6.5-SDD1
root (hd0,0)
kernel /boot/lfskernel-2.6.30.2 root=/dev/sdd1 rootdelay=10

title LFS 6.5-UUID
root (hd0,0)
kernel /boot/lfskernel-2.6.30.2 
root=UUID=6cb4887-1eb2-4180-9566-391a8b3f7b45 ro rootdelay=10

title LFS 6.5-LABEL
root (hd0,0)
kernel /boot/lfskernel-2.6.30.2 root=LABEL=LFS-6.5 ro rootdelay=10

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: LFS-6.6 booting USB grub

[Baho Utot]

Bruce Dubbs wrote:
> Hans Kaper wrote:
>
>   
>> I am curious to know what the experts have to say about why the UUID- and  
>> LABEL-options don't work.
>> 
>
> I'm not sure about the LABEL, but I know that the UUID option has to be 
> handled in an initrd.
>
>-- Bruce
>   
I have since found out that UUID and LABEL are a redhat twist.  THey 
require an initrd and nash.
nash mounts the drives ( does the dirty work and passes the info to the 
kernel ).
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: LFS-6.6 booting USB grub

[Baho Utot]

Hans Kaper wrote:
> Op Thu, 25 Feb 2010 17:23:58 +0100 schreef Baho Utot  
> :
>
>   
>> I would like to boot LFS-6.5 on USB
>>
>> I have it working except that when I change from my desktop computer
>> which has 3 drives to my laptop that only has one drive I must edit grub
>> and change the kernel line to point to the prober /dev/sdx drive
>>
>> I would like to boot grub on the USB drive and have it come up without
>> editing the kernel line for the drive
>>
>> I have searched the web looking for fixes and tried using UUID and  
>> Labels.
>>
>> I have used e2label to set the label on the USB drive to LFS-6.5
>>
>> 
>
>   
>> # The first entry is for LFS.
>> title LFS 6.5-SDD1
>> root (hd0,0)
>> kernel /boot/lfskernel-2.6.30.2 root=/dev/sdd1 rootdelay=10
>>
>> 
> It surprises me that this works on your laptop with only one drive. Why  
> should your USB-device on the laptop also be named sdd1 as it is on your  
> desktop?
>
>   

It doesn't work on the laptop, I need to change the entry to 
root=/dev/sdb1 to make it work

>> title LFS 6.5-UUID
>> root (hd0,0)
>> kernel /boot/lfskernel-2.6.30.2
>> root=UUID=6cb4887-1eb2-4180-9566-391a8b3f7b45 ro rootdelay=10
>>
>> title LFS 6.5-LABEL
>> root (hd0,0)
>> kernel /boot/lfskernel-2.6.30.2 root=LABEL=LFS-6.5 ro rootdelay=10
>>
>> 
> I tried these too, but did not succeed either. The succesful advice I got  
> was to delete the root= option altogether when booting from the USB-device  
> because the bootpartition is already defined with the root(hd0,0)  
> Grub-entry.
> I am curious to know what the experts have to say about why the UUID- and  
> LABEL-options don't work.
>   

I'll try deleting the root= option and have a go at it.
The rootdelay option that you posted worked

See my follow up to Bruce on the LABEL/UUID

Thanks


-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: LFS-6.6 booting USB grub

[Baho Utot]

Ken Moffat wrote:
> On 25 February 2010 21:38, Baho Utot  wrote:
>
>   
>> I have since found out that UUID and LABEL are a redhat twist. Â THey
>> require an initrd and nash.
>> nash mounts the drives ( does the dirty work and passes the info to the
>> kernel ).
>> 
>
> Do you mean that (about UUID and LABEL), or perhaps you mean
> "when booting from an external disk" ?
>
>   

Doesn't matter internal or external.
See below.
 
> I've had LABEL= in the fstab on my server for about 2 years,
> ever since I had to start using libata on that box.  No initrds,
> no fedoras, and no substandard minimalist shells.
>   

I have used it as well for a number of years with different distros ( 
RH6.0 to Fedora 10 and  Arch).
That is why I tried it with LFS. 
Apparently it won't work with a "pure" gnu/grub environment.
It takes some tickling.

According to some info I found from a site while searching google it was 
redhat that started the UUID LABEL into grub stuff.
It also reported that some other distros picked it up as well, using 
their own implementation(s).
I will see if I can find the link again as I did not save it and post it.

>  Might not work on all filesystems, but should work for at
> least ext{2,3,4} - set it in tune2fs or e2label.
>   

I am using ext2 as I have it on a 2GB thumb drive.
On my raid arrays I use jfs and ext2 for the /boot partition. 
I need a separated boot partition because I have an encrypted root file 
system and all the /home file systems are encrypted as well.
The only thing not encrypted is the lone /boot partition.

>  But for explanations of your inability to boot from an external
> disk except by specifying /dev/sdXn I have no idea.  Are you
> sure you set it to what you put in grub.conf ?
>
>   

Yes, tried many times by modifying menu.lst and by using the cmd line in 
grub to change the kernel line.
When the kernel line is set to uuid or label you get the error Kernel 
panic - not syncing:VFS : unable to mount root fs on unknown block(2,0).
Meaning it can not digest the uuid or label params, it barfs and then I 
need to clean that up.

If I look up into the boot sequence I find that it doesn't know about 
the root=/dev/disk/by-uuid=
same with root=UUID= or root=LABEL=:LFS-6.5".
It all fails.

When I use the root=/dev/sdX1 it works, so I know I have the drivers 
that I need compiled into the kernel etc.

>  If you were using "grub2" I would guess that using labels in
> grub is not yet implemented:
> http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/516ac0deccafb3af?pli=1
>
> ĸen
>   

I am not ready for grub2 yetI have well enough trouble with 
grub-legacy. ;-)

Thanks

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Error in BLFS Book Version svn-20100215

[Baho Utot]

Small flea on the MTA page.   
/blfs-book-svn-html-2010-02-25/server/mail.html

There isn't any IMAP server (Courier-IMAP)

Mail Server Software
 MTAs are the programs which transport mail from one machine to the 
other. The traditional MTA is Sendmail, however there are several other 
choices.
 As well as SMTP servers there is a POP server (qpopper) and an IMAP 
server (Courier-IMAP).
 Table of Contents
Exim-4.67
Postfix-2.5.1
Qpopper-4.0.9
Sendmail-8.14.1
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: Partition Sizes, AGAIN!

[Baho Utot]

Andrew Benton wrote:
> On 04/03/10 20:13, Mike McCarty wrote:
>   
>> Andrew Benton wrote:
>>
>> 
>>> I use one partition for both /home and /boot. IE, /boot is a symbolic link
>>> pointing at /home/boot
>>>   
>> Why not just use an ordinary directory for /boot, then? Is
>> there something I don't know?
>> 
>
> I keep my kernel in /home/boot, along with all grub's files, so that if I 
> boot into one
> LFS partition or the other I can use the same kernel and I never need to use 
> grub to rewrite
> the MBR
>
> Andy
>   

I don't understand how that helps

I use a boot partition and this layout

$ ls /boot
LFS-6.5/  Slack-x86-crypt/  Slackware-13.0-x86/  grub/  lost+found/


-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: Partition Sizes, AGAIN!

[Baho Utot]

Bruce Dubbs wrote:
> Mike McCarty wrote:
>
>   
>> I don't like a separate swap partition, because it's difficult to
>> resize, and the information I have is that with 2.6 kernels a swap file
>> is as fast as a separate partition, and much easier to resize.
>> 
>
> Interesting.  I've never had to resize a swap partition.  I generally 
> start a new system using a commercial distro and just let it use the 
> default size for a swap partition.  My current systems have swap size 
> the same a RAM size.
>
> You do know that you can use both a swap partition and a swap file at 
> the same time, right?
>
>-- Bruce
>   

You can also split up the swap partition over multiple drive ( If you 
have them ) and the kernel will strip the writes to the different drives 
something like raid does.


-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: Partition Sizes, AGAIN!

[Baho Utot]

Mike McCarty wrote:
> Baho Utot wrote:
[putolin]

I use a boot partition and this layout
>> $ ls /boot
>> LFS-6.5/  Slack-x86-crypt/  Slackware-13.0-x86/  grub/  lost+found/
>> 
>
> If /boot is an ordinary directory under /, and not a mount point,
> then one needs to modify the MBR to point to the place to find
> the boot record.
>
> Mike
>   

Only the first time it is set up.  Never on updates.
All that you have to modify menu.lst.
The way I have it you have all the boot stuff in one place.
I also don't mount the boot partition from the fstab $( it is not 
necessary ).
That way if you do an update the update can not clobber the others.
You do have to then move the updated files to the boot partition though.

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: Partition Sizes, AGAIN!

[Baho Utot]

Mike McCarty wrote:
> Baho Utot wrote:
>   
>> Mike McCarty wrote:
>> 
>>> Baho Utot wrote:
>>>   
>> [putolin]
>>
>> I use a boot partition and this layout
>> 
>>>> $ ls /boot
>>>> LFS-6.5/  Slack-x86-crypt/  Slackware-13.0-x86/  grub/  lost+found/
>>>> 
>>>> 
>>> If /boot is an ordinary directory under /, and not a mount point,
>>> then one needs to modify the MBR to point to the place to find
>>> the boot record.
>>>
>>> Mike
>>>   
>>>   
>> Only the first time it is set up.  Never on updates.
>> 
>
> Perhaps I haven't made clear what my understanding was.
>
> If /boot is an ordinary directory, then one appears in each
> of the "/" partitions, and that's the point of not doing so,
> but rather making /boot in each of the / partitions be a link
> to the one in /home/boot. Since /home is only one partition,
> then there is only one "real" /boot.
>
>   

So as my setup, I just do it it a more standard way. 
BTW I understand your method.

> If each partition has it's own /boot which is an ordinary
> directory, and not a mount point or link to another ordinary
> directory in another mounted partition, then you'd have to
> modify the MBR to point to the appropriate /boot in order
> to load the GRUB which is set up to use that partition.
>
>   

Not so.  I have one point a boot partition that works/serves  3 installs 
$(currently), when I add a fourth all that needs to be done is to add a 
directory in /boot $(partition), add the kernel files for the install 
and add an entry to menu.lst.
 I never have to change the master boot record or "install"/rerun grub.  
it's always "in the same place", it never changes.

This current running system ( Slackware 12-2 ) has this in fstab:

~$ cat /etc/fstab
/dev/md1 swap swapdefaults,noatime 0   0
/dev/mapper/root /jfs defaults,noatime 1   1
devpts   /dev/pts devpts  gid=5,mode=620   0   0
proc /procprocdefaults 0   0
tmpfs/dev/shm tmpfs   defaults,size=256M 0   0
tmpfs   /tmptmpfs   defaults,nodev,nosuid,mode=1777,size=256M 0 0

this is the result of ~$  ls /boot
~$ 

Notice that it is empty, there are no files there.  I just leave the 
/boot filesystem $( on the root filesystem ) there in case I need to 
work on it, I just mount it when I need to.
Notice that the fstab does not have the boot partition mounted.
You don't need to. Once the system has booted /boot has done its work.

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: LFS on USB?

[Baho Utot]

cly...@clydew.org wrote:
> Is it possible to build Linux from Scratch on a USB Flash Drive.  I 
> did build it there but am having a time getting Grub to recognize it.
>
Yes I built LFS-6.5 on my desktop and transfered it to a USB drive with 
rsync
Building directly on the usb drive is slow and not necessary.
Don't do the rsync while booted into LFS.
You need the USB stuff built into the kernel as well as the filesystem ( 
I used ext2) and necessary hardware drivers, not as modules.

The sequence should go something like the following:

partition and format the usb drive
mount the the drive
mount /dev/sdXn  
rsync -var /mnt/lfs/  
install grub to the usb drive MBR
Then setup /boot

The following is from my bootable usb thumb drive (mount at /media/LFS):

/boot should look like this

~$ ls /media/LFS/boot/
System.map-2.6.30.2 config-2.6.30.2-2010-02-28  lfskernel-2.6.30.2
config-2.6.30.2-2010-02-26  grub/

~$ ls /media/LFS/boot/grub
defaultffs_stage1_5  minix_stage1_5 ufs2_stage1_5
device.map iso9660_stage1_5  reiserfs_stage1_5  vstafs_stage1_5
e2fs_stage1_5  jfs_stage1_5  stage1 xfs_stage1_5
fat_stage1_5   menu.lst  stage2

/boot/grub/menu.lst should be like this

# Begin /boot/grub/menu.lst

# By default boot the first menu entry.
default 0

# Allow 30 seconds before booting the default.
timeout 30

# Use prettier colors.
color green/black light-green/black

# The first entry is for LFS.
title LFS 6.5
root (hd0,0)
kernel /boot/lfskernel-2.6.30.2 ro rootdelay=10

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: lLFS on USB?

[Baho Utot]

Mike McCarty wrote:
> ga ho wrote:
>   
>> cly...@clydew.org wrote:
>> 
>>> Is it possible to build Linux from Scratch on a USB Flash Drive.  I 
>>> did build it there but am having a time getting Grub to recognize it.
>>>
>>>   
>> Yes I built LFS-6.5 on my desktop and transfered it to a USB drive with 
>> rsync
>> Building directly on the usb drive is slow and not necessary.
>> Don't do the rsync while booted into LFS.
>> You need the USB stuff built into the kernel as well as the filesystem ( 
>> I used ext2) and necessary hardware drivers, not as modules.
>> 
>
> This is not a good file system to use on USB FLASH drives. You want
> one which doesn't require rewriting the directory with every
> access to the file system. It'll wear out the FLASH, and it'll
> also be very very slow.
>
> Mike
>   
noatime and noadirtime fixes that and yes it does work well


-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: LFS on USB?

[Baho Utot]

Mike McCarty wrote:
> Hans Kaper wrote:
>   
>>> My grub entry for my LFS6.4 stick is:
>>>
>>> title Linux From Scratch 6.4 Kernel 2.6.30.2
>>> root (hd0,0)
>>> kernel /boot/lfskernel-2.6.30.2 root=/dev/uba1
>>>
>>>   
>> Omit the root=/dev/uba1-option. root (hd0,0) points already to the device  
>> you want to boot from.
>> 
>
> Erm, those pieces of information go to different parts of the
> system. The first is sent to, and acted upon, by GRUB. The second
> is sent to, and acted upon, by the kernel. GRUB doesn't see the
> second one, except as just some uninterpretable data to pass along,
> and the kernel never even sees the first.
>
> Mike
>   

Still it works well, I have omited the root= line on my USB drive and it 
works like a champ,  always boots.

The problem with the root line on a USB boot drive and using a root= 
line is you have to adjust it depending on how many drives the computer 
has, ie my desktop has four drives and my laptop 1.  Removing the root=/ 
line makes it work on both machines without farting around without 
adjusting the root line at boot for each.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

LFS-6.4 Book

[Baho Utot]

I would like to download the LFS-6.4 version of the book but it is 
missing from the download section

http://archive.linuxfromscratch.org/lfs-museum/

Is it still available?
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: LFS-6.4 Book

[Baho Utot]

Ken Moffat wrote:
> On 1 April 2010 00:17, Baho Utot  wrote:
>   
>> I would like to download the LFS-6.4 version of the book but it is
>> missing from the download section
>>
>> http://archive.linuxfromscratch.org/lfs-museum/
>>
>> Is it still available?
>> 
>
>  You can read it at:
> http://www.linuxfromscratch.org/lfs/view/6.4/
>
>  Quite why anyone would want to read it now, other than to compare
> what has changed, is beyond me.
>
> ĸen
>   
I need some information from it

Thanks
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: LFS-6.4 Book

[Baho Utot]

Bruce Dubbs wrote:
> Baho Utot wrote:
>   
>> I would like to download the LFS-6.4 version of the book but it is 
>> missing from the download section
>>
>> http://archive.linuxfromscratch.org/lfs-museum/
>>
>> Is it still available?
>> 
>
> Just a minor permissions problem.  Both 6.3 and 6.4 are accessible now.
>
>-- Bruce
>   
Ok thank you

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: LFS-6.4 Book

[Baho Utot]

Trent Shea wrote:
> On March 31, 2010 05:31:07 pm Ken Moffat wrote:
>   
>>  Quite why anyone would want to read it now, other than to compare
>> what has changed, is beyond me.
>> 
> I agree with Ken. I see you fighting with KDE-3, but it's mainly because 
> you're building a version that's not maintained - not officially anyways... 
>
>   

Yes my goal is a successful build of KDE3...by hook or by crook ;)

> The few packages that I have (or had) gcc-4.4 trouble with have been updated 
> or documented, the amount of time to sort them out would be far less than a 
> rebuild, push on!
>
>
>   

I just want to fetch some information.

I would like not to rebuild the system,  I want to look at compiling 
gcc-4.3.2 to see if I can be successful.
If I can build gcc-4.3.2 into /opt/gcc-4.3.2 and then use that to build 
KDE3 successfully then I am good to go and I won't
have to rebuild the system I am working with now.  That's my plan...even 
if it doesn't work, at least I'll know what not to do!


I want to use  KDE 3.5.10 as my desktop, otherwise I will have to move 
to Xcfe
I am _NOT_ going to KDE 4.x and gnome doesn't cut it for me.

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: LFS-6.6, Stage2, glibc, nscd.c:442

[Baho Utot]

On 06/01/10 15:19, Bruce Dubbs wrote:
> Paul Rogers wrote:
>
>> As seems
>> indicated by the current situation, someone should adopt a QC role, and
>> have one system that trails, i.e. has exactly the package versions
>> specified in the HSR, and verifies that each version of LFS does in fact
>> install flawlessly with those prerequisites.
>
> Volunteers welcomed.

I'll volunteer...I can mess up anything :)

At this moment I have just about recovered my LFS 6.5/BLFS devel system, 
from my LFS-6.3 build script screw up which, Ahem over wrote LFS-6.5 
with the files/package from LFS-6.3.  Care to guess when the host system 
puked?

Thank goodness I have my self written build system/scripts ;)

I am going to try it again as I am a gluten for punishment.

Hopefully without the same result!
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: LFS-6.6, Stage2, glibc, nscd.c:442

[Baho Utot]

On 06/01/10 18:24, Bruce Dubbs wrote:
> Baho Utot wrote:
>> On 06/01/10 15:19, Bruce Dubbs wrote:
>>> Paul Rogers wrote:
>>>
>>>> As seems
>>>> indicated by the current situation, someone should adopt a QC role, and
>>>> have one system that trails, i.e. has exactly the package versions
>>>> specified in the HSR, and verifies that each version of LFS does in fact
>>>> install flawlessly with those prerequisites.
>>> Volunteers welcomed.
>>
>> I'll volunteer...I can mess up anything :)
>
> Excellent.
>
>> At this moment I have just about recovered my LFS 6.5/BLFS devel system,
>> from my LFS-6.3 build script screw up which, Ahem over wrote LFS-6.5
>> with the files/package from LFS-6.3.  Care to guess when the host system
>> puked?
>
>> I am going to try it again as I am a gluten for punishment.
>
> Can you please explain a little more.  You are doing to start with a new
> 6.3 LFS system and build LFS-6.6?

I am presently using LFS-6.5 ( The one I just rebuilt  ).
That is my current daily used system.

I am using that to build LFS-6.3 with KDE-3.5.10, sound ( the works ). I 
am going to put it on an older laptop when I get it completed.

The system I am using to compile this stuff is an AMD Phenom(tm) II X4 
810 Processor that has 8G DDR3 memory. I use that system so I can make 
mistakes really fast ;) ie things can go sour quickly and at a high rate 
of speed.  You usually don't get a chance to see them let alone try to 
stop it.  Once you hit the  key its all over.  Not even enough 
time to yell out a Oh Shhhi.

I build the system(s) on a removable SATA 500G drive. Then rsync it to 
the resulting victim system.

After I get that completed I am going to try using the LFS-6.3 with 
BLFS-6.3-svn to build LFS 6.6. All of this would be using i686.

I can try building LFS-6.6 after I get the LFS-6.3 up and running then I 
can to the LFS-6.3 BLFS combo.

I can currently build the LFS-6.3 tools, that part works
I am looking at why the scripts over wrote the host instead of going to 
the chroot.  I think that I was not really in the chroot when I ran the 
chapter 06 build script.

>
> Please do report back any successes or problems.
>
> -- Bruce

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: LFS-6.6, Stage2, glibc, nscd.c:442

[Baho Utot]

On 06/01/10 19:05, Bruce Dubbs wrote:
> Baho Utot wrote:
>
>> The system I am using to compile this stuff is an AMD Phenom(tm) II X4
>> 810 Processor that has 8G DDR3 memory. I use that system so I can make
>> mistakes really fast ;) ie things can go sour quickly and at a high rate
>> of speed.  You usually don't get a chance to see them let alone try to
>> stop it.  Once you hit the  key its all over.  Not even enough
>> time to yell out a Oh Shhhi.
>
> I recommend:
>
> build-instruction 2>&1 | tee -a build.log

I do log the build but when you over write binutils/glibc/gcc and /etc/* 
with an earlier version, one has to boot to the "rescue install" to see 
what when astray. :)

>
>> I build the system(s) on a removable SATA 500G drive. Then rsync it to
>> the resulting victim system.
>
> Be careful as the kernel drivers are probably different on the systems.

Oh yes, I'll indeed get bit that that one.

>
>> After I get that completed I am going to try using the LFS-6.3 with
>> BLFS-6.3-svn to build LFS 6.6. All of this would be using i686.
>>
>> I can try building LFS-6.6 after I get the LFS-6.3 up and running then I
>> can to the LFS-6.3 BLFS combo.
>>
>> I can currently build the LFS-6.3 tools, that part works
>> I am looking at why the scripts over wrote the host instead of going to
>> the chroot.  I think that I was not really in the chroot when I ran the
>> chapter 06 build script.
>
> OK, thanks for the update.

Ok I'll let you know if I find something.

>
> -- Bruce

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: LFS (Version SVN-20100529) - 5.9. Binutils-2.20.1 - Pass 2

[Baho Utot]

Neal Murphy wrote:
> On Friday 02 July 2010 15:11:31 Face wrote:
>   
>> well, thank you all, i will start over and see what will happen.
>> I am using a shell script to do the book if someone could take a look
>> at it, that would be nice .
>>
>>
>> Sincerely
>> 
>
> Ah, you don't seem to have error detection in your script.
>
> After many of your actions, you could put
>   || (echo "'action' failed."; exit 1)
>
> For example:
>   tar -jxf ../mpfr-2.4.2.tar.bz2  >>$Logs || \
> (echo "Extracting mpfr failed."; exit 1)
>   mv -v mpfr-2.4.2 mpfr | source $Msg || \
> (echo "Renaming mpfr failed."; exit 1)
>
>
> Also 'man bash' and read up on the 'trap' built-in. You can do something like:
>   trap "echo \"'action' failed!\"; exit 1" ERR; action-to-take; trap "" ERR
>
> For example:
>   trap "echo \"Extracting mpfr failed.\"; exit 1" ERR
>   tar -jxf ../mpfr-2.4.2.tar.bz2  >>$Logs
>
>   trap "echo \"Renaming mpfr failed.\"; exit 1" ERR
>   mv -v mpfr-2.4.2 mpfr | source $Msg
>
>   trap "" ERR
>
>
> You might have to change the script to use bash instead of sh.
>
> Cleverly crafted, you should be able to catch most of the errors when they 
> happen while maintaining a readable script.
>   
If using bash a simple:

#!/bin/bash -e
set +h

at the top of the script works, bails on any error
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: LFS-svn chap 6.7 (gcc: No such file or directory)

[Baho Utot]

  On 09/08/2010 05:56 AM, Martin Zajíc  wrote:

[putolin]

> So i've rewrite gcc pass2 with last svn and it's working.
>
> I have another question about testing error.
> I try to make LOG with '{} 2>&1 | tee $BUILD_DIR/LOG_$PROGRAM.log'
> but when I did it how can I test it for errors, becouse '$?' not
> working even if the script inside ending with 'exit 1'.
>

( make 2>&1 | tee -a ${LOG} && exit $PIPESTATUS )


-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: building a driver for a different system

[Baho Utot]

On 11/02/10 07:21, Jannis Kafkoulas wrote:

Off topic for this listbut see below.
> Hi,
>
> well it's not exactly a lfs issue but a similar one in his structure.
>
> I have a RedHat EL 5.5 installed on a HP Proliant DL 360 server.
> I actually need the 5.0 version but it's missing (at least) the NIC driver 
> which is offered by HP as a rpm source.
> In any case I can't install the 5.0 system at all from the original CD.
>
> My problem now is, how do I build the driver on the 5.5 system for the 5.0 
> system and include it in a 5.0 install CD?
>
>
> I already have built a lfs a few months ago and also have heard about cross 
> compiling.
>
> My question now is, do I need to build a new 5.0 system on my 5.5 system in 
> the manner of the lfs project or is it enough to just build a cross compiler 
> and then compile the driver source with this cross compiler.

Compiling for an older distro is not cross compiling.  Cross compiling 
for instance is using an i686 computer to compile for an x86_64, or 
using a i686 to compile for a powerpc.

> As I know the driver names ends up in .ko.
> Which files do I need additionally for the driver to work in the 5.0 system, 
> like headers and alike?
>
> Any hints?
>

I would install a fresh 5.0 install and use rpm-build to build that 
package, put the resulting rpm on a usb thumb drive.

Have a look here: http://linux.die.net/man/8/rpmbuild


> Thanks
>
> Jannis
>
>
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: LFS problem

[Baho Utot]

On Monday, December 13, 2010 06:27:26 am code.xiyou wrote:
> Hello everyone,
> Some errors happened like following when i compile LFS6.3. My
> version is Ubuntu 9.04.
> l...@jiawei-laptop:/mnt/lfs/sources/glibc-build$ sudo make install

[putolin]

> /mnt/lfs/sources/glibc-build/libc.so.6
> /mnt/lfs/sources/glibc-build/libc_nonshared.a -lgcc -Wl,--as-needed -lgcc_s
> -Wl,--no-as-needed `gcc -B/tools/bin/ --print-file-name=crtend.o`
> /mnt/lfs/sources/glibc-build/csu/crtn.o
> /tools/bin/ld: unrecognized option '--hash-style=both'
> /tools/bin/ld: use the --help option for usage information
> collect2: ld returned 1 exit status


LDFLAGS="-Wl,--hash-style=gnu -Wl,--as-needed"


> make[2]: *** [/mnt/lfs/sources/glibc-build/iconv/iconv_prog] Error 1
> make[2]: Leaving directory `/mnt/lfs/sources/glibc-2.5.1/iconv'
> make[1]: *** [iconv/subdir_install] Error 2
> make[1]: Leaving directory `/mnt/lfs/sources/glibc-2.5.1'
> make: *** [install] Error 2
> 
> Any answer is okay, thanks.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: iana-etc-2.30-1-any.pkg.tar.xz

[Baho Utot]

On Sunday, December 19, 2010 06:07:04 pm Ken Moffat wrote:
> On Sun, Dec 19, 2010 at 11:43:30PM +0100, pieter blomme wrote:
> > Hi,
> > 
> > I'm at section 6.23 of the book.  I need to decompress this package, but
> > I have never encountered a .xz archive before.  I've tried several
> > suggestions on the web concerning depackaging .xz archives, but all seem
> > to return errors.  Mostly something like:
> > 
> > root:/sources# tar xzvf iana-etc-2.30-1-any.pkg.tar.xz
> > 
> > gzip: stdin: not in gzip format
> > tar: Child returned status 1
> > tar: Error is not recoverable: exiting now
> > 
> > 
> > any help would be appreciated,
> > pieter
> 
>  You seem to have two problems.  The first is trivial - recent
> versions of tar will use xz-utils to extract .tar.xz files.  The
> correct switch to force processing of a .xz archive is -J (-z is for
> gzip or .gz files).  However, xz-utils has not yet made it into the
> LFS book (unless I missed the mail from the commit).
> 
>  Which leads me to your second problem: you should be using a pristine
> version of this (apparently now orphaned) package, but the
> '-1-any.pkg' in its name suggests you have been tricked into getting
> something alse.  I've no idea about the '.any.pkg' part of the name
> (except, it has correctly been added by whoever packaged this and
> made it available - I see no malice here), but the '-1' part indicates
> a (distro-style) revision.

That package is part of Arch linux.
The any refers to the architecure, this one works on any as opposed to i686 or 
x86_64
The pkg is for pacman pkg, their package manager
The -1 is the first release of the 2.30 iana-etc source/package

> 
>  For this package, please try the copy from the development book:
> http://anduin.linuxfromscratch.org/sources/LFS/lfs-packages/conglomeration/
> /iana-etc/iana-etc-2.30.tar.bz2 and please, for all packages, check the
> md5sums of what you have
> downloaded to be sure you haven't accidentally picked up something
> different.
> 
> ĸen
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] Nobody has received the fatal error missing gmp.h in coreutils-8.14

[Baho Utot]

On 01/03/2012 06:28 PM, jasonps...@jegas.com wrote:
> I posted earlier, and I don't expect speedy response but I was hoping
> someone would say yay or Nay.
>
> compiling: coreutils-8.14 I get:
>
> expr.c:54:18 fatal error : gmp.h: no such file or directory
>
>
> Sounds kind of serious to me... has anyone see this before? Or is it me,
> my linux host or something?
>
> Thank You
> Jason
>

No I have not seen that error, but from what I can puzzle out.


If we are talking chapter 05

gmp is installed in the gcc step


If we are talking chapter 06

gmp.h is defined in the gmp-5.0.2 package, which should have been 
installed just before gcc

So it looks like you have missed something in you build.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] LFS 7.0 - No Devices in /dev on boot up - Kernel then shuts off PC

[Baho Utot]

On Wednesday 11 January 2012 05:04:31 am Simon Geard wrote:
> On Tue, 2012-01-10 at 02:20 -0700, jasonps...@jegas.com wrote:
> > Well, I opend the "previous untouchable" RC file and tossed readline all
> > over it ... and when I booted .. GUESS WHAT? I was able to step through
> > the actual boot process one command at a time... and I saw the offending
> > error for the first time... and bot this is embarrassing
> >
> > /etc/rc.f/rcS.d/S10udev Line 78 /sbin/udevd - No Such File
> >
> > I looked in my scripts that build LFS, and realized I forgot to UNTAR
> > UDEV!
>
> Next lesson - when doing scripted builds, error handling is important.
> You want the entire build to stop immediately when something goes wrong,
> instead of trying to continue, making the original error hard to find.
>
> Personally, my preferred means of dealing with that is to simply add
> "set -e" near the top of my scripts. The has the effect that if any
> command run by the script exits with a non-zero status (i.e fails), the
> script aborts immediately.
>
> Simon.

I use the following:

#!/bin/bash -e
shopt -s -o pipefail


the shopt makes sure that the error makes it through a pipe. so if you 
redirect to a log (which I do) it will stop on the error.

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: [lfs-support] Tools directory is empty

[Baho Utot]

On Tuesday 17 January 2012 12:29:40 am Firerat wrote:
> On Jan 17, 2012 5:21 AM, "Uthayanan"  wrote:
> > lfsuthayan@ubuntu:/$ ls -l /tools
> > total 48
> > drwxr-xr-x  2 lfsuthayan lfs 12288 Jan 16 11:22 bin
> > drwxr-xr-x  2 lfsuthayan lfs  4096 Jan 16 04:18 etc
> > drwxr-xr-x  4 lfsuthayan lfs  4096 Jan 10 09:26 i686-lfs-linux-gnu
> > drwxr-xr-x  4 lfsuthayan lfs  4096 Jan 16 05:00 i686-pc-linux-gnu
> > drwxr-xr-x 32 lfsuthayan lfs  4096 Jan 16 11:20 include
> > drwxr-xr-x 10 lfsuthayan lfs  4096 Jan 16 11:22 lib
> > drwxr-xr-x  6 lfsuthayan lfs  4096 Jan 16 11:06 libexec
> > drwxr-xr-x  2 lfsuthayan lfs  4096 Jan 16 11:22 sbin
> > drwxr-xr-x 13 lfsuthayan lfs  4096 Jan 16 11:23 share
> > drwxr-xr-x  2 lfsuthayan lfs  4096 Jan 16 09:21 var
> > lfsuthayan@ubuntu:/$
> >
> >> put I got
>
> /tools is not a link
>
> Confirm with
>
>  ls -l /
>
> to fix
>
> mv /tools/* /mnt/lfs/tools/
> rmdir /tools
> ln -s /mnt/lfs/tools /tools
>
> Tbh I'm a little confused how you managed to do that, as you would need to
> be root

If you are using a package manager it is easy to overwrite the symlink with a 
directory /tools.

I have had this happend many times.  In fact it is something I am very good 
at. ;)

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

[lfs-support] LFS-7.0 Chapter 6.16. MPC-0.9 FYI

[Baho Utot]

I have been working on mpc.

I have noticed that the way it is built in the book it only builds the static 
library.

If --enable-shared is passed to configure it look like that is ignored as it 
still doesn't build the shared library.

If autoreconf is run before doing the configure it builds the shared library 
as well.

I expect gcc will links to mpc statically as per the book.






-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

LFS-6.1, Kernel-2.6.11.12

[baho-utot]

LFS-6.1 build

I build a kernel (2.6.11.12) for my scratch built system and it populates
/dev with the wrong permissions, ie /dev/null with crw-rw permissions.

Non root users can not access it example: echo "Cat shit" > /dev/null.
Fails with Permission denied. (because of 660 perms)

Why would the kernel mount/populate /dev with perms set to 660.

How could it be fixed?

Could anyone explain (overview) how the kernel populates and set 
permissions in /dev ?


Thanks
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: LFS-6.1, Kernel-2.6.11.12

[baho-utot]

Andrew Benton wrote:


baho-utot wrote:


LFS-6.1 build

I build a kernel (2.6.11.12) for my scratch built system and it 
populates
/dev with the wrong permissions, ie /dev/null with crw-rw 
permissions.


Non root users can not access it example: echo "Cat shit" > /dev/null.
Fails with Permission denied. (because of 660 perms)

Why would the kernel mount/populate /dev with perms set to 660.

How could it be fixed?

Could anyone explain (overview) how the kernel populates and set 
permissions in /dev ?




There is a HTML file in the udev source, 
docs/writing_udev_rules/index.html which explains it quite well. It 
looks like you may have forgotten to copy udev-config-3.rules to 
/etc/udev/rules.d/25-lfs.rules so all the nodes in /dev are being 
created with the default permissions, 660


Thank you,
I will read the HTML file, Printing it now.
Yes indeed I did not copy the rules filesOpps :-[
Copying the file did indeed correct my problem.
Now on to BLFS O:-)
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

find error

[baho-utot]

I get this error when I run find:
find  Hard link count is wrong for /proc
filesystem driver may have bug

Anyone know anything about that?

Thanks
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: Chapter 8:Host system Booting Problem

[baho-utot]

[EMAIL PROTECTED] wrote:

We have completed upto chapter8

and have booted the LFS system,
But we cannot boot  the Base system,

The base system we had  used was RedhatEnterpriseLinux4

Our Menu.lst file reads

#LFS Entry
title LFS6.2
root(hd0,3)
kernel /boot/lfskernel-2.6.16.27 root=/dev/hda4

#Host system
title RHEL4
root(hd0,1)
kernel /boot/vmlinuz-2.6.9-5 ro root=LABEL =/ rhgb quiet
initrd /boot/initrd-2.6.9-5.EL.img



But In the GRUB menu when we select
the base system

We get
Error 15: Which is FileNot Found...


We have even tried the syntax given in the book,
But that doesnotseem towork and my host system is now not available foruse...

please help..

Sincerely,
Rahul Rege..

  

Grub can not find /boot/vmlinuz-2.6.9-5.

Try changing the "root=LABEL =/" to root=/dev/hdaX where X is the partition 
that RHEL4 resides.

In my case I had a separate boot partition and I needed to change 
/boot/vmlinuz-2.6.9-5 to /vmlinuz-2.6.9-5.


--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: Useradd

[baho-utot]

Geoffrey Thomas wrote:
After a few keyboard issues, I now have a LFS system that boots 
without problems.
I can login as root and cruise through directories and use basic 
commands.
When I add a user with useradd, all the info goes into the 
/etc/password and /etc/shadow files
When I try to login to the new user, I get the message /bin/bash 
Permission denied.

I check /bin/bash permissions.
The file is owned by root (group -root) and the permissions are 755.
Any ideas?
Geoff


Did you set the password by using
passwd  ?

--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: SATA

[Baho Utot]

On Wednesday 27 June 2007 8:09 pm, Chris Staub wrote:
> Baho Utot wrote:
> > I have just finished installing LFS-6.2 jhalfs build on my notebook a
> > DELL INSPERION 1501.  It has a SATA hard drive controller.  The
> > motherboard is some kind of ATI board from dmesg and from the sys.log.
> >
> > I am currently booting LFS using all-generic-ide on the grub "kernel
> > line" and I want to change it to SATA.
> >
> > Does LFS support SATA out of the box?
>
> The kernel has a number of SATA drivers. Just select the one that
> matches your hardware.

I think I need to enable libata but I can not find where to enable it.  From 
what I can determine it is under SCSI but I have not found it.

>From what I can determine:
It also appears that the kernel does not have a driver specifically for the 
hardware on the notebook.   I have FC6 installed and it seems to use libata  
as determined by lsmod.  From lspci -v on FC6 gives me a SATA controller ATI 
Technologies Inc SB600 Non-Raid SATA.


I also see from the sys.log that I have some other "kernel" issues as the 
sound hardware is not found and some other PCI devices failed initialization.
I am currently looking into this.  It is  ATI Tech. SB600 Azalia.

On a more positive note, LFS runs really fast on the AMD x2 TL-50,  top 
reports 0.3% cpu utilization on CPU 1 and 0% on the other (system idle is 
99.7 and 100% and CPU 1 reports 100% idle on some of the "top scans").  I 
think it will be a fast system :)
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Configure: error: cannot compute sizeof (long double)

[Baho Utot]

I  started a build of LFS-6.2 under a LFS-6.2 host.  I want to create a dual 
boot system, one for a server and the second for a desktop system.  I have 
the first (server system) complete and had started on the desktop build.  The 
system only has a single LFS system on it presently.  The build has been 
successful until Chapter 6.  

At Chapter 6.9 Glibc-2.3.6 I get the following error when on the configuring 
glibc step: 
checking sizeof long double... configure: error: cannot compute sizeof (long 
double), 77

I have searched the archive and google and according to those sources it is a 
version problem or I am missing libc.so.6 in the /tools/lib directory.  I do 
have libc.so.6 link to libc.2.3.6.so.

Does anyone have any more insight into this error?

Thanks
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: Configure: error: cannot compute sizeof (long double)

[Baho Utot]

On Sunday 15 July 2007 10:14 am, Ken Moffat wrote:
> On Sun, Jul 15, 2007 at 09:28:23AM -0400, Baho Utot wrote:
> > At Chapter 6.9 Glibc-2.3.6 I get the following error when on the
> > configuring glibc step:
> > checking sizeof long double... configure: error: cannot compute sizeof
> > (long double), 77
> >
> > I have searched the archive and google and according to those sources it
> > is a version problem or I am missing libc.so.6 in the /tools/lib
> > directory.  I do have libc.so.6 link to libc.2.3.6.so.
> >
> > Does anyone have any more insight into this error?
>
>  Look for config.log (with glibc, you might have several of these in
> different subdirectories), find the error message, and look at the
> lines around it (probably, up to 40 lines above it) to see what
> error was reported by the test program.
>

It is hard to parse the config.log in glibc-build directory.  It is the only 
file there, there are no others.  I would like to know how the test for long 
double works.

The only thing I see missing is configure looking for crt1.so and Scrt1.so.
Those are in /tools/lib.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: Configure: error: cannot compute sizeof (long double)

[Baho Utot]

On Sunday 15 July 2007 4:06 pm, Ken Moffat wrote:
> On Sun, Jul 15, 2007 at 02:09:51PM -0400, Baho Utot wrote:
> > It is hard to parse the config.log in glibc-build directory.
>
>  Yes, but it is essential.  The last part of it is a dump of all the
> variables, which you can probably ignore.  Before that, each test in
> the configure script typically generates something to say what is
> running, some code which you will see, and then command(s) to check
> the result, plus the output including errors, and the one-liner that
> appears on the screen.
>
> >  It is the only
> > file there, there are no others.  I would like to know how the test for
> > long double works.:u
>
>  Mostly, configure generates some code (you can see it in config.log)
> - it will be near the error message.  In this case the code is
> probably just a call to sizeof(long double).  Configure then ompiles
> the code and tries to run it.  Sizeof uses glibc,  and compiling
> uses gcc.  If it works, you would get a result of something like 12
> or 16 (the number of bytes meeded to hold a long double - it varies
> across different architectures).
>
> > The only thing I see missing is configure looking for crt1.so and
> > Scrt1.so. Those are in /tools/lib.
>
>  When a test works as expected, it often fails because something is
> not present on a particular platform.  In your case, there is a real
> problem.  You are getting some sort of error message (crt1.so ? is
> that a typo for crt1.o ?) - please tell the list what it says.

Yes it was a typo it was crt1.o and Scrt1.o 
What is it for?

I did some C programming many years ago on the doze platform and have some 
code in Bob Stouts "snippets" I just need to figure out how gcc and company 
works on Linux :)

>
>  It looks as if glibc is broken, so from here, I _guess_ that
> either you went wrong when adjusting the toolchain, or you missed
> one of the symlinks, or perhaps you built in stages and something
> is linked agaisnt the host's libraries.

Ok, I am going to remake the "tools"  using "cut, paste and run" from the 
book.  Then I will try again.

>
>  Start by checking each of the symlinks (does the link exists, is it
> the right name, does it point to the right destination (beware of
> typos), and does the file it points to exist).  After that, run
> 'readelf -l' against example programs to make sure they are linked
> against /tools.
>

I did check the symlinks and they were right as far as I could tell :)
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

http://www.linuxfromscratch.org/hints/downloads/files/fakeroot.txt

[Baho Utot]

The link in the following section is broken:

Hopefully, now you are convinced that the fakeroot approach is the right
approach for you. So lets get down to the details on how to achieve this.
Since it is impossible to include instructions for all the packages in LFS and
BLFS, I will go through some common ways to install packages into fakeroot. If
you get stuck in a particular package:
* Check out my build scripts at
  
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: Diffutils chapter 5 make install error

[Baho Utot]

On Sunday 19 August 2007 7:58:50 pm Peter Santimauro wrote:
> I am working on building the LFS system, I am currently installing
> diffutils in 5.17.   I ran the ./configure ... , make, and make
> install.  Make install finishes with an error, saying that it cannot
> create regular file  /usr/local/bin/cmp, .../bin/diff, .../bin/diff3.
> ../bin/sdiff, Permission denied.
>
> Does anyone know why I could get this error?  

You are trying to install diffutils to the host system. The lfs user doesn't 
have permissions to install there, that is what brings the error.  It would 
be an error to install 5.17 Diffutils there,  it should go 
into /mnt/lfs/tools.

> Did i mess something up 
> earlyer?  I dont want to move on until i resolve this issue, because
> this it like my 6th attempt to build LFS.
>

Did you use for the --> ./configure --prefix=/tools


> Also I am using the LFS live cd for the build.
>
> thanks
> pete


-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Re: 18 hours and counting ... gcc pass 1

[Baho Utot]

On Friday 31 August 2007 2:59 am, J. Greenlees wrote:
> Yup, 18 hours and counting for 'make bootstrap' of gcc 4.1.2
>
> host is lfs livecd r2032
> target:
> Dell inspiron 3000, a pentium-mmx @266 MHz (i586-linux-gnu)
> ram 128 MB ( system reports 144 MB from onboard cache ram for bios and
> video )
> swap space is 571.44 MB [ no more out of pages errors ]
> hda is a total of 3 GB.
>
> has anyone else ever had this length of time taken for gcc pass 1?
> No errors yet, just no activity from gcc in the last 9 hours.
>
>
> Jaqui

Using the live cd and building LFS 6.2 using jhalfs 2.3 it takes a little less 
than 24 hours to complete the entire build on my DELL dimension 300. 
Pentium II 300 with 256MB RAM, I have the SWAP set at 1024MB . If I remember 
correctly to do the pass 1 of gcc took about 229 minutes, a little less than 
4 hours.  Glibc took 549 minutes.  I can check the logs later if you really 
need the exact times.

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page