From: Daniel Egger <degger@fhm.edu>
To: John Bradford <john@grabjohn.com>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: Release of 2.4.21
Date: 22 Mar 2003 15:54:29 +0100 [thread overview]
Message-ID: <1048344868.15199.73.camel@sonja> (raw)
In-Reply-To: <200303220827.h2M8R4YW000282@81-2-122-30.bradfords.org.uk>
[-- Attachment #1: Type: text/plain, Size: 2105 bytes --]
Am Sam, 2003-03-22 um 09.27 schrieb John Bradford:
> So why did you trim the part of my quote that said that production
> systems should always be backed up anyway?
You consider normal desktop systems "production system"? Interesting...
The best on can hope for a desktop system is a regular becakup of
important work files to CD-R; we're more talking about a sector-wise
harddisk backup here which is not even common for server systems (no,
I'm not talking about RAID here) let alone Joe users system.
For instance I do have a RAID and a regular rsync backup on my
production system here. That's still not enough for trying development
kernels on real data which might fry the filesystem because it'd be
fried on the mirrored harddrives at the same time and the rsynced copy
is not enough to fully recover the system.
> It's not exactly much work to put a different disk in a machine.
Yeah, though not something Joe user could do. And honestly this is not
something someone would do "just for fun", because it's still a lot of
trouble for a minor intent.
> With a notebook, it might be 30-45 minutes work dismantling it,
You certainly must be kidding. Dismantling my PowerBook is hardly
possible at all without killing it and the harddrive is quite hard to
replace. This is more like a 2h work and something I'd rather do once
in its lifetime for the sake of a bigger harddrive instead of trying
a development kernel.
> but on a typical desktop, about 2 minutes, and on a rackmount server, probably
> 60 seconds.
Right. Let's see. It took me about 20 minutes to swap the CPU in this
"desktop" machine here, 15 minutes of that were used to dismantle the
system, pull the mounted motherboard (with all PCI cards in the slots,
my case luckily allows for that) and reassemble those parts. This action
is necessary to get to the right hand side screws which fasten the
harddrive.
It's not even realistic to assume that simply opening the case, and
reconnecting a loosely hanging around harddrive will just take 2
minutes.
--
Servus,
Daniel
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-03-22 14:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 19:56 Release of 2.4.21 Adrian Knoth
2003-03-20 20:21 ` Sebastian D.B. Krause
2003-03-20 20:34 ` Jeff Garzik
2003-03-20 20:42 ` Christoph Hellwig
2003-03-20 20:53 ` Jeff Garzik
2003-03-20 21:05 ` David Lang
2003-03-21 1:55 ` Andrew Morton
2003-03-21 0:13 ` John Bradford
2003-03-21 1:30 ` Samuel Flory
2003-03-21 9:33 ` John Bradford
2003-03-21 8:40 ` Bernd Petrovitsch
2003-03-21 9:23 ` John Bradford
2003-03-21 21:53 ` Daniel Egger
2003-03-22 8:27 ` John Bradford
2003-03-22 14:54 ` Daniel Egger [this message]
2003-03-21 1:01 ` Alan Cox
2003-03-21 0:04 ` David Lang
[not found] <20030320200019$6ddc@gated-at.bofh.it>
[not found] ` <20030320203015$4839@gated-at.bofh.it>
2003-03-20 20:43 ` Florian Weimer
2003-03-20 21:03 ` Jeff Garzik
2003-03-20 21:33 ` H. Peter Anvin
2003-03-20 22:08 ` Sebastian D.B. Krause
2003-03-21 11:06 ` Oliver Feiler
2003-03-20 22:18 ` Arador
2003-03-21 1:20 ` Chris Wright
-- strict thread matches above, loose matches on Subject: below --
2003-03-20 21:17 Dow, Benjamin
2003-03-21 0:57 ` Alan Cox
[not found] <20030320205011$1378@gated-at.bofh.it>
[not found] ` <20030320205011$0acb@gated-at.bofh.it>
[not found] ` <20030320205011$2c88@gated-at.bofh.it>
[not found] ` <20030320211011$5967@gated-at.bofh.it>
2003-03-20 21:48 ` Florian Weimer
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=1048344868.15199.73.camel@sonja \
--to=degger@fhm.edu \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
/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