Hi Scott
Well I'm new to this too, but I've done this in two ways.
Method 1 - editing existing:
Download an existing boot floppies (eg bf2.4) set, dd to floppy and mount
rescue.bin
i.e. mount -t auto -o loop rescue.bin /mnt
create a custom kernel flavour to meet your needs
Then replace linux.bin
Could someone kindly point out how to stop
boot-floppies from producing compact / idepci / bf2.4 flavours when building a
custom (2.4.19) package?
I seem to have narrowed it down to release.sh and
rootdisk.sh, where a variable $revext is invoked, but I can's see (after a long
time eyeballi
dure for doing this, but the
solution eludes me. Any guidance in this is much appreciated.
Regards, David
- Original Message -
From: "Chris Tillman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, October 15, 2002 2:13 AM
Subject: Re: building a 2.4.19 i
Could someone kindly lead me to where I might
find documentation on how to use boot-floppies to create a custom boot set
of 2.4.19.
I've tried cvs, the included readme file and
endless searches, but can't find anything specific enough to help.
I've downloaded a 2.4.19 stock kernel and hav
I'm trying to get boot-floppies to build a
stripped-down 2.4.19 install set and am running into a couple of
problems.
I'd like to check first that this is an appropriate
place to ask about the correct procedure of creating custom install sets with
boot-floppies - if not could you direct me
Hello
Having successfully compiled a custom 2.4.19 kernel
for ide raid support (and stripping out all modules etc), I created a set of
boot-floppies from the bf2.4 set.
On mounting rescue.bin, I dropped the new kernel
in, ran rdev.sh etc, edited install.sh, making VERSION=2.4.19 .
Ins
aller ignored files)
Rgds, David
- Original Message -
From: "Eduard Bloch" <[EMAIL PROTECTED]>
To: "David Murphy" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, July 10, 2002 5:18 PM
Subject: Re: promise controller
> #include
>
How did you name the hardrive when you used fdisk? I've tried using fdisk on
/dev/ataraid/hd0 and also /dev/hda .. /hdd etc without luck.
Rgds, David
- Original Message -
From: "Ed Street" <[EMAIL PROTECTED]>
To: "'David Murphy'" <[EMAIL PRO
which logs should i send?
- Original Message -
From: "Eduard Bloch" <[EMAIL PROTECTED]>
To: "David Murphy" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, July 10, 2002 11:48 AM
Subject: Re: promise controller
> #include
> Dav
is a standard 2.4.18 - I've
looked at the config file and it seems that the same Promise drivers are
selected for slackware as they are for the bf2.4
Regards, David
- Original Message -
From: "Eduard Bloch" <[EMAIL PROTECTED]>
To: "David Murphy" <[EMAIL P
I've read jut about everything I can on trying to get debian woody to
install on a promise controller but the install still fails.
I'm using bf2.4 netinst images but the installer still fails to detect a
hard drive.
An 8.1 slackware installation runs fine so I know it's not a hardware
problem.
I have managed to successfully dd the bf2.4 rescue.bin to a floppy and I've
replaced linux.bin with my own compiled kernel (having run rdev.sh).
This rescue floppy successfully boots and allows me to format and partition
my hard drive. I've also been able to setup networking.
But, as soon as I
> I have managed to successfully dd the bf2.4 rescue.bin to a floppy and
> I've replaced linux.bin with my own compiled kernel (having run rdev.sh).
>
> This rescue floppy successfully boots and allows me to format and
> partition my hard drive. I've also been able to setup networking.
>
> But,
I have managed to successfully dd the bf2.4 rescue.bin to a floppy and I've
replaced linux.bin with my own compiled kernel (having run rdev.sh).
This rescue floppy successfully boots and allows me to format and partition
my hard drive. I've also been able to setup networking.
But, as soon as I
14 matches
Mail list logo
