Unique Hostname

[A.Skwar]

It would be very nice and useful, if the hostname of the Knoppix box would be unique. This would allow, that there are several Knoppix hosts running on the same net. Currently, if dynamic dns and DHCP is used, only the first "knoppix" host gets added to the DNS.

One easy way would be, to add the MAC adress of the 1st NIC to hostname (without the : of course). This would make the hostname look something like "knoppix-0008743EFDE2".

[amp77]

I would prefer a cheatcode. By the way, how do you change the hostname? hostname command doesn't seem to be enough as i still can't samba between two Knoppix boxes

[The-Big-E]

I would prefer a cheatcode. By the way, how do you change the hostname? hostname command doesn't seem to be enough as i still can't samba between two Knoppix boxes

Why would you use samba between 2 knoppix boxes? why not ssh or nfs?

[A.Skwar]

Why would you use samba between 2 knoppix boxes? why not ssh or nfs?

That's not the point at all.

A possible scenario might be, that there are 2+ knoppix boxes and one or more Windows machines. How do you access one specific Knoppix box using CIFS/SMB from the Windows machine?

[The-Big-E]

That's not the point at all.

A possible scenario might be, that there are 2+ knoppix boxes and one or more Windows machines. How do you access one specific Knoppix box using CIFS/SMB from the Windows machine?

I understand, but enable ssh on 1/both/all knoppix boxes, then access them via putty or winscp to the IP. The only time I found the hostname to be really important (at least when using live cd's and interacting with windows boxes) is when using cups.

What are you trying to do that you would need more then I live cd running at a time anyway?

[Harry Kuhman]

What are you trying to do that you would need more then I live cd running at a time anyway?
I agree that accessing by IP address is a work around, although hardly a great one. I can certainly think of lots of reasons to run with more than one Live CD though, in fact any reason to run with one Live CD would be a good reason to run with more than one. And if you want to learn about Linux networking before ditching your Windows network, it an obvious choice. Other reasons: Transfering files without having to deal with Linux to Windows issues, debugging network problems with ethereal, playing multiplayer games like Crack Attack on the 4.0.2 DVD across the local network.

[A.Skwar]

What are you trying to do that you would need more then I live cd running at a time anyway?

You're again missing the point. The current state of behaviour can very well be seen as a bug that needs to be fixed. The way it is now, it's *NOT* possible to access one specified box using a name. You have to know the IP.

That's not easy. And up to know, Knoppix to me always made the impression, that it's an implmentation of "It Just Works!".

But you're right, accessing by IP is a workaround. Could you please file a bug, so that the DHCP Client doesn't try to register the hostname in DNS? Also, please try to do away with all that auto configuration. Heck, you just need to enter the correct hardware data by hand. Hardly a big deal...

[bitey]

I'm glad somebody mentioned using the IP address. I've been going nuts trying to use LinNeighborhood and smb4k to connect a Knoppix client to a Knoppix file server. Turns out typing smb://192.168.1.107 into Konqueror works just fine.

[A.Skwar]

I'm glad somebody mentioned using the IP address. I've been going nuts trying to use LinNeighborhood and smb4k to connect a Knoppix client to a Knoppix file server. Turns out typing smb://192.168.1.107 into Konqueror works just fine.

Yes, it does - but in Windows, this might result in Windows putting/assuming the server to be in the Internet Zone and thus be more restrictive. Further, it may slow down transfers.

Not so, if you use the NETBIOS name - ie. \\KNOPPIX instead of \\192.168.1.107. So, IP isn't really a solution.

All of this would work fine, if each Knoppix box had a unique hostname. Quite a simple solution for a lot of problems...

[firnsy]

I have this exact type of setup with my remaster, I have built a custom IDS solution with distributed sensors, central server (with redundants) and remote consoles. On boot up I added a cheatcode 'hostname' that determines the type of role that the machine will perform. This type of functionality, I believe, is what some of you are after.

If so you can easily achieve this with only a few extra lines of code to the linuxrc file in miniroot.gz

If anyone is interested I'll post some possible modifications to achieve this functionality. Fortunately this type of modification should not require a complete remaster and could be tackled by the novice Knoppix tinkerer.

The proposed modification would be:
1. Instead of standard 'Knoppix' hostname, it would be be something like 'knoppix-MACADDRESS'
2. If cheatcode is supplied override hostname (eg. boot: knoppix 'hostname=knoppix-1')

[trevmar]

Firnsy,
Can you please post or send the modification to the init script? And also let me know how I integrate it with the Knoppix DVD image? I have two machines side by side, each running molecular modeling software with Knoppix as OS, and it is a pain rebooting, as I have to 'su' then 'hostname Athlon64' BEFORE I start Samba. That does work for me, however, and it allows the Windoze boxes to see seperate machines on the network neighborhood.

[ruymbeke]

Firnsy, Can you please post or send the modification to the init script?
Same request: could you please post your update of linuxrc ?
I would like to add this functionality in my initrd_iso.gz ramdisk boot file.
I can obviously reinvent the wheel but I am lazy by nature...
Thanks, Gilles

[ruymbeke]

Done !
I modified the linuxrc boot script to setup the hostname at boot time (kernel cheatcode: hostname=mymachine)
Please follow the link below to get the updated minirt_host.gz ramdisk file:
http://www.knoppix.net/forum/viewtopic.php?p=96827#96827
Please give it a try and give me some feedback.
Thanks,
Gilles

[firnsy]

Alternatively, I posted my patch in the Customising/Remastering section http://www.knoppix.net/forum/viewtopic.php?t=22301

It expands a little further by providing an autogenerating option which will append the MACADDRESS to at the end of the knoppix string.

[ruymbeke]

Alternatively, I posted my patch in the Customising/Remastering section http://www.knoppix.net/forum/viewtopic.php?t=22301
It expands a little further by providing an autogenerating option which will append the MACADDRESS to at the end of the knoppix string.
Thank you very much !
I will try to add your macaddress hostname option when I have some time.

The solution I have chosen do not require a remaster of the 689MB KNOPPIX file
but only the use of the new 2.4MB minirt_host.gz boot ramdisk.
It will work "as is" with the official KNOPPIX file or the official Knoppix ISO cd/dvd image.
cf: http://www.knoppix.net/forum/viewtopic.php?p=96827#96827

Technical description:
==============
The trick was to find a way (using the linuxrc boot script) to have
the hostname updated way after the end of the execution of the linuxrc boot script
and after the end of the execution of the knoppix-autoconfig auto detection script.
(The knoppix-autoconfig script is responsible for the hardcoded knoppix hostname)
The knoppix-autoconfig script file being located within the 700MB KNOPPIX file
an update of this file requires a remaster, which in my case, was not desirable.

To achieve this, the linuxrc boot script overwrite the content of the file /etc/hostname
with the hostname provided in the kernel command line (after the UNIONfs has been mounted)
Then, to force Knoppix to read this file after the linuxrc boot script and the knoppix-autoconfig
auto detection script have run and setup the machine hostname to the hardcoded knoppix name,
the linuxrc create a soft link (ln -s /etc/init.d/hostname.sh /etc/rcS.d/S01hostname.sh)
in order to have the init process to launch the execution of the hostname.sh script
which is used to update the machine hostname using the previously updated /etc/hostname file.
CQFD.

Best Regards,
Gilles

[ruymbeke]

Hello,
If someone is till interested in that, I now have added the option to use dynamic hostnames:
hostname=auto-clock -> knoppix-200512031753 (date+time)
hostname=auto-mac -> knoppix-123456789012 (eth0 mac address)
cf: http://www.knoppix.net/forum/viewtopic.php?p=96986#96986
Cheers,
Gilles

[Erick90022]

I love it do you not?:I:I

[trevmar]

ruymbeke,
I have changed the minirt.gz on my Knoppix 4.0.2 distribution DVD to your 25 Dec 2005 version of minirt-usb2.gz

when I give the boot string 'knoppix hostname=Athlon64' the system boots OK. The hostname is Athlon64

but Samba is awfully slow. If I select a volume from my Windows 2000 Pro machine it takes maybe 2 minutes to log in, and then another 2 minutes to show me files.

when I give the command 'su' I get the following error message:
'sudo: unable to lookup Athlon64 via gethostbyname()'

I guess I can live without su, but have you any idea what I can do to speed up the Samba access?

Thanks for all you are doing for the community,
Trevor

[firnsy]

ruymbeke,
I have changed the minirt.gz on my Knoppix 4.0.2 distribution DVD to your 25 Dec 2005 version of minirt-usb2.gz

when I give the boot string 'knoppix hostname=Athlon64' the system boots OK. The hostname is Athlon64

but Samba is awfully slow. If I select a volume from my Windows 2000 Pro machine it takes maybe 2 minutes to log in, and then another 2 minutes to show me files.

when I give the command 'su' I get the following error message:
'sudo: unable to lookup Athlon64 via gethostbyname()'

I guess I can live without su, but have you any idea what I can do to speed up the Samba access?

Thanks for all you are doing for the community,
Trevor

The reason for the error is that the /etc/hosts file does not have the machine name assigned to the local ip (127.0.0.1), from what I can determine, ruymbeke's method changes the hostname but does not modify the /etc/hosts file which is required.

[trevmar]

Yes, of course, Firnsy, thanks for reminding me :)
I will set up the hosts file manually for now

Thanks again :)

[trevmar]

Arrrgh - /etc/hosts is a read-only filesystem :) (LOLOL...weeping...)

[ruymbeke]

The reason for the error is that the /etc/hosts file does not have the machine name assigned to the local ip (127.0.0.1), from what I can determine, ruymbeke's method changes the hostname but does not modify the /etc/hosts file which is required.
Good catch, Thanks ! I will fix it asap...
Gilles

[ruymbeke]

Hello,
Please find the bug fix minirt_usb3.gz (/etc/hosts updated with hostname) in here:
http://www.knoppix.net/forum/viewtopic.php?p=98906#98906
I would apreciate some feedback...
Best Regards,
Gilles

[trevmar]

Gilles,
Yes, that works fine. I created new 4.0.2 DVDs with the new minirt file. I now have quick access to each of the Knoppix servers on my Windoze network. Previously it was lethargic and painful to have more than one server running at a time.

Thanks again to everybody.

..Trevor...