Randy Welch [EMAIL PROTECTED] writes:
9.1: 1252778 Mar 14 2003 /boot/vmlinuz-2.4.21-0.13mdk
But you can still create a boot floppy with 9.1...
That depends on the quantity of modules that will need to go in
the initrd. If you use XFS or some large SCSI adapters, that
won't be possible.
--
Guillaume Cottenceau wrote:
Svetoslav Slavtchev [EMAIL PROTECTED] writes:
FWIW, this exact same problem also existed in 9.1, so it is not a 9.2
regression.
well not exactly
in 9.1 the problem was only with xfs (module is ~300k)
in cooker/9.2 the kernel is compiled with all debuging
John Allen [EMAIL PROTECTED] writes:
[...]
Get a bigger floppy disk, or use ext2 filesystems only, or provide a
patch to make smaller kernels.
Yes; but who is responsible for this. 9.2 has been released with the inability
to create a boot floppy on a standard 1440 sized floppy.
John Allen [EMAIL PROTECTED] writes:
Not so. I periodically tested the cooker tree for the ability to
create a good install and a running Mandrake.
Try this script; it creates a 1680k formatted floppy.
If we want to go with larger floppies with 1.44 MBytes drives, we
need serious
Svetoslav Slavtchev [EMAIL PROTECTED] writes:
FWIW, this exact same problem also existed in 9.1, so it is not a 9.2
regression.
well not exactly
in 9.1 the problem was only with xfs (module is ~300k)
in cooker/9.2 the kernel is compiled with all debuging symbols
(not the case with
Pascal Cavy [EMAIL PROTECTED] writes:
I second this, for example I have a machine where lilo does not work so I HAVE
TO use a boot disk to start it. After 9.2 upgrade, I cannot create such a
boot disk. (disk full during creation).
You might consider the 1.6 mbytes floppy. But rather, why
Ron Stodden [EMAIL PROTECTED] writes:
well not exactly in 9.1 the problem was only with xfs (module
is ~300k)
Disagree. I am talking about a vanilla ext2 install of 9.1 - it
cannot produce a boot floppy.
/me thinks it can.
--
Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Felix Miata [EMAIL PROTECTED] writes:
Mandrake 9.1
127509 Jul 30 17:48 initrd-2.4.21-0.25mdk.img
1263795 Jul 24 16:02 vmlinuz-2.4.21-0.25mdk
1391304
Mandrake 9.2
414616 Sep 22 12:46 initrd-2.4.22-10mdk.img
1343803 Sep 18 06:43 vmlinuz-2.4.22-10mdk
1758419
What a large
Randy Welch [EMAIL PROTECTED] writes:
Only problem is that it will only find the first installed linux
on your disk. My test installs are always in later partitions.
Well, not exactly, the first installed *Mandrake* Linux on your
disk.
That's automatic stuff: go to a console and mount any
Le Mercredi 22 Octobre 2003 14:31, Guillaume Cottenceau a écrit :
Pascal Cavy [EMAIL PROTECTED] writes:
I second this, for example I have a machine where lilo does not work so I
HAVE TO use a boot disk to start it. After 9.2 upgrade, I cannot create
such a boot disk. (disk full during
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pascal Cavy wrote:
Le Mercredi 22 Octobre 2003 14:31, Guillaume Cottenceau a écrit :
You might consider the 1.6 mbytes floppy. But rather, why lilo
doesn't work? It should.
humm Guillaume, is the idea of generating an iso image for booting too
Svetoslav Slavtchev [EMAIL PROTECTED] writes:
FWIW, this exact same problem also existed in 9.1, so it is not a 9.2
regression.
well not exactly
in 9.1 the problem was only with xfs (module is ~300k)
in cooker/9.2 the kernel is compiled with all debuging symbols
(not
On Wednesday 22 October 2003 13:20, Guillaume Cottenceau wrote:
John Allen [EMAIL PROTECTED] writes:
[...]
Get a bigger floppy disk, or use ext2 filesystems only, or provide a
patch to make smaller kernels.
Previously I posted a mkbootdisk that used the 1680K format for floppys; and
John Allen wrote:
Try this script; it creates a 1680k formatted floppy.
Yes,
[EMAIL PROTECTED] ron]# ./mkbootdisk --device /dev/floppy/0u1680 2.4.22-10mdk
creates a floppy,
[EMAIL PROTECTED] ron]# ls -l /local/floppy
total 1584
-rwxr--r--1 root root 204 Oct 23 00:35 boot.msg*
On Wednesday 22 October 2003 16:13, Ron Stodden wrote:
John Allen wrote:
Try this script; it creates a 1680k formatted floppy.
Yes,
[EMAIL PROTECTED] ron]# ./mkbootdisk --device /dev/floppy/0u1680 2.4.22-10mdk
creates a floppy,
[EMAIL PROTECTED] ron]# ls -l /local/floppy
total 1584
On Wed, Oct 22, 2003 at 02:25:34PM +0200, Guillaume Cottenceau wrote:
John Allen [EMAIL PROTECTED] writes:
Not so. I periodically tested the cooker tree for the ability to
create a good install and a running Mandrake.
Try this script; it creates a 1680k formatted floppy.
If we want to go with
On Wed, 22 Oct 2003, Luca Berra wrote:
On Wed, Oct 22, 2003 at 02:25:34PM +0200, Guillaume Cottenceau wrote:
John Allen [EMAIL PROTECTED] writes:
Not so. I periodically tested the cooker tree for the ability to
create a good install and a running Mandrake.
Try this script; it
On Wednesday 22 October 2003 08:25 am, Guillaume Cottenceau wrote:
If we want to go with larger floppies with 1.44 MBytes drives, we
need serious testing. I'm afraid this brings lots of hardware
problems (and floppies already have much hardware problems).
This would be a good thing for a
Thomas Backlund wrote:
From: Svetoslav Slavtchev [EMAIL PROTECTED]
PS.
there is one related thred on lkml may be
Where's the bzip2 compressed linux-kernel patch?
might be interesting to include it ?
http://marc.theaimsgroup.com/?t=10664547841r=1w=2
http://shepard.kicks-ass.net/~cc/
I have
Svetoslav Slavtchev [EMAIL PROTECTED] writes:
so the bloat started with 9.1 ?
can you check
grep CONFIG_KALLSYMS /boot/config-*
the bloat really was acpi support out of the box
Svetoslav Slavtchev [EMAIL PROTECTED] writes:
so the bloat started with 9.1 ?
can you check
grep CONFIG_KALLSYMS /boot/config-*
the bloat really was acpi support out of the box
acpi is about 120k that's true,
but acpi doesn't say :
the kernel size will increase with 10-20 %
From: Svetoslav Slavtchev [EMAIL PROTECTED]
PS.
there is one related thred on lkml may be
Where's the bzip2 compressed linux-kernel patch?
might be interesting to include it ?
http://marc.theaimsgroup.com/?t=10664547841r=1w=2
http://shepard.kicks-ass.net/~cc/
(I'm cc'ing the minicd-scripts
Svetoslav Slavtchev [EMAIL PROTECTED] writes:
so the bloat started with 9.1 ?
can you check
grep CONFIG_KALLSYMS /boot/config-*
the bloat really was acpi support out of the box
acpi is about 120k that's true,
but acpi doesn't say :
the kernel size will increase with 10-20
Svetoslav Slavtchev [EMAIL PROTECTED] writes:
so the bloat started with 9.1 ?
can you check
grep CONFIG_KALLSYMS /boot/config-*
the bloat really was acpi support out of the box
acpi is about 120k that's true,
but acpi doesn't say :
the kernel size will increase
From: Svetoslav Slavtchev [EMAIL PROTECTED]
PS.
there is one related thred on lkml may be
Where's the bzip2 compressed linux-kernel patch?
might be interesting to include it ?
http://marc.theaimsgroup.com/?t=10664547841r=1w=2
http://shepard.kicks-ass.net/~cc/
(I'm cc'ing the
Buchan Milne wrote:
Using the rescue mode of CD1 remains the only way to recover from an
unbootable (lilo, grub, XOSL, etc.) system. hd or network installed
systems do not have any CDs, nor can they be made with mkcd on an
unbootable system. Catch 22?
Rescue is available for network
Ron Stodden wrote:
John
FWIW, this exact same problem also existed in 9.1, so it is not a 9.2
regression.
Ahh but in 9.1 you could create a floppy from drakfloppy. You cannot do
that in 9.2.
I filed a bug report on it
-randy
Buchan Milne wrote:
Felix Miata wrote:
OTOH, not being able to make a standard boot floppy is a serious
handicap to those who for whatever reason can't or don't boot from
the HD, and don't have CDRW or don't want to boot from CD each time.
Hmm, IMHO better to ensure that they
Randy Welch wrote:
Ron Stodden wrote:
John
FWIW, this exact same problem also existed in 9.1, so it is not a 9.2
regression.
Ahh but in 9.1 you could create a floppy from drakfloppy. You cannot do
that in 9.2.
I filed a bug report on it
Interesting. drakfloppy provides a pulldown list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Svetoslav Slavtchev wrote:
so the bloat started with 9.1 ?
can you check
grep CONFIG_KALLSYMS /boot/config-*
Good call:
$ grep CONFIG_KALLSYMS /boot/config-*
/boot/config-2.4.19-16mdk:# CONFIG_KALLSYMS is not set
Randy Welch wrote:
Only problem is that it will only find the first installed linux on
your disk. My test installs are always in later partitions. The
rescue image tends to find the first one it sees. (so on my system it
would see my 9.1 install instead of the 9.2...
I almost never tell
9.2 cannot produce a floppy boot disk!
The installer option to produce a boot 1.44 floppy, if you can manage to
find it from its hiding place, produces only an ?Error! message.
That floppy will not boot the system.
Trying explicitly leads to exactly the same behaviour and again produces
a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ron Stodden wrote:
9.2 cannot produce a floppy boot disk!
The installer option to produce a boot 1.44 floppy, if you can manage to
find it from its hiding place, produces only an ?Error! message.
That floppy will not boot the system.
Trying
On Friday 17 October 2003 12:07, Ron Stodden wrote:
9.2 cannot produce a floppy boot disk!
[snipped]
[EMAIL PROTECTED] ron]# uname -r
2.4.22-10mdk
[EMAIL PROTECTED] ron]# mkbootdisk 2.4.22-10mdk
Insert a disk in /dev/floppy/0. Any information on the disk will be lost.
Press Enter to
On Friday 17 October 2003 12:17, Buchan Milne wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[snipped]
Get a bigger floppy disk, or use ext2 filesystems only, or provide a
patch to make smaller kernels.
Yes; but who is responsible for this. 9.2 has been released with the inability
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Allen wrote:
On Friday 17 October 2003 12:17, Buchan Milne wrote:
This is a very basic and essential requirement which should not be in
any way hidden.
Haven't made a boot floppy (besides to install from) myself in over 2
years.
Oh, I forgot
On Friday 17 October 2003 12:37, Buchan Milne wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Many new machines now come without floppy disks.
Yeah, my home made PC's don't have floppys (except for the server).
Yes; usually use the CD myself. But none the less this is really not
John Allen wrote:
On Friday 17 October 2003 12:17, Buchan Milne wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[snipped]
Get a bigger floppy disk, or use ext2 filesystems only, or provide a
patch to make smaller kernels.
Yes; but who is responsible for this. 9.2 has been released with
Buchan Milne wrote:
Of course, it would be nice to have it working by default, but Ron
always goes overboard on his small niggles in the first two weeks of a
release (he could have tested this in the beta series of course ...).
Not so. I periodically tested the cooker tree for the ability to
On Friday 17 October 2003 14:46, Ron Stodden wrote:
Buchan Milne wrote:
Of course, it would be nice to have it working by default, but Ron
always goes overboard on his small niggles in the first two weeks of a
release (he could have tested this in the beta series of course ...).
Not so.
Buchan Milne wrote:
Rescue is available for network and hd installs. Have you tried it? I
have used it a few times on a network install.
That´s news to me.
Pray tell us how rescue is initiated from an hd or network install, and
where that is so unmissably documented that I must have missed it
Ron Stodden wrote:
Buchan Milne wrote:
Rescue is available for network and hd installs. Have you tried it? I
have used it a few times on a network install.
That´s news to me.
Pray tell us how rescue is initiated from an hd or network install,
and where that is so unmissably documented that I
Buchan Milne wrote:
Using the rescue mode of CD1 remains the only way to recover from an
unbootable (lilo, grub, XOSL, etc.) system. hd or network installed
systems do not have any CDs, nor can they be made with mkcd on an
unbootable system. Catch 22?
Ron Stodden wrote:
Pray tell us where
John Allen wrote:
On Friday 17 October 2003 12:17, Buchan Milne wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[snipped]
Get a bigger floppy disk, or use ext2 filesystems only, or provide a
patch to make smaller kernels.
Yes; but who is responsible for this.
Svetoslav Slavtchev wrote:
FWIW, this exact same problem also existed in 9.1, so it is not a 9.2
regression.
well not exactly
in 9.1 the problem was only with xfs (module is ~300k)
Disagree. I am talking about a vanilla ext2 install of 9.1 - it cannot
produce a boot floppy.
--
Ron.
Le Vendredi 17 Octobre 2003 17:18, Svetoslav Slavtchev a écrit :
Yes; but who is responsible for this. 9.2 has been released with the
inability
to create a boot floppy on a standard 1440 sized floppy.
This is a very basic and essential requirement which should not be in
any way
Svetoslav Slavtchev wrote:
FWIW, this exact same problem also existed in 9.1, so it is not a 9.2
regression.
well not exactly
in 9.1 the problem was only with xfs (module is ~300k)
Disagree. I am talking about a vanilla ext2 install of 9.1 - it cannot
produce a boot
Ron Stodden wrote:
Buchan Milne wrote:
Using the rescue mode of CD1 remains the only way to recover from an
unbootable (lilo, grub, XOSL, etc.) system. hd or network installed
systems do not have any CDs, nor can they be made with mkcd on an
unbootable system. Catch 22?
Pray tell us
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Felix Miata wrote:
OTOH, not being able to make a standard boot floppy is a serious
handicap to those who for whatever reason can't or don't boot from
the HD, and don't have CDRW or don't want to boot from CD each time.
Hmm, IMHO better to ensure
On Fri, 2003-10-17 at 14:46, Ron Stodden wrote:
Buchan Milne wrote:
Of course, it would be nice to have it working by default, but Ron
always goes overboard on his small niggles in the first two weeks of a
release (he could have tested this in the beta series of course ...).
Not so. I
Svetoslav Slavtchev wrote:
what does your 9.1 install tells for ls -l /boot/vmlinuz*`
My 9.1 is my lowest numbered Linux partition, so it has the job of
lilo-booting everything. I install a Linux to use its own partition
as lilo boot manager. Since this approach neglects the requirement
Buchan Milne wrote:
Felix Miata wrote:
OTOH, not being able to make a standard boot floppy is a serious
handicap to those who for whatever reason can't or don't boot from
the HD, and don't have CDRW or don't want to boot from CD each time.
Hmm, IMHO better to ensure that they can boot
On Fri Oct 17 22:22 -0400, Felix Miata wrote:
Why so much kernel and initrd swell of late?
Because there's more hardware out there than there was a few years ago
and if MDKSoft decides that a certain IDE controller isn't common enough
to justify taking up rescue and kernel space, some nut comes
53 matches
Mail list logo
