Thanks everyone!
The --iso option funcions very well. But this option is not listed in
mkbootdisk version 1.4.8 manpage.
Thanks again!
- Mensagem Original
De: Michael Schwendt <[EMAIL PROTECTED]>
Para: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Assunto: Re: mkbootdisk f
ot; floppy disk fit 1474560 bytes,
space left = 47886 bytes, looks a bit like that is not enough upon
gzip'ping the created initrd image
I think mkinitrd of Red Hat Linux 9 is smarter and copies the existing
initrd onto the bootdisk.
> How can I create a boot CD?
Option --iso: mkbootdisk
Did you by any chance set up your disk using lvm?
We set up 2 of our systems recently using lvm
and coincidentally, we are unable to successfully
run a mkbootdisk on these two systems.
===/etc/fstab
/dev/rootvg/LogVol00 / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts
Luciano Rabelo,
On Tuesday July 01, 2003 10:19, Luciano Rabelo wrote:
> Hi,
>
> I'm trying to create a stand-alone boot floppy with mkbootdisk.
> Can any one help me?
>
> # mkbootdisk -v --device /tmp/mkbootdisk/test 2.4.18-14smp
> Formatting /tmp/mkbootdisk/test... don
root 220241 May 27 09:57
/boot/initrd-2.4.18-14smp.img
-rw-r--r--1 root root 1206433 Sep 4 2002
/boot/vmlinuz-2.4.18-14smp
- Mensagem Original
De: Michael Schwendt <[EMAIL PROTECTED]>
Para: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Assunto: Re: mkbootd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 01 Jul 2003 11:19:26 -0300, Luciano Rabelo wrote:
> I'm trying to create a stand-alone boot floppy with mkbootdisk.
> Can any one help me?
>
> # mkbootdisk -v --device /tmp/mkbootdisk/test 2.4.18-14smp
> Formatting
PROTECTED]>
Assunto: Re: mkbootdisk failed - help!
Data: 01/07/03 11:15
> Luciano Rabelo wrote:
> Hi,
>
> I'm trying to create a stand-alone boot floppy with mkbootdisk.
> Can any one help me?
>
> # mkbootdisk -v --device /tmp/mkbootdisk/test 2.4.18-14smp
> Formatting /tmp
Luciano Rabelo wrote:
Hi,
I'm trying to create a stand-alone boot floppy with mkbootdisk.
Can any one help me?
# mkbootdisk -v --device /tmp/mkbootdisk/test 2.4.18-14smp
Formatting /tmp/mkbootdisk/test... done.
Copying /boot/vmlinuz-2.4.18-14smp... done.
Creating initrd image...
gzip: stdou
Hi,
I'm trying to create a stand-alone boot floppy with mkbootdisk.
Can any one help me?
# mkbootdisk -v --device /tmp/mkbootdisk/test 2.4.18-14smp
Formatting /tmp/mkbootdisk/test... done.
Copying /boot/vmlinuz-2.4.18-14smp... done.
Creating initrd image...
gzip: stdout: No space left on d
Hi List,
I can't use mkbootdisk to make a bootable floppy disk for my linux server. I wou
ld like to get some help from this list.
Here is the detail:
My linux server is running on a Compaq server box which has RAID hardware.
# ls /lib/modules
2.4.7-10 2.4.7-10smp fs
# mkbootdisk -v 2.4.7-
On Thursday 27 March 2003 02:31 am, you wrote:
> * Stephen Kuhn
>
> > > mkboootdisk kernel-2.4.18-27.8.0
> > >
> > > bash: mkbootdisk: command not found
> >
> > /sbin/mkbootdisk
>
> Maybe it should be run by root? (Haven't tried neither, th
* Stephen Kuhn
> > mkboootdisk kernel-2.4.18-27.8.0
> >
> > bash: mkbootdisk: command not found
>
> /sbin/mkbootdisk
Maybe it should be run by root? (Haven't tried neither, though.)
--
Jon Haugsand, [EMAIL PROTECTED]
http://www.norges-bank.no
--
redhat-
On Thu, 2003-03-27 at 17:24, Shawn wrote:
> Hi,
>
> I need to make a bootdisk after installation and following RedHat's
> guide use:
>
> mkboootdisk kernel-2.4.18-27.8.0
>
> but get:
>
> bash: mkbootdisk: command not found
>
> What do I need to
t;
>> mkboootdisk kernel-2.4.18-27.8.0
>>
>> but get:
>>
>> bash: mkbootdisk: command not found
>>
>> What do I need to do differently?
>Perhaps you are not root, or you did "su" vs "su -"
>That means among others that /sbin/ is no
Shawn wrote:
sorry needed the full path
/sbin/mkbootdisk
FYI - if you jump to root using "su -", prepending the "/sbin/" to your
commands becomes unneccesary as the "-" tells su to use root's (or the
user's for that matter) environment and subsequently
sorry needed the full path
/sbin/mkbootdisk
--
Shawn <[EMAIL PROTECTED]>
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
On Thu, 2003-03-27 at 07:24, Shawn wrote:
> Hi,
>
> I need to make a bootdisk after installation and following RedHat's
> guide use:
>
> mkboootdisk kernel-2.4.18-27.8.0
>
> but get:
>
> bash: mkbootdisk: command not found
>
> What do I need to do diff
Hi,
I need to make a bootdisk after installation and following RedHat's
guide use:
mkboootdisk kernel-2.4.18-27.8.0
but get:
bash: mkbootdisk: command not found
What do I need to do differently?
--
Shawn <[EMAIL PROTECTED]>
--
redhat-list mailing list
unsubscribe ma
On Sun, 13 Oct 2002 12:34:47 -0500
Robert Canary <[EMAIL PROTECTED]> wrote:
> Good day listers,
>
> I have a machine that I always boot from floppy, with a disk created
> from mkbootdisk utility. However, this machine is hardly ever
> accessed via the keyboard and is very
Here is a guide for you:
http://www.ibiblio.org/pub/Linux/docs/HOWTO/Remote-Serial-Console-HOWTO
On Sun, 2002-10-13 at 13:34, Robert Canary wrote:
> Good day listers,
>
> I have a machine that I always boot from floppy, with a disk created
> from mkbootdisk utility. However, thi
Good day listers,
I have a machine that I always boot from floppy, with a disk created
from mkbootdisk utility. However, this machine is hardly ever accessed
via the keyboard and is very combersome to hook up a monitor to as well
because of the location. What/how do I need to include on the
Title: mkbootdisk not working
Hi,
I'm new to Linux and I was trying to make a new boot disk afer updating my system, but the mkbootdisk command will not work. I get a response that says it is not a valid command. Can anyone tell me how to fix this problem? Is there some package I m
> I was able to boot this kernel 2.4.19-pre2 using the cat
> arch/i386/bzImage >/dev/fd0
ack.. use dd. Don't cat an image to a device. That's just gross. I
wouldn't even expect it to work :)
2.4.19 hasn't been released yet. As noted, it's in pre-release stages. If
it don't boot.. whatever. Pr
I know the stable kernel is 2.4.9-31... but I thought I would make you
all aware that
I had problems with running the stock RH 7.2 mkbootdisk in creating a
boot floppy
for this kernel 2.4.19-pre2.
mkbootdisk successfully creates the standard boot files as noted below:
[root@f1j rpms
I made a bootdisk with mkbootdisk and always get the Kernel Panic message
saying it was not able to find init and open a console, I've checked all the
files in my boot disk and still doesn'r work. Why???
Beatriz Elena Durán Castañeda
www.EMon
system,
> >are you?)
>
> >If mkbootdisk set the wrong root partition, it would be handy to see
> >your /etc/fstab file and the lilo.conf files from your running system
> >and from your boot disk.
>
> >Mikkel
>
> This is my lilo.conf in the floppy
>
> boot=/de
>Try mounting the boot disk, and looking at etc/lilo.conf. Make sure it
>has the correct partition for the root file system. (You are not
>trying to use a boot disk made on one system to boot a different system,
>are you?)
>If mkbootdisk set the wrong root partition, it would
On Thu, 5 Apr 2001, Beatriz Elena Duran Castañeda wrote:
> I made a bootdisk with mkbootdisk and always get the Kernel Panic message
> saying it was not able to find init and open a console, I've checked all the
> files in my boot disk and still doesn'r work. Why???
>
&g
I made a bootdisk with mkbootdisk and always get the Kernel Panic message
saying it was not able to find init and open a console, I've checked all the
files in my boot disk and still doesn'r work. Why???
Ing. Beatriz Elena Durán Castañeda
www.EMon
oot@circuit /root]# file /boot/vmlinuz-2.4.3
/boot/vmlinuz-2.4.3: x86 boot sector
as it is on my system.
On 4 Apr 2001, Dominic Mitchell wrote:
>
> Hi,
>
> I just made a bootdisk for kernel 2.2.18 which seems to be working
> correctly. However I do not understand why 'mkbootdis
"Mikkel L. Ellertson" <[EMAIL PROTECTED]> writes:
> >
> >
> mkinitrd needs to use the loop device to put files in the RAM disk>
> image. What happens if you run "modprobe loop"? Or if you are
> running a custom kernel, did you leave out loop device support?
> The other major cause of this er
On 4 Apr 2001, Dominic Mitchell wrote:
>
> Hi,
>
> I just made a bootdisk for kernel 2.2.18 which seems to be working
> correctly. However I do not understand why 'mkbootdisk' complains
> that all of my loopback devices are in use and can't open
> /vmlinuz-2
Hi,
I just made a bootdisk for kernel 2.2.18 which seems to be working
correctly. However I do not understand why 'mkbootdisk' complains
that all of my loopback devices are in use and can't open
/vmlinuz-2.2.18. See below.
Would someone shed some lights on this?
T
I mkbootdisk well for RH-Linux 6.0 kernel 2.2.5-15.
When I boot with it, I get a message at a later stage:
Warning: Unable to open an initial console.
Kernel panic: No init found. Try passing init= option to kernel.
Let ideas flow here now...
Francis.
--
To unsubscribe: mail [EMAIL
34 matches
Mail list logo