|
Toiletbrush posted:Three simple questions: There's driver support in OpenBSD, so the other BSDs should pick it up soon if they haven't already. WPA is considered a flawed and broken protocol by the OpenBSD guys so there's very little interest in getting WPA support in OpenBSD. I'm not sure about the status of WPA in FreeBSD. I've never used Linux, but have a look at atactl(8) and tunefs(8). FreeBSD doesn't have atactl but try looking at atacontrol(8). Since ZFS is both a new filesystem and a new filesystem to FreeBSD, my gut says "not as stable as FFS" but they've been working on it for quite some time. The fact that they've been making so much noise about finally enabling it by default in the 7.0 release makes me think that it's stable enough for real world testing and use. The BSDs tend to be much more conservative about adding new features, OpenBSD in particular. If something is enabled in the GENERIC kernel it must be stable enough to be considered production worthy. New drivers and features generally start out as a patch on the mailing lists that's thrown around until someone decides it's good enough to be imported into the tree. When that happens it's usually not connected to the build in the case of a userland program, or commented out in GENERIC in the case of a kernel change. Only when the developers consider a feature to be ready for wider testing and real world usage is it enabled by default. Just keep in mind that this is the first release that supports ZFS. AKA FreeBSD-ZFS 1.0, and we all know how 1.0 releases are. If you're planning on doing some major, mission-critical stuff for a multi-million dollar corporation you might want to wait for FreeBSD 7.1 just in case.
|
#
¿
Mar 17, 2008 17:18
|
|
|
|
| # ¿ Apr 19, 2024 22:32 |
|
|
wolrah posted:What? Seeing that the other option is WEP, WPA is a godsend. Or is this only referring to WPA1, with WPA2 being supported? I mean WPA2. The other option is not WEP. There are many other ways to secure a wireless connection; authpf, SSH, VPNs, and IPSec can already do everything WPA2 can do and more. They're simpler (WPA2 requires a state machine) and they've been around longer. WPA2 is a complex standard and requires too much bullshit in its implementation for anyone to consider writing support for it when there are already multiple tried-and-true ways of accomplishing the same thing.
|
|
#
¿
Mar 18, 2008 11:48
|
|
|
wolrah posted:This is exactly the kind of thing I'd expect from the OpenBSD guys, sacrificing practical usability over an idealist point of view. Given that OpenBSD strives to be technically correct, I'm not surprised either. They're not sacrificing practical usability for any OpenBSD users. OpenBSD targets a different market and userbase (primarily developers) from most other operating systems. Don't mistake lack of interest in supporting a redundant, overdesigned, consumer-oriented "security" standard as anything other than it actually is. People are working on WPA2 support in OpenBSD, primarily for people who are at colleges and have no other option to connect to their wireless network, but it's a very low priority task. OpenBSD is a small project with few developers. None of them have a pressing need for WPA2, so nobody's interested in writing the code to support it. wolrah posted:I can't speak for its design and or the challenges involved in implementation, but from an ease of use standpoint WPA2 beats the poo poo out of all of those. If all you want is internet you could have the same convenience with authpf + a shell script. It would require an SSH client but the shell script could automatically authenticate you via SSH at which point authpf adds rules to your firewall to allow traffic to pass between your laptop and the internet. Your browsing would be unencrypted unless you use SSL or TLS but the overall security wouldn't be much different from using a public AP. If you want more encryption then you would need to use IPSec or WPA2. wolrah posted:Wireless networks in the home and most offices are about convenience. WPA/WPA2 means I can have friends show up, toss them a post-it with the key, and expect them to be able to get online almost without care for their OS or if it's even a normal computer. I know the AppleTV, Xbox 360, and PS3 support WPA2, I think the PSP does as well. As far as I know the DS is limited to WEP, but that's it. Don't the AppleTV, Xbox 360, and PS3 have ethernet ports that can be used instead? Yes, I know it's not as convenient as wireless but for anyone using OpenBSD in this case it's a lot easier to run a cable than to write who knows how many thousands of lines of code. OpenBSD is not a consumer oriented operating system. Faulting it for not supporting consumer oriented stuff is stupid. In the end, computers and by extension operating systems, are tools. Use the right one for the job. If one isn't working for you, find one that does. But don't complain about one not having all the features you want if you don't even use it and already have something that fits your needs. OpenBSD doesn't try to be everything. If it can't do what you want, use something that does. Even some of the OpenBSD developers dual-boot between other operating systems.
|
|
#
¿
Mar 24, 2008 14:17
|
|
|
Requested username posted:For anyone interested, OpenBSD-current just got WPA2-PSK support. Chipset support is a bit limited at the moment but according to the article it will expand given time.
|
|
#
¿
Apr 16, 2008 22:34
|
|
|
If you truly want to "Create a command that will list the contents of each subdirectory of the /home directory beginning with the letter k, count the number of files found, and save that number in a file called k-users-files." Then you want this: code:It could also be that ls is aliased to something else. If the output of "which ls" says that it's an alias then you'll have to fix whatever's setting that. On typical *nix systems this will be a file like .profile for Bourne-ish shells or .login for the 'C' shells.
|
|
#
¿
Jul 13, 2008 05:52
|
|