Re:
Mike McCarty schrieb: [...] > is used to encode the 8 bit character with hex code xx. > Since 0x3D is the code for "=", then "=3D" is the code > for "=". These substitutions are sometimes made by mailers > or even by machines in between. ... which teaches us: "don't copy/paste code snippets from emails" ;) BTW, Mike, I like your signature, and it works, so no mailer got between that. I know a guy who has a 1-liner rot13 implementation in his email signature :) Cheers, Jan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: lose data on shutdown?
Aleksandar Kuktin wrote:
[...]
> But make sure you do it properly - if your script is like this:
>
> # Begin my_script.sh
> export LFS=/mnt/lfs
> export FOO="blabla"
>
> Then simle `bash my_script.sh' won't help becouse the bash you just
> ordered will fork a totally new process which will run my_script.sh, set
> its own enviroment and then die. You should do: `source my_script.sh'.
What I usually do is
# mount /dev/device /mnt/someplace
# cd /mnt/someplace
# ./restart_script
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I speak only for myself, and I am unanimous in that!
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: Booting problems again
Bruce Dubbs wrote:
[...]
> IMO, 750G is way too big for an LFS partition. I store my BLFS sources
> on /usr/src which is a separate partition (50G, 50% full) and of course
> /home and /boot (100M) are separate so I can share them across multiple
> builds. Some people have /tmp and /opt as separate partitions too.
>
> I've been using the same main system since 2005. I have my LFS
> partition 8G (70% full) and really haven't had much problem with that.
> It does have most of BLFS built, but most of the bigger packages (kde,
> qt, mysql, gnome, etc) go on /opt (20G, 40% full).
>
> Multiple partitions give a lot more flexibility. I make my newer LFS
> partitions 10G.
This is great information. While the info in the book is great,
and will build a "working" system, that is, one which can boot,
there is not much hand holding when it comes to how to set up
partitions, recommended minimum sizes, etc.
Ongoing system maintenance has a plethora of solutions, I'm sure,
but some suggestions, along with the considerations which entered
in behind them, would be very nice to have.
When I do a backup, I like to reboot to single user mode,
unmount all file systems and do fscks on them first, then
remount them ro. Of course, one cannot unmount /, so it simply
has to be remounted ro and checked. Only the partition destined
to hold the actual backup data gets mounted rw, and is not
part of the data which gets backed up, though it does get
checked before it gets mounted.
I have separate partitions for / (which contains the distro
maintained files), /usr/local (which contains the stuff I
install, and some of which is not under the control of the
package manager, though I've packaged up some of it), and
/home (for user data). The backup destination is on an external
USB hard disc. After the backup, I reboot to multiuser mode,
and split up the gzipped tarball on the external drive and
write the pieces to DVDs. I use a little script yackup
(search the web, it's around) which does this very nicely.
I think that a general maintenace helper guide, or even a
section in the book relating to that, giving considerations
which enter into philosophy of maintenance and how to go
about keeping a (B)LFS system up and running, like doing
upgrades without having to destroy the system or create
a new one or buy a new disc, would be very helpful to sysadmin
newbies like me.
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I speak only for myself, and I am unanimous in that!
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: Booting problems again
On Sat, Feb 13, 2010 at 2:21 PM, Mike McCarty wrote: > Bruce Dubbs wrote: > > [...] > >> IMO, 750G is way too big for an LFS partition. I store my BLFS sources >> on /usr/src which is a separate partition (50G, 50% full) and of course >> /home and /boot (100M) are separate so I can share them across multiple >> builds. Some people have /tmp and /opt as separate partitions too. >> >> I've been using the same main system since 2005. I have my LFS >> partition 8G (70% full) and really haven't had much problem with that. >> It does have most of BLFS built, but most of the bigger packages (kde, >> qt, mysql, gnome, etc) go on /opt (20G, 40% full). >> >> Multiple partitions give a lot more flexibility. I make my newer LFS >> partitions 10G. > > This is great information. While the info in the book is great, > and will build a "working" system, that is, one which can boot, > there is not much hand holding when it comes to how to set up > partitions, recommended minimum sizes, etc. > > Ongoing system maintenance has a plethora of solutions, I'm sure, > but some suggestions, along with the considerations which entered > in behind them, would be very nice to have. > > When I do a backup, I like to reboot to single user mode, > unmount all file systems and do fscks on them first, then > remount them ro. Of course, one cannot unmount /, so it simply > has to be remounted ro and checked. Only the partition destined > to hold the actual backup data gets mounted rw, and is not > part of the data which gets backed up, though it does get > checked before it gets mounted. > > I have separate partitions for / (which contains the distro > maintained files), /usr/local (which contains the stuff I > install, and some of which is not under the control of the > package manager, though I've packaged up some of it), and > /home (for user data). The backup destination is on an external > USB hard disc. After the backup, I reboot to multiuser mode, > and split up the gzipped tarball on the external drive and > write the pieces to DVDs. I use a little script yackup > (search the web, it's around) which does this very nicely. > > I think that a general maintenace helper guide, or even a > section in the book relating to that, giving considerations > which enter into philosophy of maintenance and how to go > about keeping a (B)LFS system up and running, like doing > upgrades without having to destroy the system or create > a new one or buy a new disc, would be very helpful to sysadmin > newbies like me. Mike, you already have a good start on what could be a useful hint. Go ahead, massage it and submit it to the devs for consideration. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Booting problems again
stosss wrote:
> On Sat, Feb 13, 2010 at 2:21 PM, Mike McCarty
> wrote:
[...]
>> I think that a general maintenace helper guide, or even a
>> section in the book relating to that, giving considerations
>> which enter into philosophy of maintenance and how to go
>> about keeping a (B)LFS system up and running, like doing
>> upgrades without having to destroy the system or create
>> a new one or buy a new disc, would be very helpful to sysadmin
>> newbies like me.
>
> Mike, you already have a good start on what could be a useful hint. Go
> ahead, massage it and submit it to the devs for consideration.
Did you read that last sentence? I've been "maintaining" a Linux
system for about four or five years, but by no means does
that mean that I consider myself anything but a newbie. I took
more or less the default partitioning my distro did upon install.
As the years go by, I've wanted to add more discs space, and
done so, and so there came natural decision points about how
to add them. Some of the decisions I've made, I've later come
to reconsider, and think that there could be better ways to do
them. That doesn't meant that I think I have any sort of handle
on how they "should" be done, based on what considerations.
I have studied the recommended layout (I can't recall what it's
called, now)
/tmpvariable stuff which does not have to survive reboot
/varvariable stuff stored by games, backup programs, etc.
which must survive reboot, but not necessarily present
immediately
/binsystem program files, must be present to boot
/sbin system program files, usually used only by root,
must be present to boot
/usr/binsystem program files, not necessary for boot
/usr/sbin system program files, usually used only by
root, not necessary for boot
/etcsystem configuration data, must be present to boot
/home user data (used to be under /usr)
/usr/local/bin user installed programs
/usr/local/... user installed config stuff
The stuff marked "must be present to boot" means it
must be part of the base partition, not something mounted
later. So, these are considerations for where to add new
partitions. Like, /var, /tmp, /usr/local, /home are all
good candidates for being separate partitions. I like
for /tmp to be in a separate partition from /home, so
a user program which fills up /home/some-user/... doesn't
make /tmp also full, causing a system halt.
However, by no means do I consider myself any kind of expert.
What I just wrote is about the limit of all I know. It would
be nice if some who have professionally admin'd some UNIX
systems could write some stuff which would be meaningful.
Not the drivel I can come up with.
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I speak only for myself, and I am unanimous in that!
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: Booting problems again
Mike McCarty schrieb: [...] > I have studied the recommended layout (I can't recall what it's > called, now) Maybe FHS? http://www.pathname.com/fhs/ Cheers, Jan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Booting problems again
Jan-Christoph Bornschlegel wrote:
> Mike McCarty schrieb:
> [...]
>> I have studied the recommended layout (I can't recall what it's
>> called, now)
>
> Maybe FHS?
> http://www.pathname.com/fhs/
Yes, that's it!
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
Oppose globalization and One World Governments like the UN.
This message made from 100% recycled bits.
You have found the bank of Larn.
I speak only for myself, and I am unanimous in that!
--
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
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: Booting problems again
On Sat, 2010-02-13 at 14:04 -0600, Mike McCarty wrote: > partitions. Like, /var, /tmp, /usr/local, /home are all > good candidates for being separate partitions. I like > for /tmp to be in a separate partition from /home, so > a user program which fills up /home/some-user/... doesn't > make /tmp also full, causing a system halt. With a by-the-book LFS setup, /tmp is a tmpfs mount - an in-memory filesystem that's thrown away on shutdown/reboot. Simon. signature.asc Description: This is a digitally signed message part -- 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
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. signature.asc Description: This is a digitally signed message part -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Help compiling Gcc (chap. 5.5)
Hello, First, thanks for creating this project. I have been looking for something like this for some time now. I am eager to show people this project once I get this to work for myself. * I am using version 6.5 of the book * All the software packages used are exact MD5SUM matches as in the book. * I am preparing this on a 32-bit i686 machine, hosted with Debian Lenny. * I have followed the instructions exactly as stated. * Step 5.4.1 was completed successfully. I unpacked mpfr and gmp and then created gcc-build to build gcc in. When I try to 'configure' before compiling, it fails because "Building GCC requires GMP 4.1+ and MPFR 2.3.2+". This is consistent with what I read in Chapter 5.5.1, but I am not told what is to be done about it. I moved the mpfr and gmp directories to gcc-build, and it still didn't see the files. Should I compile them first? It never told me to do that though. Or maybe it is because I might have been in the wrong directory. You see the path here in this line is relative to the path given by 'pwd'. tar -jxf ../mpfr-2.4.1.tar.bz2 I was never told which directory I was supposed to be in when I executed this, but it might have been incorrect. I am looking for ideas. It has been over 10 years since I have done this. Tim Legg -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: Help compiling Gcc (chap. 5.5)
Hi, On Saturday 13 February 2010 22:06:20 Timothy Legg wrote: >tar -jxf ../mpfr-2.4.1.tar.bz2 > > I was never told which directory I was supposed to be in when I executed > this, but it might have been incorrect. > There's a note about this in: /lfs-6.5-book/chapter05/generalinstructions.html But basically, you want the mpfr and gmp sources in the gcc source directory so that they can be built by/with gcc. -- Regards, Trent. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
