5 ms·

> - ancient userland pthread implementation There is support for kernel threads in the form of a flag on rfork(2). The golang port uses this. The pthreads libr

by dmm 15y ago

> - ancient userland pthread implementation There is support for kernel threads in the form of a flag on rfork(2). The golang port uses this. The pthreads library is still the shitty userland one though. OpenBSD is great because the man pages aren't absolute shit like Linux and networking is so much better. Linux wifi drivers are absolute crap in comparison. Configure WPA on OpenBSD: ifconfig <interface> nwid <ssid> wpa wpakey <wpakey> up; dhclient <interface> The equivalent on linux is left as an exercise... It's still a pretty usable desktop though. The new ACPI support is amazing and a completely new implementation, rather than being built on the reference implementation everyone else used. > no 802.11n support That's going to require some work on the 80211 layer.

deleted 15y ago
[deleted]
jolan 15y ago
> That's going to require some work on the 80211 layer. The 80211 guy retired so there's little chance of that happening.
deleted 15y ago
[deleted]
adestefan 15y ago
> Configure WPA on OpenBSD: ifconfig <interface> nwid <ssid> wpa wpakey <wpakey> up; dhclient <interface> The equivalent on linux is left as an exercise... wpa_passphrase <ssid> <wpakey> > /etc/wpa_supplicant.conf wpa_supplicant -i<interface> -c/etc/wpa_supplicant.conf -B dhclient <inteface> Everything is easy when you know how to do it.
- dmm 15y ago
  On OpenBSD, all of your interface configuration is done with ifconfig and it's all documented with 'man ifconfig'. On a linux system 'man ifconfig' doesn't even mention iwconfig or wpa_supplicant. I think that makes it a little easier to learn how to do it.
  - levabalkin 15y ago
    I guess in Linux ifconfig is deprecated in favor of iproute2.
    - ghshephard 15y ago
      Another advantage to OpenBSD - For at least the last 10 years, configuring a network interface has been done through ifconfig. I'm willing to wager that 10 years from now - configuring an interface will still be done through ifconfig.
    - sigzero 15y ago
      Really? No Linux SA that I know...and I know a lot...is using iproute2 over ifconfig.
      - CrLf 15y ago
        The "ip" command has been the preferred way to configure network interfaces in Linux for a few years now. Most functionality isn't available through "ifconfig" at all.
    - wazoox 15y ago
      It's a mistake IMO for old hats like myself. After 20 years using ifconfig, it's almost impossible to get used to some new, linux-only tool (even though it may be better).
    - adestefan 15y ago
      It's pretty rare that you actually need to use ifconfig/ip directly in Linux. For every distribution that I know of there's a specific way to setup network interfaces (e.g. /etc/network/interfaces, /etc/sysconfig/network-scripts/ifcfg-*, etc.)
KonradKlause 15y ago
>OpenBSD is great because the man pages aren't absolute shit like Linux and networking is so much better. Linux wifi drivers are absolute crap in comparison. For example?
- vegai 15y ago
  http://www.openbsd.org/cgi-bin/man.cgi?query=wireless&sektion=0&manpath=OpenBSD+Current&arch=i386&apropos=1&format=html http://www.openbsd.org/cgi-bin/man.cgi?query=wireless&se... I like Linux in practice, but one must admit that BSDs' manuals are way better.
  - deleted 15y ago
    [deleted]
  - cturner 15y ago
    The problem with linux is that nobody owns responsibility for making the whole man system good. Linux kernel stuff is covered by the linux man project. This is run by Kerrisk, who is a good communicator - _The Linux Programming Interface_ reads like Stevens but is richer in practical advice. But if you go to the man page for something like awk or bash or grep (the common use-case - where you need a quick reference), they're maintained by the team who write the tool, or - often enough - not maintained by the team. There are undocumented flags, often the doc only tends to make sense if you already understand the internals of the tool. GNU tool man pages are generally obtuse. BSD and plan 9 have much better man systems. Unless a linux distribution comes along and makes a conscious effort to solve GNU/linux doc, the man system available to linux users will always suck - it's structural.
    - CrLf 15y ago
      "But if you go to the man page for something like awk or bash or grep [...]" And this is where you are doing it wrong. For GNU tools, the man page is just a stub. The official documentation is maintained in the form of "info" pages. Now, you may consider this obtuse (I sure do), but it doesn't mean there is no documentation.

by dmm 15y ago

deleted 15y ago

[deleted]

jolan 15y ago

> That's going to require some work on the 80211 layer. The 80211 guy retired so there's little chance of that happening.

deleted 15y ago

[deleted]

adestefan 15y ago

> Configure WPA on OpenBSD: ifconfig <interface> nwid <ssid> wpa wpakey <wpakey> up; dhclient <interface> The equivalent on linux is left as an exercise... wpa_passphrase <ssid> <wpakey> > /etc/wpa_supplicant.conf wpa_supplicant -i<interface> -c/etc/wpa_supplicant.conf -B dhclient <inteface> Everything is easy when you know how to do it.

dmm 15y ago
On OpenBSD, all of your interface configuration is done with ifconfig and it's all documented with 'man ifconfig'. On a linux system 'man ifconfig' doesn't even mention iwconfig or wpa_supplicant. I think that makes it a little easier to learn how to do it.
- levabalkin 15y ago
  I guess in Linux ifconfig is deprecated in favor of iproute2.
  - ghshephard 15y ago
    Another advantage to OpenBSD - For at least the last 10 years, configuring a network interface has been done through ifconfig. I'm willing to wager that 10 years from now - configuring an interface will still be done through ifconfig.
  - sigzero 15y ago
    Really? No Linux SA that I know...and I know a lot...is using iproute2 over ifconfig.
    - CrLf 15y ago
      The "ip" command has been the preferred way to configure network interfaces in Linux for a few years now. Most functionality isn't available through "ifconfig" at all.
  - wazoox 15y ago
    It's a mistake IMO for old hats like myself. After 20 years using ifconfig, it's almost impossible to get used to some new, linux-only tool (even though it may be better).
  - adestefan 15y ago
    It's pretty rare that you actually need to use ifconfig/ip directly in Linux. For every distribution that I know of there's a specific way to setup network interfaces (e.g. /etc/network/interfaces, /etc/sysconfig/network-scripts/ifcfg-*, etc.)

KonradKlause 15y ago

>OpenBSD is great because the man pages aren't absolute shit like Linux and networking is so much better. Linux wifi drivers are absolute crap in comparison. For example?

vegai 15y ago
http://www.openbsd.org/cgi-bin/man.cgi?query=wireless&sektion=0&manpath=OpenBSD+Current&arch=i386&apropos=1&format=html http://www.openbsd.org/cgi-bin/man.cgi?query=wireless&se... I like Linux in practice, but one must admit that BSDs' manuals are way better.
- deleted 15y ago
  [deleted]
- cturner 15y ago
  The problem with linux is that nobody owns responsibility for making the whole man system good. Linux kernel stuff is covered by the linux man project. This is run by Kerrisk, who is a good communicator - _The Linux Programming Interface_ reads like Stevens but is richer in practical advice. But if you go to the man page for something like awk or bash or grep (the common use-case - where you need a quick reference), they're maintained by the team who write the tool, or - often enough - not maintained by the team. There are undocumented flags, often the doc only tends to make sense if you already understand the internals of the tool. GNU tool man pages are generally obtuse. BSD and plan 9 have much better man systems. Unless a linux distribution comes along and makes a conscious effort to solve GNU/linux doc, the man system available to linux users will always suck - it's structural.
  - CrLf 15y ago
    "But if you go to the man page for something like awk or bash or grep [...]" And this is where you are doing it wrong. For GNU tools, the man page is just a stub. The official documentation is maintained in the form of "info" pages. Now, you may consider this obtuse (I sure do), but it doesn't mean there is no documentation.