Hi
On Sat, Oct 29, 2005 at 09:42:06PM +0200, Ca?ada.Andres wrote:
> I'm trying to image a Debian OS.
> It seems, due to the kind of error (/sbin/init: 432: cannot create /dev/null:
> Read-only file system /sbin/init: 433: cannot open /dev/console: No such file
> Kernel panic: Attempted to kill in
o compile a new kernel without initrd for Debian and see if it works.
Any ideas??
Thanks in advance.
Andrés.
-Original Message-
From: [EMAIL PROTECTED] on behalf of Bernard Li
Sent: Fri 10/28/2005 7:19 PM
To: sisuite-users@lists.sourceforge.net
Cc:
Subject: RE: [Sisuite-user
Andres, What OS are you trying to image?
Cheers,
Bernard
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Cañada.Andres
> Sent: Friday, October 28, 2005 9:48
> To: sisuite-users@lists.sourceforge.net
> Subject: RE: [Sisuit
On Friday 28 October 2005 11:47, Cañada.Andres wrote:
> I saw something similar with my amd64 boxes, and fixed it by adding a
> rsync /dev/* /a/dev before the chroot. the node files weren't getting
> created for some reason...has to do with udev on gentoo, in my case. To
> check, when it says it'
I saw something similar with my amd64 boxes, and fixed it by adding a
rsync /dev/* /a/dev before the chroot. the node files weren't getting
created for some reason...has to do with udev on gentoo, in my case. To
check, when it says it's done please reboot me, hit ctrl-c and mount your
root
Asunto: Re: [Sisuite-users] kernel panic Systemimager
>
> On Friday 28 October 2005 10:03, Cañada.Andres wrote:
> > Hello!
> > I'm having some problems with Systemimager.
> > Everything seems to be Ok, but after the image has been installed in the
> > cli
-Mensaje original-
De: [EMAIL PROTECTED] en nombre de John Jolet
Enviado el: vie 28/10/2005 17:09
Para: sisuite-users@lists.sourceforge.net
CC:
Asunto: Re: [Sisuite-users] kernel panic Systemimager
On Friday 28 October 2005 10:03, Cañada.Andres wrote:
> Hello!
&g
On Friday 28 October 2005 10:03, Cañada.Andres wrote:
> Hello!
> I'm having some problems with Systemimager.
> Everything seems to be Ok, but after the image has been installed in the
> client using the diskette created with mkautoinstalldiskette command, I
> reboot the client and get a kernel pani
Hello!
I'm having some problems with Systemimager.
Everything seems to be Ok, but after the image has been installed in the client
using the diskette created with mkautoinstalldiskette command, I reboot the
client and get a kernel panic::
/sbin/init: 432: cannot create /dev/null: Read-only file
