From: Uriel <uriel@berlinblue.org>
To: 9front@googlegroups.com
Subject: Re: Installing 9front
Date: Mon, 30 Jul 2012 20:32:22 +0200 [thread overview]
Message-ID: <CAK=G1ThGYCG2dJFMTyCqHxcO3Y4vts9NqvNs+shN5FhDtuTkuA@mail.gmail.com> (raw)
In-Reply-To: <5016B4B8.3040608@gmail.com>
On Mon, Jul 30, 2012 at 6:22 PM, Matthew Veety <mveety@gmail.com> wrote:
> On 7/30/12 7:09 AM, Uriel wrote:
>>
>> 3) Not only are the disk space requirements are somewhat high, but you
>> get no warning if your disk is too small, you go all the way into
>> copydist, which barfs on disk full errors, but 'completes' anyway and
>> pretends it is done and that you can go on with the next install step.
>>
>> At the very least we should warn if the disk is too small, and
>> probably we should fail before going into copydist.
>
>
> I agree with you here, an option to use kfs would be awesome, especially
> because cwfs is overkill for non-fileserver cases.
>
> Also, I think work should be done to make cwfs a little more versatile when
> it comes to disk size.
I'm not convinced that adding extra complexity to save some Gb is
worth it, it creates a very different kind of system to test.
I'd rather handle properly the situations where there is no enough
space, and trim the system where it is reasonable (maybe look into a
way to 'clip' the hg history?)
Uriel
next prev parent reply other threads:[~2012-07-30 18:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 11:09 Uriel
2012-07-30 14:57 ` sl
2012-07-30 18:30 ` Uriel
2012-07-30 20:45 ` sl
2012-07-31 11:59 ` Ethan Grammatikidis
2012-07-31 12:51 ` Steven Ruckdashel
2012-07-30 16:22 ` Matthew Veety
2012-07-30 18:32 ` Uriel [this message]
2012-07-30 19:32 ` Julius Schmidt
2012-07-30 23:09 ` Matthew Veety
2012-07-30 23:14 ` Julius Schmidt
2012-07-30 23:57 ` Matthew Veety
2012-07-31 11:48 ` Ethan Grammatikidis
2012-07-31 11:46 ` Ethan Grammatikidis
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='CAK=G1ThGYCG2dJFMTyCqHxcO3Y4vts9NqvNs+shN5FhDtuTkuA@mail.gmail.com' \
--to=uriel@berlinblue.org \
--cc=9front@googlegroups.com \
/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).