1) Find someone who has been to one of the Linux conferences and ask them who they liked: you might be surprised; there are some great, experienced speakers out there. Good geeks aren't always good speakers.
2) Get numbers, then try to get Linuxcare (my employer), RedHat, VA Linux, SuSE etc. to send one of their people. They may contribute or pay outright to send someone.
3) Try just emailing the person you want: maybe there's something near you which she/he always wanted to see, they just don't know it yet (you'd probably think they're cheesy touristy things). It's easier if you can finance it, but otherwise they may fast track you onto (2).
> Thats *22* seperate sub-versions of the same > kernel version over a period of a month. > Thats not chaos, thats insanity.
No, it's more like looking into an active CVS tree. Classic troll.
> Look at the firewalling stuff. It's been > different in every stable version since 2.0, > and will be different in 2.4.
And you're conveniently ignoring that 2.2 provided backwards compatibility via ipfwadm-wrapper (userspace), and that 2.4 provides backwards compatibility by compatibility modules (kernel space).
> Linuxcare is pointless because the tech support is out there all over the place. > The few people who need to be spoonfed w/ Linuxcare will get frustrated > with Linux and go back to Micro$oft.
But who wrote that tech support info? Some of us are now working for Linuxcare. And trust me, the support calls/EMails from Linuxcare customers go straight to the top of my list.
Say 99% of the time, your trouble is not some subtle kernel bug. It's nice to have someone to go to who can handle the other 1% as well.
Rusty, Linuxcare Employee and Linux Netfilter Maintainer.
The reason I joined Linuxcare: I feel they are in a position to make a reasonable amount of money; consulting in the Linux space is going to be big, and I think will be a good thing to work in, because you can actually fix the problems a customer might have.
This makes the engineer in me feel satisfied; even if the stock is a bust, Linuxcare has a bright future.
Actually, Tridge is mainly working on Samba and rsync right now. I know that jitterbug is on his TODO list as well, and he's done some smbfs work. It's anyone's guess what else he's cooking up here in the office...
If you're not a US Citizen, you need not apply. Hell, I wouldn't mind having some Red Hat stock in case some of their investors try to change their excellent record of unswerving Free Software support.
I'm surprised noone has complained about this: it does seem that Red Hat tried to avoid non-US addresses in their mailout, but even so, GNU/Linux isn't a US product, even if Red Hat is.
Various other people pointed to broken protocols, and protocols which need special help. In general, any protocol which does not restrict itself to a single connection (ie. src ip/port dst ip/port quad) will require special assistance. This includes FTP (both passive and active) in the general case, although for simple masquerading passive ftp does not need help.
For static NAT, where an IP address is always mapped the same way (n:n NAT, eg. 192.168.1.* is mapped straight into 1.2.3.*), only protocols which actually include IP addresses within their data stream will be impaired. Unfortunately, FTP is one of these.
A special note on games: Dan Kegel (of Activision) produced a fairly well-thought-out proposal for UDP gaming through NAT. IP masquerading in Linux 2.2 meets this standard. Here is the draft
Firstly, RedHat don't develop proprietary code. They turned down the opportunity to become an official channel for Quake II, and they chose not to include KDE.
Secondly, they sponsor Alan Cox, Stephen Tweedie, David Miller, Rasterman, Federico Quintero, and others, as well as sponsoring projects like the port of KDE to Qt 2.0 and the Gnome project.
I don't know the recent stats, but three years ago, RedHat was the largest single contributor to the Free Software Foundation.
Now I'm a Debian user, and professional Free Software developer, but I have great difficulty finding any faults with Red Hat, other than the fact that their growing pains sometimes show themselves by a less-than-polished performance. They deserve their success, and I hope they all get a nice big bucket of money.
1) Find someone who has been to one of the Linux conferences and ask them who they liked: you might be surprised; there are some great, experienced speakers out there. Good geeks aren't always good speakers.
2) Get numbers, then try to get Linuxcare (my employer), RedHat, VA Linux, SuSE etc. to send one of their people. They may contribute or pay outright to send someone.
3) Try just emailing the person you want: maybe there's something near you which she/he always wanted to see, they just don't know it yet (you'd probably think they're cheesy touristy things). It's easier if you can finance it, but otherwise they may fast track you onto (2).
Hope that helps,
Rusty.
> Thats *22* seperate sub-versions of the same
> kernel version over a period of a month.
> Thats not chaos, thats insanity.
No, it's more like looking into an active CVS tree. Classic troll.
> Look at the firewalling stuff. It's been
> different in every stable version since 2.0,
> and will be different in 2.4.
And you're conveniently ignoring that 2.2 provided backwards compatibility via ipfwadm-wrapper (userspace), and that 2.4 provides backwards compatibility by compatibility modules (kernel space).
IMHO,it's a nice compromise,
Rusty.
> Linuxcare is pointless because the tech support is out there all over the place.
> The few people who need to be spoonfed w/ Linuxcare will get frustrated
> with Linux and go back to Micro$oft.
But who wrote that tech support info? Some of us are now working for Linuxcare. And trust me, the support calls/EMails from Linuxcare customers go straight to the top of my list.
Say 99% of the time, your trouble is not some subtle kernel bug. It's nice to have someone to go to who can handle the other 1% as well.
Rusty,
Linuxcare Employee and Linux Netfilter Maintainer.
How do you feel about the claims Microsoft are making with regards to Windows 2000?
Rusty.
I hacked up a compressed loopback block device, which is used on the card.
From the early prototypes we got around 2.5:1 compression on the stuff we put on there. I haven't seen the final ones.
Rusty.
I'm pretty sure we put the SVGA server on there at least.
Rusty.
This makes the engineer in me feel satisfied; even if the stock is a bust, Linuxcare has a bright future.
Just my opinion,
Rusty.
Actually, Tridge is mainly working on Samba and rsync right now. I know that jitterbug is on his TODO list as well, and he's done some smbfs work. It's anyone's guess what else he's cooking up here in the office...
Best bet is to check out Tridge's diary
Rusty.
I'm surprised noone has complained about this: it does seem that Red Hat tried to avoid non-US addresses in their mailout, but even so, GNU/Linux isn't a US product, even if Red Hat is.
Rusty.
Various other people pointed to broken protocols, and protocols which need special help. In general, any protocol which does not restrict itself to a single connection (ie. src ip/port dst ip/port quad) will require special assistance. This includes FTP (both passive and active) in the general case, although for simple masquerading passive ftp does not need help.
For static NAT, where an IP address is always mapped the same way (n:n NAT, eg. 192.168.1.* is mapped straight into 1.2.3.*), only protocols which actually include IP addresses within their data stream will be impaired. Unfortunately, FTP is one of these.
A special note on games: Dan Kegel (of Activision) produced a fairly well-thought-out proposal for UDP gaming through NAT. IP masquerading in Linux 2.2 meets this standard.
Here is the draft
Rusty.
Secondly, they sponsor Alan Cox, Stephen Tweedie, David Miller, Rasterman, Federico Quintero, and others, as well as sponsoring projects like the port of KDE to Qt 2.0 and the Gnome project.
I don't know the recent stats, but three years ago, RedHat was the largest single contributor to the Free Software Foundation.
Now I'm a Debian user, and professional Free Software developer, but I have great difficulty finding any faults with Red Hat, other than the fact that their growing pains sometimes show themselves by a less-than-polished performance. They deserve their success, and I hope they all get a nice big bucket of money.