SoylentNews is people
SoylentNews
The NetBSD Project has announced the release of version 7 of the operating system, which is known for its portability.
Acceleration, with a direct rendering manager (DRM) and kernel mode-setting (KMS), is now available on recent Intel and Radeon graphics chips.
The new version ships with a daemon, blacklistd, which can block unwanted network connections.
The installer now supports GPT-partitioned disks.
ARM multiprocessing is now possible, and several ARM-based single board computers are now supported.
NetBSD now has an experimental port to certain Psion PDAs.
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Conquering Russia should be done steppe by steppe.
(Score: 2, Interesting) by cnst on Sunday October 11 2015, @10:14PM
What's "a sockets at paths specified"?
(Score: 1, Funny) by Anonymous Coward on Sunday October 11 2015, @11:27PM
/var/nsa/inconspicuous-socket
(Score: 3, Informative) by coolgopher on Monday October 12 2015, @01:17AM
Ignoring the extraneous "a", I'd assume the answer is that it's one or more regular unix domain socket (AF_UNIX). See unix(7).
(Score: 2) by joshuajon on Monday October 12 2015, @06:44PM
I think the other poster was correct about what the referenced paths file is. This sounds very much like a generic implementation of something like Fail2Ban [fail2ban.org]. In fact the rest of the man page describes what it does pretty clearly I think.
(Score: 0, Funny) by Anonymous Coward on Sunday October 11 2015, @11:56PM
Last I remember, the following acronyms have already been colloquially associated with the following:
DRM: Digital Rights Management
KMS: Key Management Server (also associated with Digital Rights Management)
(Score: 2, Informative) by cnst on Monday October 12 2015, @02:57AM
What you're referring to is actually Digital Restrictions Management -- we don't need no restrictions, so, who cares?!
(Score: 2, Interesting) by throwaway28 on Monday October 12 2015, @12:49AM
FYI, GPT partitioning is necessary to support drives greater than 2 terabytes. Lack of support for it, was one of the reasons for moving away from slackware.
(Score: 0) by Anonymous Coward on Monday October 12 2015, @02:26AM
Actually, it is limited to 2^32 sectors. Most newer hard drives use 4096 sectors and therefore have a maximum of 16 TB of space. However, if your OS uses 512 emulation or has 512 wired in, then they can freak out with the larger drive.
(Score: 0) by Anonymous Coward on Monday October 12 2015, @08:27PM
NetBSD does support GPT partitions, via wedges:
https://wiki.netbsd.org/users/mlelstv/using-large-disks/ [netbsd.org]
(Score: 3, Touché) by MichaelDavidCrawford on Monday October 12 2015, @02:51AM
If I am to make a real difference on a codebase, it's best if it starts out as a steaming pile. That just doesn't happen with any of the BSDs.
Yes I Have No Bananas. [gofundme.com]
(Score: 3, Interesting) by cnst on Monday October 12 2015, @03:52AM
It's important to be able to grasp what the code is doing, and make sensible changes easily.
OpenBSD is one of the easiest ones, I think, because it doesn't have almost any untested or dead code (NetBSD probably has the most), and minimal use of preprocessor marcos, making it much easier to understand the code compared to FreeBSD, which has so many macros and awk-based source files that it gets quite crazy.
That's not to say that OpenBSD doesn't have bugs -- it has lots of bugs, just as any other software out there, but the difference is that they're quite easy to grasp and fix.
(Score: 0) by Anonymous Coward on Monday October 12 2015, @09:52PM
I gave it a whirl last night in a VM on my LinuxMint system ... timemachine back to the 1990's. Console welcome.
login:
Ok, and then I dared for the impossible:
> startx
This brought tears and memories to me. I recall a GEM system back on an Apple ][ that looked like this, circa 1984.
BSD, for a retro experience in 2015. Worth the 371MB ISO download for a good laugh.
(Score: -1, Troll) by Anonymous Coward on Monday October 12 2015, @09:40AM
caveat emptor
https://www.gnu.org/distros/common-distros.html#BSD [gnu.org]
(Score: -1, Flamebait) by Anonymous Coward on Monday October 12 2015, @01:01PM
"Firmware" is something found in hardware such as eproms. Did you mean "Drivers" or something like that?
(Score: 2) by jummama on Monday October 12 2015, @02:15PM
Much of the time, firmware is pushed into a devices address space as part of initialization, rather than it existing on ROM/EEPROM on the device itself. As a result, you have to either have a proprietary binary blob to initialize the device, or you have to develop a functional alternative. Lots of WiFi chips are like this, most modern GPUs are like this, and even some ethernet controllers are like this. Without this firmware, drivers won't work.