|
|
 Up |
|
|
  |
Author: bblochlbblochl Date: May 11, 2008 05:26
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 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 srv/dos: '/srv/dos' file does not exist
cp: can't create /n/9fat/9load: '/n/9fat/9load' clone failed
cp: can't create /n/9fat/9pcf '/n/9fat/9pcf' clone failed
/n/9fat/plan9.ini: rc (bootsetup): can't open: '/n/9fat/plan9.ini' clone
failed
------------------------------------------------------------------------------------
I tried it not only once, but a couple of times. How can I start plan 9
from my harddisk?
|
| Show full article (1.08Kb) |
|
| | 12 Comments |
|
|
Author: erik quanstromerik quanstrom Date: May 11, 2008 06:33
> 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 srv/dos: '/srv/dos' file does not exist
> cp: can't create /n/9fat/9load: '/n/9fat/9load' clone failed
> cp: can't create /n/9fat/9pcf '/n/9fat/9pcf' clone failed
> /n/9fat/plan9.ini: rc (bootsetup): can't open: '/n/9fat/plan9.ini' clone
> failed
that's odd. it sounds like dossrv is not running.
otherwise /srv/dos would exist. if you're doing this
from the installer, you can trystarting it by hand
by typing "dossrv" at the prompt.
it may be that your iso is missing dossrv.
- erik
|
| |
|
| | 11 Comments |
|
|
Author: bblochlbblochl Date: May 11, 2008 08:51
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 open srv/dos: '/srv/dos' file does not exist
>> cp: can't create /n/9fat/9load: '/n/9fat/9load' clone failed
>> cp: can't create /n/9fat/9pcf '/n/9fat/9pcf' clone failed
>> /n/9fat/plan9.ini: rc (bootsetup): can't open: '/n/9fat/plan9.ini' clone
>> failed
>>
>
> that's odd. it sounds like dossrv is not running.
> otherwise /srv/dos would exist. if you're doing this
> from the installer, you can trystarting it by hand
> by typing "dossrv" at the prompt. ...
|
| Show full article (2.16Kb) |
| 10 Comments |
|
|
Author: erik quanstromerik quanstrom Date: May 11, 2008 09:02
> 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 subdirectory n/9fat
> and found it empty!! So one should not wonder about the error messages
> given above.
this directory is served by dossrv. if you haven't expressly mounted something
on /n/9fat, nothing will be there.
this is probablly hard to follow in the abstract, so here's an example:
ladd# lc /srv
boot cs dns factotum slashn
consoles cs_net.alt dns_net.alt ratify
no /srv/dos there.
ladd# dossrv
dossrv: serving #s/dos
ladd# lc /srv/dos
boot cs dns dos ratify
consoles cs_net.alt dns_net.alt factotum slashn
|
| Show full article (1.04Kb) |
| 9 Comments |
|
|
Author: bblochlbblochl Date: May 11, 2008 14:18
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 did some more installation trials in the meantime following the
"installation instructions" from
http://cm.bell-labs.com/wiki/plan9/installation_instructions.
I followed that recipe just before, but in a more mechanical and
brainless way.)
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...
|
| Show full article (1.98Kb) |
| no comments |
|
|
Author: Martin NeubauerMartin Neubauer Date: May 11, 2008 16:13
* bblochl (bblochl@fh-lausitz.de) 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 directory is NOT on the
> distribution disk (sdD0)! (May be I am wrong again?) But that entry of
> "/dev/sdD0/data" will only be accepted! Very strange! There is a
> directory /dev/sdD0/distro on /dev/sdD0, but that will not be accepted
> as an entry.
In Plan 9 the disc driver creates a directory in /dev for each drive (sdC0,
sdC1, sdD0, etc.) In each of those directories you'll find (among others) a
file named data which gives you access to the raw data of that drive. To
access the file system hierarchy of a cd you have to mount /dev/sdD0/data
somewhere.
> (In the description is mentioned "a CD image named
> plan9.iso" but where should that be in the installation process?) I also
> tried a download of the archive via ethernet, but without success. I
> argue that at this point there is the bug in the description or
> something wrong with my trials.
|
| Show full article (2.28Kb) |
| no comments |
|
|
Author: bblochlbblochl Date: May 12, 2008 01:31
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 also couldn't quite get the
> network going from the installer, but I didn't depend on that, anyway. If
> you boot from cd, just say /dev/sdD0/data.
>
>
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 solution for other users eventually
fighting with a similar problem.
|
| Show full article (4.44Kb) |
| no comments |
|
|
Author: Martin NeubauerMartin Neubauer Date: May 12, 2008 04:14
* bblochl (bblochl@fh-lausitz.de) 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 solution for other users eventually
> fighting with a similar problem.
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 gave me trouble in either
case.
> As you pointed out in your mail, the data must be somewhere in the
> installation process. That clearly is the CD that one has to mount as
> /dev/sdD0/data at the installation step "mountdist". But the
> Installation Manual is wrong as it is saying:
> "When prompted for "distribution disk" the usual value is /dev/sdD0/data
> - it is not, that never does work. The usual value must be simply "/"
> for that case of installation from this mounted CD, say sdD0!
Using /dev/sdD0/data worked for me. Did you actually try it?
|
| Show full article (3.82Kb) |
| 3 Comments |
|
|
Author: bblochlbblochl Date: May 12, 2008 06:19
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 gave me trouble in either
> case.
>
"My" trouble just begins at the task "Locate and mount the distribution
archive" or to be correct at the prompt for the "distribution disk".
Before that point everything is running "flush".
> Using /dev/sdD0/data worked for me. Did you actually try it?
>
One must decide between the prompt "mountdisk", where the input
"/dev/sdD0/data" is correct and the prompt "distribution disk" that
follows up, where the input "/dev/sdD0/data" will never be accepted (at
least in my configuration). I tried that many times for hours over hours
with many different test assemblies, bacause I blindly trusted the
"Installation Instructions". Well, I have explained in detail that I did
more than one trials to make shure that this is reproducible. Let me
repeat that the only successful and by the system accepted input (in my ...
|
| Show full article (7.73Kb) |
| no comments |
|
|
|
|
|
Author: bblochlbblochl Date: May 12, 2008 10:33
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", where the
input "/dev/sdD0/data" is correct and the prompt "distribution disk"
that follows up, where the input "/dev/sdD0/data" will never be accepted
(at least in my configuration)..........
Some additional infos to the VESA-Standard, I think is good to know:
The reason for the failure save function of the VESA standard is the
VESA BIOS extension (VBE), so most PCs have the VESA on board. VBE may
be implemented in hardware or in software. Some video cards that do not
support VESA natively carriy a particular additional hardware for VESA.
With some software even proprietary hardware will work in standard
software. So I am convinced that VESA as a standard (and others a s
options) is an absolutely safe bet.
Sorry for my strange English!
Bernhard
|
| |
| no comments |
|
|
|
|
