FreeBSD 11.0 Now Available
111–120 of 163 posts
Re: FreeBSD 11.0 Now Available
#112Earlier quoted context omitted.
As a full time developer, you are correct that the relnotes don't capture all the great stuff. It is difficult to keep track of all that is going on. The only way I know how is to continuously read the commit logs. But distilling that down into a useful document for end users is quite hard, especially retroactively. I will say that the release has non-trivial improvements in TCP performance (Mike Karels, Matt Macy, N…
>SysV SHM can be jailed/virtualized which should be interesting to many users. You mean I can run multiple postgresql jails on a machine? YASSS
Re: FreeBSD 11.0 Now Available
#113Earlier quoted context omitted.
Is anyone using FreeBSD on their development machine? Are there any gotchas compared to Linux?
I use 11-rc on Thinkpad X220. Compare to Linux I miss a lot native Dropbox client (Currently I use rclone, but it is not convenient: sync dropbox->local, change, sync local->dropbox). Skype probably will work via Linux emulation, but I haven't tried yet. Update: also almost all closed source products are not available for FreeBSD, e. g. I'd like to try Jetbrains CLion - it has version for Linux, but not for FreeBSD.
Re: FreeBSD 11.0 Now Available
#114So, have you donated yet? We need FreeBSD and FreeBSD needs your support!
Re: FreeBSD 11.0 Now Available
#115Earlier quoted context omitted.
Is anyone using FreeBSD on their development machine? Are there any gotchas compared to Linux?
I use CURRENT on a Thinkpad X230. It works ok. Main gotchas: * No SSL CA certificates out of the box. FreeBSD security team has taken the curious posture of claiming that shipping no CAs is better than just shipping e.g. Mozilla's CA bundle.[0] * rc.d is like Linux init from 5 years ago. Dynamic network configuration is not handled well. * Intel GPU driver support for anything above Haswell is still waiting to be mer…
Also small note on FreeBSDs rc vs Linux old init is that it for example always had support for dependencies.
I'm saying that because BSD's especially FreeBSD's simple, pretty and working rc system have always been a thing that I missed when using Linux. Or in other words I disliked that run level system that makes managing dependencies really hard.
I always hoped OpenRC would become the most common init system on Linux and actually still do, because I think it is the best option, when compared with sysv init and systemd.
Also about the CAs: Everything that wants it has a dependency.
About package conflicts: Choose between official packages or your own with Poudriere
Out of the box the system is like Arch Linux, Debian or Ubuntu Server. It's the FreeBSD base system. You can install packages to make it into a router, a server, a thing hosting your private cloud using jails, a jail itself, etc.
And the plus side. You don't have to get rid of all the stuff when you want your nice little i3 environment. And if you want KDE, just install it and kdm using pkg install and do sysrc kdm_enable=yes.
Or go for TueOS (former pc-bsd).
Or if you just want some FreeBSD tools go on MacOS and enter grep --version.
With the other things I agree. FreeBSD isn't really your multimedia desktop environment. It is maybe for people that like it liked Gentoo or Arch Linux, but you should really check on your laptop's hardware before.
Most driver development really happens in the server or usual suspects (Lenovo, Raspberry, ...) area.
Sorry, didn't mean to even strongly disagree, but wanting to share my own experiences. Not everyone comes with the same views and I'm personally someone who is switching back from Arch Linux, because of the developments in the last few years in the Linux world.
It just in my personal experience felt so much more easy to do stuff and have the system I want. Having used Arch for around a decade with only a relatively short break doesn't make that easy, but I liked it's initial idea about keeping things simple and that's what I miss on many ends.
The main reason for not using FreeBSD on laptops really was the lack of some drivers for me. So that's maybe the biggest gotcha. Oh and for new people maybe that it is not just another Linux distribution so many things work differently.
Biggest is probably the separation between base system and ports/packages.
Re: FreeBSD 11.0 Now Available
#116Earlier quoted context omitted.
There is reuse, for example iwm(4) is based on the Linux driver and pulls from it. But the process is manual, not like the Linux-KPI graphics and OFED stuff. It would be great if Intel stepped up to the plate and helped.
I was thinking about a common driver interface similar to POSIX standard would solve the problem of multiple OS device support on a single hardware platform. There was an effort for Uniform Driver Interface (UDI)[0], looks like it is dormant. [0] http://wiki.osdev.org/Uniform_Driver_Interface
Re: FreeBSD 11.0 Now Available
#117> A kernel panic triggered when destroying a vnet(9) jail(8) configured with gif(4) has been fixed. [r271917] > A kernel panic triggered when destroying a vnet(9) jail(8) configured with gre(4) has been fixed. [r271918] I see they fixed the kernel panics when destroying vnet jails but is vnet enabled by default? Or do I have to compile a custom kernel like with FreeBSD 10.x
I started using SmartOS partly because it has really nice VNIC support and you don't have to recompile the 10.x FreeBSD kernels. :-) It'd be good to know if 11.0 changed that.
Re: FreeBSD 11.0 Now Available
#118Earlier quoted context omitted.
Is this a thing? I'm running Slackware and mounting a disk is still done with good ol' `mount`, same as it ever was.
I've been in the linux world for less than a decade, and I miss 'mount' being useful. It's full of spam now - so I've started using 'lsblk' instead... $ mount | wc -l 32 $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 698.7G 0 disk ├─sda1 8:1 0 512M 0 part /boot/efi ├─sda2 8:2 0 690.3G 0 part / └─sda3 8:3 0 7.9G 0 part [SWAP] # this was a mistake... sr0 11:0 1 1024M 0 rom
That's not an unfixable mistake: sda3 is at the end of the partition table, so if it's deleted, sda2 can be safely resized offline. For example,
parted /dev/sda rm 3
parted /dev/sda "resizepart 2 -0"
resize2fs /dev/sda2 # for ext2/3/4
And then you can create a swap file or volume on sda2, so long as it isn't on btrfs.Re: FreeBSD 11.0 Now Available
#119FreeBSD is not 'just another OS out there' but an important piece of technology powering lots of things we often use: from Sony's PlayStation and WhatsApp, through Netflix and Yahoo, to Juniper and PFSense networking gear and EMC storage and FreeNAS appliance - and many, many more! So, have you donated yet? We need FreeBSD and FreeBSD needs your support! https://www.freebsdfoundation.org/donate/