headers
Dan McGhee | 1 Jan 2011 16:04
Favicon

Editorial Question on Chapter 7.4 of LFS-6.7

I'm just reacting to "the way things used to be."  The title of Chapter 
7.4 is "Configuring the setclock Script."  The file created in this 
section is now named /etc/sysconfig/clock.  I'm used to having it named 
"setclock."  I couldn't find any mention of a change in the "Change 
Log."  Is this now going to be the name of this script?

Additionally, I'm not used to having anything else defined in this 
script.  So should the line

CLOCKPARAMS=

be commented out.

Thanks,
Dan
--

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Permalink | Reply | 3 comments |
headers
Dan McGhee | 1 Jan 2011 18:02
Favicon

Re: Editorial Question on Chapter 7.4 of LFS-6.7 [SOLVED]

On 01/01/2011 09:04 AM, Dan McGhee wrote:
> I'm just reacting to "the way things used to be."  The title of Chapter
> 7.4 is "Configuring the setclock Script."  The file created in this
> section is now named /etc/sysconfig/clock.  I'm used to having it named
> "setclock."  I couldn't find any mention of a change in the "Change
> Log."  Is this now going to be the name of this script?
>
> Additionally, I'm not used to having anything else defined in this
> script.  So should the line
>
> CLOCKPARAMS=
>
> be commented out.
>
>
The answer is in Appendix D. Nice addition. Thanks.

Dan
--

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Permalink | Reply | 0 comments |
headers
Andrew Benton | 1 Jan 2011 18:03
Picon

Re: Editorial Question on Chapter 7.4 of LFS-6.7

On Sat, 01 Jan 2011 09:04:40 -0600
Dan McGhee <beesnees <at> grm.net> wrote:

> I'm just reacting to "the way things used to be."  The title of Chapter 
> 7.4 is "Configuring the setclock Script."  The file created in this 
> section is now named /etc/sysconfig/clock.  I'm used to having it named 
> "setclock."  I couldn't find any mention of a change in the "Change 
> Log."  Is this now going to be the name of this script?

That file has been called clock for as long as I can remember. Perhaps
you're thinking of /etc/rc.d/init.d/setclock?

> 
> Additionally, I'm not used to having anything else defined in this 
> script.  So should the line
> 
> CLOCKPARAMS=
> 
> be commented out.

CLOCKPARAMS is not mentioned in /etc/sysconfig/clock, but it is
mentioned in /etc/rc.d/init.d/setclock. As it stands setting the
variable CLOCKPARAMS to null is safer than commenting the line out as
the variable CLOCKPARAMS may have been set in the environment for some
other use which may cause a problem for hwclock.

Andy
--

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
(Continue reading)

Permalink | Reply | 1 comment |
headers
Bavithra R | 2 Jan 2011 09:00
Picon

Using Repositories

Hi all


I am a newbie for creating distro from scratch.
Initially I started with LFS book.
Now I am in a need to use the Debian repository.
Can any one please tell me clearly how this repository is used in this process and also in what stage?
Could it be used either after finishing the LFS book or prior to it?


Thank you all in advance.

regards
--Bavithra.R

--

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Permalink | Reply | 3 comments |
headers
Andrew Benton | 2 Jan 2011 13:45
Picon

Re: Using Repositories

On Sun, 2 Jan 2011 13:30:58 +0530
Bavithra R <bavithra.r <at> gmail.com> wrote:

> Hi all
> 
> 
> I am a newbie for creating distro from scratch.
> Initially I started with LFS book.
> Now I am in a need to use the Debian repository.

Then install Debian

> Can any one please tell me clearly how this repository is used in this
> process and also in what stage?

We don't use Debian packages in LFS.

> Could it be used either after finishing the LFS book or prior to it?

No. It's sometimes possible to extract a .deb and then run the binary

ar xv some_package.deb
tar xf data.tar.gz

Andy
--

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Permalink | Reply | 1 comment |
headers
Dan McGhee | 2 Jan 2011 15:55
Favicon

Re: Editorial Question on Chapter 7.4 of LFS-6.7 [SOLVED]

On 01/01/2011 11:03 AM, Andrew Benton wrote:
> On Sat, 01 Jan 2011 09:04:40 -0600
> Dan McGhee<beesnees <at> grm.net>  wrote:
>
>> I'm just reacting to "the way things used to be."  The title of Chapter
>> 7.4 is "Configuring the setclock Script."  The file created in this
>> section is now named /etc/sysconfig/clock.  I'm used to having it named
>> "setclock."  I couldn't find any mention of a change in the "Change
>> Log."  Is this now going to be the name of this script?
> That file has been called clock for as long as I can remember. Perhaps
> you're thinking of /etc/rc.d/init.d/setclock?
>
>> Additionally, I'm not used to having anything else defined in this
>> script.  So should the line
>>
>> CLOCKPARAMS=
>>
>> be commented out.
> CLOCKPARAMS is not mentioned in /etc/sysconfig/clock, but it is
> mentioned in /etc/rc.d/init.d/setclock. As it stands setting the
> variable CLOCKPARAMS to null is safer than commenting the line out as
> the variable CLOCKPARAMS may have been set in the environment for some
> other use which may cause a problem for hwclock.
>
> Andy
My router and I were not playing nicely yesterday and my reply to my own 
questions got lost somewhere.

I found the information I needed in Appendix D, "Boot and sysconfig 
scripts version 20100627." Another well of information that I hadn't 
used before. It's a great addition to the book.

Andy, you're probably right about what I was thinking. Except for my 
very first build many years ago, I have "copied and pasted" the commands 
from the book. Soooooo.......

Dan
--

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Permalink | Reply | 0 comments |
headers
NeoAmsterdam | 2 Jan 2011 18:07
Picon

[LFS 6.7] 6.9 Glibc-2.12.1: make -k check 2>&1 | tee glibc-check-log → Target `check' not remade because of errors.

Hi, folks!  Before I begin, the obligatory preliminaries:

- LFS 6.7 (stable at time of writing, issue not covered by errata)
- AMD Athlon 64 X2 Dual-Core (Windsor BH-F2), 90nm Processor 3800+  
(Build, host, and target)
- Building from Fedora 12 (Constantine) running a 64-bit kernel  
without a GUI
- This (6.9 Glibc-2.12.1) is the first warning and/or error I've had  
all build
- It happens regardless of optimization and/or parallel v. normal make
- And Google may be a friend, but it's not a particularly helpful one

Everything's building fine and dandy until Glibc in chapter 6: ``make - 
k check 2>&1 | tee glibc-check-log`` always ends up with the following  
error:

	make[1]: Target `check' not remade because of errors.
	make[1]: Leaving directory `/sources/glibc-2.12.1'
	make: *** [check] Error 2

I knew to expect an error or two here, but since Glibc's tests are  
critical and since there wasn't even so much as a warning leading up  
to this point... well, you know.

Here's what ``grep Error glibc-check-log`` had to say:

	make[2]: *** [/sources/glibc-build/posix/tst-waitid.out] Error 1
	make[2]: [/sources/glibc-build/posix/annexc.out] Error 1 (ignored)
	make[1]: *** [posix/tests] Error 2
	make[2]: *** [/sources/glibc-build/nptl/tst-rwlock6.out] Error 1
	make[2]: *** [/sources/glibc-build/nptl/tst-rwlock7.out] Error 1
	make[2]: *** [/sources/glibc-build/nptl/tst-rwlock9.out] Error 1
	make[2]: *** [/sources/glibc-build/nptl/tst-rwlock11.out] Error 1
	make[2]: *** [/sources/glibc-build/nptl/tst-rwlock12.out] Error 139
	make[2]: *** [/sources/glibc-build/nptl/tst-rwlock14.out] Error 1
	make[1]: *** [nptl/tests] Error 2
	make[2]: *** [/sources/glibc-build/rt/tst-cpuclock2.out] Error 1
	make[1]: *** [rt/tests] Error 2
	make[2]: *** [/sources/glibc-build/elf/tst-xmmymm.out] Error 1
	make[1]: *** [elf/tests] Error 2
	make: *** [check] Error 2

Eyeballing `glibc-check-log` itself didn't reveal any clues to me -  
nothing looked out of the ordinary.  And considering that the `make  
check` seems to have exited gracefully, I'm leaning towards the  
assumption that error 1 is an ignorable "oops".

Still, what is error 139 and why would `nptl/tst-rwlock12` be the only  
test throwing that exception?  Can these errors be ignored, or do they  
suggest a bad build somewhere in Chap. 5 and that I've overlooked it?

Thanks for the help (and Happy New Year)
	______    ______
	\_(_)_\  /_(_)_/

--

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Permalink | Reply | 2 comments |
headers
Rosario Turco | 2 Jan 2011 19:05
Picon
Favicon

LFS grub start error

 created a virtual machine with Fedora 14 guest host a filesystem with no errors
everything is set up in LFS 6.7 Chapter 9. Kernel is ok.

When I mount the new virtual machine obtained LFS, I get errors because I did
not understand how to configure fstab and grub.cfg

For LFS I have created these partitions on virtual machine:
/boot  /dev/sdb1
/home  /dev/sdb2
/swap  /dev/sdb3
/LFS   /dev/sdb4

My actual /etc/fstab  is:

# Begin /etc/fstab
# file system mount-point type options dump fsck
# order
/dev/sdb1 /boot ext3 defaults 1 1
/dev/sdb3 /home ext3 defaults 1 1
/dev/sdb4 / ext3 defaults 1 1
/dev/sdb2 swap swap pri=1 0 0
proc /proc proc 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
none /proc/bus/usb usbfs devgid=46,devmode=664 0 0
# End /etc/fstab

My /boot/grub/grub.cfg is:
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
  set saved_entry=${prev_saved_entry}
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z ${boot_once} ]; then
    saved_entry=${chosen}
"/boot/grub/grub.cfg" [readonly] 60L, 1772C
    save_env saved_entry
  fi
}
insmod ext2
set root='(hd1,4)'
search --no-floppy --fs-uuid --set c544afb8-6417-4d14-89e0-5aa35173c3c3
set locale_dir=($root)/boot/grub/locale
set lang=
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry "GNU/Linux, with Linux 2.6.36-lfs-6.7" --class gnu-linux --class gnu
--class os {
        insmod ext2
        set root='(hd1,4)'
        search --no-floppy --fs-uuid --set c544afb8-6417-4d14-89e0-5aa35173c3c3
        echo    Loading Linux 2.6.36-lfs-6.7 ...
        linux   /boot/vmlinux-2.6.36-lfs-6.7 root=/dev/sdb4 ro  
}
menuentry "GNU/Linux, with Linux 2.6.36-lfs-6.7 (recovery mode)" --class
gnu-linux --class gnu --class os {
        insmod ext2
        set root='(hd1,4)'
        search --no-floppy --fs-uuid --set c544afb8-6417-4d14-89e0-5aa35173c3c3
        echo    Loading Linux 2.6.36-lfs-6.7 ...
        linux   /boot/vmlinux-2.6.36-lfs-6.7 root=/dev/sdb4 ro single 
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

My /dev is:
brw-rw---- 1 root daemon 8, 0 Jan  2 18:31 /dev/sda
brw-rw---- 1 root daemon 8, 1 Jan  2 18:31 /dev/sda1
brw-rw---- 1 root daemon 8, 2 Jan  2 18:31 /dev/sda2
brw-rw---- 1 root daemon 8, 16 Jan  2 18:31 /dev/sdb
brw-rw---- 1 root daemon 8, 17 Jan  2 18:31 /dev/sdb1
brw-rw---- 1 root daemon 8, 18 Jan  2 18:31 /dev/sdb2
brw-rw---- 1 root daemon 8, 19 Jan  2 18:31 /dev/sdb3
brw-rw---- 1 root daemon 8, 20 Jan  2 18:31 /dev/sdb4

The error is:
VFS: cannot open root device "sdb4" or unknown block (2,0)
Please append a correct "root=" boot options; here are the available partions:

0800 sda
0801 sda1
0802 sda2
0803 sda3
0804 sda4
0b00 sr0 driver
Kernel panic: not syncing: VFS: Unable to mpunt root fs on unknown block(2,0)

--

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Permalink | Reply | 8 comments |
headers
Bruce Dubbs | 2 Jan 2011 19:30
Picon

Re: Using Repositories

Andrew Benton wrote:
> On Sun, 2 Jan 2011 13:30:58 +0530
> Bavithra R <bavithra.r <at> gmail.com> wrote:
> 
>> Hi all
>>
>>
>> I am a newbie for creating distro from scratch.
>> Initially I started with LFS book.
>> Now I am in a need to use the Debian repository.
> 
> Then install Debian
> 
>> Can any one please tell me clearly how this repository is used in this
>> process and also in what stage?
> 
> We don't use Debian packages in LFS.

Well, actually we do use some packages from debian, but not in .deb 
format.  See, for instance, shadow and BLFS.

   -- Bruce
--

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Permalink | Reply | 0 comments |
headers
Bruce Dubbs | 2 Jan 2011 19:41
Picon

Re: [LFS 6.7] 6.9 Glibc-2.12.1: make -k check 2>&1 | tee glibc-check-log ? Target `check' not remade because of errors.

NeoAmsterdam wrote:

> Here's what ``grep Error glibc-check-log`` had to say:
> 
> 	make[2]: *** [/sources/glibc-build/posix/tst-waitid.out] Error 1
> 	make[2]: [/sources/glibc-build/posix/annexc.out] Error 1 (ignored)
> 	make[1]: *** [posix/tests] Error 2
> 	make[2]: *** [/sources/glibc-build/nptl/tst-rwlock6.out] Error 1
> 	make[2]: *** [/sources/glibc-build/nptl/tst-rwlock7.out] Error 1
> 	make[2]: *** [/sources/glibc-build/nptl/tst-rwlock9.out] Error 1
> 	make[2]: *** [/sources/glibc-build/nptl/tst-rwlock11.out] Error 1
> 	make[2]: *** [/sources/glibc-build/nptl/tst-rwlock12.out] Error 139
> 	make[2]: *** [/sources/glibc-build/nptl/tst-rwlock14.out] Error 1
> 	make[1]: *** [nptl/tests] Error 2
> 	make[2]: *** [/sources/glibc-build/rt/tst-cpuclock2.out] Error 1
> 	make[1]: *** [rt/tests] Error 2
> 	make[2]: *** [/sources/glibc-build/elf/tst-xmmymm.out] Error 1
> 	make[1]: *** [elf/tests] Error 2
> 	make: *** [check] Error 2

All these errors are fairly common.  I got exactly the same ones except 
for me tst-rwlock12 gives an error 11.

Some of these are just hw dependent timeout issues.  You can safely 
ignore them.

   -- Bruce
--

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

Gmane