On Fri, Apr 8, 2011 at 2:16 PM, Klaus Knopper
<debian-knoppix@knopper.net> wrote:
Hi Gilles,
Sorry about the late answer, well, you know me... ;-)
> 1) How do you compile and run 64 bits code ? (after using "knoppix64" as a boot parameter)
It does not matter whether you started with the 32bit or the 64bit
kernel. If you want to create 64bit executables on a 32bit host (binary)
system, you will be cross-compiling.
You need to install the 64bit GCC development libraries (be careful not
to overwrite your system libs, though), and set -m64 for gcc
additionally to LD_LIBRARY_PATH for the 64-bit libs.
[GvR] Thanks for the tip, I will give it a try. (I am used to cross-compile for ARM using CodeSourcery)
I just thought that a 64bit host was required to compile for 64 bits binaries.
Btw, Knoppix dual boot with both a true 32bits and true 64bits system would be just fantastic !
> 2) Could you please consider removing the legacy support
> in the the 64 bits kernel for speed improvement ?
Do you mean 32-bit support for the 64 bit kernel? But then, Knoppix will
no longer run, since all the programs are still 32bit. I cannot install
both a 32bit and a 64bit system in parallel.
Is there really a noticeable difference in speed if "legacy support" is
enabled?
[GvR] Ok I understand, please forget it.
> 3) Could you please compile the kernel to allow for more than 8 cloop files ?
How many do you need?
[GvR] Unless there is a kernel memory issue it would be desirable to have 32 cloops.
I use a lot of them to patch at boot time your great DVD and add extra features as:
ARM cross-compile, Coverity, Zenoss, VmWare workstation & tools and other proprietary softwares.
> 4) Could you please compile the kernel to allow for more than 8 processor cores ?
> (the i7-980X has 12 and more are coming soon)
I'm not sure if this would not cost additional memory and resources if
there are LESS than the specified cores. The kernels documentation
suggests that adding support for mode CPUs will increase the kernels
memory consumption somewhat.
What's you proposal for the right maximum cpu core value? 32, or rather 16?
[GvR] It looks like that 32 processors/cores should be enough to cover for the next two years
as 24 cores are already in the pipe of some vendors for this year. If you have such a system
and use the 64bits kernel most likely the memory (including the cache) should not be a problem.
> 5) How to change (or restore) a soft link date/time ?
> (to create an exact replication of a file tree, cp, tar, rsync do not work, is this a bug ?)
knopper@eeepc:~$ ln -s 1 2
knopper@eeepc:~$ ls -l 2
lrwxrwxrwx 1 knopper users 1 8. Apr 23:09 2 -> 1
knopper@eeepc:~$ cp -a 2 3
knopper@eeepc:~$ ls -l 2 3
lrwxrwxrwx 1 knopper users 1 8. Apr 23:09 2 -> 1
lrwxrwxrwx 1 knopper users 1 8. Apr 23:09 3 -> 1
Apparently, cp -a DOES copy the symlinks date/time correctly.
Can you give me an example where cp -a did not work?
[GvR] I have a different result (assuming you wait long enough to have a minute change between the commands):
This is a problem when using rsync update after tar (backup recovery) as the recovered links are always newer than the original !
# touch 1
# ls -l 1
-rw-r--r-- 1 root root 0 Apr 11 01:29 1
(wait until next minute)
# ln -s 1 2
# ls -l 1 2
-rw-r--r-- 1 root root 0 Apr 11 01:29 1
lrwxrwxrwx 1 root root 1 Apr 11 01:30 2 -> 1
(wait until next minute)
# cp -a 2 3
# ls -l 1 2 3
-rw-r--r-- 1 root root 0 Apr 11 01:29 1
lrwxrwxrwx 1 root root 1 Apr 11 01:30 2 -> 1
lrwxrwxrwx 1 root root 1 Apr 11 01:31 3 -> 1
[GvR] 6) Since the new forum have all the internal references (links) broken,
is it possible to make a snapshot of the old forum so it can be used for reference ?
[GvR] 7) I did find some new problems with the AUFS (which I did not have with UNIONFS):
When adding a ramdisk as the last layer to an existing AUFS stack of cloops & ramdisk
(to get the deltas in the new Ramdisk as an example, as the process to create a new cloop)
the new data is still partially copied into the first Ramdisk (and not in the last Ramdisk layer as it should)
Setting the first Ramdisk as read-only force AUFS to write all the new data into the new Ramdisk
but this (setting the first Ramdisk to read-only) does not work during the Knoppix boot process.
This is not an issue of running it as an other process as all the command are run from init (process id 1)
Any suggestion ? Do you experience the same issue ?
> When is the next
> version available for download ? (not everybody have access to Linux
> Magazine)
I know... :-(
As always, I will need some time to evaluate feedback from 6.5, add some
changes (including some of your proposals), and prepare the CD version
as well. So, probably not before May.
> If you are interested I have customized the init boot script and
> minirt.gz to add functionalities suh as: boot from iso on hdd (for speed),
> pxe boot from iso on a samba or nfs share, data persistence stored in a
> partition,...
Great! Please send me your script and let me know if I can use it in
parts or in total under the conditions of the GPL V2.
[GvR] Please find all the data in the Knoppix Forum and as far as I know all of it could be used as GPL V2.
(The data is either coming from your Knoppix DVD or scripts I created or modified from your DVD.
Regards
-Klaus