> hello all,
> i ran the fai-setup, and it was fine.
> however, in fai guide there is written that "it needs more than 390MB MBtes
> disk space" and my fai-setup has just 302MB of data.
> i hope there is no problem with the setup.
>
Did you notice any error messages? If not, you should be fine. M
Hello,
I am a little confused ATM. What is the correct way to install a
different kernel (than installed on the fai-server) on a client.
We have a setup with dhcp, tftpd and pxe. If I set another kernel in the
pxelinux.cfg/XXX file, everything works fine. In the very last steps
of the client
Uwe Kastens wrote:
> Hello,
>
> I am a little confused ATM. What is the correct way to install a
> different kernel (than installed on the fai-server) on a client.
Make an entry for the different kernel package in your software package
lists - but see below.
> We have a setup with dhcp, tftpd an
Hello,
We need to patch grub-install each time we build nfsroot new. Anybody
else with this problem?
debian lenny
*** /srv/fai/nfsroot/live/filesystem.dir/usr/sbin/grub-install.orig
2009-02-06 13:39:42.0 +0100
--- /srv/fai/nfsroot/live/filesystem.dir/usr/sbin/grub-install
2009-02-06 13:4
> Hello,
>
> We need to patch grub-install each time we build nfsroot new. Anybody
> else with this problem?
>
> debian lenny
>
[...]
Yes, see here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513216
(with exactly the same bugfix). Apparently you can safely ignore this error.
Best,
Mic
[...]
>
> The error message is the following (full log is at
> http://paste.debian.net/34215/)
>
The uninitialized stuff warnings indicated some bugs that I need to look into,
but that doesn't seem to be the showstopper.
>
> Executing: /lib/udev/vol_id -u /dev/sda2
> Command /lib/udev/vol_id -u
Michael Tautschnig a écrit :
Executing: /lib/udev/vol_id -u /dev/sda2
Command /lib/udev/vol_id -u /dev/sda2 had exit code 4
Failed to obtain UUID for /dev/sda2
I originally wanted to have one swap slice on each disk, but in this
case the error is on the sdb swap partition:
Executing: /lib/ud
[...]
>>
>> So, mysteriously, that information is lost afterwards. Hmm, looking at the
>> code
>> of vol_id it seems that parted might have overridden the volume id for
>> /dev/sda2 (instead of /dev/sda1 or /dev/sda3). Could you re-run that failing
>> installation and, once it aborts, do
>>
>> par
Michael Tautschnig a écrit :
[...]
So, mysteriously, that information is lost afterwards. Hmm, looking at the code
of vol_id it seems that parted might have overridden the volume id for
/dev/sda2 (instead of /dev/sda1 or /dev/sda3). Could you re-run that failing
installation and, once it abor
> Michael Tautschnig a écrit :
>> [...]
>>
So, mysteriously, that information is lost afterwards. Hmm, looking at the
code
of vol_id it seems that parted might have overridden the volume id for
/dev/sda2 (instead of /dev/sda1 or /dev/sda3). Could you re-run that
failin
Michael Tautschnig a écrit :
Michael Tautschnig a écrit :
[...]
So, mysteriously, that information is lost afterwards. Hmm, looking at the code
of vol_id it seems that parted might have overridden the volume id for
/dev/sda2 (instead of /dev/sda1 or /dev/sda3). Could you re-run t
11 matches
Mail list logo
