/usr/share/gnome/help/ltsp/C/savedinfo.xml is in ltsp-docs 1.2-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 | <!-- FIXME:
commented out. This info should probably move to a wiki page. Not
suitable for LTSP upstream documentation, as it's too distro specific.
Or, we could create a secondary "tips and tricks" document. Either/or,
this shouldn't be here.
<sect1>
<title>Setting up LDAP for thin clients</title>
<para>
There are 2 scenarios possible here, either you are setting
up authentication on the server itself, or making a fat client
so authentication happens in the client chroot. If you are not
on Ubuntu or Debian, replace apt-get with the distro specific
package management software. The steps below are required to
make it work:
</para>
<screen>
apt-get install auth-client-config libpam-ldap libnss-ldap nano nfs-common ldap-utils
</screen>
<para>
Then do:
</para>
<screen>nano /etc/ldap.conf</screen>
<para>
this should be edited according to your ldap settings so
change:
</para>
<screen>host 127.0.0.1</screen>
<para>
to
</para>
<screen>host LDAP_SERVER_IP</screen>
<para>
and change
</para>
<screen>base = padl.....</screen>
<para>
to
</para>
<screen>base = dc=yourdomain,dc=local</screen>
<para>
You also need to edit
<filename>/etc/ldap/ldap.conf</filename>
and make sure all the settings are changed to your ldap
server's settings. When you've done this you need to make sure
authentication happens via ldap first, like this:
</para>
<screen>nano /etc/auth-client-config/profile.d/open_ldap</screen>
<para>
and paste the following into it:</para>
<screen>
[open_ldap]
nss_passwd=passwd: ldap files
nss_group=group: ldap files
nss_shadow=shadow: ldap files
pam_auth=auth required pam_env.so
auth sufficient pam_unix.so likeauth nullok
auth sufficient pam_ldap.so use_first_pass
auth required pam_deny.so
pam_account=account sufficient pam_unix.so
account sufficient pam_ldap.so
account required pam_deny.so
pam_password=password sufficient pam_unix.so nullok md5 shadow
password sufficient pam_ldap.so use_first_pass
password required pam_deny.so
pam_session=session required pam_limits.so
session required pam_mkhomedir.so skel=/etc/skel/
session required pam_unix.so
session optional pam_ldap.so
</screen>
<para>
Now to activate that pam profile do the following:
</para>
<screen>auth-client-config -a -p open_ldap</screen>
<para>
You also have to edit /etc/pam.d/login and /etc/pam.d/gdm
and add the following line to the top of both files:
</para>
<screen>auth optional pam_group.so</screen>
<para>
And, perhaps this is necessary, perhaps, not, but it was
taken from another wiki someplace:
</para>
<para>
add the following to /etc/security/group.conf
</para>
<screen>
login;*;*;Al0000-2400;users,cdrom,floppy,plugdev,audio,dip
kdm;*;*;Al0000-2400;users,cdrom,floppy,plugdev,audio,dip,video
gdm;*;*;Al0000-2400;users,cdrom,floppy,plugdev,audio,dip,video
</screen>
</sect1>
-->
<!-- FIXME:
Removed as being too distro specific. Suitable for a wiki page.
<para>
To configure the share, install the
package <command>nfs-kernel-server</command>. Then, edit the
file <filename>/etc/exports</filename> and add the following
line, by replacing <command>secondary_server_ip</command> by
the real IP address of the server. /home
secondary_server_ip(rw,no_root_squash) After this
modification, the service needs to be restarted. sudo
invoke-rc.d nfs-kernel-server restart You can define the mount
point on each secondary servers, by editing the file <filename>
/etc/fstab
</filename>
and adding the following line: 192.168.0.1:/home /home nfs
hard,intr,rsize=8192,wsize=8192,bg 0 0
</para>
<para>
With the default setup, the home directory of the user must
exist before the first login. To create the home directory on
the fly on the first login, you can use the pam_mkhomedir
plug in. The NFS export option <command>no_root_squash</command> allows any secondary server to create directories on the primary server.
</para>
-->
<!-- FIXME:
Removed. Distro specific.
<sect1>
<title>Synchronization of packages</title>
<para>
Once you install one desktop application on one server, then
you must install it on all the other servers, as well.
Otherwise, users may not be able to use the same set of
applications. First, make sure that <command>
/etc/apt/sources.list
</command>
file is the same on each server. Then, list packages of the
reference server. Using the primary server for this purpose is
not recommended, since it may install other server packages
that are not necessary on secondary servers. To build the
package list: dpkg -get-selections deblist Then, copy this
file on the target server you want to sync applications, and
perform the following steps: sudo dpkg -set-selections <
deblist sudo apt-get dselect-upgrade Apt will install
additional packages that are not already installed on the
target machine.
</para>
</sect1>
-->
<!-- FIXME: Removed. Nothing to do with LTSP.
<chapter id='backup'>
<title>Backing Up</title>
<para>
Now that you have your LTSP server working, and are keeping it
updated, you're going to want to back up your users' data.
</para>
<para>
There are a variety of options available for external backup
media. SCSI tape drives, DVD RAM or ROM's, or even CD/R's may all
be used to back up your server on a regular basis.
</para>
<sect1>
<title>What needs to be backed up?</title>
<para>
When backing up a server, there are typically two
approaches:
</para>
<orderedlist>
<listitem>
<para>
Back up everything.</para>
</listitem>
<listitem>
<para>
Back up config files, and user data.</para>
</listitem>
</orderedlist>
<para>
We'll look at each briefly.</para>
<sect2>
<title>Back up everything</title>
<para>
Typically, by backing up everything, the administrator
is looking to do a restore of the entire operating system,
as well as user data.
</para>
<para>
Typically, you'll want to use a SCSI tape drive, and a
program like <command>amanda</command> (available in the
universe repository) to do this kind of backup strategy.
</para>
</sect2>
<sect2>
<title>Back up configs and data</title>
<para>
Backing up only config files and data is an acceptable
strategy for sites on a budget. On a typical LTSP system,
without a lot of customization, backing up the following
files and directories should capture most of what's on
your system. Following a disaster, you'll need to
re-install LTSP, re-install any programs you added, and
re-apply all updates. At that point, you can pull the
config files and user data from your backup.
</para>
<para>
Configuration Files
</para>
</sect2>
</sect1>
</chapter>
-->
<!--
Removed. Too distro specific, and not really LTSP related.
<sect1>
<title>Managing users with groups</title>
<para>
Managing users and groups should be done with the
distribution specific desktop tools on the server itself, but
can also be done from the command line:
</para>
<para>
To add a user using the shell, launch a terminal
(Applications -> Accessories -> Terminal) and type:
</para>
<screen>sudo adduser <username> </screen>
<para>
You should see something similar to the following, and then
a prompt to enter the password for the new user:
</para>
<screen>
Adding user `<username'> ...
Adding new group `<groupname'> (1007) ...
Adding new user `<username'> (1004) with group `<groupname'> ...
Creating home directory `/home/<username'> ...
Copying files from `/etc/skel' ...
Enter new UNIX password:
</screen>
<para>
Type in a password for the new user, and retype it when
prompted. You should then see:
</para>
<screen>
passwd: password updated successfully
Changing the user information for <username>
Enter the new value, or press ENTER for the default
Full Name []:
</screen>
<para>
Type in the user's full name (if desired). You may hit
<Enter> through any prompts you do not wish to fill in.
Hit Y to finish the creation of the new user when prompted if
the information you entered was correct.
</para>
<para>
To add the newly created user to a group simply type: </para>
<screen>
sudo addgroup <username> <groupname>
Adding user `<username'> to group `<groupname'> ...
Adding user <username> to group <groupname>
Done.
</screen>
<para>
You can also simply add a new group to the system by typing:
</para>
<screen>
sudo addgroup <groupname>
Adding group `<groupname'> (GID 1007) ...
Done.
</screen>
</sect1>
<sect1>
<title>Ending Misbehaving processes</title>
<para>
Sooner or later, you will have to deal with misbehaving
processes. Misbehaving processes are programs, utilities or
other software that stops, crashes or otherwise is not acting
as it normally should (one common example is if you launch the
Firefox web browser and it claims that it is already running,
though there is no Firefox window present for that user). A
Linux system administrator's job is to find and "kill"
(official Unix terminology) these processes. The concept of
killing misbehaving processes is the same across operating
systems -the difference is that in Linux environments,
misbehaving processes rarely bring the entire OS down with it.
</para>
<para>
We will explore two different ways to kill processes -one
with a GUI called "System Monitor" and one using the
shell.
</para>
<para>
Using the "System Monitor" GUI </para>
<para>
System Monitor is a graphical application that allows you to
view current running processes, system performance, and other
aspects of the system. You can launch System Monitor by
navigating System -> Administration -> System Monitor. The
first thing you will want to do is enable the viewing of all
user processes (Navigate to Edit -> Preferences and on the
Processes tab, under Information Fields click the check box
next to User). Click on Close and sort the processes under the
Processes tab by User. Find the misbehaving process of the
user, right-click on it and select End Process. This will
attempt to end the process with normal means. If this does not
end the process, right-click on the process again and select
Kill Process.
</para>
<para>
Using the shell
</para>
<para>
To kill a process(es) of a certain user using the shell, you
must first identify the name of the process. In this example,
we will assume the user's Firefox browser is misbehaving.
Launch a terminal (Applications -> Accessories -> Terminal)
and type:
</para>
<screen>ps w -u <username></screen>
<para>
Your output will look similar (but definitely not the same)
as this:
</para>
<screen>
PID TTY TIME CMD
5236 ? 00:00:05 gconfd-2
5336 ? 00:00:00 sshd
5337 pts/0 00:00:00 bash
5342 pts/0 00:00:00 sh
5345 ? 00:00:00 bash
5348 ? 00:00:00 ck-launch-sessions
5372 ? 00:00:00 ssh-agent
5376 ? 00:00:00 x-session-manager
5792 ? 01:03:19 firefox
</screen>
<para>
As you can see in the process list, there is a process
called firefox which is running. To kill this process, we use
the 'killall' command.
</para>
<screen>sudo killall -u <username firefox</screen>
<para>
Will kill all processes called 'firefox' running as the user
<username. We prepend this command with sudo so we run the
command as the root user, which has the privileges necessary
to kill other users' processes (other users cannot do this for
security reasons). Alternately, we can use the 'kill' command
to kill processes by process number:
</para>
<screen>sudo kill 5792</screen>
<para>
will kill process number 5792 (derived from the process list
above). Process numbers are unique across the system, so you
don't have to specify a user when running 'kill'. If you use
one of the examples above to end a process and it remains
(verified by another process listing), you might have to use a
switch to unmercifully kill the process (normal usage of
'kill' and 'killall' try to end the process politely -this
is the recommended route unless the process is persistent and
will not end by normal means). Simply append a switch to the
'kill' or 'killall' command to end it without remorse:
</para>
<screen>sudo killall -9 -u <username firefox </screen>
<para>
or </para>
<screen>sudo kill -9 5792 </screen>
<para>
For a more automated approach there is also a script that
helps with this called gnome-watchdog, which is available here
for download:
</para>
<para>
<ulink url="http://logicalnetworking.net/other/gnome-watchdog_0.9.2_i386.deb">
http://logicalnetworking.net/other/gnome-watchdog_0.9.2_i386.deb
</ulink>
</para>
</sect1>
</chapter>
<chapter id='managing-servers'>
<title>LTSP Server Management</title>
<para>
When logging onto the LTSP network as an administrator you will
sometimes find a bubble appear in the top right informing you that
there are updates available for your computer.
</para>
<para>
Any updates you apply here will automatically be applied to all
clients, though they may require a reboot. This is because LTSP
clients all use the same set of applications on the server. When
this prompt appears click the small red icon, and enter your
password to display the following application.
</para>
<para>
This application allows you to apply all available updates for
your computer quickly and easily. Clicking on the <emphasis>Check</emphasis> button,
checks to see if there are any more updates since the computer
last checked. If you are going to perform the updates, it's a
good idea to click this button. Once the check is completed,
you are ready to update your system.
</para>
<para>
Be sure to check how much information is going to be downloaded,
if you are low on bandwidth, or using a slow connection. Click on
the <emphasis>Update</emphasis> button, to set the computer
downloading and installing updates. Once clicked, if there are any
verification issues, these will be shown. If you are happy that
the packages come from a trusted source, you can click <keycap>OK</keycap>
to continue. First, your computer will download all available packages
and display a screen similar to that below.
</para>
<para>
After all packages have finished downloading, you will be
presented with the progress box, which shows how far the computer
has come in updating. If you wish you can click the word
<emphasis>terminal</emphasis>
to show more detailed information about the updates as shown
below.
</para>
<para>
After the updates have completed, the computer will inform you
if you need to restart in order for the updates to come into
effect. You can either shutdown when you wish, or click the small
blue icon in the top righthand corner, and you will be presented
with this question.
</para>
-->
<!--
Distro specific information removed, as it's a constantly moving
target. Distro's looking to provide a distro specific version of
this document for installation should insert specific instructions
in this section.
<sect2>
<title>Ubuntu LTSP - CD installation</title>
<para>
With the Hardy Heron (8.04.1) release the LTSP installer
functionality developed in Edubuntu was moved to the
Ubuntu alternate CD.
</para>
<para>
You can get the ISO from
<ulink
url="http://releases.ubuntu.com/releases/8.04.1/">http://releases.ubuntu.com/releases/8.04.1/</ulink>.
</para>
<para>
The installer will set up an out of the box working LTSP
install for you if your server has two network cards built
in.
If that is not the case it will tell you what to modify to
run with a single network card.
</para>
<para>
Once you boot up the CD, hit <keycap>F4</keycap>. The "Modes" menu will
pop up. Select "Install an LTSP Server". Now just move on
with the install.
</para>
<para>
Towards the end of the install the installer will start
to build the client environment from the packages on the
CD, which then will be compressed into an image.
</para>
<para>
If the installer is done and has rebooted into your new
system you will be able to boot your first Thin Client
right away.
</para>
</sect2>
<sect2>
<title>Ubuntu LTSP - Installing on an existing system</title>
<para>
You need to set up one static network interface where you
will attach the thin clients, install two packages and run
one command.
</para>
<para>
Configure your spare interface for the thin clients to
have the IP 192.168.0.1 (and make sure it is up and
running), then follow the instructions below.
</para>
<screen>
sudo apt-get install ltsp-server-standalone openssh-server
</screen>
<para>
Now create your Thin Client environment on the server
with:
</para>
<screen>
sudo ltsp-build-client
</screen>
<para>
If you are on a 64-bit system but your clients
have another architecture use the -arch option
e.g. <screen>sudo ltsp-build-client -arch i386</screen>
</para>
<para>
After that, you will be able to boot your first thin
client.
</para>
<orderedlist>
<listitem>
<para>
Note that if you want to use another IP than the
above, you need to edit the
<filename>/etc/ltsp/dhcpd.conf</filename>
file to match the IP values and restart the DHCP
server.
</para>
</listitem>
</orderedlist>
</sect2>
<sect2>
<title>Debian LTSP</title>
<orderedlist>
<listitem>
<para>
Download and install the latest Debian release.</para>
</listitem>
<listitem>
<para>
If you have a DHCP server already up and
running on your network:
</para>
<para>
<screen>apt-get install ltsp-server openssh-server</screen>
</para>
<para>
Otherwise, if you want your LTSP server to
function as the DHCP server:
</para>
<para>
<screen>apt-get install ltsp-server-standalone openssh-server</screen>
</para>
</listitem>
<listitem>
<para>
Build the LTSP client environment: </para>
<para>
<screen>ltsp-build-client</screen>
</para>
<para>
If you're installing a different Debian
distribution than what's on the server, you will
need to specify the -dist xxx command line option.
where xxx is your Debian distribution (e.g. lenny,
etch). See
<filename>/usr/share/debootstrap/scripts/</filename>.
</para>
<para>
ltsp-build-client will download a complete
Debian filesystem into
<filename>/opt/ltsp/i386</filename> (or specify
an alternate location with '-base') and install
the ltsp-client and ldm packages (the LTSP Display
Manager). Typically, you will need a desktop
environment like gnome or XFCE, or a window
manager such as IceWM installed on the server (NOT
in the chroot).
</para>
<para>
The 2 ltsp configuration files inside the client
are <filename>/etc/lts.conf</filename> and
<filename>/etc/default/ltsp-client-setup</filename>. See the examples
in <filename>/usr/share/doc/ltsp-client</filename>
</para>
<para>
See customizing thin client behaviour (note:
Debian LTSP still uses NFS by default).
</para>
<para>
If you change the IP data after you have done
the initial setup and run ltsp-update-sshkeys on
the server.
</para>
<para>
The files the client will boot are installed on
the server into/var/lib/tftpboot.
</para>
</listitem>
<listitem>
<para>
Configure
<filename>/etc/dhcp3/dhcpd.conf</filename>: </para>
<para>
See examples in
<filename>/usr/share/doc/ltsp-server/examples/dhcpd.conf</filename> or
<filename>/etc/ltsp/dhcpd.conf</filename> and adapt to your network.
</para>
<para>
Restart dhcp3-server: </para>
<screen>
invoke-rc.d dhcp3-server restart
</screen>
<para>
Alternately, configure
<filename>/etc/dnsmasq.conf</filename>:
</para>
<para>
See example in
<filename>/usr/share/doc/ltsp-server/examples/dhcpd-dnsmasq</filename>
and adapt to your network.
</para>
<para>
Restart dnsmasq: </para>
<screen>
invoke-rc.d dnsmasq restart
</screen>
</listitem>
<listitem>
<para>
Configure <filename>/etc/exports</filename>:</para>
<screen>
/opt/ltsp *(ro,no_root_squash,async,no_subtree_check)
</screen>
</listitem>
<listitem>
<para> Start <command>tftpd</command>. By default,
<command>tftpd-hpa</command> is started
from inetd. you may need to restart inetd after
installing <command>tftpd-hpa</command>.
</para>
<screen>
invoke-rc.d openbsd-inetd restart
</screen>
<para>
Alternately, edit
<filename>/etc/default/tftpd-hpa</filename> to have
<command>tftpd-hpa</command> start on it's own.
</para>
<screen>
RUN_DAEMON="yes"
</screen>
<para>
and restart <command>tftpd-hpa</command>
</para>
<screen>
invoke-rc.d tftpd-hpa restart
</screen>
</listitem>
<listitem>
<para> Boot a PXE or Etherboot capable machine and
enjoy. note that some older versions of Etherboot
do not support ELF images, and may not work
without additional configuration.
</para>
</listitem>
</orderedlist>
</sect2>
<sect2>
<title>OpenSuSE - Kiwi-LTSP</title>
<orderedlist>
<listitem>
<para>
Install the latest OpenSuSE dvd or cd image,
and during installation make sure your one or 2
card setup has the internal network's firewall
turned off and statically defined.
</para>
</listitem>
<listitem>
<para>.Then go to SuSE's LTSP web page:</para>
<para>
http://en.opensuse.org/LTSP
</para>
</listitem>
<listitem>
<para>
Use the first 1-click install link
</para>
<para>1-click installation will begin and might take
some time (125 MB+ download)
</para>
</listitem>
<listitem>
<para>
Once the installation completes, launch
"easy-ltsp" GUI as root
</para>
</listitem>
<listitem>
<para>
Select "prebuilt" image configuration from
KIWI menu.
</para>
</listitem>
<listitem>
<para>
Your LTSP server is ready once the
configuration process ends successfully.
</para>
</listitem>
</orderedlist>
</sect2>
<sect2>
<title>Fedora - K12Linux</title>
<orderedlist>
<listitem>
<para>
Install the latest version of Fedora (currently 9)
</para>
</listitem>
<listitem>
<para>
Make sure your system is up to date.</para>
<screen>yum update</screen>
</listitem>
<listitem>
<para>
Install the LTSP packages
</para>
<screen>yum install ltsp-server</screen>
</listitem>
<listitem>
<para>
You can:</para>
<screen>yum install ltsp-vmclient</screen>
<para>
if you want the
<command>qemu-kvm</command> PXE boot client launcher. Requires
hardware virtualization support or it will be very
slow and possibly unusable.</para>
</listitem>
<listitem>
<para>
Uncomment the option_cache_value line in
<filename>/etc/ltsp/ltsp-build-client.conf</filename> if you want to
keep a local cache of packages to be installed in
the client chroot. This might be useful if you
keep testing newer versions of ltsp-server and you
will be reinstalling the client chroot. Erase
<filename>/var/cache/chroot</filename> if you no longer need this
cache.
</para>
</listitem>
<listitem>
<para>
Update NFS <filename>/etc/exports</filename>
file.</para>
<screen>echo "/opt/ltsp *(ro,async,no_root_squash)" >>/etc/exports</screen>
</listitem>
<listitem>
<para>
Bring the network up with:</para>
<screen>ifup ltspbr0</screen>
<para>
This works fine for now, but after
reboot it might not start up automatically unless
you have service network running. NetworkManager
does not know how to bring up TYPE=Bridge devices.
You could enable service network with chkconfig
network on then rebooting (or do it manually).
service network will mostly co-exist with
NetworkManager until you need to plug in a real
client via Ethernet. See <ulink url="https://fedorahosted.org/k12linux/wiki/NetworkSetup">
NetworkSetup
</ulink>
for more info.
</para>
</listitem>
<listitem>
<para>
Restart services:</para>
<screen>for service in xinetd ltsp-dhcpd rpcbind nfs
sshd; do chkconfig $service on; service $service
restart; done
</screen>
</listitem>
<listitem>
<para>
Make sure services restart on reboot:</para>
<screen>for server in ldminfod nbdrootd nbdswapd tftp;
do chkconfig $server on; done
</screen>
</listitem>
<listitem>
<para>
Build the chroot:</para>
<screen>ltsp-build-client</screen>
</listitem>
<listitem>
<para>
Disable your firewall during these tests. It
will interfere with DHCP and other incoming
connections.
</para>
</listitem>
<listitem>
<para>
At this point ltsp-vmclient will theoretically
work. If you want to boot a real thin client see <ulink url="https://fedorahosted.org/k12linux/wiki/NetworkSetup">
NetworkSetup
</ulink>
.
</para>
</listitem>
</orderedlist>
</sect2>
-->
|