From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: backups
Date: Tue, 25 Apr 1995 11:34:22 -0400 [thread overview]
Message-ID: <19950425153422.ynCkyI7JBooMej-7i9P7WvVSi5LgBSfUkW_3Jfk0hW0@z> (raw)
>>| i configure the file server with a pseudo-worm for `main'
>>| (and a plain file system for `other', for paging files).
>>What about a cache for the pseudo-worm?
i was including that as part of the pseudo-worm. i don't think
you can run it without the cache, since the cache size limits how
much can change between dumps.
anyhow, here's my disc config
config w0
filsys main cp[w0w1]10.20fp[w0w1]30.70
filsys dump o
filsys other p[w0w1]0.10
w0 and w1 are both 512 Mb Fujitsu drives. the file server is
a 486sx33 (don't need floating-point) with 16 Mbytes and
an Ultrastor 14F controller.
next reply other threads:[~1995-04-25 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-04-25 15:34 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-04-25 14:46 backups Scott
1995-04-25 9:13 backups forsyth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19950425153422.ynCkyI7JBooMej-7i9P7WvVSi5LgBSfUkW_3Jfk0hW0@z \
--to=forsyth@plan9.cs.york.ac.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).