nbsd4life

the 'cold war' ended up being a bunch of proxy actual-wars in my area, and I don't think the thousands that died liked it very much.

I recommend using the package manager than building yourself. If something needs to be modified about the source, it will first be patched in the widely used package manager. convincing upstream to take in a patch & then waiting for a new version to be released with that patch takes time.

Ridiculous claim. A few months ago Gaza militants fired 460 rockets in one day, injuring 80 people (mostly civilians) and killing one, and the IDF has barely done anything besides bomb empty buildings.

When's the last time your country restrained itself after being hit by 460 rockets in one day?

Google has 100 times as many employs as NSO group. The equivalent for a group of 100 Google employees signing a petition is one person signing it. They can just be fired & replaced.

The suggestion to invalidate cache is also in ACPI 6.2A 16.1.1.2 Example 2: S1 Sleeping State Implementation (page 783)

http://www.uefi.org/sites/default/files/resources/ACPI%206_2...

Is it weird to support some of these today? we just dropped acorn26, although it was gone for a few years.

I think mips r3k has a better behaving add ("addu"), or is that only on some? if your compiler outputs these you don't have to worry about special behavior.

I'd say a bigger concern, for vax - the lack of IEEE754 is noticeable when people pick unsuitable float constants, or it traps by default. or the many GCC bugs now.

For mips r3k, the complete lack of atomics. And the load delays.

If you've ever been on the bad side of banks you'll dread this a lot. I merely had my credit card stolen but getting a replacement was surprisingly time-consuming and I'm glad I could still eat and travel until then.

Apple isn't the best example. They generally do publish the modified source code to FOSS projects they do, and sometimes they don't add their own license clause, so the changes can get merged back.

it can't backfire too bad, if it does they'll change the license again.

so you want a non-commercial use license. these aren't seen as open source by most people, but perhaps they'll be accepted by users.

calling it open source is harming actual open source projects by making people fear adopting them.

No need to work so hard, VMs self-identify: https://kb.vmware.com/s/article/1009458

This question sounds so silly I wonder if it's a strawman argument.

Can you have any advanced device that doesn't contain anything made by 50% of humanity? no.

This comment is sent to you from Asia and 7000km away from Beijing.

HP's "keylogger" doesn't belong in this discussion. It was a debug trace to a driver. I've left similar traces as part of debugging. It wasn't even their driver but belonged to Synaptics.

That only refers to copyright, not the patent, right? I know FOSS projects avoiding a different implementation of RCU for patent reasons.

I have this in my ~/.xinitrc because I found the color changes of f.lux distracting:

xrandr --output DVI-I-1 --gamma 1:1:0.5

Why are there so many fish?

> there's a one in four chance

Closer to 1 in 7, because the reviewer might be female (who are rarely color blind).

I've enjoyed cleaning chores a lot more after mentally declaring them to be exercise.

> The cartel tested their bulbs and fined manufacturers for bulbs that lasted more than 1,000 hours

If their motivations were pure, they would set a standard for efficiency and/or brightness, or a minimum but not maximum of 1,000 hours.

The way netbsd does GCC updates gives a really wide margin for figuring out compiler issues:

- Copy existing compiler into gcc.old

- Add new compiler as "gcc"

- Switch architectures one by one

If one architecture is left behind it's not a big pressing issue, you have until the next GCC update. They're done once 2-3 years hopefully so the GCC VAX issue taking 6 months to resolve wasn't close to being a problem.

As for removing architecture support, as long as it builds without extreme intervention, the non-VAX crowd is going to leave it alone. The VAX code is mostly separate in its own directory so doesn't get in the way.

The people who care about VAX within NetBSD are very knowledgeable and it would be a shame to alienate them without a good reason. They've contributed a lot of non-VAX stuff too.

I doubt that Fabrice Bellard is getting a lot of money for his work. The money in open source goes to adding a feature in widely used projects. New projects have no users, so nobody to pay money.

NetBSD 8.0 took longer to release than intended.

The comparison to "oldest clang/gcc you can get in a linux distro" is not right, you can get a lot of different versions as packages. this refers to the base compiler which is used to build everything. GCC 8.1 is available as a package for example.

As for the base GCC versions, NetBSD is a little conservative when updating, but keep in mind that it's doing this on a lot of architectures and problems arise. a complete transition to GCC 5.x was held back somewhat by a tricky mipseb-softfloat bug, GCC 6.x (in -current) was held back by a VAX ICE. Newer GCC kills ARMv4-nonthumb support.

If that is OpenSSL 1.0.2k it probably should be updated, yeah.

It isn't a zero sum game with a finite number of FOSS idealists. Linux's popularity grew rapidly in what were previously proprietary software users. It didn't take away that much from BSDs.

Linux and other FOSS software becoming popular makes using NetBSD a lot more convenient, not less. There's a top tier FOSS browser that will accept NetBSD related patches, several really good document editors, graphical tools. We can even take some driver code from Linux itself.

it's probably a mistake that it got enabled there, I don't think the architecture has support for it. Even the edgerouter shouldn't, but don't quote me on it.

it's a nice OS, friendly community.

It's very easy to build and modify everything, it doesn't hide errors under a rug (syslog messages are legible, coredumps not disabled by default and so on), so I feel like I can tackle any problem I encounter on it.

Also, if you're the type that carries their long .xinitrc/.Xresources/.profile around, it's more comfortable than the friendly linuxes which require you to re-do everything but in dconf.

No those changes are in -current, and still a bit rough around the edges but much better.

I do, I'm using dwm, firefox and urxvt.

I've got a lot of netbsd running machines. The one I use now is a Haswell CPU with nvidia graphics, and everything works well on it (even nvidia graphics!).

Not all machines are so good. I have a too new Dell XPS. It doesn't have graphical acceleration. But it was very cool to have the touchscreen working already (although with rough edges).

Dell XPS uses almost the same wifi as the macbook stuff AFAIK - the fullmac broadcom chips.

You're editing your ACPI tables, compiling the result, and telling the kernel to use it instead of what it gets from the hardware.

You're responding as if you didn't read the article and don't realize how widespread it was. We don't consider a child's consent as valid even if they were told the correct facts about what they were taking, which they weren't.