From: "Lluís Batlle i Rossell" <viriketo@gmail.com>
To: 9fans Mailing list <9fans@cse.psu.edu>
Subject: [9fans] Plan9 installation invading the other partitions?
Date: Wed, 19 Jul 2006 22:53:27 +0200 [thread overview]
Message-ID: <44BE9BC7.9050302@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1517 bytes --]
I just installed plan9 in my PC, where there are many partitions. I can
give you a "fdisk -l /dev/hda":
omitting empty partition (8)
Disk /dev/hda: 40.0 GB, 40020664320 bytes
16 heads, 63 sectors/track, 77545 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 128 64480+ 83 Linux
/dev/hda2 * 129 20318 10175760 39 Plan 9
/dev/hda3 20319 20839 262584 82 Linux swap / Solaris
/dev/hda4 20840 77543 28578767+ f W95 Ext'd (LBA)
/dev/hda5 20840 41157 10240240+ 83 Linux
/dev/hda6 41158 52784 5859976+ 83 Linux
/dev/hda7 52785 77542 12478000+ 83 Linux
I did the Plan9 partition using Linux fdisk. Well... after the plan9 CD
installation (I downloaded the iso a few hours ago), I started linux
again and the SuperBlock of my Reiserfs partition /dev/hda7 had been
overwritten. I had to run reiserfsck --rebuild-sb, and it fixed almost
everything. Further reiser checking fixed something with two tmp files
(the partition is quite full and with many files. Nice only two files
were bad.)
I don't know if I'm the only one having problems with PC partitions (I
guess not), but I'd prefer feeling like Plan9 couldn't have done this
little exter-partition writting.
I hope running Plan9 won't break anything more. hda7 is my linux /home
partition.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3311 bytes --]
next reply other threads:[~2006-07-19 20:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 20:53 Lluís Batlle i Rossell [this message]
2006-07-20 5:14 ` Russ Cox
2006-07-21 11:09 ` Lluís Batlle
2006-07-21 11:43 ` Christian Walther
2006-07-21 11:51 ` Lluís Batlle
2006-07-21 14:22 ` Iruatã Souza (muzgo)
2006-07-24 0:22 ` Harri Haataja
2006-07-24 0:28 ` erik quanstrom
2006-07-24 13:46 ` Paweł Lasek
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=44BE9BC7.9050302@gmail.com \
--to=viriketo@gmail.com \
--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).