Debian is
> usually quite good.
Debian-based FAI cannot build Ubuntu intrepid or jaunty systems; the
boot from the NFS root fails. That's due to the initramfs-tools and
live-initramfs problems.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
Henning Sprang writes:
> Russ Allbery wrote:
>> Debian-based FAI cannot build Ubuntu intrepid or jaunty systems; the
>> boot from the NFS root fails. That's due to the initramfs-tools and
>> live-initramfs problems.
>
> But that happens only when you try t
t of debootstrap. The base tarball doesn't need
to have anything special installed in it; only the NFS root has special
package requirements. So you can just run debootstrap for your desired
distribution and then tar up the results and use it as the base.tar.gz for
FAI.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
Frédéric Boiteux writes:
> Russ Allbery a écrit :
>> But to add a bit more to that, in case you don't want to run
>> make-fai-nfsroot for one of the distributions you nonetheless want to
>> build, yes, it's the output of debootstrap. The base tarball doesn
"Thomas Neumann" writes:
> P.S.: It may be necessary to add bnx2 to /etc/initramfs-tools/modules
> prior to updating the initrd. I'm not sure.
It shouldn't be if /etc/initramfs-tools/initramfs.conf has MODULES=most.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
class specified.
> Am I missing something obvious?
Are you configuring your pins properly in the apt configuration that gets
installed during the FAI build process before packages are installed? The
above will only work if backports is pinned at a lower priority and hence
not preferred w
command can check the IP address that's connecting, map that to the
appropriate keytab, and then cat the keytab to stdout, marking it as
having been installed so that this step can't be done more than once
without an intervening system build.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
loader. /proc/cmdline on the system shows the
contents of append from above, so that part is also working.
Does anyone have any ideas what might be going wrong?
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
P address became necessary.
> Correction: the latter applies to wheezy, not squeeze.
Oh! I'll try that tomorrow. But it's supposed to default to next-server
from the DHCP reply; I assume that's no longer happening?
Thanks for the help!
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
Russ Allbery writes:
> Toomas Tamm writes:
>> On Fri, 2013-06-07 at 11:56 +0300, Toomas Tamm wrote:
>>> TFTP server. In squeeze, however, it (dracut) defaults to the DHCP
>>> server's IP address. In my setup, the DHCP server is separate from the
>>> TFTP
command line of the newly-installed system, whether missing the
serial console configuration or using the wrong speed, etc. The system is
booting, just sending all the messages off into never-never land.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
nt
packages? It would be nice to get this fixed permanently so that FAI can
just depend on new-enough versions of the other packages.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
is a
> bug,... but someone will have to track which mount call does the bad
> job, if it is a dinamic mount (What's the dinamic mount's package ) or
> an static mount (busybox). Or is it maybe a ld bug?
As I recall, this was the problem that the ld.so.cache file was out of
that the firmware is included in the initrd images of
all of your boot kernels, both for PXE and after installation.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
14 matches
Mail list logo