Le Sun, Apr 07, 2002 at 06:50:14PM -0500, Chris Lawrence écrivait:
> Sure. Do you want me to commit the whole set of changes for ISOLINUX
> or just this fix? (The whole set will be easier, but I can give you a
> "manual patch" to fix the boot.bat file with a bit of work.)
Yeah, go for it.
Chee
On Apr 08, Philip Hands wrote:
> On Mon, 2002-04-08 at 00:05, Chris Lawrence wrote:
>
> > I tracked down the problem... each flavor uses its own root.bin.
> > After some tweaking, I fixed the build process and updates are now
> > online (see my lagged mail to the list).
>
> Hm, doesn't fix it fo
On Apr 08, Raphael Hertzog wrote:
> Le Sun, Apr 07, 2002 at 04:54:15PM -0500, Chris Lawrence écrivait:
> > Hmm. I see the problem. There's a separate root.bin for each flavor,
> > and the code isn't accounting for that.
>
> Are you going to fix it also for the boot.bat that is generated by
> de
I just tried a few other test installs.
vanilla works (well it gets past the devices problem), all others,
including the default idepci are broken, because the are looking to see,
for example:
/target/lib/modules/2.2.20-idepci
after the drvers install
Cheers, Phil.
--
Say no to software pat
On Mon, 2002-04-08 at 00:05, Chris Lawrence wrote:
> I tracked down the problem... each flavor uses its own root.bin.
> After some tweaking, I fixed the build process and updates are now
> online (see my lagged mail to the list).
Hm, doesn't fix it for the bf2.4 flavour when I try it I'm afraid.
On Apr 08, Raphael Hertzog wrote:
> Le Sun, Apr 07, 2002 at 10:29:31PM +0100, Philip Hands écrivait:
> > Just tried this -- If one tries an install of the bf24 kernel, when you
> > get to the "Configure Device Driver Modules", it's obviously not taking
> > account of the kernel it was booted with,
Le Sun, Apr 07, 2002 at 04:54:15PM -0500, Chris Lawrence écrivait:
> Hmm. I see the problem. There's a separate root.bin for each flavor,
> and the code isn't accounting for that.
Are you going to fix it also for the boot.bat that is generated by
debian-cd in tools/boot/woody/boot-i386 ?
Cheer
Le Sun, Apr 07, 2002 at 10:29:31PM +0100, Philip Hands écrivait:
> Just tried this -- If one tries an install of the bf24 kernel, when you
> get to the "Configure Device Driver Modules", it's obviously not taking
> account of the kernel it was booted with, but is unpacking the modules
> for 2.2.20
-BEGIN PGP SIGNED MESSAGE-
Hash: MD5
On Sunday 07 April 2002 14:29, Philip Hands wrote:
> On Sun, 2002-04-07 at 20:14, Chris Lawrence wrote:
> > Yes, it is ISOLINUX-based, not MULTIBOOT. It just got attached to
> > this thread because that's where Raphael mentioned that I was going to
>
On Apr 07, Philip Hands wrote:
> On Sun, 2002-04-07 at 20:14, Chris Lawrence wrote:
> > Yes, it is ISOLINUX-based, not MULTIBOOT. It just got attached to
> > this thread because that's where Raphael mentioned that I was going to
> > work on it.
>
> Just tried this -- If one tries an install of t
On Sun, 2002-04-07 at 20:14, Chris Lawrence wrote:
> Yes, it is ISOLINUX-based, not MULTIBOOT. It just got attached to
> this thread because that's where Raphael mentioned that I was going to
> work on it.
Just tried this -- If one tries an install of the bf24 kernel, when you
get to the "Config
On Apr 07, Jim Westveer wrote:
[Something, my reply function killed it...]
Yes, it is ISOLINUX-based, not MULTIBOOT. It just got attached to
this thread because that's where Raphael mentioned that I was going to
work on it.
It looks like I forgot to put the PROMPT setting in the config file.
Fo
12 matches
Mail list logo
