From owner-freebsd-hackers Mon May 1 14:10:22 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA06148 for hackers-outgoing; Mon, 1 May 1995 14:10:22 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.223.46]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA06137 for ; Mon, 1 May 1995 14:10:18 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id OAA14064 for ; Mon, 1 May 1995 14:10:18 -0700 X-Authentication-Warning: time.cdrom.com: Host localhost didn't use HELO protocol To: hackers@FreeBSD.org Subject: Hackers - send me your setups! Date: Mon, 01 May 1995 14:10:18 -0700 Message-ID: <14062.799362618@time.cdrom.com> From: "Jordan K. Hubbard" Sender: hackers-owner@FreeBSD.org Precedence: bulk One of the things I'll be putting on the 2.0.5 CD is a couple of "canned users", given that the first thing a new user generally does on a system is clone some local wizard's setup. Well, since our poor users are typically all alone on their new machines, they don't have anyone to copy and are left somewhat in the dark. I'd like to change that by setting up 3-4 fake users with descriptive names (and starred passwords - not to worry! :-) that cover the range of available shells and X/non-X setups. For example, for `csh-user' we'd have a .cshrc & .login, and for `sh-user' we'd have a .login and .profile or something (I can't remember - it's been too long since I was a sh user :-). For the X user, and I think I'd want about 2 of those, we'd have things like .xinitrc, .fvwmrc, etc. files. That's one approach. The other is to tie this in with the adduser phase somehow and copy one of several different "skeleton" files into place. The idea here is that if a user would like to see something like a really nice X setup, they can import someone's tricked-out .fvwmrc-from-hell and then modify it rather than having to invent it all from scratch. PLEASE don't just send me these files individually in the mail - I don't want to have to reassemble everything by hand. Send me a shar file or some suitable bundle of all the `dotfiles' you think are relevant, along with a short description of what makes it special. If you're not a shar fan, then make a tarfile out of it and stick it in incoming, sending me a pointer to it. Note that this isn't a call for several thousand 4 line .cshrc files; I'm looking for "complete setups" that people have spent a fair bit of time on and are proud of (and feel would be of genuine use to someone else). Due credit will, of course, be given.. Your chance to see your name in lights and live on in people's .login files all over the planet! :-) Thanks! Jordan