Re: Installation on Dell Poweredge 6300
On Tue, Feb 11, 2003 at 10:05:29AM +, Dave Whiteley wrote: > I had great difficulty with my original install because of the adaptec > AIC7xxx scsi. I had to create a special rescue disk for it. The compact distro has AIC7k support compiled in. I've used the compact boot floppies for just about every install I've done over the past few years. In fact, the first system I haven't used compact on since '99 was this incredibly obnoxious Compaq box with a goofy Intel gig NIC which, as yet, unsupported by the kernel. (As you might guess, I do everything in my power to use generic, well-supported hardware -- which I consider the AIC7k series to be.) http://http.us.debian.org/dists/Debian3.0r1a/main/disks-i386/current/images-1.44/compact/ I got a PE1400SC while they were on sale a while back. Good stuff, very happy with it. -- bda Cyberpunk is dead. Long live cyberpunk. http://mirrorshades.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Mixed platform network
On Sun, Feb 09, 2003 at 09:05:29PM -0500, David Turetsky wrote: > Are there packages available to support a LAN between a Windows XP > Professional gateway to the Internet and a debian woody system? Perhaps you should tell us exactly what it is you want to do. > I understand that Samba has some of these characteristics but I have not > found anything to suggest capabilities beyond printer and file sharing Samba also does authentication, but that's essentially correct. -- bda Cyberpunk is dead. Long live cyberpunk. http://mirrorshades.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: What's the "debian" way to bind multiple IP addresses to a single NIC???`
On Tue, Feb 04, 2003 at 02:25:59PM +0100, Mark Janssen wrote: > On Tue, 2003-02-04 at 13:59, Jeff Hahn wrote: > > I've scanned the fine manual and googled, but I'm unable to determine the > > "official" way to bind multiple IP addresses to a single NIC. > > I realize I can just ifconfig the interface, but I guess I'm looking for the > > documentation/format of the interfaces file in /etc/networks. > > Just define a new interface in /etc/network interfaces: > > iface tr0:1 inet static > address 192.168.0.1 > netmask 255.255.255.0 This is the 2.2 way of doing things. This has been deprecated with the 2.4 kernels (as IP aliasing was -- to my understanding -- essentially a dirty hack) for iproute2. I realize that Debian still defaults to 2.2.x for installation, but I would be also be curious to know you're supposed to bind multiple IPs to a single interface `the Debian way' without IP aliasing (with does still work with 2.4). I spent some time digging through docs when I first discovered iproute2 a year or so ago, but didn't really come up with anything. Ended up writing a script do to it for me. If anyone has any information on the Correct way to do this with 2.4, I'd also appreciate a tap from the clue bat. -- bda Cyberpunk is dead. Long live cyberpunk. http://mirrorshades.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Timing a program run?
On Thu, Jan 02, 2003 at 03:57:10AM -0600, Gerald Livingston wrote: > OK -- dumb question that I can't remember the answer to and can't find > by googling. > > How the heck do I time how long it takes a certain script to run? > > I've searched the archives and google and apropos and apt-cache on all > kinds of variations of "time" (timing, timer, etc) and can't find > anything. `time ' It's a bash built-in, at least for bda@eos:~$ bash --version GNU bash, version 2.05b.0(1)-release (i386-pc-linux-gnu) This is the second hit I get from googling for `bash time built-in': http://www.ss64.demon.co.uk/bash/time.html ... bda@eos:~$ time ls -lF total 32 drwxr-xr-x 15 bda bda 4096 Jan 1 05:41 Endymion/ drwx--2 bda bda 4096 Dec 17 08:21 Mail/ drwxr-xr-x 6 root root 4096 Dec 21 17:39 Media/ drwxr-xr-x 3 bda bda 4096 Dec 17 16:37 bin/ drwx-- 3 bda bda 4096 Dec 30 02:52 etc/ drwxr-sr-x 7 bda bda 4096 Dec 25 22:03 img/ drwxr-xr-x 6 bda bda 4096 Jan 2 05:01 tmp/ drwxr-sr-x 13 bda bda 4096 Dec 28 16:31 txt/ real0m0.005s user0m0.000s sys 0m0.010s ... Other shells, YMMV. -- bda Cyberpunk is dead. Long live cyberpunk. http://mirrorshades.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Samba
On Sat, Dec 07, 2002 at 04:41:15PM +0100, Stefaan Teerlinck wrote: > Found it, thanks. > Users have to be valid under global options, and then only the valid users for a >share have to be assigned als valid in the share options. Right? Set "security = user" in global. You only need to set valid/invalid users on a per share basis. No need to declare them globally; that's what /etc/passwd and /etc/smbpasswd are for. -- bda Cyberpunk is dead. Long live cyberpunk. http://mirrorshades.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Samba
On Sat, Dec 07, 2002 at 11:14:40AM +0100, Stefaan Teerlinck wrote: > > I just installed a samba server, but I can't seem to find a way to set restrictions >of the shares so just some users can read it. I can set read/write permissions for >some users, so just those users can write to those shares, but all shares can be read >by all known users. How do I do this? > > Thanks, > Stefaan. In /etc/samba/smb.conf: valid users = foo or valid users = @bar for groups. smb.conf is very well documented, check its man page: `man smb.conf'. -- bda Cyberpunk is dead. Long live cyberpunk. http://mirrorshades.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: sync root passwords?
My philosophy has always been to make root's password completely random for each manchine, document it somewhere secure, and then use sudo for all management requirements. However, I've never worked in a situation where there were more than two or three active system admins for the entire network, so I'm not sure how scalable this method is (although it's much easier to copy /etc/sudoers around than /etc/shadow, assuming you already have a method for generating passwd file entries -- NIS or LDAP, or something more homegrown, which is what I'm prone to). Since root's password is random, and you're using sudo to gain su access, you then set up a key structure in which all root logins (for updating /etc/sudoers, or performing "pull" backups, for instance) in which only one or two machines -- preferably ones which are not accessable to anyone easily -- can root into the machines via ssh and private/public key pairs. The only time not knowing what a machine's root password becomes an issue is when it decides to go explodey and you've got to boot it into single user and do some maint on it. But you've got the root passwd documented (and possibly printed out and locked up in a Big Black Folder of DOOM in a fireproof safe hidden in the middle of the Yucatan), so that's only a minor inconvience. On Wed, Dec 04, 2002 at 01:15:58PM -0800, Mike Egglestone wrote: > Hi, > Is there a debian package for syncing root passwords on multiple servers? > If I had a 100 debian servers, and want the root passwords all be the same, > is there a util that will sync just the root password? > > or perhaps someone has a script they use? > > At first glance, its appears that I start with one server, > change the password, extract the encrpted line from /etc/shadow and somehow > copy this line to all other servers at /etc/shadow. > > Thanks for any suggestions! > > Cheers, > Mike > > > > > > - > This mail sent through IMP: http://horde.org/imp/ > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- bda Cyberpunk is dead. Long live cyberpunk. http://mirrorshades.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
