From: Russ Cox <russcox@gmail.com>
To: 9fans <9fans@cse.psu.edu>
Subject: Fwd: [9fans] XP boot
Date: Wed, 1 Jun 2005 22:11:54 -0400 [thread overview]
Message-ID: <ee9e417a050601191157c2de90@mail.gmail.com> (raw)
In-Reply-To: <ee9e417a0502021114c9fcf2d@mail.gmail.com>
hey look! history repeats itself.
---------- Forwarded message ----------
From: Russ Cox <russcox@gmail.com>
Date: Feb 2, 2005 3:14 PM
Subject: Re: [9fans] XP boot
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
it's much easier just to install smart boot manager
and avoid the nt boot loader.
hget http://pdos.lcs.mit.edu/~rsc/mbr.bootmgr
disk/mbr -m mbr.bootmgr /dev/sdC0/data
russ
On Wed, 2 Feb 2005 18:16:43 +0100, boyd, rounin <boyd@insultant.net> wrote:
> Any other method fails—boot.ini is protected by more than the NTFS
> file protection scheme, and I don't believe there's another way around it.
>
> yes, it is a very strange file. i got some private mail from russ and after
> finding boot.ini it was read only. turn that off and write it with notepad.
> [seemingly] randomly it would turn on read only.
>
> there is this command line thing called 'bootcfg' which is absolutely
> undecipherable, although i now understand something about the format
> of the file by tinkering.
>
> boot.ini essentially points at a 'boot block'. i'm a bit wary about [potentially]
> smashing a currently bootable system.
>
> this will take some thought.
> --
> MGRS 31U DQ 52572 12604
>
>
next prev parent reply other threads:[~2005-06-02 2:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 23:59 boyd, rounin
2005-02-02 0:12 ` Russ Cox
2005-02-02 1:11 ` boyd, rounin
2005-02-02 1:20 ` Russ Cox
2005-02-02 4:42 ` Joel Salomon
2005-02-02 5:05 ` Federico Benavento
2005-02-02 17:16 ` boyd, rounin
2005-02-02 19:14 ` Russ Cox
2005-06-02 2:11 ` Russ Cox [this message]
2005-06-02 2:17 ` boyd, rounin
2005-06-04 7:42 ` Bruce Ellis
2005-02-02 23:37 ` Adrian Tritschler
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=ee9e417a050601191157c2de90@mail.gmail.com \
--to=russcox@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).