> Right. One solution to that which I am interested in pursuing a bit more
> is what I mentioned in alfs-discuss and what Greg Schafer has referred to
> recently in another thread: extracting the commands from the book's XML
> source.
>
> There have been others who have pursued this goal, ie, Bor
Randy McMurchy([EMAIL PROTECTED])@Tue, Aug 09, 2005 at 03:52:11PM -0500:
> Randy McMurchy wrote these words on 08/01/05 13:33 CST:
>
> I am now convinced that a branch for GCC4 in BLFS is not necessary.
> There isn't that much that is going to be changed, and maintenance
> of the branch would be a
I have a question about the pure 64bit x86_64 bit book. During the
installation of grub you use the following instruction:
CC="gcc -m32 -static" ./configure --prefix=/usr
However because this is a pure 64bit build their are no 32 bit libraries
or the capability for gcc to build 32 bit correct
> Non-Technical explanation: I actually tested fully (I believe) and it
> works!!! :-D
Well that looks better. ;) I'm still wondering, though, why: When I have a
process not running (spamd in this case), and I do a "spamd stop", it still
says, "[ OK ]". :D Shouldn't it say "/usr/bin/spamd is
> I've become rather fond on the style shown in Bruce's SBU pages:
>
> http://linuxfromscratch.org/~bdubbs/about.html
>
> it neatly gets you:
> 1) a log
> 2) the time it took recorded in the log
> 3) a deeper understanding of how the shell works :-)
Nice! :) Thanks!
Dave
--
ht
John Miller wrote:
I have a question about the pure 64bit x86_64 bit book. During the
installation of grub you use the following instruction:
CC="gcc -m32 -static" ./configure --prefix=/usr
However because this is a pure 64bit build their are no 32 bit libraries
or the capability for gcc to
David Fix wrote:
Non-Technical explanation: I actually tested fully (I believe) and it
works!!! :-D
Well that looks better. ;) I'm still wondering, though, why: When I have a
process not running (spamd in this case), and I do a "spamd stop", it still
says, "[ OK ]". :D Shouldn't it say "/
Torsten Vollmann wrote:
> Bruce Dubbs wrote:
> Just out of curiosity or lack of understaning:
>
> The fix for the missing configure command in autofs was merged into -pre2
> but I can't see it in trunk. So, from where was it merged?
My keyboard. :)
Doing a svn merge doesn't really work because
> Not now. 3.2.x went after partial LSB-2.1.0 compliancy to ease the
> transition. See below from the spec.
Ah, gotcha. :) Makes sense then. :) Thanks so much for your hard work,
DJ. :)
Dave
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratc
John Miller wrote:
I have a question about the pure 64bit x86_64 bit book. During the
installation of grub you use the following instruction:
CC="gcc -m32 -static" ./configure --prefix=/usr
However because this is a pure 64bit build their are no 32 bit
libraries or the capability for gcc to
Jim Gifford wrote:
John Miller wrote:
I have a question about the pure 64bit x86_64 bit book. During the
installation of grub you use the following instruction:
CC="gcc -m32 -static" ./configure --prefix=/usr
However because this is a pure 64bit build their are no 32 bit
libraries or the
Someone has information on how to make grub work 64 bit, I hope to get
that very soon.
--
--
[EMAIL PROTECTED]
[EMAIL PROTECTED]
LFS User # 2577
Registered Linux User # 299986
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See
Jim Gifford wrote:
Someone has information on how to make grub work 64 bit, I hope to get
that very soon.
Would you like to give grub-1.90 (grub-2.0 pre-release) a try for us all? :)
Matt.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsub
Sure, I'll give it a shot.
--
--
[EMAIL PROTECTED]
[EMAIL PROTECTED]
LFS User # 2577
Registered Linux User # 299986
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Seth Payne wrote:
chroot: cannot run command `/tools/bin/env': No such file or directory
Seth,
I realise you've sorted your problem now, but I thought I'd take this
opportunity to remind folks of our FAQ page, which just happens to
answer this question and many more too.
http://www.linuxfr
Matthew Burgess wrote:
Uggh, sorry! Stupid autocomplete on Thunderbird got the wrong list!
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Matthew Burgess wrote these words on 08/10/05 11:32 CST:
> Uggh, sorry! Stupid autocomplete on Thunderbird got the wrong list!
Sure.
Actually, it was just a sneaky way to get your message sent to another
list. :-)
You know, something you might consider. Several technical lists
(newsgroups)
Matthew Burgess wrote:
Would you like to give grub-1.90 (grub-2.0 pre-release) a try for us
all? :)
Interesting Note
GRUB depends on some software packages installed into your system. If
you don't have any of them, please obtain and install them before
configuring the GRUB.
* GCC 2.95 or lat
Matt,
I decided to try this on my 586 test machine. I ran into a few issues.
Issues
cannnot find /usr/sbin/grub-mkimage
Error line at 213 /usr/sbin/grub-install
Only boots into grub-rescue
Fixes
cp /usr/bin/grub-install /usr/sbin/gru
While testing the new LFS LiveCD Makefile system, I ran across some
corrupted files downloaded from anduin via ftp.lfs-matrix.net, but have
confirmed that even downloading from anduin still results in
corruption.
The following files are affected:
openssl-0.9.7g.tar.bz2
tcl-8.4.11.tar.bz2
tk-8.4.1
Looks like it will only support 32 bit also, so we may have to change to
lilo for pure 64 builds.
http://lists.gnu.org/archive/html/grub-devel/2005-08/msg00065.html
--
--
[EMAIL PROTECTED]
[EMAIL PROTECTED]
LFS User # 2577
Registered Linux User # 299986
--
http://linuxfromscratch.org/mail
Matthew Burgess wrote:
Jens Olav Nygaard wrote:
Any ideas?
Yep, I just use ntp (see BLFS). My hardware clock seems to gain even
Tried this and went for the first option mentioned in the BLFS-book:
Option one is to run ntpd continuously and allow it to
synchronize the time in a grad
I've been working on our cross-lfs build methods quite a bit lately, but
have ran into some dead ends when it comes to the bootloaders for all
the architectures we support. None of them will build properly on a Pure
64 bit system. The only way I see to get around this is to build some 32
bit to
Jim Gifford wrote:
I've been working on our cross-lfs build methods quite a bit lately,
but have ran into some dead ends when it comes to the bootloaders for
all the architectures we support. None of them will build properly on
a Pure 64 bit system. The only way I see to get around this is to
John Miller wrote:
I have only been a lurker on the list, but since I stirred up all the
trouble over bootloaders with my thread I should probably say
something. I used lilo for my pure 64 bit system and it built just
fine. Since sometime towards the end of 2004 lilo no longer requires
nasm
On Wed, Aug 10, 2005 at 07:25:27AM +0100, Richard A Downing wrote:
>
> My way now is never to type the commands directly, but create a
> scriptlet for each package built from a template that is essentially
> Bruce's script plus some checks.
And to take automation one step further, you could put B
On Wed, Aug 10, 2005 at 09:53:13AM -0500, DJ Lucas wrote:
> *
>
> running "start" on a service already running
> *
>
> running "stop" on a service already stopped or not running
That just seems silly. Warn was much nicer and still allowed things to
proceed.
--
Archaic
Want
On Wed, Aug 10, 2005 at 02:57:31PM -0700, Jim Gifford wrote:
>
> I was having this problem for a while, I've been working with the Silo
> maintainer for a few weeks now, but there is no way to build a 64 bit
> silo. Colo for the raq2 MIPS and Grub, also seem to have this problem. I
> guess a 32
Jim Gifford wrote:
I was having this problem for a while, I've been working with the Silo
maintainer for a few weeks now, but there is no way to build a 64 bit
silo. Colo for the raq2 MIPS and Grub, also seem to have this problem.
I guess a 32 Bit loader is the unwritten law for bootloaders.
Archaic wrote:
LILO is reported to work for 64 bit. You don't seem to be acknowledging
that since all I can see is talk of silo, colo, and grub.
Actually I don't want to add any packages. I have talked to some people
that have actually built grub on a 64 bit architecture. But this still
liv
Archaic wrote:
LILO is reported to work for 64 bit. You don't seem to be acknowledging
that since all I can see is talk of silo, colo, and grub.
Does LILO work for sparcs and/or MIPS machines?
--
JH
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/f
Jeremy Huntwork wrote:
Does LILO work for sparcs and/or MIPS machines?
No bug Grub 2 is scheduled to support Sparc, x86, and ppc, but only as
32 bit. Currently none of the MIPS bootloaders that I'm familar with
will boot a ELF64 object, arcboot and colo.
--
--
[EMAIL PROTECTED]
[EMAIL
Archaic wrote:
That just seems silly. Warn was much nicer and still allowed things to
proceed.
Can we not still warn, but just leave the exit status as '0'. The spec
(from the quote given) doesn't appear to forbid output, it just mandates
what the exit status should be.
--
http://linuxfro
33 matches
Mail list logo
