Ah. You're right, of course. The critical bit I missed was that
it's Plan 9 complaining, not vacfs (per se) or even 9p. I can't
test vacfs on the Mac right now (9pfuse isn't getting along
well with macfuse), but '9p ls' shows the full listing for /
complete with anti-social files.
It would be nice
Both the vac file format and p9p can handle files
that Plan 9 cannot. Other than anti-social characters
in file names, they also handle symbolic links. There are
people who use vac and p9p but have never used Plan 9.
Imposing Plan 9's restrictions on non-Plan 9 users seems odd
and certainly isn't
HFS (and derivative) volumes contain one or both of the folloing
directories with astoundingly anti-social names:
HFS+ Private Data
.HFS+ Private Directory Data
(that's a at the end of the last one). This is an awful hack
to support hard links. There may be others (I think at s
On 7/19/08, Russ Cox <[EMAIL PROTECTED]> wrote:
>> I think it would be good to place the for-loop
>> in a "if(~ $dmamode yes)" as well.
>
> I don't see the point of that one. If you're running
> vmware, you want dma on, no? Otherwise the disk
> is very slow.
Well, the "use DMA for ide drives[yes
i've put up a lightly corrected version of covington's
newbie guide
http://www.quanstro.net/newbie-guide.pdf
many thanks to geoff for his input.
- erik
> I think it would be good to place the for-loop
> in a "if(~ $dmamode yes)" as well.
I don't see the point of that one. If you're running
vmware, you want dma on, no? Otherwise the disk
is very slow.
Russ
On 7/18/08, Antonin Vecera <[EMAIL PROTECTED]> wrote:
> I proposed a patch which turns off hw acceleration for vga if you boot
> in VMware.
> But now I find out that it is necessary to do the same in installation tree.
> So, if anybody can, please, correct this file /386/bin/aux/vmware on
> install
