Re: Small Debian Installs
I believe that the nycwireless Pebble image is under 64MB. It isn't a full distro, just an image intended for WLAN router/bridges running on the soekris hardware: http://www.nycwireless.net/pebble/ It has some great features if you're interested in building your own WLAN stuff. Eirik Thomas Lamy wrote: Randy Kramer wrote: On Wednesday 05 March 2003 02:42 pm, Russell Coker wrote: Just install a small Debian system. That might be exactly what I want to do (for a different purpose). aol Me too! /aol What's the smallest someone on the list has installed, and what's the easiest way to go about doing it? I needed a WLAN Router 3 weeks ago, and didn't want to start with a new distro (I really like debian). I did the standard install (basedebs only), and removed portmap, NFS, lpr, gcc and the like, added only wireless tools and shorewall. That way I brought it down to ~200 MB (which would fit on a 256 MB CF-Card), and I'm sure it would be possible to even get under 100 MB (delete /usr/share/doc etc).
Replacing Sendmail with Exim
A quick question for the pros: I'm planning to replace sendmail with Exim on a webserver that only uses the MTA to relay outgoing mail from web applications to the mail server for the domain. Based upon what I've read in the documentation Exim is a drop-in replacement. My question is: Are there any gotchas that you've run across that aren't covered in the official Exim documentation? Thanks in advance. eirik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Replacing Sendmail with Exim
A quick question for the pros: I'm planning to replace sendmail with Exim on a webserver that only uses the MTA to relay outgoing mail from web applications to the mail server for the domain. Based upon what I've read in the documentation Exim is a drop-in replacement. My question is: Are there any gotchas that you've run across that aren't covered in the official Exim documentation? Thanks in advance. eirik
Re: chroot and OpenSSH
I'm happy to report that it did work. I had to apply the third hunk of the patch manually since the OpenSSH source code had changed slightly on the effected lines since the patch had been submitted, but once it was applied, it compiled without any problem and is working as it should. Following Jeremy Reed's suggestion I've opted to hard link the libs and bins rather than copying them. Thanks for the suggestion, it is working quite well, but in the course of making these links I've come up against another probably clueless question: According to the ln manpage and info page, the super user can hard link directories by setting the -d or -F options. For some reason I cannot get this option to work, even though I have tried it with a variety of directories, with different permissions, but all located on the same filesystem. I did some digging around for more documentation on hard links, but the most prominent thing that I found was contrary to the man page, but consistent with my experience in that it said that one couldn't hard link directories. Anyone know of a somewhat definitive documentation on hard links, preferrably with examples? Thanks again to everyone who responded. eirik Frank Louwers wrote: Thanks for taking the time to answer my somewhat clueless questions. np ;) and let us know if it works ... Frank -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
