On Wed Jun 22 21:12:01 EDT 2011, lyn...@orthanc.ca wrote:
> > you may wish to download just the kernel.
>
> I've given up on Parallels. And VMware (where I leapt to after Parallels 5
> stopped working). For half the price of either, Craigslist will spit up
> hardware that will run Plan 9 on bar
you may wish to download just the kernel.
I've given up on Parallels. And VMware (where I leapt to after Parallels 5
stopped working). For half the price of either, Craigslist will spit up
hardware that will run Plan 9 on bare metal.
i've incorporated the patch and rerolled the cd. unfortunately
it's not tested because i don't have any igbe anymore. the change
to the eeprom access might be a problem, but i think just an extra
clock cycle should be okay.
you may wish to download just the kernel.
- erik
On Wed Jun 22 20:41:07 EDT 2011, lyn...@orthanc.ca wrote:
> But speaking of annoyed, have you done any DSDT rewrites to get gear
> going? From what I've seen of EFI it seems like it's just an excuse to
> rewrite all the fucked up ACPI tables they (read: intel) got wrong the
> first time around.
But speaking of annoyed, have you done any DSDT rewrites to get gear
going? From what I've seen of EFI it seems like it's just an excuse to
rewrite all the fucked up ACPI tables they (read: intel) got wrong the
first time around. sigh.
don't worry about it.
I was worried about the mailing list, and not you my son ;-)
On Wed Jun 22 20:31:59 EDT 2011, lyn...@orthanc.ca wrote:
> > --annoyed
>
> At Parallels, not Eric.
don't worry about it.
- erik
--annoyed
At Parallels, not Eric.
Just to add to the misery, I tried a 9atom (from three days ago) install
in Parallels 6.0.12090.660720 (2011-05-26 build date, apparently). It
hangs after lamenting "igbe: unusable PciCLS: 0, using 8 longs."
Screenshot attached, FWIW.
--annoyed<>
On Wed Jun 22 12:00:07 EDT 2011, fors...@terzarima.net wrote:
> >ifs seems a holdover. it's only ever used in `{} yet
> >it's a global inherited variable. so it's easy to write
> >a script that assumes that ifs is set to the default.
>
> i wonder if it's best left alone. it isn't detailed enough
>ifs seems a holdover. it's only ever used in `{} yet
>it's a global inherited variable. so it's easy to write
>a script that assumes that ifs is set to the default.
i wonder if it's best left alone. it isn't detailed enough
to crack many plausible formats, for instance full csv.
if i needed one
>ioctl was handled by having the client "know" exactly what each ioctl "looked
>like", i.e. it only worked for known cases.
there isn't really any other choice, especially between machines
with different conventions. i think it was one of the bigger parts
of the newcastle connection implementatio
I can't remember ever having lost data with fossil+venti,
on two complete networked systems that have been running
on fossil/venti since 2004 and 2005, and they both store
quite a bit:
[2004]
index=main
total arenas=11 active=7
total space=51,385,286,656 used=28,842,582,973
clumps=10,363,594 compr
On Tue, Jun 21, 2011 at 7:54 PM, Russ Cox wrote:
>
> sam -a
>
That is great! I didn't see it in 'sam -h' but looks like the p9p
manual has that listed. Thanks.
> directory (I think we know who's fault that is)? Your dog tripping over
> the power cord with no battery backup doesn't count...
at least where i live, that sort of thing does count. battery backup
is not infiinite. but then again, i'm biased heavily against data loss. :-)
- erik
Fellow 9fans,
I am about to build a large-ish fileserver to go along with my cpu/auth
machines (native and qemu).
I'd like to know some recent real world experiences with fossil+venti.
This stems from rumors that for some people, fossil has a history of
data loss. I don't like rumors (or da
16 matches
Mail list logo
