"I don't think so"
Well, of course nobody has to "type a couple commands" if they don't want to. lol You said better than anybody else with, "It's just MY opinion." The moment someone chooses to disregard another persons opinion and tries to force-feed them their own opinion on a subject is the moment they begin blowing gas out their a$$. ;)
Those advocating CLI have a valid point.
Those advocating GUI have a valid point.
It sounds like you're simply saying that you like GUI and don't like CLI. That's totally cool... I don't hear anybody bible-beatin' ya otherwise. <grin>
Well, I DID try.
Are you referring to PC-BSD or another *BSD?
What did you try?
Problem was, the thing never worked and I just wiped it off the partition and installed Solaris 10 instead
Awesome! In my opinion, Solaris is an excellent OS. Sun has revolutionized computing on many occasions.
(which is a true UNIX with a working GUI at boot).
:neutral: Just a heads up: you might want to be careful with a statement like that.
If you want to get into semantics - and not start a "flame war" - then UNIX (not Unix or unix) is a product of AT&T... not Sun. Yes, there have been relations between the two, even among many other *nix systems, though a "true" "UNIX" in the all-caps sense is nothing of the sort.
If you are referring to SysV, then Solaris... which is from Sun... which is currently known as a SysV system... did not originate from SysV alone but, rather, 4.1BSD and V7. Yes. BSD was there in the beginning of Sun.
It is true that BSD came from UNIX, which included the different Editions (including V5), though code from both "BSD" and "SysV" type systems were included in the original Sun operating system. (Using "SysV" generically as the "mostly non-BSD Unix".)
Here's a very condensed and extremely truncated look at *nix timeline, and I'll only
include the systems that have been mentioned recently in this (our OpenBSD) thread, and I'll include Linux basics since this is a linux forum:
1969, UNIX (as UNICS), at AT&T/Bell Labs.
1971, UNIX V1, "UNIX Time-Sharing System First Edition (V1)".
1975, V6.
1978, 1BSD (with a V6 influence).
1981, UNIX System III (late-1981).
1982, SunOS (from 4.1BSD and UniSoft UniPlus (V7)).
1983, UNIX System V ("SysV").
1984, Minix (late-1984, with a 4.1BSD and V7 influence, eventually spawned Linux).
1984, GNU.
1985, FSF.
1986, 4.3BSD.
1987, Minix (version 1.0).
1988, OSF.
1990, SunOS 4.1.1 is given an additional title, Solaris 1 (which includes 4.3BSD).
1991, BSD Net/2 (4.3BSD influence, later NetBSD, FreeBSD, and OpenBSD).
1991, Linux (0.01) (mid-1991, with a Minix influence).
1992, Solaris 2 (both x86 and sparc architectures), a second line of Solaris.
1993, AT&T sales UNIX to Novell (January 1993).
1993, NetBSD (early 1993, which eventually spawned OpenBSD).
1993, Slackware Linux (released in July, spawns SuSE (Novell now owns) and more).
1993, Debian Linux (released in August, spawns Ubuntu and more).
1993, FreeBSD (late 1993, which eventually spawned PC-BSD).
1994, Red Hat Linux.
1994, Novell gives "UNIX" trademark to The Open Group (aka "X/Open Company").
1994, Novell sales UNIX source code to SCO.
1995, OpenBSD (with a NetBSD influence).
1999, Enoch Linux (renamed to Gentoo Linux in 2002).
2002, Arch Linux.
2004, Ubuntu Linux (released in October, Debian influence).
2005, Solaris 10 ("official" release, from SunOS).
2005, OpenSolaris (about 6 months after Solaris 10).
2005, PC-BSD (mid-2005, with a FreeBSD influence).
2008, FreeBSD 7.0 (early-2008 ).
2008, PC-BSD 7 (mid-to-late-2008 ).
2008, Ubuntu 8.10 (10/08 ).
2008, Solaris 10 10/08.
2008, OpenBSD 4.4 (10/08 ).
In 1987, AT&T's system (the real UNIX) and Sun's system (a Unix spawn) united. This spawned the OSF, another evolution of open source, which was a response to the proprietary contracts between AT&T and Sun. In other words, BSD started branching out and expanding as a response to the AT&T/Sun deal.
In 1993, AT&T sold UNIX to Novell. More branching out and expanding of all *nix systems took place at this point, notably of the open source variety. The three early big dogs of BSD (NetBSD, FreeBSD, OpenBSD) and the three early big dogs of Linux (Slackware, Debian, and Red Hat) were developed, from which the plethora of other systems were spawned.
In 1994, Novell gave the UNIX name to the Open Group and sold the UNIX source code to SCO. The rest is history.
This was also the early stage of general SysV+BSD merging, which has since developed into an extremely interchangeable aspect of all *nix systems.
The real UNIX, by name and by code, is presently only one system - not multiple systems - although the multiple Unix (not UNIX) systems and Unix-based (not Unix) systems, aka GNU/Linux, that we have today inevitably share some of that UNIX code. The real UNIX includes the likes of UNIX 93, UNIX 95, UNIX 98, UNIX 03. What we have and classify as POSIX compliant, among all *nix systems, is based off of UNIX. There is also more of an open source involvement with UNIX now than there used to be.
When you get into the GUI of all of these systems, you immediately introduce the open community of software development to the "operating system", which includes anything on top of the kernel.
Even Solaris, in the more recent revisions of version 10, has an extremely Linux-friendly foundation, including the GUI. Likewise, the *BSD operating systems have also had the extremely Linux-friendly foundation, including the GUI.
All in all, in response to your:
"...which is a true UNIX with a working GUI at boot..."
I have to say...
Regarding the "UNIX" specification:
All Unix and Linux set-ups are "true" Unix-like systems. However, none of them - not even Solaris - are true UNIX systems.
In other words: There can be only one. (...and Solaris ain't it.)
Regarding a working GUI at boot:
The vast majority of Unix and Linux installs include GUI as defaults to boot to. This includes OpenBSD - when you go through the install process you are given the option of installing X, which is a GUI.
Also note the different types of GUIs, especially DEs and WMs.
A destktop environment (DE) is something like GNOME and KDE.
A window manager (WM) is something like Fluxbox and FVWM.
Note the differences:
DE = a WM with extra applications bundled/packaged together.
WM = the GUI environment without the extra packages.
When you install OpenBSD, for example, you are given an initial X (GUI) environment, a WM specifically. If you want a DE like GNOME, you can do something like this:
1. Find your OpenBSD mirror at http://www.openbsd.org (http://www.openbsd.org/) (for installing apps).
2. Set up your package path so you can add packages:
$ export pkg_path=ftp://<your.ftp.mirror>/pub/OpenBSD/4.4/packages/`machine -a`/ (Or replace 4.4 with a newer version when OpenBSD releases future versions.)
You can also add the path to your root's profile, open this in a text editor:
/root/.profile ...and add these 2 lines:
export pkg_path=ftp://your.ftp.mirror/pub/OpenBSD/4.4/packages/`machine -a`/
export fetch_packages=yes (We work with the "root" account's profile since we use either "sudo" or "su", aka root, to install/remove/etc. packages. If you are an Ubuntu user who is scared of using a root account, then you might opt to do a little research on the benefits of using root. I advocate using root, though that's just me... though, I do not advocate use of root by someone or anyone who is likely to screw up the computer. lol)
Remember:
With great power comes great responsibility. 3. Add your packages:
You'll probably want both GNOME and the GNOME log-in manager, which are "gnome-session" and "gdm", respectively.
$ sudo pkg_add gnome-session-2.20.3p11.tgz
$ sudo pkg_add gdm-2.20.2p6.tgz You can add flags/options to the pkg_add command if you like, such as "-i" for interactive, "-v" for verbose, or more.
4. Set up your new GUI to load at boot:
echo "/usr/local/bin/gdm -nodaemon &" >> /etc/rc.local 5. Add "/usr/local/bin" to your PATH environment, within "/root/.profile" if it's not already:
PATH=$HOME/bin:/bin:/sbin:/usr/bin:/usr/X11R6/bin:/usr/local/bin:/usr/local/sbin (This will let your binaries in your user's local path load.)
(Make sure there is not a "." or ":." at the end of the PATH line (for security purposes.))
Note that you can install either of 2 basic ways:
A) ports (/usr/ports, not recommended)
You can refer to this link for more: http://www.openbsd.org/ports.html
or
B) packages (pkg_path and pkg_add, the recommended way)
You can refer to this link for more: http://www.openbsd.org/faq/faq15.html#Easy
Ports = compile from source, which is okay, and offers more flexibility, though could be time-consuming and take up more space during the install process.
Packages = the "pkg_" type commands are part of OpenBSD's package management system, which still offers flexibility, though it installs apps faster and without consuming more space during the install process.
Some additional "pkg_" commands...
View what you have installed:
pkg_infoUpdates:
pkg_add -u <applications>Deinstall applications:
pkg_delete <applications>That is almost as easy as typing "ls -la" or anything of that sort. :)
Using the command line isn't as bad as it might seem at first. Once you get the hang of things - the simple commands - you can more comfortably take on the more complex commands.
Just for the heck of it, I'll include more goodies:
A. Install ports tree:
1. Download the following files from the ..."/pub/OpenBSD/"...(etc.) directory:
src.tar.gz
ports.tar.gz 2. Unzip/untar the src file into:
/usr/src/ ...and unzip/untar the ports file into:
/usr/ports/ In other words, do this:
cd /usr/src/
tar xvfz /mnt/cdrom/src.tar.gz
cd /usr/
tar xvfz /mnt/cdrom/ports.tar.gzB. Set up Java:
1. Retrieve Sun JDK (newest version) via:
http://download.java.net/tiger/tiger_u12/
You'll want the files with this info in their names:
jdk-*src*jar
jdk-*bin*jar
2. Retrieve bsd-jdk*patches*.tar.bz2 via:
http://www.eyesbeyond.com/freebsddom/java/jdk15.html
(...links might refer to JDK 1.5, you may need a newer version.)
3. Retrieve jdk-*solaris*<arch>*.tar.Z via:
http://java.sun.com/products/archive/j2se/5.0_12/index.html
4. Retriev xalan-j*-bin.tar.gz via:
http://www.apache.org/dist/xml/xalan-j/
If you're curious why Java is a more involved install process, feel free to ask Theo de Raadt. lol. <wink>
5. Check for possible manual fetching of files:
Go to "/usr/ports/devel/jdk/<version>" and type "make" (no quotes).
It may ask for your guidance if necessary, though will provide address and file that it needs. Download the files to this directory: "/usr/ports/distfiles/". Continue the build.
6. Follow any steps that you are prompted with after installation if you'd like to apply Java plugins to extra apps like browsers.
7. Add Java executable to your shell config file:
If you're using Korn shell, go into "~/.profile" (if you're using BASH, go into "~/.bashrc"). Find the PATH environment in the profile and add this to it: "/usr/local/jdk-<yourversion>/bin" (make sure there is no "." at the end).
8. Some apps require "java_home", add this line to that file: "export JAVA_HOME=/usr/local/jdk-<yourversion>/" (and log out and back in).
C. Enable Linux (binary support):
This part - along everything else, except Java - can be fairly simple if you follow the correct steps/process.
1. Edit this config file:
/etc/sysctl.conf Uncomment the lines of your choice, such as Linux support:
kern.emul.linux=1 2. Install "fedora_base" via pkg_add.
3. Create "/proc".
4. Update "fstab" (/etc/fstab) file, adding this line: "/proc /proc procfs rw,linux 0 0"
D. SMP support for dual-core, quad-core, etc.:
1. If you are using a computer with a multi-core CPU, install "bsd.mp" (copy it to your root ("/") directory).
2. Test bsd.mp at boot prompt, prior to init. Type "bsd.mp" (no quotes) and press enter.
3. Make the change permanent by going to the / (root) directory and typing:
mv bsd.mp bsd I could go on and on... but this is already lengthy enough of a post.
I hope it helps. :D