Here for the same purpose.
I have a computer with two mirrored zfs disks, but no OS.
I boot with PXE and mount the root from my Desktop.
The biggest problem is the case, small tower, but too big, with Intel atom main board.
I would like to have...
You laugh, but it is a small, usable piece of software that in my opinion deserves to be in base.
I did not mean that, but just the idea of using Rust or other language in the kernel together with C.
The industry has abandoned NIS. Sun replaced NIS with NIS+. Oracle has moved on to LDAP.
Personally, I replaced my NIS on FreeBSD with OpenLDAP + Kerberos. It works just as well and is more secure.
NIS is scheduled for removal.
For telnet and...
ftpd, telnetd, rsh, rscp, etc are sure useful on local networks, unthinkable today in the internet.
In any case, FreeBSD was till now a box with surprises, in base and in ports/packages, one always found something new and usable.
Now things are...
I wanted zfs for long term backup.
Perhaps I should make a NAS with zfs on linux / FreeBSD, or Hammer ob DragonFly BSD.
The only think I wanted is the self-healing using the checksums on mirroring raid.
I read a little further on in that netbsd zfs wiki.
"Known Problems
zfs is prone to full-system lockups. They seem to be related to heavyzfs activity, especially writing data or deleting files, while at thesame time there is memory pressure...
Well, hold the horses.
I have seen ports removed because the original software is "unmaintained" (didn't have changes lately) when clearly that software was just a working, enclosed, finished system. There is some software that is just finished...
I use it now at $JOB. It shouldn't be in the base O/S. But RH supports multiple versions of whatever just like we do in ports. RH does /etc/alternatives. That's a mess but it does what they advertise it to do.
Perl was in base but it didn't integrate into the build so it was removed from base about 25 years ago. Why? It uses GNU configure. Base doesn't. Perl scripts are sensitive to the version of the Perl interpreter. It made more sense to remove it...
There's nothing wrong with moving stuff from base to ports to keep it tidy and manageable. Stuff like the r* commands, the FTP daemon and others belong in ports.
My opinions only, again "what you paid for them" :)
Removing something from base: to me that implies "should it have been in base to begin with". Scripting languages: should a separate version be maintained in base or should a version be...
And I generally refuse to run anything with DRM. If something has DRM, I try to crack it. (Not endorsing piracy here, I still legally buy the game I crack)
Proponents of PkgBase and other terrible ideas mainly. FreeBSD is going to be hit quite badly by this unfortunately and I would rather watch from the sidelines.
I have migrated most of my machines to OpenBSD. Quite happy so far.
I don't...
Well, hold the horses.
I have seen ports removed because the original software is "unmaintained" (didn't have changes lately) when clearly that software was just a working, enclosed, finished system. There is some software that is just finished...
Celsius -- Erik Wøllo
View: https://www.youtube.com/watch?v=e8SOMB7HOHQ
From this album (released on 19-Oct-25):
View: https://www.youtube.com/watch?v=bu6HsFTl1_4
Another think that attracts me is the lot of ports, but there are a lot of unmaintained, interesting ports.
It will come the time at which they will become unportable.
iirc, a lot of stuff is in git to be ported to FreeBSD. Also, a lot of developers have gotten used to it from their jobs or working with Linux. iow, everyone else was doing it.
Updates (sec and other) will hit ports tree a few days before updated pkg will be available in the repo, so it depends on user needs and role.
IMHO:
If user is an admin at $DAYJOB having their own poudriere repo is smart thing to do anyways...
There's nothing wrong with moving stuff from base to ports to keep it tidy and manageable. Stuff like the r* commands, the FTP daemon and others belong in ports.
Agreed. You can see a good example of that on this recent OpenBSD mail list thread.
(some idiot wanted to start removing stuff because "they didn't need it and its old")
There are a couple of companies currently trying to monetize FreeBSD, so...
My opinions only, again "what you paid for them" :)
Removing something from base: to me that implies "should it have been in base to begin with". Scripting languages: should a separate version be maintained in base or should a version be...
They provide a display server but none provide a full fledged GUI system.
Agreed. And the above is why. Your opionions about a good GUI is likely very different to mine which in turn is very different to some random Steam DRM platform gamer...
Perl was in base but it didn't integrate into the build so it was removed from base about 25 years ago. Why? It uses GNU configure. Base doesn't. Perl scripts are sensitive to the version of the Perl interpreter. It made more sense to remove it...
Agreed. You can see a good example of that on this recent OpenBSD mail list thread.
(some idiot wanted to start removing stuff because "they didn't need it and its old")
There are a couple of companies currently trying to monetize FreeBSD, so...
They provide a display server but none provide a full fledged GUI system.
Agreed. And the above is why. Your opionions about a good GUI is likely very different to mine which in turn is very different to some random Steam DRM platform gamer...
Now, I'm reading that /etc/nsswitch.conf takes information from /etc/hosts and /etc/networks. Though, it's not clear to me what this does. Also, that nsswitch.conf works with unbound in base which comes with resolv.conf. For a small scale...
And they (FreeBSD devs) just started removing stuff that had been around since 4.2BSD because "not everyone uses it". At this point, remove everything but /bin. FreeBSD traditionally has a minimal base, but there is a difference between minimal...
Agreed. You can see a good example of that on this recent OpenBSD mail list thread.
(some idiot wanted to start removing stuff because "they didn't need it and its old")
There are a couple of companies currently trying to monetize FreeBSD, so...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.