http://www.freebsdwiki.net/api.php?action=feedcontributions&feedformat=atom&user=Map7 2026-05-03T09:21:34Z User contributions MediaWiki 1.18.0 http://www.freebsdwiki.net/index.php/Etc/fstab 2007-10-15T01:37:46Z

<p>Map7: </p> <hr /> <div>'''/etc/fstab''' is the system config file used to control how filesystem devices are automatically mounted and/or fscked.<br /> <br /> ph34r# cat /etc/fstab<br /> # Device Mountpoint FStype Options Dump Pass#<br /> /dev/ad4s1b none swap sw 0 0<br /> /dev/ad4s1a / ufs rw 1 1<br /> /dev/ad4s1e /tmp ufs rw 2 2<br /> /dev/ad4s1f /usr ufs rw 2 2<br /> /dev/ad4s1d /var ufs rw 2 2<br /> /dev/ad6s1e /data ufs rw 2 2<br /> /dev/acd0 /cdrom cd9660 ro,noauto 0 0<br /> /dev/da4s1 /mnt/usbdrive msdos rw,noauto 0 0<br /> <br /> In the '''fstab''' file shown above, we can see entries for all the standard system partitions, as well as /cdrom and /mnt/usbdrive. The first column in each entry denotes the actual device location, the second shows the filesystem directory the device will be mounted to, the third shows the type of filesystem used on the device, the fourth shows options to be followed, and the last two devices discuss [[dump]]ing and [[fsck]]ing of the device in question.<br /> <br /> Since the /cdrom and /mnt/usbdrive devices are set to &quot;noauto&quot; in options, they will not be automatically mounted at boot time. Also note that they have &quot;dump&quot; and &quot;pass&quot; set to 0 and 0, so they will not be automatically backed up by the system &quot;dump&quot; command, nor will they be automatically [[fsck]]'ed at boot.<br /> <br /> Also note that while the normal partitions are marked &quot;rw&quot;, for ReadWrite, the CD-ROM is marked &quot;ro&quot; since it's a ReadOnly device, and the swap partition is marked &quot;sw&quot; since it's a swap partition, not a normal filesystem.<br /> <br /> For the devices listed in /etc/fstab, [[mount]] and [[umount]] can be used with no argument other than the name of the mountpoint - for instance on the system whose '''fstab''' is displayed above, '''mount /mnt/usbdrive''' and '''mount -t msdos /dev/da4s1 /mnt/usbdrive''' would both do the exact same thing.<br /> <br /> ==Enabling Soft-Updates==<br /> By enabling soft updates you can make your system faster and more reliable if there is a crash/power failure.<br /> <br /> # tunefs -n enable /filesystem<br /> <br /> ==Faster read performance==<br /> You can get faster read performance by not writing to the files access time every time you read. <br /> Warning: Some people don't think that this is the right way to do things, run at own risk.<br /> <br /> In the options part of fstab for each disk add 'noatime'.<br /> <br /> See also: [[Partitioning Tips and Tricks]]<br /> <br /> [[Category:Important Config Files|Fstab]]</div>

Map7 http://www.freebsdwiki.net/index.php/CUPS 2007-10-11T06:32:40Z

<p>Map7: </p> <hr /> <div>CUPS (Common Unix Printing System)<br /> This makes it easy to add printers to your system and programs such as firefox will pick up the printer list automatically.<br /> <br /> ==Installing CUPS==<br /> # pkg_add -r cups<br /> <br /> or <br /> <br /> # cd /usr/ports/print/cups<br /> # make install clean<br /> <br /> ==Install a Parallel Printer==<br /> <br /> If you use an old parallel printer then you need to do the following before you add the printer through cups:<br /> <br /> # chown root:cups /dev/lpt0<br /> # chmod 0660 /dev/lpt0<br /> <br /> Now add these lines to /etc/devfs.conf so that the permissions are set during boot time<br /> <br /> own /dev/lpt0 root:cups<br /> perm /dev/lpt0 0660<br /> <br /> Now go back into the cups setup http://localhost:631 and add your printer, you will notice that there is now a Parallel device present.<br /> <br /> <br /> ==Installing a PCL printer==<br /> <br /> If you have a printer which handles PCL but not PS then you need to install the 'hpijs' port<br /> <br /> # portinstall -P hpijs<br /> <br /> Now you will have a huge list of HP printers to select from, if you have a basic B&amp;W laser printer which accepts PCL then use the 'HP LaserJet 5L Foomatic/hpijs' driver and you shouldn't have a problem.<br /> <br /> ==Printing from Windows XP to a FreeBSD CUPs server==<br /> You don't require samba to print from an XP client through a FreeBSD CUPs server to your printer. It's easier to do this without samba actually. It doesn't matter if you have samba installed though.<br /> <br /> Simply get your printers working under CUPs and on the local server and test these. Then on the windows box add a new network printer and point that printer to your server by using the URL section of the wizard.<br /> <br /> For example <br /> http://&lt;server&gt;:631/printers/&lt;printer name&gt;<br /> <br /> Then you will be able to have full rights of that printer on each windows box.<br /> <br /> <br /> ==KDE Setup==<br /> You can setup any non KDE applications such as Openoffice to use the KDE printer dialogue by setting up the default printer of that applications as:<br /> <br /> kprinter -stdin<br /> <br /> <br /> ===Openoffice===<br /> Change the default printer in openoffice spadmin program<br /> <br /> <br /> ===xpdf===<br /> <br /> Add the following to /usr/X11R6/etc/xpdfrc config file.<br /> psFile &quot;|kprinter -stdin&quot;<br /> <br /> ==CUPS to PDF==<br /> CUPS can also be used to print directly from any program to a PDF file.<br /> <br /> # pkg_add -r cups-pdf<br /> <br /> <br /> ==CUPS mimics lpr==<br /> If you have old programs which use lpr to print then you should install CUPS-lpr<br /> <br /> # pkg_add -r cups-lpr<br /> <br /> ==CUPS Troubleshooting==<br /> <br /> ===CUPS with proxy===<br /> Make sure if you run a proxy to set localhost in the exceptions of your browser.<br /> Should now be able to connect to http://localhost:631<br /> <br /> ===CUPS and KDE Error===<br /> If you get an error in KDE print manager such as:<br /> cups host not found.<br /> <br /> Then change the host from<br /> host: /var/run/cups.sock<br /> to<br /> host: localhost<br /> <br /> <br /> <br /> <br /> ===CUPS and Gnome Warning===<br /> I've installed CUPS on a few machines and found everytime I do I cannot print though any gnome based application. If you like to use gnome applications to print your work, don't install CUPS just use LPD.<br /> <br /> programs which crashed right out when printing were:<br /> gedit, abiword, gnumeric, inkscape.<br /> <br /> &lt;b&gt;Error you will get&lt;/b&gt;<br /> &lt;pre&gt;<br /> (gdb) run<br /> Starting program: /usr/X11R6/bin/gnumeric<br /> <br /> Program received signal SIGBUS, Bus error.<br /> [Switching to Thread 3 (LWP 100326)]<br /> 0x29dfd450 in ippWriteIO (dst=0x8542000, cb=0x29dfa3bc &lt;httpWrite&gt;,<br /> blocking=1, parent=0x0, ipp=0x8517880) at ipp.c:1418<br /> 1418 ipp.c: No such file or directory.<br /> in ipp.c<br /> &lt;/pre&gt;<br /> <br /> ==links==<br /> http://forums.bsdnexus.com/viewtopic.php?id=36<br /> <br /> <br /> [[Category:Ports and Packages]]</div>

Map7 http://www.freebsdwiki.net/index.php/CUPS 2007-10-11T00:04:59Z

<p>Map7: </p> <hr /> <div>CUPS (Common Unix Printing System)<br /> This makes it easy to add printers to your system and programs such as firefox will pick up the printer list automatically.<br /> <br /> ==Installing CUPS==<br /> # pkg_add -r cups<br /> <br /> or <br /> <br /> # cd /usr/ports/print/cups<br /> # make install clean<br /> <br /> ==Install a Parallel Printer==<br /> <br /> If you use an old parallel printer then you need to do the following before you add the printer through cups:<br /> <br /> # chown root:cups /dev/lpt0<br /> # chmod 0660 /dev/lpt0<br /> <br /> Now add these lines to /etc/devfs.conf so that the permissions are set during boot time<br /> <br /> own /dev/lpt0 root:cups<br /> perm /dev/lpt0 0660<br /> <br /> Now go back into the cups setup http://localhost:631 and add your printer, you will notice that there is now a Parallel device present.<br /> <br /> <br /> ==Installing a PCL printer==<br /> <br /> If you have a printer which handles PCL but not PS then you need to install the 'hpijs' port<br /> <br /> # portinstall -P hpijs<br /> <br /> Now you will have a huge list of HP printers to select from, if you have a basic B&amp;W laser printer which accepts PCL then use the 'HP LaserJet 5L Foomatic/hpijs' driver and you shouldn't have a problem.<br /> <br /> <br /> <br /> ==KDE Setup==<br /> You can setup any non KDE applications such as Openoffice to use the KDE printer dialogue by setting up the default printer of that applications as:<br /> <br /> kprinter -stdin<br /> <br /> <br /> ===Openoffice===<br /> Change the default printer in openoffice spadmin program<br /> <br /> <br /> ===xpdf===<br /> <br /> Add the following to /usr/X11R6/etc/xpdfrc config file.<br /> psFile &quot;|kprinter -stdin&quot;<br /> <br /> ==CUPS to PDF==<br /> CUPS can also be used to print directly from any program to a PDF file.<br /> <br /> # pkg_add -r cups-pdf<br /> <br /> <br /> ==CUPS mimics lpr==<br /> If you have old programs which use lpr to print then you should install CUPS-lpr<br /> <br /> # pkg_add -r cups-lpr<br /> <br /> ==CUPS Troubleshooting==<br /> <br /> ===CUPS with proxy===<br /> Make sure if you run a proxy to set localhost in the exceptions of your browser.<br /> Should now be able to connect to http://localhost:631<br /> <br /> ===CUPS and KDE Error===<br /> If you get an error in KDE print manager such as:<br /> cups host not found.<br /> <br /> Then change the host from<br /> host: /var/run/cups.sock<br /> to<br /> host: localhost<br /> <br /> <br /> <br /> <br /> ===CUPS and Gnome Warning===<br /> I've installed CUPS on a few machines and found everytime I do I cannot print though any gnome based application. If you like to use gnome applications to print your work, don't install CUPS just use LPD.<br /> <br /> programs which crashed right out when printing were:<br /> gedit, abiword, gnumeric, inkscape.<br /> <br /> &lt;b&gt;Error you will get&lt;/b&gt;<br /> &lt;pre&gt;<br /> (gdb) run<br /> Starting program: /usr/X11R6/bin/gnumeric<br /> <br /> Program received signal SIGBUS, Bus error.<br /> [Switching to Thread 3 (LWP 100326)]<br /> 0x29dfd450 in ippWriteIO (dst=0x8542000, cb=0x29dfa3bc &lt;httpWrite&gt;,<br /> blocking=1, parent=0x0, ipp=0x8517880) at ipp.c:1418<br /> 1418 ipp.c: No such file or directory.<br /> in ipp.c<br /> &lt;/pre&gt;<br /> <br /> ==links==<br /> http://forums.bsdnexus.com/viewtopic.php?id=36<br /> <br /> <br /> [[Category:Ports and Packages]]</div>

Map7 http://www.freebsdwiki.net/index.php/CUPS 2007-10-10T23:49:09Z

<p>Map7: </p> <hr /> <div>CUPS (Common Unix Printing System)<br /> This makes it easy to add printers to your system and programs such as firefox will pick up the printer list automatically.<br /> <br /> ==Installing CUPS==<br /> # pkg_add -r cups<br /> <br /> or <br /> <br /> # cd /usr/ports/print/cups<br /> # make install clean<br /> <br /> ==Install a Parallel Printer==<br /> <br /> If you use an old parallel printer then you need to do the following before you add the printer through cups:<br /> <br /> # chown root:cups /dev/lpt0<br /> # chmod 0660 /dev/lpt0<br /> <br /> Now add these lines to /etc/devfs.conf so that the permissions are set during boot time<br /> <br /> own /dev/lpt0 root:cups<br /> perm /dev/lpt0 0660<br /> <br /> Now go back into the cups setup http://localhost:631 and add your printer, you will notice that there is now a Parallel device present.<br /> <br /> <br /> ==KDE Setup==<br /> You can setup any non KDE applications such as Openoffice to use the KDE printer dialogue by setting up the default printer of that applications as:<br /> <br /> kprinter -stdin<br /> <br /> <br /> ===Openoffice===<br /> Change the default printer in openoffice spadmin program<br /> <br /> <br /> ===xpdf===<br /> <br /> Add the following to /usr/X11R6/etc/xpdfrc config file.<br /> psFile &quot;|kprinter -stdin&quot;<br /> <br /> ==CUPS to PDF==<br /> CUPS can also be used to print directly from any program to a PDF file.<br /> <br /> # pkg_add -r cups-pdf<br /> <br /> <br /> ==CUPS mimics lpr==<br /> If you have old programs which use lpr to print then you should install CUPS-lpr<br /> <br /> # pkg_add -r cups-lpr<br /> <br /> ==CUPS Troubleshooting==<br /> <br /> ===CUPS with proxy===<br /> Make sure if you run a proxy to set localhost in the exceptions of your browser.<br /> Should now be able to connect to http://localhost:631<br /> <br /> ===CUPS and KDE Error===<br /> If you get an error in KDE print manager such as:<br /> cups host not found.<br /> <br /> Then change the host from<br /> host: /var/run/cups.sock<br /> to<br /> host: localhost<br /> <br /> <br /> <br /> <br /> ===CUPS and Gnome Warning===<br /> I've installed CUPS on a few machines and found everytime I do I cannot print though any gnome based application. If you like to use gnome applications to print your work, don't install CUPS just use LPD.<br /> <br /> programs which crashed right out when printing were:<br /> gedit, abiword, gnumeric, inkscape.<br /> <br /> &lt;b&gt;Error you will get&lt;/b&gt;<br /> &lt;pre&gt;<br /> (gdb) run<br /> Starting program: /usr/X11R6/bin/gnumeric<br /> <br /> Program received signal SIGBUS, Bus error.<br /> [Switching to Thread 3 (LWP 100326)]<br /> 0x29dfd450 in ippWriteIO (dst=0x8542000, cb=0x29dfa3bc &lt;httpWrite&gt;,<br /> blocking=1, parent=0x0, ipp=0x8517880) at ipp.c:1418<br /> 1418 ipp.c: No such file or directory.<br /> in ipp.c<br /> &lt;/pre&gt;<br /> <br /> ==links==<br /> http://forums.bsdnexus.com/viewtopic.php?id=36<br /> <br /> <br /> [[Category:Ports and Packages]]</div>

Map7 http://www.freebsdwiki.net/index.php/Firefox 2007-09-10T03:34:55Z

<p>Map7: </p> <hr /> <div>Firefox is a great browser and this documentation relates to version 2.01<br /> <br /> ==Installing video plugin==<br /> Install the mplayer-plugin for mozilla<br /> <br /> # cd /usr/ports/www/mplayer-plugin<br /> # make install<br /> <br /> mplayer plugin will support:<br /> <br /> Window Media wmv, avi, asf, wav and asx<br /> QuickTime mov and smil<br /> MPEG Video and Audio mpeg and mp3<br /> Ogg Vorbis ogg<br /> AutoDesk FLI fli and flc<br /> Vivo vivo<br /> Real Player ram and rm<br /> <br /> <br /> <br /> ==Installing Java VM plugin==<br /> Install the Java Runtime Environment via ports ({PORTSDIR}/java/diablo-jre15) or the Java Development Kit ({PORTSDIR}/java/diablo-jre15)&lt;br&gt;<br /> &lt;br&gt;<br /> Then to add the plugin go to the directory:&lt;br&gt;<br /> &lt;pre&gt;<br /> # cd /usr/X11R6/lib/browser_plugins<br /> &lt;/pre&gt;<br /> &lt;br&gt;<br /> and if you installed the JRE type the following:&lt;br&gt;<br /> &lt;pre&gt;<br /> # ln -s /usr/local/diablo-jre1.5.0/jre/plugin/i386/ns7/libjavaplugin_oji.so<br /> &lt;/pre&gt;<br /> or if you installed the JDK type the following:&lt;br&gt;<br /> &lt;pre&gt;<br /> # ln -s /usr/local/diablo-jdk1.5.0/jre/plugin/i386/ns7/libjavaplugin_oji.so<br /> &lt;/pre&gt;<br /> &lt;br&gt;<br /> Now you should have java VM working. To test go to this site and wait a while for the Java VM to load:&lt;br&gt;<br /> http://www.java.com/en/download/help/testvm.xml&lt;br&gt;<br /> &lt;br&gt;<br /> <br /> ==Installing flash on native firefox==<br /> http://www.freebsdwiki.net/index.php/Flash#Native_Firefox<br /> <br /> ==Links==<br /> http://www.math.colostate.edu/~reinholz/freebsd/firefox_plugins.html<br /> <br /> [[Category:Ports_and_Packages]]</div>

Map7 http://www.freebsdwiki.net/index.php/Thunderbird,_link_handling_preferences 2007-05-03T07:27:55Z

<p>Map7: </p> <hr /> <div>==Open links in firefox==<br /> <br /> Edit your pref.js file in .thunderbird/*default*/pref.js and add the following<br /> <br /> user_pref(&quot;network.protocol-handler.app.ftp&quot;, &quot;/usr/local/bin/firefox&quot;);<br /> user_pref(&quot;network.protocol-handler.app.http&quot;, &quot;/usr/local/bin/firefox&quot;);<br /> user_pref(&quot;network.protocol-handler.app.https&quot;, &quot;/usr/local/bin/firefox&quot;);<br /> <br /> ==Open links in konqueror==<br /> <br /> user_pref(&quot;network.protocol-handler.app.ftp&quot;, &quot;/usr/local/bin/konqueror&quot;);<br /> user_pref(&quot;network.protocol-handler.app.http&quot;, &quot;/usr/local/bin/konqueror&quot;);<br /> user_pref(&quot;network.protocol-handler.app.https&quot;, &quot;/usr/local/bin/konqueror&quot;);</div>

Map7 http://www.freebsdwiki.net/index.php/PHP,_Installing 2007-05-02T00:00:11Z

<p>Map7: /* PHP 5 Installing */</p> <hr /> <div>Installing PHP with all the proper extensions can be a little tricky. The easiest way to do it (assuming you've already got your preferred version of Apache up and running) is as follows... first, head to /usr/ports/www/mod_php4 and '''make install clean'''. There isn't too much to be aware of here, except to make sure you either do or don't check &quot;use Apache2&quot; depending on whether your version of Apache is 1.x or 2.x.<br /> <br /> Next, head to /usr/ports/lang/php4-extensions and '''make install''' - this time, though, you might want to leave the &quot;clean&quot; off. This one's lots more fun - this is where you get to pick and choose capabilities for everything from MySQL (or other SQL server variants) support, PDF library support, image manipulation... you name it. Pick everything you need, but try not to pick anything you DON'T need - remember, &quot;just what you need and no more&quot; is always better (and more secure) than &quot;everything but the kitchen sink&quot;. You can always come back later and add more extensions if you need to - all you have to do to change which extensions you're building is type '''make config''' (a trick that works in any of the ports that have ncurses-style text menus to configure them).<br /> <br /> Depending on how many extensions you selected, this one can take a LONG time to compile. You may also run into problems where it bombs out due to old versions of some of the dependencies for some of the extensions being installed - for example, when I just now rebuilt the extensions on this webserver, I encountered the following problem:<br /> <br /> ===&gt; Installing for pdflib-6.0.0p1<br /> ===&gt; Generating temporary packing list<br /> ===&gt; Checking if print/pdflib already installed<br /> ===&gt; an older version of print/pdflib is already installed<br /> You may wish to ``make deinstall'' and install this port again<br /> by ``make reinstall'' to upgrade it properly.<br /> If you really wish to overwrite the old port of print/pdflib<br /> without deleting it first, set the variable &quot;FORCE_PKG_REGISTER&quot;<br /> in your environment or the &quot;make install&quot; command line.<br /> *** Error code 1 <br /> <br /> Stop in /usr/ports/print/pdflib.<br /> *** Error code 1<br /> <br /> Stop in /usr/ports/lang/php4-extensions.<br /> <br /> This was the fix:<br /> <br /> freebsdwiki# '''cd /usr/ports/print/pdflib'''<br /> freebsdwiki# '''make deinstall'''<br /> freebsdwiki# '''cd /usr/ports/lang/php4-extensions'''<br /> freebsdwiki# '''make install'''<br /> <br /> ... and off it happily trundled again, finishing my aborted installation from whence it had left off. Situations like this are why, for complex ports like this one, it's well-advised NOT to issue a '''make install clean''' all in one fell swoop, but instead to '''make install''' first, and wait to '''make clean''' until everything is satisfactorily built and installed to specification. (If you're really feeling paranoid and/or are working on a really critical high-traffic server, it's better yet to start with '''make''', then don't '''make install''' until you've already done the compilation and everything looks good, and THEN '''make clean''' to reclaim the space taken up by the work directories!)<br /> <br /> In this case, if I had issued '''make install clean''' all in one step, I would have lost close to an hour's worth of compilation time when the process bombed out due to the older version of pdflib being in place, and would have had to begin recompiling all the extensions all over again when I returned to the php4-extensions port after removing the old pdflib.<br /> <br /> You may even, if you've got the hard drive space to spare, wish to NOT issue a '''make clean''' at all on this port - it'll save you a lot of time if you ever need to install new extensions, since the work will already be done on any of the extensions that haven't been updated since the last time.<br /> <br /> ==PHP 5 Installing==<br /> Install from ports<br /> <br /> /usr/ports/lang/php5<br /> <br /> Select Apache when configuring<br /> # make config<br /> <br /> Then install the port<br /> # make install clean<br /> <br /> # cp /usr/local/etc/php.ini-dist /usr/local/etc/php.ini<br /> <br /> Add the following lines to /usr/local/etc/apache2/httpd.conf<br /> AddType application/x-httpd-php .php<br /> AddType application/x-httpd-php-source .phps<br /> <br /> Change the following line in httpd.conf from<br /> DirectoryIndex index.html <br /> To:<br /> DirectoryIndex index.html index.php<br /> <br /> Test with &lt;? phpinfo(); ?&gt; <br /> # echo &quot;&lt;? phpinfo(); ?&gt;&quot; &gt;&gt; /usr/local/www/data/test.php<br /> <br /> Restart apache. <br /> <br /> <br /> <br /> [[Category:Common Tasks]]</div>

Map7 http://www.freebsdwiki.net/index.php/PHP,_Installing 2007-05-01T23:59:41Z

<p>Map7: </p> <hr /> <div>Installing PHP with all the proper extensions can be a little tricky. The easiest way to do it (assuming you've already got your preferred version of Apache up and running) is as follows... first, head to /usr/ports/www/mod_php4 and '''make install clean'''. There isn't too much to be aware of here, except to make sure you either do or don't check &quot;use Apache2&quot; depending on whether your version of Apache is 1.x or 2.x.<br /> <br /> Next, head to /usr/ports/lang/php4-extensions and '''make install''' - this time, though, you might want to leave the &quot;clean&quot; off. This one's lots more fun - this is where you get to pick and choose capabilities for everything from MySQL (or other SQL server variants) support, PDF library support, image manipulation... you name it. Pick everything you need, but try not to pick anything you DON'T need - remember, &quot;just what you need and no more&quot; is always better (and more secure) than &quot;everything but the kitchen sink&quot;. You can always come back later and add more extensions if you need to - all you have to do to change which extensions you're building is type '''make config''' (a trick that works in any of the ports that have ncurses-style text menus to configure them).<br /> <br /> Depending on how many extensions you selected, this one can take a LONG time to compile. You may also run into problems where it bombs out due to old versions of some of the dependencies for some of the extensions being installed - for example, when I just now rebuilt the extensions on this webserver, I encountered the following problem:<br /> <br /> ===&gt; Installing for pdflib-6.0.0p1<br /> ===&gt; Generating temporary packing list<br /> ===&gt; Checking if print/pdflib already installed<br /> ===&gt; an older version of print/pdflib is already installed<br /> You may wish to ``make deinstall'' and install this port again<br /> by ``make reinstall'' to upgrade it properly.<br /> If you really wish to overwrite the old port of print/pdflib<br /> without deleting it first, set the variable &quot;FORCE_PKG_REGISTER&quot;<br /> in your environment or the &quot;make install&quot; command line.<br /> *** Error code 1 <br /> <br /> Stop in /usr/ports/print/pdflib.<br /> *** Error code 1<br /> <br /> Stop in /usr/ports/lang/php4-extensions.<br /> <br /> This was the fix:<br /> <br /> freebsdwiki# '''cd /usr/ports/print/pdflib'''<br /> freebsdwiki# '''make deinstall'''<br /> freebsdwiki# '''cd /usr/ports/lang/php4-extensions'''<br /> freebsdwiki# '''make install'''<br /> <br /> ... and off it happily trundled again, finishing my aborted installation from whence it had left off. Situations like this are why, for complex ports like this one, it's well-advised NOT to issue a '''make install clean''' all in one fell swoop, but instead to '''make install''' first, and wait to '''make clean''' until everything is satisfactorily built and installed to specification. (If you're really feeling paranoid and/or are working on a really critical high-traffic server, it's better yet to start with '''make''', then don't '''make install''' until you've already done the compilation and everything looks good, and THEN '''make clean''' to reclaim the space taken up by the work directories!)<br /> <br /> In this case, if I had issued '''make install clean''' all in one step, I would have lost close to an hour's worth of compilation time when the process bombed out due to the older version of pdflib being in place, and would have had to begin recompiling all the extensions all over again when I returned to the php4-extensions port after removing the old pdflib.<br /> <br /> You may even, if you've got the hard drive space to spare, wish to NOT issue a '''make clean''' at all on this port - it'll save you a lot of time if you ever need to install new extensions, since the work will already be done on any of the extensions that haven't been updated since the last time.<br /> <br /> ==PHP 5 Installing==<br /> Install from ports<br /> <br /> /usr/ports/lang/php5<br /> <br /> Select Apache when configuring<br /> # make config<br /> <br /> Then install the port<br /> # make install clean<br /> <br /> # cp /usr/local/etc/php.ini-dist /usr/local/etc/php.ini<br /> <br /> Add the following lines to /usr/local/etc/apache2/httpd.conf<br /> AddType application/x-httpd-php .php<br /> AddType application/x-httpd-php-source .phps<br /> <br /> Change the following line in httpd.conf from<br /> DirectoryIndex index.html <br /> To:<br /> DirectoryIndex index.html index.php<br /> <br /> Test with &lt;? phpinfo(); ?&gt; <br /> # echo &quot;&lt;? phpinfo(); ?&gt;&quot; &gt;&gt; /usr/local/www/data/test.php<br /> <br /> Restart apache. <br /> <br /> <br /> <br /> [[Category:Common Tasks]]</div>

Map7 http://www.freebsdwiki.net/index.php/PuTTY 2007-05-01T00:03:28Z

<p>Map7: </p> <hr /> <div>a free [[ssh]]/telnet client for Windows and Linux, available at http://www.chiark.greenend.org.uk/~sgtatham/putty/<br /> <br /> There are several utilities that you can obtain from that page, which are: <br /> # '''PuTTY''': the Telnet and SSH client itself<br /> # '''PSCP''': command-line secure file copy<br /> # '''PSFTP''': an SFTP client for secure file transfer<br /> # '''PuTTYtel''': a Telnet-only client<br /> # '''Plink''': a command-line interface to the PuTTY back ends<br /> # '''Pageant''': an SSH authentication agent for PuTTY, PSCP and Plink<br /> # '''PuTTYgen''': an RSA and DSA key generation utility<br /> [[Category:Windows Equivalents]]</div>

Map7 http://www.freebsdwiki.net/index.php/Updating_the_system 2007-04-30T23:59:16Z

<p>Map7: </p> <hr /> <div>'''Note''': If you only want to install security updates, it's enough to subscribe to [http://lists.freebsd.org/mailman/listinfo/freebsd-security-notifications FreeBSD security notifications] and follow the instructions in each advisory. Otherwise, read on.<br /> <br /> In FreeBSD, the base system and ports can be updated independently if desired. Here's how to do it.<br /> <br /> == Basic Security updates ==<br /> From FreeBSD 6.X you can simply keep up to date using freebsd-update<br /> <br /> First time use:<br /> # freebsd-update fetch<br /> # freebsd-update install<br /> <br /> You can rollback in-case of problems<br /> # freebsd-update rollback<br /> <br /> Use the following line in your /etc/crontab to keep your machine up to date:<br /> 30 3 * * * root /usr/sbin/freebsd-update cron -t &lt;email address&gt;<br /> <br /> This will email you when updates are available and to install them type<br /> # freebsd-update install<br /> <br /> == Updating the base system ==<br /> <br /> To upgrade to a RELEASE version of FreeBSD, you can do one of three things:<br /> #Do a binary Upgrade to a release version<br /> #Do a binary Upgrade using the method described [http://www.daemonology.net/freebsd-upgrade-5.4-to-6.0/ here]<br /> #Do a source upgrade as described [[upgrading the base system | here]]<br /> <br /> A binary upgrade to a release version can be done by running '''sysinstall''' from the installation medium (e.g. CDROM). See the [http://www.freebsd.org/releases/ release notes] of the release for details. Note that this will wipe out a lot of customizations.<br /> <br /> == Updating applications ==<br /> <br /> Many open-source apps are under active development, so this is something you'll probably want to do quite regularly to ensure that you have the latest versions of everything.<br /> <br /> First update the ports tree (/usr/ports/). This can be done via [[cvsup]], [[ctm]] or [[portsnap]]. The ports can then be automatically updated using [[portupgrade]] or [[portmanager]], which are capable of dealing with dependencies.<br /> <br /> == How do I download updates? ==<br /> <br /> The most common method used is [[cvsup]] (see [[updating the ports tree]]). However, you might not be able to use it if you're behind a restrictive firewall (blocking tcp port 5999) or on a weak connection. In that case you can use [[ctm]] to obtain differential updates by email or ftp.<br /> <br /> For updating the ports tree, a third option is available. [[Portsnap]] is an automated tool which offers many advantages over both the other methods:<br /> <br /> * secure (uses cryptographic signing)<br /> * very efficient in terms of bandwidth consumption and server load<br /> * uses http only<br /> * easy to use<br /> <br /> [[Category:Common Tasks]]</div>

Map7 http://www.freebsdwiki.net/index.php/Sound_card 2007-04-30T23:51:40Z

<p>Map7: Remove crap</p> <hr /> <div>In order to get sound out of your FreeBSD box, you'll need to either load your sound driver module or compile sound support in your kernel -- it's not installed by default. For this you need to use [[kldload]] to load your sound driver. If you don't know which sound card you have -- and therefore don't know which driver to use -- you can load the generic [[snd_driver]] module (in 5.x systems -- in 4.x you need to load the [[snd]] module), which works for most cards, like so:<br /> samizdata# kldload snd_driver <br /> <br /> If that works, you'll probably want it to load automatically at boot time. To do so, you'll want to append a line about snd_driver to your loader.conf:<br /> <br /> samizdata# echo snd_driver_load=&quot;YES&quot; &gt;&gt; /boot/loader.conf<br /> <br /> And presto, when booting, your system will always try to load snd_driver.<br /> <br /> If you don't know your sound card type the following:<br /> # man sound<br /> Now look at the SEE ALSO section and start loading each of these until your sound works.<br /> <br /> For instance for an ASUS A8V board it's a running a VIA sound card so I would run:<br /> # kldload snd_via8233<br /> <br /> If this works I put this line into my /boot/loader.conf<br /> snd_via8233_load=&quot;YES&quot;<br /> <br /> That way it's loaded at boot time without having to recompile the kernel.<br /> <br /> <br /> == FreeBSD5.4 and above Sound ==<br /> <br /> Since 27/07/04 the sound system has changed a lot and now to install sound under FreeBSD you have to do the following:<br /> freebsd# kldload sound<br /> <br /> Then find out your sound card. I'm using an ASUS A7N8X motherboard with Nvidia onboard sound so I typed <br /> freebsd# kldload snd_ich<br /> <br /> To find out what driver will work with your sound board/chip have a look at the NOTES file in<br /> /usr/src/sys/conf/NOTES - search for 'snd' and you will find descriptions of all the different sound drivers. (The impatient may want to try running [[Sound_card:_checking_drivers|this shell script]] instead, which will automatically check each sound driver installed on the system to see if it works, and let you know what it found out.)<br /> <br /> Then when I had tested this and it worked I entered the following into my kernel:<br /> <br /> <br /> # Base sound driver - required for all cards<br /> device sound<br /> <br /> # Device-specific driver - may be different on other systems besides mine!<br /> device snd_ich<br /> <br /> and recompiled. However, recompiling the kernel is absolutely NOT necessary for sound support, as you can just dynamically load the modules for sound support at boot time, by adding lines to /boot/loader.conf:<br /> <br /> sound_load=&quot;YES&quot;<br /> snd_ich_load=&quot;YES&quot;<br /> <br /> Of course remember to replace snd_ich_load with whatever your individual device is.<br /> <br /> == External Links ==<br /> [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/sound-setup.html FreeBSD Handbook]<br /> <br /> [[Category:FreeBSD for Workstations]]</div>

Map7 http://www.freebsdwiki.net/index.php/Upgrading_the_base_system 2007-04-30T04:08:13Z

<p>Map7: Removing crap</p> <hr /> <div>Upgrading a FreeBSD system is relatively painless if the proper steps are followed. The standard way to upgrade a FreeBSD system is to update the source code to the new version then recompile the source and install. There are automatic commands for much of the process. <br /> <br /> In overview the steps are:<br /> *Backup important files<br /> *Update the system source code ([[cvsup]] over the internet or install source from a new CD)<br /> *Read [[UPDATING|/usr/src/UPDATING]] to look for any gotcha's or recent changes<br /> *Compile the source for the system except for the kernel (make buildworld)<br /> *Compile the source for the [[kernel]] ([[make buildkernel]])<br /> *Install any critical config files that have been updated (mergemaster -p)<br /> *Install the new kernel if it has built successfully (make installkernel)<br /> *Reboot to run the new kernel<br /> *Drop to [[single user mode]] (see [[init]])<br /> *Install the rest of the system (make installworld)<br /> *Update the config files ([[mergemaster]])<br /> <br /> For information about the different FreeBSD release branches, look at [[FreeBSD Release Branches]].<br /> For a specialized HOWTO regarding updating from FreeBSD 5.4 to FreeBSD 6.0, see [[Updating to FreeBSD 6.0]]<br /> <br /> [[Category:Common Tasks]]</div>

Map7 http://www.freebsdwiki.net/index.php/PHP 2007-04-30T01:10:03Z

<p>Map7: /* PHP for dynamic websites */</p> <hr /> <div>PHP is a recursive acronym for ''PHP Hypertext Preprocessor''. It is an interpreted script language commonly used for dynamic pages generation on webservers. It is generally installed side by side with the [[Apache]] web server, and [[MySQL]] or [[PostgreSQL]] as database management system.<br /> <br /> ==Installing PHP==<br /> <br /> PHP is available from the port-tree ...<br /> # cd /usr/ports/lang/php5<br /> ... and the packages ...<br /> # pkg_add -r php5<br /> <br /> ==Using PHP==<br /> There are two ways to use PHP :<br /> * With apache: configure apache to use php to process .php files requested by the user.<br /> * As a command interpreter: php can process scripts, or instructions typed at the commandline.<br /> <br /> ===PHP for dynamic websites===<br /> <br /> All the steps of Apache configuration are explained after PHP installation. You have to add these two lines in httpd.conf:<br /> AddType application/x-httpd-php .php<br /> AddType application/x-httpd-php-source .phps<br /> <br /> You will probably also want to add ''index.php'' as a possible directory index:<br /> DirectoryIndex index.html index.php<br /> <br /> You have to restart Apache to have your changes effective. For example, if you use Apache 2:<br /> /usr/local/etc/rc.d/apache2.sh restart<br /> <br /> Now, you can try your installation by creating a file test.php in the /usr/local/www/data directory:<br /> &lt;?<br /> phpinfo();<br /> ?&gt;<br /> <br /> Request test.php using your web browser, and if all is well it will show you your PHP configuration.<br /> <br /> ===Scripts in PHP===<br /> <br /> If you have compiled PHP with the commandline interface, you can write scripts in PHP that can be used from the [[shell]]. This is very useful for ''quick and dirty'' hacks; especially if you want your output to be HTML. Put the PHP code in a file like this :<br /> &lt;pre&gt;<br /> #!/usr/local/bin/php<br /> # phpscript<br /> &amp;lt;html&amp;gt; &amp;lt;title&amp;gt;Defined Constants&amp;lt;/title&amp;gt; &amp;lt;body&amp;gt;<br /> <br /> &amp;lt;h1&amp;gt;&amp;lt;? echo &quot;Hello from PHP &quot; .phpversion() ?&amp;gt;&amp;lt;/h1&amp;gt;<br /> &amp;lt;pre&amp;gt;&amp;lt;? print_r(get_defined_constants()) ?&amp;gt;&amp;lt;/pre&amp;gt;<br /> <br /> &amp;lt;/body&amp;gt;&amp;lt;/html&amp;gt;<br /> &lt;/pre&gt;<br /> <br /> Make the file executable:<br /> '''%''' chmod +x phpscript<br /> <br /> Then, you can run it from the command line.<br /> <br /> '''%''' ./phpscript | lynx -stdin<br /> In this case, we've piped to &lt;code&gt;lynx&lt;/code&gt;, so that we can browse the nicely formatted result.<br /> &lt;pre&gt;<br /> Defined Constants (p1 of 154)<br /> <br /> Hello from PHP 5.1.4<br /> <br /> Array<br /> (<br /> [E_ERROR] =&gt; 1<br /> [E_WARNING] =&gt; 2<br /> [E_PARSE] =&gt; 4<br /> [E_NOTICE] =&gt; 8<br /> -- press space for more, use arrow keys to move, '?' for help, 'q' to quit.<br /> &lt;/pre&gt;<br /> <br /> Or, we could have executed the command directly from the command line:<br /> '''%''' php -r 'echo &quot;Hello from PHP &quot;. phpversion() . &quot;\n&quot;; print_r(get_defined_constants());'<br /> Hello from PHP 5.1.4 <br /> Array<br /> (<br /> ...<br /> <br /> ==PHP Website==<br /> [http://www.php.net http://www.php.net]<br /> <br /> <br /> [[Category: Ports and Packages]]<br /> [[Category: Configuring FreeBSD]]</div>

Map7 http://www.freebsdwiki.net/index.php/PHP 2007-04-30T01:08:58Z

<p>Map7: /* PHP for dynamic websites */</p> <hr /> <div>PHP is a recursive acronym for ''PHP Hypertext Preprocessor''. It is an interpreted script language commonly used for dynamic pages generation on webservers. It is generally installed side by side with the [[Apache]] web server, and [[MySQL]] or [[PostgreSQL]] as database management system.<br /> <br /> ==Installing PHP==<br /> <br /> PHP is available from the port-tree ...<br /> # cd /usr/ports/lang/php5<br /> ... and the packages ...<br /> # pkg_add -r php5<br /> <br /> ==Using PHP==<br /> There are two ways to use PHP :<br /> * With apache: configure apache to use php to process .php files requested by the user.<br /> * As a command interpreter: php can process scripts, or instructions typed at the commandline.<br /> <br /> ===PHP for dynamic websites===<br /> <br /> All the steps of Apache configuration are explained after PHP installation. You have to add these two lines in httpd.conf:<br /> AddType application/x-httpd-php .php<br /> AddType application/x-httpd-php-source .phps<br /> <br /> You will probably also want to add ''index.php'' as a possible directory index:<br /> DirectoryIndex index.html index.php<br /> <br /> You have to restart Apache to have your changes effective. For example, if you use Apache 2:<br /> /usr/local/etc/rc.d/apache2.sh restart<br /> <br /> Now, you can try your installation by creating a file test.php:<br /> &lt;?<br /> phpinfo();<br /> ?&gt;<br /> <br /> Request test.php using your web browser, and if all is well it will show you your PHP configuration.<br /> <br /> ===Scripts in PHP===<br /> <br /> If you have compiled PHP with the commandline interface, you can write scripts in PHP that can be used from the [[shell]]. This is very useful for ''quick and dirty'' hacks; especially if you want your output to be HTML. Put the PHP code in a file like this :<br /> &lt;pre&gt;<br /> #!/usr/local/bin/php<br /> # phpscript<br /> &amp;lt;html&amp;gt; &amp;lt;title&amp;gt;Defined Constants&amp;lt;/title&amp;gt; &amp;lt;body&amp;gt;<br /> <br /> &amp;lt;h1&amp;gt;&amp;lt;? echo &quot;Hello from PHP &quot; .phpversion() ?&amp;gt;&amp;lt;/h1&amp;gt;<br /> &amp;lt;pre&amp;gt;&amp;lt;? print_r(get_defined_constants()) ?&amp;gt;&amp;lt;/pre&amp;gt;<br /> <br /> &amp;lt;/body&amp;gt;&amp;lt;/html&amp;gt;<br /> &lt;/pre&gt;<br /> <br /> Make the file executable:<br /> '''%''' chmod +x phpscript<br /> <br /> Then, you can run it from the command line.<br /> <br /> '''%''' ./phpscript | lynx -stdin<br /> In this case, we've piped to &lt;code&gt;lynx&lt;/code&gt;, so that we can browse the nicely formatted result.<br /> &lt;pre&gt;<br /> Defined Constants (p1 of 154)<br /> <br /> Hello from PHP 5.1.4<br /> <br /> Array<br /> (<br /> [E_ERROR] =&gt; 1<br /> [E_WARNING] =&gt; 2<br /> [E_PARSE] =&gt; 4<br /> [E_NOTICE] =&gt; 8<br /> -- press space for more, use arrow keys to move, '?' for help, 'q' to quit.<br /> &lt;/pre&gt;<br /> <br /> Or, we could have executed the command directly from the command line:<br /> '''%''' php -r 'echo &quot;Hello from PHP &quot;. phpversion() . &quot;\n&quot;; print_r(get_defined_constants());'<br /> Hello from PHP 5.1.4 <br /> Array<br /> (<br /> ...<br /> <br /> ==PHP Website==<br /> [http://www.php.net http://www.php.net]<br /> <br /> <br /> [[Category: Ports and Packages]]<br /> [[Category: Configuring FreeBSD]]</div>

Map7 http://www.freebsdwiki.net/index.php/Samba,_Installation 2007-03-07T07:16:36Z

<p>Map7: </p> <hr /> <div>Installing Samba under FreeBSD is simple and painless. The easiest method is to install from ports, which also guarantees you'll get the latest released version. Be sure to use [[CVSUP]] to update your ports tree before installing any software.<br /> <br /> See also: [[Samba]] - [[Samba_Configuration]]<br /> <br /> All operations listed in this article must be performed by the [[superuser]], so [[su]] to root.<br /> <br /> This install procedure will walk you through a basic, simple Samba install. No printers, no complicated options, just samba with some extended logging options which you don't even have to ever look at to run or use samba.<br /> <br /> First, find the port:<br /> &lt;pre&gt;oyabun# cd /usr/ports/net<br /> oyabun# ls | grep samba<br /> gnosamba<br /> py-samba<br /> samba<br /> samba-devel<br /> samba-libsmbclient<br /> samba3<br /> sambasentinel<br /> oyabun#&lt;/pre&gt;<br /> <br /> This lists all samba-related ports in the net category. We want the '''samba''' port.<br /> <br /> &lt;pre&gt;oyabun# cd samba&lt;/pre&gt;<br /> [[Category:Common Tasks]]<br /> <br /> Now, we need to install it.<br /> <br /> &lt;pre&gt;oyabun# make install clean&lt;/pre&gt;<br /> <br /> This will start the installation process, downloading and compiling the necessary files. It will '''install''' it (after it asks some questions) and then it will '''clean''' all the work files after it's done.<br /> <br /> Shortly, you'll see a menu, which you should configure thusly:<br /> <br /> [[Image:Samba_Installation_installmenu.png]]<br /> <br /> '''With syslog''' will enable some logging to the syslog, as well as Samba's internal logs. '''Without CUPS''' means you don't want to configure print services right now, you just want Samba to share your files.<br /> <br /> Make sure both of those options are selected (by moving the arrows keys and selecting them with space) then hit enter. Samba will now be installed, and barring accidents or problems, you will eventually be dumped back to a shell# prompt.<br /> <br /> Make sure you have the following line in your /etc/rc.conf so that samba will startup on boot.<br /> samba_enable=&quot;YES&quot;<br /> <br /> That's it. You just installed Samba. Now you need to configure it ( [[Samba_Configuration]] ), but you're done with step one.</div>

Map7 http://www.freebsdwiki.net/index.php/Samba,_Installation 2007-03-07T07:16:19Z

<p>Map7: </p> <hr /> <div>Installing Samba under FreeBSD is simple and painless. The easiest method is to install from ports, which also guarantees you'll get the latest released version. Be sure to use [[CVSUP]] to update your ports tree before installing any software.<br /> <br /> See also: [[Samba]] - [[Samba_Configuration]]<br /> <br /> All operations listed in this article must be performed by the [[superuser]], so [[su]] to root.<br /> <br /> This install procedure will walk you through a basic, simple Samba install. No printers, no complicated options, just samba with some extended logging options which you don't even have to ever look at to run or use samba.<br /> <br /> First, find the port:<br /> &lt;pre&gt;oyabun# cd /usr/ports/net<br /> oyabun# ls | grep samba<br /> gnosamba<br /> py-samba<br /> samba<br /> samba-devel<br /> samba-libsmbclient<br /> samba3<br /> sambasentinel<br /> oyabun#&lt;/pre&gt;<br /> <br /> This lists all samba-related ports in the net category. We want the '''samba''' port.<br /> <br /> &lt;pre&gt;oyabun# cd samba&lt;/pre&gt;<br /> [[Category:Common Tasks]]<br /> <br /> Now, we need to install it.<br /> <br /> &lt;pre&gt;oyabun# make install clean&lt;/pre&gt;<br /> <br /> This will start the installation process, downloading and compiling the necessary files. It will '''install''' it (after it asks some questions) and then it will '''clean''' all the work files after it's done.<br /> <br /> Shortly, you'll see a menu, which you should configure thusly:<br /> <br /> [[Image:Samba_Installation_installmenu.png]]<br /> <br /> '''With syslog''' will enable some logging to the syslog, as well as Samba's internal logs. '''Without CUPS''' means you don't want to configure print services right now, you just want Samba to share your files.<br /> <br /> Make sure both of those options are selected (by moving the arrows keys and selecting them with space) then hit enter. Samba will now be installed, and barring accidents or problems, you will eventually be dumped back to a shell# prompt.<br /> <br /> Make sure you have the following line in your /etc/rc.conf so that samba will startup on boot.<br /> samba_enable=&quot;YES&quot;<br /> <br /> That's it. You just installed Samba. Now you need to configure it ( [[Samba_Configuration]] ), but you're done with step one.</div>

Map7 http://www.freebsdwiki.net/index.php/Packages,_Installing 2006-11-29T23:47:31Z

<p>Map7: </p> <hr /> <div>Installing from a pre-built package is faster than [[Ports, Installing|installing ports]] but the trade-off is that you don't get to configure the package the way that you would like to: you must take the package as the person who made the package compiled it. <br /> <br /> It's a fairly straightfoward affair, you just need to use the [[pkg_add]] command, and if you don't have the .tbz package already on your system (which you likely won't,) use the -r switch to get the package remotely:<br /> <br /> %pwd<br /> /usr/home/dave<br /> %su -m<br /> Password:<br /> %pwd<br /> /usr/home/dave<br /> %pkg_add -r xmotd<br /> Fetching ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5.3-release/Latest/xmotd.tbz... Done.<br /> %<br /> <br /> You can create a [[script to install common packages]] so that you get them all in one go, if you like.<br /> <br /> ==Other Package FTP sties==<br /> The following list can be used if you cannot find the package using 'pkg_add -r &lt;package name&gt;'.<br /> <br /> ftp://ftp.riken.go.jp/pub/FreeBSD/ports/i386/packages-6.2-release<br /> <br /> <br /> To install a package using this site simple type the following:<br /> # pkg_add -K ftp://ftp.riken.go.jp/pub/FreeBSD/ports/i386/packages-6.2-release/editors/openoffice.org-2.0.4.tbz<br /> <br /> The -K is optional, it tells pkg_add to keep the files which maybe useful if you have more than one machine as you could just copy all the tbz files to the next machine and do it locally with command:<br /> <br /> # pkg_add openoffice.org-2.0.4.tbz<br /> <br /> Don't bother downloading the package and doing it locally as you will spend most of your life manually downloading the dependancies.<br /> <br /> [[Category:Common Tasks]]<br /> [[Category:FreeBSD for Workstations]]</div>

Map7 http://www.freebsdwiki.net/index.php/Flash 2006-11-26T04:46:55Z

<p>Map7: /* Linux Opera */</p> <hr /> <div>==How to install flash==<br /> <br /> First install linuxpluginwrapper<br /> # pkg_add -r linuxpluginwrapper<br /> Or with options:<br /> # cd /usr/ports/*/linuxpluginwrapper;make install<br /> <br /> Next install flashplugin7<br /> # cd /usr/ports/*/linux-flashplugin7;make install<br /> <br /> If it cannot fetch the file download it from here:<br /> http://freshmeat.net/projects/flashplugin/<br /> <br /> <br /> <br /> <br /> ===libmap.conf===<br /> <br /> Add the following to /etc/libmap.conf<br /> # Flash7 for Firefox<br /> [/usr/local/lib/npapi/linux-flashplugin/libflashplayer.so]<br /> libpthread.so.0 pluginwrapper/flash7.so<br /> libdl.so.2 pluginwrapper/flash7.so<br /> libz.so.1 libz.so.3<br /> libstdc++-libc6.2-2.so.3 libstdc++.so.4<br /> libm.so.6 libm.so.4<br /> libc.so.6 pluginwrapper/flash7.so<br /> <br /> <br /> # Flash6 for Konqueror<br /> [/usr/X11R6/lib/linux-flashplugin6/libflashplayer.so]<br /> libpthread.so.0 pluginwrapper/flash6.so<br /> libdl.so.2 pluginwrapper/flash6.so<br /> libz.so.1 libz.so.3<br /> libstdc++-libc6.2-2.so.3 libstdc++.so.5<br /> libm.so.6 libm.so.4<br /> libc.so.6 pluginwrapper/flash6.so<br /> <br /> <br /> ===Konqueror===<br /> <br /> Go to Settings -&gt; Configure Konqueror -&gt; plugins<br /> <br /> Create the directory and link files<br /> # mkdir /usr/X11R6/lib/linux-flashplugin6<br /> # cd /usr/X11R6/lib/linux-flashplugin6<br /> # ln -s /usr/local/lib/npapi/linux-flashplugin/flashplayer.xpt<br /> # ln -s /usr/local/lib/npapi/linux-flashplugin/libflashplayer.so<br /> <br /> Now hit 'Scan for new plugins'<br /> <br /> Now go and test it out.<br /> <br /> ===Native Firefox===<br /> <br /> You will need to patch a file and compile it's all explained on this site:<br /> <br /> http://www.jail.se/freebsd.html<br /> <br /> ===Linux Opera===<br /> <br /> I've noticed that some things work better under linux-opera than any other browser on FreeBSD. For instance the Asterisk Flash Operator Panel will only work properlly under this port and YouTube works with sound and video under opera!<br /> <br /> All you should have to do is install it. Opera will automatically use the libmap.conf file to find the flash libraries and load them.<br /> # pkg_add -r linux-opera<br /> <br /> ==External Links==<br /> http://freebsd.kde.org/howtos/konqueror-flash.php<br /> <br /> <br /> [[Category : FreeBSD Multimedia]]</div>

Map7 http://www.freebsdwiki.net/index.php/Vim 2006-11-01T11:46:45Z

<p>Map7: </p> <hr /> <div>''Vim'' is a very powerful text editor. It is an extended version of [[Vi]] and means ''VI iMproved''. It supports many features such as syntax highlighting or folding, can keep backups of files, and many others ...<br /> <br /> Note that vim is not part of FreeBSD, you will have to install it before running it. Once installed, you are advised to copy the file &quot;/usr/local/share/vim/vim63/vimrc_example.vim&quot; into your home directory and rename it &quot;.vimrc&quot;.<br /> <br /> See also [[vi]], [[ee]] (commonly aliased under FreeBSD as &quot;[[edit]]&quot;), [[joe]], [[nano]], [[pico]], [[vim]] or [[emacs]].<br /> <br /> <br /> ===VIMRC Extras===<br /> The example has most options but here are some more that you can insert on the end of your ~/.vimrc file<br /> <br /> set tabstop=4 &quot; numbers of spaces of tab character<br /> set shiftwidth=4 &quot; numbers of spaces to (auto)indent<br /> set number &quot; show line numbers<br /> <br /> ===VIMRC Colors===<br /> If you use a dark terminal window use<br /> set background=dark<br /> <br /> [[Category:Ports and Packages]]</div>

Map7 http://www.freebsdwiki.net/index.php/Vim 2006-11-01T03:53:56Z

<p>Map7: /* VIMRC Extras */</p> <hr /> <div>''Vim'' is a very powerful text editor. It is an extended version of [[Vi]] and means ''VI iMproved''. It supports many features such as syntax highlighting or folding, can keep backups of files, and many others ...<br /> <br /> Note that vim is not part of FreeBSD, you will have to install it before running it. Once installed, you are advised to copy the file &quot;/usr/local/share/vim/vim63/vimrc_example.vim&quot; into your home directory and rename it &quot;.vimrc&quot;.<br /> <br /> See also [[vi]], [[ee]] (commonly aliased under FreeBSD as &quot;[[edit]]&quot;), [[joe]], [[nano]], [[pico]], [[vim]] or [[emacs]].<br /> <br /> <br /> ===VIMRC Extras===<br /> The example has most options but here are some more that you can insert on the end of your ~/.vimrc file<br /> <br /> set tabstop=4 &quot; numbers of spaces of tab character<br /> set shiftwidth=4 &quot; numbers of spaces to (auto)indent<br /> set number &quot; show line numbers<br /> <br /> [[Category:Ports and Packages]]</div>

Map7 http://www.freebsdwiki.net/index.php/Vim 2006-11-01T03:53:33Z

<p>Map7: </p> <hr /> <div>''Vim'' is a very powerful text editor. It is an extended version of [[Vi]] and means ''VI iMproved''. It supports many features such as syntax highlighting or folding, can keep backups of files, and many others ...<br /> <br /> Note that vim is not part of FreeBSD, you will have to install it before running it. Once installed, you are advised to copy the file &quot;/usr/local/share/vim/vim63/vimrc_example.vim&quot; into your home directory and rename it &quot;.vimrc&quot;.<br /> <br /> See also [[vi]], [[ee]] (commonly aliased under FreeBSD as &quot;[[edit]]&quot;), [[joe]], [[nano]], [[pico]], [[vim]] or [[emacs]].<br /> <br /> <br /> ===VIMRC Extras===<br /> The example has most options but here are some more that you can insert on the end of your ~/.vimrc file<br /> <br /> set tabstop=4 &quot; numbers of spaces of tab character<br /> set shiftwidth=4 &quot; numbers of spaces to (auto)indent<br /> set number &quot; show line numbers<br /> <br /> [[Category:Ports and Packages]]</div>

Map7 http://www.freebsdwiki.net/index.php/Flash 2006-10-31T03:05:14Z

<p>Map7: </p> <hr /> <div>==How to install flash==<br /> <br /> First install linuxpluginwrapper<br /> # pkg_add -r linuxpluginwrapper<br /> Or with options:<br /> # cd /usr/ports/*/linuxpluginwrapper;make install<br /> <br /> Next install flashplugin7<br /> # cd /usr/ports/*/linux-flashplugin7;make install<br /> <br /> If it cannot fetch the file download it from here:<br /> http://freshmeat.net/projects/flashplugin/<br /> <br /> <br /> <br /> <br /> ===libmap.conf===<br /> <br /> Add the following to /etc/libmap.conf<br /> # Flash7 for Firefox<br /> [/usr/local/lib/npapi/linux-flashplugin/libflashplayer.so]<br /> libpthread.so.0 pluginwrapper/flash7.so<br /> libdl.so.2 pluginwrapper/flash7.so<br /> libz.so.1 libz.so.3<br /> libstdc++-libc6.2-2.so.3 libstdc++.so.4<br /> libm.so.6 libm.so.4<br /> libc.so.6 pluginwrapper/flash7.so<br /> <br /> <br /> # Flash6 for Konqueror<br /> [/usr/X11R6/lib/linux-flashplugin6/libflashplayer.so]<br /> libpthread.so.0 pluginwrapper/flash6.so<br /> libdl.so.2 pluginwrapper/flash6.so<br /> libz.so.1 libz.so.3<br /> libstdc++-libc6.2-2.so.3 libstdc++.so.5<br /> libm.so.6 libm.so.4<br /> libc.so.6 pluginwrapper/flash6.so<br /> <br /> <br /> ===Konqueror===<br /> <br /> Go to Settings -&gt; Configure Konqueror -&gt; plugins<br /> <br /> Create the directory and link files<br /> # mkdir /usr/X11R6/lib/linux-flashplugin6<br /> # cd /usr/X11R6/lib/linux-flashplugin6<br /> # ln -s /usr/local/lib/npapi/linux-flashplugin/flashplayer.xpt<br /> # ln -s /usr/local/lib/npapi/linux-flashplugin/libflashplayer.so<br /> <br /> Now hit 'Scan for new plugins'<br /> <br /> Now go and test it out.<br /> <br /> ===Native Firefox===<br /> <br /> You will need to patch a file and compile it's all explained on this site:<br /> <br /> http://www.jail.se/freebsd.html<br /> <br /> ===Linux Opera===<br /> <br /> I've noticed that some things work better under linux-opera than any other browser on FreeBSD. For instance the Asterisk Flash Operator Panel will only work properlly under this port.<br /> <br /> All you should have to do is install it. Opera will automatically use the libmap.conf file to find the flash libraries and load them.<br /> # pkg_add -r linux-opera<br /> <br /> ==External Links==<br /> http://freebsd.kde.org/howtos/konqueror-flash.php<br /> <br /> <br /> [[Category : FreeBSD Multimedia]]</div>

Map7 http://www.freebsdwiki.net/index.php/Sound_card 2006-10-31T02:22:18Z

<p>Map7: </p> <hr /> <div>In order to get sound out of your FreeBSD box, you'll need to either load your sound driver module or compile sound support in your kernel -- it's not installed by default. For this you need to use [[kldload]] to load your sound driver. If you don't know which sound card you have -- and therefore don't know which driver to use -- you can load the generic [[snd_driver]] module (in 5.x systems -- in 4.x you need to load the [[snd]] module), which works for most cards, like so:<br /> samizdata# kldload snd_driver <br /> <br /> If that works, you'll probably want it to load automatically at boot time. To do so, you'll want to append a line about snd_driver to your loader.conf:<br /> <br /> samizdata# echo snd_driver_load=&quot;YES&quot; &gt;&gt; /boot/loader.conf<br /> <br /> And presto, when booting, your system will always try to load snd_driver.<br /> <br /> If you don't know your sound card type the following:<br /> # man sound<br /> Now look at the SEE ALSO section and start loading each of these until your sound works.<br /> <br /> For instance for an ASUS A8V board it's a running a VIA sound card so I would run:<br /> # kldload snd_via8233<br /> <br /> If this works I put this line into my /boot/loader.conf<br /> snd_via8233_load=&quot;YES&quot;<br /> <br /> That way it's loaded at boot time without having to recompile the kernel.<br /> <br /> <br /> == FreeBSD5.4 and above Sound ==<br /> <br /> Since 27/07/04 the sound system has changed a lot and now to install sound under FreeBSD you have to do the following:<br /> freebsd# kldload sound<br /> <br /> Then find out your sound card. I'm using an ASUS A7N8X motherboard with Nvidia onboard sound so I typed <br /> freebsd# kldload snd_ich<br /> <br /> To find out what driver will work with your sound board/chip have a look at the NOTES file in<br /> /usr/src/sys/conf/NOTES - search for 'snd' and you will find descriptions of all the different sound drivers. (The impatient may want to try running [[Sound_card:_checking_drivers|this shell script]] instead, which will automatically check each sound driver installed on the system to see if it works, and let you know what it found out.)<br /> <br /> Then when I had tested this and it worked I entered the following into my kernel:<br /> <br /> <br /> # Base sound driver - required for all cards<br /> device sound<br /> <br /> # Device-specific driver - may be different on other systems besides mine!<br /> device snd_ich<br /> <br /> and recompiled. However, recompiling the kernel is absolutely NOT necessary for sound support, as you can just dynamically load the modules for sound support at boot time, by adding lines to /boot/loader.conf:<br /> <br /> sound_load=&quot;YES&quot;<br /> snd_ich_load=&quot;YES&quot;<br /> <br /> Of course remember to replace snd_ich_load with whatever your individual device is.<br /> <br /> == External Links ==<br /> [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/sound-setup.html FreeBSD Handbook]<br /> <br /> [[Category:FreeBSD for Workstations]]</div>

Map7 http://www.freebsdwiki.net/index.php/K3b 2006-10-31T01:07:23Z

<p>Map7: </p> <hr /> <div>K3b is a burning program which will burn just about anything to CD/DVD.<br /> <br /> Here is a quick config guide to getting k3b working under FreeBSD6.X<br /> <br /> ==Setup IDE CDROM Drive==<br /> Load your atapicam driver to see your IDE drive as part of the SCSI system.<br /> <br /> Add this line to /boot/loader.conf<br /> atapicam_load=&quot;YES&quot;<br /> <br /> Type the following<br /> # kldload atapicam<br /> <br /> <br /> Change /etc/fstab CDROM lines<br /> From:<br /> /dev/acd0 /cdrom cd9660 ro,noauto 0 0<br /> <br /> To:<br /> /dev/cd0 /cdrom cd9660 ro,noauto 0 0<br /> <br /> Check that your devices are showing up:<br /> # camcontrol devlist<br /> &lt;HL-DT-ST DVDRAM GMA-4020B A106&gt; at scbus0 target 1 lun 0 (pass1,cd1)<br /> <br /> ==Setup for users==<br /> <br /> Change some file permissions<br /> # chown root /usr/local/bin/cdrecord<br /> # chmod 4711 /usr/local/bin/cdrecord<br /> <br /> For the user who you want to be able to burn, add a mount point to their home directory for the cdrom:<br /> $ mkdir ~/cd0<br /> <br /> Add it to fstab<br /> /dev/cd0c /usr/home/XXX/cd0 cd9660 ro,noauto,nodev,nosuid 0 0<br /> <br /> ===Allow user mounts===<br /> <br /> add the following to /etc/sysctl.conf <br /> vfs.usermount=1 <br /> <br /> Change it manually<br /> # sysctl -w vfs.usermount=1<br /> <br /> Edit /etc/devfs.conf and add the following:<br /> own /dev/cd0 root:operator<br /> perm /dev/cd0 0666<br /> own /dev/pass0 root:operator<br /> perm /dev/pass0 0666<br /> own /dev/xpt0 root:operator<br /> perm /dev/xpt0 0666<br /> <br /> Change it manually<br /> # chmod 666 /dev/cd0<br /> # chmod 666 /dev/pass0<br /> # chmod 666 /dev/xpt0<br /> <br /> add to /etc/rc.conf<br /> devd_enable=&quot;YES&quot;<br /> <br /> Create a temp area for CD images<br /> # mkdir /usr/cdtemp<br /> # chmod 777 /usr/cdtemp<br /> <br /> ===More Info===<br /> For more information refer to the documentation from the k3b installation<br /> # pkg_info -Dx k3b<br /> <br /> ==Extras==<br /> Here I will explain how to burn to either extra mediums or different types of data ie: Audio.<br /> <br /> ===DVD burning===<br /> Install dvd+rw-tools<br /> # pkg_add -r dvd+rw-tools<br /> <br /> [[Category : Ports and Packages]]</div>

Map7 http://www.freebsdwiki.net/index.php/K3b 2006-10-31T01:04:52Z

<p>Map7: </p> <hr /> <div>K3b is a burning program which will burn just about anything to CD/DVD.<br /> <br /> Here is a quick config guide to getting k3b working under FreeBSD6.X<br /> <br /> ==Setup IDE CDROM Drive==<br /> Load your atapicam driver to see your IDE drive as part of the SCSI system.<br /> <br /> Add this line to /boot/loader.conf<br /> atapicam_load=&quot;YES&quot;<br /> <br /> Type the following<br /> # kldload atapicam<br /> <br /> <br /> Change /etc/fstab CDROM lines<br /> From:<br /> /dev/acd0 /cdrom cd9660 ro,noauto 0 0<br /> <br /> To:<br /> /dev/cd0 /cdrom cd9660 ro,noauto 0 0<br /> <br /> Check that your devices are showing up:<br /> # camcontrol devlist<br /> &lt;HL-DT-ST DVDRAM GMA-4020B A106&gt; at scbus0 target 1 lun 0 (pass1,cd1)<br /> <br /> ==Setup for users==<br /> <br /> Change some file permissions<br /> # chown root /usr/local/bin/cdrecord<br /> # chmod 4711 /usr/local/bin/cdrecord<br /> <br /> For the user who you want to be able to burn, add a mount point to their home directory for the cdrom:<br /> $ mkdir ~/cd0<br /> <br /> Add it to fstab<br /> /dev/cd0c /usr/home/XXX/cd0 cd9660 ro,noauto,nodev,nosuid 0 0<br /> <br /> ===Allow user mounts===<br /> <br /> add the following to /etc/sysctl.conf <br /> vfs.usermount=1 <br /> <br /> Change it manually<br /> # sysctl -w vfs.usermount=1<br /> <br /> Edit /etc/devfs.conf and add the following:<br /> own /dev/cd0 root:operator<br /> perm /dev/cd0 0666<br /> own /dev/pass0 root:operator<br /> perm /dev/pass0 0666<br /> own /dev/xpt0 root:operator<br /> perm /dev/xpt0 0666<br /> <br /> Change it manually<br /> # chmod 666 /dev/cd0<br /> # chmod 666 /dev/pass0<br /> # chmod 666 /dev/xpt0<br /> <br /> add to /etc/rc.conf<br /> devd_enable=&quot;YES&quot;<br /> <br /> Create a temp area for CD images<br /> # mkdir /usr/cdtemp<br /> # chmod 777 /usr/cdtemp<br /> <br /> ===More Info===<br /> For more information refer to the documentation from the k3b installation<br /> # pkg_info -Dx k3b<br /> <br /> <br /> <br /> [[Category : Ports and Packages]]</div>

Map7 http://www.freebsdwiki.net/index.php/Samba 2006-10-30T22:14:02Z

<p>Map7: </p> <hr /> <div>Samba ([http://www.samba.org samba.org]) is an open-source program that, in a nutshell, makes FreeBSD (or any flavor of Unix it has been ported to) look and act like a Windows machine from the perspective of REAL windows machines. <br /> <br /> This means Samba can be used to set up network shares (file and printer) that Win.x machines on the same network can access, just as if the FreeBSD machine was an actual Windows server.<br /> <br /> This main page will be updated as articles are added, and will act as a portal to the rest of the Samba-related content on this wiki.<br /> <br /> These articles will cover installing Samba under FreeBSD, configuring it, and configuring the client windows machines.<br /> <br /> [[Samba_Installation]] - <br /> [[Samba_Configuration]]<br /> [[Category:Ports and Packages]]</div>

Map7 http://www.freebsdwiki.net/index.php/Samba 2006-10-30T22:13:00Z

<p>Map7: </p> <hr /> <div>Samba ([http://www.samba.org samba.org]) is an open-source program that, in a nutshell, makes FreeBSD (or any flavor of Unix it has been ported to) look and act like a Windows machine from the perspective of REAL windows machines. <br /> <br /> This means Samba can be used to set up network shares (file and printer) that Win.x machines on the same network can access, just as if the FreeBSD machine was an actual Windows server.<br /> <br /> This main page will be updated as articles are added, and will act as a portal to the rest of the Samba-related content on this wiki.<br /> <br /> These articles will cover installing Samba under FreeBSD, configuring it, and configuring the client windows machines.<br /> <br /> [[Samba_Installation]] - <br /> [[Samba_Configuration]] -<br /> [[SWAT_-_Samba_Web_Interface‎]]<br /> [[Category:Ports and Packages]]</div>

Map7 http://www.freebsdwiki.net/index.php/Samba 2006-10-30T22:12:22Z

<p>Map7: </p> <hr /> <div>Samba ([http://www.samba.org samba.org]) is an open-source program that, in a nutshell, makes FreeBSD (or any flavor of Unix it has been ported to) look and act like a Windows machine from the perspective of REAL windows machines. <br /> <br /> This means Samba can be used to set up network shares (file and printer) that Win.x machines on the same network can access, just as if the FreeBSD machine was an actual Windows server.<br /> <br /> This main page will be updated as articles are added, and will act as a portal to the rest of the Samba-related content on this wiki.<br /> <br /> These articles will cover installing Samba under FreeBSD, configuring it, and configuring the client windows machines.<br /> <br /> [[Samba_Installation]] - <br /> [[Samba_Configuration]] -<br /> [[SWAT - Samba Web Interface‎]]<br /> [[Category:Ports and Packages]]</div>

Map7 http://www.freebsdwiki.net/index.php/Samba,_SWAT_(Samba_Web_Interface) 2006-10-30T22:11:05Z

<p>Map7: </p> <hr /> <div>==Web Interface (SWAT)==<br /> If you would like to use a Web interface to make this configuration much easier then you need to configure SWAT<br /> <br /> uncomment the following line in your /etc/inetd.conf<br /> swat stream tcp nowait/400 root /usr/local/sbin/swat swat<br /> <br /> Restart inetd<br /> # killall -HUP inetd<br /> <br /> Now you should be able to go to the address<br /> http://localhost:901<br /> <br /> &lt;b&gt;NOTE&lt;/b&gt;<br /> SWAT has been known to have security flaws, use at own risk.<br /> <br /> [[Category:Common Tasks]] [[Category:Configuring FreeBSD]]</div>

Map7 http://www.freebsdwiki.net/index.php/Burncd 2006-10-30T02:37:52Z

<p>Map7: </p> <hr /> <div>When using burncd your data must be put into a CD Image (iso file) before hand.<br /> <br /> Install mkisofs<br /> # pkg_add -r cdrtools<br /> <br /> Make sure /dev/acd* have 666 permissions so users can write cd's<br /> # chmod 666 /dev/acd*<br /> <br /> Make the iso<br /> # mkisofs -o file.iso -r &lt;files&gt;<br /> <br /> Burn the CD<br /> # burncd -f /dev/acd0 data file.iso fixate<br /> Or do both commands in one:<br /> # mkisofs -r mystuff | burncd -f /dev/acd0 -s max data – fixate<br /> <br /> Shortcut (if you are burning to acd0 you don't have to use -f as acd0 is default)<br /> # mkisofs -r mystuff | burncd data – fixate<br /> <br /> <br /> [[Category:FreeBSD for Workstations]]</div>

Map7 http://www.freebsdwiki.net/index.php/Burncd 2006-10-30T02:31:40Z

<p>Map7: </p> <hr /> <div>When using burncd your data must be put into a CD Image (iso file) before hand.<br /> <br /> Install mkisofs<br /> # pkg_add -r cdrtools<br /> <br /> Make sure /dev/acd* have 666 permissions so users can write cd's<br /> # chmod 666 /dev/acd*<br /> <br /> Make the iso<br /> # mkisofs -o file.iso -r &lt;files&gt;<br /> <br /> Burn the CD<br /> # burncd -f /dev/acd0 data file.iso fixate<br /> Or do both commands in one:<br /> # mkisofs -r mystuff | burncd -f /dev/acd0 -s max data – fixate<br /> <br /> <br /> <br /> [[Category:FreeBSD for Workstations]]</div>

Map7 http://www.freebsdwiki.net/index.php/Burncd 2006-10-30T01:46:10Z

<p>Map7: </p> <hr /> <div>When using burncd your data must be put into a CD Image (iso file) before hand.<br /> <br /> Install mkisofs<br /> # pkg_add -r cdrtools<br /> <br /> Make sure /dev/acd* have 666 permissions so users can write cd's<br /> # chmod 666 /dev/acd*<br /> <br /> Make the iso<br /> # mkisofs -o file.iso -r &lt;files&gt;<br /> <br /> Burn the CD<br /> # burncd -f /dev/acd1 data file.iso fixate<br /> Or do both commands in one:<br /> # mkisofs -r mystuff | burncd -s max data – fixate<br /> <br /> <br /> <br /> [[Category:FreeBSD for Workstations]]</div>

Map7 http://www.freebsdwiki.net/index.php/Samba,_Configuration 2006-10-29T23:21:44Z

<p>Map7: </p> <hr /> <div>This article will walk you through a quick setup of [[Samba]] - creating directories to be shared, telling Samba to share those directories, how to limit access to different shares, and finally, how to set up a windows machine to have unfettered access to appropriate shares based on the currently logged in user. This article assumes you have a fresh, unconfigured [[Samba Installation]] to work with.<br /> <br /> == Setting up your shares on the machine ==<br /> <br /> First we need to decide what we're going to share, or at the very least, where the shares will actually reside. The simplest way to do this is to simply create a new directory in an easy to remember place, say, '''/usr'''. You can either share that new folder directly, or create several new directories within it, and limit access to each directory based on criteria I will make clear later in this article. For now, let's assume you have two sets of documents, public and private, and that you want to limit users' access to those documents based on who they are - they can either access both, or just public. So:<br /> <br /> Oyabun# '''mkdir /usr/smbroot'''<br /> Oyabun# '''mkdir /usr/smbroot/public'''<br /> Oyabun# '''mkdir /usr/smbroot/private'''<br /> <br /> The first command creates the '''/usr/smbroot/''' directory, which will hold all of your shares. The second command creates the public directory, which '''all''' users will be able to access, and the third command creates the private directory, which only '''select''' users will be able to access.<br /> <br /> Now we need to set [[permissions]] on these directories. The [[permissions]] article goes into great detail about permissions, but a quick run through here will be fine. We'll use [[chown]] to change ownership of these two directories now. We'll assume you have or will set up two groups for your users, one group named '''public''', and another named '''private'''.<br /> <br /> Oyabun# '''chown :public /usr/smbroot/public'''<br /> Oyabun# '''chown :private /usr/smbroot/private'''<br /> <br /> The first command sets the owning group of /usr/smbroot/public to :public. The second command assigns ownership of /usr/smbroot/private to the group :private.<br /> <br /> Now we need to set the actual [[permissions]] with [[chmod]].<br /> <br /> Oyabun# '''chmod 770 /usr/smbroot/public'''<br /> Oyabun# '''chmod 770 /usr/smbroot/private'''<br /> <br /> Same [[permissions]] for each directory, broken down thusly: The first '''7''' is the 'owner' flag, and 7 means read/write/execute. The owner can do all of those things. The second '''7''' is the group flag, meaning the owning :group can also r/w/x. The third character, '''0''', is in the 'rest of the world' position, meaning anyone who is NOT the owner, and NOT a member of the owning group. They can't read, they can't write, and they can't execute. Since we're not setting up anonymous access, we don't want users who aren't explicitly defined as having access to actually have any access, and this will accomplish that.<br /> <br /> == Configuring Samba to use your shares and interface with local Win.X machines ==<br /> <br /> Ok, now we have the shares set up appropriately, we just need to define them for Samba. In '''/usr/local/etc/''', there is a file named &quot;'''smb.conf.default'''&quot;. This is a seriously large and complex file with waaaay more options than the average user will ever need to get Samba up and running. I highly suggest you go through it, as it has several examples of methods used to share directories, and access restriction methods. For this article, we'll be writing an [[smb.conf]] from scratch.<br /> <br /> '''[global]'''<br /> <br /> The first section of your new [[smb.conf]] file should look like this:<br /> <br /> [global]<br /> workgroup = WORKGROUP<br /> server string = NameOfServer<br /> log file = /var/log/log.%m<br /> max log size = 50<br /> security = user<br /> encrypt passwords = yes<br /> socket options = TCP_NODELAY<br /> preferred master = yes<br /> <br /> '''[global]''' is a header in the file, telling Samba all entries after that, before the next [section] are to be globally applied.<br /> <br /> '''workgroup = WORKGROUP''' - Specifies which Windows Workgroup to make the server a member of.<br /> <br /> '''server string = NameOfServer''' - Names the server. This is the name you'll see in network neighborhood. For example, my smb.conf names my server 'Oyabun'. (cuz it's the boss!)<br /> <br /> '''log file = /var/log/log%m''' - Tells Samba to create log files for each machine that connects in the var/log/ directory. For example, if a machine with the name of ''johndesktop'' connected, a log file named '''log.johndesktop''' would be created in /var/log, and appropriate entries for that machine would be made there.<br /> <br /> '''max log size = 50''': limits the size of each log files to x kilobytes, in this case 50. This is so you don't find a gig of logs a year down the road.<br /> <br /> '''security = user''': This is '''important''', and integral to simple networking between your new Samba server and your Windows machines.<br /> <br /> '''encrypt passwords = yes''': This is also '''important''' - passwords must be encrypted for each machine to successfuly negotiate login credentials with your Samba server.<br /> <br /> '''socket options = TCP_NODELAY''': This is not required, but the Samba documentation within smb.conf.default suggests this may yield better performance, so I include it.<br /> <br /> '''preferred master = yes''': Windows machines &quot;elect&quot; master browsers, which is a machine which takes on the duties of describing to other machines what all the machine names and locations are. Since your Samba machine is likely to be the sanest machine on your network, it's a good idea to have it 'fudge' the election results and always be the master browser. This option causes Samba to force a browser election when it starts up, and cheats to give it a higher chance of 'winning'.<br /> <br /> And that's the global section. Now, on to actually setting up shares.<br /> <br /> <br /> ----<br /> <br /> '''[homes]'''<br /> <br /> If you want your users to be able to access the home directories of their FreeBSD user accounts, add a [homes] section. If you do NOT want individual users to have private storage areas, do not include this section.<br /> <br /> [homes]<br /> comment = Home Directories<br /> browseable = no<br /> writeable = yes<br /> <br /> The mere existence of [homes] tells Samba to allow users to have access to their home directories via network sharing. If it's not there, they don't have it.<br /> <br /> '''comment = Home Directories''' is a description for the [section], and will show up in Windows Explorer under the 'comment' field.<br /> <br /> '''browseable = no''' means users other than the owner can't see or browse the share. (I can't see your home directory, you can't see mine, but we're both valid users.) Similar in purpose and execution to the 'My Documents' folder Windows users are familiar with. Each user has their own 'My Documents' folder.<br /> <br /> '''writeable = yes''' means users can save files in their home directories from across the network.<br /> <br /> That's it, setting up home directories is simple.<br /> <br /> ---<br /> <br /> '''[public]'''<br /> <br /> Now we'll set up the publicly accessible folder, located at '''/usr/smbroot/public/'''.<br /> <br /> [public]<br /> comment = Public<br /> path = /usr/smbroot/public<br /> public = no<br /> writeable = yes<br /> write list = @public<br /> directory mask = 0770<br /> create mask = 0770<br /> <br /> '''[public]''': Create a new share named 'Public', which will look like a folder named 'Public' in Network Neighborhood.<br /> <br /> '''comment = Public''': Same deal, this fills the 'comment' field in windows explorer / network neighborhood, when you're looking at the share.<br /> <br /> '''path = /usr/smbroot/public''': This tells samba exactly where on the local machine to store files for this share. This is pretty important.<br /> <br /> '''public = no''': This is sort of counter-intuitive, but you don't want this set to yes.<br /> <br /> '''writeable = yes''': This tells Samba to let authorized users write to the directory.<br /> <br /> '''write list = @public''': Lists the ''users'' and ''@groups'' allowed to write here. This is important! To define this further, or add more users or @groups, you'd write the line like this:<br /> &quot;valid users = joe bill @public @friends @dogs&quot;.<br /> <br /> '''directory mask = 0750''': The directory mask setting controls the '''most permissive''' setting Windows clients are allowed to give a directory. In this example, the mask is set to 750, so a client can set read, write, and execute permissions to anything it wants to for the directory's owner; but for the group the Windows client can only set read and execute permissions, and since the &quot;world&quot; bit is set to 0, the Windows client will be unable to set any allowable permissions at all for &quot;world&quot; (neither the owner nor the group) for that directory. Note that the windows client is free to set ''less'' permissive settings on the directory - if it wanted to, it could still deny access to the owner or group; it just can't ''give'' access more permissive than that specified by the mass.<br /> <br /> '''create mask = 0750''': Same deal, only this applies to files.<br /> <br /> That's it - you've defined all the important parts of the share for Samba, so it knows where to find it, and how to limit users' access to it.<br /> <br /> Test your new config with [[testparm]], which is a Samba tool that lets you validate your smb.conf.<br /> <br /> Oyabun# '''testparm''' <br /> <br /> I won't list the results here, but you should see a list of your shares. If there are any warnings or error messages, you'll want to analyze and correct the problem. Lastly, testparm will dump your smb.conf to the console.<br /> <br /> ---<br /> <br /> '''[private]'''<br /> <br /> Now we'll set up the private share. It will actually look just like the public share, with a few small changes.<br /> <br /> [private]<br /> comment = Private<br /> path = /usr/smbroot/private<br /> public = no<br /> writeable = yes<br /> valid users = @private<br /> write list = @private<br /> directory mask = 0770<br /> create mask = 0770<br /> <br /> Obviously we defined the basic stuff like [private] and where the directory is.<br /> <br /> '''valid users = @private''' - This prevents anyone who is not a member of @private from having access to this share. Because '''public = no''', people who are NOT members of @private won't even see this share when they browse the server.<br /> <br /> That's it, you now have two distinct shares set up, with two distinct sets of criteria to determine who gets access to those shares from a windows machine.<br /> <br /> == User accounts in BSD, Samba, and Windows ==<br /> <br /> There are two parts to this step, adding matching matching user accounts to the Samba server and the various windows machines, and adding matching Samba passwords to the Samba server for each user. '''Usernames and passwords must match exactly between the client Windows machines and the Samba server.'''<br /> <br /> Let's say ''Bob'' logs onto his windows machine with the username &quot;''bob''&quot; and the password &quot;''syeruncle''&quot;. He already has an existing windows account, obviously, so you don't need to set that up, but if he didn't, you would. Bob is going to be a member of the @public group, and Greg will be a member of @private.<br /> <br /> The quickest way to do this is to use '''/stand/[[sysinstall]]''' to add the user. You can also add users via the command line with [[adduser]] or [[pw]]. Make sure you are root before trying to add user accounts or Samba accounts, and remember to make each user a member of the appropriate group!<br /> <br /> Oyabun# '''pw useradd bob -g public'''<br /> Oyabun# '''pw useradd greg -g private''' <br /> <br /> Now we need to use [[smbpasswd]] to validate these users in the eyes of Samba.<br /> <br /> Oyabun# '''smbpasswd -a bob'''<br /> New SMB password:<br /> Retype new SMB password:<br /> Password changed for user bob.<br /> <br /> In this example, as root, I used the [[smbpasswd]] command to create a Samba account for ''bob''. It then asked me to enter a password for the new user, asked me to confirm it, and announced that the password was changed.<br /> <br /> Repeat this process for ''greg'', entering greg's password.<br /> <br /> If ''greg'' and ''bob'' are not really unix users at all, but only windows users that you want to be able to access Samba shares, you may wish to consider making sure they can't use the system accounts you created for them to actually log in to the box. For example:<br /> <br /> Oyabun# '''[[pw]] usermod bob -s /sbin/nologin'''<br /> Oyabun# '''su bob'''<br /> This account is currently not available.<br /> Oyabun#<br /> <br /> In this example, we set the ''bob'' account's default shell to /sbin/nologin, and then checked to make sure that account really couldn't shell into the box by using [[su]] to see what would happen if someone tried.<br /> <br /> ---<br /> <br /> Finally, we're done. We have shares set up, user accounts are in place, and everything is ready to go - now we just have to start Samba. This is easy. A startup script was placed in &quot;'''/usr/local/etc/rc.d/'''&quot;, with a likely name of &quot;''samba.sh.sample''&quot;.<br /> <br /> Let's rename it, and run it.<br /> <br /> &lt;pre&gt;Oyabun# cd /usr/local/etc/rc.d<br /> Oyabun# mv samba.sh.sample samba.sh<br /> Oyabun# /usr/local/etc/rc.d/samba start<br /> SambaOyabun#<br /> Oyabun#&lt;/pre&gt;<br /> <br /> First, rename the file from samba.sh.sample to samba.sh. Then, execute it, using the full path (it will complain otherwise). If all went well, after execting ''samba.sh start'', you'll see ''Samba'' inserted before the name of your server at the next shell prompt. This means Samba is indeed running, and that you can now attempt to connect to this machine from your Windows machines. You should do so, testing the various accounts you have set up to make sure they can all connect.<br /> <br /> Congrats, you now have a Samba server.<br /> <br /> ==Web Interface (SWAT)==<br /> If you would like to use a Web interface to make this configuration much easier then you need to configure SWAT<br /> <br /> uncomment the following line in your /etc/inetd.conf<br /> swat stream tcp nowait/400 root /usr/local/sbin/swat swat<br /> <br /> Restart inetd<br /> # killall -HUP inetd<br /> <br /> Now you should be able to go to the address<br /> http://localhost:901<br /> <br /> <br /> See also: [[Samba]] - [[Samba_Installation]]<br /> <br /> [[Category:Common Tasks]] [[Category:Configuring FreeBSD]]</div>

Map7 http://www.freebsdwiki.net/index.php/Flash 2006-10-27T02:46:27Z

<p>Map7: /* How to install flash */</p> <hr /> <div>==How to install flash==<br /> <br /> First install linuxpluginwrapper<br /> # pkg_add -r linuxpluginwrapper<br /> Or with options:<br /> # cd /usr/ports/*/linuxpluginwrapper;make install<br /> <br /> Next install flashplugin7<br /> # cd /usr/ports/*/linux-flashplugin7;make install<br /> <br /> If it cannot fetch the file download it from here:<br /> http://freshmeat.net/projects/flashplugin/<br /> <br /> <br /> <br /> <br /> ===libmap.conf===<br /> <br /> Add the following to /etc/libmap.conf<br /> # Flash7 for Firefox<br /> [/usr/local/lib/npapi/linux-flashplugin/libflashplayer.so]<br /> libpthread.so.0 pluginwrapper/flash7.so<br /> libdl.so.2 pluginwrapper/flash7.so<br /> libz.so.1 libz.so.3<br /> libstdc++-libc6.2-2.so.3 libstdc++.so.4<br /> libm.so.6 libm.so.4<br /> libc.so.6 pluginwrapper/flash7.so<br /> <br /> <br /> # Flash6 for Konqueror<br /> [/usr/X11R6/lib/linux-flashplugin6/libflashplayer.so]<br /> libpthread.so.0 pluginwrapper/flash6.so<br /> libdl.so.2 pluginwrapper/flash6.so<br /> libz.so.1 libz.so.3<br /> libstdc++-libc6.2-2.so.3 libstdc++.so.5<br /> libm.so.6 libm.so.4<br /> libc.so.6 pluginwrapper/flash6.so<br /> <br /> <br /> ===Konqueror===<br /> <br /> Go to Settings -&gt; Configure Konqueror -&gt; plugins<br /> <br /> Create the directory and link files<br /> # mkdir /usr/X11R6/lib/linux-flashplugin6<br /> # cd /usr/X11R6/lib/linux-flashplugin6<br /> # ln -s /usr/local/lib/npapi/linux-flashplugin/flashplayer.xpt<br /> # ln -s /usr/local/lib/npapi/linux-flashplugin/libflashplayer.so<br /> <br /> Now hit 'Scan for new plugins'<br /> <br /> Now go and test it out.<br /> <br /> ===Native Firefox===<br /> <br /> You will need to patch a file and compile it's all explained on this site:<br /> <br /> http://www.jail.se/freebsd.html<br /> <br /> ==External Links==<br /> http://freebsd.kde.org/howtos/konqueror-flash.php<br /> <br /> <br /> [[Category : FreeBSD Multimedia]]</div>

Map7 http://www.freebsdwiki.net/index.php/Flash 2006-10-27T02:45:25Z

<p>Map7: /* How to install flash7 in Konqueror */</p> <hr /> <div>==How to install flash==<br /> <br /> First install linuxpluginwrapper<br /> # pkg_add -r linuxpluginwrapper<br /> Or with options:<br /> # cd /usr/ports/*/linuxpluginwrapper;make install<br /> <br /> Install linuxthreads<br /> # cd /usr/ports/*/linuxthreads;make install<br /> <br /> Next install flashplugin7<br /> # cd /usr/ports/*/linux-flashplugin7;make install<br /> <br /> If it cannot fetch the file download it from here:<br /> http://freshmeat.net/projects/flashplugin/<br /> <br /> <br /> <br /> <br /> ===libmap.conf===<br /> <br /> Add the following to /etc/libmap.conf<br /> # Flash7 for Firefox<br /> [/usr/local/lib/npapi/linux-flashplugin/libflashplayer.so]<br /> libpthread.so.0 pluginwrapper/flash7.so<br /> libdl.so.2 pluginwrapper/flash7.so<br /> libz.so.1 libz.so.3<br /> libstdc++-libc6.2-2.so.3 libstdc++.so.4<br /> libm.so.6 libm.so.4<br /> libc.so.6 pluginwrapper/flash7.so<br /> <br /> <br /> # Flash6 for Konqueror<br /> [/usr/X11R6/lib/linux-flashplugin6/libflashplayer.so]<br /> libpthread.so.0 pluginwrapper/flash6.so<br /> libdl.so.2 pluginwrapper/flash6.so<br /> libz.so.1 libz.so.3<br /> libstdc++-libc6.2-2.so.3 libstdc++.so.5<br /> libm.so.6 libm.so.4<br /> libc.so.6 pluginwrapper/flash6.so<br /> <br /> <br /> ===Konqueror===<br /> <br /> Go to Settings -&gt; Configure Konqueror -&gt; plugins<br /> <br /> Create the directory and link files<br /> # mkdir /usr/X11R6/lib/linux-flashplugin6<br /> # cd /usr/X11R6/lib/linux-flashplugin6<br /> # ln -s /usr/local/lib/npapi/linux-flashplugin/flashplayer.xpt<br /> # ln -s /usr/local/lib/npapi/linux-flashplugin/libflashplayer.so<br /> <br /> Now hit 'Scan for new plugins'<br /> <br /> Now go and test it out.<br /> <br /> ===Native Firefox===<br /> <br /> You will need to patch a file and compile it's all explained on this site:<br /> <br /> http://www.jail.se/freebsd.html<br /> <br /> ==External Links==<br /> http://freebsd.kde.org/howtos/konqueror-flash.php<br /> <br /> <br /> [[Category : FreeBSD Multimedia]]</div>

Map7 http://www.freebsdwiki.net/index.php/Flash 2006-10-27T00:24:08Z

<p>Map7: </p> <hr /> <div>==How to install flash7 in Konqueror==<br /> <br /> First install linuxpluginwrapper<br /> # pkg_add -r linuxpluginwrapper<br /> Or with options:<br /> # cd /usr/ports/*/linuxpluginwrapper;make install<br /> <br /> Next install flashplugin7<br /> # cd /usr/ports/*/linux-flashplugin7;make install<br /> <br /> If it cannot fetch the file download it from here:<br /> http://freshmeat.net/projects/flashplugin/<br /> <br /> ===libmap.conf===<br /> <br /> Add the following to /etc/libmap.conf<br /> # Flash7 for Firefox<br /> [/usr/local/lib/npapi/linux-flashplugin/libflashplayer.so]<br /> libpthread.so.0 pluginwrapper/flash7.so<br /> libdl.so.2 pluginwrapper/flash7.so<br /> libz.so.1 libz.so.3<br /> libstdc++-libc6.2-2.so.3 libstdc++.so.4<br /> libm.so.6 libm.so.4<br /> libc.so.6 pluginwrapper/flash7.so<br /> <br /> <br /> # Flash6 for Konqueror<br /> [/usr/X11R6/lib/linux-flashplugin6/libflashplayer.so]<br /> libpthread.so.0 pluginwrapper/flash6.so<br /> libdl.so.2 pluginwrapper/flash6.so<br /> libz.so.1 libz.so.3<br /> libstdc++-libc6.2-2.so.3 libstdc++.so.5<br /> libm.so.6 libm.so.4<br /> libc.so.6 pluginwrapper/flash6.so<br /> <br /> <br /> ===Konqueror===<br /> <br /> Go to Settings -&gt; Configure Konqueror -&gt; plugins<br /> <br /> Create the directory and link files<br /> # mkdir /usr/X11R6/lib/linux-flashplugin6<br /> # cd /usr/X11R6/lib/linux-flashplugin6<br /> # ln -s /usr/local/lib/npapi/linux-flashplugin/flashplayer.xpt<br /> # ln -s /usr/local/lib/npapi/linux-flashplugin/libflashplayer.so<br /> <br /> Now hit 'Scan for new plugins'<br /> <br /> Now go and test it out.<br /> <br /> ===Native Firefox===<br /> <br /> You will need to patch a file and compile it's all explained on this site:<br /> <br /> http://www.jail.se/freebsd.html<br /> <br /> ==External Links==<br /> http://freebsd.kde.org/howtos/konqueror-flash.php<br /> <br /> <br /> [[Category : FreeBSD Multimedia]]</div>

Map7 http://www.freebsdwiki.net/index.php/CUPS 2006-10-26T05:35:12Z

<p>Map7: /* KDE Setup */</p> <hr /> <div>CUPS (Common Unix Printing System)<br /> This makes it easy to add printers to your system and programs such as firefox will pick up the printer list automatically.<br /> <br /> ==Installing CUPS==<br /> # pkg_add -r cups<br /> <br /> or <br /> <br /> # cd /usr/ports/print/cups<br /> # make install clean<br /> <br /> ==KDE Setup==<br /> You can setup any non KDE applications such as Openoffice to use the KDE printer dialogue by setting up the default printer of that applications as:<br /> <br /> kprinter -stdin<br /> <br /> <br /> ===Openoffice===<br /> Change the default printer in openoffice spadmin program<br /> <br /> <br /> ===xpdf===<br /> <br /> Add the following to /usr/X11R6/etc/xpdfrc config file.<br /> psFile &quot;|kprinter -stdin&quot;<br /> <br /> ==CUPS to PDF==<br /> CUPS can also be used to print directly from any program to a PDF file.<br /> <br /> # pkg_add -r cups-pdf<br /> <br /> <br /> ==CUPS mimics lpr==<br /> If you have old programs which use lpr to print then you should install CUPS-lpr<br /> <br /> # pkg_add -r cups-lpr<br /> <br /> ==CUPS Troubleshooting==<br /> <br /> ===CUPS with proxy===<br /> Make sure if you run a proxy to set localhost in the exceptions of your browser.<br /> Should now be able to connect to http://localhost:631<br /> <br /> ===CUPS and KDE Error===<br /> If you get an error in KDE print manager such as:<br /> cups host not found.<br /> <br /> Then change the host from<br /> host: /var/run/cups.sock<br /> to<br /> host: localhost<br /> <br /> <br /> <br /> <br /> ===CUPS and Gnome Warning===<br /> I've installed CUPS on a few machines and found everytime I do I cannot print though any gnome based application. If you like to use gnome applications to print your work, don't install CUPS just use LPD.<br /> <br /> programs which crashed right out when printing were:<br /> gedit, abiword, gnumeric, inkscape.<br /> <br /> &lt;b&gt;Error you will get&lt;/b&gt;<br /> &lt;pre&gt;<br /> (gdb) run<br /> Starting program: /usr/X11R6/bin/gnumeric<br /> <br /> Program received signal SIGBUS, Bus error.<br /> [Switching to Thread 3 (LWP 100326)]<br /> 0x29dfd450 in ippWriteIO (dst=0x8542000, cb=0x29dfa3bc &lt;httpWrite&gt;,<br /> blocking=1, parent=0x0, ipp=0x8517880) at ipp.c:1418<br /> 1418 ipp.c: No such file or directory.<br /> in ipp.c<br /> &lt;/pre&gt;<br /> <br /> ==links==<br /> http://forums.bsdnexus.com/viewtopic.php?id=36<br /> <br /> <br /> [[Category:Ports and Packages]]</div>

Map7 http://www.freebsdwiki.net/index.php/Flash 2006-10-26T05:27:56Z

<p>Map7: </p> <hr /> <div>==How to install flash7 in Konqueror==<br /> <br /> First install linuxpluginwrapper<br /> # pkg_add -r linuxpluginwrapper<br /> Or with options:<br /> # cd /usr/ports/*/linuxpluginwrapper;make install<br /> <br /> Next install flashplugin7<br /> # cd /usr/ports/*/linux-flashplugin7;make install<br /> <br /> If it cannot fetch the file download it from here:<br /> http://freshmeat.net/projects/flashplugin/<br /> <br /> ===libmap.conf===<br /> <br /> Add the following to /etc/libmap.conf<br /> <br /> # Flash7 with Konqueror<br /> [/usr/local/lib/npapi/linux-flashplugin/libflashplayer.so]<br /> libpthread.so.0 pluginwrapper/flash7.so<br /> libdl.so.2 pluginwrapper/flash7.so<br /> libz.so.1 libz.so.3<br /> libstdc++-libc6.2-2.so.3 libstdc++.so.5<br /> libm.so.6 libm.so.4<br /> libc.so.6 pluginwrapper/flash7.so<br /> <br /> ===Konqueror===<br /> <br /> Go to Settings -&gt; Configure Konqueror -&gt; plugins<br /> <br /> Add the following to the list to search:<br /> /usr/local/lib/npapi/linux-flashplugin<br /> <br /> Now hit 'Scan for new plugins'<br /> <br /> Now go and test it out.<br /> <br /> ===Native Firefox===<br /> <br /> You will need to patch a file and compile it's all explained on this site:<br /> <br /> http://www.jail.se/freebsd.html<br /> <br /> ==External Links==<br /> http://freebsd.kde.org/howtos/konqueror-flash.php<br /> <br /> <br /> [[Category : FreeBSD Multimedia]]</div>

Map7 http://www.freebsdwiki.net/index.php/Flash 2006-10-26T01:19:36Z

<p>Map7: /* How to install flash */</p> <hr /> <div>==How to install flash7 in Konqueror==<br /> <br /> First install linuxpluginwrapper<br /> # pkg_add -r linuxpluginwrapper<br /> Or with options:<br /> # cd /usr/ports/*/linuxpluginwrapper;make install<br /> <br /> Next install flashplugin7<br /> # cd /usr/ports/*/linux-flashplugin7;make install<br /> <br /> If it cannot fetch the file download it from here:<br /> http://freshmeat.net/projects/flashplugin/<br /> <br /> ===libmap.conf===<br /> <br /> Add the following to /etc/libmap.conf<br /> <br /> # Flash7 with Konqueror<br /> [/usr/local/lib/npapi/linux-flashplugin/libflashplayer.so]<br /> libpthread.so.0 pluginwrapper/flash6.so<br /> libdl.so.2 pluginwrapper/flash6.so<br /> libz.so.1 libz.so.3<br /> libstdc++-libc6.2-2.so.3 libstdc++.so.5<br /> libm.so.6 libm.so.4<br /> libc.so.6 pluginwrapper/flash6.so<br /> <br /> ===Konqueror===<br /> <br /> Go to Settings -&gt; Configure Konqueror -&gt; plugins<br /> <br /> Add the following to the list to search:<br /> /usr/local/lib/npapi/linux-flashplugin<br /> <br /> Now hit 'Scan for new plugins'<br /> <br /> Now go and test it out.<br /> <br /> ==External Links==<br /> http://freebsd.kde.org/howtos/konqueror-flash.php<br /> <br /> <br /> [[Category : FreeBSD Multimedia]]</div>

Map7 http://www.freebsdwiki.net/index.php/Flash 2006-10-26T01:19:15Z

<p>Map7: </p> <hr /> <div>==How to install flash==<br /> <br /> First install linuxpluginwrapper<br /> # pkg_add -r linuxpluginwrapper<br /> Or with options:<br /> # cd /usr/ports/*/linuxpluginwrapper;make install<br /> <br /> Next install flashplugin7<br /> # cd /usr/ports/*/linux-flashplugin7;make install<br /> <br /> If it cannot fetch the file download it from here:<br /> http://freshmeat.net/projects/flashplugin/<br /> <br /> ===libmap.conf===<br /> <br /> Add the following to /etc/libmap.conf<br /> <br /> # Flash7 with Konqueror<br /> [/usr/local/lib/npapi/linux-flashplugin/libflashplayer.so]<br /> libpthread.so.0 pluginwrapper/flash6.so<br /> libdl.so.2 pluginwrapper/flash6.so<br /> libz.so.1 libz.so.3<br /> libstdc++-libc6.2-2.so.3 libstdc++.so.5<br /> libm.so.6 libm.so.4<br /> libc.so.6 pluginwrapper/flash6.so<br /> <br /> ===Konqueror===<br /> <br /> Go to Settings -&gt; Configure Konqueror -&gt; plugins<br /> <br /> Add the following to the list to search:<br /> /usr/local/lib/npapi/linux-flashplugin<br /> <br /> Now hit 'Scan for new plugins'<br /> <br /> Now go and test it out.<br /> <br /> <br /> ==External Links==<br /> http://freebsd.kde.org/howtos/konqueror-flash.php<br /> <br /> <br /> [[Category : FreeBSD Multimedia]]</div>

Map7 http://www.freebsdwiki.net/index.php/CUPS 2006-10-26T00:28:41Z

<p>Map7: </p> <hr /> <div>CUPS (Common Unix Printing System)<br /> This makes it easy to add printers to your system and programs such as firefox will pick up the printer list automatically.<br /> <br /> ==Installing CUPS==<br /> # pkg_add -r cups<br /> <br /> or <br /> <br /> # cd /usr/ports/print/cups<br /> # make install clean<br /> <br /> ==KDE Setup==<br /> You can setup any non KDE applications such as Openoffice to use the KDE printer dialogue by setting up the default printer of that applications as:<br /> <br /> kprinter -stdin<br /> <br /> ==CUPS to PDF==<br /> CUPS can also be used to print directly from any program to a PDF file.<br /> <br /> # pkg_add -r cups-pdf<br /> <br /> <br /> ==CUPS mimics lpr==<br /> If you have old programs which use lpr to print then you should install CUPS-lpr<br /> <br /> # pkg_add -r cups-lpr<br /> <br /> ==CUPS Troubleshooting==<br /> <br /> ===CUPS with proxy===<br /> Make sure if you run a proxy to set localhost in the exceptions of your browser.<br /> Should now be able to connect to http://localhost:631<br /> <br /> ===CUPS and KDE Error===<br /> If you get an error in KDE print manager such as:<br /> cups host not found.<br /> <br /> Then change the host from<br /> host: /var/run/cups.sock<br /> to<br /> host: localhost<br /> <br /> <br /> <br /> <br /> ===CUPS and Gnome Warning===<br /> I've installed CUPS on a few machines and found everytime I do I cannot print though any gnome based application. If you like to use gnome applications to print your work, don't install CUPS just use LPD.<br /> <br /> programs which crashed right out when printing were:<br /> gedit, abiword, gnumeric, inkscape.<br /> <br /> &lt;b&gt;Error you will get&lt;/b&gt;<br /> &lt;pre&gt;<br /> (gdb) run<br /> Starting program: /usr/X11R6/bin/gnumeric<br /> <br /> Program received signal SIGBUS, Bus error.<br /> [Switching to Thread 3 (LWP 100326)]<br /> 0x29dfd450 in ippWriteIO (dst=0x8542000, cb=0x29dfa3bc &lt;httpWrite&gt;,<br /> blocking=1, parent=0x0, ipp=0x8517880) at ipp.c:1418<br /> 1418 ipp.c: No such file or directory.<br /> in ipp.c<br /> &lt;/pre&gt;<br /> <br /> ==links==<br /> http://forums.bsdnexus.com/viewtopic.php?id=36<br /> <br /> <br /> [[Category:Ports and Packages]]</div>

Map7 http://www.freebsdwiki.net/index.php/CUPS 2006-10-26T00:21:08Z

<p>Map7: </p> <hr /> <div>CUPS (Common Unix Printing System)<br /> This makes it easy to add printers to your system and programs such as firefox will pick up the printer list automatically.<br /> <br /> ==Installing CUPS==<br /> # pkg_add -r cups<br /> <br /> or <br /> <br /> # cd /usr/ports/print/cups<br /> # make install clean<br /> <br /> ==CUPS to PDF==<br /> CUPS can also be used to print directly from any program to a PDF file.<br /> <br /> # pkg_add -r cups-pdf<br /> <br /> <br /> ==CUPS mimics lpr==<br /> If you have old programs which use lpr to print then you should install CUPS-lpr<br /> <br /> # pkg_add -r cups-lpr<br /> <br /> ==CUPS Troubleshooting==<br /> <br /> ===CUPS with proxy===<br /> Make sure if you run a proxy to set localhost in the exceptions of your browser.<br /> Should now be able to connect to http://localhost:631<br /> <br /> ===CUPS and KDE Error===<br /> If you get an error in KDE print manager such as:<br /> cups host not found.<br /> <br /> Then change the host from<br /> host: /var/run/cups.sock<br /> to<br /> host: localhost<br /> <br /> <br /> <br /> <br /> ===CUPS and Gnome Warning===<br /> I've installed CUPS on a few machines and found everytime I do I cannot print though any gnome based application. If you like to use gnome applications to print your work, don't install CUPS just use LPD.<br /> <br /> programs which crashed right out when printing were:<br /> gedit, abiword, gnumeric, inkscape.<br /> <br /> &lt;b&gt;Error you will get&lt;/b&gt;<br /> &lt;pre&gt;<br /> (gdb) run<br /> Starting program: /usr/X11R6/bin/gnumeric<br /> <br /> Program received signal SIGBUS, Bus error.<br /> [Switching to Thread 3 (LWP 100326)]<br /> 0x29dfd450 in ippWriteIO (dst=0x8542000, cb=0x29dfa3bc &lt;httpWrite&gt;,<br /> blocking=1, parent=0x0, ipp=0x8517880) at ipp.c:1418<br /> 1418 ipp.c: No such file or directory.<br /> in ipp.c<br /> &lt;/pre&gt;<br /> <br /> ==links==<br /> http://forums.bsdnexus.com/viewtopic.php?id=36<br /> <br /> <br /> [[Category:Ports and Packages]]</div>

Map7 http://www.freebsdwiki.net/index.php/Format_new_msdos_drive 2006-10-24T05:01:22Z

<p>Map7: </p> <hr /> <div>To create and format a new FAT32 drive do the following:<br /> <br /> Go into sysinstall<br /> <br /> select fdisk<br /> <br /> use type 11 (fat32)<br /> <br /> exit sysinstall<br /> <br /> # newfs_msdos /dev/da0<br /> <br /> Note when I went to do this on a IDE drive on ad1 I had to do<br /> # newfs_msdos /dev/ad1s1<br /> <br /> Now you should be able to mount it as msdos.<br /> <br /> <br /> [[Category:Common Tasks]]</div>

Map7 http://www.freebsdwiki.net/index.php/Format_new_msdos_drive 2006-10-24T05:00:21Z

<p>Map7: </p> <hr /> <div>To create and format a new FAT32 drive do the following:<br /> <br /> Go into sysinstall<br /> <br /> <br /> [[Category:Common Tasks]]</div>

Map7 http://www.freebsdwiki.net/index.php/Scanner,_installing 2006-10-23T04:39:58Z

<p>Map7: </p> <hr /> <div>To install a scanner make sure that the scanner you are using is supported by FreeBSD.<br /> <br /> I'm going to use a HP Scanjet 6200C because it's supported and that's what I have laying around.<br /> <br /> Connect your scanner to the USB and type the following commands.<br /> <br /> ==Initial setup==<br /> # cd /dev<br /> # chmod 0660 uscanner0<br /> # chgrp operator uscanner0<br /> # pw groupmod operator -m &lt;user&gt;<br /> <br /> <br /> ==sane (text access to scanner)==<br /> <br /> Install through packages<br /> # pkg_add -r sane-frontends<br /> # pkg_add -r sane-backends<br /> <br /> Find your scanner, this doesn't mean that it will work though:<br /> # sane-find-scanner -q<br /> found USB scanner (vendor=0x03f0, product=0x0201) at /dev/uscanner0<br /> <br /> To scan a test page type the following (replacing hp with your scanner brand).<br /> # scanimage -d hp:/dev/uscanner0 &gt; /tmp/image.pnm<br /> <br /> To allow for gray scale<br /> # scanimage --mode Gray -d hp:/dev/uscanner0 &gt; /tmp/image.pnm<br /> <br /> If this all works then you want some automation so you don't have to tell scanimage the device.<br /> # scanimage -L<br /> device `hp:/dev/uscanner0' is a Hewlett-Packard ScanJet 62x0C flatbed scanner<br /> <br /> This should list your device, if it doesn't make sure you do the following commands:<br /> # cd /usr/local/etc/sane.d<br /> # cp -v dist/* .<br /> <br /> Now edit the file which relates to your scanner brand<br /> # vi hp.conf<br /> <br /> make sure that the device is set to /dev/uscanner0 at the end of the file with the line:<br /> /dev/uscanner0<br /> <br /> <br /> ==Xsane==<br /> <br /> Install through package system if you are not going to use gimp integration<br /> # pkg_add -r xsane<br /> <br /> Otherwise install through ports system.<br /> # cd /usr/ports/*/xsane;make install clean<br /> <br /> <br /> Find your scanner with this tool<br /> # sane-find-scanner -q<br /> <br /> <br /> <br /> <br /> ==Gimp==<br /> Yet to be done.<br /> <br /> ==Reference==<br /> <br /> For more information on how to configure/troubleshoot/user setup for scanners refer to the handbook:<br /> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/scanners.html<br /> <br /> [[Category:Configuring FreeBSD]]</div>

Map7 http://www.freebsdwiki.net/index.php/Scanner,_installing 2006-10-23T04:39:21Z

<p>Map7: </p> <hr /> <div>To install a scanner make sure that the scanner you are using is supported by FreeBSD.<br /> <br /> I'm going to use a HP Scanjet 6200C because it's supported and that's what I have laying around.<br /> <br /> Connect your scanner to the USB and type the following commands.<br /> <br /> # cd /dev<br /> # chmod 0660 uscanner0<br /> # chgrp operator uscanner0<br /> # pw groupmod operator -m &lt;user&gt;<br /> <br /> <br /> ==sane (text access to scanner)==<br /> <br /> Install through packages<br /> # pkg_add -r sane-frontends<br /> # pkg_add -r sane-backends<br /> <br /> Find your scanner, this doesn't mean that it will work though:<br /> # sane-find-scanner -q<br /> found USB scanner (vendor=0x03f0, product=0x0201) at /dev/uscanner0<br /> <br /> To scan a test page type the following (replacing hp with your scanner brand).<br /> # scanimage -d hp:/dev/uscanner0 &gt; /tmp/image.pnm<br /> <br /> To allow for gray scale<br /> # scanimage --mode Gray -d hp:/dev/uscanner0 &gt; /tmp/image.pnm<br /> <br /> If this all works then you want some automation so you don't have to tell scanimage the device.<br /> # scanimage -L<br /> device `hp:/dev/uscanner0' is a Hewlett-Packard ScanJet 62x0C flatbed scanner<br /> <br /> This should list your device, if it doesn't make sure you do the following commands:<br /> # cd /usr/local/etc/sane.d<br /> # cp -v dist/* .<br /> <br /> Now edit the file which relates to your scanner brand<br /> # vi hp.conf<br /> <br /> make sure that the device is set to /dev/uscanner0 at the end of the file with the line:<br /> /dev/uscanner0<br /> <br /> <br /> ==Xsane==<br /> <br /> Install through package system if you are not going to use gimp integration<br /> # pkg_add -r xsane<br /> <br /> Otherwise install through ports system.<br /> # cd /usr/ports/*/xsane;make install clean<br /> <br /> <br /> Find your scanner with this tool<br /> # sane-find-scanner -q<br /> <br /> <br /> <br /> <br /> ==Gimp==<br /> Yet to be done.<br /> <br /> ==Reference==<br /> <br /> For more information on how to configure/troubleshoot/user setup for scanners refer to the handbook:<br /> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/scanners.html<br /> <br /> [[Category:Configuring FreeBSD]]</div>

Map7 http://www.freebsdwiki.net/index.php/X_Windows_Terminal 2006-10-15T11:07:31Z

<p>Map7: /* todo */</p> <hr /> <div>==Advantages==<br /> X Windows can be used in a Server-Client relationship. By setting up your X Windows Server you allow the use of all the programs on that computer to all the client PC's. <br /> <br /> There are many advantages of running client computers in this manner:<br /> * They don't even need a hard drive. <br /> * It's silent as there are no moving parts<br /> * The solution saves power as your computers are very thin.<br /> * Everything can be backed up centrally.<br /> * Boot times for client PC's are the fastest around.<br /> * Clients don't need much CPU speed, memory, etc. Because of this they would be very cheap. You could get away with using a Pentium 100Mhz with 32MB ram, no hard drive, no CD-ROM, no Floppy and a fanless power supply. You just need a ethernet card with a PXEBOOT ROM. (XDM mode)<br /> * Central management of applications, users, config<br /> <br /> ==From the Beginning==<br /> I've based this document on FreeBSD 6.1.<br /> <br /> Install FreeBSD 6.1 as per usual.<br /> I've setup my mount points as this:<br /> '''Part Mount Size'''<br /> ad0s1b Swap (equal to how much memory I have in my machine)<br /> ad0s1a / 512MB<br /> ad0s1d /var 1G<br /> ad0s1e /tmp 512MB<br /> ad0s1f /usr 2GB min.<br /> /diskless_ro 512MB<br /> /diskless_rw 1GB min.<br /> <br /> I selected 'A' for auto and then deleted /usr and created /usr as 2g.<br /> <br /> Select User-X install. Yes to Ports if you have the room.<br /> <br /> Select SSH Server and NFS Server in the installation process, for the rest of the options go with the default.<br /> <br /> <br /> NOTE: If you forget to add any of the labels above, you will have to reboot as you cannot add labels to your boot drive when you have booted off it. So boot of the installation CD and use the configure -&gt; label option in the sysinstall screen to add these labels to your boot drive. You may need to retype the mount points for /, /var, /tmp and /usr by hitting 'm' on each label. Once you have created these labels in the 'Disklabel Editor' then you can hit 'w' to write them to the disk. answer 'yes' to the next question, hit 'ok' to the warning message. Now quit and reboot. Add them to fstab (/dev/ad0s1g /diskless_ro) &amp; (/dev/ad0s1h /diskless_rw) and mount.<br /> <br /> I find the best way to get this working is to break it down in to small steps and get each step working independantly. IE: Setup NFS and see if you can mount it from another FreeBSD machine, don't just assume it will work and boot your PXE-Boot machine.<br /> <br /> <br /> Throughout my documentation<br /> <br /> 192.168.1.1 = the Server<br /> <br /> 192.168.1.2 = the client (may be a full freebsd system or pxeboot)<br /> <br /> <br /> At this point I normally install fluxbox with the following line:<br /> <br /> shell# pkg_add -r fluxbox-devel<br /> <br /> <br /> change your ~/.xinitrc file to the following:<br /> <br /> startfluxbox<br /> <br /> <br /> Use the following command to update your fluxbox menus:<br /> <br /> shell$ fluxbox-generate_menu<br /> <br /> ==Running a single application==<br /> <br /> To get started I have my server setup running FreeBSD, with X-Windows and a few applications. Nothing too special. Then I have my client PC, which to start off I used the frenzy 1.0 boot CD to perform these initial tests. You can get this from [http://frenzy.org.ua/eng/ frenzy website]. I entered into fluxbox, but you could equally use any X session.<br /> You must allow incoming connections this is done with two commands<br /> <br /> client$ startx -listen_tcp<br /> client$ xhost +<br /> <br /> This allows all computers to start applications on your client PC. It's dangerous but good for testing everything is setup correctly.<br /> <br /> client$ ssh &lt;server user@server ip&gt;<br /> eg: ssh mick@192.168.1.1<br /> <br /> ssh$ export DISPLAY='192.168.1.2:0'<br /> <br /> Or if your running bash:<br /> ssh$ DISPLAY=&lt;client ip&gt;:&lt;client display&gt;; export DISPLAY<br /> eg: DISPLAY=192.168.1.2:0; export DISPLAY<br /> <br /> <br /> ssh$ xcalc &amp;<br /> <br /> This should display on your client<br /> <br /> ==Running a whole X Windows Session (XDM)==<br /> This sets up a server so that you can share your X session with any clients which want to connect. (Simular to Terminal Services under windows)<br /> <br /> <br /> ===server===<br /> edit:<br /> /usr/X11R6/lib/X11/xdm/xdm-config<br /> <br /> comment out with a '!' the request line&lt;br&gt;<br /> DisplayManager.requestPort: 0<br /> <br /> edit:&lt;br&gt;<br /> /usr/X11R6/lib/X11/xdm/Xaccess<br /> <br /> Enter a single asterisk any where in the file, so the contents should be one asterisk and the rest commented out. There should be an asterisk on line 49 which you can uncomment.<br /> <br /> Whilst in the /usr/X11R6/lib/X11/xdm directory do these commands:<br /> shell# vi Xstartup<br /> <br /> Add into this file:<br /> &lt;pre&gt;<br /> #!/bin/sh<br /> #<br /> # Xstartup<br /> #<br /> # This program is run as root after the user is verified<br /> #<br /> if [ -f /etc/nologin ]; then<br /> xmessage -file /etc/nologin -timeout 30 -center<br /> exit 1<br /> fi<br /> sessreg -a -l $DISPLAY -x /usr/X11R6/lib/xdm/Xservers $LOGNAME<br /> /usr/X11R6/lib/xdm/GiveConsole<br /> exit 0<br /> &lt;/pre&gt;<br /> <br /> <br /> shell# chmod +x Xstartup<br /> <br /> <br /> Make sure your firewall has all traffic for you lan. (Need to know which exact ports to allow).<br /> <br /> <br /> &lt;b&gt;Make sure you &lt;/b&gt;create ~/.xsession for each user which requires access and enter your start up for x <br /> eg:<br /> <br /> startfluxbox<br /> <br /> &lt;b&gt;run xdm on server as root&lt;/b&gt;<br /> <br /> shell# xdm<br /> <br /> <br /> You can put this xdm into the /etc/ttys so that it starts automatically on boot up.<br /> <br /> ===client===<br /> make sure your not in X<br /> <br /> type this command:<br /> <br /> shell# X -broadcast<br /> <br /> This assumes that you are running only one server.<br /> Otherwise use:<br /> <br /> shell# X -query 192.168.1.1<br /> <br /> ==DHCP - Install and setup==<br /> Server setup.<br /> <br /> install through package<br /> # pkg_add -r isc-dhcp3-server<br /> <br /> We do this so we can define the root path for the diskless system.<br /> <br /> copy /usr/local/etc/dhcpd.conf.sample to /usr/local/etc/dhcpd.conf<br /> <br /> edit /usr/local/etc/dhcpd.conf and make sure it has these lines in it.<br /> &lt;pre&gt;<br /> # dhcpd.conf<br /> #<br /> # Sample configuration file for ISC dhcpd<br /> #<br /> <br /> # option definitions common to all supported networks...<br /> #option domain-name &quot;example.org&quot;;<br /> #option domain-name-servers ns1.example.org, ns2.example.org;<br /> <br /> default-lease-time 3600;<br /> max-lease-time 86400;<br /> <br /> # If this DHCP server is the official DHCP server for the local<br /> # network, the authoritative directive should be uncommented.<br /> authoritative;<br /> <br /> # ad-hoc DNS update scheme - set to &quot;none&quot; to disable dynamic DNS updates.<br /> ddns-update-style none;<br /> <br /> option root-path &quot;192.168.1.1:/diskless_ro&quot;;<br /> <br /> # lines added for pxeboot client<br /> use-host-decl-names on;<br /> next-server 192.168.1.1;<br /> filename &quot;pxeboot&quot;;<br /> <br /> # Use this to send dhcp log messages to a different log file (you also<br /> # have to hack syslog.conf to complete the redirection).<br /> log-facility local7;<br /> <br /> # No service will be given on this subnet, but declaring it helps the<br /> # DHCP server to understand the network topology.<br /> <br /> <br /> # This is a very basic subnet declaration.<br /> <br /> subnet 192.168.1.0 netmask 255.255.255.0 {<br /> range 192.168.1.10 192.168.1.20;<br /> }<br /> &lt;/pre&gt;<br /> <br /> Create the leases file<br /> &lt;pre&gt;<br /> # touch /var/db/dhcpd.leases<br /> &lt;/pre&gt;<br /> <br /> <br /> Restart the daemon<br /> &lt;pre&gt;<br /> # killall dhcpd<br /> # dhcpd<br /> &lt;/pre&gt;<br /> <br /> <br /> Add to /etc/rc.conf<br /> &lt;pre&gt;<br /> dhcpd_enable=&quot;YES&quot;<br /> &lt;/pre&gt;<br /> <br /> ===Using a seperate DHCP server===<br /> If you already have a DHCP server and you want to use that instead then you have to do these steps.<br /> <br /> <br /> ====On your DHCP Server====<br /> 1. edit /usr/local/etc/dhcpd.conf and add the following<br /> &lt;pre&gt;<br /> authoritative;<br /> ddns-update-style none;<br /> <br /> option root-path &quot;&lt;X Server IP&gt;:/diskless_ro&quot;;<br /> <br /> # lines added for pxeboot client<br /> use-host-decl-names on;<br /> next-server &lt;X Server IP&gt;;<br /> filename &quot;pxeboot&quot;;<br /> &lt;/pre&gt;<br /> 2. stop dhcpd<br /> 3. start dhcpd<br /> <br /> <br /> ====Client====<br /> Your client should boot now just remember that you may get a different IP now that you are talking to a different DHCP server so you have to change your exports file and copy accross a directory in /diskless_rw for the new IP. All this is done on the X Server.<br /> <br /> ==TFTP Setup==<br /> TFTP helps us transport the kernel to the PXE-Boot machines.<br /> <br /> &lt;pre&gt;<br /> # mkdir /tftpboot<br /> # cp /boot/pxeboot /tftpboot<br /> &lt;/pre&gt;<br /> <br /> Uncomment the following line in /etc/inetd.conf<br /> <br /> &lt;pre&gt;<br /> tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /tftpboot<br /> &lt;/pre&gt;<br /> <br /> Restart the inetd service<br /> &lt;pre&gt;<br /> # killall -HUP inetd<br /> &lt;/pre&gt;<br /> <br /> If inetd has not started automatically do the following:<br /> <br /> Add the following to /etc/rc.conf<br /> &lt;pre&gt;<br /> inetd_enable=&quot;YES&quot;<br /> &lt;/pre&gt;<br /> <br /> Now start inetd manually.<br /> &lt;pre&gt;<br /> # inetd<br /> &lt;/pre&gt;<br /> <br /> ===Test===<br /> To test that tftp has loaded type the following:<br /> &lt;pre&gt;<br /> # sockstat -4l | grep 69 <br /> &lt;/pre&gt;<br /> <br /> and you should see this:<br /> &lt;pre&gt;<br /> root inetd 13719 5 udp4 *:69 *:*<br /> &lt;/pre&gt;<br /> <br /> ==NFS Setup==<br /> Network File System. Here we share all the directories from the server so that the diskless clients see these drives as if those directories were the diskless client's.<br /> <br /> ===Server Setup===<br /> If you forgot to select 'Yes' to NFS server setup in the FreeBSD installation then you have to setup the server manually like so:<br /> <br /> Enable NFS /etc/rc.conf<br /> &lt;pre&gt;<br /> rpcbind_enable=&quot;YES&quot;<br /> nfs_server_enable=&quot;YES&quot;<br /> &lt;/pre&gt;<br /> <br /> ===Test===<br /> A quick test to see if your NFS server is acting normal:<br /> <br /> Edit the /etc/exports and add the following<br /> &lt;pre&gt;<br /> /usr -alldirs<br /> &lt;/pre&gt;<br /> <br /> This allows anyone to connect to your /usr mount.<br /> <br /> Now run these commands to restart and view your mounts<br /> &lt;pre&gt;<br /> # kill -HUP `cat /var/run/mountd.pid`<br /> # showmount -e<br /> &lt;/pre&gt;<br /> <br /> Now try and mount it from a client running BSD<br /> &lt;pre&gt;<br /> # mount -t nfs 192.168.1.1:/usr /mnt<br /> &lt;/pre&gt;<br /> <br /> <br /> ===Server exports setup===<br /> <br /> Make directories for each IP for your clients<br /> &lt;pre&gt;<br /> # cd /diskless_rw<br /> # mkdir 192.168.1.2<br /> # cd 192.168.1.2<br /> # mkdir etc var<br /> &lt;/pre&gt;<br /> <br /> Configure /etc/exports<br /> &lt;pre&gt;<br /> # file systems accessible only for reading:<br /> # Original way of linking up the /usr<br /> #/usr -ro -maproot=0 -network 192.168.1.0 -mask 255.255.255.0<br /> <br /> /usr -network 192.168.1.0 -mask 255.255.255.0<br /> /diskless_ro -ro -maproot=0 -network 192.168.1.0 -mask 255.255.255.0<br /> /diskless_rw/192.168.1.2/etc /diskless_rw/192.168.1.2/var -maproot=root 192.168.1.2<br /> <br /> &lt;/pre&gt;<br /> <br /> Restarting NFS<br /> &lt;pre&gt;<br /> # kill -HUP `cat /var/run/mountd.pid`<br /> &lt;/pre&gt;<br /> <br /> <br /> If NFS is not started yet do the following:<br /> &lt;pre&gt;<br /> data# rpcbind<br /> data# nfsd -u -t -n 20 -h 192.168.1.1<br /> data# mountd -r<br /> &lt;/pre&gt;<br /> <br /> Testing to see if the exports are correct<br /> &lt;pre&gt;<br /> data# showmount -e<br /> Exports list on localhost:<br /> /usr 192.168.1.0<br /> /diskless_rw/192.168.1.2/var 192.168.1.2<br /> /diskless_rw/192.168.1.2/etc 192.168.1.2<br /> /diskless_ro 192.168.1.0<br /> &lt;/pre&gt;<br /> <br /> ==Setup diskless_rw==<br /> Create directories<br /> <br /> &lt;pre&gt;<br /> # cd /diskless_rw/192.168.1.2/etc<br /> # mkdir pam.d X11<br /> <br /> # cd /diskless_rw/192.168.1.2/var<br /> # mkdir home log run tmp<br /> # chmod 1777 tmp<br /> &lt;/pre&gt;<br /> <br /> Create a swap file in the var directory for the client<br /> &lt;pre&gt;<br /> # dd if=/dev/zero of=/diskless_rw/192.168.1.2/var/swap bs=1k count=32000<br /> &lt;/pre&gt;<br /> <br /> in the /diskless_rw/&lt;ip&gt;/var/log directory I created the following log files so that syslogd would have files to write to:<br /> &lt;pre&gt;<br /> # cd /diskless_rw/192.168.1.2/var/log<br /> # touch messages security auth.log maillog lpd-errs xferlog cron debug.log slip.log ppp.log<br /> &lt;/pre&gt;<br /> <br /> <br /> Copy the following files from the systems /etc directory to /diskless_rw/&lt;client ip&gt;/etc<br /> # cp -Rv &lt;files&gt; /diskless_rw/&lt;ip&gt;/etc<br /> <br /> &lt;pre&gt;<br /> auth.conf<br /> disktab<br /> gettytab<br /> group<br /> hosts<br /> login.access<br /> login.conf<br /> login.conf.db<br /> master.passwd<br /> netconfig<br /> protocols<br /> pam.d<br /> pwd.db<br /> services<br /> spwd.db<br /> syslog.conf<br /> termcap -&gt; /usr/share/misc/termcap<br /> ttys<br /> &lt;/pre&gt;<br /> <br /> It's very important that you copy all the files in pam.d across otherwise you will not have a password prompt on your login.<br /> <br /> Create a fstab in /diskless_rw/&lt;ip&gt;/etc<br /> # touch /diskless_rw/&lt;ip&gt;/etc/fstab<br /> <br /> ==Setup diskless_ro==<br /> This is the common root mount for all pxe-boot clients.<br /> <br /> Copy accross important directories and kernel from boot to diskless_ro<br /> &lt;pre&gt;<br /> # cp -rv /bin /lib /libexec /sbin /boot /diskless_ro<br /> # mkdir /diskless_ro/usr<br /> &lt;/pre&gt;<br /> <br /> For some client machines you may have to disable the ACPI (Power management) in the /diskless_ro/boot/device.hints<br /> &lt;pre&gt;<br /> hint.acpi.0.disabled=&quot;1&quot; <br /> &lt;/pre&gt;<br /> <br /> Make a dev so that clients can boot without freezing.<br /> &lt;pre&gt;<br /> # mkdir /diskless_ro/dev<br /> &lt;/pre&gt;<br /> <br /> Make a directory so that we can mount var from the /diskless_rw/&lt;client ip&gt;/var<br /> &lt;pre&gt;<br /> # mkdir /diskless_ro/var<br /> &lt;/pre&gt; <br /> <br /> So we can use the systems /var/tmp and /usr/home directory make soft links to them<br /> &lt;pre&gt;<br /> # cd /diskless_ro<br /> # ln -s /var/tmp<br /> # ln -s /usr/home<br /> &lt;/pre&gt;<br /> <br /> We require a few files from the systems /etc directory to be copied into the /diskless_ro/etc for common use between the thin clients.<br /> &lt;pre&gt;<br /> # mkdir /diskless_ro/etc<br /> # cd /etc<br /> # cp /services /netconfig /login.conf /diskless_ro/etc<br /> &lt;/pre&gt;<br /> <br /> <br /> ===rc file===<br /> The /diskless_ro/etc/rc file is the first file which is ran after the kernel has loaded. Here we mount a the labels from the server.<br /> <br /> Create the /diskless_ro/etc/rc<br /> &lt;pre&gt;<br /> #!/bin/sh<br /> <br /> PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin; export PATH<br /> TMPDIR=~/tmp;export TMPDIR<br /> TMP=~/tmp;export TMP<br /> <br /> mount -t nfs 192.168.1.1:/usr /usr<br /> <br /> boot_ip=`/sbin/ifconfig | /usr/bin/grep &quot;inet &quot; | /usr/bin/grep -v 127.0.0.1 |<br /> /usr/bin/awk '{print $2}'`<br /> mount_nfs -L 192.168.1.1:/diskless_rw/${boot_ip}/etc /etc<br /> mount_nfs -L 192.168.1.1:/diskless_rw/${boot_ip}/var /var<br /> <br /> swapon /var/swap<br /> <br /> #rm -rf /var/tmp/*<br /> #rm -rf /var/tmp/.*<br /> <br /> # Option if you choose XDM terminals<br /> #X -query 192.168.1.1<br /> <br /> . /etc/rc2<br /> exit 0<br /> <br /> &lt;/pre&gt;<br /> <br /> &lt;b&gt;Remember to change 192.168.1.1 to your X server's IP&lt;/b&gt;<br /> <br /> The -L on the mount_nfs is there so we don't get flock errors.<br /> <br /> ===rc2 file===<br /> This sets up some links for libraries and the logging daemon.<br /> <br /> &lt;pre&gt;<br /> #!/bin/sh<br /> <br /> mount -a<br /> /sbin/ldconfig -elf /usr/lib/compat /usr/X11R6/lib /usr/local/lib<br /> <br /> syslogd<br /> &lt;/pre&gt;<br /> <br /> <br /> Now change permissions so rc can run.<br /> # chmod +x rc*<br /> <br /> Copy /diskless_ro/etc/rc and rc2 to /diskless_rw/&lt;client ip&gt;/etc<br /> # cp /diskless_ro/etc/rc* /diskless_rw/192.168.1.2/etc<br /> <br /> ==GRUB Floppy boot (optional)==<br /> <br /> (would like to compile this ourselves later)<br /> To get started we downloaded the image from www.hp.uab.edu/~ed/grub-net<br /> <br /> shell# dd if=/data/grub-net.img of=/dev/fd0<br /> <br /> Then we mounted it as msdos<br /> Remove/rename menu.1st from the grub directory as it was doing something funny with it. We think that it was looking for a tftp server through our dhcp and we don't have a the dhcp setup correctly here, so we wanted to do it manually.<br /> <br /> Reboot off the floppy now..<br /> <br /> grub&gt; ifconfig --address=192.168.1.2 --mask=255.255.255.0 --gateway=192.168.1.1<br /> --server=192.168.1.2<br /> <br /> OR you can use dhcp&lt;br&gt;<br /> <br /> grub&gt; dhcp&lt;br&gt; <br /> grub&gt; tftpserver 192.168.1.2&lt;br&gt;<br /> <br /> <br /> Setup tftp on your server, we created a directory /tftpboot. <br /> <br /> <br /> ===Starting diskless system through GRUB===<br /> This is an alternative boot loader. You can use this for testing, if you don't have a pxeboot chip, otherwise skip this section.<br /> <br /> These commands are half working...&lt;br&gt;<br /> <br /> grub&gt; root (nd)&lt;br&gt;<br /> grub&gt; kernel /kernel root=ad0s1a&lt;br&gt;<br /> grub&gt; pxeboot&lt;br&gt;<br /> <br /> ==Completely Diskless System (PXEBOOT ROM) (optional)==<br /> <br /> Running completely diskless by booting from a Network ROM Chip.<br /> <br /> We have now got a Intel GD82559 Etherexpress pro/100 Card.<br /> <br /> When we boot up on the client machine with that card it displays:&lt;br /&gt;<br /> &lt;br /&gt;<br /> Intel UNDI, PXE-2.0 (build 067)&lt;br /&gt;<br /> Copyright (C) 1997-1998 Intel Corporation&lt;br /&gt;<br /> &lt;br /&gt;<br /> Which we cannot get working so we have read that you have to update this version to Build 82.&lt;br /&gt;<br /> &lt;br /&gt;<br /> &lt;br /&gt;<br /> copy /boot/pxeboot to /tftpboot directory we made before&lt;br /&gt;<br /> &lt;br /&gt;<br /> - Downloaded proboot.exe from support.intel.com and unpacked into a windows box.&lt;br /&gt;<br /> - Copied ibautil.exe onto a windows 98 boot disk.&lt;br /&gt;<br /> - Rebooted the test box after disabling network boot on the nic (otherwise it'll kick in before the floppy).&lt;br /&gt;<br /> - Ran ibautil -iv to see what embedded image versions were available:&lt;br /&gt;<br /> &lt;br /&gt;<br /> Intel(R) Boot Agent XG v1.0.09&lt;br /&gt;<br /> Intel(R) Boot Agent GE v1.2.36&lt;br /&gt;<br /> Intel(R) Boot Agent FE v4.1.19&lt;br /&gt;<br /> &lt;br /&gt;<br /> - Ran ibautil -up to perform the image upgrade.&lt;br /&gt;<br /> &lt;br /&gt;<br /> It's interesting to note that no version showed up for out intel nic when initially running ibautil. After the upgrade, however, the version corectly showed as 4.1.19.&lt;br /&gt;&lt;br /&gt;<br /> <br /> I made sure that I had simular features to this in my dhcpd.conf file:&lt;br /&gt;<br /> option broadcast-address 192.168.254.255;&lt;br /&gt;<br /> option domain-name-servers 192.168.254.3;&lt;br /&gt;<br /> option domain-name &quot;simerson.net&quot;;&lt;br /&gt;<br /> option routers 192.168.254.1;&lt;br /&gt;<br /> option subnet-mask 255.255.255.0;&lt;br /&gt;<br /> server-name &quot;pxe-gw&quot;;&lt;br /&gt;<br /> server-identifier 192.168.254.3;&lt;br /&gt;<br /> next-server 192.168.254.3;&lt;br /&gt;<br /> default-lease-time -1;&lt;br /&gt;<br /> &lt;br /&gt;<br /> subnet 192.168.254.0 netmask 255.255.255.0 {&lt;br /&gt;<br /> range 192.168.254.32 192.168.254.99;&lt;br /&gt;<br /> option root-path &quot;/usr/local/export/pxe&quot;;&lt;br /&gt;<br /> filename &quot;pxeboot&quot;;&lt;br /&gt;<br /> }&lt;br /&gt;<br /> host cm.simerson.net {&lt;br /&gt;<br /> hardware ethernet 00:e0:18:98:f0:cc;&lt;br /&gt;<br /> fixed-address 192.168.254.126;&lt;br /&gt;<br /> }&lt;br /&gt;<br /> host c1.simerson.net {&lt;br /&gt;<br /> hardware ethernet 00:60:97:0e:bb:a7;&lt;br /&gt;<br /> fixed-address 192.168.254.131;&lt;br /&gt;<br /> }&lt;br /&gt;<br /> &lt;br /&gt;<br /> <br /> ==X config notes==<br /> On the X server the /etc/X11/xorg.conf file is only used for the X server not the clients.<br /> <br /> To use this same configuration for your X Terminal Clients copy this file to /diskless_rw/&lt;Client IP&gt;/etc/X11 and it will use it.<br /> <br /> ==Starting X on the client==<br /> There are two ways of doing this and it depends on your hardware mainly. <br /> <br /> 1. run all programs on the server using the servers CPU and Memory this we will call the 'XDM Method'<br /> 2. run all programs from the NFS mounts using the clients CPU and Memory but the HD of the server, this we will call the 'NFS Method'<br /> <br /> Both methods will boot from PXE-Boot and can be diskless.<br /> <br /> ===XDM Method===<br /> Recommended for machines less than 1Ghz 256MB<br /> <br /> This is quite simple to setup. Change your rc file in the /diskless_ro/etc directory to have this line at the end:<br /> &lt;pre&gt;<br /> X -query &lt;server ip&gt;<br /> &lt;/pre&gt;<br /> <br /> Make sure on the server you setup xdm to start on system startup<br /> # vi /etc/ttys<br /> <br /> Search for this line:<br /> ttyv8 &quot;/usr/X11R6/bin/xdm -nodaemon&quot; xterm off secure<br /> <br /> and change it to:<br /> ttyv8 &quot;/usr/X11R6/bin/xdm -nodaemon&quot; xterm on secure<br /> <br /> <br /> You can also type this command at the command line on the client to test before hand.<br /> <br /> ===NFS Method===<br /> Recommended for machines over 1Ghz 256MB or if you want to utilise any of the clients devices such as local HD, USB, CD/DVD burners, etc.<br /> <br /> This is much trickier.<br /> <br /> Log in<br /> Now type 'startx' at the command line.<br /> <br /> ==Custom Kernels==<br /> If you want to create custom kernels for your clients then do this:<br /> <br /> Create your custom kernel<br /> # cd /sys/i386/conf<br /> # cp GENERIC DISKLESS<br /> # vi DISKLESS<br /> <br /> Make changes and build and install<br /> <br /> # cd /usr/src<br /> # make buildkernel KERNCONF=DISKLESS<br /> # make installkernel KERNCONF=DISKLESS DESTDIR=/diskless_ro<br /> <br /> ==todo==<br /> Here are some of the jobs left to do to make this secure or generally better:<br /> <br /> - There must be a simplier way to set this up if your going to use XDM in the end. IE: do we need to do half of this tutorial if we are going to run XDM.<br /> <br /> - When the same user logs onto two seperate machines they cannot start firefox or thunderbird as it complains about being open somewhere else. This assumes you have firefox and thunderbird already open on both machines that you logged onto.<br /> <br /> ===Known Issues===<br /> <br /> - Doesn't work with HP-COMPAQ-T5525 thin client as it doesn't want to boot, it says it's missing libfreetype.so.9 which we do have it just cannot find it for some reason. It's trying to use the VIA chipset for graphics which is different to all the other clients I've loaded successfully so far.<br /> <br /> - USB mice not working instead use PS/2. If we got this working it may help get the HP T5525 working<br /> <br /> ===Keyboard repeating on notebooks===<br /> - typing on some keyboards (like my notebook) causes double characters to display if you type too fast. - This is the notebook, if you go and set the KDE Accessabiltiy options and set the keyboard rate to 50ms, this fixes the problem.<br /> <br /> ===USB mouse===<br /> <br /> Editing /etc/devd.conf file and searched for ums<br /> remarked out the action line.<br /> <br /> rebooted.<br /> <br /> Someone off IRC suggested that I build a GENERIC xorg.conf file which has vesa, usb mouse and ps/2 mouse configurations through it.<br /> <br /> I reverted everything back to normal ps/2 mouse config, copying my usb config files to the following:<br /> /etc/devd.conf_usb<br /> /etc/rc.conf_usb<br /> /etc/X11/xorg.conf_usb<br /> <br /> I think we need a seperate configuration for the HP, it uses a weird display driver.<br /> <br /> ==links==<br /> <br /> http://www.onlamp.com/pub/a/bsd/2004/09/09/diskless_server.html<br /> <br /> http://www.onlamp.com/pub/a/bsd/2004/09/30/diskless_clients.html<br /> <br /> http://people.freebsd.org/~alfred/pxe/en_US.ISO8859-1/articles/pxe/article.html<br /> <br /> http://www.the-labs.com/FreeBSD/Diskless/<br /> <br /> http://www.nber.org/sys-admin/FreeBSD-diskless.html<br /> <br /> <br /> <br /> http://wikitest.freebsd.org/MarkusBoelter<br /> <br /> http://www.daemonsecurity.com/pub/pxeboot/<br /> <br /> http://www.kano.org.uk/projects/pxe/<br /> <br /> File Examples:<br /> <br /> http://www.watson.org/~robert/freebsd/pxe/<br /> <br /> PXE Information<br /> http://www.computerworld.com/action/article.do?command=viewArticleBasic&amp;articleId=108551<br /> <br /> [[Category:FreeBSD_for_Workstations]]</div>

Map7 http://www.freebsdwiki.net/index.php/X_Windows_Terminal 2006-10-15T11:03:17Z

<p>Map7: </p> <hr /> <div>==Advantages==<br /> X Windows can be used in a Server-Client relationship. By setting up your X Windows Server you allow the use of all the programs on that computer to all the client PC's. <br /> <br /> There are many advantages of running client computers in this manner:<br /> * They don't even need a hard drive. <br /> * It's silent as there are no moving parts<br /> * The solution saves power as your computers are very thin.<br /> * Everything can be backed up centrally.<br /> * Boot times for client PC's are the fastest around.<br /> * Clients don't need much CPU speed, memory, etc. Because of this they would be very cheap. You could get away with using a Pentium 100Mhz with 32MB ram, no hard drive, no CD-ROM, no Floppy and a fanless power supply. You just need a ethernet card with a PXEBOOT ROM. (XDM mode)<br /> * Central management of applications, users, config<br /> <br /> ==From the Beginning==<br /> I've based this document on FreeBSD 6.1.<br /> <br /> Install FreeBSD 6.1 as per usual.<br /> I've setup my mount points as this:<br /> '''Part Mount Size'''<br /> ad0s1b Swap (equal to how much memory I have in my machine)<br /> ad0s1a / 512MB<br /> ad0s1d /var 1G<br /> ad0s1e /tmp 512MB<br /> ad0s1f /usr 2GB min.<br /> /diskless_ro 512MB<br /> /diskless_rw 1GB min.<br /> <br /> I selected 'A' for auto and then deleted /usr and created /usr as 2g.<br /> <br /> Select User-X install. Yes to Ports if you have the room.<br /> <br /> Select SSH Server and NFS Server in the installation process, for the rest of the options go with the default.<br /> <br /> <br /> NOTE: If you forget to add any of the labels above, you will have to reboot as you cannot add labels to your boot drive when you have booted off it. So boot of the installation CD and use the configure -&gt; label option in the sysinstall screen to add these labels to your boot drive. You may need to retype the mount points for /, /var, /tmp and /usr by hitting 'm' on each label. Once you have created these labels in the 'Disklabel Editor' then you can hit 'w' to write them to the disk. answer 'yes' to the next question, hit 'ok' to the warning message. Now quit and reboot. Add them to fstab (/dev/ad0s1g /diskless_ro) &amp; (/dev/ad0s1h /diskless_rw) and mount.<br /> <br /> I find the best way to get this working is to break it down in to small steps and get each step working independantly. IE: Setup NFS and see if you can mount it from another FreeBSD machine, don't just assume it will work and boot your PXE-Boot machine.<br /> <br /> <br /> Throughout my documentation<br /> <br /> 192.168.1.1 = the Server<br /> <br /> 192.168.1.2 = the client (may be a full freebsd system or pxeboot)<br /> <br /> <br /> At this point I normally install fluxbox with the following line:<br /> <br /> shell# pkg_add -r fluxbox-devel<br /> <br /> <br /> change your ~/.xinitrc file to the following:<br /> <br /> startfluxbox<br /> <br /> <br /> Use the following command to update your fluxbox menus:<br /> <br /> shell$ fluxbox-generate_menu<br /> <br /> ==Running a single application==<br /> <br /> To get started I have my server setup running FreeBSD, with X-Windows and a few applications. Nothing too special. Then I have my client PC, which to start off I used the frenzy 1.0 boot CD to perform these initial tests. You can get this from [http://frenzy.org.ua/eng/ frenzy website]. I entered into fluxbox, but you could equally use any X session.<br /> You must allow incoming connections this is done with two commands<br /> <br /> client$ startx -listen_tcp<br /> client$ xhost +<br /> <br /> This allows all computers to start applications on your client PC. It's dangerous but good for testing everything is setup correctly.<br /> <br /> client$ ssh &lt;server user@server ip&gt;<br /> eg: ssh mick@192.168.1.1<br /> <br /> ssh$ export DISPLAY='192.168.1.2:0'<br /> <br /> Or if your running bash:<br /> ssh$ DISPLAY=&lt;client ip&gt;:&lt;client display&gt;; export DISPLAY<br /> eg: DISPLAY=192.168.1.2:0; export DISPLAY<br /> <br /> <br /> ssh$ xcalc &amp;<br /> <br /> This should display on your client<br /> <br /> ==Running a whole X Windows Session (XDM)==<br /> This sets up a server so that you can share your X session with any clients which want to connect. (Simular to Terminal Services under windows)<br /> <br /> <br /> ===server===<br /> edit:<br /> /usr/X11R6/lib/X11/xdm/xdm-config<br /> <br /> comment out with a '!' the request line&lt;br&gt;<br /> DisplayManager.requestPort: 0<br /> <br /> edit:&lt;br&gt;<br /> /usr/X11R6/lib/X11/xdm/Xaccess<br /> <br /> Enter a single asterisk any where in the file, so the contents should be one asterisk and the rest commented out. There should be an asterisk on line 49 which you can uncomment.<br /> <br /> Whilst in the /usr/X11R6/lib/X11/xdm directory do these commands:<br /> shell# vi Xstartup<br /> <br /> Add into this file:<br /> &lt;pre&gt;<br /> #!/bin/sh<br /> #<br /> # Xstartup<br /> #<br /> # This program is run as root after the user is verified<br /> #<br /> if [ -f /etc/nologin ]; then<br /> xmessage -file /etc/nologin -timeout 30 -center<br /> exit 1<br /> fi<br /> sessreg -a -l $DISPLAY -x /usr/X11R6/lib/xdm/Xservers $LOGNAME<br /> /usr/X11R6/lib/xdm/GiveConsole<br /> exit 0<br /> &lt;/pre&gt;<br /> <br /> <br /> shell# chmod +x Xstartup<br /> <br /> <br /> Make sure your firewall has all traffic for you lan. (Need to know which exact ports to allow).<br /> <br /> <br /> &lt;b&gt;Make sure you &lt;/b&gt;create ~/.xsession for each user which requires access and enter your start up for x <br /> eg:<br /> <br /> startfluxbox<br /> <br /> &lt;b&gt;run xdm on server as root&lt;/b&gt;<br /> <br /> shell# xdm<br /> <br /> <br /> You can put this xdm into the /etc/ttys so that it starts automatically on boot up.<br /> <br /> ===client===<br /> make sure your not in X<br /> <br /> type this command:<br /> <br /> shell# X -broadcast<br /> <br /> This assumes that you are running only one server.<br /> Otherwise use:<br /> <br /> shell# X -query 192.168.1.1<br /> <br /> ==DHCP - Install and setup==<br /> Server setup.<br /> <br /> install through package<br /> # pkg_add -r isc-dhcp3-server<br /> <br /> We do this so we can define the root path for the diskless system.<br /> <br /> copy /usr/local/etc/dhcpd.conf.sample to /usr/local/etc/dhcpd.conf<br /> <br /> edit /usr/local/etc/dhcpd.conf and make sure it has these lines in it.<br /> &lt;pre&gt;<br /> # dhcpd.conf<br /> #<br /> # Sample configuration file for ISC dhcpd<br /> #<br /> <br /> # option definitions common to all supported networks...<br /> #option domain-name &quot;example.org&quot;;<br /> #option domain-name-servers ns1.example.org, ns2.example.org;<br /> <br /> default-lease-time 3600;<br /> max-lease-time 86400;<br /> <br /> # If this DHCP server is the official DHCP server for the local<br /> # network, the authoritative directive should be uncommented.<br /> authoritative;<br /> <br /> # ad-hoc DNS update scheme - set to &quot;none&quot; to disable dynamic DNS updates.<br /> ddns-update-style none;<br /> <br /> option root-path &quot;192.168.1.1:/diskless_ro&quot;;<br /> <br /> # lines added for pxeboot client<br /> use-host-decl-names on;<br /> next-server 192.168.1.1;<br /> filename &quot;pxeboot&quot;;<br /> <br /> # Use this to send dhcp log messages to a different log file (you also<br /> # have to hack syslog.conf to complete the redirection).<br /> log-facility local7;<br /> <br /> # No service will be given on this subnet, but declaring it helps the<br /> # DHCP server to understand the network topology.<br /> <br /> <br /> # This is a very basic subnet declaration.<br /> <br /> subnet 192.168.1.0 netmask 255.255.255.0 {<br /> range 192.168.1.10 192.168.1.20;<br /> }<br /> &lt;/pre&gt;<br /> <br /> Create the leases file<br /> &lt;pre&gt;<br /> # touch /var/db/dhcpd.leases<br /> &lt;/pre&gt;<br /> <br /> <br /> Restart the daemon<br /> &lt;pre&gt;<br /> # killall dhcpd<br /> # dhcpd<br /> &lt;/pre&gt;<br /> <br /> <br /> Add to /etc/rc.conf<br /> &lt;pre&gt;<br /> dhcpd_enable=&quot;YES&quot;<br /> &lt;/pre&gt;<br /> <br /> ===Using a seperate DHCP server===<br /> If you already have a DHCP server and you want to use that instead then you have to do these steps.<br /> <br /> <br /> ====On your DHCP Server====<br /> 1. edit /usr/local/etc/dhcpd.conf and add the following<br /> &lt;pre&gt;<br /> authoritative;<br /> ddns-update-style none;<br /> <br /> option root-path &quot;&lt;X Server IP&gt;:/diskless_ro&quot;;<br /> <br /> # lines added for pxeboot client<br /> use-host-decl-names on;<br /> next-server &lt;X Server IP&gt;;<br /> filename &quot;pxeboot&quot;;<br /> &lt;/pre&gt;<br /> 2. stop dhcpd<br /> 3. start dhcpd<br /> <br /> <br /> ====Client====<br /> Your client should boot now just remember that you may get a different IP now that you are talking to a different DHCP server so you have to change your exports file and copy accross a directory in /diskless_rw for the new IP. All this is done on the X Server.<br /> <br /> ==TFTP Setup==<br /> TFTP helps us transport the kernel to the PXE-Boot machines.<br /> <br /> &lt;pre&gt;<br /> # mkdir /tftpboot<br /> # cp /boot/pxeboot /tftpboot<br /> &lt;/pre&gt;<br /> <br /> Uncomment the following line in /etc/inetd.conf<br /> <br /> &lt;pre&gt;<br /> tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /tftpboot<br /> &lt;/pre&gt;<br /> <br /> Restart the inetd service<br /> &lt;pre&gt;<br /> # killall -HUP inetd<br /> &lt;/pre&gt;<br /> <br /> If inetd has not started automatically do the following:<br /> <br /> Add the following to /etc/rc.conf<br /> &lt;pre&gt;<br /> inetd_enable=&quot;YES&quot;<br /> &lt;/pre&gt;<br /> <br /> Now start inetd manually.<br /> &lt;pre&gt;<br /> # inetd<br /> &lt;/pre&gt;<br /> <br /> ===Test===<br /> To test that tftp has loaded type the following:<br /> &lt;pre&gt;<br /> # sockstat -4l | grep 69 <br /> &lt;/pre&gt;<br /> <br /> and you should see this:<br /> &lt;pre&gt;<br /> root inetd 13719 5 udp4 *:69 *:*<br /> &lt;/pre&gt;<br /> <br /> ==NFS Setup==<br /> Network File System. Here we share all the directories from the server so that the diskless clients see these drives as if those directories were the diskless client's.<br /> <br /> ===Server Setup===<br /> If you forgot to select 'Yes' to NFS server setup in the FreeBSD installation then you have to setup the server manually like so:<br /> <br /> Enable NFS /etc/rc.conf<br /> &lt;pre&gt;<br /> rpcbind_enable=&quot;YES&quot;<br /> nfs_server_enable=&quot;YES&quot;<br /> &lt;/pre&gt;<br /> <br /> ===Test===<br /> A quick test to see if your NFS server is acting normal:<br /> <br /> Edit the /etc/exports and add the following<br /> &lt;pre&gt;<br /> /usr -alldirs<br /> &lt;/pre&gt;<br /> <br /> This allows anyone to connect to your /usr mount.<br /> <br /> Now run these commands to restart and view your mounts<br /> &lt;pre&gt;<br /> # kill -HUP `cat /var/run/mountd.pid`<br /> # showmount -e<br /> &lt;/pre&gt;<br /> <br /> Now try and mount it from a client running BSD<br /> &lt;pre&gt;<br /> # mount -t nfs 192.168.1.1:/usr /mnt<br /> &lt;/pre&gt;<br /> <br /> <br /> ===Server exports setup===<br /> <br /> Make directories for each IP for your clients<br /> &lt;pre&gt;<br /> # cd /diskless_rw<br /> # mkdir 192.168.1.2<br /> # cd 192.168.1.2<br /> # mkdir etc var<br /> &lt;/pre&gt;<br /> <br /> Configure /etc/exports<br /> &lt;pre&gt;<br /> # file systems accessible only for reading:<br /> # Original way of linking up the /usr<br /> #/usr -ro -maproot=0 -network 192.168.1.0 -mask 255.255.255.0<br /> <br /> /usr -network 192.168.1.0 -mask 255.255.255.0<br /> /diskless_ro -ro -maproot=0 -network 192.168.1.0 -mask 255.255.255.0<br /> /diskless_rw/192.168.1.2/etc /diskless_rw/192.168.1.2/var -maproot=root 192.168.1.2<br /> <br /> &lt;/pre&gt;<br /> <br /> Restarting NFS<br /> &lt;pre&gt;<br /> # kill -HUP `cat /var/run/mountd.pid`<br /> &lt;/pre&gt;<br /> <br /> <br /> If NFS is not started yet do the following:<br /> &lt;pre&gt;<br /> data# rpcbind<br /> data# nfsd -u -t -n 20 -h 192.168.1.1<br /> data# mountd -r<br /> &lt;/pre&gt;<br /> <br /> Testing to see if the exports are correct<br /> &lt;pre&gt;<br /> data# showmount -e<br /> Exports list on localhost:<br /> /usr 192.168.1.0<br /> /diskless_rw/192.168.1.2/var 192.168.1.2<br /> /diskless_rw/192.168.1.2/etc 192.168.1.2<br /> /diskless_ro 192.168.1.0<br /> &lt;/pre&gt;<br /> <br /> ==Setup diskless_rw==<br /> Create directories<br /> <br /> &lt;pre&gt;<br /> # cd /diskless_rw/192.168.1.2/etc<br /> # mkdir pam.d X11<br /> <br /> # cd /diskless_rw/192.168.1.2/var<br /> # mkdir home log run tmp<br /> # chmod 1777 tmp<br /> &lt;/pre&gt;<br /> <br /> Create a swap file in the var directory for the client<br /> &lt;pre&gt;<br /> # dd if=/dev/zero of=/diskless_rw/192.168.1.2/var/swap bs=1k count=32000<br /> &lt;/pre&gt;<br /> <br /> in the /diskless_rw/&lt;ip&gt;/var/log directory I created the following log files so that syslogd would have files to write to:<br /> &lt;pre&gt;<br /> # cd /diskless_rw/192.168.1.2/var/log<br /> # touch messages security auth.log maillog lpd-errs xferlog cron debug.log slip.log ppp.log<br /> &lt;/pre&gt;<br /> <br /> <br /> Copy the following files from the systems /etc directory to /diskless_rw/&lt;client ip&gt;/etc<br /> # cp -Rv &lt;files&gt; /diskless_rw/&lt;ip&gt;/etc<br /> <br /> &lt;pre&gt;<br /> auth.conf<br /> disktab<br /> gettytab<br /> group<br /> hosts<br /> login.access<br /> login.conf<br /> login.conf.db<br /> master.passwd<br /> netconfig<br /> protocols<br /> pam.d<br /> pwd.db<br /> services<br /> spwd.db<br /> syslog.conf<br /> termcap -&gt; /usr/share/misc/termcap<br /> ttys<br /> &lt;/pre&gt;<br /> <br /> It's very important that you copy all the files in pam.d across otherwise you will not have a password prompt on your login.<br /> <br /> Create a fstab in /diskless_rw/&lt;ip&gt;/etc<br /> # touch /diskless_rw/&lt;ip&gt;/etc/fstab<br /> <br /> ==Setup diskless_ro==<br /> This is the common root mount for all pxe-boot clients.<br /> <br /> Copy accross important directories and kernel from boot to diskless_ro<br /> &lt;pre&gt;<br /> # cp -rv /bin /lib /libexec /sbin /boot /diskless_ro<br /> # mkdir /diskless_ro/usr<br /> &lt;/pre&gt;<br /> <br /> For some client machines you may have to disable the ACPI (Power management) in the /diskless_ro/boot/device.hints<br /> &lt;pre&gt;<br /> hint.acpi.0.disabled=&quot;1&quot; <br /> &lt;/pre&gt;<br /> <br /> Make a dev so that clients can boot without freezing.<br /> &lt;pre&gt;<br /> # mkdir /diskless_ro/dev<br /> &lt;/pre&gt;<br /> <br /> Make a directory so that we can mount var from the /diskless_rw/&lt;client ip&gt;/var<br /> &lt;pre&gt;<br /> # mkdir /diskless_ro/var<br /> &lt;/pre&gt; <br /> <br /> So we can use the systems /var/tmp and /usr/home directory make soft links to them<br /> &lt;pre&gt;<br /> # cd /diskless_ro<br /> # ln -s /var/tmp<br /> # ln -s /usr/home<br /> &lt;/pre&gt;<br /> <br /> We require a few files from the systems /etc directory to be copied into the /diskless_ro/etc for common use between the thin clients.<br /> &lt;pre&gt;<br /> # mkdir /diskless_ro/etc<br /> # cd /etc<br /> # cp /services /netconfig /login.conf /diskless_ro/etc<br /> &lt;/pre&gt;<br /> <br /> <br /> ===rc file===<br /> The /diskless_ro/etc/rc file is the first file which is ran after the kernel has loaded. Here we mount a the labels from the server.<br /> <br /> Create the /diskless_ro/etc/rc<br /> &lt;pre&gt;<br /> #!/bin/sh<br /> <br /> PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin; export PATH<br /> TMPDIR=~/tmp;export TMPDIR<br /> TMP=~/tmp;export TMP<br /> <br /> mount -t nfs 192.168.1.1:/usr /usr<br /> <br /> boot_ip=`/sbin/ifconfig | /usr/bin/grep &quot;inet &quot; | /usr/bin/grep -v 127.0.0.1 |<br /> /usr/bin/awk '{print $2}'`<br /> mount_nfs -L 192.168.1.1:/diskless_rw/${boot_ip}/etc /etc<br /> mount_nfs -L 192.168.1.1:/diskless_rw/${boot_ip}/var /var<br /> <br /> swapon /var/swap<br /> <br /> #rm -rf /var/tmp/*<br /> #rm -rf /var/tmp/.*<br /> <br /> # Option if you choose XDM terminals<br /> #X -query 192.168.1.1<br /> <br /> . /etc/rc2<br /> exit 0<br /> <br /> &lt;/pre&gt;<br /> <br /> &lt;b&gt;Remember to change 192.168.1.1 to your X server's IP&lt;/b&gt;<br /> <br /> The -L on the mount_nfs is there so we don't get flock errors.<br /> <br /> ===rc2 file===<br /> This sets up some links for libraries and the logging daemon.<br /> <br /> &lt;pre&gt;<br /> #!/bin/sh<br /> <br /> mount -a<br /> /sbin/ldconfig -elf /usr/lib/compat /usr/X11R6/lib /usr/local/lib<br /> <br /> syslogd<br /> &lt;/pre&gt;<br /> <br /> <br /> Now change permissions so rc can run.<br /> # chmod +x rc*<br /> <br /> Copy /diskless_ro/etc/rc and rc2 to /diskless_rw/&lt;client ip&gt;/etc<br /> # cp /diskless_ro/etc/rc* /diskless_rw/192.168.1.2/etc<br /> <br /> ==GRUB Floppy boot (optional)==<br /> <br /> (would like to compile this ourselves later)<br /> To get started we downloaded the image from www.hp.uab.edu/~ed/grub-net<br /> <br /> shell# dd if=/data/grub-net.img of=/dev/fd0<br /> <br /> Then we mounted it as msdos<br /> Remove/rename menu.1st from the grub directory as it was doing something funny with it. We think that it was looking for a tftp server through our dhcp and we don't have a the dhcp setup correctly here, so we wanted to do it manually.<br /> <br /> Reboot off the floppy now..<br /> <br /> grub&gt; ifconfig --address=192.168.1.2 --mask=255.255.255.0 --gateway=192.168.1.1<br /> --server=192.168.1.2<br /> <br /> OR you can use dhcp&lt;br&gt;<br /> <br /> grub&gt; dhcp&lt;br&gt; <br /> grub&gt; tftpserver 192.168.1.2&lt;br&gt;<br /> <br /> <br /> Setup tftp on your server, we created a directory /tftpboot. <br /> <br /> <br /> ===Starting diskless system through GRUB===<br /> This is an alternative boot loader. You can use this for testing, if you don't have a pxeboot chip, otherwise skip this section.<br /> <br /> These commands are half working...&lt;br&gt;<br /> <br /> grub&gt; root (nd)&lt;br&gt;<br /> grub&gt; kernel /kernel root=ad0s1a&lt;br&gt;<br /> grub&gt; pxeboot&lt;br&gt;<br /> <br /> ==Completely Diskless System (PXEBOOT ROM) (optional)==<br /> <br /> Running completely diskless by booting from a Network ROM Chip.<br /> <br /> We have now got a Intel GD82559 Etherexpress pro/100 Card.<br /> <br /> When we boot up on the client machine with that card it displays:&lt;br /&gt;<br /> &lt;br /&gt;<br /> Intel UNDI, PXE-2.0 (build 067)&lt;br /&gt;<br /> Copyright (C) 1997-1998 Intel Corporation&lt;br /&gt;<br /> &lt;br /&gt;<br /> Which we cannot get working so we have read that you have to update this version to Build 82.&lt;br /&gt;<br /> &lt;br /&gt;<br /> &lt;br /&gt;<br /> copy /boot/pxeboot to /tftpboot directory we made before&lt;br /&gt;<br /> &lt;br /&gt;<br /> - Downloaded proboot.exe from support.intel.com and unpacked into a windows box.&lt;br /&gt;<br /> - Copied ibautil.exe onto a windows 98 boot disk.&lt;br /&gt;<br /> - Rebooted the test box after disabling network boot on the nic (otherwise it'll kick in before the floppy).&lt;br /&gt;<br /> - Ran ibautil -iv to see what embedded image versions were available:&lt;br /&gt;<br /> &lt;br /&gt;<br /> Intel(R) Boot Agent XG v1.0.09&lt;br /&gt;<br /> Intel(R) Boot Agent GE v1.2.36&lt;br /&gt;<br /> Intel(R) Boot Agent FE v4.1.19&lt;br /&gt;<br /> &lt;br /&gt;<br /> - Ran ibautil -up to perform the image upgrade.&lt;br /&gt;<br /> &lt;br /&gt;<br /> It's interesting to note that no version showed up for out intel nic when initially running ibautil. After the upgrade, however, the version corectly showed as 4.1.19.&lt;br /&gt;&lt;br /&gt;<br /> <br /> I made sure that I had simular features to this in my dhcpd.conf file:&lt;br /&gt;<br /> option broadcast-address 192.168.254.255;&lt;br /&gt;<br /> option domain-name-servers 192.168.254.3;&lt;br /&gt;<br /> option domain-name &quot;simerson.net&quot;;&lt;br /&gt;<br /> option routers 192.168.254.1;&lt;br /&gt;<br /> option subnet-mask 255.255.255.0;&lt;br /&gt;<br /> server-name &quot;pxe-gw&quot;;&lt;br /&gt;<br /> server-identifier 192.168.254.3;&lt;br /&gt;<br /> next-server 192.168.254.3;&lt;br /&gt;<br /> default-lease-time -1;&lt;br /&gt;<br /> &lt;br /&gt;<br /> subnet 192.168.254.0 netmask 255.255.255.0 {&lt;br /&gt;<br /> range 192.168.254.32 192.168.254.99;&lt;br /&gt;<br /> option root-path &quot;/usr/local/export/pxe&quot;;&lt;br /&gt;<br /> filename &quot;pxeboot&quot;;&lt;br /&gt;<br /> }&lt;br /&gt;<br /> host cm.simerson.net {&lt;br /&gt;<br /> hardware ethernet 00:e0:18:98:f0:cc;&lt;br /&gt;<br /> fixed-address 192.168.254.126;&lt;br /&gt;<br /> }&lt;br /&gt;<br /> host c1.simerson.net {&lt;br /&gt;<br /> hardware ethernet 00:60:97:0e:bb:a7;&lt;br /&gt;<br /> fixed-address 192.168.254.131;&lt;br /&gt;<br /> }&lt;br /&gt;<br /> &lt;br /&gt;<br /> <br /> ==X config notes==<br /> On the X server the /etc/X11/xorg.conf file is only used for the X server not the clients.<br /> <br /> To use this same configuration for your X Terminal Clients copy this file to /diskless_rw/&lt;Client IP&gt;/etc/X11 and it will use it.<br /> <br /> ==Starting X on the client==<br /> There are two ways of doing this and it depends on your hardware mainly. <br /> <br /> 1. run all programs on the server using the servers CPU and Memory this we will call the 'XDM Method'<br /> 2. run all programs from the NFS mounts using the clients CPU and Memory but the HD of the server, this we will call the 'NFS Method'<br /> <br /> Both methods will boot from PXE-Boot and can be diskless.<br /> <br /> ===XDM Method===<br /> Recommended for machines less than 1Ghz 256MB<br /> <br /> This is quite simple to setup. Change your rc file in the /diskless_ro/etc directory to have this line at the end:<br /> &lt;pre&gt;<br /> X -query &lt;server ip&gt;<br /> &lt;/pre&gt;<br /> <br /> Make sure on the server you setup xdm to start on system startup<br /> # vi /etc/ttys<br /> <br /> Search for this line:<br /> ttyv8 &quot;/usr/X11R6/bin/xdm -nodaemon&quot; xterm off secure<br /> <br /> and change it to:<br /> ttyv8 &quot;/usr/X11R6/bin/xdm -nodaemon&quot; xterm on secure<br /> <br /> <br /> You can also type this command at the command line on the client to test before hand.<br /> <br /> ===NFS Method===<br /> Recommended for machines over 1Ghz 256MB or if you want to utilise any of the clients devices such as local HD, USB, CD/DVD burners, etc.<br /> <br /> This is much trickier.<br /> <br /> Log in<br /> Now type 'startx' at the command line.<br /> <br /> ==Custom Kernels==<br /> If you want to create custom kernels for your clients then do this:<br /> <br /> Create your custom kernel<br /> # cd /sys/i386/conf<br /> # cp GENERIC DISKLESS<br /> # vi DISKLESS<br /> <br /> Make changes and build and install<br /> <br /> # cd /usr/src<br /> # make buildkernel KERNCONF=DISKLESS<br /> # make installkernel KERNCONF=DISKLESS DESTDIR=/diskless_ro<br /> <br /> ==todo==<br /> Here are some of the jobs left to do to make this secure or generally better:<br /> <br /> - If you don't configure your clients to run xdm it will put you at the text login. The problem here is people can login as root without a password for some reason. If the user hits &lt;Ctrl&gt;&lt;Alt&gt;&lt;Back space&gt; then it will crash them out to a login screen which the user could then login as root with out a password, not good!<br /> <br /> - Optimise the boot up sequence<br /> <br /> - There must be a simplier way to set this up if your going to use XDM in the end. IE: do we need to do half of this tutorial if we are going to run XDM.<br /> <br /> - When the same user logs onto two seperate machines they cannot start firefox or thunderbird as it complains about being open somewhere else. This assumes you have firefox and thunderbird already open on both machines that you logged onto.<br /> <br /> ===Known Issues===<br /> <br /> - Doesn't work with HP-COMPAQ-T5525 thin client as it doesn't want to boot, it says it's missing libfreetype.so.9 which we do have it just cannot find it for some reason. It's trying to use the VIA chipset for graphics which is different to all the other clients I've loaded successfully so far.<br /> <br /> - USB mice not working instead use PS/2. If we got this working it may help get the HP T5525 working<br /> <br /> ===Keyboard repeating on notebooks===<br /> - typing on some keyboards (like my notebook) causes double characters to display if you type too fast. - This is the notebook, if you go and set the KDE Accessabiltiy options and set the keyboard rate to 50ms, this fixes the problem.<br /> <br /> ===USB mouse===<br /> <br /> Editing /etc/devd.conf file and searched for ums<br /> remarked out the action line.<br /> <br /> rebooted.<br /> <br /> Someone off IRC suggested that I build a GENERIC xorg.conf file which has vesa, usb mouse and ps/2 mouse configurations through it.<br /> <br /> I reverted everything back to normal ps/2 mouse config, copying my usb config files to the following:<br /> /etc/devd.conf_usb<br /> /etc/rc.conf_usb<br /> /etc/X11/xorg.conf_usb<br /> <br /> I think we need a seperate configuration for the HP, it uses a weird display driver.<br /> <br /> ==links==<br /> <br /> http://www.onlamp.com/pub/a/bsd/2004/09/09/diskless_server.html<br /> <br /> http://www.onlamp.com/pub/a/bsd/2004/09/30/diskless_clients.html<br /> <br /> http://people.freebsd.org/~alfred/pxe/en_US.ISO8859-1/articles/pxe/article.html<br /> <br /> http://www.the-labs.com/FreeBSD/Diskless/<br /> <br /> http://www.nber.org/sys-admin/FreeBSD-diskless.html<br /> <br /> <br /> <br /> http://wikitest.freebsd.org/MarkusBoelter<br /> <br /> http://www.daemonsecurity.com/pub/pxeboot/<br /> <br /> http://www.kano.org.uk/projects/pxe/<br /> <br /> File Examples:<br /> <br /> http://www.watson.org/~robert/freebsd/pxe/<br /> <br /> PXE Information<br /> http://www.computerworld.com/action/article.do?command=viewArticleBasic&amp;articleId=108551<br /> <br /> [[Category:FreeBSD_for_Workstations]]</div>

Map7 http://www.freebsdwiki.net/index.php/X_Windows_Terminal 2006-10-15T09:01:06Z

<p>Map7: /* Setup diskless_rw */</p> <hr /> <div>==Advantages==<br /> X Windows can be used in a Server-Client relationship. By setting up your X Windows Server you allow the use of all the programs on that computer to all the client PC's. <br /> <br /> There are many advantages of running client computers in this manner:<br /> * They don't even need a hard drive. <br /> * It's silent as there are no moving parts<br /> * The solution saves power as your computers are very thin.<br /> * Everything can be backed up centrally.<br /> * Boot times for client PC's are the fastest around.<br /> * Clients don't need much CPU speed, memory, etc. Because of this they would be very cheap. You could get away with using a Pentium 100Mhz with 32MB ram, no hard drive, no CD-ROM, no Floppy and a fanless power supply. You just need a ethernet card with a PXEBOOT ROM. (XDM mode)<br /> * Central management of applications, users, config<br /> <br /> ==From the Beginning==<br /> I've based this document on FreeBSD 6.1.<br /> <br /> Install FreeBSD 6.1 as per usual.<br /> I've setup my mount points as this:<br /> '''Part Mount Size'''<br /> ad0s1b Swap (equal to how much memory I have in my machine)<br /> ad0s1a / 512MB<br /> ad0s1d /var 1G<br /> ad0s1e /tmp 512MB<br /> ad0s1f /usr 2GB min.<br /> /diskless_ro 512MB<br /> /diskless_rw 1GB min.<br /> <br /> I selected 'A' for auto and then deleted /usr and created /usr as 2g.<br /> <br /> Select User-X install. Yes to Ports if you have the room.<br /> <br /> Select SSH Server and NFS Server in the installation process, for the rest of the options go with the default.<br /> <br /> <br /> NOTE: If you forget to add any of the labels above, you will have to reboot as you cannot add labels to your boot drive when you have booted off it. So boot of the installation CD and use the configure -&gt; label option in the sysinstall screen to add these labels to your boot drive. You may need to retype the mount points for /, /var, /tmp and /usr by hitting 'm' on each label. Once you have created these labels in the 'Disklabel Editor' then you can hit 'w' to write them to the disk. answer 'yes' to the next question, hit 'ok' to the warning message. Now quit and reboot. Add them to fstab (/dev/ad0s1g /diskless_ro) &amp; (/dev/ad0s1h /diskless_rw) and mount.<br /> <br /> I find the best way to get this working is to break it down in to small steps and get each step working independantly. IE: Setup NFS and see if you can mount it from another FreeBSD machine, don't just assume it will work and boot your PXE-Boot machine.<br /> <br /> <br /> Throughout my documentation<br /> <br /> 192.168.1.1 = the Server<br /> <br /> 192.168.1.2 = the client (may be a full freebsd system or pxeboot)<br /> <br /> <br /> At this point I normally install fluxbox with the following line:<br /> <br /> shell# pkg_add -r fluxbox-devel<br /> <br /> <br /> change your ~/.xinitrc file to the following:<br /> <br /> startfluxbox<br /> <br /> <br /> Use the following command to update your fluxbox menus:<br /> <br /> shell$ fluxbox-generate_menu<br /> <br /> ==Running a single application==<br /> <br /> To get started I have my server setup running FreeBSD, with X-Windows and a few applications. Nothing too special. Then I have my client PC, which to start off I used the frenzy 1.0 boot CD to perform these initial tests. You can get this from [http://frenzy.org.ua/eng/ frenzy website]. I entered into fluxbox, but you could equally use any X session.<br /> You must allow incoming connections this is done with two commands<br /> <br /> client$ startx -listen_tcp<br /> client$ xhost +<br /> <br /> This allows all computers to start applications on your client PC. It's dangerous but good for testing everything is setup correctly.<br /> <br /> client$ ssh &lt;server user@server ip&gt;<br /> eg: ssh mick@192.168.1.1<br /> <br /> ssh$ export DISPLAY='192.168.1.2:0'<br /> <br /> Or if your running bash:<br /> ssh$ DISPLAY=&lt;client ip&gt;:&lt;client display&gt;; export DISPLAY<br /> eg: DISPLAY=192.168.1.2:0; export DISPLAY<br /> <br /> <br /> ssh$ xcalc &amp;<br /> <br /> This should display on your client<br /> <br /> ==Running a whole X Windows Session (XDM)==<br /> This sets up a server so that you can share your X session with any clients which want to connect. (Simular to Terminal Services under windows)<br /> <br /> <br /> ===server===<br /> edit:<br /> /usr/X11R6/lib/X11/xdm/xdm-config<br /> <br /> comment out with a '!' the request line&lt;br&gt;<br /> DisplayManager.requestPort: 0<br /> <br /> edit:&lt;br&gt;<br /> /usr/X11R6/lib/X11/xdm/Xaccess<br /> <br /> Enter a single asterisk any where in the file, so the contents should be one asterisk and the rest commented out. There should be an asterisk on line 49 which you can uncomment.<br /> <br /> Whilst in the /usr/X11R6/lib/X11/xdm directory do these commands:<br /> shell# vi Xstartup<br /> <br /> Add into this file:<br /> &lt;pre&gt;<br /> #!/bin/sh<br /> #<br /> # Xstartup<br /> #<br /> # This program is run as root after the user is verified<br /> #<br /> if [ -f /etc/nologin ]; then<br /> xmessage -file /etc/nologin -timeout 30 -center<br /> exit 1<br /> fi<br /> sessreg -a -l $DISPLAY -x /usr/X11R6/lib/xdm/Xservers $LOGNAME<br /> /usr/X11R6/lib/xdm/GiveConsole<br /> exit 0<br /> &lt;/pre&gt;<br /> <br /> <br /> shell# chmod +x Xstartup<br /> <br /> <br /> Make sure your firewall has all traffic for you lan. (Need to know which exact ports to allow).<br /> <br /> <br /> &lt;b&gt;Make sure you &lt;/b&gt;create ~/.xsession for each user which requires access and enter your start up for x <br /> eg:<br /> <br /> startfluxbox<br /> <br /> &lt;b&gt;run xdm on server as root&lt;/b&gt;<br /> <br /> shell# xdm<br /> <br /> <br /> You can put this xdm into the /etc/ttys so that it starts automatically on boot up.<br /> <br /> ===client===<br /> make sure your not in X<br /> <br /> type this command:<br /> <br /> shell# X -broadcast<br /> <br /> This assumes that you are running only one server.<br /> Otherwise use:<br /> <br /> shell# X -query 192.168.1.1<br /> <br /> ==DHCP - Install and setup==<br /> Server setup.<br /> <br /> install through package<br /> # pkg_add -r isc-dhcp3-server<br /> <br /> We do this so we can define the root path for the diskless system.<br /> <br /> copy /usr/local/etc/dhcpd.conf.sample to /usr/local/etc/dhcpd.conf<br /> <br /> edit /usr/local/etc/dhcpd.conf and make sure it has these lines in it.<br /> &lt;pre&gt;<br /> # dhcpd.conf<br /> #<br /> # Sample configuration file for ISC dhcpd<br /> #<br /> <br /> # option definitions common to all supported networks...<br /> #option domain-name &quot;example.org&quot;;<br /> #option domain-name-servers ns1.example.org, ns2.example.org;<br /> <br /> default-lease-time 3600;<br /> max-lease-time 86400;<br /> <br /> # If this DHCP server is the official DHCP server for the local<br /> # network, the authoritative directive should be uncommented.<br /> authoritative;<br /> <br /> # ad-hoc DNS update scheme - set to &quot;none&quot; to disable dynamic DNS updates.<br /> ddns-update-style none;<br /> <br /> option root-path &quot;192.168.1.1:/diskless_ro&quot;;<br /> <br /> # lines added for pxeboot client<br /> use-host-decl-names on;<br /> next-server 192.168.1.1;<br /> filename &quot;pxeboot&quot;;<br /> <br /> # Use this to send dhcp log messages to a different log file (you also<br /> # have to hack syslog.conf to complete the redirection).<br /> log-facility local7;<br /> <br /> # No service will be given on this subnet, but declaring it helps the<br /> # DHCP server to understand the network topology.<br /> <br /> <br /> # This is a very basic subnet declaration.<br /> <br /> subnet 192.168.1.0 netmask 255.255.255.0 {<br /> range 192.168.1.10 192.168.1.20;<br /> }<br /> &lt;/pre&gt;<br /> <br /> Create the leases file<br /> &lt;pre&gt;<br /> # touch /var/db/dhcpd.leases<br /> &lt;/pre&gt;<br /> <br /> <br /> Restart the daemon<br /> &lt;pre&gt;<br /> # killall dhcpd<br /> # dhcpd<br /> &lt;/pre&gt;<br /> <br /> <br /> Add to /etc/rc.conf<br /> &lt;pre&gt;<br /> dhcpd_enable=&quot;YES&quot;<br /> &lt;/pre&gt;<br /> <br /> ===Using a seperate DHCP server===<br /> If you already have a DHCP server and you want to use that instead then you have to do these steps.<br /> <br /> <br /> ====On your DHCP Server====<br /> 1. edit /usr/local/etc/dhcpd.conf and add the following<br /> &lt;pre&gt;<br /> authoritative;<br /> ddns-update-style none;<br /> <br /> option root-path &quot;&lt;X Server IP&gt;:/diskless_ro&quot;;<br /> <br /> # lines added for pxeboot client<br /> use-host-decl-names on;<br /> next-server &lt;X Server IP&gt;;<br /> filename &quot;pxeboot&quot;;<br /> &lt;/pre&gt;<br /> 2. stop dhcpd<br /> 3. start dhcpd<br /> <br /> <br /> ====Client====<br /> Your client should boot now just remember that you may get a different IP now that you are talking to a different DHCP server so you have to change your exports file and copy accross a directory in /diskless_rw for the new IP. All this is done on the X Server.<br /> <br /> ==TFTP Setup==<br /> TFTP helps us transport the kernel to the PXE-Boot machines.<br /> <br /> &lt;pre&gt;<br /> # mkdir /tftpboot<br /> # cp /boot/pxeboot /tftpboot<br /> &lt;/pre&gt;<br /> <br /> Uncomment the following line in /etc/inetd.conf<br /> <br /> &lt;pre&gt;<br /> tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /tftpboot<br /> &lt;/pre&gt;<br /> <br /> Restart the inetd service<br /> &lt;pre&gt;<br /> # killall -HUP inetd<br /> &lt;/pre&gt;<br /> <br /> If inetd has not started automatically do the following:<br /> <br /> Add the following to /etc/rc.conf<br /> &lt;pre&gt;<br /> inetd_enable=&quot;YES&quot;<br /> &lt;/pre&gt;<br /> <br /> Now start inetd manually.<br /> &lt;pre&gt;<br /> # inetd<br /> &lt;/pre&gt;<br /> <br /> ===Test===<br /> To test that tftp has loaded type the following:<br /> &lt;pre&gt;<br /> # sockstat -4l | grep 69 <br /> &lt;/pre&gt;<br /> <br /> and you should see this:<br /> &lt;pre&gt;<br /> root inetd 13719 5 udp4 *:69 *:*<br /> &lt;/pre&gt;<br /> <br /> ==NFS Setup==<br /> Network File System. Here we share all the directories from the server so that the diskless clients see these drives as if those directories were the diskless client's.<br /> <br /> ===Server Setup===<br /> If you forgot to select 'Yes' to NFS server setup in the FreeBSD installation then you have to setup the server manually like so:<br /> <br /> Enable NFS /etc/rc.conf<br /> &lt;pre&gt;<br /> rpcbind_enable=&quot;YES&quot;<br /> nfs_server_enable=&quot;YES&quot;<br /> &lt;/pre&gt;<br /> <br /> ===Test===<br /> A quick test to see if your NFS server is acting normal:<br /> <br /> Edit the /etc/exports and add the following<br /> &lt;pre&gt;<br /> /usr -alldirs<br /> &lt;/pre&gt;<br /> <br /> This allows anyone to connect to your /usr mount.<br /> <br /> Now run these commands to restart and view your mounts<br /> &lt;pre&gt;<br /> # kill -HUP `cat /var/run/mountd.pid`<br /> # showmount -e<br /> &lt;/pre&gt;<br /> <br /> Now try and mount it from a client running BSD<br /> &lt;pre&gt;<br /> # mount -t nfs 192.168.1.1:/usr /mnt<br /> &lt;/pre&gt;<br /> <br /> <br /> ===Server exports setup===<br /> <br /> Make directories for each IP for your clients<br /> &lt;pre&gt;<br /> # cd /diskless_rw<br /> # mkdir 192.168.1.2<br /> # cd 192.168.1.2<br /> # mkdir etc var<br /> &lt;/pre&gt;<br /> <br /> Configure /etc/exports<br /> &lt;pre&gt;<br /> # file systems accessible only for reading:<br /> # Original way of linking up the /usr<br /> #/usr -ro -maproot=0 -network 192.168.1.0 -mask 255.255.255.0<br /> <br /> /usr -network 192.168.1.0 -mask 255.255.255.0<br /> /diskless_ro -ro -maproot=0 -network 192.168.1.0 -mask 255.255.255.0<br /> /diskless_rw/192.168.1.2/etc /diskless_rw/192.168.1.2/var -maproot=root 192.168.1.2<br /> <br /> &lt;/pre&gt;<br /> <br /> Restarting NFS<br /> &lt;pre&gt;<br /> # kill -HUP `cat /var/run/mountd.pid`<br /> &lt;/pre&gt;<br /> <br /> <br /> If NFS is not started yet do the following:<br /> &lt;pre&gt;<br /> data# rpcbind<br /> data# nfsd -u -t -n 20 -h 192.168.1.1<br /> data# mountd -r<br /> &lt;/pre&gt;<br /> <br /> Testing to see if the exports are correct<br /> &lt;pre&gt;<br /> data# showmount -e<br /> Exports list on localhost:<br /> /usr 192.168.1.0<br /> /diskless_rw/192.168.1.2/var 192.168.1.2<br /> /diskless_rw/192.168.1.2/etc 192.168.1.2<br /> /diskless_ro 192.168.1.0<br /> &lt;/pre&gt;<br /> <br /> ==Setup diskless_rw==<br /> Create directories<br /> <br /> &lt;pre&gt;<br /> # cd /diskless_rw/192.168.1.2/etc<br /> # mkdir pam.d X11<br /> <br /> # cd /diskless_rw/192.168.1.2/var<br /> # mkdir home log run tmp<br /> # chmod 1777 tmp<br /> &lt;/pre&gt;<br /> <br /> Create a swap file in the var directory for the client<br /> &lt;pre&gt;<br /> # dd if=/dev/zero of=/diskless_rw/192.168.1.2/var/swap bs=1k count=32000<br /> &lt;/pre&gt;<br /> <br /> in the /diskless_rw/&lt;ip&gt;/var/log directory I created the following log files so that syslogd would have files to write to:<br /> &lt;pre&gt;<br /> # cd /diskless_rw/192.168.1.2/var/log<br /> # touch messages security auth.log maillog lpd-errs xferlog cron debug.log slip.log ppp.log<br /> &lt;/pre&gt;<br /> <br /> <br /> Copy the following files from the systems /etc directory to /diskless_rw/&lt;client ip&gt;/etc<br /> # cp -Rv &lt;files&gt; /diskless_rw/&lt;ip&gt;/etc<br /> <br /> &lt;pre&gt;<br /> auth.conf<br /> disktab<br /> gettytab<br /> group<br /> hosts<br /> login.access<br /> login.conf<br /> login.conf.db<br /> master.passwd<br /> netconfig<br /> protocols<br /> pam.d<br /> pwd.db<br /> services<br /> spwd.db<br /> syslog.conf<br /> termcap -&gt; /usr/share/misc/termcap<br /> ttys<br /> &lt;/pre&gt;<br /> <br /> It's very important that you copy all the files in pam.d across otherwise you will not have a password prompt on your login.<br /> <br /> Create a fstab in /diskless_rw/&lt;ip&gt;/etc<br /> # touch /diskless_rw/&lt;ip&gt;/etc/fstab<br /> <br /> ==Setup diskless_ro==<br /> This is the common root mount for all pxe-boot clients.<br /> <br /> Copy accross important directories and kernel from boot to diskless_ro<br /> &lt;pre&gt;<br /> # cp -rv /bin /lib /libexec /sbin /boot /diskless_ro<br /> # mkdir /diskless_ro/usr<br /> &lt;/pre&gt;<br /> <br /> For some client machines you may have to disable the ACPI (Power management) in the /diskless_ro/boot/device.hints<br /> &lt;pre&gt;<br /> hint.acpi.0.disabled=&quot;1&quot; <br /> &lt;/pre&gt;<br /> <br /> Make a dev so that clients can boot without freezing.<br /> &lt;pre&gt;<br /> # mkdir /diskless_ro/dev<br /> &lt;/pre&gt;<br /> <br /> Make a directory so that we can mount var from the /diskless_rw/&lt;client ip&gt;/var<br /> &lt;pre&gt;<br /> # mkdir /diskless_ro/var<br /> &lt;/pre&gt; <br /> <br /> So we can use the systems /var/tmp and /usr/home directory make soft links to them<br /> &lt;pre&gt;<br /> # cd /diskless_ro<br /> # ln -s /var/tmp<br /> # ln -s /usr/home<br /> &lt;/pre&gt;<br /> <br /> We require a few files from the systems /etc directory to be copied into the /diskless_ro/etc for common use between the thin clients.<br /> &lt;pre&gt;<br /> # mkdir /diskless_ro/etc<br /> # cd /etc<br /> # cp /services /netconfig /login.conf /diskless_ro/etc<br /> &lt;/pre&gt;<br /> <br /> <br /> ===rc file===<br /> The /diskless_ro/etc/rc file is the first file which is ran after the kernel has loaded. Here we mount a the labels from the server.<br /> <br /> Create the /diskless_ro/etc/rc<br /> &lt;pre&gt;<br /> #!/bin/sh<br /> <br /> PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin; export PATH<br /> TMPDIR=~/tmp;export TMPDIR<br /> TMP=~/tmp;export TMP<br /> <br /> mount -t nfs 192.168.1.1:/usr /usr<br /> <br /> boot_ip=`/sbin/ifconfig | /usr/bin/grep &quot;inet &quot; | /usr/bin/grep -v 127.0.0.1 |<br /> /usr/bin/awk '{print $2}'`<br /> mount_nfs -L 192.168.1.1:/diskless_rw/${boot_ip}/etc /etc<br /> mount_nfs -L 192.168.1.1:/diskless_rw/${boot_ip}/var /var<br /> <br /> swapon /var/swap<br /> <br /> #rm -rf /var/tmp/*<br /> #rm -rf /var/tmp/.*<br /> <br /> # Option if you choose XDM terminals<br /> #X -query 192.168.1.1<br /> <br /> . /etc/rc2<br /> exit 0<br /> <br /> &lt;/pre&gt;<br /> <br /> &lt;b&gt;Remember to change 192.168.1.1 to your X server's IP&lt;/b&gt;<br /> <br /> The -L on the mount_nfs is there so we don't get flock errors.<br /> <br /> ===rc2 file===<br /> This sets up some links for libraries and the logging daemon.<br /> <br /> &lt;pre&gt;<br /> #!/bin/sh<br /> <br /> mount -a<br /> /sbin/ldconfig -elf /usr/lib/compat /usr/X11R6/lib /usr/local/lib<br /> <br /> syslogd<br /> &lt;/pre&gt;<br /> <br /> <br /> Now change permissions so rc can run.<br /> # chmod +x rc*<br /> <br /> Copy /diskless_ro/etc/rc and rc2 to /diskless_rw/&lt;client ip&gt;/etc<br /> # cp /diskless_ro/etc/rc* /diskless_rw/192.168.1.2/etc<br /> <br /> ==GRUB Floppy boot (optional)==<br /> <br /> (would like to compile this ourselves later)<br /> To get started we downloaded the image from www.hp.uab.edu/~ed/grub-net<br /> <br /> shell# dd if=/data/grub-net.img of=/dev/fd0<br /> <br /> Then we mounted it as msdos<br /> Remove/rename menu.1st from the grub directory as it was doing something funny with it. We think that it was looking for a tftp server through our dhcp and we don't have a the dhcp setup correctly here, so we wanted to do it manually.<br /> <br /> Reboot off the floppy now..<br /> <br /> grub&gt; ifconfig --address=192.168.1.2 --mask=255.255.255.0 --gateway=192.168.1.1<br /> --server=192.168.1.2<br /> <br /> OR you can use dhcp&lt;br&gt;<br /> <br /> grub&gt; dhcp&lt;br&gt; <br /> grub&gt; tftpserver 192.168.1.2&lt;br&gt;<br /> <br /> <br /> Setup tftp on your server, we created a directory /tftpboot. <br /> <br /> <br /> ===Starting diskless system through GRUB===<br /> This is an alternative boot loader. You can use this for testing, if you don't have a pxeboot chip, otherwise skip this section.<br /> <br /> These commands are half working...&lt;br&gt;<br /> <br /> grub&gt; root (nd)&lt;br&gt;<br /> grub&gt; kernel /kernel root=ad0s1a&lt;br&gt;<br /> grub&gt; pxeboot&lt;br&gt;<br /> <br /> ==Completely Diskless System (PXEBOOT ROM) (optional)==<br /> <br /> Running completely diskless by booting from a Network ROM Chip.<br /> <br /> We have now got a Intel GD82559 Etherexpress pro/100 Card.<br /> <br /> When we boot up on the client machine with that card it displays:&lt;br /&gt;<br /> &lt;br /&gt;<br /> Intel UNDI, PXE-2.0 (build 067)&lt;br /&gt;<br /> Copyright (C) 1997-1998 Intel Corporation&lt;br /&gt;<br /> &lt;br /&gt;<br /> Which we cannot get working so we have read that you have to update this version to Build 82.&lt;br /&gt;<br /> &lt;br /&gt;<br /> &lt;br /&gt;<br /> copy /boot/pxeboot to /tftpboot directory we made before&lt;br /&gt;<br /> &lt;br /&gt;<br /> - Downloaded proboot.exe from support.intel.com and unpacked into a windows box.&lt;br /&gt;<br /> - Copied ibautil.exe onto a windows 98 boot disk.&lt;br /&gt;<br /> - Rebooted the test box after disabling network boot on the nic (otherwise it'll kick in before the floppy).&lt;br /&gt;<br /> - Ran ibautil -iv to see what embedded image versions were available:&lt;br /&gt;<br /> &lt;br /&gt;<br /> Intel(R) Boot Agent XG v1.0.09&lt;br /&gt;<br /> Intel(R) Boot Agent GE v1.2.36&lt;br /&gt;<br /> Intel(R) Boot Agent FE v4.1.19&lt;br /&gt;<br /> &lt;br /&gt;<br /> - Ran ibautil -up to perform the image upgrade.&lt;br /&gt;<br /> &lt;br /&gt;<br /> It's interesting to note that no version showed up for out intel nic when initially running ibautil. After the upgrade, however, the version corectly showed as 4.1.19.&lt;br /&gt;&lt;br /&gt;<br /> <br /> I made sure that I had simular features to this in my dhcpd.conf file:&lt;br /&gt;<br /> option broadcast-address 192.168.254.255;&lt;br /&gt;<br /> option domain-name-servers 192.168.254.3;&lt;br /&gt;<br /> option domain-name &quot;simerson.net&quot;;&lt;br /&gt;<br /> option routers 192.168.254.1;&lt;br /&gt;<br /> option subnet-mask 255.255.255.0;&lt;br /&gt;<br /> server-name &quot;pxe-gw&quot;;&lt;br /&gt;<br /> server-identifier 192.168.254.3;&lt;br /&gt;<br /> next-server 192.168.254.3;&lt;br /&gt;<br /> default-lease-time -1;&lt;br /&gt;<br /> &lt;br /&gt;<br /> subnet 192.168.254.0 netmask 255.255.255.0 {&lt;br /&gt;<br /> range 192.168.254.32 192.168.254.99;&lt;br /&gt;<br /> option root-path &quot;/usr/local/export/pxe&quot;;&lt;br /&gt;<br /> filename &quot;pxeboot&quot;;&lt;br /&gt;<br /> }&lt;br /&gt;<br /> host cm.simerson.net {&lt;br /&gt;<br /> hardware ethernet 00:e0:18:98:f0:cc;&lt;br /&gt;<br /> fixed-address 192.168.254.126;&lt;br /&gt;<br /> }&lt;br /&gt;<br /> host c1.simerson.net {&lt;br /&gt;<br /> hardware ethernet 00:60:97:0e:bb:a7;&lt;br /&gt;<br /> fixed-address 192.168.254.131;&lt;br /&gt;<br /> }&lt;br /&gt;<br /> &lt;br /&gt;<br /> <br /> ==X config notes==<br /> On the X server the /etc/X11/xorg.conf file is only used for the X server not the clients.<br /> <br /> To use this same configuration for your X Terminal Clients copy this file to /diskless_rw/&lt;Client IP&gt;/etc/X11 and it will use it.<br /> <br /> ==Starting X on the client==<br /> There are two ways of doing this and it depends on your hardware mainly. <br /> <br /> 1. run all programs on the server using the servers CPU and Memory this we will call the 'XDM Method'<br /> 2. run all programs from the NFS mounts using the clients CPU and Memory but the HD of the server, this we will call the 'NFS Method'<br /> <br /> Both methods will boot from PXE-Boot and can be diskless.<br /> <br /> ===XDM Method===<br /> Recommended for machines less than 1Ghz 256MB<br /> <br /> This is quite simple to setup. Change your rc file in the /diskless_ro/etc directory to have this line at the end:<br /> &lt;pre&gt;<br /> X -query &lt;server ip&gt;<br /> &lt;/pre&gt;<br /> <br /> Make sure on the server you setup xdm to start on system startup<br /> # vi /etc/ttys<br /> <br /> Search for this line:<br /> ttyv8 &quot;/usr/X11R6/bin/xdm -nodaemon&quot; xterm off secure<br /> <br /> and change it to:<br /> ttyv8 &quot;/usr/X11R6/bin/xdm -nodaemon&quot; xterm on secure<br /> <br /> <br /> You can also type this command at the command line on the client to test before hand.<br /> <br /> ===NFS Method===<br /> Recommended for machines over 1Ghz 256MB or if you want to utilise any of the clients devices such as local HD, USB, CD/DVD burners, etc.<br /> <br /> This is much trickier.<br /> <br /> Log in<br /> Now type 'startx' at the command line.<br /> <br /> <br /> <br /> ==todo==<br /> Here are some of the jobs left to do to make this secure or generally better:<br /> <br /> - If you don't configure your clients to run xdm it will put you at the text login. The problem here is people can login as root without a password for some reason. If the user hits &lt;Ctrl&gt;&lt;Alt&gt;&lt;Back space&gt; then it will crash them out to a login screen which the user could then login as root with out a password, not good!<br /> <br /> - Optimise the boot up sequence<br /> <br /> - There must be a simplier way to set this up if your going to use XDM in the end. IE: do we need to do half of this tutorial if we are going to run XDM.<br /> <br /> - When the same user logs onto two seperate machines they cannot start firefox or thunderbird as it complains about being open somewhere else. This assumes you have firefox and thunderbird already open on both machines that you logged onto.<br /> <br /> ===Known Issues===<br /> <br /> - Doesn't work with HP-COMPAQ-T5525 thin client as it doesn't want to boot, it says it's missing libfreetype.so.9 which we do have it just cannot find it for some reason. It's trying to use the VIA chipset for graphics which is different to all the other clients I've loaded successfully so far.<br /> <br /> - USB mice not working instead use PS/2. If we got this working it may help get the HP T5525 working<br /> <br /> ===Keyboard repeating on notebooks===<br /> - typing on some keyboards (like my notebook) causes double characters to display if you type too fast. - This is the notebook, if you go and set the KDE Accessabiltiy options and set the keyboard rate to 50ms, this fixes the problem.<br /> <br /> ===USB mouse===<br /> <br /> Editing /etc/devd.conf file and searched for ums<br /> remarked out the action line.<br /> <br /> rebooted.<br /> <br /> Someone off IRC suggested that I build a GENERIC xorg.conf file which has vesa, usb mouse and ps/2 mouse configurations through it.<br /> <br /> I reverted everything back to normal ps/2 mouse config, copying my usb config files to the following:<br /> /etc/devd.conf_usb<br /> /etc/rc.conf_usb<br /> /etc/X11/xorg.conf_usb<br /> <br /> I think we need a seperate configuration for the HP, it uses a weird display driver.<br /> <br /> ==links==<br /> <br /> http://www.onlamp.com/pub/a/bsd/2004/09/09/diskless_server.html<br /> <br /> http://www.onlamp.com/pub/a/bsd/2004/09/30/diskless_clients.html<br /> <br /> http://people.freebsd.org/~alfred/pxe/en_US.ISO8859-1/articles/pxe/article.html<br /> <br /> http://www.the-labs.com/FreeBSD/Diskless/<br /> <br /> http://www.nber.org/sys-admin/FreeBSD-diskless.html<br /> <br /> <br /> <br /> http://wikitest.freebsd.org/MarkusBoelter<br /> <br /> http://www.daemonsecurity.com/pub/pxeboot/<br /> <br /> http://www.kano.org.uk/projects/pxe/<br /> <br /> File Examples:<br /> <br /> http://www.watson.org/~robert/freebsd/pxe/<br /> <br /> PXE Information<br /> http://www.computerworld.com/action/article.do?command=viewArticleBasic&amp;articleId=108551<br /> <br /> [[Category:FreeBSD_for_Workstations]]</div>

Map7 http://www.freebsdwiki.net/index.php/X_Windows_Terminal 2006-10-15T08:37:32Z

<p>Map7: /* Setup diskless_ro */</p> <hr /> <div>==Advantages==<br /> X Windows can be used in a Server-Client relationship. By setting up your X Windows Server you allow the use of all the programs on that computer to all the client PC's. <br /> <br /> There are many advantages of running client computers in this manner:<br /> * They don't even need a hard drive. <br /> * It's silent as there are no moving parts<br /> * The solution saves power as your computers are very thin.<br /> * Everything can be backed up centrally.<br /> * Boot times for client PC's are the fastest around.<br /> * Clients don't need much CPU speed, memory, etc. Because of this they would be very cheap. You could get away with using a Pentium 100Mhz with 32MB ram, no hard drive, no CD-ROM, no Floppy and a fanless power supply. You just need a ethernet card with a PXEBOOT ROM. (XDM mode)<br /> * Central management of applications, users, config<br /> <br /> ==From the Beginning==<br /> I've based this document on FreeBSD 6.1.<br /> <br /> Install FreeBSD 6.1 as per usual.<br /> I've setup my mount points as this:<br /> '''Part Mount Size'''<br /> ad0s1b Swap (equal to how much memory I have in my machine)<br /> ad0s1a / 512MB<br /> ad0s1d /var 1G<br /> ad0s1e /tmp 512MB<br /> ad0s1f /usr 2GB min.<br /> /diskless_ro 512MB<br /> /diskless_rw 1GB min.<br /> <br /> I selected 'A' for auto and then deleted /usr and created /usr as 2g.<br /> <br /> Select User-X install. Yes to Ports if you have the room.<br /> <br /> Select SSH Server and NFS Server in the installation process, for the rest of the options go with the default.<br /> <br /> <br /> NOTE: If you forget to add any of the labels above, you will have to reboot as you cannot add labels to your boot drive when you have booted off it. So boot of the installation CD and use the configure -&gt; label option in the sysinstall screen to add these labels to your boot drive. You may need to retype the mount points for /, /var, /tmp and /usr by hitting 'm' on each label. Once you have created these labels in the 'Disklabel Editor' then you can hit 'w' to write them to the disk. answer 'yes' to the next question, hit 'ok' to the warning message. Now quit and reboot. Add them to fstab (/dev/ad0s1g /diskless_ro) &amp; (/dev/ad0s1h /diskless_rw) and mount.<br /> <br /> I find the best way to get this working is to break it down in to small steps and get each step working independantly. IE: Setup NFS and see if you can mount it from another FreeBSD machine, don't just assume it will work and boot your PXE-Boot machine.<br /> <br /> <br /> Throughout my documentation<br /> <br /> 192.168.1.1 = the Server<br /> <br /> 192.168.1.2 = the client (may be a full freebsd system or pxeboot)<br /> <br /> <br /> At this point I normally install fluxbox with the following line:<br /> <br /> shell# pkg_add -r fluxbox-devel<br /> <br /> <br /> change your ~/.xinitrc file to the following:<br /> <br /> startfluxbox<br /> <br /> <br /> Use the following command to update your fluxbox menus:<br /> <br /> shell$ fluxbox-generate_menu<br /> <br /> ==Running a single application==<br /> <br /> To get started I have my server setup running FreeBSD, with X-Windows and a few applications. Nothing too special. Then I have my client PC, which to start off I used the frenzy 1.0 boot CD to perform these initial tests. You can get this from [http://frenzy.org.ua/eng/ frenzy website]. I entered into fluxbox, but you could equally use any X session.<br /> You must allow incoming connections this is done with two commands<br /> <br /> client$ startx -listen_tcp<br /> client$ xhost +<br /> <br /> This allows all computers to start applications on your client PC. It's dangerous but good for testing everything is setup correctly.<br /> <br /> client$ ssh &lt;server user@server ip&gt;<br /> eg: ssh mick@192.168.1.1<br /> <br /> ssh$ export DISPLAY='192.168.1.2:0'<br /> <br /> Or if your running bash:<br /> ssh$ DISPLAY=&lt;client ip&gt;:&lt;client display&gt;; export DISPLAY<br /> eg: DISPLAY=192.168.1.2:0; export DISPLAY<br /> <br /> <br /> ssh$ xcalc &amp;<br /> <br /> This should display on your client<br /> <br /> ==Running a whole X Windows Session (XDM)==<br /> This sets up a server so that you can share your X session with any clients which want to connect. (Simular to Terminal Services under windows)<br /> <br /> <br /> ===server===<br /> edit:<br /> /usr/X11R6/lib/X11/xdm/xdm-config<br /> <br /> comment out with a '!' the request line&lt;br&gt;<br /> DisplayManager.requestPort: 0<br /> <br /> edit:&lt;br&gt;<br /> /usr/X11R6/lib/X11/xdm/Xaccess<br /> <br /> Enter a single asterisk any where in the file, so the contents should be one asterisk and the rest commented out. There should be an asterisk on line 49 which you can uncomment.<br /> <br /> Whilst in the /usr/X11R6/lib/X11/xdm directory do these commands:<br /> shell# vi Xstartup<br /> <br /> Add into this file:<br /> &lt;pre&gt;<br /> #!/bin/sh<br /> #<br /> # Xstartup<br /> #<br /> # This program is run as root after the user is verified<br /> #<br /> if [ -f /etc/nologin ]; then<br /> xmessage -file /etc/nologin -timeout 30 -center<br /> exit 1<br /> fi<br /> sessreg -a -l $DISPLAY -x /usr/X11R6/lib/xdm/Xservers $LOGNAME<br /> /usr/X11R6/lib/xdm/GiveConsole<br /> exit 0<br /> &lt;/pre&gt;<br /> <br /> <br /> shell# chmod +x Xstartup<br /> <br /> <br /> Make sure your firewall has all traffic for you lan. (Need to know which exact ports to allow).<br /> <br /> <br /> &lt;b&gt;Make sure you &lt;/b&gt;create ~/.xsession for each user which requires access and enter your start up for x <br /> eg:<br /> <br /> startfluxbox<br /> <br /> &lt;b&gt;run xdm on server as root&lt;/b&gt;<br /> <br /> shell# xdm<br /> <br /> <br /> You can put this xdm into the /etc/ttys so that it starts automatically on boot up.<br /> <br /> ===client===<br /> make sure your not in X<br /> <br /> type this command:<br /> <br /> shell# X -broadcast<br /> <br /> This assumes that you are running only one server.<br /> Otherwise use:<br /> <br /> shell# X -query 192.168.1.1<br /> <br /> ==DHCP - Install and setup==<br /> Server setup.<br /> <br /> install through package<br /> # pkg_add -r isc-dhcp3-server<br /> <br /> We do this so we can define the root path for the diskless system.<br /> <br /> copy /usr/local/etc/dhcpd.conf.sample to /usr/local/etc/dhcpd.conf<br /> <br /> edit /usr/local/etc/dhcpd.conf and make sure it has these lines in it.<br /> &lt;pre&gt;<br /> # dhcpd.conf<br /> #<br /> # Sample configuration file for ISC dhcpd<br /> #<br /> <br /> # option definitions common to all supported networks...<br /> #option domain-name &quot;example.org&quot;;<br /> #option domain-name-servers ns1.example.org, ns2.example.org;<br /> <br /> default-lease-time 3600;<br /> max-lease-time 86400;<br /> <br /> # If this DHCP server is the official DHCP server for the local<br /> # network, the authoritative directive should be uncommented.<br /> authoritative;<br /> <br /> # ad-hoc DNS update scheme - set to &quot;none&quot; to disable dynamic DNS updates.<br /> ddns-update-style none;<br /> <br /> option root-path &quot;192.168.1.1:/diskless_ro&quot;;<br /> <br /> # lines added for pxeboot client<br /> use-host-decl-names on;<br /> next-server 192.168.1.1;<br /> filename &quot;pxeboot&quot;;<br /> <br /> # Use this to send dhcp log messages to a different log file (you also<br /> # have to hack syslog.conf to complete the redirection).<br /> log-facility local7;<br /> <br /> # No service will be given on this subnet, but declaring it helps the<br /> # DHCP server to understand the network topology.<br /> <br /> <br /> # This is a very basic subnet declaration.<br /> <br /> subnet 192.168.1.0 netmask 255.255.255.0 {<br /> range 192.168.1.10 192.168.1.20;<br /> }<br /> &lt;/pre&gt;<br /> <br /> Create the leases file<br /> &lt;pre&gt;<br /> # touch /var/db/dhcpd.leases<br /> &lt;/pre&gt;<br /> <br /> <br /> Restart the daemon<br /> &lt;pre&gt;<br /> # killall dhcpd<br /> # dhcpd<br /> &lt;/pre&gt;<br /> <br /> <br /> Add to /etc/rc.conf<br /> &lt;pre&gt;<br /> dhcpd_enable=&quot;YES&quot;<br /> &lt;/pre&gt;<br /> <br /> ===Using a seperate DHCP server===<br /> If you already have a DHCP server and you want to use that instead then you have to do these steps.<br /> <br /> <br /> ====On your DHCP Server====<br /> 1. edit /usr/local/etc/dhcpd.conf and add the following<br /> &lt;pre&gt;<br /> authoritative;<br /> ddns-update-style none;<br /> <br /> option root-path &quot;&lt;X Server IP&gt;:/diskless_ro&quot;;<br /> <br /> # lines added for pxeboot client<br /> use-host-decl-names on;<br /> next-server &lt;X Server IP&gt;;<br /> filename &quot;pxeboot&quot;;<br /> &lt;/pre&gt;<br /> 2. stop dhcpd<br /> 3. start dhcpd<br /> <br /> <br /> ====Client====<br /> Your client should boot now just remember that you may get a different IP now that you are talking to a different DHCP server so you have to change your exports file and copy accross a directory in /diskless_rw for the new IP. All this is done on the X Server.<br /> <br /> ==TFTP Setup==<br /> TFTP helps us transport the kernel to the PXE-Boot machines.<br /> <br /> &lt;pre&gt;<br /> # mkdir /tftpboot<br /> # cp /boot/pxeboot /tftpboot<br /> &lt;/pre&gt;<br /> <br /> Uncomment the following line in /etc/inetd.conf<br /> <br /> &lt;pre&gt;<br /> tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /tftpboot<br /> &lt;/pre&gt;<br /> <br /> Restart the inetd service<br /> &lt;pre&gt;<br /> # killall -HUP inetd<br /> &lt;/pre&gt;<br /> <br /> If inetd has not started automatically do the following:<br /> <br /> Add the following to /etc/rc.conf<br /> &lt;pre&gt;<br /> inetd_enable=&quot;YES&quot;<br /> &lt;/pre&gt;<br /> <br /> Now start inetd manually.<br /> &lt;pre&gt;<br /> # inetd<br /> &lt;/pre&gt;<br /> <br /> ===Test===<br /> To test that tftp has loaded type the following:<br /> &lt;pre&gt;<br /> # sockstat -4l | grep 69 <br /> &lt;/pre&gt;<br /> <br /> and you should see this:<br /> &lt;pre&gt;<br /> root inetd 13719 5 udp4 *:69 *:*<br /> &lt;/pre&gt;<br /> <br /> ==NFS Setup==<br /> Network File System. Here we share all the directories from the server so that the diskless clients see these drives as if those directories were the diskless client's.<br /> <br /> ===Server Setup===<br /> If you forgot to select 'Yes' to NFS server setup in the FreeBSD installation then you have to setup the server manually like so:<br /> <br /> Enable NFS /etc/rc.conf<br /> &lt;pre&gt;<br /> rpcbind_enable=&quot;YES&quot;<br /> nfs_server_enable=&quot;YES&quot;<br /> &lt;/pre&gt;<br /> <br /> ===Test===<br /> A quick test to see if your NFS server is acting normal:<br /> <br /> Edit the /etc/exports and add the following<br /> &lt;pre&gt;<br /> /usr -alldirs<br /> &lt;/pre&gt;<br /> <br /> This allows anyone to connect to your /usr mount.<br /> <br /> Now run these commands to restart and view your mounts<br /> &lt;pre&gt;<br /> # kill -HUP `cat /var/run/mountd.pid`<br /> # showmount -e<br /> &lt;/pre&gt;<br /> <br /> Now try and mount it from a client running BSD<br /> &lt;pre&gt;<br /> # mount -t nfs 192.168.1.1:/usr /mnt<br /> &lt;/pre&gt;<br /> <br /> <br /> ===Server exports setup===<br /> <br /> Make directories for each IP for your clients<br /> &lt;pre&gt;<br /> # cd /diskless_rw<br /> # mkdir 192.168.1.2<br /> # cd 192.168.1.2<br /> # mkdir etc var<br /> &lt;/pre&gt;<br /> <br /> Configure /etc/exports<br /> &lt;pre&gt;<br /> # file systems accessible only for reading:<br /> # Original way of linking up the /usr<br /> #/usr -ro -maproot=0 -network 192.168.1.0 -mask 255.255.255.0<br /> <br /> /usr -network 192.168.1.0 -mask 255.255.255.0<br /> /diskless_ro -ro -maproot=0 -network 192.168.1.0 -mask 255.255.255.0<br /> /diskless_rw/192.168.1.2/etc /diskless_rw/192.168.1.2/var -maproot=root 192.168.1.2<br /> <br /> &lt;/pre&gt;<br /> <br /> Restarting NFS<br /> &lt;pre&gt;<br /> # kill -HUP `cat /var/run/mountd.pid`<br /> &lt;/pre&gt;<br /> <br /> <br /> If NFS is not started yet do the following:<br /> &lt;pre&gt;<br /> data# rpcbind<br /> data# nfsd -u -t -n 20 -h 192.168.1.1<br /> data# mountd -r<br /> &lt;/pre&gt;<br /> <br /> Testing to see if the exports are correct<br /> &lt;pre&gt;<br /> data# showmount -e<br /> Exports list on localhost:<br /> /usr 192.168.1.0<br /> /diskless_rw/192.168.1.2/var 192.168.1.2<br /> /diskless_rw/192.168.1.2/etc 192.168.1.2<br /> /diskless_ro 192.168.1.0<br /> &lt;/pre&gt;<br /> <br /> ==Setup diskless_rw==<br /> Create directories<br /> <br /> &lt;pre&gt;<br /> # cd /diskless_rw/192.168.1.2/etc<br /> # mkdir pam.d X11<br /> <br /> # cd /diskless_rw/192.168.1.2/var<br /> # mkdir home log run tmp<br /> # chmod 1777 tmp<br /> &lt;/pre&gt;<br /> <br /> Create a swap file in the var directory for the client<br /> &lt;pre&gt;<br /> # dd if=/dev/zero of=/diskless_rw/192.168.1.2/var/swap bs=1k count=32000<br /> &lt;/pre&gt;<br /> <br /> in the /diskless_rw/&lt;ip&gt;/var/log directory I created the following log files so that syslogd would have files to write to:<br /> &lt;pre&gt;<br /> # cd /diskless_rw/192.168.1.2/var/log<br /> # touch messages security auth.log maillog lpd-errs xferlog cron debug.log slip.log ppp.log<br /> &lt;/pre&gt;<br /> <br /> <br /> Copy the following files from the systems /etc directory to /diskless_rw/&lt;client ip&gt;/etc<br /> # cp -Rv &lt;files&gt; /diskless_rw/&lt;ip&gt;/etc<br /> <br /> &lt;pre&gt;<br /> auth.conf<br /> disktab<br /> gettytab<br /> group<br /> hosts<br /> login.access<br /> login.conf<br /> login.conf.db<br /> master.passwd<br /> netconfig<br /> protocols<br /> pam.d<br /> pwd.db<br /> services<br /> spwd.db<br /> syslog.conf<br /> termcap -&gt; /usr/share/misc/termcap<br /> ttys<br /> &lt;/pre&gt;<br /> <br /> It's very important that you copy all the files in pam.d across otherwise you will not have a password prompt on your login.<br /> <br /> ==Setup diskless_ro==<br /> This is the common root mount for all pxe-boot clients.<br /> <br /> Copy accross important directories and kernel from boot to diskless_ro<br /> &lt;pre&gt;<br /> # cp -rv /bin /lib /libexec /sbin /boot /diskless_ro<br /> # mkdir /diskless_ro/usr<br /> &lt;/pre&gt;<br /> <br /> For some client machines you may have to disable the ACPI (Power management) in the /diskless_ro/boot/device.hints<br /> &lt;pre&gt;<br /> hint.acpi.0.disabled=&quot;1&quot; <br /> &lt;/pre&gt;<br /> <br /> Make a dev so that clients can boot without freezing.<br /> &lt;pre&gt;<br /> # mkdir /diskless_ro/dev<br /> &lt;/pre&gt;<br /> <br /> Make a directory so that we can mount var from the /diskless_rw/&lt;client ip&gt;/var<br /> &lt;pre&gt;<br /> # mkdir /diskless_ro/var<br /> &lt;/pre&gt; <br /> <br /> So we can use the systems /var/tmp and /usr/home directory make soft links to them<br /> &lt;pre&gt;<br /> # cd /diskless_ro<br /> # ln -s /var/tmp<br /> # ln -s /usr/home<br /> &lt;/pre&gt;<br /> <br /> We require a few files from the systems /etc directory to be copied into the /diskless_ro/etc for common use between the thin clients.<br /> &lt;pre&gt;<br /> # mkdir /diskless_ro/etc<br /> # cd /etc<br /> # cp /services /netconfig /login.conf /diskless_ro/etc<br /> &lt;/pre&gt;<br /> <br /> <br /> ===rc file===<br /> The /diskless_ro/etc/rc file is the first file which is ran after the kernel has loaded. Here we mount a the labels from the server.<br /> <br /> Create the /diskless_ro/etc/rc<br /> &lt;pre&gt;<br /> #!/bin/sh<br /> <br /> PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin; export PATH<br /> TMPDIR=~/tmp;export TMPDIR<br /> TMP=~/tmp;export TMP<br /> <br /> mount -t nfs 192.168.1.1:/usr /usr<br /> <br /> boot_ip=`/sbin/ifconfig | /usr/bin/grep &quot;inet &quot; | /usr/bin/grep -v 127.0.0.1 |<br /> /usr/bin/awk '{print $2}'`<br /> mount_nfs -L 192.168.1.1:/diskless_rw/${boot_ip}/etc /etc<br /> mount_nfs -L 192.168.1.1:/diskless_rw/${boot_ip}/var /var<br /> <br /> swapon /var/swap<br /> <br /> #rm -rf /var/tmp/*<br /> #rm -rf /var/tmp/.*<br /> <br /> # Option if you choose XDM terminals<br /> #X -query 192.168.1.1<br /> <br /> . /etc/rc2<br /> exit 0<br /> <br /> &lt;/pre&gt;<br /> <br /> &lt;b&gt;Remember to change 192.168.1.1 to your X server's IP&lt;/b&gt;<br /> <br /> The -L on the mount_nfs is there so we don't get flock errors.<br /> <br /> ===rc2 file===<br /> This sets up some links for libraries and the logging daemon.<br /> <br /> &lt;pre&gt;<br /> #!/bin/sh<br /> <br /> mount -a<br /> /sbin/ldconfig -elf /usr/lib/compat /usr/X11R6/lib /usr/local/lib<br /> <br /> syslogd<br /> &lt;/pre&gt;<br /> <br /> <br /> Now change permissions so rc can run.<br /> # chmod +x rc*<br /> <br /> Copy /diskless_ro/etc/rc and rc2 to /diskless_rw/&lt;client ip&gt;/etc<br /> # cp /diskless_ro/etc/rc* /diskless_rw/192.168.1.2/etc<br /> <br /> ==GRUB Floppy boot (optional)==<br /> <br /> (would like to compile this ourselves later)<br /> To get started we downloaded the image from www.hp.uab.edu/~ed/grub-net<br /> <br /> shell# dd if=/data/grub-net.img of=/dev/fd0<br /> <br /> Then we mounted it as msdos<br /> Remove/rename menu.1st from the grub directory as it was doing something funny with it. We think that it was looking for a tftp server through our dhcp and we don't have a the dhcp setup correctly here, so we wanted to do it manually.<br /> <br /> Reboot off the floppy now..<br /> <br /> grub&gt; ifconfig --address=192.168.1.2 --mask=255.255.255.0 --gateway=192.168.1.1<br /> --server=192.168.1.2<br /> <br /> OR you can use dhcp&lt;br&gt;<br /> <br /> grub&gt; dhcp&lt;br&gt; <br /> grub&gt; tftpserver 192.168.1.2&lt;br&gt;<br /> <br /> <br /> Setup tftp on your server, we created a directory /tftpboot. <br /> <br /> <br /> ===Starting diskless system through GRUB===<br /> This is an alternative boot loader. You can use this for testing, if you don't have a pxeboot chip, otherwise skip this section.<br /> <br /> These commands are half working...&lt;br&gt;<br /> <br /> grub&gt; root (nd)&lt;br&gt;<br /> grub&gt; kernel /kernel root=ad0s1a&lt;br&gt;<br /> grub&gt; pxeboot&lt;br&gt;<br /> <br /> ==Completely Diskless System (PXEBOOT ROM) (optional)==<br /> <br /> Running completely diskless by booting from a Network ROM Chip.<br /> <br /> We have now got a Intel GD82559 Etherexpress pro/100 Card.<br /> <br /> When we boot up on the client machine with that card it displays:&lt;br /&gt;<br /> &lt;br /&gt;<br /> Intel UNDI, PXE-2.0 (build 067)&lt;br /&gt;<br /> Copyright (C) 1997-1998 Intel Corporation&lt;br /&gt;<br /> &lt;br /&gt;<br /> Which we cannot get working so we have read that you have to update this version to Build 82.&lt;br /&gt;<br /> &lt;br /&gt;<br /> &lt;br /&gt;<br /> copy /boot/pxeboot to /tftpboot directory we made before&lt;br /&gt;<br /> &lt;br /&gt;<br /> - Downloaded proboot.exe from support.intel.com and unpacked into a windows box.&lt;br /&gt;<br /> - Copied ibautil.exe onto a windows 98 boot disk.&lt;br /&gt;<br /> - Rebooted the test box after disabling network boot on the nic (otherwise it'll kick in before the floppy).&lt;br /&gt;<br /> - Ran ibautil -iv to see what embedded image versions were available:&lt;br /&gt;<br /> &lt;br /&gt;<br /> Intel(R) Boot Agent XG v1.0.09&lt;br /&gt;<br /> Intel(R) Boot Agent GE v1.2.36&lt;br /&gt;<br /> Intel(R) Boot Agent FE v4.1.19&lt;br /&gt;<br /> &lt;br /&gt;<br /> - Ran ibautil -up to perform the image upgrade.&lt;br /&gt;<br /> &lt;br /&gt;<br /> It's interesting to note that no version showed up for out intel nic when initially running ibautil. After the upgrade, however, the version corectly showed as 4.1.19.&lt;br /&gt;&lt;br /&gt;<br /> <br /> I made sure that I had simular features to this in my dhcpd.conf file:&lt;br /&gt;<br /> option broadcast-address 192.168.254.255;&lt;br /&gt;<br /> option domain-name-servers 192.168.254.3;&lt;br /&gt;<br /> option domain-name &quot;simerson.net&quot;;&lt;br /&gt;<br /> option routers 192.168.254.1;&lt;br /&gt;<br /> option subnet-mask 255.255.255.0;&lt;br /&gt;<br /> server-name &quot;pxe-gw&quot;;&lt;br /&gt;<br /> server-identifier 192.168.254.3;&lt;br /&gt;<br /> next-server 192.168.254.3;&lt;br /&gt;<br /> default-lease-time -1;&lt;br /&gt;<br /> &lt;br /&gt;<br /> subnet 192.168.254.0 netmask 255.255.255.0 {&lt;br /&gt;<br /> range 192.168.254.32 192.168.254.99;&lt;br /&gt;<br /> option root-path &quot;/usr/local/export/pxe&quot;;&lt;br /&gt;<br /> filename &quot;pxeboot&quot;;&lt;br /&gt;<br /> }&lt;br /&gt;<br /> host cm.simerson.net {&lt;br /&gt;<br /> hardware ethernet 00:e0:18:98:f0:cc;&lt;br /&gt;<br /> fixed-address 192.168.254.126;&lt;br /&gt;<br /> }&lt;br /&gt;<br /> host c1.simerson.net {&lt;br /&gt;<br /> hardware ethernet 00:60:97:0e:bb:a7;&lt;br /&gt;<br /> fixed-address 192.168.254.131;&lt;br /&gt;<br /> }&lt;br /&gt;<br /> &lt;br /&gt;<br /> <br /> ==X config notes==<br /> On the X server the /etc/X11/xorg.conf file is only used for the X server not the clients.<br /> <br /> To use this same configuration for your X Terminal Clients copy this file to /diskless_rw/&lt;Client IP&gt;/etc/X11 and it will use it.<br /> <br /> ==Starting X on the client==<br /> There are two ways of doing this and it depends on your hardware mainly. <br /> <br /> 1. run all programs on the server using the servers CPU and Memory this we will call the 'XDM Method'<br /> 2. run all programs from the NFS mounts using the clients CPU and Memory but the HD of the server, this we will call the 'NFS Method'<br /> <br /> Both methods will boot from PXE-Boot and can be diskless.<br /> <br /> ===XDM Method===<br /> Recommended for machines less than 1Ghz 256MB<br /> <br /> This is quite simple to setup. Change your rc file in the /diskless_ro/etc directory to have this line at the end:<br /> &lt;pre&gt;<br /> X -query &lt;server ip&gt;<br /> &lt;/pre&gt;<br /> <br /> Make sure on the server you setup xdm to start on system startup<br /> # vi /etc/ttys<br /> <br /> Search for this line:<br /> ttyv8 &quot;/usr/X11R6/bin/xdm -nodaemon&quot; xterm off secure<br /> <br /> and change it to:<br /> ttyv8 &quot;/usr/X11R6/bin/xdm -nodaemon&quot; xterm on secure<br /> <br /> <br /> You can also type this command at the command line on the client to test before hand.<br /> <br /> ===NFS Method===<br /> Recommended for machines over 1Ghz 256MB or if you want to utilise any of the clients devices such as local HD, USB, CD/DVD burners, etc.<br /> <br /> This is much trickier.<br /> <br /> Log in<br /> Now type 'startx' at the command line.<br /> <br /> <br /> <br /> ==todo==<br /> Here are some of the jobs left to do to make this secure or generally better:<br /> <br /> - If you don't configure your clients to run xdm it will put you at the text login. The problem here is people can login as root without a password for some reason. If the user hits &lt;Ctrl&gt;&lt;Alt&gt;&lt;Back space&gt; then it will crash them out to a login screen which the user could then login as root with out a password, not good!<br /> <br /> - Optimise the boot up sequence<br /> <br /> - There must be a simplier way to set this up if your going to use XDM in the end. IE: do we need to do half of this tutorial if we are going to run XDM.<br /> <br /> - When the same user logs onto two seperate machines they cannot start firefox or thunderbird as it complains about being open somewhere else. This assumes you have firefox and thunderbird already open on both machines that you logged onto.<br /> <br /> ===Known Issues===<br /> <br /> - Doesn't work with HP-COMPAQ-T5525 thin client as it doesn't want to boot, it says it's missing libfreetype.so.9 which we do have it just cannot find it for some reason. It's trying to use the VIA chipset for graphics which is different to all the other clients I've loaded successfully so far.<br /> <br /> - USB mice not working instead use PS/2. If we got this working it may help get the HP T5525 working<br /> <br /> ===Keyboard repeating on notebooks===<br /> - typing on some keyboards (like my notebook) causes double characters to display if you type too fast. - This is the notebook, if you go and set the KDE Accessabiltiy options and set the keyboard rate to 50ms, this fixes the problem.<br /> <br /> ===USB mouse===<br /> <br /> Editing /etc/devd.conf file and searched for ums<br /> remarked out the action line.<br /> <br /> rebooted.<br /> <br /> Someone off IRC suggested that I build a GENERIC xorg.conf file which has vesa, usb mouse and ps/2 mouse configurations through it.<br /> <br /> I reverted everything back to normal ps/2 mouse config, copying my usb config files to the following:<br /> /etc/devd.conf_usb<br /> /etc/rc.conf_usb<br /> /etc/X11/xorg.conf_usb<br /> <br /> I think we need a seperate configuration for the HP, it uses a weird display driver.<br /> <br /> ==links==<br /> <br /> http://www.onlamp.com/pub/a/bsd/2004/09/09/diskless_server.html<br /> <br /> http://www.onlamp.com/pub/a/bsd/2004/09/30/diskless_clients.html<br /> <br /> http://people.freebsd.org/~alfred/pxe/en_US.ISO8859-1/articles/pxe/article.html<br /> <br /> http://www.the-labs.com/FreeBSD/Diskless/<br /> <br /> http://www.nber.org/sys-admin/FreeBSD-diskless.html<br /> <br /> <br /> <br /> http://wikitest.freebsd.org/MarkusBoelter<br /> <br /> http://www.daemonsecurity.com/pub/pxeboot/<br /> <br /> http://www.kano.org.uk/projects/pxe/<br /> <br /> File Examples:<br /> <br /> http://www.watson.org/~robert/freebsd/pxe/<br /> <br /> PXE Information<br /> http://www.computerworld.com/action/article.do?command=viewArticleBasic&amp;articleId=108551<br /> <br /> [[Category:FreeBSD_for_Workstations]]</div>

Map7 http://www.freebsdwiki.net/index.php/X_Windows_Terminal 2006-10-15T08:29:25Z

<p>Map7: /* Setup diskless_rw */</p> <hr /> <div>==Advantages==<br /> X Windows can be used in a Server-Client relationship. By setting up your X Windows Server you allow the use of all the programs on that computer to all the client PC's. <br /> <br /> There are many advantages of running client computers in this manner:<br /> * They don't even need a hard drive. <br /> * It's silent as there are no moving parts<br /> * The solution saves power as your computers are very thin.<br /> * Everything can be backed up centrally.<br /> * Boot times for client PC's are the fastest around.<br /> * Clients don't need much CPU speed, memory, etc. Because of this they would be very cheap. You could get away with using a Pentium 100Mhz with 32MB ram, no hard drive, no CD-ROM, no Floppy and a fanless power supply. You just need a ethernet card with a PXEBOOT ROM. (XDM mode)<br /> * Central management of applications, users, config<br /> <br /> ==From the Beginning==<br /> I've based this document on FreeBSD 6.1.<br /> <br /> Install FreeBSD 6.1 as per usual.<br /> I've setup my mount points as this:<br /> '''Part Mount Size'''<br /> ad0s1b Swap (equal to how much memory I have in my machine)<br /> ad0s1a / 512MB<br /> ad0s1d /var 1G<br /> ad0s1e /tmp 512MB<br /> ad0s1f /usr 2GB min.<br /> /diskless_ro 512MB<br /> /diskless_rw 1GB min.<br /> <br /> I selected 'A' for auto and then deleted /usr and created /usr as 2g.<br /> <br /> Select User-X install. Yes to Ports if you have the room.<br /> <br /> Select SSH Server and NFS Server in the installation process, for the rest of the options go with the default.<br /> <br /> <br /> NOTE: If you forget to add any of the labels above, you will have to reboot as you cannot add labels to your boot drive when you have booted off it. So boot of the installation CD and use the configure -&gt; label option in the sysinstall screen to add these labels to your boot drive. You may need to retype the mount points for /, /var, /tmp and /usr by hitting 'm' on each label. Once you have created these labels in the 'Disklabel Editor' then you can hit 'w' to write them to the disk. answer 'yes' to the next question, hit 'ok' to the warning message. Now quit and reboot. Add them to fstab (/dev/ad0s1g /diskless_ro) &amp; (/dev/ad0s1h /diskless_rw) and mount.<br /> <br /> I find the best way to get this working is to break it down in to small steps and get each step working independantly. IE: Setup NFS and see if you can mount it from another FreeBSD machine, don't just assume it will work and boot your PXE-Boot machine.<br /> <br /> <br /> Throughout my documentation<br /> <br /> 192.168.1.1 = the Server<br /> <br /> 192.168.1.2 = the client (may be a full freebsd system or pxeboot)<br /> <br /> <br /> At this point I normally install fluxbox with the following line:<br /> <br /> shell# pkg_add -r fluxbox-devel<br /> <br /> <br /> change your ~/.xinitrc file to the following:<br /> <br /> startfluxbox<br /> <br /> <br /> Use the following command to update your fluxbox menus:<br /> <br /> shell$ fluxbox-generate_menu<br /> <br /> ==Running a single application==<br /> <br /> To get started I have my server setup running FreeBSD, with X-Windows and a few applications. Nothing too special. Then I have my client PC, which to start off I used the frenzy 1.0 boot CD to perform these initial tests. You can get this from [http://frenzy.org.ua/eng/ frenzy website]. I entered into fluxbox, but you could equally use any X session.<br /> You must allow incoming connections this is done with two commands<br /> <br /> client$ startx -listen_tcp<br /> client$ xhost +<br /> <br /> This allows all computers to start applications on your client PC. It's dangerous but good for testing everything is setup correctly.<br /> <br /> client$ ssh &lt;server user@server ip&gt;<br /> eg: ssh mick@192.168.1.1<br /> <br /> ssh$ export DISPLAY='192.168.1.2:0'<br /> <br /> Or if your running bash:<br /> ssh$ DISPLAY=&lt;client ip&gt;:&lt;client display&gt;; export DISPLAY<br /> eg: DISPLAY=192.168.1.2:0; export DISPLAY<br /> <br /> <br /> ssh$ xcalc &amp;<br /> <br /> This should display on your client<br /> <br /> ==Running a whole X Windows Session (XDM)==<br /> This sets up a server so that you can share your X session with any clients which want to connect. (Simular to Terminal Services under windows)<br /> <br /> <br /> ===server===<br /> edit:<br /> /usr/X11R6/lib/X11/xdm/xdm-config<br /> <br /> comment out with a '!' the request line&lt;br&gt;<br /> DisplayManager.requestPort: 0<br /> <br /> edit:&lt;br&gt;<br /> /usr/X11R6/lib/X11/xdm/Xaccess<br /> <br /> Enter a single asterisk any where in the file, so the contents should be one asterisk and the rest commented out. There should be an asterisk on line 49 which you can uncomment.<br /> <br /> Whilst in the /usr/X11R6/lib/X11/xdm directory do these commands:<br /> shell# vi Xstartup<br /> <br /> Add into this file:<br /> &lt;pre&gt;<br /> #!/bin/sh<br /> #<br /> # Xstartup<br /> #<br /> # This program is run as root after the user is verified<br /> #<br /> if [ -f /etc/nologin ]; then<br /> xmessage -file /etc/nologin -timeout 30 -center<br /> exit 1<br /> fi<br /> sessreg -a -l $DISPLAY -x /usr/X11R6/lib/xdm/Xservers $LOGNAME<br /> /usr/X11R6/lib/xdm/GiveConsole<br /> exit 0<br /> &lt;/pre&gt;<br /> <br /> <br /> shell# chmod +x Xstartup<br /> <br /> <br /> Make sure your firewall has all traffic for you lan. (Need to know which exact ports to allow).<br /> <br /> <br /> &lt;b&gt;Make sure you &lt;/b&gt;create ~/.xsession for each user which requires access and enter your start up for x <br /> eg:<br /> <br /> startfluxbox<br /> <br /> &lt;b&gt;run xdm on server as root&lt;/b&gt;<br /> <br /> shell# xdm<br /> <br /> <br /> You can put this xdm into the /etc/ttys so that it starts automatically on boot up.<br /> <br /> ===client===<br /> make sure your not in X<br /> <br /> type this command:<br /> <br /> shell# X -broadcast<br /> <br /> This assumes that you are running only one server.<br /> Otherwise use:<br /> <br /> shell# X -query 192.168.1.1<br /> <br /> ==DHCP - Install and setup==<br /> Server setup.<br /> <br /> install through package<br /> # pkg_add -r isc-dhcp3-server<br /> <br /> We do this so we can define the root path for the diskless system.<br /> <br /> copy /usr/local/etc/dhcpd.conf.sample to /usr/local/etc/dhcpd.conf<br /> <br /> edit /usr/local/etc/dhcpd.conf and make sure it has these lines in it.<br /> &lt;pre&gt;<br /> # dhcpd.conf<br /> #<br /> # Sample configuration file for ISC dhcpd<br /> #<br /> <br /> # option definitions common to all supported networks...<br /> #option domain-name &quot;example.org&quot;;<br /> #option domain-name-servers ns1.example.org, ns2.example.org;<br /> <br /> default-lease-time 3600;<br /> max-lease-time 86400;<br /> <br /> # If this DHCP server is the official DHCP server for the local<br /> # network, the authoritative directive should be uncommented.<br /> authoritative;<br /> <br /> # ad-hoc DNS update scheme - set to &quot;none&quot; to disable dynamic DNS updates.<br /> ddns-update-style none;<br /> <br /> option root-path &quot;192.168.1.1:/diskless_ro&quot;;<br /> <br /> # lines added for pxeboot client<br /> use-host-decl-names on;<br /> next-server 192.168.1.1;<br /> filename &quot;pxeboot&quot;;<br /> <br /> # Use this to send dhcp log messages to a different log file (you also<br /> # have to hack syslog.conf to complete the redirection).<br /> log-facility local7;<br /> <br /> # No service will be given on this subnet, but declaring it helps the<br /> # DHCP server to understand the network topology.<br /> <br /> <br /> # This is a very basic subnet declaration.<br /> <br /> subnet 192.168.1.0 netmask 255.255.255.0 {<br /> range 192.168.1.10 192.168.1.20;<br /> }<br /> &lt;/pre&gt;<br /> <br /> Create the leases file<br /> &lt;pre&gt;<br /> # touch /var/db/dhcpd.leases<br /> &lt;/pre&gt;<br /> <br /> <br /> Restart the daemon<br /> &lt;pre&gt;<br /> # killall dhcpd<br /> # dhcpd<br /> &lt;/pre&gt;<br /> <br /> <br /> Add to /etc/rc.conf<br /> &lt;pre&gt;<br /> dhcpd_enable=&quot;YES&quot;<br /> &lt;/pre&gt;<br /> <br /> ===Using a seperate DHCP server===<br /> If you already have a DHCP server and you want to use that instead then you have to do these steps.<br /> <br /> <br /> ====On your DHCP Server====<br /> 1. edit /usr/local/etc/dhcpd.conf and add the following<br /> &lt;pre&gt;<br /> authoritative;<br /> ddns-update-style none;<br /> <br /> option root-path &quot;&lt;X Server IP&gt;:/diskless_ro&quot;;<br /> <br /> # lines added for pxeboot client<br /> use-host-decl-names on;<br /> next-server &lt;X Server IP&gt;;<br /> filename &quot;pxeboot&quot;;<br /> &lt;/pre&gt;<br /> 2. stop dhcpd<br /> 3. start dhcpd<br /> <br /> <br /> ====Client====<br /> Your client should boot now just remember that you may get a different IP now that you are talking to a different DHCP server so you have to change your exports file and copy accross a directory in /diskless_rw for the new IP. All this is done on the X Server.<br /> <br /> ==TFTP Setup==<br /> TFTP helps us transport the kernel to the PXE-Boot machines.<br /> <br /> &lt;pre&gt;<br /> # mkdir /tftpboot<br /> # cp /boot/pxeboot /tftpboot<br /> &lt;/pre&gt;<br /> <br /> Uncomment the following line in /etc/inetd.conf<br /> <br /> &lt;pre&gt;<br /> tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /tftpboot<br /> &lt;/pre&gt;<br /> <br /> Restart the inetd service<br /> &lt;pre&gt;<br /> # killall -HUP inetd<br /> &lt;/pre&gt;<br /> <br /> If inetd has not started automatically do the following:<br /> <br /> Add the following to /etc/rc.conf<br /> &lt;pre&gt;<br /> inetd_enable=&quot;YES&quot;<br /> &lt;/pre&gt;<br /> <br /> Now start inetd manually.<br /> &lt;pre&gt;<br /> # inetd<br /> &lt;/pre&gt;<br /> <br /> ===Test===<br /> To test that tftp has loaded type the following:<br /> &lt;pre&gt;<br /> # sockstat -4l | grep 69 <br /> &lt;/pre&gt;<br /> <br /> and you should see this:<br /> &lt;pre&gt;<br /> root inetd 13719 5 udp4 *:69 *:*<br /> &lt;/pre&gt;<br /> <br /> ==NFS Setup==<br /> Network File System. Here we share all the directories from the server so that the diskless clients see these drives as if those directories were the diskless client's.<br /> <br /> ===Server Setup===<br /> If you forgot to select 'Yes' to NFS server setup in the FreeBSD installation then you have to setup the server manually like so:<br /> <br /> Enable NFS /etc/rc.conf<br /> &lt;pre&gt;<br /> rpcbind_enable=&quot;YES&quot;<br /> nfs_server_enable=&quot;YES&quot;<br /> &lt;/pre&gt;<br /> <br /> ===Test===<br /> A quick test to see if your NFS server is acting normal:<br /> <br /> Edit the /etc/exports and add the following<br /> &lt;pre&gt;<br /> /usr -alldirs<br /> &lt;/pre&gt;<br /> <br /> This allows anyone to connect to your /usr mount.<br /> <br /> Now run these commands to restart and view your mounts<br /> &lt;pre&gt;<br /> # kill -HUP `cat /var/run/mountd.pid`<br /> # showmount -e<br /> &lt;/pre&gt;<br /> <br /> Now try and mount it from a client running BSD<br /> &lt;pre&gt;<br /> # mount -t nfs 192.168.1.1:/usr /mnt<br /> &lt;/pre&gt;<br /> <br /> <br /> ===Server exports setup===<br /> <br /> Make directories for each IP for your clients<br /> &lt;pre&gt;<br /> # cd /diskless_rw<br /> # mkdir 192.168.1.2<br /> # cd 192.168.1.2<br /> # mkdir etc var<br /> &lt;/pre&gt;<br /> <br /> Configure /etc/exports<br /> &lt;pre&gt;<br /> # file systems accessible only for reading:<br /> # Original way of linking up the /usr<br /> #/usr -ro -maproot=0 -network 192.168.1.0 -mask 255.255.255.0<br /> <br /> /usr -network 192.168.1.0 -mask 255.255.255.0<br /> /diskless_ro -ro -maproot=0 -network 192.168.1.0 -mask 255.255.255.0<br /> /diskless_rw/192.168.1.2/etc /diskless_rw/192.168.1.2/var -maproot=root 192.168.1.2<br /> <br /> &lt;/pre&gt;<br /> <br /> Restarting NFS<br /> &lt;pre&gt;<br /> # kill -HUP `cat /var/run/mountd.pid`<br /> &lt;/pre&gt;<br /> <br /> <br /> If NFS is not started yet do the following:<br /> &lt;pre&gt;<br /> data# rpcbind<br /> data# nfsd -u -t -n 20 -h 192.168.1.1<br /> data# mountd -r<br /> &lt;/pre&gt;<br /> <br /> Testing to see if the exports are correct<br /> &lt;pre&gt;<br /> data# showmount -e<br /> Exports list on localhost:<br /> /usr 192.168.1.0<br /> /diskless_rw/192.168.1.2/var 192.168.1.2<br /> /diskless_rw/192.168.1.2/etc 192.168.1.2<br /> /diskless_ro 192.168.1.0<br /> &lt;/pre&gt;<br /> <br /> ==Setup diskless_rw==<br /> Create directories<br /> <br /> &lt;pre&gt;<br /> # cd /diskless_rw/192.168.1.2/etc<br /> # mkdir pam.d X11<br /> <br /> # cd /diskless_rw/192.168.1.2/var<br /> # mkdir home log run tmp<br /> # chmod 1777 tmp<br /> &lt;/pre&gt;<br /> <br /> Create a swap file in the var directory for the client<br /> &lt;pre&gt;<br /> # dd if=/dev/zero of=/diskless_rw/192.168.1.2/var/swap bs=1k count=32000<br /> &lt;/pre&gt;<br /> <br /> in the /diskless_rw/&lt;ip&gt;/var/log directory I created the following log files so that syslogd would have files to write to:<br /> &lt;pre&gt;<br /> # cd /diskless_rw/192.168.1.2/var/log<br /> # touch messages security auth.log maillog lpd-errs xferlog cron debug.log slip.log ppp.log<br /> &lt;/pre&gt;<br /> <br /> <br /> Copy the following files from the systems /etc directory to /diskless_rw/&lt;client ip&gt;/etc<br /> # cp -Rv &lt;files&gt; /diskless_rw/&lt;ip&gt;/etc<br /> <br /> &lt;pre&gt;<br /> auth.conf<br /> disktab<br /> gettytab<br /> group<br /> hosts<br /> login.access<br /> login.conf<br /> login.conf.db<br /> master.passwd<br /> netconfig<br /> protocols<br /> pam.d<br /> pwd.db<br /> services<br /> spwd.db<br /> syslog.conf<br /> termcap -&gt; /usr/share/misc/termcap<br /> ttys<br /> &lt;/pre&gt;<br /> <br /> It's very important that you copy all the files in pam.d across otherwise you will not have a password prompt on your login.<br /> <br /> ==Setup diskless_ro==<br /> This is the common root mount for all pxe-boot clients.<br /> <br /> Copy accross important directories and kernel from boot to diskless_ro<br /> &lt;pre&gt;<br /> # cp -rv /bin /lib /libexec /sbin /boot /diskless_ro<br /> # mkdir /diskless_ro/usr<br /> &lt;/pre&gt;<br /> <br /> For some client machines you may have to disable the ACPI (Power management) in the /diskless_ro/boot/device.hints<br /> &lt;pre&gt;<br /> hint.acpi.0.disabled=&quot;1&quot; <br /> &lt;/pre&gt;<br /> <br /> Make a dev so that clients can boot without freezing.<br /> &lt;pre&gt;<br /> # mkdir /diskless_ro/dev<br /> &lt;/pre&gt;<br /> <br /> Make a directory so that we can mount var from the /diskless_rw/&lt;client ip&gt;/var<br /> &lt;pre&gt;<br /> # mkdir /diskless_ro/var<br /> &lt;/pre&gt; <br /> <br /> So we can use the systems /var/tmp and /usr/home directory make soft links to them<br /> &lt;pre&gt;<br /> # cd /diskless_ro<br /> # ln -s /var/tmp .<br /> # ln -s /usr/home .<br /> &lt;/pre&gt;<br /> <br /> We require a few files from the systems /etc directory to be copied into the /diskless_ro/etc for common use between the thin clients.<br /> &lt;pre&gt;<br /> # mkdir /diskless_ro/etc<br /> # cp /etc/services /etc/netconfig /etc/login.conf /diskless_ro/etc<br /> &lt;/pre&gt;<br /> <br /> <br /> ===rc file===<br /> The /diskless_ro/etc/rc file is the first file which is ran after the kernel has loaded. Here we mount a the labels from the server.<br /> <br /> Create the /diskless_ro/etc/rc<br /> &lt;pre&gt;<br /> #!/bin/sh<br /> <br /> PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin; export PATH<br /> TMPDIR=~/tmp;export TMPDIR<br /> TMP=~/tmp;export TMP<br /> <br /> mount -t nfs 192.168.0.1:/usr /usr<br /> <br /> boot_ip=`/sbin/ifconfig | /usr/bin/grep &quot;inet &quot; | /usr/bin/grep -v 127.0.0.1 |<br /> /usr/bin/awk '{print $2}'`<br /> mount_nfs -L 192.168.0.1:/diskless_rw/${boot_ip}/etc /etc<br /> mount_nfs -L 192.168.0.1:/diskless_rw/${boot_ip}/var /var<br /> <br /> swapon /var/swap<br /> <br /> #rm -rf /var/tmp/*<br /> #rm -rf /var/tmp/.*<br /> <br /> # Option if you choose XDM terminals<br /> #X -query 192.168.0.1<br /> <br /> . /etc/rc2<br /> exit 0<br /> <br /> &lt;/pre&gt;<br /> <br /> &lt;b&gt;Remember to change 192.168.0.1 to your X server's IP&lt;/b&gt;<br /> <br /> The -L on the mount_nfs is there so we don't get flock errors.<br /> <br /> ===rc2 file===<br /> This sets up some links for libraries and the logging daemon.<br /> <br /> &lt;pre&gt;<br /> #!/bin/sh<br /> <br /> mount -a<br /> /sbin/ldconfig -elf /usr/lib/compat /usr/X11R6/lib /usr/local/lib<br /> <br /> syslogd<br /> &lt;/pre&gt;<br /> <br /> <br /> Now change permissions so rc can run.<br /> # chmod +x rc*<br /> <br /> Copy /diskless_ro/etc/rc and rc2 to /diskless_rw/&lt;client ip&gt;/etc<br /> # cp /diskless_ro/etc/rc* /diskless_rw/192.168.1.2/etc<br /> <br /> <br /> <br /> ==GRUB Floppy boot (optional)==<br /> <br /> (would like to compile this ourselves later)<br /> To get started we downloaded the image from www.hp.uab.edu/~ed/grub-net<br /> <br /> shell# dd if=/data/grub-net.img of=/dev/fd0<br /> <br /> Then we mounted it as msdos<br /> Remove/rename menu.1st from the grub directory as it was doing something funny with it. We think that it was looking for a tftp server through our dhcp and we don't have a the dhcp setup correctly here, so we wanted to do it manually.<br /> <br /> Reboot off the floppy now..<br /> <br /> grub&gt; ifconfig --address=192.168.1.2 --mask=255.255.255.0 --gateway=192.168.1.1<br /> --server=192.168.1.2<br /> <br /> OR you can use dhcp&lt;br&gt;<br /> <br /> grub&gt; dhcp&lt;br&gt; <br /> grub&gt; tftpserver 192.168.1.2&lt;br&gt;<br /> <br /> <br /> Setup tftp on your server, we created a directory /tftpboot. <br /> <br /> <br /> ===Starting diskless system through GRUB===<br /> This is an alternative boot loader. You can use this for testing, if you don't have a pxeboot chip, otherwise skip this section.<br /> <br /> These commands are half working...&lt;br&gt;<br /> <br /> grub&gt; root (nd)&lt;br&gt;<br /> grub&gt; kernel /kernel root=ad0s1a&lt;br&gt;<br /> grub&gt; pxeboot&lt;br&gt;<br /> <br /> ==Completely Diskless System (PXEBOOT ROM) (optional)==<br /> <br /> Running completely diskless by booting from a Network ROM Chip.<br /> <br /> We have now got a Intel GD82559 Etherexpress pro/100 Card.<br /> <br /> When we boot up on the client machine with that card it displays:&lt;br /&gt;<br /> &lt;br /&gt;<br /> Intel UNDI, PXE-2.0 (build 067)&lt;br /&gt;<br /> Copyright (C) 1997-1998 Intel Corporation&lt;br /&gt;<br /> &lt;br /&gt;<br /> Which we cannot get working so we have read that you have to update this version to Build 82.&lt;br /&gt;<br /> &lt;br /&gt;<br /> &lt;br /&gt;<br /> copy /boot/pxeboot to /tftpboot directory we made before&lt;br /&gt;<br /> &lt;br /&gt;<br /> - Downloaded proboot.exe from support.intel.com and unpacked into a windows box.&lt;br /&gt;<br /> - Copied ibautil.exe onto a windows 98 boot disk.&lt;br /&gt;<br /> - Rebooted the test box after disabling network boot on the nic (otherwise it'll kick in before the floppy).&lt;br /&gt;<br /> - Ran ibautil -iv to see what embedded image versions were available:&lt;br /&gt;<br /> &lt;br /&gt;<br /> Intel(R) Boot Agent XG v1.0.09&lt;br /&gt;<br /> Intel(R) Boot Agent GE v1.2.36&lt;br /&gt;<br /> Intel(R) Boot Agent FE v4.1.19&lt;br /&gt;<br /> &lt;br /&gt;<br /> - Ran ibautil -up to perform the image upgrade.&lt;br /&gt;<br /> &lt;br /&gt;<br /> It's interesting to note that no version showed up for out intel nic when initially running ibautil. After the upgrade, however, the version corectly showed as 4.1.19.&lt;br /&gt;&lt;br /&gt;<br /> <br /> I made sure that I had simular features to this in my dhcpd.conf file:&lt;br /&gt;<br /> option broadcast-address 192.168.254.255;&lt;br /&gt;<br /> option domain-name-servers 192.168.254.3;&lt;br /&gt;<br /> option domain-name &quot;simerson.net&quot;;&lt;br /&gt;<br /> option routers 192.168.254.1;&lt;br /&gt;<br /> option subnet-mask 255.255.255.0;&lt;br /&gt;<br /> server-name &quot;pxe-gw&quot;;&lt;br /&gt;<br /> server-identifier 192.168.254.3;&lt;br /&gt;<br /> next-server 192.168.254.3;&lt;br /&gt;<br /> default-lease-time -1;&lt;br /&gt;<br /> &lt;br /&gt;<br /> subnet 192.168.254.0 netmask 255.255.255.0 {&lt;br /&gt;<br /> range 192.168.254.32 192.168.254.99;&lt;br /&gt;<br /> option root-path &quot;/usr/local/export/pxe&quot;;&lt;br /&gt;<br /> filename &quot;pxeboot&quot;;&lt;br /&gt;<br /> }&lt;br /&gt;<br /> host cm.simerson.net {&lt;br /&gt;<br /> hardware ethernet 00:e0:18:98:f0:cc;&lt;br /&gt;<br /> fixed-address 192.168.254.126;&lt;br /&gt;<br /> }&lt;br /&gt;<br /> host c1.simerson.net {&lt;br /&gt;<br /> hardware ethernet 00:60:97:0e:bb:a7;&lt;br /&gt;<br /> fixed-address 192.168.254.131;&lt;br /&gt;<br /> }&lt;br /&gt;<br /> &lt;br /&gt;<br /> <br /> ==X config notes==<br /> On the X server the /etc/X11/xorg.conf file is only used for the X server not the clients.<br /> <br /> To use this same configuration for your X Terminal Clients copy this file to /diskless_rw/&lt;Client IP&gt;/etc/X11 and it will use it.<br /> <br /> ==Starting X on the client==<br /> There are two ways of doing this and it depends on your hardware mainly. <br /> <br /> 1. run all programs on the server using the servers CPU and Memory this we will call the 'XDM Method'<br /> 2. run all programs from the NFS mounts using the clients CPU and Memory but the HD of the server, this we will call the 'NFS Method'<br /> <br /> Both methods will boot from PXE-Boot and can be diskless.<br /> <br /> ===XDM Method===<br /> Recommended for machines less than 1Ghz 256MB<br /> <br /> This is quite simple to setup. Change your rc file in the /diskless_ro/etc directory to have this line at the end:<br /> &lt;pre&gt;<br /> X -query &lt;server ip&gt;<br /> &lt;/pre&gt;<br /> <br /> Make sure on the server you setup xdm to start on system startup<br /> # vi /etc/ttys<br /> <br /> Search for this line:<br /> ttyv8 &quot;/usr/X11R6/bin/xdm -nodaemon&quot; xterm off secure<br /> <br /> and change it to:<br /> ttyv8 &quot;/usr/X11R6/bin/xdm -nodaemon&quot; xterm on secure<br /> <br /> <br /> You can also type this command at the command line on the client to test before hand.<br /> <br /> ===NFS Method===<br /> Recommended for machines over 1Ghz 256MB or if you want to utilise any of the clients devices such as local HD, USB, CD/DVD burners, etc.<br /> <br /> This is much trickier.<br /> <br /> Log in<br /> Now type 'startx' at the command line.<br /> <br /> <br /> <br /> ==todo==<br /> Here are some of the jobs left to do to make this secure or generally better:<br /> <br /> - If you don't configure your clients to run xdm it will put you at the text login. The problem here is people can login as root without a password for some reason. If the user hits &lt;Ctrl&gt;&lt;Alt&gt;&lt;Back space&gt; then it will crash them out to a login screen which the user could then login as root with out a password, not good!<br /> <br /> - Optimise the boot up sequence<br /> <br /> - There must be a simplier way to set this up if your going to use XDM in the end. IE: do we need to do half of this tutorial if we are going to run XDM.<br /> <br /> - When the same user logs onto two seperate machines they cannot start firefox or thunderbird as it complains about being open somewhere else. This assumes you have firefox and thunderbird already open on both machines that you logged onto.<br /> <br /> ===Known Issues===<br /> <br /> - Doesn't work with HP-COMPAQ-T5525 thin client as it doesn't want to boot, it says it's missing libfreetype.so.9 which we do have it just cannot find it for some reason. It's trying to use the VIA chipset for graphics which is different to all the other clients I've loaded successfully so far.<br /> <br /> - USB mice not working instead use PS/2. If we got this working it may help get the HP T5525 working<br /> <br /> ===Keyboard repeating on notebooks===<br /> - typing on some keyboards (like my notebook) causes double characters to display if you type too fast. - This is the notebook, if you go and set the KDE Accessabiltiy options and set the keyboard rate to 50ms, this fixes the problem.<br /> <br /> ===USB mouse===<br /> <br /> Editing /etc/devd.conf file and searched for ums<br /> remarked out the action line.<br /> <br /> rebooted.<br /> <br /> Someone off IRC suggested that I build a GENERIC xorg.conf file which has vesa, usb mouse and ps/2 mouse configurations through it.<br /> <br /> I reverted everything back to normal ps/2 mouse config, copying my usb config files to the following:<br /> /etc/devd.conf_usb<br /> /etc/rc.conf_usb<br /> /etc/X11/xorg.conf_usb<br /> <br /> I think we need a seperate configuration for the HP, it uses a weird display driver.<br /> <br /> ==links==<br /> <br /> http://www.onlamp.com/pub/a/bsd/2004/09/09/diskless_server.html<br /> <br /> http://www.onlamp.com/pub/a/bsd/2004/09/30/diskless_clients.html<br /> <br /> http://people.freebsd.org/~alfred/pxe/en_US.ISO8859-1/articles/pxe/article.html<br /> <br /> http://www.the-labs.com/FreeBSD/Diskless/<br /> <br /> http://www.nber.org/sys-admin/FreeBSD-diskless.html<br /> <br /> <br /> <br /> http://wikitest.freebsd.org/MarkusBoelter<br /> <br /> http://www.daemonsecurity.com/pub/pxeboot/<br /> <br /> http://www.kano.org.uk/projects/pxe/<br /> <br /> File Examples:<br /> <br /> http://www.watson.org/~robert/freebsd/pxe/<br /> <br /> PXE Information<br /> http://www.computerworld.com/action/article.do?command=viewArticleBasic&amp;articleId=108551<br /> <br /> [[Category:FreeBSD_for_Workstations]]</div>

Map7