problems with current iso

[Jean-Michel Brünn]

Hello,

i had two bigger problems, installing the current lunar iso, here's a report just
in case someone is interested. As it's a "fresh install" please don't come arround
with "i think that's wdps setup" - many other ppl doing a fresh install with the
current iso will have to fight with exact the same problems:

--- problem one
i had yesterday a little problem with coreutils-6.12. Typing "touch something"
gave out a "Function not implemented" error, downgrading to 6-11 helped.
v4hn reported the same error two days ago.

After upgrading everything today, coreutils-6.12 works without problems, it
seems that this error is related to having-old-dependecies.

People installing the current lunar ISO (1.6.1) will have the same problems:
	after first booting the box and doing a lunar renew, and so
	after the first lin of coreutils-6.12, many lin's (configure, make,
	whatever) using "touch" will most likely abort/fail because of that
	error.

	I can't say which module needs to be compiled first, maybe someone
	will try to reproduce it - install the iso, boot it, do:
		lin moonbase; lin theedge; lunar renew and watch after it compiled
		coreutils.

--- problem two
Another Problem exists with udev. After booting a fresh install and doing a
lin moonbase; lin theedge; lin -cr udev - udev will fail because it's missing a
file from glibc-2.7: "bits/syscall.h" like seen here:
	http://nopaste.tshw.de/12124777900394e/
doing as Moe suggested, copying syscall.h from /usr/include/ to
/usr/include/sys/ brings up the following error:
	http://nopaste.tshw.de/12124779690394e/
only an upgrade from glibc-2.3.6 to glibc-2.7 helps. Because of this problem,
your shiny new compiled kernel will not boot up with udev, because udev is not
creating the devices correctly. You can only boot with one default kernel from
the lunar iso - so you need to recompile glibc before you can compile an
actual self-made kernel.

Cheers
Jean