10 ms·
FreeBSD Q2 2016 Status Report
- akerro 10y agoDoes anyone know when can we expect KDE5 in FreeBSD? Better support for Rust would be also nice :(
- LeoPanthera 10y agoDoesn't it rely on dbus and by extension systemd?
- fredmorcos 10y agoNo. It's the other way around. SyStEmD depends on dbus. You can depend on dbus without depending on SyStEmD but you can't depend on SyStEmD without depending on dbus.
- Tomte 10y agoWhat's this weird capitalization?
- gens 10y agoLennart gets pissy about spelling. https://www.freedesktop.org/wiki/Software/systemd/ https://www.freedesktop.org/wiki/Software/systemd/ Oh, and yea, systemd depends on dbus, not the other way around. (one of the dumbest decisions in the whole thing, if you ask me)
- ianai 10y agohttps://freebsd.kde.org/ https://freebsd.kde.org/ and it looks like https://freebsd.kde.org/area51.php https://freebsd.kde.org/area51.php is where you can figure out how to get the latest, greatest
- akerro 10y agoI know all of these.
- feld 10y agoswills is working on KDE5 https://twitter.com/swills/status/757797521133449216 https://twitter.com/swills/status/757797521133449216
- swills 10y agoSince you mentioned it, here's an update. My testing went well except for one issue which was with unlocking after the screen locked. That turned out to be because I'd built using a jail that was built before pam was updated, but was testing on a system after the pam update (11.0-BETA2). Also, the sddm package didn't build because the kdemerge tool can't merge the UIDs/GIDs files. That was changed to go ahead and build the package and give a pkg-message to create the user. I want people to be able to test using 11.0-BETA2 and have sddm, so I've updated the jail and am currently in the process of rebuilding the packages. Because the jail changed, everything builds from scratch, so it's taking a little while, but when they're done building (should be soon), I'll test some more and write up some docs on testing KDE5 and post them for those who are interested.
- tachion 10y agoThere's also some work around the OS installer to implement a new menu where OS security features are turnable, it wasnt on the report, but I hope it gets to the 11.0-RELEASE.
- jlgaddis 10y agoThis sounds interesting. I'll go looking for it myself, but can you point me towards the (mailing list?) discussion of this?
- olavgg 10y agoReally cool to see active work on patching Ceph to run on FreeBSD. There should be some advantages by running Ceph OSD on ZFS, but there is very little information about if ZFS work well with Ceph even on Linux. Transparent compression and checksum validation on read are two features I would love have on a Ceph cluster.
- tachion 10y agoOn another note, have YOU donated[0] yet? :) 0. https://www.freebsdfoundation.org/donate/ https://www.freebsdfoundation.org/donate/
- laumars 10y agoI hadn't until now. Thank you for the nudge.
- pyvpx 10y agoon a somewhat related note: if you're reading this and you use OpenSSH, you really ought to donate to the OpenBSD project via their foundation. And you should band together with the rest of your technical team(s) who most likely also use OpenSSH, and get management to make a donation in kind. http://www.openbsdfoundation.org/ http://www.openbsdfoundation.org/
- X86BSD 10y ago+1 EVERYONE uses OSSH. The OBSD foundation should be just rolling in cash like scrooge mcduck from everyone donating. I think it's pretty sad and says a lot about the IT industry that they are not. Considering that everyone uses it and it's a pretty damn vital part of everyones core infrastructure.
- xoa 10y agoEdit: I debated how to phrase some of this and apparently was not careful enough based on the reply. I in no way meant to imply that OpenBSD was for profit, scummy, taking money or any such thing or hadn't carefully formulated their bylaws or weren't following them. I have tons of respect for them and have repeatedly donated myself. What I was arguing (and am far from the first) is that they have made it harder and less rewarding in numerous small ways that affect donations, and I stand by that. ---- True, but at the same time (and this is not an uncommon pattern with the OpenBSD team) they have thrown up some silly roadblocks that shouldn't deter individual small contributions, but are certainly of concern for large contributions or GP pyvpx's suggestion of organized donations and matching ones, ie >"and get management to make a donation in kind" Unlike FreeBSD and pretty much every other serious donation-supported project (including NetBSD) the OpenBSD Foundation is not a [strike]legal non-profit[/strike] "tax deductible charity" (in the US that'd commonly be a 501(c) tax empty). So donations are not tax deductible and may run into barriers that others sail through. Many of the matching programs I've seen for example simply have official non-profit status as a flat-out requirement. While of course it might be possible to negotiate exceptions with management, just in having the conversation at all we're already talking massively more friction, and friction is the enemy of spending. OpenBSD has some little bit of handwaving about it (Canadian, too much trouble) which may well be valid in isolation but is irrelevant in the larger picture, and feels more like a common pattern of prideful disdain at being about "anything but the code". But to the extent money from non-coders is considered important, the interests of non-coders also have to be at least mildly considered if an increased response rate is desired. It's the 100% right of OpenBSD to make it a PITA and have snark and proudly run rough sites and such, but of course that's going to have natural consequences in interactions with the rest of the world. There's no right or wrong answer here, but I don't think your "it's pretty sad and says a lot about the IT industry that they are not" actually fully captures the situation. Other foundations are registered non-profits, have somewhat nicer pages (not crazy webapp monstrosities, but even little things like simple acknowledgment of smaller donors that OpenBSD blows off), and so on. Donors are special and rare, and a bit of personal recognition and appreciation is free and can go a long way. A lot of coders may dislike the softer general human networking side of things, but tossing it aside will generally result in a reduced experience unless there is some other form of stickiness.
- cm3 10y agoThe organization of these status reports is outstanding and so structured, like the rest of FreeBSD's documentation and communication. I wish more of the HardenedBSD features would land in FreeBSD trunk. Other than that, I'm really glad to see that it's making great progress, like RISC-V support. The address randomization feature in 11 is ASR (not ASLR), per the review comments by the inventor of ASLR (PaX dev), so it's a pity the initial HardenedBSD devs decided to not continue upstreaming things after they felt the ASLR patch review was taking too long. OPNsense seems to be basing itself on HardenedBSD, so that's nice to see.
- tachion 10y agoThis is not exactly what happened. People behind HardenedBSD code take criticism of their code personally and are very, very, very reluctant to adhere to advices on correction of the code, or design or even processes around their code(one of the main points aganist accepting their ASLR code was that it wasn't designed, but ...just written) so the claims of that code being well tested, well written and in general production ready quality should be taken with a grain of salt. However, its worth noting, that if it wasnt for them persistently making a lot of 'noise' around this particular feature, FreeBSD guys wouldnt come up with their own implementation anytime soon.
- cm3 10y agoI see, that's unfortunate. TBH, I wasn't entirely sure what to make of the comments in the ASLR Phabricator ticket, and it looked like they gave up after failing to address the VM comments. Do you know if there are there plans to implement the rest of the important mitigation techniques?
- tachion 10y agoTo be honest, I am not sure there are such plans. First of all, there's that discussion (and lack of agreement) between FBSD implementation author and the ASLR idea author on what's the 'L' there really is (or what it should be), and second, there is another division of opinions wether the ASLR is worth much in first place, given there were successful bruteforce (and other) cracking reports for other platforms proud ASLR implementations.
- Arnt 10y agoOf particular note: the core team takes action against bad behavour. I wish others would. I'm not talking about Linus. Linus swears, I think that's almost OK. No, I'm talking about the people who go out of their way to be unpleasant. Some of them swear too, but saying fuck isn't the heart of what makes them bad. And I wish Linus wouldn't swear — he attracts too much criticism and shields people who could use a little headwind. I'm going to donate to freebsd just for that.
- Arnt 10y agoIf any freebsd people read this, could you please have a quick look at ff-wbe1.nyi.freebsd.org, which is thanking me for my generous donation once per minute?
- marklgr 10y agoCheck that you're not making a donation per minute too :)
- laumars 10y agoI'm seeing multiple emails too
- Arnt 10y agoBeing fixed; it should be safe to donate now.
- dgoodkin 10y agoOn behalf of the FreeBSD Foundation, I want to apologize for this inconvenience. We are experiencing a problem with our receipt generator right now. We have someone looking into the issue right now. Thank you for your support and donating to the Foundation!
- tazjin 10y agoI like FreeBSD but after getting used to systemd I can't go back to systems without useful init systems anymore. Maybe at some point one of the BSDs will implement a new, cleaner init system.
- cm3 10y agoThe strongest contender (which also happens to be cross-platform), from what I can tell, is nosh (https://news.ycombinator.com/item?id=10493926 https://news.ycombinator.com/item?id=10493926).
- e12e 10y agoLooks like the nosh homepage is gone? Do you happen to know if the project has moved, or is available anywhere? I find various outdated links, but nothing up to date on nosh anywhere.
- cm3 10y agoCan't find it either, might be worthwhile to contact Jonathan about it.
- JdeBP 10y agoIt has moved. There's an article on the new WWW site about what happened. There's a new version of nosh ready on the new WWW site. I'll be announcing in the usual places soon. I believe that it has a few things of interest to people, including (given what was said above) a slight further extension on the cross-platform front.
- cm3 10y agoAnnouncement: https://lists.debian.org/debian-user/2016/08/msg00116.html https://lists.debian.org/debian-user/2016/08/msg00116.html URL: https://jdebp.eu/Softwares/nosh/ https://jdebp.eu/Softwares/nosh/ > It has moved. There's an article on the new WWW site about what happened. Can't find the article though.
- hibbelig 10y agoI am excited to read about AllWinner support. How do I find out which devices are impacted? I have a Cubietruck (aka Cubieboard 3) and it would be great if I could run FreeBSD on it...
- jmcneill 10y agoCubietruck definitely works! There is no pre-configured image, so you need to build your own. Easiest is to start with another Allwinner image (say the Cubieboard2 one), replace U-Boot with the one for your board, and add your dtb. Look at ports/sysutils/u-boot-cubieboard2 for a template on how to build a suitable U-Boot, and sys/boot/fdt/dts/arm/cubieboard2.dts for a template for your dtb. For a detailed list of supported hardware, have a look at the wiki: https://wiki.freebsd.org/FreeBSD/arm/Allwinner https://wiki.freebsd.org/FreeBSD/arm/Allwinner
- floatboth 10y agoThe best part: > Intel GPUs up to and including the unreleased Kaby Lake are supported > Amdgpu AMD/ATI driver has been updated to GCN 1.1 and higher
- tedunangst 10y agoUnfortunately https://wiki.freebsd.org/Graphics https://wiki.freebsd.org/Graphics still has big red boxes for broadwell and skylake.