From owner-freebsd-java Wed Nov 17 14: 3:58 1999 Delivered-To: freebsd-java@freebsd.org Received: from sith.wlcg.com (209-9-101-127.sdsl.cais.net [209.9.101.127]) by hub.freebsd.org (Postfix) with ESMTP id 61BA514E07; Wed, 17 Nov 1999 14:03:37 -0800 (PST) (envelope-from joe@wlcg.com) Received: from localhost (joe@localhost) by sith.wlcg.com (8.9.3/8.9.3/Debian 8.9.3-6) with SMTP id RAA07181; Wed, 17 Nov 1999 17:06:24 -0500 X-Authentication-Warning: sith.wlcg.com: joe owned process doing -bs Date: Wed, 17 Nov 1999 17:06:24 -0500 (EST) From: Joe Yandle To: Chuck Robey Cc: Nik Clayton , Steve Price , java@FreeBSD.ORG Subject: Re: Status of JDK for FreeBSD? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Impossible. Sun enforces unique usernames, the entire subject was a > reasonable thing to ask, but absolutely not a worry. I didn't mean that everyone would register using 'asdf123' as their username. I was saying that when people have to register for something that they don't plan on ever using again, they generally type 'asdf'. Since usernames have to be unique on any real system, the system will respond with something like "We're sorry, but username 'asdf' is already taken. However, 'asdf109' is still available". The 109 comes from the fact that asdf[0-108] are already taken by other lazy people who didn't feel like having a real username. So when a sysadmin sees a lot of these usernames, it's a sign that people aren't taking things seriously. This could lead to Sun ignoring the multitude of votes that are liklely to result from a slashdot effect. Of course, they might not check or care. Joe Yandle Internet Programmer Westlake Consulting Group To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message