http://freebsdwiki.net/api.php?action=feedcontributions&user=DrModiford&feedformat=atomFreeBSDwiki - User contributions [en]2024-03-29T07:53:35ZUser contributionsMediaWiki 1.18.0http://freebsdwiki.net/index.php/Sparc_-_GotchasSparc - Gotchas2009-06-04T00:17:46Z<p>DrModiford: Enough comments gentlemen! Added link to a real "been there, done it" guide.</p>
<hr />
<div>This is a stub article for different things to be aware of when installing or using FreeBSD on Sparc hardware.<br />
<br />
See [[Sparc_-_Installing_FreeBSD|this article]] containing documentation based on a real life installation on an Ultra-based system, including a brief essential guide to the OpenBoot firmware (enough to get FreeBSD booted at least).<br />
<br />
==Servers only, thanks.==<br />
FreeBSD + Sparc = No GUI. See [http://www.freebsd.org/releases/5.0R/hardware-sparc64.html#AEN273 this link] w/r/t 5.0; later versions of FreeBSD documentation do not mention it at all.<br />
<br />
==Sun keyboard and mouse? Throw them away!==<br />
Toss 'em because you can't use 'em. Serial console installation only, please. See [[Sparc_-_Terminal_Emulation]]<br /><br />
-- This is no longer true for FreeBSD6? I have used sun keyboards to install FreeBSD6 on my sparc machines.<br /><br />
--I also was able to install using the Sun mouse and keyboard using FreeBSD 7.<br />
<br />
==Booting can be problematic==<br />
The OpenBoot Firmware: learn it, love it.<br />
<br />
==Java is more of a pain==<br />
All the Java sources and installers etc etc -- they're iX86 only. <br />
<br />
[[Category : Architecture-Specific]]</div>DrModifordhttp://freebsdwiki.net/index.php/NTP,_configuringNTP, configuring2009-05-29T18:24:15Z<p>DrModiford: Added small section on forcing synchronisation on extended drift</p>
<hr />
<div>After installing [[Ntp]], you'll want to configure it properly. Remember to allow TCP and UDP ports 123 if you're firewalling the client/server.<br />
<br />
==NTP Clients==<br />
If you're a client, you'll need to listen locally if you've got an NTP server locally to get the time. To start, edit [[/etc/ntp.conf]] and make sure it has something like this in it: <br />
<br />
# Because the computer clocks drift, keep the drift info somewhere:<br />
driftfile /etc/ntp.drift <br />
<br />
# if we are a client that listens to NTP broadcasts on the LAN, uncomment this line:<br />
#broadcastclient<br />
<br />
# Let's setup a log file for NTP:<br />
logfile /var/log/ntp.log<br />
<br />
==NTP Servers==<br />
<br />
First, synchronize to a known good time server -- there are many listed at ntp.isc.org, and due to common sense and politeness, I won't list one particular server here, but [http://tycho.usno.navy.mil/ntp.html the US Navy] has some servers available -- be sure to read their policies for allowed use. Once you've got a server that you can use, run<br />
ntpdate time.someserver.somewhere.com <br />
and your system will update to that time. You may want to verify that the time is correct, if you've got a Java-capable browser handy, [http://time.gov time.gov] will give you the correct time for the timezone you're in.<br />
<br />
Once you've got that done, find a server that you can update from regularly -- be sure you've read through [http://ntp.isc.org/bin/view/Servers/WebHome the documentation] and obtained permission to use the server (seriously, this is important, folks have no sense of humor about this, see links below for why) -- it's time to set up your [[/etc/ntpd.conf]] which will at a minimum need to have three lines:<br />
server time.someserver.somewhere.com prefer<br />
driftfile /var/db/ntpd.drift<br />
restrict default notrust nomodify nopeer<br />
The server line may be repeated (you'll want more than one and less than 5 -- although it's recommended you don't go over 3), and if you leave out the "prefer" keyword and have multiple server lines, then you'll round-robin through the list. If you have multiple server lines and leave the "prefer" keyword in, you'll only go to the other servers (without the "prefer") if your "preferred" server can't be reached. <br />
<br />
The ''restrict'' keyword is basically an allow statement that restricts how your NTP service on your server may be used (and by who); modifier options after restrict help with this:<br />
<br />
restrict Address [ mask Number | default ] [ Parameter ... ] <br />
<br />
Allowed parameters are:<br />
ignore <br />
Specifies to ignore all packets from hosts which match this entry. <br />
Does not respond to queries nor time server polls. <br />
<br />
limited <br />
Specifies that these hosts are subject to limitation of number of <br />
clients from the same net. Net in this context refers to the IP notion <br />
of net (class A, class B, class C, and so on). Only accepts the first <br />
client_limit hosts that have shown up at the server and that have been<br />
active during the last client_limit_period seconds. Rejects requests <br />
from other clients from the same net. Only takes into account time <br />
request packets. Private, control, and broadcast packets are not subject<br />
to client limitation and therefore do not contribute to client count. <br />
The monitoring capability of the xntpd daemon keeps a history of clients.<br />
When you use this option, monitoring remains active. The default value for<br />
client_limit is 3. The default value for client_limit_period is 3600 seconds. <br />
<br />
nomodify <br />
Specifies to ignore all NTP mode 6 and 7 packets which attempt to modify the<br />
state of the server (run time reconfiguration). Permits queries which return<br />
information. <br />
<br />
nopeer <br />
Specifies to provide stateless time service to polling hosts, but not to <br />
allocate peer memory resources to these hosts. <br />
<br />
noquery <br />
Specifies to ignore all NTP mode 6 and 7 packets (information queries and<br />
configuration requests) from the source. Does not affect time service. <br />
<br />
noserve <br />
Specifies to ignore NTP packets whose mode is not 6 or 7. This denies time<br />
service, but permits queries. <br />
<br />
notrap <br />
Specifies to decline to provide mode 6 control message trap service to<br />
matching hosts. The trap service is a subsystem of the mode 6 control message<br />
protocol intended for use by remote event-logging programs. <br />
<br />
notrust <br />
Specifies to treat these hosts normally in other respects, but never use<br />
them as synchronization sources. <br />
<br />
ntpport <br />
Specifies to match the restriction entry only if the source port in the<br />
packet is the standard NTP UDP port (123). <br />
<br />
Note that using no parameters means "open access" for your server.<br />
<br />
Now that you've configured your ntp.conf file and want to use your server, start up the program manually:<br />
# ntpd -p /var/run/ntpd.pid<br />
<br />
===NTP pool servers===<br />
Please consider using the [http://ntp.isc.org/bin/view/Servers/NTPPoolServers NTP Pool servers]. These are public time servers selected by round-robin. The DNS reference changes each hour. These time servers have ''volunteered'' to offer their services through the pool. As the server pool grows, the service regions will become increasingly more specific, and the results will be even more reliable. To [http://www.pool.ntp.org/use.html use the pool], for example, users in the U.S. would add these lines to their /etc/ntp.conf <br />
server 0.us.pool.ntp.org<br />
server 1.us.pool.ntp.org<br />
server 2.us.pool.ntp.org<br />
<br />
Some say that you do not need, and should not use, more than three server lines in your /etc/ntp.conf. [http://ntp.isc.org/bin/view/Support/ConfiguringNTP Others disagree].<br />
<br />
Similarly, if you need to quickly set your system clock, to use the pool (if your ISP does not offer a time service) you would say (e.g. in the U.S.):<br />
# /usr/sbin/ntpdate 0.us.pool.ntp.org<br />
<br />
It is usually considered poor manners to regularly hit even a server pool more than a few times in a 24 hour period. If you're one of those many who are in the habit of synching every clock on your LAN against a single public server, every few seconds, your IP may end up on the clock-master's list of Folks We Don't Like, and your network's time of reckoning will eventually arrive - or worse, you will contribute to stopping these vital services.<br />
<br />
==Auto-starting ntpd==<br />
Edit your /etc/rc.conf and add this to the end; <br />
<br />
# ntpd sets the time in small increments, ntpdate sets the time<br />
# no matter how large the discrepancy is. If you're running ntpd<br />
# you'll want to weigh the risks of getting a wildly different time<br />
# given to your system from whatever system _you_ are getting the<br />
# time from. If you're polling time data from absolutely known-good<br />
# servers, it might not be a bad idea to get the time from them on boot-up.<br />
# If you want to do that, uncomment this line;<br />
# ntpdate_enable="NO"<br />
# turn on the ntp daemon:<br />
ntpd_enable="YES"<br />
# The NTP program is located here:<br />
ntpd_program="/usr/local/bin/ntpd"<br />
# and we want to use it with these options; see man page for details<br />
ntpd_flags="-A -g -N -c /etc/ntp.conf -p /var/run/ntpd.pid -l /var/log/ntpd.log"<br />
<br />
<br />
''Note: ntpd_enable was xntpd_enable in older FreeBSD releases (before FreeBSD-5). If you're running FreeBSD-4, replace every instance of ntpd with xntpd (xntpd_enable="YES", for example).''<br />
<br />
==NTP etiquette==<br />
<br />
The N stands for Network, but if you've got your own network, it behooves you -- and you're expected to -- either keep an ntp server for it or use one that you're allowed to; your ISP's or one you setup yourself. NTP stratum 1 servers are neither ubiquitous nor fair use for everyone. If you have a GPS or atomic-clock enabled server, then you can run your own stratum 1 server. More than likely you'll want to run a stratum 3 (or higher) server for your network, and you'll want to pull time from stratum 2 or 1 servers that are more accurate for you. <br />
<br />
Horror stories on why you want to only use servers you're allowed to:<br />
<br />
http://www.cs.wisc.edu/~plonka/netgear-sntp/<br />
<br />
http://people.freebsd.org/~phk/dlink/<br />
<br />
http://www.lightbluetouchpaper.org/2006/04/07/when-firmware-attacks-ddos-by-d-link/<br />
<br />
== Synchronisation Tip ==<br />
<br />
Sometimes the time on your FreeBSD server can drift beyond the maximum limit that the NTP daemon allows for bringing it back into line. Perhaps the workstation isn't on very often or the server was off at the last daylight savings time shift (such as BST in the United Kingdom). If you have a log file enabled for NTP it will highlight this issue.<br />
<br />
A tip from the [http://www.pool.ntp.org/en/use.html NTP organisation website] offers the following to force synchronisation:<br />
<br />
server# /etc/rc.d/ntpd stop<br />
Stopping ntpd.<br />
server# ntpdate pool.ntp.org<br />
29 May 19:09:50 ntpdate[40071]: step time server 213.9.73.106 offset 3474.968729 sec<br />
server# /etc/rc.d/ntpd start<br />
<br />
This may affect time-critical servers such as firewalls where event logging is date and time stamped for possible investigative / audit purposes.<br />
<br />
[[Category: Common Tasks]] [[Category: FreeBSD for Servers]]</div>DrModifordhttp://freebsdwiki.net/index.php/KopeteKopete2009-05-12T01:28:55Z<p>DrModiford: Small changes</p>
<hr />
<div>Kopete is an application designed for KDE (and features as part of KDE's network package) that emulates many of the common (and some not so common) internet messenger programs, in particular the following: <br />
<br />
* AOL Instant Manager (AIM);<br />
* Gadu-Gadu<br />
* ICQ (part of AOL, also known as QIP in eastern countries);<br />
* Internet Relay Chat (IRC);<br />
* Jabber;<br />
* Lotus Sametime;<br />
* Microsoft Messenger (MSN, rebranded as Live Messenger);<br />
* Novell GroupWise<br />
* Short Message Service (SMS);<br />
* Skype (being removed eventually);<br />
* Winpopup (as issued by a NET SEND command on Microsoft Windows platform);<br />
* Yahoo! Messenger;<br />
<br />
The interface is similar to other messenger applications, like that of Live / MSN Messenger or ICQ for example, but has the advantage of hosting multiple accounts using the multiple protocols. This means you can have an account for each ICQ, MSN and Yahoo! and use a single instance of Kopete to sign into all of them. Indeed you could have two or more accounts of the same protocol at once, such as two ICQ accounts. Kopete allows the user to assign different colours to identical protocols to differentiate them.<br />
<br />
Being KDE specific means it integrates very well into the desktop, including the system tray as an icon and the use of KDE's KWallet feature for password management.<br />
<br />
Many of the features provided by the genuine messenger protocols are supported by the 'emulation' within Kopete, including the ability to use and receive voice and webcam sessions (though this is largely dependent on the hardware support of the underlying operating system). Other features include pop-up 'speech bubble' notifications of contacts online status, multi-person chat and, possibly considered eye-candy, MSN's animated pictorial words and nudges (much to the annoyance of many!).<br />
<br />
Those messenger protocols available under open source licenses are fully supported where-as the commercial protocols are available by methods of reverse engineering and therefore are on a best-efforts basis, hence the term ''emulation''.<br />
<br />
See [http://kopete.kde.org/ Kopete] official website.<br />
<br />
[[Category: Ports and Packages]] [[Category: FreeBSD for Workstations]]</div>DrModifordhttp://freebsdwiki.net/index.php/RAID0,_Software,_How_to_setupRAID0, Software, How to setup2009-05-09T20:50:16Z<p>DrModiford: The -g should be -h (that's been wrong for a while!)</p>
<hr />
<div>The following is a practical guide to setting up software RAID0 on FreeBSD using the [[GEOM]] subsystem. This may appear to be written as an aide-memoir however it is a real-working example written by the author actually configuring a real system. <br />
<br />
The system is intended to be a file server using Samba.<br />
<br />
== Obligatory warning == <br />
<br />
By using RAID0, you are at least '''doubling''' the chance of data loss over any given period of time. There is '''no''' parity in RAID0, which means that failure of any drive in the array '''will destroy the entire volume.''' If you are well aware of the MTBF (Mean Time Between Failure) ratings of all the drives you will use, understand the increased risk of data loss, and have a satisfactory backup plan to compensate for this, read on. If any of this sounds scary - and it should - [[User:Jimbo|Jimbo]] strongly suggests you consider adding one more drive and setting up a [[RAID3]] array instead.<br />
<br />
== The Hardware ==<br />
<br />
The system comprises of the following hardware:<br />
<br />
* Processor: AMD Athlon XP 3000;<br />
* Motherboard: ASUS KT4AV;<br />
* Memory: 512MB;<br />
* Storage:<br />
** Hard Drive: Maxtor 30GB IDE (for Operating System);<br />
** Hard Drive: Seagate 500GB SATA x2 (for RAID0 file share);<br />
** Hard Drive Controller: Promise PDC20375 SATA150<br />
* Case: basic full-ATX sized;<br />
* PSU: Antec ATX (with SATA power connections).<br />
<br />
The Promise SATA controller is capable of RAID0 and [[RAID1]] however it is being used as a simple hard drive controller for the two SATA Seagate drives since the motherboard has no SATA ports. The RAID0 is provided by the FreeBSD software-based solution documented within this article.<br />
<br />
== The Software ==<br />
<br />
This guide wouldn't be here unless it involved FreeBSD! It is intended that the system will be a file server for media files using [[Samba]] to not only share the files but also to offer [[WINS]] for name resolution on a small LAN.<br />
<br />
== Configuring RAID0 ==<br />
<br />
The following steps are based on a working implementation however it should be broad enough to cover most instances and be used as a guide to others wishing to implement RAID0.<br />
<br />
You will need to [[su]] or otherwise become [[root]] to execute these steps.<br />
<br />
On FreeBSD the RAID0 "driver" is provided by the [[GEOM]] subsystem and is referred to as ''disk striping''. The driver is available as a loadable kernel module called 'geom_striping'. In order to automatically load this driver on boot, the line '''geom_stripe_load="YES"''' needs to be added to the '''/boot/loader.conf''' file. We can avoid having to actually reboot the system now by loading the driver manually, however.<br />
<br />
server# '''kldload geom_stripe'''<br />
<br />
There needs to be a [[mount]] point for this RAID drive. Because this RAID drive is intended to be used with Samba it will be called '/smb' and created as follows.<br />
<br />
server# '''mkdir /smb'''<br />
<br />
In order to establish the RAID0 drive the underlying drives need to be determined. Here we'll use [[grep]] with a [[regexp]] expression to find all kernel messages that begin with 'ad0:' through 'ad9:'. (For SCSI drives we would have used 'da' instead.) This will show us the drives the kernel detected the last time it was booted.<br />
<br />
server# '''dmesg | grep -e "ad[0-9]:"'''<br />
ad0: 29325MB <Maxtor 6E030L0 NAR61590> at ata0-master UDMA133<br />
ad4: 476940MB <Seagate ST3500630AS 3.AAK> at ata2-master SATA150<br />
ad6: 476940MB <Seagate ST3500630AS 3.AAK> at ata3-master SATA150<br />
<br />
This reveals that the drives intended for use as part of the RAID0 setup - the two Seagate drives - have been allocated 'ad4' and 'ad6'. The operating system drive, the Maxtor, is allocated 'ad0'.<br />
<br />
To create the RAID0 drive using the two drives determined above the [[gstripe]] command is used as follows.<br />
<br />
server# '''gstripe label -v st0 /dev/ad4 /dev/ad6'''<br />
Metadata value stored on /dev/ad4.<br />
Metadata value stored on /dev/ad6.<br />
Done.<br />
<br />
This created a RAID0 drive called '''st0''', which is a virtual device the system treats in much the same way as the physical drives found under '''ad4''' and '''ad6'''. The use of '''-v''' instructed the '''gstripe''' command to be more verbose - without that argument, it would have returned us to the prompt completely silently.<br />
<br />
Piping [[dmesg]] through [[grep]] again will reveal more details of what was actually done.<br />
<br />
server# '''dmesg | grep GEOM_STRIPE'''<br />
GEOM_STRIPE: Device st0 created (id=2925520033).<br />
GEOM_STRIPE: Disk ad4 attached to st0.<br />
GEOM_STRIPE: Disk ad6 attached to st0.<br />
GEOM_STRIPE: Device st0 activated.<br />
<br />
The new RAID0 drive is located under '''/dev/stripe/st0'''.<br />
<br />
Before FreeBSD can utilise a drive, whether it is a regular single drive or a [[RAID]] array, it must be initialised and marked as an available drive. This is done by writing a marker to the drive. Under FreeBSD this is done by using the '[[bsdlabel]]' command.<br />
<br />
server# '''bsdlabel -w /dev/stripe/st0'''<br />
<br />
This simply writes to the new virtual device that hosts the RAID0 drive enabling FreeBSD to reference it as an available drive. As a result of this command executing the virtual device shows a single [[slice]] (or "partition" under Microsoft speak) under '''/dev/stripe/st0a'''.<br />
<br />
To allow data to be written to the RAID0 drive it must be formatted. FreeBSD has a native file system called [[UFS2]] but is also capable of reading and writing to file systems of other operating systems. These "foreign" file systems include Microsoft's variations of the FAT system (called 'MSDOS' on FreeBSD). Since Samba will be running locally on this system the file system will be the native UFS2 and is created using the following command.<br />
<br />
server# '''newfs -U /dev/stripe/st0'''<br />
<br />
The "-U" instructs newfs to enable [[soft updates]] on the file system as it is formatted. The command will fill the screen with output similar to the following.<br />
<br />
/dev/stripe/st0a: 953880.0MB (1953546304 sectors) block size 16384, fragment size 2048<br />
using 5191 cylinder groups of 183.77MB, 11761 blks, 23552 inodes.<br />
with soft updates<br />
super-block backups (for fsck -b #) at:<br />
160, 376512, 752864, 1129216, 1505568, 1881920, 2258272, 2634624, 3010976, 3387328, 3763680, 4140032, 4516384, 4892736, 5269088, 5645440, 6021792, 6398144, <br />
6774496, 7150848, 7527200, 7903552, 8279904, 8656256, 9032608, 9408960, 9785312, 10161664, 10538016, 10914368, 11290720, 11667072, 12043424, 12419776, <br />
12796128, 13172480, 13548832, 13925184, 14301536, 14677888, 15054240, 15430592, 15806944, 16183296, 16559648, 16936000, 17312352, 17688704, 18065056, 18441408, <br />
18817760, 19194112, 19570464, 19946816, 20323168, 20699520, 21075872, 21452224, 21828576, 22204928, 22581280, 22957632, 23333984, 23710336, 24086688, 24463040, <br />
24839392, 25215744, 25592096, 25968448, 26344800, (and on and on...), 1944610944, 1944987296, 1945363648, 1945740000, 1946116352, 1946492704, 1946869056,<br />
1947245408, 1947621760, 1947998112, 1948374464, 1948750816, 1949127168, 1949503520, 1949879872, 1950256224, 1950632576, 1951008928, 1951385280, 1951761632,<br />
1952137984, 1952514336, 1952890688, 1953267040<br />
<br />
The 'newfs' command has many more options available, including one to specify the size of the drive to format meaning it is possible to create more then one 'slice' (again, akin to "partition") on it. Since no such option was specified the entire drive is formatted as one single slice. This resulted in the creation of almost 1TB of storage using the two 500GB drives.<br />
<br />
The final stage in which to permit FreeBSD to access this drive, and from there allow Samba to read and write via network file shares, is to actually mount it. In order to do this the RAID0 drive needs adding as a mountable drive to the '/etc/fstab' file. The following example taken from the above system shows, on the last line, the entry required in particular.<br />
<br />
# Device Mountpoint FStype Options Dump Pass#<br />
/dev/ad0s1b none swap sw 0 0<br />
/dev/ad0s1a / ufs rw 1 1<br />
/dev/ad0s1e /tmp ufs rw 2 2<br />
/dev/ad0s1f /usr ufs rw 2 2<br />
/dev/ad0s1d /var ufs rw 2 2<br />
/dev/acd0 /cdrom cd9660 ro,noauto 0 0<br />
/dev/stripe/st0a /smb ufs rw 2 2<br />
<br />
After a reboot the drive will be mounted as '/smb' however issuing the following command will save a reboot at this stage.<br />
<br />
server# '''mount /dev/stripe/st0a /smb'''<br />
<br />
This will allow you to use the RAID0 drive much like any other drive on the system. The drive can be verified and the free space determined by using the [[df]] command.<br />
<br />
server# '''df -h /smb'''<br />
<br />
The "-h", somewhat strangely, shows free space in Gigabytes (where-as "-k" and "-m" are logically Kilobytes and Megabytes, respectively).<br />
<br />
== Removing RAID0 ==<br />
<br />
While the drives can simply be removed and thereby remove the RAID0 drive the system will very likely become unstable. The following explains the cleaner way to remove a RAID0 drive from a running system.<br />
<br />
Removing the RAID0 configuration will result in loss of all data. '''Ensure all essential data is backed up prior to doing the following.'''<br />
<br />
Ensure any and all services that might use the drive are either stopped or configured to no longer have a dependency to the drive.<br />
<br />
Remove the drives entry from '/etc/fstab' (see above with regards to how it was added) and [[unmount]] the drive from its mount point.<br />
<br />
Using the [[gstripe]] command inform the GEOM driver to unload the RAID0 drive.<br />
<br />
server# '''gstripe unload /dev/stripe/st0a'''<br />
<br />
To ensure the underlying drives of the RAID0 set can be used for other purposes it is recommended the metadata (data used by GEOM, stored on the last sector of each drive, describing the setup in use) is cleared.<br />
<br />
server# '''gstripe clear -v /dev/ad4'''<br />
server# '''gstripe clear -v /dev/ad6'''<br />
<br />
The 'da4' and 'da6' being the drives used in the above example.<br />
<br />
Issuing these commands will result in the following from [[dmesg]], confirming the removal of RAID0 was successful.<br />
<br />
GEOM_STRIPE: Disk '''ad4''' removed from st0.<br />
GEOM_STRIPE: Device st0 removed.<br />
GEOM_STRIPE: Disk '''ad6''' removed from st0.<br />
GEOM_STRIPE: Device st0 destroyed.<br />
<br />
[[Category: Common Tasks]] [[Category: FreeBSD for Servers]]</div>DrModifordhttp://freebsdwiki.net/index.php/MySQL,_tipsMySQL, tips2008-09-24T11:41:23Z<p>DrModiford: Added tip about moving MySQL databases from the /var volume</p>
<hr />
<div>This article will be devoted to tips that will either enhance or tune MySQL for better performance.<br />
<br />
==Optimize MySQL tables==<br />
<br />
MySQL tables can grow large and cumbersome, and similar to defragging a hard drive to get optimal space, you can run<br />
# mysqlcheck -u <username> -p -o <database><br />
(enter password)<br />
to achieve a similar effect on your database. This is especially important and useful when you've changed a large database (e.g., deleted a lot of stuff from it.)<br />
<br />
== Larger Databases ==<br />
<br />
The default installation of MySQL will use the '/var' volume (or [[mount]] point) to store the database files on FreeBSD systems. This volume is typically used to store system log files and as such is typically allocated a small portion of the available disk space, particularly since logs are rotated and removed as part of the system maintenance processes. This poses a great limitation if a MySQL database is to grow beyond the available space on that volume. Fortunately it is possible to utilise another mount point with greater storage space with which MySQL can utilise as a database store. This is done using the following method:<br />
<br />
# /usr/local/etc/rc.d/mysql-server stop<br />
# cd /var/db<br />
# mv mysql /svr<br />
# ln -s /svr/mysql mysql<br />
<br />
(thanks to [http://www.freebsddiary.org/mysql.php The FreeBSD Diary] for this tip)<br />
<br />
This has the effect of moving the physical 'mysql' database store from the default '/var' volume to the larger '/svr' volume and then creates a symbolic link to the original location. This 'trick' allows MySQL to function without needing to re-configure all of its data store locations individually. This is greatly beneficial to systems with lots of databases.<br />
<br />
For more information on the concepts of symbolic links used in this method, review [[ln|this article]].<br />
<br />
==Play nice with others==<br />
<br />
If you're running a server that does a lot of heavy MySQL lifting, it makes sense that MySQL should run as fast as possible. An easy way to give MySQL priority is to re-[[nice]] it to a lower value. Go through the ''safe_mysqld'' script in your MySQL directory and add a line like<br />
renice -10 $$ <br />
to it. You may find it necessary to comment out the section that starts with NOHUP_NICENESS and any [[if]]/[[fi]] loops in it. Note that if you set the [[nice]] value too low, the rest of the system's performance can be affected. For this reason, it's usually best not to go below -10 or -15; between -5 and -10 should be a pretty safe spot.<br />
<br />
See also: [[MySQL]]<br />
[[Category:Common Tasks]]</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_XenServerInstallation on XenServer2008-09-23T09:34:38Z<p>DrModiford: Corrected link</p>
<hr />
<div>The following guide covers the base installation of FreeBSD on the [[XenServer]] virtual server system from Citrix. This should also be suitable for the open-source [[Xen]] platform. The installation is similar to an installation of FreeBSD on regular x86 systems. The following covers the specifics of the XenServer system installation.<br />
<br />
== Pre-requisites ==<br />
<br />
The following assumes that an installation of XenServer has been completed on a server featuring compatible hardware-assisted virtualisation processors from AMD or Intel. Citrix, the company behind XenServer, offer a free but functionality-restricted version called 'XenServer Express'. These restrictions are just limitations on the number of virtual guests that can be run at once (currently limited to four) and the amount of memory accessible by the guest operating systems and others (see the [http://www.citrix.com Citrix] website for further details). There are commercial licenses available from Citrix that remove these restrictions and offer enhanced usability features.<br />
<br />
The open-source version of XenServer, called Xen, is available under the [[GPL]] and features none of the above restrictions on use. However it is an open-source release and as such requires the ability to install a Xen system from source-code or binary packages within a special [[Linux]] kernel.<br />
<br />
There is no specific Xen-based release of FreeBSD, instead the installation media for [[FreeBSD Platforms|AMD64]] must be downloaded (or purchased through one of the affiliated on-line stores). The standard [[FreeBSD Platforms|i386]] release might also work but the underlying Xen virtualisation is 64-bit based. If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the XenServer 'creates' a virtual machine within which to run an operating system (a kind of guest-space within the host server) the creation of such virtual machines is done via a wizard. As of writing there is no official FreeBSD specific guest template available during the wizard stage, instead the 'Other install media' must be selected. This involves specifying the required number of (virtual) CPUs, RAM, hard drive space and network interfaces manually - the templates simply define defaults for known guest operating systems.<br />
<br />
== Booting FreeBSD ==<br />
<br />
Booting FreeBSD within a XenServer host is much the same as an installation on commodity PC hardware. The XenServer guest is viewable through the XenCenter console and keyboard and mouse interaction is passed from the desktop machine through to it.<br />
<br />
== FreeBSD on XenServer specific issues ==<br />
<br />
The following lists some variations to the typical x86-based installation.<br />
<br />
=== Networking ===<br />
<br />
The '''Network interface information required''' page will list the available (recognised) Ethernet cards installed. The virtualised network card(s) provided by the XenServer host appear as physical network devices to the FreeBSD operating system. They are detected by the '''RealTec 8139C+/8169/8169S/8110S PCI Ethernet card''' driver.<br />
<br />
FreeBSD refers to the above driver using the interface name ''re0'' for the first detected card and ''re1'', ''re2'', etc. for subsequent (virtualised) network devices.<br />
<br />
=== Sound ===<br />
<br />
The XenServer host does not present an audio device to the guest operating system. Therefore no sound support is available.<br />
<br />
=== Video ===<br />
<br />
The XenServer host presents the video card as a virtual Cirrus Logic based 5446 display controller chip. Despite being an old graphics card by modern standards it is widely compatible with many operating systems since they typically ship with suitable drivers. Where no drivers exist it can be utilised as a generic VGA / SVGA display.<br />
<br />
FreeBSD, through the [[X.Org]] (and [[XFree86]]) subsystem, has a driver that supports the Cirrus Logic chips allowing the use of a graphical desktop such as [[KDE]], [[Gnome]] and others.<br />
<br />
== Settings used ==<br />
<br />
During the installation on a XenServer system the following choices were used.<br />
<br />
The hard drive was split up into the following [[slices]]:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
! Part<br />
! Mount<br />
! Size<br />
! NewFS<br />
|-<br />
| ad0a<br />
| /<br />
| 512MB<br />
| UFS2 Y<br />
|-<br />
| ad0b<br />
| <br />
| 1024MB<br />
| SWAP<br />
|-<br />
| ad0d<br />
| /var<br />
| 1024MB<br />
| UFS2+s Y<br />
|-<br />
| ad0e<br />
| /tmp<br />
| 512MB<br />
| UFS2+S Y<br />
|-<br />
| ad0f<br />
| /usr<br />
| 32768MB<br />
| UFS2+S Y<br />
|-<br />
| ad0g<br />
| /svr<br />
| 114GB<br />
| UFS2+S Y<br />
|-<br />
|}<br />
<br />
The 'SWAP' is set to 2x the on-board RAM size (a FreeBSD system recommendation). The '/usr' splice is 32GB, but shown as 32768MB on the screen. The '/svr' slice used the remainder of the disk, which happened to be 114GB of the 160GB (give-or-take) capacity and exists as a place to host the 'server' specific data instead of the default '/usr' locations used by [[Apache]] and others.<br />
<br />
== See also ==<br />
<br />
The [[XenServer]] article and details of other FreeBSD [[FreeBSD Platforms|architectures]].<br />
<br />
[[Category : Installation]]</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_XenServerInstallation on XenServer2008-09-23T09:34:09Z<p>DrModiford: Formatting</p>
<hr />
<div>The following guide covers the base installation of FreeBSD on the [[XenServer]] virtual server system from Citrix. This should also be suitable for the open-source [[Xen]] platform. The installation is similar to an installation of FreeBSD on regular x86 systems. The following covers the specifics of the XenServer system installation.<br />
<br />
== Pre-requisites ==<br />
<br />
The following assumes that an installation of XenServer has been completed on a server featuring compatible hardware-assisted virtualisation processors from AMD or Intel. Citrix, the company behind XenServer, offer a free but functionality-restricted version called 'XenServer Express'. These restrictions are just limitations on the number of virtual guests that can be run at once (currently limited to four) and the amount of memory accessible by the guest operating systems and others (see the [http://www.citrix.com Citrix] website for further details). There are commercial licenses available from Citrix that remove these restrictions and offer enhanced usability features.<br />
<br />
The open-source version of XenServer, called Xen, is available under the [[GPL]] and features none of the above restrictions on use. However it is an open-source release and as such requires the ability to install a Xen system from source-code or binary packages within a special [[Linux]] kernel.<br />
<br />
There is no specific Xen-based release of FreeBSD, instead the installation media for [[FreeBSD Platforms|AMD64]] must be downloaded (or purchased through one of the affiliated on-line stores). The standard [[FreeBSD Platforms|i386]] release might also work but the underlying Xen virtualisation is 64-bit based. If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the XenServer 'creates' a virtual machine within which to run an operating system (a kind of guest-space within the host server) the creation of such virtual machines is done via a wizard. As of writing there is no official FreeBSD specific guest template available during the wizard stage, instead the 'Other install media' must be selected. This involves specifying the required number of (virtual) CPUs, RAM, hard drive space and network interfaces manually - the templates simply define defaults for known guest operating systems.<br />
<br />
== Booting FreeBSD ==<br />
<br />
Booting FreeBSD within a XenServer host is much the same as an installation on commodity PC hardware. The XenServer guest is viewable through the XenCenter console and keyboard and mouse interaction is passed from the desktop machine through to it.<br />
<br />
== FreeBSD on XenServer specific issues ==<br />
<br />
The following lists some variations to the typical x86-based installation.<br />
<br />
=== Networking ===<br />
<br />
The '''Network interface information required''' page will list the available (recognised) Ethernet cards installed. The virtualised network card(s) provided by the XenServer host appear as physical network devices to the FreeBSD operating system. They are detected by the '''RealTec 8139C+/8169/8169S/8110S PCI Ethernet card''' driver.<br />
<br />
FreeBSD refers to the above driver using the interface name ''re0'' for the first detected card and ''re1'', ''re2'', etc. for subsequent (virtualised) network devices.<br />
<br />
=== Sound ===<br />
<br />
The XenServer host does not present an audio device to the guest operating system. Therefore no sound support is available.<br />
<br />
=== Video ===<br />
<br />
The XenServer host presents the video card as a virtual Cirrus Logic based 5446 display controller chip. Despite being an old graphics card by modern standards it is widely compatible with many operating systems since they typically ship with suitable drivers. Where no drivers exist it can be utilised as a generic VGA / SVGA display.<br />
<br />
FreeBSD, through the [[X.Org]] (and [[XFree86]]) subsystem, has a driver that supports the Cirrus Logic chips allowing the use of a graphical desktop such as [[KDE]], [[Gnome]] and others.<br />
<br />
== Settings used ==<br />
<br />
During the installation on a XenServer system the following choices were used.<br />
<br />
The hard drive was split up into the following [[slices]]:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
! Part<br />
! Mount<br />
! Size<br />
! NewFS<br />
|-<br />
| ad0a<br />
| /<br />
| 512MB<br />
| UFS2 Y<br />
|-<br />
| ad0b<br />
| <br />
| 1024MB<br />
| SWAP<br />
|-<br />
| ad0d<br />
| /var<br />
| 1024MB<br />
| UFS2+s Y<br />
|-<br />
| ad0e<br />
| /tmp<br />
| 512MB<br />
| UFS2+S Y<br />
|-<br />
| ad0f<br />
| /usr<br />
| 32768MB<br />
| UFS2+S Y<br />
|-<br />
| ad0g<br />
| /svr<br />
| 114GB<br />
| UFS2+S Y<br />
|-<br />
|}<br />
<br />
The 'SWAP' is set to 2x the on-board RAM size (a FreeBSD system recommendation). The '/usr' splice is 32GB, but shown as 32768MB on the screen. The '/svr' slice used the remainder of the disk, which happened to be 114GB of the 160GB (give-or-take) capacity and exists as a place to host the 'server' specific data instead of the default '/usr' locations used by [[Apache]] and others.<br />
<br />
== See also ==<br />
<br />
The [[XenServer]] article and details of other FreeBSD [[Platforms|architectures]].<br />
<br />
[[Category : Installation]]</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_XenServerInstallation on XenServer2008-09-23T09:33:16Z<p>DrModiford: Corrected link</p>
<hr />
<div>The following guide covers the base installation of FreeBSD on the [[XenServer]] virtual server system from Citrix. This should also be suitable for the open-source [[Xen]] platform. The installation is similar to an installation of FreeBSD on regular x86 systems. The following covers the specifics of the XenServer system installation.<br />
<br />
== Pre-requisites ==<br />
<br />
The following assumes that an installation of XenServer has been completed on a server featuring compatible hardware-assisted virtualisation processors from AMD or Intel. Citrix, the company behind XenServer, offer a free but functionality-restricted version called 'XenServer Express'. These restrictions are just limitations on the number of virtual guests that can be run at once (currently limited to four) and the amount of memory accessible by the guest operating systems and others (see the [http://www.citrix.com Citrix] website for further details). There are commercial licenses available from Citrix that remove these restrictions and offer enhanced usability features.<br />
<br />
The open-source version of XenServer, called Xen, is available under the [[GPL]] and features none of the above restrictions on use. However it is an open-source release and as such requires the ability to install a Xen system from source-code or binary packages within a special [[Linux]] kernel.<br />
<br />
There is no specific Xen-based release of FreeBSD, instead the installation media for [[FreeBSD Platforms|AMD64]] must be downloaded (or purchased through one of the affiliated on-line stores). The standard [[FreeBSD Platforms|i386]] release might also work but the underlying Xen virtualisation is 64-bit based. If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the XenServer 'creates' a virtual machine within which to run an operating system (a kind of guest-space within the host server) the creation of such virtual machines is done via a wizard. As of writing there is no official FreeBSD specific guest template available during the wizard stage, instead the 'Other install media' must be selected. This involves specifying the required number of (virtual) CPUs, RAM, hard drive space and network interfaces manually - the templates simply define defaults for known guest operating systems.<br />
<br />
== Booting FreeBSD ==<br />
<br />
Booting FreeBSD within a XenServer host is much the same as an installation on commodity PC hardware. The XenServer guest is viewable through the XenCenter console and keyboard and mouse interaction is passed from the desktop machine through to it.<br />
<br />
== FreeBSD on XenServer specific issues ==<br />
<br />
The following lists some variations to the typical x86-based installation.<br />
<br />
=== Networking ===<br />
<br />
The '''Network interface information required''' page will list the available (recognised) Ethernet cards installed. The virtualised network card(s) provided by the XenServer host appear as physical network devices to the FreeBSD operating system. They are detected by the "RealTec 8139C+/8169/8169S/8110S PCI Ethernet card" driver.<br />
<br />
FreeBSD refers to the above driver using the interface name 're0' for the first detected card and 're1', 're2', etc. for subsequent (virtualised) network devices.<br />
<br />
=== Sound ===<br />
<br />
The XenServer host does not present an audio device to the guest operating system. Therefore no sound support is available.<br />
<br />
=== Video ===<br />
<br />
The XenServer host presents the video card as a virtual Cirrus Logic based 5446 display controller chip. Despite being an old graphics card by modern standards it is widely compatible with many operating systems since they typically ship with suitable drivers. Where no drivers exist it can be utilised as a generic VGA / SVGA display.<br />
<br />
FreeBSD, through the [[X.Org]] (and [[XFree86]]) subsystem, has a driver that supports the Cirrus Logic chips allowing the use of a graphical desktop such as [[KDE]], [[Gnome]] and others.<br />
<br />
== Settings used ==<br />
<br />
During the installation on a XenServer system the following choices were used.<br />
<br />
The hard drive was split up into the following [[slices]]:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
! Part<br />
! Mount<br />
! Size<br />
! NewFS<br />
|-<br />
| ad0a<br />
| /<br />
| 512MB<br />
| UFS2 Y<br />
|-<br />
| ad0b<br />
| <br />
| 1024MB<br />
| SWAP<br />
|-<br />
| ad0d<br />
| /var<br />
| 1024MB<br />
| UFS2+s Y<br />
|-<br />
| ad0e<br />
| /tmp<br />
| 512MB<br />
| UFS2+S Y<br />
|-<br />
| ad0f<br />
| /usr<br />
| 32768MB<br />
| UFS2+S Y<br />
|-<br />
| ad0g<br />
| /svr<br />
| 114GB<br />
| UFS2+S Y<br />
|-<br />
|}<br />
<br />
The 'SWAP' is set to 2x the on-board RAM size (a FreeBSD system recommendation). The '/usr' splice is 32GB, but shown as 32768MB on the screen. The '/svr' slice used the remainder of the disk, which happened to be 114GB of the 160GB (give-or-take) capacity and exists as a place to host the 'server' specific data instead of the default '/usr' locations used by [[Apache]] and others.<br />
<br />
== See also ==<br />
<br />
The [[XenServer]] article and details of other FreeBSD [[Platforms|architectures]].<br />
<br />
[[Category : Installation]]</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_XenServerInstallation on XenServer2008-09-23T09:32:12Z<p>DrModiford: Corrections and changes</p>
<hr />
<div>The following guide covers the base installation of FreeBSD on the [[XenServer]] virtual server system from Citrix. This should also be suitable for the open-source [[Xen]] platform. The installation is similar to an installation of FreeBSD on regular x86 systems. The following covers the specifics of the XenServer system installation.<br />
<br />
== Pre-requisites ==<br />
<br />
The following assumes that an installation of XenServer has been completed on a server featuring compatible hardware-assisted virtualisation processors from AMD or Intel. Citrix, the company behind XenServer, offer a free but functionality-restricted version called 'XenServer Express'. These restrictions are just limitations on the number of virtual guests that can be run at once (currently limited to four) and the amount of memory accessible by the guest operating systems and others (see the [http://www.citrix.com Citrix] website for further details). There are commercial licenses available from Citrix that remove these restrictions and offer enhanced usability features.<br />
<br />
The open-source version of XenServer, called Xen, is available under the [[GPL]] and features none of the above restrictions on use. However it is an open-source release and as such requires the ability to install a Xen system from source-code or binary packages within a special [[Linux]] kernel.<br />
<br />
There is no specific Xen-based release of FreeBSD, instead the installation media for [[platforms|AMD64]] must be downloaded (or purchased through one of the affiliated on-line stores). The standard [[platforms|i386]] release might also work but the underlying Xen virtualisation is 64-bit based. If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the XenServer 'creates' a virtual machine within which to run an operating system (a kind of guest-space within the host server) the creation of such virtual machines is done via a wizard. As of writing there is no official FreeBSD specific guest template available during the wizard stage, instead the 'Other install media' must be selected. This involves specifying the required number of (virtual) CPUs, RAM, hard drive space and network interfaces manually - the templates simply define defaults for known guest operating systems.<br />
<br />
== Booting FreeBSD ==<br />
<br />
Booting FreeBSD within a XenServer host is much the same as an installation on commodity PC hardware. The XenServer guest is viewable through the XenCenter console and keyboard and mouse interaction is passed from the desktop machine through to it.<br />
<br />
== FreeBSD on XenServer specific issues ==<br />
<br />
The following lists some variations to the typical x86-based installation.<br />
<br />
=== Networking ===<br />
<br />
The '''Network interface information required''' page will list the available (recognised) Ethernet cards installed. The virtualised network card(s) provided by the XenServer host appear as physical network devices to the FreeBSD operating system. They are detected by the "RealTec 8139C+/8169/8169S/8110S PCI Ethernet card" driver.<br />
<br />
FreeBSD refers to the above driver using the interface name 're0' for the first detected card and 're1', 're2', etc. for subsequent (virtualised) network devices.<br />
<br />
=== Sound ===<br />
<br />
The XenServer host does not present an audio device to the guest operating system. Therefore no sound support is available.<br />
<br />
=== Video ===<br />
<br />
The XenServer host presents the video card as a virtual Cirrus Logic based 5446 display controller chip. Despite being an old graphics card by modern standards it is widely compatible with many operating systems since they typically ship with suitable drivers. Where no drivers exist it can be utilised as a generic VGA / SVGA display.<br />
<br />
FreeBSD, through the [[X.Org]] (and [[XFree86]]) subsystem, has a driver that supports the Cirrus Logic chips allowing the use of a graphical desktop such as [[KDE]], [[Gnome]] and others.<br />
<br />
== Settings used ==<br />
<br />
During the installation on a XenServer system the following choices were used.<br />
<br />
The hard drive was split up into the following [[slices]]:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
! Part<br />
! Mount<br />
! Size<br />
! NewFS<br />
|-<br />
| ad0a<br />
| /<br />
| 512MB<br />
| UFS2 Y<br />
|-<br />
| ad0b<br />
| <br />
| 1024MB<br />
| SWAP<br />
|-<br />
| ad0d<br />
| /var<br />
| 1024MB<br />
| UFS2+s Y<br />
|-<br />
| ad0e<br />
| /tmp<br />
| 512MB<br />
| UFS2+S Y<br />
|-<br />
| ad0f<br />
| /usr<br />
| 32768MB<br />
| UFS2+S Y<br />
|-<br />
| ad0g<br />
| /svr<br />
| 114GB<br />
| UFS2+S Y<br />
|-<br />
|}<br />
<br />
The 'SWAP' is set to 2x the on-board RAM size (a FreeBSD system recommendation). The '/usr' splice is 32GB, but shown as 32768MB on the screen. The '/svr' slice used the remainder of the disk, which happened to be 114GB of the 160GB (give-or-take) capacity and exists as a place to host the 'server' specific data instead of the default '/usr' locations used by [[Apache]] and others.<br />
<br />
== See also ==<br />
<br />
The [[XenServer]] article and details of other FreeBSD [[Platforms|architectures]].<br />
<br />
[[Category : Installation]]</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_XenServerInstallation on XenServer2008-09-23T09:24:37Z<p>DrModiford: Installation on Xen moved to Installation on XenServer: Was Installation on Xen, should have read Installation on XenServer</p>
<hr />
<div>The following guide covers the base installation of FreeBSD on the [[XenServer]] virtual server system from Citrix. This should also be suitable for the open-source [[Xen]] platform. The installation is similar to an installation of FreeBSD on regular x86 systems. The following covers the specifics of the XenServer system installation.<br />
<br />
== Pre-requisites ==<br />
<br />
The following assumes that an installation of XenServer has been completed on a server featuring compatible hardware-assisted virtualisation processors from AMD or Intel. Citrix offer a fully-free version of XenServer called the 'Express' release with a few limitations on it such as the number of virtual guests that can run within it (currently 4) and the memory accessible by them (see the [http://www.citrix.com Citrix] website for further details).<br />
<br />
There is no specific Xen-based release of FreeBSD, instead the installation media for [[platforms|AMD64]] must be downloaded (or purchased through one of the affiliated on-line stores). The standard [[platforms|i386]] release might also work but the underlying Xen virtualisation in 64-bit based. If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the XenServer 'creates' a virtual machine within which to run an operating system (a kind of guest-space within the host server) the creation of such virtual machines is done via a wizard. As of writing there is no official FreeBSD specific guest template available during the wizard stage, instead the 'Other install media' must be selected. This involves specifying the required number of (virtual) CPUs, RAM, hard drive space and network interfaces manually - the templates simply define defaults for known guest operating systems.<br />
<br />
== Booting FreeBSD ==<br />
<br />
Booting FreeBSD within a XenServer host is much the same as an installation on commodity PC hardware. The XenServer guest is viewable through the XenCenter console and keyboard and mouse interaction is passed from the desktop machine through to it.<br />
<br />
== FreeBSD on XenServer specific issues ==<br />
<br />
The following lists some variations to the typical x86-based installation.<br />
<br />
=== Networking ===<br />
<br />
The '''Network interface information required''' page will list the available (recognised) Ethernet cards installed. The virtualised network card(s) provided by the XenServer host appear as physical network devices to the FreeBSD operating system. They are detected by the "RealTec 8139C+/8169/8169S/8110S PCI Ethernet card" driver.<br />
<br />
FreeBSD refers to the above driver using the interface name 're0' for the first detected card and 're1', 're2', etc. for subsequent (virtualised) network devices.<br />
<br />
=== Sound ===<br />
<br />
The XenServer host does not present an audio device to the guest operating system. Therefore no sound support is available.<br />
<br />
=== Video ===<br />
<br />
The XenServer host presents the video card as a virtual Cirrus Logic based 5446 display controller chip. Despite being an old graphics card by modern standards it is widely compatible with many operating systems since they typically ship with suitable drivers. Where no drivers exist it can be utilised as a generic VGA / SVGA display.<br />
<br />
FreeBSD, through the [[X.Org]] (and [[XFree86]]) subsystem, has a driver that supports the Cirrus Logic chips allowing the use of a graphical desktop such as [[KDE]], [[Gnome]] and others.<br />
<br />
== Settings used ==<br />
<br />
During the installation on a XenServer system the following choices were used.<br />
<br />
The hard drive was split up into the following [[slices]]:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
! Part<br />
! Mount<br />
! Size<br />
! NewFS<br />
|-<br />
| ad0a<br />
| /<br />
| 512MB<br />
| UFS2 Y<br />
|-<br />
| ad0b<br />
| <br />
| 1024MB<br />
| SWAP<br />
|-<br />
| ad0d<br />
| /var<br />
| 1024MB<br />
| UFS2+s Y<br />
|-<br />
| ad0e<br />
| /tmp<br />
| 512MB<br />
| UFS2+S Y<br />
|-<br />
| ad0f<br />
| /usr<br />
| 32768MB<br />
| UFS2+S Y<br />
|-<br />
| ad0g<br />
| /svr<br />
| 114GB<br />
| UFS2+S Y<br />
|-<br />
|}<br />
<br />
The 'SWAP' is set to 2x the on-board RAM size (a FreeBSD system recommendation). The '/usr' splice is 32GB, but shown as 32768MB on the screen. The '/svr' slice used the remainder of the disk, which happened to be 114GB of the 160GB (give-or-take) capacity and exists as a place to host the 'server' specific data instead of the default '/usr' locations used by [[Apache]] and others.<br />
<br />
== See also ==<br />
<br />
The [[XenServer]] article and details of other FreeBSD [[Platforms|architectures]].<br />
<br />
[[Category : Installation]]</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_XenInstallation on Xen2008-09-23T09:24:37Z<p>DrModiford: Installation on Xen moved to Installation on XenServer: Was Installation on Xen, should have read Installation on XenServer</p>
<hr />
<div>#REDIRECT [[Installation on XenServer]]</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_XenServerInstallation on XenServer2008-09-23T09:24:03Z<p>DrModiford: Created XenServer specific install guide (covering the differences to a normal x86 style install)</p>
<hr />
<div>The following guide covers the base installation of FreeBSD on the [[XenServer]] virtual server system from Citrix. This should also be suitable for the open-source [[Xen]] platform. The installation is similar to an installation of FreeBSD on regular x86 systems. The following covers the specifics of the XenServer system installation.<br />
<br />
== Pre-requisites ==<br />
<br />
The following assumes that an installation of XenServer has been completed on a server featuring compatible hardware-assisted virtualisation processors from AMD or Intel. Citrix offer a fully-free version of XenServer called the 'Express' release with a few limitations on it such as the number of virtual guests that can run within it (currently 4) and the memory accessible by them (see the [http://www.citrix.com Citrix] website for further details).<br />
<br />
There is no specific Xen-based release of FreeBSD, instead the installation media for [[platforms|AMD64]] must be downloaded (or purchased through one of the affiliated on-line stores). The standard [[platforms|i386]] release might also work but the underlying Xen virtualisation in 64-bit based. If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the XenServer 'creates' a virtual machine within which to run an operating system (a kind of guest-space within the host server) the creation of such virtual machines is done via a wizard. As of writing there is no official FreeBSD specific guest template available during the wizard stage, instead the 'Other install media' must be selected. This involves specifying the required number of (virtual) CPUs, RAM, hard drive space and network interfaces manually - the templates simply define defaults for known guest operating systems.<br />
<br />
== Booting FreeBSD ==<br />
<br />
Booting FreeBSD within a XenServer host is much the same as an installation on commodity PC hardware. The XenServer guest is viewable through the XenCenter console and keyboard and mouse interaction is passed from the desktop machine through to it.<br />
<br />
== FreeBSD on XenServer specific issues ==<br />
<br />
The following lists some variations to the typical x86-based installation.<br />
<br />
=== Networking ===<br />
<br />
The '''Network interface information required''' page will list the available (recognised) Ethernet cards installed. The virtualised network card(s) provided by the XenServer host appear as physical network devices to the FreeBSD operating system. They are detected by the "RealTec 8139C+/8169/8169S/8110S PCI Ethernet card" driver.<br />
<br />
FreeBSD refers to the above driver using the interface name 're0' for the first detected card and 're1', 're2', etc. for subsequent (virtualised) network devices.<br />
<br />
=== Sound ===<br />
<br />
The XenServer host does not present an audio device to the guest operating system. Therefore no sound support is available.<br />
<br />
=== Video ===<br />
<br />
The XenServer host presents the video card as a virtual Cirrus Logic based 5446 display controller chip. Despite being an old graphics card by modern standards it is widely compatible with many operating systems since they typically ship with suitable drivers. Where no drivers exist it can be utilised as a generic VGA / SVGA display.<br />
<br />
FreeBSD, through the [[X.Org]] (and [[XFree86]]) subsystem, has a driver that supports the Cirrus Logic chips allowing the use of a graphical desktop such as [[KDE]], [[Gnome]] and others.<br />
<br />
== Settings used ==<br />
<br />
During the installation on a XenServer system the following choices were used.<br />
<br />
The hard drive was split up into the following [[slices]]:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
! Part<br />
! Mount<br />
! Size<br />
! NewFS<br />
|-<br />
| ad0a<br />
| /<br />
| 512MB<br />
| UFS2 Y<br />
|-<br />
| ad0b<br />
| <br />
| 1024MB<br />
| SWAP<br />
|-<br />
| ad0d<br />
| /var<br />
| 1024MB<br />
| UFS2+s Y<br />
|-<br />
| ad0e<br />
| /tmp<br />
| 512MB<br />
| UFS2+S Y<br />
|-<br />
| ad0f<br />
| /usr<br />
| 32768MB<br />
| UFS2+S Y<br />
|-<br />
| ad0g<br />
| /svr<br />
| 114GB<br />
| UFS2+S Y<br />
|-<br />
|}<br />
<br />
The 'SWAP' is set to 2x the on-board RAM size (a FreeBSD system recommendation). The '/usr' splice is 32GB, but shown as 32768MB on the screen. The '/svr' slice used the remainder of the disk, which happened to be 114GB of the 160GB (give-or-take) capacity and exists as a place to host the 'server' specific data instead of the default '/usr' locations used by [[Apache]] and others.<br />
<br />
== See also ==<br />
<br />
The [[XenServer]] article and details of other FreeBSD [[Platforms|architectures]].<br />
<br />
[[Category : Installation]]</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_Ultra_5Installation on Ultra 52008-09-23T08:23:16Z<p>DrModiford: Added link to other article</p>
<hr />
<div>The following guide covers the base installation of FreeBSD on the [[Sun Microsystems Hardware|Sun Microsystems]]' Ultra 5 platform. This should also be suitable for the Ultra 10 platform, a faster and improved variant of the Ultra 5. The installation is similar to an installation of FreeBSD on regular x86 systems. The following covers the specifics of the Ultra 5 system installation.<br />
<br />
== Pre-requisites ==<br />
<br />
The specific SPARC-based installation media must be downloaded (or purchased through one of the affiliated on-line stores) - the x86-based installation media will not work! If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the Ultra 5 uses the [[OpenBoot]] system to initiate system start-up, the equivalent of the ubiquitous PC BIOS, accessing it is different to what you may be used to coming from the PC world. Upon starting up and viewing the white boot screen (featuring the Sun classic logo and various system details) the key combination 'Stop' and the letter 'A' must be pressed together. This results in a prompt that simply states: "ok".<br />
<br />
This allows commands to be typed that control the system's start-up. For example, typing "probe-ide" and pressing enter will reveal the devices attached to the IDE ports. Typically one hard drive and a CD-ROM will be revealed though that is dependant on the installed hardware.<br />
<br />
== Initiating the FreeBSD installer ==<br />
<br />
With the OpenBoot system in command mode (see above how to interrupt system start-up) and the FreeBSD for SPARC installation cd-rom in the drive, type the following command to begin the process:<br />
<br />
ok '''boot cdrom /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== Installing FreeBSD ==<br />
<br />
After a short while with lots of information scrolling across the screen the familiar '''Country Selection''' page appears. From this point the installation becomes the same as an x86-based installation.<br />
<br />
Please refer to [[Installing FreeBSD - Standard Installation|this guide]] for continued installation instructions.<br />
<br />
== Booting FreeBSD ==<br />
<br />
Following a successful installation the system will reboot and attempt to load an operating system. If the system fails to load type the following command to begin the process:<br />
<br />
ok '''boot disk /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
If the server fails to start upon reboot, requiring the above command to be run manually each time, the following commands should be issued on the OpenBoot screen:<br />
<br />
ok '''setenv boot-device disk''' (press Enter)<br />
ok '''setenv boot-file /boot/loader''' (press Enter)<br />
ok '''nvstore''' (press Enter)<br />
<br />
These commands will set the environment variables 'boot-device' and 'boot-file' with the appropriate values for FreeBSD's boot loader and then commit the values to the system's non-volatile memory (similar to Save Settings in a conventional PC BIOS).<br />
<br />
Either reboot the system or re-issue the 'boot' command above to continue loading FreeBSD.<br />
<br />
== FreeBSD on UltraSPARC specific issues ==<br />
<br />
The following lists some variations to the typical x86-based installation.<br />
<br />
=== Country Selection ===<br />
<br />
This page does not follow to the prompt for '''Code Page''' selection.<br />
<br />
=== Hard Disk Partitioning ===<br />
<br />
The various hard drive stages and boot loader options are skipped and the '''FreeBSD Disklabel Editor''' starts directly.<br />
<br />
This could be because dual-booting and co-existing with other operating systems is not possible under this architecture.<br />
<br />
=== Networking ===<br />
<br />
The '''Network interface information required''' page will list the available (recognised) Ethernet cards installed. The on-board network card is supported by the 'hme' driver, known (and listed on-screen) as the "Happy Meal Ethernet" adaptor. Other network cards, if installed and are compatible, will also be listed.<br />
<br />
Most, if not all, PCI network cards supported by the x86 release should be supported by the UltraSPARC release.<br />
<br />
=== Sound ===<br />
<br />
The Ultra 5 has on-board audio featuring line-in, line-out, microphone and speaker sockets on the rear (using conventional jacks) and a CD-audio connection internally. The audio device is based on the Crystal Sounds CS4231A and FreeBSD for Sparc64 features a driver for this chip-set.<br />
<br />
The file '/boot/loader.conf' requires the following lines added to it:<br />
<br />
'''sound_load="YES"'''<br />
'''snd_audiocs_load="YES"'''<br />
<br />
'''Note:''' this file might not exist and will need creating.<br />
<br />
The system will need rebooting for these drivers to load. It is possible to use [[kldload]] to start them without a reboot as follows:<br />
<br />
'''kldload sound''' (press Enter)<br />
'''kldload snd_audiocd''' (press Enter)<br />
<br />
The [[dmesg]] command will output a similar entry to the following after successful detection of the audio device:<br />
<br />
pcm0: <Sun Audiocs> addr 0x147...<br />
<br />
There is also an audio driver for the 'Ensoniq AudioPCI ES137x' series of chip-sets from Creative Labs. Substitute the above 'snd_audiocs' with 'snd_es137x' to utilise this audio device.<br />
<br />
== Settings used ==<br />
<br />
During the installation on a real Ultra 5 system the following choices were used.<br />
<br />
The hard drive was split up into the following [[slices]]:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
! Part<br />
! Mount<br />
! Size<br />
! NewFS<br />
|-<br />
| ad0a<br />
| /<br />
| 512MB<br />
| UFS2 Y<br />
|-<br />
| ad0b<br />
| <br />
| 1024MB<br />
| SWAP<br />
|-<br />
| ad0d<br />
| /var<br />
| 1024MB<br />
| UFS2+s Y<br />
|-<br />
| ad0e<br />
| /tmp<br />
| 512MB<br />
| UFS2+S Y<br />
|-<br />
| ad0f<br />
| /usr<br />
| 32768MB<br />
| UFS2+S Y<br />
|-<br />
| ad0g<br />
| /svr<br />
| 114GB<br />
| UFS2+S Y<br />
|-<br />
|}<br />
<br />
The 'SWAP' is set to 2x the on-board RAM size (a FreeBSD system recommendation). The '/usr' splice is 32GB, but shown as 32768MB on the screen. The '/svr' slice used the remainder of the disk, which happened to be 114GB of the 160GB (give-or-take) capacity and exists as a place to host the 'server' specific data instead of the default '/usr' locations used by [[Apache]] and others.<br />
<br />
== See also ==<br />
<br />
The [[Sparc - Installing FreeBSD]] article contains some further information regarding OpenBios and the installation of FreeBSD.<br />
<br />
For more details on configuring the OpenBoot system, see Sun Microsystem's [http://docs.sun.com/app/docs/doc/802-3242/6i75cc1kk?a=view Command Reference Manual] web page.<br />
<br />
[[Category : Installation]]</div>DrModifordhttp://freebsdwiki.net/index.php/XenXen2008-09-23T08:17:34Z<p>DrModiford: Updated XenServer information</p>
<hr />
<div>The '''xen''' system is a form of virtualisation that enables a host system to run many different operating systems. These hosted operating systems are referred to as guests and can be from different vendors and include Microsoft's Windows platforms and many [[GNU/Linux]] distributions.<br />
<br />
The Xen system was bought by Citrix and is sold under the [http://citrix.com/English/ps2/products/product.asp?contentID=683148 XenServer] brand name. The open source code remains available from the [http://www.xen.org/ official website].<br />
<br />
Work is in progress to enable FreeBSD to run natively on xen using the 'enlightened' paravirtualisation method.<br />
<br />
It is currently possible to run FreeBSD for i386 (32-bit) and amd64 (64-bit) using the hardware-assisted virtualisation instructions found on newer AMD and Intel processors. This ability came out with the XenServer 5.0 and Xen 3.2 releases (this was tested by the [[User:DrModiford|author]] using the official FreeBSD 7.0 current ISO releases).</div>DrModifordhttp://freebsdwiki.net/index.php/XenServerXenServer2008-09-23T08:16:02Z<p>DrModiford: Redirection page</p>
<hr />
<div>#REDIRECT [[Xen]]</div>DrModifordhttp://freebsdwiki.net/index.php/XenXen2008-09-23T08:15:21Z<p>DrModiford: Link corrected</p>
<hr />
<div>The '''xen''' system is a form of virtualisation that enables a host system to run many different operating systems. These hosted operating systems are referred to as guests and can be from different vendors and include Microsoft's Windows platforms and many [[GNU/Linux]] distributions.<br />
<br />
Work is in progress to enable FreeBSD to run natively on xen using the 'enlightened' paravirtualisation method.<br />
<br />
It is currently possible to run FreeBSD for i386 (32-bit) and amd64 (64-bit) using the hardware-assisted virtualisation instructions found on newer AMD and Intel processors. This ability came out with the XenServer 5.0 and Xen 3.2 releases (this was tested by the [[User:DrModiford|author]] using the official FreeBSD 7.0 current ISO releases).</div>DrModifordhttp://freebsdwiki.net/index.php/XenXen2008-09-23T08:15:04Z<p>DrModiford: Updated information to confirm Xen (and XenServer) will run unmodified FreeBSD i386 and amd64 platforms</p>
<hr />
<div>The '''xen''' system is a form of virtualisation that enables a host system to run many different operating systems. These hosted operating systems are referred to as guests and can be from different vendors and include Microsoft's Windows platforms and many [[GNU/Linux]] distributions.<br />
<br />
Work is in progress to enable FreeBSD to run natively on xen using the 'enlightened' paravirtualisation method.<br />
<br />
It is currently possible to run FreeBSD for i386 (32-bit) and amd64 (64-bit) using the hardware-assisted virtualisation instructions found on newer AMD and Intel processors. This ability came out with the XenServer 5.0 and Xen 3.2 releases (this was tested by the [[DrModiford|author]] using the official FreeBSD 7.0 current ISO releases).</div>DrModifordhttp://freebsdwiki.net/index.php/FreeBSD_PlatformsFreeBSD Platforms2008-09-23T08:09:17Z<p>DrModiford: Updated XenServer 5.0 now capable of hosting FreeBSD x86 32- and 64-bit platforms</p>
<hr />
<div>The [[FreeBSD]] Unix operating system supports a number of processor architectures, or platforms. The FreeBSD development team classifies the level of support as a tier, with Tier-1 being most compatible and supported on a certain architecture and Tier-2 (and beyond) being varying degrees of compatibility and support.<br />
<br />
== FreeBSD architectures ==<br />
<br />
The most obvious, and some might say ubiquitous, of the processor architectures is the i386 from Intel and the various clones from AMD, IBM / Cyrix and others. This architecture is widely used in all computers commonly referred to as 'PCs' and as such many of the World's operating systems support it, particularly Microsoft's range of Windows operating systems.<br />
<br />
The following is a list of FreeBSD supported processor architectures:<br />
<br />
=== i386 ===<br />
<br />
This is the architecture that will work on almost all Intel and AMD processors, both 32bit and 64bit though it will only use the 32bit mode of these processors. The i386 pre-dates the ubiquitous Pentium range of processors by two generations with the i486 processor existing between them. Therefore the backwards compatibility of the newer Intel and AMD processors ensures this architecture remains available.<br />
<br />
=== i486 ===<br />
<br />
This is simply the next generation of processor architecture from Intel, with other manufacturers making compatible clones of it. FreeBSD does not have a specific i486 release to run on this processor instead the i386 version is used for this specific architecture using the in-built backwards compatibility.<br />
<br />
=== Pentium (i586) ===<br />
<br />
The Pentium was simply a branding of next generation processors from Intel which moved away from the numerical naming of processors up until that point. The original processor in this generation is technically the i586 architecture with later Pentium processors, namely the Pentium II and Pentium III et al, being the i686 architecture.<br />
<br />
FreeBSD has no specific Pentium (either i586 or i686) release to run on this processor instead the i386 version is used for this specific architecture using the in-built backwards compatibility.<br />
<br />
=== Intel x86-64 ===<br />
<br />
This is another generation of processor architecture from Intel that featured 64bit processing. Intel moved away from the Pentium brand with this generation instead using the brand names Intel Core2 Duo amongst others.<br />
<br />
FreeBSD uses the AMD64 name for the specific release for this architecture (refer to the AMD64 section).<br />
<br />
'''Note:''' this processor architecture is different from the ia64 architecture used in the Itanium and Itanium 2 branded Intel processors (refer to the ia64 section).<br />
<br />
=== Itanium / Itanium 2 (ia64) ===<br />
<br />
The Itanium and the second generation Itanium 2 architecture was a radical change from the original Intel i386 generation of processors which saw a brand-new redesign of the processor core. As such they have no backwards-compatibility with any of the Intel i386 later generation of processor architecture.<br />
<br />
FreeBSD has a specific release for this architecture but is limited by specific supported systems. As such this is a Tier-2 platform.<br />
<br />
=== PC98 ===<br />
<br />
The PC98 was not specifically a processor but rather a standard for describing the hardware of a 'PC98' branded system. These PC98 branded systems were technically i386-compatible in architecture and were made by the large Japanese manufacturers such as EPSON and NEC. Therefore PC98 systems were typically found in Japan and neighbouring areas.<br />
<br />
All but newer PC98 systems (which feature New Extended Standard Architecture, or NESA) are support by the i386 release of FreeBSD.<br />
<br />
=== Sparc64 ===<br />
<br />
The Sparc64 architecture is a processor originally designed by Sun Microsystems but recently released under an open license. This is an entirely different architecture from the Intel and compatible processors and uses RISC as the underlying functionality. It is largely found in Sun's own line of servers.<br />
<br />
FreeBSD has a specific release for this architecture but is limited in functionality depending on the Sun server it is running on.<br />
<br />
'''Note:''' Sun Microsystems are themselves a UNIX operating system vendor with their [[Solaris]] product range.<br />
<br />
=== AMD64 ===<br />
<br />
The AMD64 is the brand name for the 64bit generation of processor architecture from AMD. The underlying functionality is different to that of Intel's 64bit implementation (on their x86-64 processors) although the two technologies are typically grouped under the title 'x64' by software vendors to denote neutrality between the two processor manufacturers. As such the majority of 64bit-enabled operating systems will run on either architecture without requiring two separate releases.<br />
<br />
FreeBSD has a specific release for this architecture under the AMD64 title (refer to the x86-64 section).<br />
<br />
=== PowerPC ===<br />
<br />
The PowerPC is the brand name for the processor architecture designed by collaboration between Apple, IBM and Motorola. This architecture was commonly used in Apple systems prior to their migration to the Intel architecture (that of the later generation Pentium brand) however it remains in use by IBM in their server range.<br />
<br />
FreeBSD is in an initial stage of developing support for this platform and as such there is little information on the availability of a specific release for this architecture.<br />
<br />
=== Xen ===<br />
<br />
The Xen platform is a form of virtualisation that abstracts the operating system running above it from the underlying hardware below it. This is controlled by the Xen 'Hypervisor', a form of high-end supervisor running at the host-processor level.<br />
<br />
In much the same way as an operating system can 'task switch' between lots of running services and applications to give the appearance of multitasking the Xen hypervisor does the same with multiple operating systems. This permits consolidation of servers from the conventional 'one operating system per physical server' to 'multiple operating systems per single server'. The operating systems can be a combination of open source, such as Red Hat, SuSE et al, and closed source, such as recent releases of Microsoft Windows.<br />
<br />
The Xen system was bought by Citrix and is sold under the [http://citrix.com/English/ps2/products/product.asp?contentID=683148 XenServer] brand name. The open source code remains available from the [http://www.xen.org/ official website].<br />
<br />
FreeBSD does not currently have official support for this ''pseudo''-architecture however as of XenServer 5.0 both the i386 (32-bit) and amd64 (64-bit) architectures will boot from the ISO media using the hardware-assisted virtualisation instructions found on AMD and Intel processors.<br />
<br />
== Architecture specific FreeBSD ==<br />
<br />
While the above list of architectures are available as releases from the FreeBSD project website it is possible to make a version of FreeBSD for a specific processor.<br />
<br />
As an example, a system administrator could install FreeBSD on a latest-generation Intel processor - say a Core2 Duo - using the i386 release of the FreeBSD CD-ROMs. This would, as mentioned in the relevant subsections above, only utilise the i386 compatibility of the processor. The system administrator could then recompile the FreeBSD kernel using the original source code and configuring the compiler to use the newer processor-specific architecture. This will take advantage of the processor's cutting-edge features and is typically done to improve the performance of the operating system as a whole. Software from the [[ports]] system can be compiled in much the same way.<br />
<br />
The [[Custom Kernel]] article covers this in greater detail.<br />
<br />
== Notes ==<br />
<br />
[[NetBSD]], a relation of FreeBSD, uses the term 'ports' to refer to processor specific releases which is different to the FreeBSD term of [[ports]]. NetBSD is most well known for supporting the most diverse set of processor architectures. Visit the [http://www.netbsd.org official NetBSD website] for more details.<br />
<br />
[[Category:Architecture-Specific]]</div>DrModifordhttp://freebsdwiki.net/index.php/OpenBootOpenBoot2008-09-16T13:02:00Z<p>DrModiford: Small article covering OpenBoot / Open Firmware (found on non-x86 systems)</p>
<hr />
<div><br />
The '''OpenBoot''' system is the equivalent of a PC-based BIOS but typically utilised on non-x86 architectures. The name 'OpenBoot' is a Sun Microsystem's term for 'Open Firmware', the actual technology used to boot systems and is endorsed by the IEEE. The technology originated at Sun but latterly Apple and IBM (and other non-x86 system manufacturers) have released systems implementing the standard.<br />
<br />
See the [http://en.wikipedia.org/wiki/Open_Firmware Wikipedia article] for more details on the 'Open Firmware' technology.</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_Ultra_5Installation on Ultra 52008-09-16T12:51:46Z<p>DrModiford: Edited the opening page</p>
<hr />
<div>The following guide covers the base installation of FreeBSD on the [[Sun Microsystems Hardware|Sun Microsystems]]' Ultra 5 platform. This should also be suitable for the Ultra 10 platform, a faster and improved variant of the Ultra 5. The installation is similar to an installation of FreeBSD on regular x86 systems. The following covers the specifics of the Ultra 5 system installation.<br />
<br />
== Pre-requisites ==<br />
<br />
The specific SPARC-based installation media must be downloaded (or purchased through one of the affiliated on-line stores) - the x86-based installation media will not work! If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the Ultra 5 uses the [[OpenBoot]] system to initiate system start-up, the equivalent of the ubiquitous PC BIOS, accessing it is different to what you may be used to coming from the PC world. Upon starting up and viewing the white boot screen (featuring the Sun classic logo and various system details) the key combination 'Stop' and the letter 'A' must be pressed together. This results in a prompt that simply states: "ok".<br />
<br />
This allows commands to be typed that control the system's start-up. For example, typing "probe-ide" and pressing enter will reveal the devices attached to the IDE ports. Typically one hard drive and a CD-ROM will be revealed though that is dependant on the installed hardware.<br />
<br />
== Initiating the FreeBSD installer ==<br />
<br />
With the OpenBoot system in command mode (see above how to interrupt system start-up) and the FreeBSD for SPARC installation cd-rom in the drive, type the following command to begin the process:<br />
<br />
ok '''boot cdrom /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== Installing FreeBSD ==<br />
<br />
After a short while with lots of information scrolling across the screen the familiar '''Country Selection''' page appears. From this point the installation becomes the same as an x86-based installation.<br />
<br />
Please refer to [[Installing FreeBSD - Standard Installation|this guide]] for continued installation instructions.<br />
<br />
== Booting FreeBSD ==<br />
<br />
Following a successful installation the system will reboot and attempt to load an operating system. If the system fails to load type the following command to begin the process:<br />
<br />
ok '''boot disk /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
If the server fails to start upon reboot, requiring the above command to be run manually each time, the following commands should be issued on the OpenBoot screen:<br />
<br />
ok '''setenv boot-device disk''' (press Enter)<br />
ok '''setenv boot-file /boot/loader''' (press Enter)<br />
ok '''nvstore''' (press Enter)<br />
<br />
These commands will set the environment variables 'boot-device' and 'boot-file' with the appropriate values for FreeBSD's boot loader and then commit the values to the system's non-volatile memory (similar to Save Settings in a conventional PC BIOS).<br />
<br />
Either reboot the system or re-issue the 'boot' command above to continue loading FreeBSD.<br />
<br />
== FreeBSD on UltraSPARC specific issues ==<br />
<br />
The following lists some variations to the typical x86-based installation.<br />
<br />
=== Country Selection ===<br />
<br />
This page does not follow to the prompt for '''Code Page''' selection.<br />
<br />
=== Hard Disk Partitioning ===<br />
<br />
The various hard drive stages and boot loader options are skipped and the '''FreeBSD Disklabel Editor''' starts directly.<br />
<br />
This could be because dual-booting and co-existing with other operating systems is not possible under this architecture.<br />
<br />
=== Networking ===<br />
<br />
The '''Network interface information required''' page will list the available (recognised) Ethernet cards installed. The on-board network card is supported by the 'hme' driver, known (and listed on-screen) as the "Happy Meal Ethernet" adaptor. Other network cards, if installed and are compatible, will also be listed.<br />
<br />
Most, if not all, PCI network cards supported by the x86 release should be supported by the UltraSPARC release.<br />
<br />
=== Sound ===<br />
<br />
The Ultra 5 has on-board audio featuring line-in, line-out, microphone and speaker sockets on the rear (using conventional jacks) and a CD-audio connection internally. The audio device is based on the Crystal Sounds CS4231A and FreeBSD for Sparc64 features a driver for this chip-set.<br />
<br />
The file '/boot/loader.conf' requires the following lines added to it:<br />
<br />
'''sound_load="YES"'''<br />
'''snd_audiocs_load="YES"'''<br />
<br />
'''Note:''' this file might not exist and will need creating.<br />
<br />
The system will need rebooting for these drivers to load. It is possible to use [[kldload]] to start them without a reboot as follows:<br />
<br />
'''kldload sound''' (press Enter)<br />
'''kldload snd_audiocd''' (press Enter)<br />
<br />
The [[dmesg]] command will output a similar entry to the following after successful detection of the audio device:<br />
<br />
pcm0: <Sun Audiocs> addr 0x147...<br />
<br />
There is also an audio driver for the 'Ensoniq AudioPCI ES137x' series of chip-sets from Creative Labs. Substitute the above 'snd_audiocs' with 'snd_es137x' to utilise this audio device.<br />
<br />
== Settings used ==<br />
<br />
During the installation on a real Ultra 5 system the following choices were used.<br />
<br />
The hard drive was split up into the following [[slices]]:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
! Part<br />
! Mount<br />
! Size<br />
! NewFS<br />
|-<br />
| ad0a<br />
| /<br />
| 512MB<br />
| UFS2 Y<br />
|-<br />
| ad0b<br />
| <br />
| 1024MB<br />
| SWAP<br />
|-<br />
| ad0d<br />
| /var<br />
| 1024MB<br />
| UFS2+s Y<br />
|-<br />
| ad0e<br />
| /tmp<br />
| 512MB<br />
| UFS2+S Y<br />
|-<br />
| ad0f<br />
| /usr<br />
| 32768MB<br />
| UFS2+S Y<br />
|-<br />
| ad0g<br />
| /svr<br />
| 114GB<br />
| UFS2+S Y<br />
|-<br />
|}<br />
<br />
The 'SWAP' is set to 2x the on-board RAM size (a FreeBSD system recommendation). The '/usr' splice is 32GB, but shown as 32768MB on the screen. The '/svr' slice used the remainder of the disk, which happened to be 114GB of the 160GB (give-or-take) capacity and exists as a place to host the 'server' specific data instead of the default '/usr' locations used by [[Apache]] and others.<br />
<br />
== See also ==<br />
<br />
For more details on configuring the OpenBoot system, see Sun Microsystem's [http://docs.sun.com/app/docs/doc/802-3242/6i75cc1kk?a=view Command Reference Manual] web page.<br />
<br />
[[Category : Installation]]</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_Ultra_5Installation on Ultra 52008-09-16T12:48:21Z<p>DrModiford: Added See also section</p>
<hr />
<div>The following guide covers the initiation of an installation of FreeBSD on the [[Sun Microsystems Hardware|Sun Microsystems]]' Ultra 5 platform. This should be suitable for the Ultra 10 platform, a faster and improved variant of the Ultra 5. It does not cover the entire installation, which is similar to an installation of FreeBSD on x86. It simply covers the starting of the installer to the point of similarity.<br />
<br />
== Pre-requisites ==<br />
<br />
The specific SPARC-based installation media must be downloaded (or purchased through one of the affiliated on-line stores) - the x86-based installation media will not work! If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the Ultra 5 uses the [[OpenBoot]] system to initiate system start-up, the equivalent of the ubiquitous PC BIOS, accessing it is different to what you may be used to coming from the PC world. Upon starting up and viewing the white boot screen (featuring the Sun classic logo and various system details) the key combination 'Stop' and the letter 'A' must be pressed together. This results in a prompt that simply states: "ok".<br />
<br />
This allows commands to be typed that control the system's start-up. For example, typing "probe-ide" and pressing enter will reveal the devices attached to the IDE ports. Typically one hard drive and a CD-ROM will be revealed though that is dependant on the installed hardware.<br />
<br />
== Initiating the FreeBSD installer ==<br />
<br />
With the OpenBoot system in command mode (see above how to interrupt system start-up) and the FreeBSD for SPARC installation cd-rom in the drive, type the following command to begin the process:<br />
<br />
ok '''boot cdrom /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== Installing FreeBSD ==<br />
<br />
After a short while with lots of information scrolling across the screen the familiar '''Country Selection''' page appears. From this point the installation becomes the same as an x86-based installation.<br />
<br />
Please refer to [[Installing FreeBSD - Standard Installation|this guide]] for continued installation instructions.<br />
<br />
== Booting FreeBSD ==<br />
<br />
Following a successful installation the system will reboot and attempt to load an operating system. If the system fails to load type the following command to begin the process:<br />
<br />
ok '''boot disk /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
If the server fails to start upon reboot, requiring the above command to be run manually each time, the following commands should be issued on the OpenBoot screen:<br />
<br />
ok '''setenv boot-device disk''' (press Enter)<br />
ok '''setenv boot-file /boot/loader''' (press Enter)<br />
ok '''nvstore''' (press Enter)<br />
<br />
These commands will set the environment variables 'boot-device' and 'boot-file' with the appropriate values for FreeBSD's boot loader and then commit the values to the system's non-volatile memory (similar to Save Settings in a conventional PC BIOS).<br />
<br />
Either reboot the system or re-issue the 'boot' command above to continue loading FreeBSD.<br />
<br />
== FreeBSD on UltraSPARC specific issues ==<br />
<br />
The following lists some variations to the typical x86-based installation.<br />
<br />
=== Country Selection ===<br />
<br />
This page does not follow to the prompt for '''Code Page''' selection.<br />
<br />
=== Hard Disk Partitioning ===<br />
<br />
The various hard drive stages and boot loader options are skipped and the '''FreeBSD Disklabel Editor''' starts directly.<br />
<br />
This could be because dual-booting and co-existing with other operating systems is not possible under this architecture.<br />
<br />
=== Networking ===<br />
<br />
The '''Network interface information required''' page will list the available (recognised) Ethernet cards installed. The on-board network card is supported by the 'hme' driver, known (and listed on-screen) as the "Happy Meal Ethernet" adaptor. Other network cards, if installed and are compatible, will also be listed.<br />
<br />
Most, if not all, PCI network cards supported by the x86 release should be supported by the UltraSPARC release.<br />
<br />
=== Sound ===<br />
<br />
The Ultra 5 has on-board audio featuring line-in, line-out, microphone and speaker sockets on the rear (using conventional jacks) and a CD-audio connection internally. The audio device is based on the Crystal Sounds CS4231A and FreeBSD for Sparc64 features a driver for this chip-set.<br />
<br />
The file '/boot/loader.conf' requires the following lines added to it:<br />
<br />
'''sound_load="YES"'''<br />
'''snd_audiocs_load="YES"'''<br />
<br />
'''Note:''' this file might not exist and will need creating.<br />
<br />
The system will need rebooting for these drivers to load. It is possible to use [[kldload]] to start them without a reboot as follows:<br />
<br />
'''kldload sound''' (press Enter)<br />
'''kldload snd_audiocd''' (press Enter)<br />
<br />
The [[dmesg]] command will output a similar entry to the following after successful detection of the audio device:<br />
<br />
pcm0: <Sun Audiocs> addr 0x147...<br />
<br />
There is also an audio driver for the 'Ensoniq AudioPCI ES137x' series of chip-sets from Creative Labs. Substitute the above 'snd_audiocs' with 'snd_es137x' to utilise this audio device.<br />
<br />
== Settings used ==<br />
<br />
During the installation on a real Ultra 5 system the following choices were used.<br />
<br />
The hard drive was split up into the following [[slices]]:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
! Part<br />
! Mount<br />
! Size<br />
! NewFS<br />
|-<br />
| ad0a<br />
| /<br />
| 512MB<br />
| UFS2 Y<br />
|-<br />
| ad0b<br />
| <br />
| 1024MB<br />
| SWAP<br />
|-<br />
| ad0d<br />
| /var<br />
| 1024MB<br />
| UFS2+s Y<br />
|-<br />
| ad0e<br />
| /tmp<br />
| 512MB<br />
| UFS2+S Y<br />
|-<br />
| ad0f<br />
| /usr<br />
| 32768MB<br />
| UFS2+S Y<br />
|-<br />
| ad0g<br />
| /svr<br />
| 114GB<br />
| UFS2+S Y<br />
|-<br />
|}<br />
<br />
The 'SWAP' is set to 2x the on-board RAM size (a FreeBSD system recommendation). The '/usr' splice is 32GB, but shown as 32768MB on the screen. The '/svr' slice used the remainder of the disk, which happened to be 114GB of the 160GB (give-or-take) capacity and exists as a place to host the 'server' specific data instead of the default '/usr' locations used by [[Apache]] and others.<br />
<br />
== See also ==<br />
<br />
For more details on configuring the OpenBoot system, see Sun Microsystem's [http://docs.sun.com/app/docs/doc/802-3242/6i75cc1kk?a=view Command Reference Manual] web page.<br />
<br />
[[Category : Installation]]</div>DrModifordhttp://freebsdwiki.net/index.php/Sparc_-_Installing_FreeBSDSparc - Installing FreeBSD2008-09-16T10:11:26Z<p>DrModiford: Added link to the more in-depth article</p>
<hr />
<div>Installation of FreeBSD on the Sparc architechture is nearly identical to the [[Installing FreeBSD | x86 architecture installation]], although booting from media differs somewhat from the x86 install procedures: <br />
<br />
For a more in-depth guide, please see [[Installation on Ultra 5|this article]] based on on the Ultra 5 model from Sun Microsystems.<br />
<br />
==Booting from the Install disc==<br />
<br />
The first step is getting your target machine to boot off of your install media. Sun's Sparc machines have a few quirks, the most relevant of which for you right now is Open Boot Firmware.<br />
<br />
Boot from the console (or console via terminal,) and during boot-up -- if you have a SUN keyboard -- hit the STOP button and the letter "a" on the keyboard. If you're on the console port of the machine, you should not have to do this. If this does not halt the POST and bootup, and there is already a version of unix on the machine (e.g., Solaris,) then you can get to the firmware prompt by executing<br />
init 0<br />
as root.<br />
<br />
This will drop you to the <B>OK</b> prompt. This is the Open Firmware prompt, which is a close cousin of the [http://www.macdevcenter.com/pub/a/mac/2003/02/18/secure_tibook.html Mac OS X Open Firmware (off-site link)]. It may help to think of it as a BIOS-commandline.<br />
<br />
The OK prompt may be displayed thus:<br />
OK <br />
or <br />
OK> <br />
this can be one of the other depending on which version of the Open Firmware the machine is running.<br />
<br />
If you're running on a machine with multiple processors, you may see<br />
OK {0} <br />
or <br />
OK {1}<br />
<br />
this will only be seen on machines with multiple processors and the number within the brackets is to let you know which processor you're currently running on.<br />
<br />
At the <b>OK></b> prompt, type in "boot cdrom" (if you've got a bootable cdrom for the sparc arch in the cd drive of the machine) or "boot net" if you're trying to do a net install from a network server. From here on in, the install should be nearly identical to an [[Installing FreeBSD | x86 install]].<br />
<br />
==It won't automatically boot from the hard drive!==<br />
<br />
Relax, young padwan, if you're still getting the OK prompt. You have to fool around in the OpenBoot prompt to get OpenBoot to auto-load the OS from the disk. The command(s) that you want are:<br />
OK> setenv boot-device disk1:a<br />
OK> setenv auto-boot? true<br />
Where disk1:a is the second disk's first partition. If you are unsure which disk is which, do a <br />
OK> probe-ide<br />
or<br />
OK> probe-scsi<br />
to show your disks. Please see the [http://docs.sun.com/db/doc/816-1177-10/6m7k5h7oe?a=view Sun Documentation on OBP booting options] for more info.<br />
<br />
Note that if you've tried to install a non-Solaris Unix on SUN hardware, e.g., a sparc-capable linux variant like debian or gentoo, then you might expect that you'd have to make a sunlabel disk label -- you don't. Just let the OS partition (or partition yourself) without worrying about it.<br />
<br />
see also: [http://sunsolve.sun.com/handbook_pub/General/OBP.html Open Boot Firmware (off-site link to sun.com's info on Open Boot parameters).]<br />
<br />
See also [[Sparc_-_Gotchas]]<br />
[[Category : Architecture-Specific]]<br />
[[Category : Installation]]</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_Ultra_5Installation on Ultra 52008-09-16T10:08:27Z<p>DrModiford: Minor corrections</p>
<hr />
<div>The following guide covers the initiation of an installation of FreeBSD on the [[Sun Microsystems Hardware|Sun Microsystems]]' Ultra 5 platform. This should be suitable for the Ultra 10 platform, a faster and improved variant of the Ultra 5. It does not cover the entire installation, which is similar to an installation of FreeBSD on x86. It simply covers the starting of the installer to the point of similarity.<br />
<br />
== Pre-requisites ==<br />
<br />
The specific SPARC-based installation media must be downloaded (or purchased through one of the affiliated on-line stores) - the x86-based installation media will not work! If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the Ultra 5 uses the [[OpenBoot]] system to initiate system start-up, the equivalent of the ubiquitous PC BIOS, accessing it is different to what you may be used to coming from the PC world. Upon starting up and viewing the white boot screen (featuring the Sun classic logo and various system details) the key combination 'Stop' and the letter 'A' must be pressed together. This results in a prompt that simply states: "ok".<br />
<br />
This allows commands to be typed that control the system's start-up. For example, typing "probe-ide" and pressing enter will reveal the devices attached to the IDE ports. Typically one hard drive and a CD-ROM will be revealed though that is dependant on the installed hardware.<br />
<br />
== Initiating the FreeBSD installer ==<br />
<br />
With the OpenBoot system in command mode (see above how to interrupt system start-up) and the FreeBSD for SPARC installation cd-rom in the drive, type the following command to begin the process:<br />
<br />
ok '''boot cdrom /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== Installing FreeBSD ==<br />
<br />
After a short while with lots of information scrolling across the screen the familiar '''Country Selection''' page appears. From this point the installation becomes the same as an x86-based installation.<br />
<br />
Please refer to [[Installing FreeBSD - Standard Installation|this guide]] for continued installation instructions.<br />
<br />
== Booting FreeBSD ==<br />
<br />
Following a successful installation the system will reboot and attempt to load an operating system. If the system fails to load type the following command to begin the process:<br />
<br />
ok '''boot disk /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
If the server fails to start upon reboot, requiring the above command to be run manually each time, the following commands should be issued on the OpenBoot screen:<br />
<br />
ok '''setenv boot-device disk''' (press Enter)<br />
ok '''setenv boot-file /boot/loader''' (press Enter)<br />
ok '''nvstore''' (press Enter)<br />
<br />
These commands will set the environment variables 'boot-device' and 'boot-file' with the appropriate values for FreeBSD's boot loader and then commit the values to the system's non-volatile memory (similar to Save Settings in a conventional PC BIOS).<br />
<br />
Either reboot the system or re-issue the 'boot' command above to continue loading FreeBSD.<br />
<br />
== FreeBSD on UltraSPARC specific issues ==<br />
<br />
The following lists some variations to the typical x86-based installation.<br />
<br />
=== Country Selection ===<br />
<br />
This page does not follow to the prompt for '''Code Page''' selection.<br />
<br />
=== Hard Disk Partitioning ===<br />
<br />
The various hard drive stages and boot loader options are skipped and the '''FreeBSD Disklabel Editor''' starts directly.<br />
<br />
This could be because dual-booting and co-existing with other operating systems is not possible under this architecture.<br />
<br />
=== Networking ===<br />
<br />
The '''Network interface information required''' page will list the available (recognised) Ethernet cards installed. The on-board network card is supported by the 'hme' driver, known (and listed on-screen) as the "Happy Meal Ethernet" adaptor. Other network cards, if installed and are compatible, will also be listed.<br />
<br />
Most, if not all, PCI network cards supported by the x86 release should be supported by the UltraSPARC release.<br />
<br />
=== Sound ===<br />
<br />
The Ultra 5 has on-board audio featuring line-in, line-out, microphone and speaker sockets on the rear (using conventional jacks) and a CD-audio connection internally. The audio device is based on the Crystal Sounds CS4231A and FreeBSD for Sparc64 features a driver for this chip-set.<br />
<br />
The file '/boot/loader.conf' requires the following lines added to it:<br />
<br />
'''sound_load="YES"'''<br />
'''snd_audiocs_load="YES"'''<br />
<br />
'''Note:''' this file might not exist and will need creating.<br />
<br />
The system will need rebooting for these drivers to load. It is possible to use [[kldload]] to start them without a reboot as follows:<br />
<br />
'''kldload sound''' (press Enter)<br />
'''kldload snd_audiocd''' (press Enter)<br />
<br />
The [[dmesg]] command will output a similar entry to the following after successful detection of the audio device:<br />
<br />
pcm0: <Sun Audiocs> addr 0x147...<br />
<br />
There is also an audio driver for the 'Ensoniq AudioPCI ES137x' series of chip-sets from Creative Labs. Substitute the above 'snd_audiocs' with 'snd_es137x' to utilise this audio device.<br />
<br />
== Settings used ==<br />
<br />
During the installation on a real Ultra 5 system the following choices were used.<br />
<br />
The hard drive was split up into the following [[slices]]:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
! Part<br />
! Mount<br />
! Size<br />
! NewFS<br />
|-<br />
| ad0a<br />
| /<br />
| 512MB<br />
| UFS2 Y<br />
|-<br />
| ad0b<br />
| <br />
| 1024MB<br />
| SWAP<br />
|-<br />
| ad0d<br />
| /var<br />
| 1024MB<br />
| UFS2+s Y<br />
|-<br />
| ad0e<br />
| /tmp<br />
| 512MB<br />
| UFS2+S Y<br />
|-<br />
| ad0f<br />
| /usr<br />
| 32768MB<br />
| UFS2+S Y<br />
|-<br />
| ad0g<br />
| /svr<br />
| 114GB<br />
| UFS2+S Y<br />
|-<br />
|}<br />
<br />
The 'SWAP' is set to 2x the on-board RAM size (a FreeBSD system recommendation). The '/usr' splice is 32GB, but shown as 32768MB on the screen. The '/svr' slice used the remainder of the disk, which happened to be 114GB of the 160GB (give-or-take) capacity and exists as a place to host the 'server' specific data instead of the default '/usr' locations used by [[Apache]] and others.<br />
<br />
[[Category : Installation]]</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_Ultra_5Installation on Ultra 52008-09-16T10:04:45Z<p>DrModiford: Added section on sound device</p>
<hr />
<div>The following guide covers the initiation of an installation of FreeBSD on the [[Sun Microsystems Hardware|Sun Microsystems]]' Ultra 5 platform. This should be suitable for the Ultra 10 platform, a faster and improved variant of the Ultra 5. It does not cover the entire installation, which is similar to an installation of FreeBSD on x86. It simply covers the starting of the installer to the point of similarity.<br />
<br />
== Pre-requisites ==<br />
<br />
The specific SPARC-based installation media must be downloaded (or purchased through one of the affiliated on-line stores) - the x86-based installation media will not work! If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the Ultra 5 uses the [[OpenBoot]] system to initiate system start-up, the equivalent of the ubiquitous PC BIOS, accessing it is different to what you may be used to coming from the PC world. Upon starting up and viewing the white boot screen (featuring the Sun classic logo and various system details) the key combination 'Stop' and the letter 'A' must be pressed together. This results in a prompt that simply states: "ok".<br />
<br />
This allows commands to be typed that control the system's start-up. For example, typing "probe-ide" and pressing enter will reveal the devices attached to the IDE ports. Typically one hard drive and a CD-ROM will be revealed though that is dependant on the installed hardware.<br />
<br />
== Initiating the FreeBSD installer ==<br />
<br />
With the OpenBoot system in command mode (see above how to interrupt system start-up) and the FreeBSD for SPARC installation cd-rom in the drive, type the following command to begin the process:<br />
<br />
ok '''boot cdrom /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== Installing FreeBSD ==<br />
<br />
After a short while with lots of information scrolling across the screen the familiar '''Country Selection''' page appears. From this point the installation becomes the same as an x86-based installation.<br />
<br />
Please refer to [[Installing FreeBSD - Standard Installation|this guide]] for continued installation instructions.<br />
<br />
== Booting FreeBSD ==<br />
<br />
Following a successful installation the system will reboot and attempt to load an operating system. If the system fails to load type the following command to begin the process:<br />
<br />
ok '''boot disk /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
If the server fails to start upon reboot, requiring the above command to be run manually each time, the following commands should be issued on the OpenBoot screen:<br />
<br />
ok '''setenv boot-device disk''' (press Enter)<br />
ok '''setenv boot-file /boot/loader''' (press Enter)<br />
ok '''nvstore''' (press Enter)<br />
<br />
These commands will set the environment variables 'boot-device' and 'boot-file' with the appropriate values for FreeBSD's boot loader and then commit the values to the system's non-volatile memory (similar to Save Settings in a conventional PC BIOS).<br />
<br />
Either reboot the system or re-issue the 'boot' command above to continue loading FreeBSD.<br />
<br />
== FreeBSD on UltraSPARC specific issues ==<br />
<br />
The following lists some variations to the typical x86-based installation.<br />
<br />
=== Country Selection ===<br />
<br />
This page does not follow to the prompt for '''Code Page''' selection.<br />
<br />
=== Hard Disk Partitioning ===<br />
<br />
The various hard drive stages and boot loader options are skipped and the '''FreeBSD Disklabel Editor''' starts directly.<br />
<br />
This could be because dual-booting and co-existing with other operating systems is not possible under this architecture.<br />
<br />
=== Networking ===<br />
<br />
The '''Network interface information required''' page will list the available (recognised) Ethernet cards installed. The on-board network card is supported by the 'hme' driver, known (and listed on-screen) as the "Happy Meal Ethernet" adaptor. Other network cards, if installed and are compatible, will also be listed.<br />
<br />
Most, if not all, PCI network cards supported by the x86 release should be supported by the UltraSPARC release.<br />
<br />
=== Sound ===<br />
<br />
The Ultra 5 has on-board audio featuring line-in, line-out, microphone and speaker sockets on the rear (using conventional jacks) and a CD-audio connection internally. The audio device is based on the Crystal Sounds CS4231A and FreeBSD for Sparc64 features a driver for this chip-set.<br />
<br />
The file '/boot/loader.conf' requires the following lines added to it:<br />
<br />
'''sound_load="YES"'''<br />
'''snd_audiocs_load="YES"'''<br />
<br />
'''Note:''' this file might not exist and need creating.<br />
<br />
The system will need rebooting for these drivers to load. It is possible to use [[kldload]] to start them without a reboot as follows:<br />
<br />
'''kldload sound''' (press Enter)<br />
'''kldload snd_audiocd''' (press Enter)<br />
<br />
The [[dmesg]] output will output a similar entry after successful detection of the sound device:<br />
<br />
pcm0: <Sun Audiocs> addr 0x147...<br />
<br />
There is also an audio driver for the 'Ensoniq AudioPCI ES137x' series of chip-sets from Creative Labs. Substitute the above 'snd_audiocs' with 'snd_es137x' to utilise this audio device.<br />
<br />
== Settings used ==<br />
<br />
During the installation on a real Ultra 5 system the following choices were used.<br />
<br />
The hard drive was split up into the following [[slices]]:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
! Part<br />
! Mount<br />
! Size<br />
! NewFS<br />
|-<br />
| ad0a<br />
| /<br />
| 512MB<br />
| UFS2 Y<br />
|-<br />
| ad0b<br />
| <br />
| 1024MB<br />
| SWAP<br />
|-<br />
| ad0d<br />
| /var<br />
| 1024MB<br />
| UFS2+s Y<br />
|-<br />
| ad0e<br />
| /tmp<br />
| 512MB<br />
| UFS2+S Y<br />
|-<br />
| ad0f<br />
| /usr<br />
| 32768MB<br />
| UFS2+S Y<br />
|-<br />
| ad0g<br />
| /svr<br />
| 114GB<br />
| UFS2+S Y<br />
|-<br />
|}<br />
<br />
The 'SWAP' is set to 2x the on-board RAM size (a FreeBSD system recommendation). The '/usr' splice is 32GB, but shown as 32768MB on the screen. The '/svr' slice used the remainder of the disk, which happened to be 114GB of the 160GB (give-or-take) capacity and exists as a place to host the 'server' specific data instead of the default '/usr' locations used by [[Apache]] and others.<br />
<br />
[[Category : Installation]]</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_Ultra_5Installation on Ultra 52008-09-16T09:40:38Z<p>DrModiford: How to configure the 'BIOS' of the Ultra system to boot FreeBSD every time</p>
<hr />
<div>The following guide covers the initiation of an installation of FreeBSD on the [[Sun Microsystems Hardware|Sun Microsystems]]' Ultra 5 platform. This should be suitable for the Ultra 10 platform, a faster and improved variant of the Ultra 5. It does not cover the entire installation, which is similar to an installation of FreeBSD on x86. It simply covers the starting of the installer to the point of similarity.<br />
<br />
== Pre-requisites ==<br />
<br />
The specific SPARC-based installation media must be downloaded (or purchased through one of the affiliated on-line stores) - the x86-based installation media will not work! If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the Ultra 5 uses the [[OpenBoot]] system to initiate system start-up, the equivalent of the ubiquitous PC BIOS, accessing it is different to what you may be used to coming from the PC world. Upon starting up and viewing the white boot screen (featuring the Sun classic logo and various system details) the key combination 'Stop' and the letter 'A' must be pressed together. This results in a prompt that simply states: "ok".<br />
<br />
This allows commands to be typed that control the system's start-up. For example, typing "probe-ide" and pressing enter will reveal the devices attached to the IDE ports. Typically one hard drive and a CD-ROM will be revealed though that is dependant on the installed hardware.<br />
<br />
== Initiating the FreeBSD installer ==<br />
<br />
With the OpenBoot system in command mode (see above how to interrupt system start-up) and the FreeBSD for SPARC installation cd-rom in the drive, type the following command to begin the process:<br />
<br />
ok '''boot cdrom /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== Installing FreeBSD ==<br />
<br />
After a short while with lots of information scrolling across the screen the familiar '''Country Selection''' page appears. From this point the installation becomes the same as an x86-based installation.<br />
<br />
Please refer to [[Installing FreeBSD - Standard Installation|this guide]] for continued installation instructions.<br />
<br />
== Booting FreeBSD ==<br />
<br />
Following a successful installation the system will reboot and attempt to load an operating system. If the system fails to load type the following command to begin the process:<br />
<br />
ok '''boot disk /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
If the server fails to start upon reboot, requiring the above command to be run manually each time, the following commands should be issued on the OpenBoot screen:<br />
<br />
ok '''setenv boot-device disk''' (press Enter)<br />
ok '''setenv boot-file /boot/loader''' (press Enter)<br />
ok '''nvstore''' (press Enter)<br />
<br />
These commands will set the environment variables 'boot-device' and 'boot-file' with the appropriate values for FreeBSD's boot loader and then commit the values to the system's non-volatile memory (similar to Save Settings in a conventional PC BIOS).<br />
<br />
Either reboot the system or re-issue the 'boot' command above to continue loading FreeBSD.<br />
<br />
== FreeBSD on UltraSPARC specific issues ==<br />
<br />
The following lists some variations to the typical x86-based installation.<br />
<br />
=== Country Selection ===<br />
<br />
This page does not follow to the prompt for '''Code Page''' selection.<br />
<br />
=== Hard Disk Partitioning ===<br />
<br />
The various hard drive stages and boot loader options are skipped and the '''FreeBSD Disklabel Editor''' starts directly.<br />
<br />
This could be because dual-booting and co-existing with other operating systems is not possible under this architecture.<br />
<br />
=== Networking ===<br />
<br />
The '''Network interface information required''' page will list the available (recognised) Ethernet cards installed. The on-board network card is supported by the 'hme' driver, known (and listed on-screen) as the "Happy Meal Ethernet" adaptor. Other network cards, if installed and are compatible, will also be listed.<br />
<br />
Most, if not all, PCI network cards supported by the x86 release should be supported by the UltraSPARC release.<br />
<br />
== Settings used ==<br />
<br />
During the installation on a real Ultra 5 system the following choices were used.<br />
<br />
The hard drive was split up into the following [[slices]]:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
! Part<br />
! Mount<br />
! Size<br />
! NewFS<br />
|-<br />
| ad0a<br />
| /<br />
| 512MB<br />
| UFS2 Y<br />
|-<br />
| ad0b<br />
| <br />
| 1024MB<br />
| SWAP<br />
|-<br />
| ad0d<br />
| /var<br />
| 1024MB<br />
| UFS2+s Y<br />
|-<br />
| ad0e<br />
| /tmp<br />
| 512MB<br />
| UFS2+S Y<br />
|-<br />
| ad0f<br />
| /usr<br />
| 32768MB<br />
| UFS2+S Y<br />
|-<br />
| ad0g<br />
| /svr<br />
| 114GB<br />
| UFS2+S Y<br />
|-<br />
|}<br />
<br />
The 'SWAP' is set to 2x the on-board RAM size (a FreeBSD system recommendation). The '/usr' splice is 32GB, but shown as 32768MB on the screen. The '/svr' slice used the remainder of the disk, which happened to be 114GB of the 160GB (give-or-take) capacity and exists as a place to host the 'server' specific data instead of the default '/usr' locations used by [[Apache]] and others.<br />
<br />
[[Category : Installation]]</div>DrModifordhttp://freebsdwiki.net/index.php/User:DrModifordUser:DrModiford2008-09-10T14:47:15Z<p>DrModiford: Uptime - update</p>
<hr />
<div>Okay, so I'm not really a doctor...<br />
<br />
= About =<br />
<br />
I started out on a Commodore 16 back when I was four and progressed through various computing platforms, most notably Windows and then Linux, before discovering FreeBSD several years ago. Since then I have had a long-term love affair with this operating system!<br />
<br />
I live in the offshore finance centre of Guernsey, part of the Channel Islands which sit between the mainlands of UK and France, and work within the IT department of a fiduciary (trust / finance industry) company.<br />
<br />
= Knowledge =<br />
<br />
I have been privileged through my career to have used many different computing platforms from the humble BBC Micro to large-scale IBM AS/400s. After discovering FreeBSD I became proficient at deploying, implementing and maintaining it in both personal and corporate environments.<br />
<br />
At home it has been used to host my web and email server over an ADSL connection and as a Samba file server to store music and movies.<br />
<br />
In the office it is used to monitor network traffic with MRTG, host an internal Wikipedia for application development documentation, allow marketing to mass-mail intermediaries using qmail and host SecureFTP file distribution on-line. Recently a Subversion server was requested by the development team and was installed within moments from the fantastic [[ports]] system.<br />
<br />
= Contact =<br />
<br />
I look forward to chatting with any like-minded FreeBSD users out there. I can be contacted on:<br />
<br />
* ICQ: 59-397-985 or;<br />
* MSN: glynb at hotmail dot co dot uk (hotmail used to be a FreeBSD house once!)<br />
<br />
Of course, I use those accounts through KDE [[Kopete]] on a laptop running PC-BSD!<br />
<br />
= Up Time =<br />
<br />
Just to prove the reliability of FreeBSD as a server operating system, here's my uptime:<br />
<br />
%uptime<br />
3:23PM up '''386 days''', 16:01, 2 users, load averages: 0.00, 0.00, 0.00<br />
<br />
...also proves that the electricity supply in Guernsey is extremely reliable as that server is not on a UPS either!<br />
<br />
It's just a shame that I have to power it off in order move my servers into a new location within the house :'-( *sniff*<br />
<br />
Update (2008-09-10) I decided not to power it off but the dust got to the machine and it died from over heating. So it managed just over the 400 days before requiring a good blow-out. In other news, I now have a Sun Microsystems Ultra 5 to play with and have managed to get FreeBSD 7.0 for Sparc running. Now... what to use it for???</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_Ultra_5Installation on Ultra 52008-09-10T10:47:45Z<p>DrModiford: Corrections</p>
<hr />
<div>The following guide covers the initiation of an installation of FreeBSD on the [[Sun Microsystems Hardware|Sun Microsystems]]' Ultra 5 platform. This should be suitable for the Ultra 10 platform, a faster and improved variant of the Ultra 5. It does not cover the entire installation, which is similar to an installation of FreeBSD on x86. It simply covers the starting of the installer to the point of similarity.<br />
<br />
== Pre-requisites ==<br />
<br />
The specific SPARC-based installation media must be downloaded (or purchased through one of the affiliated on-line stores) - the x86-based installation media will not work! If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the Ultra 5 uses the [[OpenBoot]] system to initiate system start-up, the equivalent of the ubiquitous PC BIOS, accessing it is different to what you may be used to coming from the PC world. Upon starting up and viewing the white boot screen (featuring the Sun classic logo and various system details) the key combination 'Stop' and the letter 'A' must be pressed together. This results in a prompt that simply states: "ok".<br />
<br />
This allows commands to be typed that control the system's start-up. For example, typing "probe-ide" and pressing enter will reveal the devices attached to the IDE ports. Typically one hard drive and a CD-ROM will be revealed though that is dependant on the installed hardware.<br />
<br />
== Initiating the FreeBSD installer ==<br />
<br />
With the OpenBoot system in command mode (see above how to interrupt system start-up) and the FreeBSD for SPARC installation cd-rom in the drive, type the following command to begin the process:<br />
<br />
ok '''boot cdrom /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== Installing FreeBSD ==<br />
<br />
After a short while with lots of information scrolling across the screen the familiar '''Country Selection''' page appears. From this point the installation becomes the same as an x86-based installation.<br />
<br />
Please refer to [[Installing FreeBSD - Standard Installation|this guide]] for continued installation instructions.<br />
<br />
== Booting FreeBSD ==<br />
<br />
Following a successful installation the system will reboot and attempt to load an operating system. If the system fails to load type the following command to begin the process:<br />
<br />
ok '''boot disk /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== FreeBSD on UltraSPARC specific issues ==<br />
<br />
The following lists some variations to the typical x86-based installation.<br />
<br />
=== Country Selection ===<br />
<br />
This page does not follow to the prompt for '''Code Page''' selection.<br />
<br />
=== Hard Disk Partitioning ===<br />
<br />
The various hard drive stages and boot loader options are skipped and the '''FreeBSD Disklabel Editor''' starts directly.<br />
<br />
This could be because dual-booting and co-existing with other operating systems is not possible under this architecture.<br />
<br />
=== Networking ===<br />
<br />
The '''Network interface information required''' page will list the available (recognised) Ethernet cards installed. The on-board network card is supported by the 'hme' driver, known (and listed on-screen) as the "Happy Meal Ethernet" adaptor. Other network cards, if installed and are compatible, will also be listed.<br />
<br />
Most, if not all, PCI network cards supported by the x86 release should be supported by the UltraSPARC release.<br />
<br />
== Settings used ==<br />
<br />
During the installation on a real Ultra 5 system the following choices were used.<br />
<br />
The hard drive was split up into the following [[slices]]:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
! Part<br />
! Mount<br />
! Size<br />
! NewFS<br />
|-<br />
| ad0a<br />
| /<br />
| 512MB<br />
| UFS2 Y<br />
|-<br />
| ad0b<br />
| <br />
| 1024MB<br />
| SWAP<br />
|-<br />
| ad0d<br />
| /var<br />
| 1024MB<br />
| UFS2+s Y<br />
|-<br />
| ad0e<br />
| /tmp<br />
| 512MB<br />
| UFS2+S Y<br />
|-<br />
| ad0f<br />
| /usr<br />
| 32768MB<br />
| UFS2+S Y<br />
|-<br />
| ad0g<br />
| /svr<br />
| 114GB<br />
| UFS2+S Y<br />
|-<br />
|}<br />
<br />
The 'SWAP' is set to 2x the on-board RAM size (a FreeBSD system recommendation). The '/usr' splice is 32GB, but shown as 32768MB on the screen. The '/svr' slice used the remainder of the disk, which happened to be 114GB of the 160GB (give-or-take) capacity and exists as a place to host the 'server' specific data instead of the default '/usr' locations used by [[Apache]] and others.<br />
<br />
[[Category : Installation]]</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_Ultra_5Installation on Ultra 52008-09-10T10:44:34Z<p>DrModiford: SWAP entry corrected</p>
<hr />
<div>The following guide covers the initiation of an installation of FreeBSD on the [[Sun Microsystems Hardware|Sun Microsystems]]' Ultra 5 platform. This should be suitable for the Ultra 10 platform, a faster and improved variant of the Ultra 5. It does not cover the entire installation, which is similar to an installation of FreeBSD on x86. It simply covers the starting of the installer to the point of similarity.<br />
<br />
== Pre-requisites ==<br />
<br />
The specific SPARC-based installation media must be downloaded (or purchased through one of the affiliated on-line stores) - the x86-based installation media will not work! If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the Ultra 5 uses the [[OpenBoot]] system to initiate system start-up, the equivalent of the ubiquitous PC BIOS, accessing it is different to what you may be used to coming from the PC world. Upon starting up and viewing the white boot screen (featuring the Sun classic logo and various system details) the key combination 'Stop' and the letter 'A' must be pressed together. This results in a prompt that simply states: "ok".<br />
<br />
This allows commands to be typed that control the system's start-up. For example, typing "probe-ide" and pressing enter will reveal the devices attached to the IDE ports. Typically one hard drive and a CD-ROM will be revealed though that is dependant on the installed hardware.<br />
<br />
== Initiating the FreeBSD installer ==<br />
<br />
With the OpenBoot system in command mode (see above how to interrupt system start-up) and the FreeBSD for SPARC installation cd-rom in the drive, type the following command to begin the process:<br />
<br />
ok '''boot cdrom /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== Installing FreeBSD ==<br />
<br />
After a short while with lots of information scrolling across the screen the familiar '''Country Selection''' page appears. From this point the installation becomes the same as an x86-based installation.<br />
<br />
Please refer to [[Installing FreeBSD - Standard Installation|this guide]] for continued installation instructions.<br />
<br />
== Booting FreeBSD ==<br />
<br />
Following a successful installation the system will reboot and attempt to load an operating system. If the system fails to load type the following command to begin the process:<br />
<br />
ok '''boot disk /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== FreeBSD on UltraSPARC specific issues ==<br />
<br />
The following lists some variations to the typical x86-based installation.<br />
<br />
=== Country Selection ===<br />
<br />
This page does not follow to the prompt for '''Code Page''' selection.<br />
<br />
=== Hard Disk Partitioning ===<br />
<br />
The various hard drive stages and boot loader options are skipped and the '''FreeBSD Disklabel Editor''' starts directly.<br />
<br />
This could be because dual-booting and co-existing with other operating systems is not possible under this architecture.<br />
<br />
=== Networking ===<br />
<br />
The '''Network interface information required''' page will list the available (recognised) Ethernet cards installed. The on-board network card is supported by the 'hme' driver, known (and listed on-screen) as the "Happy Meal Ethernet" adaptor. Other network cards, if installed and are compatible, will also be listed.<br />
<br />
Most, if not all, PCI network cards supported by the x86 release should be supported by the UltraSPARC release.<br />
<br />
== Settings used ==<br />
<br />
During the installation on a real Ultra 5 system the following choices were used.<br />
<br />
The hard drive was split up into the following [[slices]]:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
! Part<br />
! Mount<br />
! Size<br />
! NewFS<br />
|-<br />
| ad0a<br />
| /<br />
| 512MB<br />
| UFS2 Y<br />
|-<br />
| ad0b<br />
| <br />
| 1024MB<br />
| SWAP<br />
|-<br />
| ad0d<br />
| /var<br />
| 1024MB<br />
| UFS2+s Y<br />
|-<br />
| ad0e<br />
| /tmp<br />
| 512MB<br />
| UFS2+S Y<br />
|-<br />
| ad0f<br />
| /usr<br />
| 32768MB<br />
| UFS2+S Y<br />
|-<br />
| ad0g<br />
| /svr<br />
| 114GB<br />
| UFS2+S Y<br />
|-<br />
|}<br />
<br />
The 'SWAP' is set to 2x the on-board RAM size (a FreeBSD system recommendation). The '/usr' splice is 32GB, but shown as 32768MB on the screen. The '/svr' slice used the remainder of the disk, which happened to be 114GB of the 160GB capacity (give-or-take) and exists as a place to hose the 'server' specific data instead of the default '/usr' locations.<br />
<br />
[[Category : Installation]]</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_Ultra_5Installation on Ultra 52008-09-10T10:40:59Z<p>DrModiford: Added link to Sun Microsystems Hardware</p>
<hr />
<div>The following guide covers the initiation of an installation of FreeBSD on the [[Sun Microsystems Hardware|Sun Microsystems]]' Ultra 5 platform. This should be suitable for the Ultra 10 platform, a faster and improved variant of the Ultra 5. It does not cover the entire installation, which is similar to an installation of FreeBSD on x86. It simply covers the starting of the installer to the point of similarity.<br />
<br />
== Pre-requisites ==<br />
<br />
The specific SPARC-based installation media must be downloaded (or purchased through one of the affiliated on-line stores) - the x86-based installation media will not work! If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the Ultra 5 uses the [[OpenBoot]] system to initiate system start-up, the equivalent of the ubiquitous PC BIOS, accessing it is different to what you may be used to coming from the PC world. Upon starting up and viewing the white boot screen (featuring the Sun classic logo and various system details) the key combination 'Stop' and the letter 'A' must be pressed together. This results in a prompt that simply states: "ok".<br />
<br />
This allows commands to be typed that control the system's start-up. For example, typing "probe-ide" and pressing enter will reveal the devices attached to the IDE ports. Typically one hard drive and a CD-ROM will be revealed though that is dependant on the installed hardware.<br />
<br />
== Initiating the FreeBSD installer ==<br />
<br />
With the OpenBoot system in command mode (see above how to interrupt system start-up) and the FreeBSD for SPARC installation cd-rom in the drive, type the following command to begin the process:<br />
<br />
ok '''boot cdrom /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== Installing FreeBSD ==<br />
<br />
After a short while with lots of information scrolling across the screen the familiar '''Country Selection''' page appears. From this point the installation becomes the same as an x86-based installation.<br />
<br />
Please refer to [[Installing FreeBSD - Standard Installation|this guide]] for continued installation instructions.<br />
<br />
== Booting FreeBSD ==<br />
<br />
Following a successful installation the system will reboot and attempt to load an operating system. If the system fails to load type the following command to begin the process:<br />
<br />
ok '''boot disk /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== FreeBSD on UltraSPARC specific issues ==<br />
<br />
The following lists some variations to the typical x86-based installation.<br />
<br />
=== Country Selection ===<br />
<br />
This page does not follow to the prompt for '''Code Page''' selection.<br />
<br />
=== Hard Disk Partitioning ===<br />
<br />
The various hard drive stages and boot loader options are skipped and the '''FreeBSD Disklabel Editor''' starts directly.<br />
<br />
This could be because dual-booting and co-existing with other operating systems is not possible under this architecture.<br />
<br />
=== Networking ===<br />
<br />
The '''Network interface information required''' page will list the available (recognised) Ethernet cards installed. The on-board network card is supported by the 'hme' driver, known (and listed on-screen) as the "Happy Meal Ethernet" adaptor. Other network cards, if installed and are compatible, will also be listed.<br />
<br />
Most, if not all, PCI network cards supported by the x86 release should be supported by the UltraSPARC release.<br />
<br />
== Settings used ==<br />
<br />
During the installation on a real Ultra 5 system the following choices were used.<br />
<br />
The hard drive was split up into the following [[slices]]:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
! Part<br />
! Mount<br />
! Size<br />
! NewFS<br />
|-<br />
| ad0a<br />
| /<br />
| 512MB<br />
| UFS2 Y<br />
|-<br />
| ad0b<br />
| /<br />
| 1024MB<br />
| SWAP<br />
|-<br />
| ad0d<br />
| /var<br />
| 1024MB<br />
| UFS2+s Y<br />
|-<br />
| ad0e<br />
| /tmp<br />
| 512MB<br />
| UFS2+S Y<br />
|-<br />
| ad0f<br />
| /usr<br />
| 32768MB<br />
| UFS2+S Y<br />
|-<br />
| ad0g<br />
| /svr<br />
| 114GB<br />
| UFS2+S Y<br />
|-<br />
|}<br />
<br />
The 'SWAP' is set to 2x the on-board RAM size (a FreeBSD system recommendation). The '/usr' splice is 32GB, but shown as 32768MB on the screen. The '/svr' slice used the remainder of the disk, which happened to be 114GB of the 160GB capacity (give-or-take) and exists as a place to hose the 'server' specific data instead of the default '/usr' locations.<br />
<br />
[[Category : Installation]]</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_Ultra_5Installation on Ultra 52008-09-10T10:40:13Z<p>DrModiford: Added to category Installation</p>
<hr />
<div>The following guide covers the initiation of an installation of FreeBSD on the Sun Microsystems' Ultra 5 platform. This should be suitable for the Ultra 10 platform, a faster and improved variant of the Ultra 5. It does not cover the entire installation, which is similar to an installation of FreeBSD on x86. It simply covers the starting of the installer to the point of similarity.<br />
<br />
== Pre-requisites ==<br />
<br />
The specific SPARC-based installation media must be downloaded (or purchased through one of the affiliated on-line stores) - the x86-based installation media will not work! If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the Ultra 5 uses the [[OpenBoot]] system to initiate system start-up, the equivalent of the ubiquitous PC BIOS, accessing it is different to what you may be used to coming from the PC world. Upon starting up and viewing the white boot screen (featuring the Sun classic logo and various system details) the key combination 'Stop' and the letter 'A' must be pressed together. This results in a prompt that simply states: "ok".<br />
<br />
This allows commands to be typed that control the system's start-up. For example, typing "probe-ide" and pressing enter will reveal the devices attached to the IDE ports. Typically one hard drive and a CD-ROM will be revealed though that is dependant on the installed hardware.<br />
<br />
== Initiating the FreeBSD installer ==<br />
<br />
With the OpenBoot system in command mode (see above how to interrupt system start-up) and the FreeBSD for SPARC installation cd-rom in the drive, type the following command to begin the process:<br />
<br />
ok '''boot cdrom /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== Installing FreeBSD ==<br />
<br />
After a short while with lots of information scrolling across the screen the familiar '''Country Selection''' page appears. From this point the installation becomes the same as an x86-based installation.<br />
<br />
Please refer to [[Installing FreeBSD - Standard Installation|this guide]] for continued installation instructions.<br />
<br />
== Booting FreeBSD ==<br />
<br />
Following a successful installation the system will reboot and attempt to load an operating system. If the system fails to load type the following command to begin the process:<br />
<br />
ok '''boot disk /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== FreeBSD on UltraSPARC specific issues ==<br />
<br />
The following lists some variations to the typical x86-based installation.<br />
<br />
=== Country Selection ===<br />
<br />
This page does not follow to the prompt for '''Code Page''' selection.<br />
<br />
=== Hard Disk Partitioning ===<br />
<br />
The various hard drive stages and boot loader options are skipped and the '''FreeBSD Disklabel Editor''' starts directly.<br />
<br />
This could be because dual-booting and co-existing with other operating systems is not possible under this architecture.<br />
<br />
=== Networking ===<br />
<br />
The '''Network interface information required''' page will list the available (recognised) Ethernet cards installed. The on-board network card is supported by the 'hme' driver, known (and listed on-screen) as the "Happy Meal Ethernet" adaptor. Other network cards, if installed and are compatible, will also be listed.<br />
<br />
Most, if not all, PCI network cards supported by the x86 release should be supported by the UltraSPARC release.<br />
<br />
== Settings used ==<br />
<br />
During the installation on a real Ultra 5 system the following choices were used.<br />
<br />
The hard drive was split up into the following [[slices]]:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
! Part<br />
! Mount<br />
! Size<br />
! NewFS<br />
|-<br />
| ad0a<br />
| /<br />
| 512MB<br />
| UFS2 Y<br />
|-<br />
| ad0b<br />
| /<br />
| 1024MB<br />
| SWAP<br />
|-<br />
| ad0d<br />
| /var<br />
| 1024MB<br />
| UFS2+s Y<br />
|-<br />
| ad0e<br />
| /tmp<br />
| 512MB<br />
| UFS2+S Y<br />
|-<br />
| ad0f<br />
| /usr<br />
| 32768MB<br />
| UFS2+S Y<br />
|-<br />
| ad0g<br />
| /svr<br />
| 114GB<br />
| UFS2+S Y<br />
|-<br />
|}<br />
<br />
The 'SWAP' is set to 2x the on-board RAM size (a FreeBSD system recommendation). The '/usr' splice is 32GB, but shown as 32768MB on the screen. The '/svr' slice used the remainder of the disk, which happened to be 114GB of the 160GB capacity (give-or-take) and exists as a place to hose the 'server' specific data instead of the default '/usr' locations.<br />
<br />
[[Category : Installation]]</div>DrModifordhttp://freebsdwiki.net/index.php/Sun_Microsystems_HardwareSun Microsystems Hardware2008-09-10T10:01:14Z<p>DrModiford: Also changed to x86 reference here</p>
<hr />
<div>The computing platforms produced by '''Sun Microsystems''' under the "Ultra" brand name are unique in the respect that they do use the ubiquitous Intel or AMD processors found on typical, commodity hardware in mainstream use today. The Ultra systems derive their name from the processors they use, called the UltraSPARC, a 64-bit CPU with model speeds from 270MHz to 400MHz originally released in the late 1990's (the then current Intel CPU of the time was the Pentium III running around 500MHz). Unlike the Intel and AMD processors that are based upon the complex 'i386' (sometimes referred to as 'x86') instruction set the SPARC processors use a simplified '[[RISC]]' based instruction set.<br />
<br />
The original operating system for Sun Microsystems was called [[Solaris]], a Unix-like operatins system similar to FreeBSD and Linux. This has since been released under an open source license. Today, numerous operating systems can run on the Sun UltraSPARC platform and FreeBSD is one of them.<br />
<br />
FreeBSD on the UltraSPARC platform is noted as being a Tier-2 release which means it runs, and is fairly stable, but not nearly as reliable and tested as FreeBSD for the x86-based i386 or AMD64 releases, which are themselves designated Tier-1. That said, FreeBSD is a worthy choice for an alternative operating system to bring a fresh use for that long-unused Ultra system in the corner of the room.<br />
<br />
Since the processors are different it is impossible to run software built on an x86 processor to run on an UltraSPARC processor. This is largely true of any processor architecture. Emulation is possible but is a slow solution. This is not a big issue when using FreeBSD since software installed using the [[ports]] system will be compiled for the specific processor of the running system.<br />
<br />
The following guides exist for those wanting to try FreeBSD on the Sun Microsystems range of hardware platforms.<br />
<br />
* Installation of FreeBSD for SPARC on the [[Installation on Ultra 5|Ultra 5]] system;</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_Ultra_5Installation on Ultra 52008-09-10T10:00:05Z<p>DrModiford: Changed i386 + AMD64 to simply x86 (not strictly correct, but should be well known enough for people to understand the meaning)</p>
<hr />
<div>The following guide covers the initiation of an installation of FreeBSD on the Sun Microsystems' Ultra 5 platform. This should be suitable for the Ultra 10 platform, a faster and improved variant of the Ultra 5. It does not cover the entire installation, which is similar to an installation of FreeBSD on x86. It simply covers the starting of the installer to the point of similarity.<br />
<br />
== Pre-requisites ==<br />
<br />
The specific SPARC-based installation media must be downloaded (or purchased through one of the affiliated on-line stores) - the x86-based installation media will not work! If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the Ultra 5 uses the [[OpenBoot]] system to initiate system start-up, the equivalent of the ubiquitous PC BIOS, accessing it is different to what you may be used to coming from the PC world. Upon starting up and viewing the white boot screen (featuring the Sun classic logo and various system details) the key combination 'Stop' and the letter 'A' must be pressed together. This results in a prompt that simply states: "ok".<br />
<br />
This allows commands to be typed that control the system's start-up. For example, typing "probe-ide" and pressing enter will reveal the devices attached to the IDE ports. Typically one hard drive and a CD-ROM will be revealed though that is dependant on the installed hardware.<br />
<br />
== Initiating the FreeBSD installer ==<br />
<br />
With the OpenBoot system in command mode (see above how to interrupt system start-up) and the FreeBSD for SPARC installation cd-rom in the drive, type the following command to begin the process:<br />
<br />
ok '''boot cdrom /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== Installing FreeBSD ==<br />
<br />
After a short while with lots of information scrolling across the screen the familiar '''Country Selection''' page appears. From this point the installation becomes the same as an x86-based installation.<br />
<br />
Please refer to [[Installing FreeBSD - Standard Installation|this guide]] for continued installation instructions.<br />
<br />
== Booting FreeBSD ==<br />
<br />
Following a successful installation the system will reboot and attempt to load an operating system. If the system fails to load type the following command to begin the process:<br />
<br />
ok '''boot disk /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== FreeBSD on UltraSPARC specific issues ==<br />
<br />
The following lists some variations to the typical x86-based installation.<br />
<br />
=== Country Selection ===<br />
<br />
This page does not follow to the prompt for '''Code Page''' selection.<br />
<br />
=== Hard Disk Partitioning ===<br />
<br />
The various hard drive stages and boot loader options are skipped and the '''FreeBSD Disklabel Editor''' starts directly.<br />
<br />
This could be because dual-booting and co-existing with other operating systems is not possible under this architecture.<br />
<br />
=== Networking ===<br />
<br />
The '''Network interface information required''' page will list the available (recognised) Ethernet cards installed. The on-board network card is supported by the 'hme' driver, known (and listed on-screen) as the "Happy Meal Ethernet" adaptor. Other network cards, if installed and are compatible, will also be listed.<br />
<br />
Most, if not all, PCI network cards supported by the x86 release should be supported by the UltraSPARC release.<br />
<br />
== Settings used ==<br />
<br />
During the installation on a real Ultra 5 system the following choices were used.<br />
<br />
The hard drive was split up into the following [[slices]]:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
! Part<br />
! Mount<br />
! Size<br />
! NewFS<br />
|-<br />
| ad0a<br />
| /<br />
| 512MB<br />
| UFS2 Y<br />
|-<br />
| ad0b<br />
| /<br />
| 1024MB<br />
| SWAP<br />
|-<br />
| ad0d<br />
| /var<br />
| 1024MB<br />
| UFS2+s Y<br />
|-<br />
| ad0e<br />
| /tmp<br />
| 512MB<br />
| UFS2+S Y<br />
|-<br />
| ad0f<br />
| /usr<br />
| 32768MB<br />
| UFS2+S Y<br />
|-<br />
| ad0g<br />
| /svr<br />
| 114GB<br />
| UFS2+S Y<br />
|-<br />
|}<br />
<br />
The 'SWAP' is set to 2x the on-board RAM size (a FreeBSD system recommendation). The '/usr' splice is 32GB, but shown as 32768MB on the screen. The '/svr' slice used the remainder of the disk, which happened to be 114GB of the 160GB capacity (give-or-take) and exists as a place to hose the 'server' specific data instead of the default '/usr' locations.</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_Ultra_5Installation on Ultra 52008-09-10T09:59:01Z<p>DrModiford: </p>
<hr />
<div>The following guide covers the initiation of an installation of FreeBSD on the Sun Microsystems' Ultra 5 platform. This should be suitable for the Ultra 10 platform, a faster and improved variant of the Ultra 5. It does not cover the entire installation, which is similar to an installation of FreeBSD on x86. It simply covers the starting of the installer to the point of similarity.<br />
<br />
== Pre-requisites ==<br />
<br />
The specific SPARC-based installation media must be downloaded (or purchased through one of the affiliated on-line stores) - the x86-based installation media will not work! If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the Ultra 5 uses the [[OpenBoot]] system to initiate system start-up, the equivalent of the ubiquitous PC BIOS, accessing it is different to what you may be used to coming from the PC world. Upon starting up and viewing the white boot screen (featuring the Sun classic logo and various system details) the key combination 'Stop' and the letter 'A' must be pressed together. This results in a prompt that simply states: "ok".<br />
<br />
This allows commands to be typed that control the system's start-up. For example, typing "probe-ide" and pressing enter will reveal the devices attached to the IDE ports. Typically one hard drive and a CD-ROM will be revealed though that is dependant on the installed hardware.<br />
<br />
== Initiating the FreeBSD installer ==<br />
<br />
With the OpenBoot system in command mode (see above how to interrupt system start-up) and the FreeBSD for SPARC installation cd-rom in the drive, type the following command to begin the process:<br />
<br />
ok '''boot cdrom /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== Installing FreeBSD ==<br />
<br />
After a short while with lots of information scrolling across the screen the familiar '''Country Selection''' page appears. From this point the installation becomes the same as an i386 or AMD64-based installation.<br />
<br />
Please refer to [[Installing FreeBSD - Standard Installation|this guide]] for continued installation instructions.<br />
<br />
== Booting FreeBSD ==<br />
<br />
Following a successful installation the system will reboot and attempt to load an operating system. If the system fails to load type the following command to begin the process:<br />
<br />
ok '''boot disk /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== FreeBSD on UltraSPARC specific issues ==<br />
<br />
The following lists some variations to the typical x86-based installation.<br />
<br />
=== Country Selection ===<br />
<br />
This page does not follow to the prompt for '''Code Page''' selection.<br />
<br />
=== Hard Disk Partitioning ===<br />
<br />
The various hard drive stages and boot loader options are skipped and the '''FreeBSD Disklabel Editor''' starts directly.<br />
<br />
This could be because dual-booting and co-existing with other operating systems is not possible under this architecture.<br />
<br />
=== Networking ===<br />
<br />
The '''Network interface information required''' page will list the available (recognised) Ethernet cards installed. The on-board network card is supported by the 'hme' driver, known (and listed on-screen) as the "Happy Meal Ethernet" adaptor. Other network cards, if installed and are compatible, will also be listed.<br />
<br />
Most, if not all, PCI network cards supported by the x86 release should be supported by the UltraSPARC release.<br />
<br />
== Settings used ==<br />
<br />
During the installation on a real Ultra 5 system the following choices were used.<br />
<br />
The hard drive was split up into the following [[slices]]:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
! Part<br />
! Mount<br />
! Size<br />
! NewFS<br />
|-<br />
| ad0a<br />
| /<br />
| 512MB<br />
| UFS2 Y<br />
|-<br />
| ad0b<br />
| /<br />
| 1024MB<br />
| SWAP<br />
|-<br />
| ad0d<br />
| /var<br />
| 1024MB<br />
| UFS2+s Y<br />
|-<br />
| ad0e<br />
| /tmp<br />
| 512MB<br />
| UFS2+S Y<br />
|-<br />
| ad0f<br />
| /usr<br />
| 32768MB<br />
| UFS2+S Y<br />
|-<br />
| ad0g<br />
| /svr<br />
| 114GB<br />
| UFS2+S Y<br />
|-<br />
|}<br />
<br />
The 'SWAP' is set to 2x the on-board RAM size (a FreeBSD system recommendation). The '/usr' splice is 32GB, but shown as 32768MB on the screen. The '/svr' slice used the remainder of the disk, which happened to be 114GB of the 160GB capacity (give-or-take) and exists as a place to hose the 'server' specific data instead of the default '/usr' locations.</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_Ultra_5Installation on Ultra 52008-09-10T09:39:29Z<p>DrModiford: Small change</p>
<hr />
<div>The following guide covers the initiation of an installation of FreeBSD on the Sun Microsystems' Ultra 5 platform. This should be suitable for the Ultra 10 platform, a faster and improved variant of the Ultra 5. It does not cover the entire installation, which is similar to an installation of FreeBSD of i386 or AMD. It simply covers the starting of the installer to the point of similarity.<br />
<br />
== Pre-requisites ==<br />
<br />
The specific SPARC-based installation media must be downloaded (or purchased through one of the affiliated on-line stores) - the i386 and AMD64-based installation media will not work! If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the Ultra 5 uses the [[OpenBoot]] system to initiate system start-up, the equivalent of the ubiquitous PC BIOS, accessing it is different to what you may be used to coming from the PC world. Upon starting up and viewing the white boot screen (featuring the Sun classic logo and various system details) the key combination 'Stop' and the letter 'A' must be pressed together. This results in a prompt that simply states: "ok".<br />
<br />
This allows commands to be typed that control the system's start-up. For example, typing "probe-ide" and pressing enter will reveal the devices attached to the IDE ports. Typically one hard drive and a CD-ROM will be revealed though that is dependant on the installed hardware.<br />
<br />
== Initiating the FreeBSD installer ==<br />
<br />
With the OpenBoot system in command mode (see above how to interrupt system start-up) and the FreeBSD for SPARC installation cd-rom in the drive, type the following command to begin the process:<br />
<br />
ok '''boot cdrom /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== Installing FreeBSD ==<br />
<br />
After a short while with lots of information scrolling across the screen the familiar '''Country Selection''' page appears. From this point the installation becomes the same as an i386 or AMD64-based installation.<br />
<br />
Please refer to [[Installing FreeBSD - Standard Installation|this guide]] for continued installation instructions.<br />
<br />
== Booting FreeBSD ==<br />
<br />
Following a successful installation the system will reboot and attempt to load an operating system. If the system fails to load type the following command to begin the process:<br />
<br />
ok '''boot disk /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== FreeBSD on UltraSPARC specific issues ==<br />
<br />
The following lists some variations to the typical x86-based installation.<br />
<br />
=== Country Selection ===<br />
<br />
This page does not follow to the prompt for '''Code Page''' selection.<br />
<br />
=== Hard Disk Partitioning ===<br />
<br />
The various hard drive stages and boot loader options are skipped and the '''FreeBSD Disklabel Editor''' starts directly.<br />
<br />
This could be because dual-booting and co-existing with other operating systems is not possible under this architecture.<br />
<br />
=== Networking ===<br />
<br />
The '''Network interface information required''' page will list the available (recognised) Ethernet cards installed. The on-board network card is supported by the 'hme' driver, known (and listed on-screen) as the "Happy Meal Ethernet" adaptor. Other network cards, if installed and are compatible, will also be listed.<br />
<br />
Most, if not all, PCI network cards supported by the x86 release should be supported by the UltraSPARC release.<br />
<br />
== Settings used ==<br />
<br />
During the installation on a real Ultra 5 system the following choices were used.<br />
<br />
The hard drive was split up into the following [[slices]]:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
! Part<br />
! Mount<br />
! Size<br />
! NewFS<br />
|-<br />
| ad0a<br />
| /<br />
| 512MB<br />
| UFS2 Y<br />
|-<br />
| ad0b<br />
| /<br />
| 1024MB<br />
| SWAP<br />
|-<br />
| ad0d<br />
| /var<br />
| 1024MB<br />
| UFS2+s Y<br />
|-<br />
| ad0e<br />
| /tmp<br />
| 512MB<br />
| UFS2+S Y<br />
|-<br />
| ad0f<br />
| /usr<br />
| 32768MB<br />
| UFS2+S Y<br />
|-<br />
| ad0g<br />
| /svr<br />
| 114GB<br />
| UFS2+S Y<br />
|-<br />
|}<br />
<br />
The 'SWAP' is set to 2x the on-board RAM size (a FreeBSD system recommendation). The '/usr' splice is 32GB, but shown as 32768MB on the screen. The '/svr' slice used the remainder of the disk, which happened to be 114GB of the 160GB capacity (give-or-take) and exists as a place to hose the 'server' specific data instead of the default '/usr' locations.</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_Ultra_5Installation on Ultra 52008-09-10T09:39:09Z<p>DrModiford: Small changes</p>
<hr />
<div>The following guide covers the initiation of an installation of FreeBSD on the Sun Microsystems' Ultra 5 platform. This should be suitable for the Ultra 10 platform, a faster and improved variant of the Ultra 5. It does not cover the entire installation, which is similar to an installation of FreeBSD of i386 or AMD. It simply covers the starting of the installer to the point of similarity.<br />
<br />
== Pre-requisites ==<br />
<br />
The specific SPARC-based installation media must be downloaded (or purchased through one of the affiliated on-line stores) - the i386 and AMD64-based installation media will not work! If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the Ultra 5 uses the [[OpenBoot]] system to initiate system start-up, the equivalent of the ubiquitous PC BIOS, accessing it is different to what you may be used to coming from the PC world. Upon starting up and viewing the white boot screen (featuring the Sun classic logo and various system details) the key combination 'Stop' and the letter 'A' must be pressed together. This results in a prompt that simply states: "ok".<br />
<br />
This allows commands to be typed that control the system's start-up. For example, typing "probe-ide" and pressing enter will reveal the devices attached to the IDE ports. Typically one hard drive and a CD-ROM will be revealed though that is dependant on the installed hardware.<br />
<br />
== Initiating the FreeBSD installer ==<br />
<br />
With the OpenBoot system in command mode (see above how to interrupt system start-up) and the FreeBSD for SPARC installation cd-rom in the drive, type the following command to begin the process:<br />
<br />
ok '''boot cdrom /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== Installing FreeBSD ==<br />
<br />
After a short while with lots of information scrolling across the screen the familiar '''Country Selection''' page appears. From this point the installation becomes the same as an i386 or AMD64-based installation.<br />
<br />
Please refer to [[Installing FreeBSD - Standard Installation|this guide]] for continued installation instructions.<br />
<br />
== Booting FreeBSD ==<br />
<br />
Following a successful installation the system will reboot and attempt to load an operating system. If the system fails to load type the following command to begin the process:<br />
<br />
ok '''boot disk /boot/loader''' (press Enter)<br />
<br />
== FreeBSD on UltraSPARC specific issues ==<br />
<br />
The following lists some variations to the typical x86-based installation.<br />
<br />
=== Country Selection ===<br />
<br />
This page does not follow to the prompt for '''Code Page''' selection.<br />
<br />
=== Hard Disk Partitioning ===<br />
<br />
The various hard drive stages and boot loader options are skipped and the '''FreeBSD Disklabel Editor''' starts directly.<br />
<br />
This could be because dual-booting and co-existing with other operating systems is not possible under this architecture.<br />
<br />
=== Networking ===<br />
<br />
The '''Network interface information required''' page will list the available (recognised) Ethernet cards installed. The on-board network card is supported by the 'hme' driver, known (and listed on-screen) as the "Happy Meal Ethernet" adaptor. Other network cards, if installed and are compatible, will also be listed.<br />
<br />
Most, if not all, PCI network cards supported by the x86 release should be supported by the UltraSPARC release.<br />
<br />
== Settings used ==<br />
<br />
During the installation on a real Ultra 5 system the following choices were used.<br />
<br />
The hard drive was split up into the following [[slices]]:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
! Part<br />
! Mount<br />
! Size<br />
! NewFS<br />
|-<br />
| ad0a<br />
| /<br />
| 512MB<br />
| UFS2 Y<br />
|-<br />
| ad0b<br />
| /<br />
| 1024MB<br />
| SWAP<br />
|-<br />
| ad0d<br />
| /var<br />
| 1024MB<br />
| UFS2+s Y<br />
|-<br />
| ad0e<br />
| /tmp<br />
| 512MB<br />
| UFS2+S Y<br />
|-<br />
| ad0f<br />
| /usr<br />
| 32768MB<br />
| UFS2+S Y<br />
|-<br />
| ad0g<br />
| /svr<br />
| 114GB<br />
| UFS2+S Y<br />
|-<br />
|}<br />
<br />
The 'SWAP' is set to 2x the on-board RAM size (a FreeBSD system recommendation). The '/usr' splice is 32GB, but shown as 32768MB on the screen. The '/svr' slice used the remainder of the disk, which happened to be 114GB of the 160GB capacity (give-or-take) and exists as a place to hose the 'server' specific data instead of the default '/usr' locations.</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_Ultra_5Installation on Ultra 52008-09-10T09:37:46Z<p>DrModiford: Post-installation booting</p>
<hr />
<div>The following guide covers the initiation of an installation of FreeBSD on the Sun Microsystems' Ultra 5 platform. This should be suitable for the Ultra 10 platform, a faster and improved variant of the Ultra 5. It does not cover the entire installation, which is similar to an installation of FreeBSD of i386 or AMD. It simply covers the starting of the installer to the point of similarity.<br />
<br />
== Pre-requisites ==<br />
<br />
The specific SPARC-based installation media must be downloaded (or purchased through one of the affiliated on-line stores) - the i386 and AMD64-based installation media will not work! If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the Ultra 5 uses the [[OpenBoot]] system to initiate system start-up, the equivalent of the ubiquitous PC BIOS, accessing it is different to what you may be used to coming from the PC world. Upon starting up and viewing the white boot screen (featuring the Sun classic logo and various system details) the key combination 'Stop' and the letter 'A' must be pressed together. This results in a prompt that simply states: "ok".<br />
<br />
This allows commands to be typed that control the system's start-up. For example, typing "probe-ide" and pressing enter will reveal the devices attached to the IDE ports. Typically one hard drive and a CD-ROM will be revealed though that is dependant on the installed hardware.<br />
<br />
== Initiating the FreeBSD installer ==<br />
<br />
With the OpenBoot system in command mode (see above how to interrupt system start-up) and the FreeBSD for SPARC installation cd-rom in the drive, type the following command to begin the process:<br />
<br />
ok '''boot cdrom /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== Installing FreeBSD ==<br />
<br />
After a short while with lots of information scrolling across the screen the familiar '''Country Selection''' page appears. From this point the installation becomes the same as an i386 or AMD64-based installation.<br />
<br />
Please refer to [[Installing FreeBSD - Standard Installation|this guide]] for continued installation instructions.<br />
<br />
== Booting FreeBSD ==<br />
<br />
Following a successful installation the system will reboot and attempt to load an operating system. If the system fails to load the following command should be used:<br />
<br />
ok '''boot disk /boot/loader''' [press enter]<br />
<br />
<br />
== FreeBSD on UltraSPARC specific issues ==<br />
<br />
The following lists some variations to the typical x86-based installation.<br />
<br />
=== Country Selection ===<br />
<br />
This page does not follow to the prompt for '''Code Page''' selection.<br />
<br />
=== Hard Disk Partitioning ===<br />
<br />
The various hard drive stages and boot loader options are skipped and the '''FreeBSD Disklabel Editor''' starts directly.<br />
<br />
This could be because dual-booting and co-existing with other operating systems is not possible under this architecture.<br />
<br />
=== Networking ===<br />
<br />
The '''Network interface information required''' page will list the available (recognised) Ethernet cards installed. The on-board network card is supported by the 'hme' driver, known (and listed on-screen) as the "Happy Meal Ethernet" adaptor. Other network cards, if installed and are compatible, will also be listed.<br />
<br />
Most, if not all, PCI network cards supported by the x86 release should be supported by the UltraSPARC release.<br />
<br />
== Settings used ==<br />
<br />
During the installation on a real Ultra 5 system the following choices were used.<br />
<br />
The hard drive was split up into the following [[slices]]:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
! Part<br />
! Mount<br />
! Size<br />
! NewFS<br />
|-<br />
| ad0a<br />
| /<br />
| 512MB<br />
| UFS2 Y<br />
|-<br />
| ad0b<br />
| /<br />
| 1024MB<br />
| SWAP<br />
|-<br />
| ad0d<br />
| /var<br />
| 1024MB<br />
| UFS2+s Y<br />
|-<br />
| ad0e<br />
| /tmp<br />
| 512MB<br />
| UFS2+S Y<br />
|-<br />
| ad0f<br />
| /usr<br />
| 32768MB<br />
| UFS2+S Y<br />
|-<br />
| ad0g<br />
| /svr<br />
| 114GB<br />
| UFS2+S Y<br />
|-<br />
|}<br />
<br />
The 'SWAP' is set to 2x the on-board RAM size (a FreeBSD system recommendation). The '/usr' splice is 32GB, but shown as 32768MB on the screen. The '/svr' slice used the remainder of the disk, which happened to be 114GB of the 160GB capacity (give-or-take) and exists as a place to hose the 'server' specific data instead of the default '/usr' locations.</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_Ultra_5Installation on Ultra 52008-09-10T09:12:39Z<p>DrModiford: Further additions</p>
<hr />
<div>The following guide covers the initiation of an installation of FreeBSD on the Sun Microsystems' Ultra 5 platform. This should be suitable for the Ultra 10 platform, a faster and improved variant of the Ultra 5. It does not cover the entire installation, which is similar to an installation of FreeBSD of i386 or AMD. It simply covers the starting of the installer to the point of similarity.<br />
<br />
== Pre-requisites ==<br />
<br />
The specific SPARC-based installation media must be downloaded (or purchased through one of the affiliated on-line stores) - the i386 and AMD64-based installation media will not work! If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the Ultra 5 uses the [[OpenBoot]] system to initiate system start-up, the equivalent of the ubiquitous PC BIOS, accessing it is different to what you may be used to coming from the PC world. Upon starting up and viewing the white boot screen (featuring the Sun classic logo and various system details) the key combination 'Stop' and the letter 'A' must be pressed together. This results in a prompt that simply states: "ok".<br />
<br />
This allows commands to be typed that control the system's start-up. For example, typing "probe-ide" and pressing enter will reveal the devices attached to the IDE ports. Typically one hard drive and a CD-ROM will be revealed though that is dependant on the installed hardware.<br />
<br />
== Initiating the FreeBSD installer ==<br />
<br />
With the OpenBoot system in command mode (see above how to interrupt system start-up) and the FreeBSD for SPARC installation cd-rom in the drive, type the following command to begin the process:<br />
<br />
ok '''boot cdrom /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== Installing FreeBSD ==<br />
<br />
After a short while with lots of information scrolling across the screen the familiar '''Country Selection''' page appears. From this point the installation becomes the same as an i386 or AMD64-based installation.<br />
<br />
Please refer to [[Installing FreeBSD - Standard Installation|this guide]] for continued installation instructions.<br />
<br />
== FreeBSD on UltraSPARC specific issues ==<br />
<br />
The following lists some variations to the typical x86-based installation.<br />
<br />
=== Country Selection ===<br />
<br />
This page does not follow to the prompt for '''Code Page''' selection.<br />
<br />
=== Hard Disk Partitioning ===<br />
<br />
The various hard drive stages and boot loader options are skipped and the '''FreeBSD Disklabel Editor''' starts directly.<br />
<br />
This could be because dual-booting and co-existing with other operating systems is not possible under this architecture.<br />
<br />
=== Networking ===<br />
<br />
The '''Network interface information required''' page will list the available (recognised) Ethernet cards installed. The on-board network card is supported by the 'hme' driver, known (and listed on-screen) as the "Happy Meal Ethernet" adaptor. Other network cards, if installed and are compatible, will also be listed.<br />
<br />
Most, if not all, PCI network cards supported by the x86 release should be supported by the UltraSPARC release.<br />
<br />
== Settings used ==<br />
<br />
During the installation on a real Ultra 5 system the following choices were used.<br />
<br />
The hard drive was split up into the following [[slices]]:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
! Part<br />
! Mount<br />
! Size<br />
! NewFS<br />
|-<br />
| ad0a<br />
| /<br />
| 512MB<br />
| UFS2 Y<br />
|-<br />
| ad0b<br />
| /<br />
| 1024MB<br />
| SWAP<br />
|-<br />
| ad0d<br />
| /var<br />
| 1024MB<br />
| UFS2+s Y<br />
|-<br />
| ad0e<br />
| /tmp<br />
| 512MB<br />
| UFS2+S Y<br />
|-<br />
| ad0f<br />
| /usr<br />
| 32768MB<br />
| UFS2+S Y<br />
|-<br />
| ad0g<br />
| /svr<br />
| 114GB<br />
| UFS2+S Y<br />
|-<br />
|}<br />
<br />
The 'SWAP' is set to 2x the on-board RAM size (a FreeBSD system recommendation). The '/usr' splice is 32GB, but shown as 32768MB on the screen. The '/svr' slice used the remainder of the disk, which happened to be 114GB of the 160GB capacity (give-or-take) and exists as a place to hose the 'server' specific data instead of the default '/usr' locations.</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_Ultra_5Installation on Ultra 52008-09-10T08:59:32Z<p>DrModiford: typo on size</p>
<hr />
<div>The following guide covers the initiation of an installation of FreeBSD on the Sun Microsystems' Ultra 5 platform. This should be suitable for the Ultra 10 platform, a faster and improved variant of the Ultra 5. It does not cover the entire installation, which is similar to an installation of FreeBSD of i386 or AMD. It simply covers the starting of the installer to the point of similarity.<br />
<br />
== Pre-requisites ==<br />
<br />
The specific SPARC-based installation media must be downloaded (or purchased through one of the affiliated on-line stores) - the i386 and AMD64-based installation media will not work! If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the Ultra 5 uses the [[OpenBoot]] system to initiate system start-up, the equivalent of the ubiquitous PC BIOS, accessing it is different to what you may be used to coming from the PC world. Upon starting up and viewing the white boot screen (featuring the Sun classic logo and various system details) the key combination 'Stop' and the letter 'A' must be pressed together. This results in a prompt that simply states: "ok".<br />
<br />
This allows commands to be typed that control the system's start-up. For example, typing "probe-ide" and pressing enter will reveal the devices attached to the IDE ports. Typically one hard drive and a CD-ROM will be revealed though that is dependant on the installed hardware.<br />
<br />
== Initiating the FreeBSD installer ==<br />
<br />
With the OpenBoot system in command mode (see above how to interrupt system start-up) and the FreeBSD for SPARC installation cd-rom in the drive, type the following command to begin the process:<br />
<br />
ok '''boot cdrom /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== Installing FreeBSD ==<br />
<br />
After a short while with lots of information scrolling across the screen the familiar '''Country Selection''' page appears. From this point the installation becomes the same as an i386 or AMD64-based installation.<br />
<br />
Please refer to [[Installing FreeBSD - Standard Installation|this guide]] for continued installation instructions.<br />
<br />
== FreeBSD of UltraSPARC specific issues ==<br />
<br />
* The '''Country Selection''' page does not prompt for '''Code Page''' selection;<br />
* The '''FDisk Partition Editor''' and other boot loader options are skipped and the '''FreeBSD Disklabel Editor''' starts directly. This could because dual-booting and existing with other operating systems is not possible under this architecture.<br />
<br />
== Settings used ==<br />
<br />
During the installation on a real Ultra 5 system the following choices were used.<br />
<br />
The hard drive was split up into the following [[slices]]:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
! Part<br />
! Mount<br />
! Size<br />
! NewFS<br />
|-<br />
| ad0a<br />
| /<br />
| 512MB<br />
| UFS2 Y<br />
|-<br />
| ad0b<br />
| /<br />
| 1024MB<br />
| SWAP<br />
|-<br />
| ad0d<br />
| /var<br />
| 1024MB<br />
| UFS2+s Y<br />
|-<br />
| ad0e<br />
| /tmp<br />
| 512MB<br />
| UFS2+S Y<br />
|-<br />
| ad0f<br />
| /usr<br />
| 32768MB<br />
| UFS2+S Y<br />
|-<br />
| ad0g<br />
| /svr<br />
| 114GB<br />
| UFS2+S Y<br />
|-<br />
|}<br />
<br />
The 'SWAP' is set to 2x the on-board RAM size (a FreeBSD system recommendation). The '/usr' splice is 32GB, but shown as 32768MB on the screen. The '/svr' slice used the remainder of the disk, which happened to be 114GB of the 160GB capacity (give-or-take) and exists as a place to hose the 'server' specific data instead of the default '/usr' locations.</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_Ultra_5Installation on Ultra 52008-09-10T08:56:50Z<p>DrModiford: Added settings used sub-section (to be specific how the Ultra 5 here was setup)</p>
<hr />
<div>The following guide covers the initiation of an installation of FreeBSD on the Sun Microsystems' Ultra 5 platform. This should be suitable for the Ultra 10 platform, a faster and improved variant of the Ultra 5. It does not cover the entire installation, which is similar to an installation of FreeBSD of i386 or AMD. It simply covers the starting of the installer to the point of similarity.<br />
<br />
== Pre-requisites ==<br />
<br />
The specific SPARC-based installation media must be downloaded (or purchased through one of the affiliated on-line stores) - the i386 and AMD64-based installation media will not work! If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the Ultra 5 uses the [[OpenBoot]] system to initiate system start-up, the equivalent of the ubiquitous PC BIOS, accessing it is different to what you may be used to coming from the PC world. Upon starting up and viewing the white boot screen (featuring the Sun classic logo and various system details) the key combination 'Stop' and the letter 'A' must be pressed together. This results in a prompt that simply states: "ok".<br />
<br />
This allows commands to be typed that control the system's start-up. For example, typing "probe-ide" and pressing enter will reveal the devices attached to the IDE ports. Typically one hard drive and a CD-ROM will be revealed though that is dependant on the installed hardware.<br />
<br />
== Initiating the FreeBSD installer ==<br />
<br />
With the OpenBoot system in command mode (see above how to interrupt system start-up) and the FreeBSD for SPARC installation cd-rom in the drive, type the following command to begin the process:<br />
<br />
ok '''boot cdrom /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== Installing FreeBSD ==<br />
<br />
After a short while with lots of information scrolling across the screen the familiar '''Country Selection''' page appears. From this point the installation becomes the same as an i386 or AMD64-based installation.<br />
<br />
Please refer to [[Installing FreeBSD - Standard Installation|this guide]] for continued installation instructions.<br />
<br />
== FreeBSD of UltraSPARC specific issues ==<br />
<br />
* The '''Country Selection''' page does not prompt for '''Code Page''' selection;<br />
* The '''FDisk Partition Editor''' and other boot loader options are skipped and the '''FreeBSD Disklabel Editor''' starts directly. This could because dual-booting and existing with other operating systems is not possible under this architecture.<br />
<br />
== Settings used ==<br />
<br />
During the installation on a real Ultra 5 system the following choices were used.<br />
<br />
The hard drive was split up into the following [[slices]]:<br />
<br />
{| border="1" cellpadding="5" cellspacing="0"<br />
|-<br />
! Part<br />
! Mount<br />
! Size<br />
! NewFS<br />
|-<br />
| ad0a<br />
| /<br />
| 512MB<br />
| UFS2 Y<br />
|-<br />
| ad0b<br />
| /<br />
| 1024MB<br />
| SWAP<br />
|-<br />
| ad0d<br />
| /var<br />
| 1024MB<br />
| UFS2+s Y<br />
|-<br />
| ad0e<br />
| /tmp<br />
| 512MB<br />
| UFS2+S Y<br />
|-<br />
| ad0f<br />
| /usr<br />
| 532768MB<br />
| UFS2+S Y<br />
|-<br />
| ad0g<br />
| /svr<br />
| 114GB<br />
| UFS2+S Y<br />
|-<br />
|}<br />
<br />
The '/svr' slice used the remainder of the disk, which happened to be 114GB of the 160GB capacity (give-or-take) and exists as a place to hose the 'server' specific data instead of the default '/usr' locations.</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_Ultra_5Installation on Ultra 52008-09-10T08:26:55Z<p>DrModiford: Added last sub-section for the 'gotcha's on UltraSPARC</p>
<hr />
<div>The following guide covers the initiation of an installation of FreeBSD on the Sun Microsystems' Ultra 5 platform. This should be suitable for the Ultra 10 platform, a faster and improved variant of the Ultra 5. It does not cover the entire installation, which is similar to an installation of FreeBSD of i386 or AMD. It simply covers the starting of the installer to the point of similarity.<br />
<br />
== Pre-requisites ==<br />
<br />
The specific SPARC-based installation media must be downloaded (or purchased through one of the affiliated on-line stores) - the i386 and AMD64-based installation media will not work! If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the Ultra 5 uses the [[OpenBoot]] system to initiate system start-up, the equivalent of the ubiquitous PC BIOS, accessing it is different to what you may be used to coming from the PC world. Upon starting up and viewing the white boot screen (featuring the Sun classic logo and various system details) the key combination 'Stop' and the letter 'A' must be pressed together. This results in a prompt that simply states: "ok".<br />
<br />
This allows commands to be typed that control the system's start-up. For example, typing "probe-ide" and pressing enter will reveal the devices attached to the IDE ports. Typically one hard drive and a CD-ROM will be revealed though that is dependant on the installed hardware.<br />
<br />
== Initiating the FreeBSD installer ==<br />
<br />
With the OpenBoot system in command mode (see above how to interrupt system start-up) and the FreeBSD for SPARC installation cd-rom in the drive, type the following command to begin the process:<br />
<br />
ok '''boot cdrom /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
== Installing FreeBSD ==<br />
<br />
After a short while with lots of information scrolling across the screen the familiar '''Country Selection''' page appears. From this point the installation becomes the same as an i386 or AMD64-based installation.<br />
<br />
Please refer to [[Installing FreeBSD - Standard Installation|this guide]] for continued installation instructions.<br />
<br />
== FreeBSD of UltraSPARC specific issues ==</div>DrModifordhttp://freebsdwiki.net/index.php/Installation_on_Ultra_5Installation on Ultra 52008-09-10T08:25:08Z<p>DrModiford: Specific guide to starting FreeBSD installation of Ultra 5 (possibly Ultra 10) to the point of similarity to the i386 based install</p>
<hr />
<div>The following guide covers the initiation of an installation of FreeBSD on the Sun Microsystems' Ultra 5 platform. This should be suitable for the Ultra 10 platform, a faster and improved variant of the Ultra 5. It does not cover the entire installation, which is similar to an installation of FreeBSD of i386 or AMD. It simply covers the starting of the installer to the point of similarity.<br />
<br />
== Pre-requisites ==<br />
<br />
The specific SPARC-based installation media must be downloaded (or purchased through one of the affiliated on-line stores) - the i386 and AMD64-based installation media will not work! If using the [[ports]] system only CD1 is required for the base system installation.<br />
<br />
Since the Ultra 5 uses the [[OpenBoot]] system to initiate system start-up, the equivalent of the ubiquitous PC BIOS, accessing it is different to what you may be used to coming from the PC world. Upon starting up and viewing the white boot screen (featuring the Sun classic logo and various system details) the key combination 'Stop' and the letter 'A' must be pressed together. This results in a prompt that simply states: "ok".<br />
<br />
This allows commands to be typed that control the system's start-up. For example, typing "probe-ide" and pressing enter will reveal the devices attached to the IDE ports. Typically one hard drive and a CD-ROM will be revealed though that is dependant on the installed hardware.<br />
<br />
== Initiating the FreeBSD installer ==<br />
<br />
With the OpenBoot system in command mode (see above how to interrupt system start-up) and the FreeBSD for SPARC installation cd-rom in the drive, type the following command to begin the process:<br />
<br />
ok '''boot cdrom /boot/loader''' (press Enter)<br />
<br />
'''Note:''' The ''ok'' above is the command prompt, so enter only the part in '''bold-type'''.<br />
<br />
After a short while with lots of information scrolling across the screen the familiar '''Country Selection''' page appears. From this point the installation becomes the same as an i386 or AMD64-based installation. Please refer to this guide for continued installation instructions.</div>DrModifordhttp://freebsdwiki.net/index.php/Sun_Microsystems_HardwareSun Microsystems Hardware2008-09-10T08:02:30Z<p>DrModiford: Grrrr, it's been a while!</p>
<hr />
<div>The computing platforms produced by '''Sun Microsystems''' under the "Ultra" brand name are unique in the respect that they do use the ubiquitous Intel or AMD processors found on typical, commodity hardware in mainstream use today. The Ultra systems derive their name from the processors they use, called the UltraSPARC, a 64-bit CPU with model speeds from 270MHz to 400MHz originally released in the late 1990's (the then current Intel CPU of the time was the Pentium III running around 500MHz). Unlike the Intel and AMD processors that are based upon the complex 'i386' instruction set the SPARC processors use a simplified '[[RISC]]' based instruction set.<br />
<br />
The original operating system for Sun Microsystems was called [[Solaris]], a Unix-like operatins system similar to FreeBSD and Linux. This has since been released under an open source license. Today, numerous operating systems can run on the Sun UltraSPARC platform and FreeBSD is one of them.<br />
<br />
FreeBSD on the UltraSPARC platform is noted as being a Tier-2 release which means it runs, and is fairly stable, but not nearly as reliable and tested as FreeBSD for i386 or AMD64 releases, which are themselves designated Tier-1. That said, FreeBSD is a worthy choice for an alternative operating system to bring a fresh use for that long-unused Ultra system in the corner of the room.<br />
<br />
Since the processors are different it is impossible to run software built on an i386 processor to run on an UltraSPARC processor. This is largely true of any processor architecture. Emulation is possible but is a slow solution. This is not a big issue when using FreeBSD since software installed using the [[ports]] system will be compiled for the specific processor of the running system.<br />
<br />
The following guides exist for those wanting to try FreeBSD on the Sun Microsystems range of hardware platforms.<br />
<br />
* Installation of FreeBSD for SPARC on the [[Installation on Ultra 5|Ultra 5]] system;</div>DrModifordhttp://freebsdwiki.net/index.php/Sun_Microsystems_HardwareSun Microsystems Hardware2008-09-10T08:02:16Z<p>DrModiford: Formatting error</p>
<hr />
<div>The computing platforms produced by ''Sun Microsystems'' under the "Ultra" brand name are unique in the respect that they do use the ubiquitous Intel or AMD processors found on typical, commodity hardware in mainstream use today. The Ultra systems derive their name from the processors they use, called the UltraSPARC, a 64-bit CPU with model speeds from 270MHz to 400MHz originally released in the late 1990's (the then current Intel CPU of the time was the Pentium III running around 500MHz). Unlike the Intel and AMD processors that are based upon the complex 'i386' instruction set the SPARC processors use a simplified '[[RISC]]' based instruction set.<br />
<br />
The original operating system for Sun Microsystems was called [[Solaris]], a Unix-like operatins system similar to FreeBSD and Linux. This has since been released under an open source license. Today, numerous operating systems can run on the Sun UltraSPARC platform and FreeBSD is one of them.<br />
<br />
FreeBSD on the UltraSPARC platform is noted as being a Tier-2 release which means it runs, and is fairly stable, but not nearly as reliable and tested as FreeBSD for i386 or AMD64 releases, which are themselves designated Tier-1. That said, FreeBSD is a worthy choice for an alternative operating system to bring a fresh use for that long-unused Ultra system in the corner of the room.<br />
<br />
Since the processors are different it is impossible to run software built on an i386 processor to run on an UltraSPARC processor. This is largely true of any processor architecture. Emulation is possible but is a slow solution. This is not a big issue when using FreeBSD since software installed using the [[ports]] system will be compiled for the specific processor of the running system.<br />
<br />
The following guides exist for those wanting to try FreeBSD on the Sun Microsystems range of hardware platforms.<br />
<br />
* Installation of FreeBSD for SPARC on the [[Installation on Ultra 5|Ultra 5]] system;</div>DrModifordhttp://freebsdwiki.net/index.php/Sun_Microsystems_HardwareSun Microsystems Hardware2008-09-10T08:01:50Z<p>DrModiford: Created article covering Sun Microsystems hardware, with link to guide for the Ulta 5 (to be written while running a real installation)</p>
<hr />
<div><br />
The computing platforms produced by '''Sun Microsystems'' under the Ultra brand name are unique in the respect that they do use the ubiquitous Intel or AMD processors found on typical, commodity hardware in mainstream use today. The Ultra systems derive their name from the processors they use, called the UltraSPARC, a 64-bit CPU with model speeds from 270MHz to 400MHz originally released in the late 1990's (the then current Intel CPU of the time was the Pentium III running around 500MHz). Unlike the Intel and AMD processors that are based upon the complex 'i386' instruction set the SPARC processors use a simplified '[[RISC]]' based instruction set.<br />
<br />
The original operating system for Sun Microsystems was called [[Solaris]], a Unix-like operatins system similar to FreeBSD and Linux. This has since been released under an open source license. Today, numerous operating systems can run on the Sun UltraSPARC platform and FreeBSD is one of them.<br />
<br />
FreeBSD on the UltraSPARC platform is noted as being a Tier-2 release which means it runs, and is fairly stable, but not nearly as reliable and tested as FreeBSD for i386 or AMD64 releases, which are themselves designated Tier-1. That said, FreeBSD is a worthy choice for an alternative operating system to bring a fresh use for that long-unused Ultra system in the corner of the room.<br />
<br />
Since the processors are different it is impossible to run software built on an i386 processor to run on an UltraSPARC processor. This is largely true of any processor architecture. Emulation is possible but is a slow solution. This is not a big issue when using FreeBSD since software installed using the [[ports]] system will be compiled for the specific processor of the running system.<br />
<br />
The following guides exist for those wanting to try FreeBSD on the Sun Microsystems range of hardware platforms.<br />
<br />
* Installation of FreeBSD for SPARC on the [[Installation on Ultra 5|Ultra 5]] system;</div>DrModifordhttp://freebsdwiki.net/index.php/Network_Attached_StorageNetwork Attached Storage2008-08-03T22:50:56Z<p>DrModiford: Added homepagefor FreeNAS and m0n0wall</p>
<hr />
<div>Network Attached Storage, often shortened to NAS, as implied by the name is a form of file storage made available to the network. An early example of such a system would be the Unix-World's own [[NFS]] service, where a file system store is available from across a network.<br />
<br />
Typically a NAS system has a role of a server though it does not always take the form of a typical server, such as those that are usually rack-mounted and made by HP or Dell. Some come in a small, near portable form factor, with an embedded operating system. All that is needed for these devices to function is a power supply and a network lead. These usually have a web-based configuration utility similar to those found in home broadband routers. Obviously a real server affords the luxury of [[RAID]]-enabled storage and multiple network cards and a "full-featured" operating system.<br />
<br />
Dependant on the intended audience for a NAS server will dictate the types of protocols it will serve. The majority of portable NAS servers support [[CIFS]] (formerly [[SMB]] by Microsoft, known as [[Samba]] on [[Open Source]] operating systems) since the market share will already have Windows-based operating systems that natively support it. Other, more advanced, NAS servers have the capability to provide protocols for NFS, FTP, WEBDAV, AFP, iSCSI, UPnP as alternatives to CIFS alone.<br />
<br />
FreeBSD can support NFS and FTP natively and CIFS through the open source implementation called [[Samba]] as well as initial support for [[iSCSI]] (as a "target" in iSCSI terminology) and other 'www'-borne protocols.<br />
<br />
There is an active project called [[FreeNAS]] ([http://www.freenas.org official homepage])from which the name takes two meanings. The obvious is that it is a free implementation of a NAS server. The other is that it refers to the fact that it is based on FreeBSD. It is technically based on the work of the FreeBSD-derived firewall project called [[m0n0wall]] (note the use of zeros in the name, [http://m0n0.ch official homepage]), a stripped down FreeBSD operating system for embedded, dedicated-use projects such as firewalling and NAS serving. FreeNAS can take an old or low specification computer that is no longer used and, when fitted with a modest sized hard drive, turn it into a fully functional NAS server supporting CIFS, NFS, FTP, AFP, iSCSI and UPnP, backup systems [[rsync|RSYNC]] and [[Unison]] and Dynamic DNS functionality.</div>DrModifordhttp://freebsdwiki.net/index.php/NASNAS2008-08-03T22:48:13Z<p>DrModiford: NAS to Network Attached Storage (redirect)</p>
<hr />
<div>#REDIRECT [[Network Attached Storage]]</div>DrModifordhttp://freebsdwiki.net/index.php/Network_Attached_StorageNetwork Attached Storage2008-08-03T22:47:11Z<p>DrModiford: Few changes</p>
<hr />
<div>Network Attached Storage, often shortened to NAS, as implied by the name is a form of file storage made available to the network. An early example of such a system would be the Unix-World's own [[NFS]] service, where a file system store is available from across a network.<br />
<br />
Typically a NAS system has a role of a server though it does not always take the form of a typical server, such as those that are usually rack-mounted and made by HP or Dell. Some come in a small, near portable form factor, with an embedded operating system. All that is needed for these devices to function is a power supply and a network lead. These usually have a web-based configuration utility similar to those found in home broadband routers. Obviously a real server affords the luxury of [[RAID]]-enabled storage and multiple network cards and a "full-featured" operating system.<br />
<br />
Dependant on the intended audience for a NAS server will dictate the types of protocols it will serve. The majority of portable NAS servers support [[CIFS]] (formerly [[SMB]] by Microsoft, known as [[Samba]] on [[Open Source]] operating systems) since the market share will already have Windows-based operating systems that natively support it. Other, more advanced, NAS servers have the capability to provide protocols for NFS, FTP, WEBDAV, AFP, iSCSI, UPnP as alternatives to CIFS alone.<br />
<br />
FreeBSD can support NFS and FTP natively and CIFS through the open source implementation called [[Samba]] as well as initial support for [[iSCSI]] (as a "target" in iSCSI terminology) and other 'www'-borne protocols.<br />
<br />
There is an active project called [[FreeNAS]] from which the name takes two meanings. The obvious is that it is a free implementation of a NAS server. The other is that it refers to the fact that it is based on FreeBSD. It is technically based on the work of the FreeBSD-derived firewall project called [[m0n0wall]] (note the use of zeros in the name), a stripped down FreeBSD operating system for embedded, dedicated-use projects such as firewalling and NAS serving. FreeNAS can take an old or low specification computer that is no longer used and, when fitted with a modest sized hard drive, turn it into a fully functional NAS server supporting CIFS, NFS, FTP, AFP, iSCSI and UPnP, backup systems [[rsync|RSYNC]] and [[Unison]] and Dynamic DNS functionality.</div>DrModifordhttp://freebsdwiki.net/index.php/Network_Attached_StorageNetwork Attached Storage2008-08-03T22:45:37Z<p>DrModiford: Initial page covering NAS systems</p>
<hr />
<div>Network Attached Storage, often shortened to NAS, as implied by the name is a form of file storage made available to the network. An early example of such a system would be the Unix-World's own [[NFS]] service, where a file system store is available from across a network.<br />
<br />
Typically a NAS system has a role of a server though it does not always take the form of a typical server, such as those that are usually rack-mounted and made by HP or Dell. Some come in a small, near portable form factor, with an embedded operating system. All that is needed for these devices to function is a power supply and a network lead. These usually have a web-based configuration utility similar to those found in home broadband routers. Obviously a real server affords the luxury of [[RAID]]-enabled storage and multiple network cards and a "full-featured" operating system.<br />
<br />
Dependant on the intended audience for a NAS server will dictate the types of protocols it will serve. The majority of portable NAS servers support [[CIFS]] (formerly [[SMB]] by Microsoft, known as [[SAMBA]] on [[Open Source]] operating systems) since the market share will already have Windows-based operating systems that natively support it. Other, more advanced, NAS servers have the capability to provide protocols for NFS, FTP, WEBDAV, AFP, iSCSI, UPnP as alternatives to CIFS alone.<br />
<br />
FreeBSD can support NFS and FTP natively and CIFS through the open source implementation called [[Samba]] as well as initial support for [[iSCSI]] (as a "target" in iSCSI terminology) and other 'www'-borne protocols.<br />
<br />
There is an active project called [[FreeNAS]] from which the name takes two meanings. The obvious is that it is a free implementation of a NAS server. The other is that it refers to the fact that it is based on FreeBSD. It is technically based on the work of the FreeBSD-derived firewall project called [[m0n0wall]] (note the use of zeros in the name), a stripped down FreeBSD operating system for embedded, dedicated-use projects such as firewalling and NAS serving. FreeNAS can take an old or low specification computer that is no longer used and, when fitted with a modest sized hard drive, turn it into a fully functional NAS server supporting CIFS, NFS, FTP, AFP, iSCSI and UPnP, backup systems [[RSYNC]] and [[Unison]] and Dynamic DNS functionality.</div>DrModifordhttp://freebsdwiki.net/index.php/Talk:NFSTalk:NFS2008-08-03T22:14:42Z<p>DrModiford: Citrix XenServer compatibility confirmed</p>
<hr />
<div>For anyone interested Citrix XenServer (including the 'free' four-guest limited release) can be configured to utilise a FreeBSD server running NFS as a shared storage, despite no official documented reference to this being the case on the Citrix website as at time of writing (it appears implied that the 'free' release does not allow NFS usage - I ([[User:DrModiford]]) currently have a test lab at the office working from NFS for both guest images and ISO files).</div>DrModifordhttp://freebsdwiki.net/index.php/User:DrModifordUser:DrModiford2008-07-21T14:31:49Z<p>DrModiford: Added uptime (well, I'm impressed with it!)</p>
<hr />
<div>Okay, so I'm not really a doctor...<br />
<br />
= About =<br />
<br />
I started out on a Commodore 16 back when I was four and progressed through various computing platforms, most notably Windows and then Linux, before discovering FreeBSD several years ago. Since then I have had a long-term love affair with this operating system!<br />
<br />
I live in the offshore finance centre of Guernsey, part of the Channel Islands which sit between the mainlands of UK and France, and work within the IT department of a fiduciary (trust / finance industry) company.<br />
<br />
= Knowledge =<br />
<br />
I have been privileged through my career to have used many different computing platforms from the humble BBC Micro to large-scale IBM AS/400s. After discovering FreeBSD I became proficient at deploying, implementing and maintaining it in both personal and corporate environments.<br />
<br />
At home it has been used to host my web and email server over an ADSL connection and as a Samba file server to store music and movies.<br />
<br />
In the office it is used to monitor network traffic with MRTG, host an internal Wikipedia for application development documentation, allow marketing to mass-mail intermediaries using qmail and host SecureFTP file distribution on-line. Recently a Subversion server was requested by the development team and was installed within moments from the fantastic [[ports]] system.<br />
<br />
= Contact =<br />
<br />
I look forward to chatting with any like-minded FreeBSD users out there. I can be contacted on:<br />
<br />
* ICQ: 59-397-985 or;<br />
* MSN: glynb at hotmail dot co dot uk (hotmail used to be a FreeBSD house once!)<br />
<br />
Of course, I use those accounts through KDE [[Kopete]] on a laptop running PC-BSD!<br />
<br />
= Up Time =<br />
<br />
Just to prove the reliability of FreeBSD as a server operating system, here's my uptime:<br />
<br />
%uptime<br />
3:23PM up '''386 days''', 16:01, 2 users, load averages: 0.00, 0.00, 0.00<br />
<br />
...also proves that the electricity supply in Guernsey is extremely reliable as that server is not on a UPS either!<br />
<br />
It's just a shame that I have to power it off in order move my servers into a new location within the house :'-( *sniff*</div>DrModifordhttp://freebsdwiki.net/index.php/MkfifoMkfifo2008-06-13T12:21:59Z<p>DrModiford: Missing 'in'</p>
<hr />
<div>{{System-Commands}}<br />
<br />
The '''mkfifo''', or Make First-In First-Out, command creates a form of 'pipe' somewhere on the file system with special properties. This pipe can be thought of as a file in the traditional, or physical, sense in that it can be written-to and read-from however it takes it one step further by allowing two separate process to have access to it; one process writes to it while another process reads from it and in the order entries were made. As such it is often referred to as 'half-duplex' because only one write or one read can happen at a time. This makes it a form of 'data buffer'.<br />
<br />
In reality the 'fifo' pipe exists in memory. It is a form of virtual link, similar to file system entry created by the [[ln|link]] command. As such it is limited by available system memory. That said the pipe is persistent and will survive a reboot '''but the data within it will not''', the fifo entry remains in place until it is removed by issuing a [[rm|remove]] command.<br />
<br />
[[Category:System Commands]]</div>DrModiford