From: Christoph Plattner <[EMAIL PROTECTED]>
Subject: Re: Diskless Booting (Etherboot/nbgrub)
Date: Tue, 15 Aug 2000 20:24:16 +0200
> Using memory bekow 0x1 for boting an image is not at all a
> violation. This violation was aonly true for the documentation
> of netboot 0.8.1 and before, as
On Wed, 26 Jul 2000, Stefan Ondrejicka wrote:
Hello,
> > > So, can you rename my partid to parttype and add it to grub ? I think I
> > > saw such something in grub TODO list.
> >
> > Send a cleaned patch. My time is very limited currently.
Ok. I have just cleaned that patch - it uses now set
Hello, Victor!
> Do you really think it's right way to ask everyone to patch his(her)
> kernel headers ?
Not everyone. It's Ok to ask kernel maintainers and packagers of
distributions.
> > They might have already fixed the bug in 2.4.0-test6, though.
It's not fixed even in 2.4.0-test7-pre4
>
Using memory bekow 0x1 for boting an image is not at all a
violation. This violation was aonly true for the documentation
of netboot 0.8.1 and before, as mkbni-xxx was the base of all.
Code reading of netboot-0.9.0 has shown, that the limit to load is
0x8000 and not 0x1. Also in discuss
15-Aug-00 12:47 you wrote:
> From: Andres VHNet Staff <[EMAIL PROTECTED]>
> Subject: Re: problems w/ linux 2.4.0-testX and reiserfs 3.6.11
> Date: Mon, 14 Aug 2000 21:02:26 -0400
>> Oops, sorry about that. i wanted to keep the email short, i thought i posted
>> the errors as well ;) Anyways, h
I've fixed a serious bug in nbgrub with Matthias Kretschmer. That
was because nbgrub violated a rule in the Network Boot Image Proposal
(i.e. A loader which complies with the proposal shouldn't load any
second loader below 0x1). As that was quite disgraceful for me,
now I want to release nex
