strcmp() et al. come from an older time when external symbols had to be kept unique within the first 6 characters and not case-dependent so the GECOS, 370, etc. UNIX ports could use them.
To do what he's doing takes (a) a very thick skin and (b) a fairly hefty ego. This surprises you? And the "side effects" surprise you? Then you haven't stopped to think about it.
This is in fact a bug in Red Hat 5.2's login. The problem is that login closes the PAM session before spawning the shell; pam_krb4 destroys your ticket cache at that point.
I reported it to Red Hat almost immediately upon RH5.2's release (it breaks pam_linux_afs as well, which is disastrous in CMU ECE's environment). They have fixed it, but didn't see any point in releasing an updated util-linux RPM.
You're probably better off getting util-linux and building it yourself anyway: RH5.2 ships with an ancient version.
Or demand a rewritten contract and get them to sign off on it *before* you take the job. I did that when I was consulting for a bank last year: the IP agreement stated the bank would own anything I produced --- on or off the job --- for the duration of the contract plus some period; I rejected it because I do quite a lot of off-time Linux and OS/2 coding (not that all of it sees the light of day, it helps to have time to *finish* projects...).
They produced a new contract which was acceptable.
It even has authentication. And it has ways to reduce network load.
It's called Zephyr. And it's widely used at a number of universities. The code is freely available, there are even prebuilt RPMs (minus Kerberos authentication support) on RHCN.
Why invent yet another protocol when we already have one?
Slashdot Mirror
strcmp() et al. come from an older time when external symbols had to be kept unique within the first 6 characters and not case-dependent so the GECOS, 370, etc. UNIX ports could use them.
To do what he's doing takes (a) a very thick skin and (b) a fairly hefty ego. This surprises you? And the "side effects" surprise you? Then you haven't stopped to think about it.
This is in fact a bug in Red Hat 5.2's login. The problem is that login closes the PAM session before spawning the shell; pam_krb4 destroys your ticket cache at that point.
I reported it to Red Hat almost immediately upon RH5.2's release (it breaks pam_linux_afs as well, which is disastrous in CMU ECE's environment). They have fixed it, but didn't see any point in releasing an updated util-linux RPM.
You're probably better off getting util-linux and building it yourself anyway: RH5.2 ships with an ancient version.
Or demand a rewritten contract and get them to sign off on it *before* you take the job. I did that when I was consulting for a bank last year: the IP agreement stated the bank would own anything I produced --- on or off the job --- for the duration of the contract plus some period; I rejected it because I do quite a lot of off-time Linux and OS/2 coding (not that all of it sees the light of day, it helps to have time to *finish* projects...).
They produced a new contract which was acceptable.
Ahem. Samsung fabs Alpha chips.
Yeah, and every so often someone over in res.cmu.edu portscans the academic domains.... (Like we're not capable of detecting it, huh, d00dz? Feh.)
> 2) what server is MS running on egg.microsoft.com to have it listed by Netcraft as
/.-ers everywhere?
> "undisclosed"?
egg.microsoft.com? Isn't that the one that popped up running Linux a few months ago, to the general amusement of
OS/2's core is quite stable, assuming stable drivers. The Workplace Shell needs a major rewrite, though....
>> Let's all tell Compaq we want to buy them... Don't tell me a company would refuse to sell ?!
:-/
Seen how IBM sells OS/2 of late?
(1) In my personal experience it goes back to 1981. I'm quite certain it goes back even farther.
/etc/profile.
(2) On V7 and BSD-ish systems it's printed by login; on System III/V-ish systems it's printed in
I think TAPR has prior claim on that phrase. Watch it, AOL, you're getting too big for your britches.
It even has authentication. And it has ways to reduce network load.
It's called Zephyr. And it's widely used at a number of universities. The code is freely available, there are even prebuilt RPMs (minus Kerberos authentication support) on RHCN.
Why invent yet another protocol when we already have one?