Charles Forsyth schrieb:
Have you tried an installation (not an update!) with the actual
CD-edition ( I think it is the third edition) of plan9?
a third edition CD would be quite old and quite different as
regards both the file system implementation (kfs instead of fossil/venti)
and more i
> Have you tried an installation (not an update!) with the actual
> CD-edition ( I think it is the third edition) of plan9?
a third edition CD would be quite old and quite different as
regards both the file system implementation (kfs instead of fossil/venti)
and more important disk/fdisk and frie
Martin Neubauer schrieb:
I started out with a small installation on a spare partition of a laptop to
get the hang of the system. Later I set up a standalone file server I can
boot a terminal from (usually said laptop.) This can be regarded as the
normal mode of operation. The installation never
Martin Neubauer schrieb:
Using /dev/sdD0/data worked for me. Did you actually try it?
I am sorry I made a mistake in the last posting. i used the word decide
instead of distinguish! So the text could be misinterpreted. Please read
One must decide distinguish between the prompt "mountdisk",
Martin Neubauer schrieb:
I started out with a small installation on a spare partition of a laptop to
get the hang of the system. Later I set up a standalone file server I can
boot a terminal from (usually said laptop.) This can be regarded as the
normal mode of operation. The installation never g
* bblochl ([EMAIL PROTECTED]) wrote:
> Martin, thank you very much for your helpful answer! Indeed it might be
> somewhat strange to install plan 9 as a standalone system and I am sure
> that this is seldom done. At least I have plan 9 on the laptop happily
> now. Let me describe the problem sol
Martin Neubauer schrieb:
If you don't boot from cd you still need to have access to the data that is
getting installed. So you can either put the cd image somewhere on the
system (this can be a problem if you want to install Plan 9 on the whole
hard disc) or download it during installation. I als
* bblochl ([EMAIL PROTECTED]) wrote:
> The chapter "Locate and Mount the Distribution Archive" with the task
> "mountdisk" is very obscure (especially for me as a non-english
> speaker). First of all the value of the "Distribution disk" ist not (and
> cannot be) "/dev/sdD0/data" because such a d
Eric, thank you for explaining the facts with dossrv!
Well. I can understand now that /n/9fat/ will be populated by dossrv
and not part of the inatalled files and that cannnot be the source of
the bug, but is a follow up. There must be something wrong before that
step of "bootsetup".
I d
> Second I searched for the directory /srv/dos you mentioned in your mail
> on the iso - it is not present there.
this file isn't present on the iso. dossrv posts this srv entry when it runs.
one dossrv makes the dos entry in /srv.
> Third, I had the (somewhat late) idea to check the subdirecto
erik quanstrom schrieb:
Initializing Plan 9 FAT configuration partition (9fat)
add 9load at clust 2
Initializing FAT file system
type hard, 12 tracks, 255 heads, 63 sectors/track, 512 bytes/sec
Adding file /n/newfs/386/9load, length 338424
add 9load at clust 2
used 342016 bytes
/bin/mount: can't
> Initializing Plan 9 FAT configuration partition (9fat)
>
> add 9load at clust 2
> Initializing FAT file system
> type hard, 12 tracks, 255 heads, 63 sectors/track, 512 bytes/sec
> Adding file /n/newfs/386/9load, length 338424
> add 9load at clust 2
> used 342016 bytes
> /bin/mount: can't open sr
I installed plan 9 standalone on my hard disk and would like to boot it
from there. The probably last step of the setup process of plan 9 makes
some trouble. the task bootsetup give me the messages:
--
Initializing Plan
13 matches
Mail list logo
