What to do with an old machine.
in [UK Linux]
|
Prev: Linux equivalent of Telnet?
Next: File encryption
From: Ian Rawlings on 7 Jan 2008 06:20 On 2008-01-07, Paul Martin <pm(a)zetnet.net> wrote: > INN was a disc hog when it was a single-file-per-article spool. When we > moved to diablo on the servers, the load on the drives was greatly > reduced. We did think of moving to Diablo but INN came out with its own spooling scheme that removed the single file per article spool and IIRC even was able to hit the block devices directly so didn't even need a filesystem. I used to run INN at home too until about 5 years ago when I moved to leafnode but am thinking of going back to INN or something that can handle article lookups better, with leafnode I can't select an article and find all its children which I could do with INN. -- Blast off and strike the evil Bydo empire!
From: Ian Rawlings on 7 Jan 2008 06:55 On 2008-01-07, Paul Martin <pm(a)zetnet.net> wrote: > As you're using slrn, have you thought of using slrnpull instead? Not really, I prefer to use a client-independent server instead, more flexible if a little more work. -- Blast off and strike the evil Bydo empire!
From: Ben Shimmin on 7 Jan 2008 08:14 Ian Rawlings <news06(a)tarcus.org.uk>: > On 2008-01-07, Paul Martin <pm(a)zetnet.net> wrote: >> INN was a disc hog when it was a single-file-per-article spool. When we >> moved to diablo on the servers, the load on the drives was greatly >> reduced. > > We did think of moving to Diablo but INN came out with its own > spooling scheme that removed the single file per article spool and > IIRC even was able to hit the block devices directly so didn't even > need a filesystem. I used to run INN at home too until about 5 years > ago when I moved to leafnode but am thinking of going back to INN or > something that can handle article lookups better, with leafnode I > can't select an article and find all its children which I could do > with INN. I'd recommend upgrading to Leafnode 2, which supports XPAT and thus will allow slrn to reconstruct threads. b. -- <bas(a)bas.me.uk> <URL:http://bas.me.uk/> `If all the girls who attended the Harvard-Yale game were laid end to end, I wouldn't be surprised.' -- Dorothy Parker
From: Ian Rawlings on 7 Jan 2008 08:26 On 2008-01-07, Ben Shimmin <bas(a)llamaselector.com> wrote: > I'd recommend upgrading to Leafnode 2, which supports XPAT and thus > will allow slrn to reconstruct threads. OK, may look at that, I'll be rebuilding my network-facing machines soon so will re-evaluate everything then. Leafnode's an easy server to set up, it was only the full thread reconstruction that I was missing. -- Blast off and strike the evil Bydo empire!
From: Martin Gregorie on 7 Jan 2008 08:33
Bernard Peek wrote: > Martin Gregorie wrote: > > This BIOS is definitely limited >> to a 6.4 GB disk size. > > The limit is probably at 8Gb, but you can get round it by adding a cheap > IDE controller card. > Nope. 6.4 GB - don't ask me why it used such an odd limit, but thats what the documentation said. From memory the BIOS had an number of predefined disk geometries you could select but none defined a disk of over 6.4 GB. It also provided the ability to accept your own definition, but you couldn't put in anything that exceeded 6.4 GB. This has stuck in my brain because I couldn't get that BIOS to accept any size of drive that was commercially available when I was setting up dual booting - hence the need to scour eBay for a used 6.4 GB drive. -- martin@ | Martin Gregorie gregorie. | Essex, UK org | |