- Where is the corresponding directory of DRBL client in server ?
^TOP^
| | It's in /tftpboot/nodes/$IP, where IP is the client's IP address, like /tftpboot/nodes/192.168.0.1.
There are directories:
dev etc root var
under /tftpboot/nodes/$IP.
For common root directory it's in /tftpboot/node_root, where all clients share this same one directory.
|
- How can I append boot time parameters of the Linux kernel to DRBL clients ?
^TOP^
| | You can modify the
/tftpboot/nbi_img/pxelinux.cfg/default
It's almost similar to grub syntax. And if you are familiar with syslinux, it's the same thing.
Say, if you want to append "vga=791" for client, you can find the "label drbl", and modify or append the "append" like
------------
append initrd=initrd-pxe.img ramdisk_size=12288 devfs=nomount drblthincli=off selinux=0 vga=791
------------
|
- How can I debug in the PXE initrd when client boots ?
^TOP^
| | In the early stage in PXE initrd when client boots, there is NO log file. However, you can try to debug by:
1. edit /usr/lib/mkpxeinitrd-net/initrd-skel/linuxrc
or
"/usr/lib/mkpxeinitrd-net/initrd-skel/linuxrc/udhcpc-post"
insert some code to debug, or just put a shell (/bin/sh) so you can enter the shell.
2. run "/opt/drbl/sbin/mknic-nbi" to generate the PXE initrd.
3. reboot the client, then you can see some logs or enter the shell.
|
- In Debian Sarge, how can I let every normal user in DRBL client to access sound devices and automatically mount USB disk ?
^TOP^
| | You have to add those desktop user to group "audio" and group "plugdev". Since the default group for plugdev and audio is not open to every user, you can add them in very client's /etc/group:
1. For USB disk, like:
-------
plugdev:x:46:john, mary
-------
2. For sound, like:
-------
audio:x:29:john, mary
-------
Note!, due to the NIS/YP limitation, you can not add it in server and "make -C /var/yp" to update. NIS/YP only works in GID >= 1000 in Debian. In this method, you have to edit every /etc/group in every client.
If you are really lazy, here you are, but it not so secure...
For sound:
a. append these in /etc/udev/permissions.rules
-------
KERNEL="dsp", MODE="0666", GROUP="root"
KERNEL="mixer", MODE="0666", GROUP="root"
-------
or
b. chmod 777 /dev/dsp /dev/mixer
For USB disk:
Here is the method that you do not have to append every user to group "plugdev" in client's /usr/group:
1. In server, change the /etc/group as:
-------
plugdev:x:1100:john, mary
-------
Note, the GID must be unique and must be >= 1000
2. chgrp plugdev /usr/bin/pmount
3. make -C /var/yp
4. make sure /usr/bin/pmount is setuid, if not, chmod u+s /usr/bin/pmount
5. comment every plugdev in every client /etc/group, like:
-------
plugdev:x:46:john, mary
-------
6. logout client, and login in. It should be ok now.
|
- How can I start a service (like cron, sysklogd, klogd...) of DRBL clients in server ?
^TOP^
| | Only some necessary services of DRBL client are on, so if you need more services, like cron, sysklogd, klogd..., then:
In DRBL server, take service "cron" as an example, run:
/opt/drbl/sbin/drbl-client-service cron on
Then
(1) Reboot the clients, or
(2) Run /opt/drbl/bin/drbl-doit -u root "/etc/init.d/cron start"
if clients are already on.
|
- How can I run vmplayer in DRBL client machine ?
^TOP^
| | Here we take vmware-player 1.0.0-19317 as an example, and this method only works in the CPU arch matches each other in the server and client:
0. Make sure client's kernel is same with server, i.e.
For server, "uname -r"
For client, "cat /tftpboot/nbi_img/kernel_version_in_initrd.txt"
These two must match each other.
The CPU arch must be the same, too.
For server, "uname -m"
For client, "cat /tftpboot/nbi_img/client_kernel_arch.txt"
These two must match each other.
If not, you have to run "/opt/drbl/sbin/drblsrv -i" again, and let kernel of
client is same with that of server, or reinstall the kernel in the server to make it same with that in client.
1. wget http://download3.vmware.com/software/vmplayer/VMware-player-1.0.1-19317.i386.rpm
Or get the in http://www.vmware.com
2. sudo rpm -Uvh VMware-player-1.0.1-19317.i386.rpm
3. sudo vmware-config.pl
4. sudo /opt/drbl/sbin/dcs , then choose "others" -> re_deploy
or
run "/opt/drbl/sbin/drblpush -i" again.
5. Just in case, remove the file /etc/vmware/not_configured in every client by:
sudo /opt/drbl/sbin/drbl-rm-host /etc/vmware/not_configured
6. sudo /opt/drbl/sbin/drbl-client-service vmware on
7. If client is already on, you can run
sudo /opt/drbl/bin/drbl-doit "/etc/init.d/vmware start"
or
reboot the client
8. login client, run vmplayer
The principle is:
(a) The client must have the modules "vmmon" and "vmnet" that vmware need, and they exist in /tftpboot/node_root/lib/modules/2.6.9-22.0.1.EL/misc.
(b) The file "/tftpboot/nodes/$IP/etc/vmware/not_configured" should not exist if well configured (by vmware-config.pl).
|
|