/srv/tftp/fai/vmlinuz-2.6.27.10-faiinstall'
cp: cannot stat `/srv/fai/nfsroot/live/filesystem.dir/boot/initrd.img-*': No
such file or directory
ERROR: No initrd installed.
In the /etc/fai/NFSROOT I included
PACKAGES aptitude
:
live-initramfs
linux-image-2.6.27.10-faiinstall
:
I gue
trd for the kernel, do I need to use the live-initramfs
hook?
> I am using the kernel-package tools. I would expect to get a initrd using
> make-kpkg --revision ... kernel-image --initrd
This should work. But --initrd only saves a configuration option
somewhere inside the kernel pa
On Thu, Jan 08, 2009 at 07:43:23PM +0100, Thomas Lange wrote:
> > On Thu, 8 Jan 2009 19:36:35 +0100, Henning Fehrmann
> > said:
>
> > I guess, a proper initrd has to come already with the kernel.
> not really, because dpkg-reconfigure linux-image... should be called,
> which creates
> On Wed, 14 Jan 2009 11:39:46 +0100, Henning Fehrmann
> said:
> Actually, compiling the aufs modules is not really straight
> forward since one needs the right combination of aufs sources and
> kernel sources. I took the debian patched 2.6.26 kernel sources and
> the 0
On Wed, Jan 14, 2009 at 12:04:55PM +0100, Thomas Lange wrote:
> > On Wed, 14 Jan 2009 11:39:46 +0100, Henning Fehrmann
> > said:
>
> > Actually, compiling the aufs modules is not really straight
> > forward since one needs the right combination of aufs sources and
> > kernel
e to give a parameter to the live scripts inside
initrd to specify the network device. Let me see:
# man 7 live-initramfs (inside the nfsroot)
.
.
ip=[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:[DEVICE]:[AUTOCONF]
[,[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTN
Hi all,
I've tried to upgrade a FAI server from 3.1.8 to 3.2.4. Not
surprisingly, things didn't work any more. After a while, I started from
scratch, installing FAI and related packages and building a new nfsroot.
Still, FAI does not work, and there are two points that worry me:
- The nfsroot l
Hi Thomas,
Before discussing your problems further, please make sure you read this:
http://faiwiki.informatik.uni-koeln.de/index.php/FAI_3.2_on_Etch
Please let me know of that makes things work for you - I authored this
page and want to complete it if some things are missing.
And surely some of
like to vote for some
enhancements of the docu, for people like me who like to have everything
explained in detail. :-)
Necessary packages:
Since live-initramfs, live-helper and unionfs seem to be crucial for FAI
3.2, all three should be mentioned, also in the FAI guide. Actually they
should be
Hi,
I'm having the following issue when booting fai 3.2.4 with kernel
2.6.24. The boot seems to go fine, intializes all interfaces and
hardware correctly but the moment after mounting the nfsroot and
bringing up the network interface I get dropped into a shell like this:
bnx2: eth0: using MSI
bnx
Roel van der Made a écrit :
Hi,
I'm having the following issue when booting fai 3.2.4 with kernel
2.6.24. The boot seems to go fine, intializes all interfaces and
hardware correctly but the moment after mounting the nfsroot and
bringing up the network interface I get dropped into a shell like th
On Wed, 2008-01-30 at 17:06 +0100, Castang Jerome wrote:
> Roel van der Made a écrit :
> > Hi,
> >
> > I'm having the following issue when booting fai 3.2.4 with kernel
> > 2.6.24. The boot seems to go fine, intializes all interfaces and
> > hardware correctly but the moment after mounting the nf
uot;live" script you need to
add the BOOTIF parameter like this:
BOOTIF=*)
BOOTIF="${ARGUMENT#BOOTIF=}"
export BOOTIF
;;
After updateing the initramfs inside the chroot and copying after that
the initrd.img for the used install boot kernel int
pxelinux to catch exactly that interface, we were
> sure that our DHCP infrastructure is working (we are doing some dhcp
> relay configs inside our network).
[...]
> I'm thinking, that udhcpc is a better solution for dhcp requests inside
> (live) initramfs and we should try to go
t;
> [...]
>
> > I'm thinking, that udhcpc is a better solution for dhcp requests inside
> > (live) initramfs and we should try to go that way.
>
> > I don't know what it needs to start the discussion with initramfs
> > upstream (or the linux plumbers) but we
15 matches
Mail list logo
