<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Thomas,<br>
yes, I thought that it is required or at least better to have a
matching nfsroot (wheezy nfsroot for wheezy, ubuntu nfsroot for
ubuntu).<br>
Maybe this is not really the case... <br>
<br>
Just now I suceeded to start the first FAI-installation using a
Ubuntu/Trusty nfsroot.<br>
<br>
I had quite some problems to solve: <br>
- I had to chmod /srv/tftp/fai_ubuntu/initrd... from "-rw------"-
to "-rw-r--r--" (seems to be a known problem)<br>
- unfortunately I had to replace dracut with liveboot (there seem to
be some already known incompatibility issues between dracut and
initramfs on ubuntu)<br>
- I had to adapt the PXE-config file like this: (to be able to boot
into nfsroot)<br>
------------<br>
<small># generated by fai-chboot for host ... with IP ...<br>
default fai-generated<br>
<br>
label fai-generated<br>
kernel vmlinuz-3.13.0-30-generic<br>
append initrd=initrd.img-3.13.0-30-generic ip=dhcp <b>nfsroot=130.92.143.73:/srv/fai/nfsroot_ubuntu</b>
boot=live <b>netboot=nfs</b> FAI_FLAGS=verbose,sshd,createvt
FAI_CONFIG_SRC=nfs://phkup26/srv/fai/config_ubuntu
FAI_ACTION=install</small><br>
-------------<br>
<br>
Now my installation fails when it tries to extract the base file,
which is in my case $NFSROOT/var/tmp/base.tar.xz instead of
$NFSROOT/var/tmp/base.tgz (to be detected by task_extrbase).<br>
Ill maybe try to convert it.<br>
<br>
However because the FAI-version used on ubuntu seems to be quite old
(3.4.8. , I had even to change the DISK configuration back to old
format :-( ), I fear that there will be a whole bunch more of
problems due to FAI backwards-compatibility issues, as I used my
wheezy config-files as a base.<br>
<br>
=><br>
Probably I 'll better try to use the wheezy nfs-root also for
Ubuntu, allowing me to use dracut and an actual fai version<br>
<br>
Just a final question: can I use the
<a class="moz-txt-link-rfc2396E" href="http://fai-project.org/download">"http://fai-project.org/download"</a> also for Ubuntu 14.04/trusty? (I
remember having heard something in former e-mails)<br>
<br>
Regards<br>
René<br>
<br>
<div class="moz-cite-prefix">On 07/07/2014 02:48 PM, Thomas Neumann
wrote:<br>
</div>
<blockquote cite="mid:1473528.3uYzYJrxsC@codemonkey" type="cite">
<pre wrap="">On Monday 07 July 2014 11:05:11 René Bleisch wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I already have a FAI-server for my workstations (wheezy). Now I'm trying
to setup an additional FAI-server for my servers (Ubuntu Trusty).
</pre>
</blockquote>
<pre wrap="">
Why do you want to set up 2 different servers in the first place? To create the
matching nfsroot to install a matching OS?
There's actually nothing that prevents you from installing OS 'abc' from an
nfsroot with OS 'def'. It's not the default and there are some assumptions in
FAI that need to be circumvented (like copying sources.list from the nfsroot
to the newly installed OS.)
There's not even a need to have a separate 32 and 64bit nfsroots as long as
the client is able to boot a 64bit OS.
You may run into problems if the nfsroot's debootstrap is unable to create the
target OS base install, but that can be avoided by preparing a suitable
"base.tgz" (it's just the tarred debootstrap result). [Btw. using suitable a
base image makes it possible to install RedHat and SuSE via FAI.]
bye
thomas
</pre>
</blockquote>
</body>
</html>