From: DervishD <lkml@dervishd.net>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: Konstantin Kudin <konstantin_kudin@yahoo.com>,
linux-kernel@vger.kernel.org
Subject: Re: fdisk: What do plus signs after "Blocks" mean?
Date: Wed, 13 Jul 2005 14:13:13 +0200 [thread overview]
Message-ID: <20050713121313.GB58@DervishD> (raw)
In-Reply-To: <200507122019.j6CKJwxe021850@laptop11.inf.utfsm.cl>
Hi Horst :)
* Horst von Brand <vonbrand@inf.utfsm.cl> dixit:
> DervishD <lkml@dervishd.net> wrote:
> > It's a good idea to have a copy of the partition table around, if
> > it is not simple (the one you had is NOT simple).
> Be careful. What you'll get out of backing up the partition table is /only/
> the primary partitions, the others are handled by a weird russian doll of
> partitions-inside-partitions. AFAIR, the details were in the LILO docu.
Note that I didn't suggest to backup or have a copy of the MBR,
but of the partition table, the FULL partition table (that includes
the secondary partitions and the like. Once a disk is fully
partitioned, a couple of 'dd' commands do the trick even for
extended partitions.
It's a mess, anyway :(
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736 | http://www.dervishd.net
http://www.pleyades.net & http://www.gotesdelluna.net
It's my PC and I'll cry if I want to...
next prev parent reply other threads:[~2005-07-13 12:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 16:35 fdisk: What do plus signs after "Blocks" mean? Konstantin Kudin
2005-07-12 17:37 ` DervishD
2005-07-12 20:19 ` Horst von Brand
2005-07-12 20:48 ` Konstantin Kudin
2005-07-13 10:24 ` Jan Engelhardt
2005-07-14 13:50 ` kernel
2005-07-14 16:23 ` DervishD
2005-07-14 18:08 ` Jan Engelhardt
2005-07-13 12:14 ` DervishD
2005-07-13 12:13 ` DervishD [this message]
[not found] <mailman.1123702259.29404.linux-kernel2news@redhat.com>
2005-08-10 23:00 ` Problem with usb-storage and /dev/sd? Pete Zaitcev
2005-08-11 7:29 ` DervishD
2005-08-11 22:53 ` Horst von Brand
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=20050713121313.GB58@DervishD \
--to=lkml@dervishd.net \
--cc=konstantin_kudin@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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