Dachstein - SBC DSL ?

Charles Steinkuehler charles at steinkuehler.net
Fri Aug 1 20:26:23 CDT 2003


Brian Kelsay wrote:
> Bradley Miller wrote:
> 
>> I'm trying to get my new SBC DSL connection going on my old trusty 
>> 486DX50 box . . . I think it has 12 Mb of memory.  I fired up the 
>> dachstein-v1.0.2-1680.exe 
>> <http://leaf.sourceforge.net/devel/cstein/files/diskimages/dachstein/dachstein-v1.0.2-1680.exe>  
>> from Charles Steinkuehler's site and it boots, but I get VM errors when 
>> I try to do anything from the LRCFG menu.  I suspect it's a bit tight on 
>> memory for my old PC.  Any suggestions?
> 
> May want closer to 16MB, but most of the floppy based firewalls are 
> supposed to work on 8MB.  Is your memory good?  You may want to run 
> memtest on it.  I probably have some memory that I could sell/trade/give 
> you depending on what it requires (Idon't throw old pc parts out).  I 
> know I have 72-pin SIMMs, but I think I gave all my 30-pin stuff away.
> 
> There may also be an option with Dachstein to turn on an extra ram 
> drive.  When I used Freesco there was an option in the setup to turn on 
> 2 extra RAM drives of 4MB each before you started extra services like 
> webserver, ftp, print server, etc.  Maybe Mr. Steinkhuler will respond 
> and enlighten us all.

Dachstein is setup to expect 16 Megs.  There are two ramdisk partitions 
created: one for / (root) and one for /var/log (to keep the system 
running if your logs begin to overflow and fill up the filesystem).

You can get Dachstein to run well in 12 Meg, but I'd probably combine 
the two ramdisks (replace ramlog.lrp on Dachstein with log.lrp from an 
earlier version like Eiger), and you might want to reduce the default 
root ramdisk size.  You may need to watch your logs, or alter the log 
rotation/deletion settings to keep from running out of ramdisk space, 
especially if you're on a cable-modem network (typically cable-modems 
see a lot more garbage traffic than other high-bandwidth links).

...or just changing the default ramdisk sizes might be enough to get you 
up and running.  Change the root ramdisk size in syslinux.cfg, and the 
/var/log ramdisk size in /etc/ramdisk.conf (and backup the ramlog package).

-- 
Charles Steinkuehler
charles at steinkuehler.net




More information about the Kclug mailing list