richards:/home -- the file server -- would have been a much bigger deal. /home on this box mostly has scratchpad stuff, experiments I was in the middle of, recent downloads, config files for user apps running on this box that I don't have installed on other machines, and things I was copying from one machine to another. So losing files here is a nuisance, but not as big a deal as losing files from my real home-directory.
So in this (unusual) case, screwing up the system and making it temporarily un-runnable would actually have been a bigger pain.
Though I really do need to get around to reinstalling the OS with the full list of packages I want and current versions of everything at some point, or trying to update it piecemeal.
But my file server is also running Linux (Mandrake 6 there, vs Debian 3 in the bedroom), and its partitions are all EXT2. The file server is supporting NFS, Samba, and Appletalk (I considered Andrew but haven't gotten around to setting it up to experiment with). Does Netatalk run under BSD or Solaris? If so, I could see changing operating systems for that machine when I get around to upgrading it -- I'd already been planning to at least use a more recent version of Linux.
Of course, with the age-related hardware problems I tend to get, I'd love to use RAID on the server, but the only sizes of drives I have four of are too small to do the job. (And yeah, I'd be doing software RAID on IDE if I set it up, 'cause I don't have a RAID controller ... and I've got fewer and smaller SCSI drives than ISE drives, otherwise I'd considering making one of the Sparcs play file server.)
Though the smartass MacOS comment reminded me of a question for a hypothetical future: Ifwhen I get ahold of a Mac that can handle OS X, what'll be the best way to hook it to the file server? Netatalk, NFS, or something else entirely?
(Note: I really really like OS X. I just haven't got a studly enough Mac at home for it, so in the house I'm running 8.6 and 9.1, where Netatalk is the obvious choice.)
(no subject)
So in this (unusual) case, screwing up the system and making it temporarily un-runnable would actually have been a bigger pain.
Though I really do need to get around to reinstalling the OS with the full list of packages I want and current versions of everything at some point, or trying to update it piecemeal.
But my file server is also running Linux (Mandrake 6 there, vs Debian 3 in the bedroom), and its partitions are all EXT2. The file server is supporting NFS, Samba, and Appletalk (I considered Andrew but haven't gotten around to setting it up to experiment with). Does Netatalk run under BSD or Solaris? If so, I could see changing operating systems for that machine when I get around to upgrading it -- I'd already been planning to at least use a more recent version of Linux.
Of course, with the age-related hardware problems I tend to get, I'd love to use RAID on the server, but the only sizes of drives I have four of are too small to do the job. (And yeah, I'd be doing software RAID on IDE if I set it up, 'cause I don't have a RAID controller ... and I've got fewer and smaller SCSI drives than ISE drives, otherwise I'd considering making one of the Sparcs play file server.)
(no subject)
Netatalk could probably even work on MacOS X. :-)
(no subject)
Though the smartass MacOS comment reminded me of a question for a hypothetical future: Ifwhen I get ahold of a Mac that can handle OS X, what'll be the best way to hook it to the file server? Netatalk, NFS, or something else entirely?
(Note: I really really like OS X. I just haven't got a studly enough Mac at home for it, so in the house I'm running 8.6 and 9.1, where Netatalk is the obvious choice.)