Pascal [EMAIL PROTECTED] writes:
Le Mercredi 2 Avril 2003 16:35, Guillaume Cottenceau a écrit :
Pascal Cavy [EMAIL PROTECTED] writes:
If this is true, then that was my problem on rescue mode. And that is
why, Guillaume, an new rescue menu entry to rebuild a kernel initrd
would be a
Le Jeudi 3 Avril 2003 12:54, Guillaume Cottenceau a écrit :
Pascal [EMAIL PROTECTED] writes:
Le Mercredi 2 Avril 2003 16:35, Guillaume Cottenceau a écrit :
Pascal Cavy [EMAIL PROTECTED] writes:
If this is true, then that was my problem on rescue mode. And that is
why, Guillaume, an
Pascal Cavy [EMAIL PROTECTED] writes:
not exactly. that's the case for reinstalling bootloader for
example. all experts know easily how to do that, but there is a
menu entry, because the rescue is not only for experts. same
applies to reboot.
That's what I wanted to read, at last.
Le Mercredi 2 Avril 2003 09:24, Thierry Vignaud a écrit :
Gary Greene [EMAIL PROTECTED] writes:
First I was to mount /proc because mkinitrd _does not check_
that /proc is available and thus we end in a loop at the step it
scans for /proc/mounts FS.
I don't consider that to be a
Guillaume Cottenceau said,
I tried the following but to no avail (maybe because of using the freshly
installed system by means of a chroot on /mnt) :
boot rescue cd1
mount all FS on /mnt
go to console
chroot /mnt
First I was to mount /proc because mkinitrd _does not check_ that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 02 April 2003 12:21, Neil Bothwick wrote:
Guillaume Cottenceau said,
I tried the following but to no avail (maybe because of using the
freshly installed system by means of a chroot on /mnt) :
boot rescue cd1
mount all FS on
Le Mercredi 2 Avril 2003 12:21, Neil Bothwick a écrit :
Guillaume Cottenceau said,
I tried the following but to no avail (maybe because of using the
freshly installed system by means of a chroot on /mnt) :
boot rescue cd1
mount all FS on /mnt
go to console
chroot /mnt
First I
Pascal Cavy [EMAIL PROTECTED] writes:
If this is true, then that was my problem on rescue mode. And that is why,
Guillaume, an new rescue menu entry to rebuild a kernel initrd would be a
plus in case someone has destroyed or corrupted it. (nothing to do with mdk
installation here, just a
Le Mercredi 2 Avril 2003 16:35, Guillaume Cottenceau a écrit :
Pascal Cavy [EMAIL PROTECTED] writes:
If this is true, then that was my problem on rescue mode. And that is
why, Guillaume, an new rescue menu entry to rebuild a kernel initrd
would be a plus in case someone has destroyed or
After migration from MDK 7.2 to MDK 9.1, the installer left a new system
without an initrd for 2.4.21-0.13mdk, thus I cannot boot it anymore.
I was wondering if it is possible to rebuild my initrd from the 9.1 rescue CD.
I tried the following but to no avail (maybe because of using the freshly
Pascal Cavy wrote:
After migration from MDK 7.2 to MDK 9.1, the installer left a new system
without an initrd for 2.4.21-0.13mdk, thus I cannot boot it anymore.
I was wondering if it is possible to rebuild my initrd from the 9.1 rescue CD.
I tried the following but to no avail (maybe because of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pascal Cavy wrote:
After migration from MDK 7.2 to MDK 9.1, the installer left a new system
without an initrd for 2.4.21-0.13mdk, thus I cannot boot it anymore.
I was wondering if it is possible to rebuild my initrd from the 9.1
rescue CD.
I
Le Mardi 1 Avril 2003 19:20, Buchan Milne a écrit :
Pascal Cavy wrote:
After migration from MDK 7.2 to MDK 9.1, the installer left a new system
without an initrd for 2.4.21-0.13mdk, thus I cannot boot it anymore.
I was wondering if it is possible to rebuild my initrd from the 9.1
rescue
Pascal Cavy [EMAIL PROTECTED] writes:
After migration from MDK 7.2 to MDK 9.1, the installer left a new system
without an initrd for 2.4.21-0.13mdk, thus I cannot boot it anymore.
/root/drakx/report.bug.gz would help.
I was wondering if it is possible to rebuild my initrd from the 9.1
Pascal Cavy [EMAIL PROTECTED] writes:
Ask gc to add an option to the menu ;-)?
Buchan
yes an option in the rescue menu could be a plus for newbies...
definitely not. rebuilding the initrd wouldn't magically fix the
reason why the initrd generation failed during install.
--
Guillaume
Le Mercredi 2 Avril 2003 00:42, Guillaume Cottenceau a écrit :
Pascal Cavy [EMAIL PROTECTED] writes:
Ask gc to add an option to the menu ;-)?
Buchan
yes an option in the rescue menu could be a plus for newbies...
definitely not. rebuilding the initrd wouldn't magically fix the
something of a stupid question but
how would one make on a single non-networked box have local-host show
up as example laurencemartin.com
(but not make the real laurencemartin.com unavailible on that box)
{66.246.17.187 on the net}
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 01 April 2003 5:40 pm, Guillaume Cottenceau wrote:
Pascal Cavy [EMAIL PROTECTED] writes:
After migration from MDK 7.2 to MDK 9.1, the installer left a new system
without an initrd for 2.4.21-0.13mdk, thus I cannot boot it anymore.
Gary Greene [EMAIL PROTECTED] writes:
First I was to mount /proc because mkinitrd _does not check_
that /proc is available and thus we end in a loop at the step it
scans for /proc/mounts FS.
I don't consider that to be a bug. Many (all?) of our system
tools rely very much on /proc
19 matches
Mail list logo
