From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] swap files for diskless cpu/auth servers
Date: Tue, 25 Sep 2001 18:34:28 +0100 [thread overview]
Message-ID: <20010925174010.BD106199EA@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 30 bytes --]
that's certainly what i do
[-- Attachment #2: Type: message/rfc822, Size: 2149 bytes --]
From: Sam Ducksworth <sam@ducksworth.com>
To: 9fans <9fans@cse.psu.edu>
Subject: [9fans] swap files for diskless cpu/auth servers
Date: Tue, 25 Sep 2001 11:18:17 -0500 (CDT)
Message-ID: <Pine.BSF.4.33.0109251104240.8677-100000@lucifer.ducksworth.com>
i am setting up multiple diskless cpu/auth servers and have a
question about swap files. is it proper to create a small filesystem
on the file server and allocate swap files from that location
or should i just create them off of "main" ?
i personally think that they should be placed on a seperate filesystem
that is not dumped. i just do not see the value in wasting dump space
on backups of swap files.
--sam
next reply other threads:[~2001-09-25 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-25 17:34 forsyth [this message]
2001-09-28 3:21 ` Sam Ducksworth
-- strict thread matches above, loose matches on Subject: below --
2001-09-25 17:47 presotto
2001-09-26 14:22 ` Dan Cross
2001-09-25 16:31 anothy
2001-09-25 16:18 Sam Ducksworth
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=20010925174010.BD106199EA@mail.cse.psu.edu \
--to=forsyth@caldo.demon.co.uk \
--cc=9fans@cse.psu.edu \
/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).