I haven't been around here long enough, but having a list, even if it isn't currently used a lot isn't a bad thing. The fact that there isn't a lot of security holes in OpenBSD is a testament to how good a job the devs are doing.
unfortunately, there are louts on every mailing list (even here). It is unfortunate but it is also a fact of life. The impression I am getting is that we should all do a little of the legwork ourselves BEFORE we bug the mailing lists about it. if it is beyond the level of skill that the person reporting the problem, then by all means, a little help is certainly welcome. its like me, I am getting some help trying to resolve an orca build problem on the PPC branch but it appears that it may be a hardware related issue. not much I can do about that right now. I do have a working VINUX installation on that powerbook G3 and have developed a work around for the dubs bug that makes the machine unresponsive after a random amount of time. I wish I could say the same thing for OpenBSD, but I am not yet familiar enough with its internal working to be more than a hobbyist user at best. btw, the person who was offering me as much help as he did was Super Bisquit. He also has an identical machine and encountered the exact same issues. the machine: a powerbook G3 (750 based CPU). He was going to help me with a freeBSD installation, but that is a far more advanced installation than I am willing to work on right now. For his help, I wish to express my great appreciation for his working with me. I need to dig up a spare HDD so I can keep my current install intact. oh yeah. the issues on installing or compiling for ports both involved random halts of the ATA bus or the random stopping of bm0 (the ethernet interface). the only recovery possible from either state involved a hard reboot and a pram reset. :( Nice OS, but I think the powerbook is just old enough to have some issues. -Eric On Feb 7, 2011, at 1:41 PM, patric conant wrote: > The last time someone brought up that there could be a bug in that the > system did not work in the manner in which it was documented on the website, > I believe something mature and well-thought-out like, "Oh, yeah, shut up." > was the response. > > On Mon, Feb 7, 2011 at 11:51 AM, woolsherpahat <woolsherpa...@gmail.com>wrote: > >>> only openbsd src & X. >>> >>> we suck in actually using it. security errata are so rare that there >>> isn't really an established procedure, so don't rely on it too much. >> >> I am sure this has been suggested before, but why hasn't the security >> list been removed from list of mailing lists at >> http://www.openbsd.org/mail.html? It seems a little disingenuous to me >> to present announce-security like it is a good source of current >> security issues when it is in fact not. >> >> Speaking of, what is a good place to track any security related issues >> in Release of Stable? I have been using >> http://www.openbsd.org/errata.html. >> >> --Kevin
