Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

FreeBSD 13.0 Beta1 Now Available

lists.freebsd.org

Post reply on HN
Print view View original

71–80 of 110 posts

Re: FreeBSD 13.0 Beta1 Now Available

#71

Post by the-dude »

throwawayboise wrote: post #48
jiggawatts wrote: post #14

Earlier quoted context omitted.

One thing I haven't quite understood is why Netflix even bothers to encrypt the video streams. It seems like a waste of effort, since Netflix isn't exactly serving content that would qualify as "secret". There's not even any porn on there, so it's not the biggest concern if someone were to find out what some people were watching. This data is being collected anyway via endpoint technologies like Samsung's Automated C…

> There's not even any porn on there, so it's not the biggest concern if someone were to find out what some people were watching. True there's no out-and-out porn, but there is content that's close to the line, and beyond that there are themes that could be indicators that a viewer is gay, or in some other demographic that he might want to keep private. Target can tell if you're pregnant based on your shopping; certa…

> Target can tell if you're pregnant based on your shopping;

I am very skeptical about that story, it sounds too good/scary to be true, and there is only 1 reported incident, without proper sources. Sounds made up to me.

https://medium.com/@colin.fraser/target-didnt-figure-out-a-t...

Re: FreeBSD 13.0 Beta1 Now Available

#72

Post by rleigh »

mapgrep wrote: post #35
gautamcgoel wrote: post #30

I wish FreeBSD booted faster. I recall it took nearly a minute from turning my machine on (with an SSD and a recent Intel i5 processor) before I was prompted for my login credentials. It's little things like that which make the system feel a bit dated, at least to someone like me who is an outsider to FreeBSD but has used Linux for a decade. I also wished FreeBSD needed less configuration to use as a desktop (see htt…

One key impetus for Linux moving to systemd was faster boot time, parallelizing init tasks. Is FreeBSD looking at moving beyond traditional rc script boot?

That was one of the notional reasons, but I (and others) haven't noticed much of a speedup. If anything, it's slightly slower in my experience (though this obviously depends upon the specific configuration).

It was also not unique in parallelising startup tasks. Even sysvinit can be configured to do that with insserv+startpar.

Re: FreeBSD 13.0 Beta1 Now Available

#73

Post by oblio »

tal8d wrote: post #58
mapgrep wrote: post #52

Earlier quoted context omitted.

Wouldn’t have to be systemd, macOS has launchd for init, FreeBSD could come up with its own thing. This is a good talk I saw recently (by a FreeBSD contributor) on why these sorts of systems have become more common, and why they seem so sweeping in scope. https://youtu.be/o_AIw9bGogo (In fact systemd and launchd are so tailored to their respective operating systems that FreeBSD likely would have to do their own init…

> This is a good talk That is not a good talk unless you already advocate for abandoning standards, and celebrate Linux's growing power to dictate how the shrinking number of remaining OSes design things. You might easily miss it if you're already onboard with systemd, but in his point by point address of systemd's shortcomings - he repeatedly handwaves and redirects. Systemd is a mess, which is an amazing accomplish…

Sys V init was not a standard. Is it in POSIX? I can't find it.

Re: FreeBSD 13.0 Beta1 Now Available

#74

Post by efxhoy »

bombcar wrote: post #33
codetrotter wrote: post #3

Is OpenZFS 2.0 in base in this snapshot? Edit: It is! neat! # uname -a FreeBSD freebsd 13.0-BETA1 FreeBSD 13.0-BETA1 #0 releng/13.0-n244471-638e531019f: Fri Feb 5 17:12:07 UTC 2021 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64 # zfs version zfs-2.0.0-FreeBSD_gf11b09dec zfs-kmod-2.0.0-FreeBSD_gf11b09dec

What does 2.0 bring us?

The biggest feature for me was zstd compression

Re: FreeBSD 13.0 Beta1 Now Available

#75

Post by mnd999 »

octofish wrote: post #67

I'd hoped that aarch64 (ARM) would now be a tier 1 architecture in 13 but that's not to be the case ( https://www.freebsd.org/platforms/ ) and the FreeBSD wiki page on what's required to make aarch64 a Tier 1 architecture was flagged as being out of date ~18 months ago ( https://wiki.freebsd.org/ARMTier1 ). For info, a key thing about Tier 1 architectures is that "Binary updates and source patches for Security Adviso…

It is enormously disappointing to have to wait yet another cycle for officially supported updates on aarch64. For a relatively well funded project, FreeBSD should be able to meet this kind of goal and they should be asking what went wrong here and how they can improve.

Re: FreeBSD 13.0 Beta1 Now Available

#76

Post by petre »

mnd999 wrote: post #75
octofish wrote: post #67

I'd hoped that aarch64 (ARM) would now be a tier 1 architecture in 13 but that's not to be the case ( https://www.freebsd.org/platforms/ ) and the FreeBSD wiki page on what's required to make aarch64 a Tier 1 architecture was flagged as being out of date ~18 months ago ( https://wiki.freebsd.org/ARMTier1 ). For info, a key thing about Tier 1 architectures is that "Binary updates and source patches for Security Adviso…

It is enormously disappointing to have to wait yet another cycle for officially supported updates on aarch64. For a relatively well funded project, FreeBSD should be able to meet this kind of goal and they should be asking what went wrong here and how they can improve.

Probably not enough developers motivated enough to work on aarch64. Maybe if Nvidia and/or another Arm64 hardware vendor was a sponsor OTOH things would be different.

https://lists.freebsd.org/pipermail/freebsd-arch/2019-Decemb...

Re: FreeBSD 13.0 Beta1 Now Available

#77

Post by petre »

mapgrep wrote: post #52
tal8d wrote: post #50

Earlier quoted context omitted.

As somebody who fled Linux to FreeBSD in order to avoid systemd, the prospect of that happening again makes me a little sick to my stomach. Running out of places to go that aren't controlled by people who are openly hostile to POSIX standards.

Wouldn’t have to be systemd, macOS has launchd for init, FreeBSD could come up with its own thing. This is a good talk I saw recently (by a FreeBSD contributor) on why these sorts of systems have become more common, and why they seem so sweeping in scope. https://youtu.be/o_AIw9bGogo (In fact systemd and launchd are so tailored to their respective operating systems that FreeBSD likely would have to do their own init…

Have you even used launchd? It's an XML based init system with inconsistent launchdctl directives. I'd even use systemd any day in place of it.

Re: FreeBSD 13.0 Beta1 Now Available

#78

Post by petre »

stock_toaster wrote: post #59
tal8d wrote: post #50

Earlier quoted context omitted.

As somebody who fled Linux to FreeBSD in order to avoid systemd, the prospect of that happening again makes me a little sick to my stomach. Running out of places to go that aren't controlled by people who are openly hostile to POSIX standards.

There are a few Linux distros that use OpenRC with decent success. I run lots of FreeBSD servers, but I also run some Alpine servers, where openrc works well for me (with some s6 thrown in for a few services).

Runit in Void Linux is even faster, better. It's already in Busybox, has to be activated with a #define.

Re: FreeBSD 13.0 Beta1 Now Available

#79

Post by forty »

drewg123 wrote: post #2

This release includes most of the kTLS and NUMA work that I talked about at EuroBSDCon in 2019, including hw kTLS offload support for some NICs. This allows Netflix to serve over 350Gb/s of TLS encrypted video streams from a single 32-core AMD based server (at about 50% CPU).

Hello,

I'm genuinely curious: why did you implement it in FreeBSD rather than Linux? Isn't that kind of offload something that already exists in Linux? Or does something in the way Linux is implemented/designed that makes it impractical / impossible to implement as efficiently? Or is somehow Linux not secure enough for your use case? Or not something else enough?

I'm asking because I'm always interested to know what are the practical limitations of Linux and also because, while I think it's nice that Linux had some serious competitors, I cannot help being a bit sad that contribution like this will only benefit the few people that use FreeBSD (even if to be fair, it seems that it will benefit all netflix customers at least, which is quite a few people ;) )

Re: FreeBSD 13.0 Beta1 Now Available

#80

Post by Macha »

fis wrote: post #37
drewg123 wrote: post #22

Earlier quoted context omitted.

"This helps protect member privacy, particularly when the network is insecure — ensuring that our members are safe from eavesdropping by anyone who might want to record their viewing habits." from https://netflixtechblog.com/protecting-netflix-viewing-priva...

The parent mentioned "This data is being collected anyway via endpoint technologies like Samsung's Automated Content Recognition (ACR)". If that's true then the encryption isn't really helping.

They're required to let you choose whether to opt in to ACR in Europe because of the GDPR. While the prompt is terribly vague and designed to encourage "just hit yes" behaviour, I have a q60r and the setup wizard at least presented a prompt I could opt out of.

Also while HN likes to raise the spectre of TVs connecting to open wifi/shipping with 5G radios, at the moment there is no evidence for either so users could always use a trusted device to play back Netflix rather than the TV app and leave the TV without internet

Post reply on HN