any reason why the people on the OpenBSD newgroups are such asses?

[Mucman]

I haven't read the entire thread, but I visit BSDForums everyday... Very friendly people there (like myself )

 

[n0cmonkey]

Originally posted by: xyyz

Originally posted by: n0cmonkey
I'm bored, so I'll reply

BTW... maybe the main reason Theo was thrown outta the NetBSD core by his asshair was 'cause he was such an asshole.... just speculating though....

Reading would help here. Here.

ummm... that's THEO's viewpoint... don't base your decision based on soley on the one you advocate. i'm sure the netbsd core has quite a bit to say as to why he was thrown out.

I doubt they have much to say about it. But, it really doesn't matter.

Probably because they're all fatassed nerds...

I don't think fatass applies

okay so theo's just an ass... i'm sure not all openbsd advocates are extreme mountain bikers

Nor are all of the developers.

considering how big an ass he is, meaning theo... don't be suprised if he gains negative karma points and eats if where he becomes a veggie.

Doubtful, but definitely possible, I guess

The worst part is they're slowing the adoption of their own OS by being pricks about helping people get started.

They don't care. If no one used it, they would still code it. Unlike other OSS/FS projects, they don't care about taking over the world. Just making a good system that they can use.

Flaming on a mailing list where the originator could see it is only slightly worse than flaming on a web forum where the people you're flaming won't see it. I PMed you a link to an OpenBSD newbies list. Try that out. I don't bother with misc@ (although I do read some of it) because of the flaming.

they're stupid then... they should re-examine their model of operation. this is no way to conduct anything successfully.

Why? They are successful. They are creating a system they want to use. Which is one of the basic goals really.

Now, to take a look at the email you sent:

look here's the bottom line... i have issues with understanding syntax and reasons for syntax. you know what... if people want to post their pf.conf files... who cares. if they don't like it the should make express mention of that in the FAQ. and it's not like they need to respond and be an ass about things. they can just ignore the posts.

Agreed with all but the FAQ comment. Being an ass takes more work than ignoring an email, and I don't always see the point of it.

i think you're making a big assumption that i didn't do reading in saying that i should read the FAQ... how many times should one read it?

You obviously read it. I had to read the newer docs just to understand parts of your pf.conf.

things don't suddenly become clear just because you read something over and over and over and over again. i want to UNDERSTAND how the rules work. i want to understand the syntax. trial and error methods are stupid and a waste of time.

Tell that to any scientist. I'm guessing trial and error is a big part of the scientific process. I'll have to ask one of these days. It is how many of us have learned much of what we know. I think I learn better by trying something than by reading about it.

(I just asked "someone in the know" and he agrees that trial and error is important.)

this is my point. i don't want to give a pf.conf file and the errors and have people correct the errors. i want to understand why things work they way they are? why is the syntax the way it is? this will make me much better form proper packet filter rules.

I don't remember this being explained this well. Some of your questions were specific, others (like the reviewing of your pf.conf) were not.

you forget something... we ain't all as bright as some people when it comes to packet filter rules. you can show me all the examples in the world, but they will make no difference to me. i need someone to explain things differently.

Many people do. Messing around, through trial and error helped me quite a bit. Also time, playing, and reading about the subject. I hate to admit it, but the Checkpoint documentation helped out quite a bit. (if you want it, and can't find it on the net, let me know. I might be able to get a hold of *SOME* of it...)

i wish things were more where you can simply look at a book and learn. hell that way you'd have no need for instructors or any institutions where you need someone to teach you things... what a great place the world would be...

Besides the bsdforums, post them here. I know you posted your pf.conf here, but I don't remember much else of the thread off hand. In fact, that thread inspired me to upgrade and work on my own. I'll try to answer questions, although you may have to accept a flame or two in the process. I'll keep it friendly.

btw... i disagree... the openbsd documentation is NOT great... compare it with the FreeBSD documentation which is much more comprehensive and written in a way that anyone can understand.

I have compared it and came to a different decision. It is definitely objective though. I would put FreeBSD second on the documentation list (but I rarely look at the NetBSD documentation, so I can't comment on that project).

If you post another OpenBSD thread, feel free to PM me with a link. I don't always see all the threads I might find interresting, but I prefer threads because they can help others.

 

[T2T III]

i must say that the people on that group are real jackasses.

Well, they are geeks without any social skills. What more could one expect??