3 ms·
I always wanted to try FreeBSD, but during install, after I picked the software I wanted it would ask me for disk 10, then disk 7, then disk 5... I proceeded to
by giancarlostoro 12y ago
I always wanted to try FreeBSD, but during install, after I picked the software I wanted it would ask me for disk 10, then disk 7, then disk 5... I proceeded to giving up and installing Slackware instead (this was back in 2007 when I was new to Linux). I hope they've fixed this since, or maybe I did something wrong, who knows? Oh well...
- elektronjunge 12y agoYou can install from a flash drive or single dvd. They've been working fairly heavily on the install process in versions 9 and 10. EDIT: I thought about this more after submitting. The many disks are likely for seeding the ports tree. If you have an internet connection available or opt to not install the ports tree you can install off much smaller media.
- Zancarius 12y agoI don't think the ports tree is quite that big, at least when it's compressed (presently ~220ish megs for FreeBSD 10 as a tgz), because ports only contain Makefiles and descriptive metadata. It used to be the case, I think, that the extra disc images were for installing applications outside the base distributions and the likes as they themselves contained a snapshot of some of the binary archives for a given release. I don't know for sure, though, because I always used ports (which is better and obviously more up to date).
- rootbear 12y agoI plan to try out PC-BSD (which is basically FreeBSD with all the desktop GUI stuff set up for you) when they get their 10.1 version out. I've been told by actual FreeBSD folks that it's the least painful way to get into FreeBSD.
- Zancarius 12y agoI suspect you probably selected CDROM at the time as your software source, which can be confounding for new users. The best solution in this case is to either install binary packages via selecting FTP as your source or (better) via ports. Also, I generally avoid installing extra software outside the base packages until after the system is installed, as this was a problem that could crop up when installing earlier versions (not really a problem per se as much as if it's something you weren't familiar with, it may do unexpected things). If you install some of the tools in ports-mgmt (portupgrade, for instance, which includes portinstall), you can make the ports collection far easier to manage and use, and it might be more approachable for new users. Not that it's difficult to do a make && make install from the port you want. I haven't touched FreeBSD in years, so I'd imagine the installer is a bit more forgiving now. That said, my experience with the ports collection was what lead me to select Gentoo for my Linux preferences (later, and more presently, Arch). But, I have very fond memories of using ports, and I think everyone has their preferred methods. The trick is to neither give in or give up and play around with it until you're familiar and have picked tools you're comfortable with (this holds true for almost anything)! I'd suggest giving it another shot. Edit: I lied. Apparently I have a FreeBSD 10 vm, so it hasn't been years. I don't remember the new installation procedure at all, sadly.
- jrapdx3 12y agoI have FBSD 10.x running in VM and production, and I'd agree it's probably best to install the OS first before trying to add applications. In my experience following this policy leaves fewer ways for things to get screwed up. Re: the ports collection, as a former Gentoo/Funtoo user I felt as you describe. But I think the current FBSD package system is better. Unless there's a special use case, it's generally quite satisfactory and a whole lot easier to download and install apps using the "pkg" utility, rather than messing with ports at all. IMO the FBSD developers have been doing a terrific job of making the OS better without making it tons harder to administer. There's still a learning curve for sure (e.g., ZFS) but it's not insurmountable.
- Zancarius 12y ago> In my experience following this policy leaves fewer ways for things to get screwed up. Definitely. I still do this for exactly that reason. Unnecessarily complicating the installation process is just a recipe for frustration unless you have a well tested build script. > But I think the current FBSD package system is better. This is true. I don't have much experience with the "new" package system, because I (mostly) stopped using FreeBSD ~5.x with some more recent usage in the 8.x and 9.x series. I've dabbled in it since, rarely, but I think the old habit of "install everything via ports" is so ingrained in some of us whose FreeBSD use dates back that it's a bit difficult to overcome. :) I'll familiarize myself with it one of these days, perhaps, but the disenchantment with Gentoo is largely the reason I use Arch now and it'd be great to use something similar under a BSD. Rolling release + binary packages = vastly nicer than waiting for hours for Xorg/KDE/Gnome/whatever to build. As a fellow former Gentoo user, I hope that if you read this, I won't have triggered unfortunate flashbacks or painful memories as a consequence of mentioning this. ;) If new(ish) users come across this thread, follow jrapdx3's suggestion and learn pkg--it's supposed to be really nice and circumvents some of the old ways of doing things. FreeBSD has, IMO, done a great job of mixing something like a rolling release platform with a well-tested and stable kernel/environment. It's almost the best of both worlds, though some things might be a bit tedious to get running. (Is Java still a colossal pain?) > IMO the FBSD developers have been doing a terrific job of making the OS better without making it tons harder to administer. Here's another thing: FreeBSD is consistent. So much so that even if you return to using it after years, things still* work more or less the same, and that old knowledge transfers well (within reason). I can't really say the same for Arch, for instance, because there's usually a hugely disruptive change every 6-12 months. I love Arch (I'm using it right now), but sometimes the drastic changes can be ... surprising.
- rhizome 12y agoJust install base + src + ports and install everything you want afterwards. Much simpler.
- seliopou 12y agoThat's funny, I had the exact opposite experience. Back in 2002-ish I was trying to install Slackware and LILO kept failing for some reason I couldn't understand. That turned me off to Linux distro. So I went looking for an alternative and came upon FreeBSD. For personal computer *NIX installations, I haven't looked back. Though of Linux dominated sever installations in the subsequent years, I think the tides are changing and will be using FreeBSD for my next project. Say hello to dtrace and zfs. Can't wait.