Estevao B. K. | 1 Oct 2010 03:21
Picon

Re: "auto" in /etc/fstab

On 09/30/2010 07:52 PM, Mark Knecht wrote:
> On Thu, Sep 30, 2010 at 2:18 PM,<rhubarbpie <at> poetworld.net>  wrote:
>>
>> Is there a disadvantage of using auto for file system type in the
>> /etc/fstab file?  I have three non-swap partitions.  Why not list them
>> all as auto?

That's a good question... But since all the filesystem partitions that I 
use for most of my Linux systems are ext3, the potential risks overcome 
any benefit.

One thing that I use, though, is the argument LABEL instead of UUID or 
the absolute path for a partition. It gives flexibility and assures me 
that even if I change my disks order, I will not have to worry about it.

Most popular distros use UUID, but this changes every time you 
re-format. Label too, but it's much more simple to format as 
LABEL=LFS-HOME e.g. than re-specify the very long UUID number that your 
partition had.
--

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

Simon Geard | 1 Oct 2010 10:37
Picon

Re: "auto" in /etc/fstab

On Thu, 2010-09-30 at 16:18 -0500, rhubarbpie <at> poetworld.net wrote:
> Is there a disadvantage of using auto for file system type in the 
> /etc/fstab file?  I have three non-swap partitions.  Why not list them 
> all as auto?

I may be wrong, but I *think* auto works only for filesystems that are
registered at the time you try to mount them - in other words, if your
filesystem support is built as a loadable module, it may not work. I
remember having issues of this kind while playing with initramfs support
ages ago...

Simon.
--

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Simon Geard | 1 Oct 2010 10:50
Picon

Re: LFS Init scripts?

On Thu, 2010-09-30 at 13:32 -0700, Mark Knecht wrote:
> Am I fooling myself in thinking that for a very simple hardware
> system, maybe just an EXT2 boot, EXT3 / and a swap partition, that for
> this specific machine the init scripts might be reduced to something
> like 10-20 bash commands which get me to the bash command line where
> as root I could use the system?

Yeah, could be. Look at what the scripts in /etc/rc.d/rcsysinit.d are
doing, but the minimal list is going to look something like -

* mount /proc and /sys
* start udev to populate /dev (see /etc/rc.d/init.d/udev)
* remount / read-write (kernel mounts it read-only before init starts)
* start swap
* bring up localhost network

There's other stuff done by LFS, but I think that list is probably
enough to get you to a bash prompt. Actually, the last two aren't
critical for boot either, but you likely want them anyway...

Simon.
--

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Neal Murphy | 2 Oct 2010 06:01
Favicon

Re: LFS Init scripts?

On Thursday 30 September 2010 16:32:09 Mark Knecht wrote:
> Am I fooling myself in thinking that for a very simple hardware
> system, maybe just an EXT2 boot, EXT3 / and a swap partition, that for
> this specific machine the init scripts might be reduced to something
> like 10-20 bash commands which get me to the bash command line where
> as root I could use the system?

I's'll have to review the links posted earlier. When I was upgrading 
Smoothwall to use udev and initramfs, I didn't find much of anything of any 
use to guide me, so I puzzled my way through it, brute force.

The simplest method of getting a root shell is to:

------------------
cat <<END >/init
#! /bin/sh

bash </dev/tty1 >/dev/tty1 2>/dev/tty1

END

chmod +x /init
-------------------

But this might not give you job control (it definitely won't in early 
userspace), and you won't have any daemons started (udev, etc.) This is how I 
started on my trek to set up initramfs (the official Smoothwall still uses 
initrd). It was a journey of 3-4 months slogging through the bog of early 
userspace, getting mired in how to properly create an initramfs to begin with 
(that bit could be documented better; there's one and only one way to do it 
(Continue reading)

zhan jianyu | 3 Oct 2010 05:01
Picon
Gravatar

mistake when compile Gcc

 hello,i got a big hassle when compile gcc .i have successfully
compiled the gmp,mpfr and mpc ,and the configure option of gcc is :

../gcc-4.5.1/configure --target=i686-lfs-linux-gnu --prefix=/tools --disable
-nls --disable-shared --disable-multilib --disable-decimal-float --disable-threa
ds --disable-libmudflap --disable-libssp --disable-libgomp --enable-languages=c
--with-gmp=/tools --with-mpfr=/tools --with-mpc=/tools --without-ppl --without-c
loog (the directory /tools point to the $LFS/tools)

when i make ,a error occured:
checking for suffix of object files... configure: error: in
`/mnt/lfs/gcc-build/i686-lfs-linux-gnu/libgcc':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.
make[1]: *** [configure-target-libgcc] Error 1
make[1]: Leaving directory `/mnt/lfs/gcc-build'
make: *** [all] Error 2

and  i check the config.log .found all the error message below:

conftest.c:10:28: error: ac_nonexistent.h: No such file or directory
conftest.c:10:28: error: ac_nonexistent.h: No such file or directory
conftest.c:53:20: error: libelf.h: No such file or directory
conftest.c:20:20: error: libelf.h: No such file or directory
conftest.c:53:18: error: gelf.h: No such file or directory
conftest.c:20:18: error: gelf.h: No such file or directory
conftest.c:53:27: error: libelf/libelf.h: No such file or directory
conftest.c:20:27: error: libelf/libelf.h: No such file or directory
conftest.c:53:25: error: libelf/gelf.h: No such file or directory
conftest.c:20:25: error: libelf/gelf.h: No such file or directory
(Continue reading)

Ken Moffat | 4 Oct 2010 02:22

Re: mistake when compile Gcc

On 03/10/2010, zhan jianyu <nasa4836 <at> gmail.com> wrote:

>
> when i make ,a error occured:
> checking for suffix of object files... configure: error: in
> `/mnt/lfs/gcc-build/i686-lfs-linux-gnu/libgcc':
> configure: error: cannot compute suffix of object files: cannot compile
> See `config.log' for more details.
> make[1]: *** [configure-target-libgcc] Error 1
> make[1]: Leaving directory `/mnt/lfs/gcc-build'
> make: *** [all] Error 2
>

 With gcc and binutils, there are several 'config.log' files in
different subdirectories.
Use 'find' and 'ls -l' to identify which is the newest, and then look
at that instead of the top-level config.log.

> i have googled but not found solution . i doubt whether the packet
> needs a patch? eh...i don't really konw.i'm trying out the lfs project
> .
 And now, I get a chance to put on my pedant's hat!  The normal
english work is 'package', not 'packet' [ a packet is what we send in
the post or using TCP/IP ], despite the efforts of german-speakers to
persuade us otherwise ;-)

ĸen
-- 
After tragedy, and farce, "OMG poneys!"
--

-- 
(Continue reading)

Felice Murolo | 9 Oct 2010 09:46

SVN 20100923 - gcc-4.5.1, pass 1, won't compile

 this isn't the first time I make a linuxfromscratch installation. Other
 times, I've successfully created servers and desktop PC in this manner.

 After about two years, I've start a new LFS installation. The host machine
 where I have started LFS have KUBUNTU 10.04, updated with all recent
 packets from Ubuntu. I've start the new LFS system in a clear ext4
 partition.

 No problem with binutils (chap 5.4). When I compile GCC, something goes
 wrong.

 I decompress gcc-4.5.1.tar.bz2, I go into directory and decompress and
 rename mpfr, mpc and gmp. Then I create build directory, go in this
 directory and run the configure command as described in book. All works
 fine, so I run make. Afer abount 20 minutes of compilation, something goes
 wrong and compilation stops. The error is the attached error.log file.

 The config.log of the directory "/home/lfs/src/gcc-build/i686-lfs-linux-
 gnu/libgcc" is the attached config.log file.

 Any ideas?

Attachment (error.log): text/x-log, 613 bytes
Attachment (config.log): text/x-log, 9 KiB
--

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

Andrew Benton | 9 Oct 2010 13:23
Picon

Re: SVN 20100923 - gcc-4.5.1, pass 1, won't compile

On Sat, 9 Oct 2010 09:46:40 +0200
Felice Murolo <linuxboy <at> fel.hopto.org> wrote:

>  The config.log of the directory "/home/lfs/src/gcc-build/i686-lfs-linux-
>  gnu/libgcc" is the attached config.log file.
> 
>  Any ideas?
> 
The bit that looks odd to me is this:

configure:3020: /home/lfs/src/gcc-build/./gcc/xgcc -B/home/lfs/src/gcc-build/./gcc/
-B/tools/i686-lfs-linux-gnu/bin/ -B/tools/i686-lfs-linux-gnu/lib/ -isystem
/tools/i686-lfs-linux-gnu/include -isystem /tools/i686-lfs-linux-gnu/sys-include    -o conftest
-g -O2   conftest.c  >&5
exec: 85: : Permission denied
configure:3023: $? = 1
configure:3211: checking for suffix of object files
configure:3233: /home/lfs/src/gcc-build/./gcc/xgcc -B/home/lfs/src/gcc-build/./gcc/
-B/tools/i686-lfs-linux-gnu/bin/ -B/tools/i686-lfs-linux-gnu/lib/ -isystem
/tools/i686-lfs-linux-gnu/include -isystem /tools/i686-lfs-linux-gnu/sys-include    -c -g -O2 
conftest.c >&5
exec: 85: : Permission denied

Permission denied suggests that something strange is going on. It looks
like it's trying to execute the xgcc compiled in the first pass. 
I would suggest that you try compiling lfs on a separate partition
mounted at /mnt/lfs.

As it's a version of Ubunut, could we see the output of
version-check.sh please?
(Continue reading)

Felice Murolo | 9 Oct 2010 13:58

Re: SVN 20100923 - gcc-4.5.1, pass 1, won't compile

In data sabato 9 ottobre 2010 13:23:04, Andrew Benton ha scritto:
: > On Sat, 9 Oct 2010 09:46:40 +0200
> 
> Felice Murolo <linuxboy <at> fel.hopto.org> wrote:
> >  The config.log of the directory "/home/lfs/src/gcc-build/i686-lfs-linux-
> >  gnu/libgcc" is the attached config.log file.
> >  
> >  Any ideas?
> 
> The bit that looks odd to me is this:

as my previous reply to myself, please ignore this thread.  I've started a new 
and clean installation of LFS and the compilation error is gone.

> As it's a version of Ubunut, could we see the output of
> version-check.sh please?
> http://www.linuxfromscratch.org/lfs/view/development/prologue/hostreqs.html

only for statistics:

bash, version 4.1.5(1)-release
/bin/sh -> /bin/dash
Binutils: (GNU Binutils for Ubuntu) 2.20.1-system.20100303
bison (GNU Bison) 2.4.1
/usr/bin/yacc -> /usr/bin/bison.yacc
bzip2,  Version 1.0.5, 10-Dec-2007.
Coreutils:  7.4
diff (GNU diffutils) 2.8.1
find (GNU findutils) 4.4.2
GNU Awk 3.1.6
(Continue reading)

David Henry | 9 Oct 2010 19:51
Picon

Re: Perl Compilation Failure

I sent the email below on Friday when I was not a  member of the mailing list so I don't know if anyone has replied. I'm re-posting it now so I can see the replies. Sorry for the duplication.

On Fri, Oct 8, 2010 at 10:22 AM, David Henry <davermont <at> gmail.com> wrote:
I'm using version 6.7 of LFS with Ubuntu 10.4 as the host. Right now I'm stuck on section 5.28 Perl-5.12.1. I've untar'd Perl, patched it successfully and run:

sh Configure -des -Dprefix=/tools -Dstatic_ext='Data/Dumper Fcntl IO POSIX'

make perl utilities ext/Errno/pm_to_blib

The result is a build failure with the following output:

Running Makefile.PL in ext/POSIX
../../miniperl Makefile.PL INSTALLDIRS=perl INSTALLMAN1DIR=none INSTALLMAN3DIR=none PERL_CORE=1 LIBPERL_A=libperl.a LINKTYPE=static CCCDLFLAGS=
Can't locate Cwd.pm in <at> INC ( <at> INC contains: ../../lib) at ../../lib/File/Path.pm line 6.
BEGIN failed--compilation aborted at ../../lib/File/Path.pm line 6.
Compilation failed in require at ../../lib/ExtUtils/MakeMaker.pm line 11.
BEGIN failed--compilation aborted at ../../lib/ExtUtils/MakeMaker.pm line 11.
Compilation failed in require at Makefile.PL line 5.
BEGIN failed--compilation aborted at Makefile.PL line 5.
512 from ext/POSIX's Makefile.PL at make_ext.pl line 390.
Warning: No Makefile!
make[1]: Entering directory `/mnt/lfs/sources/perl-5.12.1/ext/POSIX'
make[1]: *** No rule to make target `config'.  Stop.
make[1]: Leaving directory `/mnt/lfs/sources/perl-5.12.1/ext/POSIX'
 make config PERL_CORE=1 LIBPERL_A=libperl.a LINKTYPE=static CCCDLFLAGS= failed, continuing anyway...
Making all in ext/POSIX
 make all PERL_CORE=1 LIBPERL_A=libperl.a LINKTYPE=static CCCDLFLAGS=
make[1]: Entering directory `/mnt/lfs/sources/perl-5.12.1/ext/POSIX'
make[1]: *** No rule to make target `all'.  Stop.
make[1]: Leaving directory `/mnt/lfs/sources/perl-5.12.1/ext/POSIX'
Unsuccessful make(ext/POSIX): code=512 at make_ext.pl line 449.
make: *** [lib/auto/POSIX/POSIX.a] Error 2

Can anyone offer some advice here? I've searched the mail archives and I found one email related to this; the solution proposed was to omit the -Dstatic_ext flag. I tried this to no avail.

Thanks,
Dave H.

--

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

Gmane