hello
I have it booting now. I did a disk/format using the 9load from the cdboot
image, and the 9pcf kernel from the iso.
Now i'm getting messages about caught missed ide interrupts. . .and this slows
down disk operations a lot, i guess first fossil dump to venti will take ages.
now i'm
hello
Seems I fell again in the bios ahci set up trap. Checking the BIOS options
seems it was in Enhaced Ide mode instead of Enhaced AHCI mode.
Now the iso works perfectly. For those of you looking for a modern PC to run
plan9, this is what i have:
* asus P6T SE
* Core i7 (4 core works)
* 4GB
I have it booting now. I did a disk/format using the 9load from
the cdboot image, and the 9pcf kernel from the iso.
Now i'm getting messages about caught missed ide interrupts. . .
and this slows down disk operations a lot, i guess first fossil dump
to venti will take ages. now i'm stuck at
9atom from this weekend boots and install with no problems setting up AHCI
mode first.
please send your pci output anyway. ide should work.
even if *nomp=1 so to do that we'll need to do the pcirouting
stuff, and for that we need a southbridge pci vid/did.
- erik
The following is a little patch to 9vx which uses getenv to read the
environmental variable PLAN9 to set plan 9 root on startup if it has not
been overloaded on the command line or in the CWD. I would enjoy any feedback.
Best regards,
EBo --
recommend using a different environment variable
other than PLAN9, since that is taken by p9p to mean
something else.
- erik
2010/4/11 erik quanstrom quans...@quanstro.net:
recommend using a different environment variable
other than PLAN9, since that is taken by p9p to mean
something else.
Agreed. PLAN9ROOT seems good.
--dho
- erik
Agreed. PLAN9ROOT seems good.
suggest 9vxroot instead. there are enough plan9y
things floating around that it makes sense to me
to specify which plan9y root you're talking about.
and there's no reason to shout. :-)
- erik
Got it! Changed. I'll also change it along the lines of Erik's suggestion.
As a note, I thought that 9vx ran on top of the p9p stuff.
Thanks again,
EBo --
Devon H. O'Dell devon.od...@gmail.com said:
2010/4/11 EBo e...@sandien.com:
I thought p9p uses it for the root of the Plan 9
I was going to suggest that, but you can't start env. var. names with
numbers in many shells.
i'd forgotten about that. unix really has gotten
crunchy.
- erik
I was going to suggest that, but you can't start env. var. names with
numbers in many shells.
That's why I named it vx9root (not to screem). ;-)
and there's no reason to shout. :-)
I'm running timesync here on a sheevaplug and an openrd-client.
The invocation was
aux/timesync -s /net -nl -d /sys/log/timesync.d chips time1 time2
100 µs accuracy seems unlikely; you might try dropping the
`-a 10' from your invocation.
ah, yes. thanks for the reply. i'd
I'm playing around with 9vx and have split up (re)building 9vx from the the
9vx root file system provided in the tarball 9vx-0.12.tar.gz
When I first start 9vx from a clean build and run /sys/lib/newuser it builds
the user directory in /$user instead of /usr/$user. The problem appears to
arize
When we try to cd to $home, it does not exist (as checked by the previous if),
and $cwd is set to / by default... The following patch simply makes $home
before cd'ing to it.
Is this supposed to be the expected nehaviour?
EBo --
=
--- a/sys/lib/newuser
newuser assumes that your home directory exists, and on a
normal plan 9 install, it's likely not possible to create anything
in /usr without doing it on the fs console.
Maybe I am missing something here, but this is not a normal plan9 install, but
9vx. There I can create a user's directory
On Sun, Apr 11, 2010 at 7:04 PM, EBo e...@sandien.com wrote:
newuser assumes that your home directory exists, and on a
normal plan 9 install, it's likely not possible to create anything
in /usr without doing it on the fs console.
Maybe I am missing something here, but this is not a normal
On a real plan 9 system, you create the user at the file server
console, then log in as that user and run newuser. That first step
creates /usr/$user. The analogue in 9vx is at least 'mkdir /usr/
$user', and (less likely) possibly creating the actual user in the
unix world, depending on
Why isn't 9vx -r yourdir good enough?
Russ
gs when compiled on arm for arm doesn't work.
gs when compiled on 386 for arm does work.
i boiled down the problem case to this wierd define
from /sys/src/cmd/gs/src/ztype.c
; cat p2.c
#include u.h
#include libc.h
#define ALT_MIN_LONG (-1L (sizeof(long) * 8L - 1))
void
main(void)
{
Why isn't 9vx -r yourdir good enough?
it is if you want to force all users to specify the root directory every
single time they run 9vx, or if you want to use an alternative root. If I use
a standard install locations then we can either change /Users/rsc/9vx and
/home/rsc/plan9/4e or I can
Anthony Sorace a...@9srv.net said:
On a real plan 9 system, you create the user at the file server
console, then log in as that user and run newuser. That first step
creates /usr/$user. The analogue in 9vx is at least 'mkdir /usr/
$user', and (less likely) possibly creating the actual
create the user dir on the host machine. run 9vx -u $user and then run
/sys/lib/newuser.
you seem to be following the wiki instructions on how to add a new
user. they are not valid for 9vx, since it usually uses the hosts
filesystem.
is there already a 9vx specific tutorial?
EBo --
Anthony Sorace a...@9srv.net said:
On a real plan 9 system, you create the user at the file server
console, then log in as that user and run newuser. That first step
creates /usr/$user. The analogue in 9vx is at least 'mkdir /usr/
$user', and (less likely) possibly creating the actual
23 matches
Mail list logo
