[syslinux] syslinux-3.36 and 3.35 compilation broke /dev/null

Steve Brown sbrown7 at umbc.edu
Mon Feb 12 06:20:57 PST 2007


On Mon, 12 Feb 2007, Gilles Espinasse wrote:

> It's necessary on ipcop actually.
> We have a master script that compile 182 scripts and they mix files loading,
> compilation and installation.
> After toolchain compilation, everything is made in a chroot, so it should
> not break the running machine.
>
> I discover the problem only after installing the resulting image because
> some errors were printed when send to /dev/null and sshd-4.5p1 failed to
> start with a cryptic message
> fatal: daemon() failed: Success
>
> Concerning environnement, we have two flavors:
> - the oldest is gcc-3.3.3, binutils-2.15.90.0.3, make-3.80
> - the most recent is gcc-3.4.5 , binutils-2.16.1, make-3.80
> Both show a broken /dev/null

Is there a /dev/null in your chroot environment?

Steve Brown
sbrown7 at umbc.edu




More information about the Syslinux mailing list