Noam Preil:
> I have a
> branch at https://git.sr.ht/~pixelherodev/plan9 which has fossil
> integrated.
I took the liberty of having a look at the fossil source in that repo.
It seems to be missing the fossil-time-backward patch. That's on the
current 9legacy distribution ISO (built 14 April
Noam Preil:
> I demonstrated one
> of the problems with fossil by (attempting to) install Go, which crashes
> the file system _every single time_.
This is a useful bit of evidence that needs following up. The go test
suite (which begins by installing and completely rebuilding go) is
running 24/7
Jacob Moody:
> I'm very glad we were able to communicate this and thank you for taking
> the time to talk about this here in this thread.
And thanks to you for pointing me to the GTX 4090 and https://crack.sh
Both real eye openers.
--
9fans: 9fans
me:
>> (OK, I know that's delusional because I've installed go. But maybe
>> not for much longer, as google seems determined to introduce python3
>> as a dependency.)
Charles Forsyth:
> wat!??
citation:
https://github.com/golang/go/issues/62025
--
9fans:
cro...@gmail.com:
> As for the proposed strawman `p9sk3`, I fail to see what advantage
> that would have over dp9ik
My point was only about the advantage of p9sk3 over p9sk1, not to
compare it with anything else. The intent was to counter the implication
that p9sk1 is terrible and completely
me:
>> I try to take a
>> minimum-intervention approach ...
cro...@gmail.com:
> Forgive my saying it, Richard, but I think this is a somewhat overly
> staid view of things.
You're welcome to say it. My minimalist attitude amounts to a religion,
and therefore I don't need to justify it ☺. I know
23h...@gmail.com:
> ... the server and client keys are the
> same in p9sk1 as far as i understood. i would welcome public/private
> key system though (is that what you were thinking of when separating
> "server key" and "client key". that would add yet another set of
> features that are currently
Jacob and Ori, thank you for filling in some more details. Without
the specifics I had been making some wrong assumptions about where
the exact threat was.
I think I now have a clearer picture:
It's not particularly p9sk1 which is vulnerable, but the protocol
for ticket request / response, which
23h...@gmail.com:
> sorry for ignoring your ideas about a p9sk3, but is your mentioning of
> ocam's razor implying that dp9ik is too complicated?
> is there any other reason to stick with DES instead of AES in
> particular? i'm not a cryptographer by any means, but just curious.
My comments are
I'm using a new subject [was: Interoperating between 9legacy and 9front]
in the hope of continuing discussion of the vulnerability of p9sk1 without
too many other distractions.
mo...@posixcafe.org said:
> If we agree that:
>
> 1) p9sk1 allows the shared secret to be brute-forced offline.
> 2)
> From: o...@eigenstate.org
> ...
> keep in mind that it can literally be brute forced in an
> afternoon by a teenager; even a gpu isn't needed to do
> this in a reasonable amount of time.
[citation needed]
--
9fans: 9fans
Permalink:
The SD card has a dos partition, not a 9fat partition, so unless
your raspberry pi has a usb hard drive the 9fat: command won't work.
Instead you can use the c: command, which mounts the first dos partition
it finds onto /n/c
--
9fans: 9fans
Permalink:
> Tried it; output:
> syntax error reading partition
> 488
>
> So my partition count is too much, correct?
Correct. The last line has been truncated at the end of the block
so it has no newline, which is a syntax error.
It's ok to use fdisk to create more than one plan9
I said:
> You might have to split it up
> into two fdisk partitions, or shorten some names.
Actually, shortening names isn't likely to help much.
If you're setting up a new venti, not expanding an
existing one, could you make the arena partitions
fewer and larger? The original idea behind
> ...
> the bloom, isect7 and arenas7 partition are gone.
> ...
> What's causing that?
The partition table has to fit in one disk sector. Has yours
got bigger than 512 bytes? You might have to split it up
into two fdisk partitions, or shorten some names.
Try 'disk/prep -p /dev/sdE0/plan9 | wc
> We do not provide the binary files ourselves you need to acquire them from
> the rasbian ISO.
Or look in https://github.com/RPi-Distro/firmware-nonfree/raw/buster/brcm
--
9fans: 9fans
Permalink:
> In the meantime, I turned off "registerization" for files that could
> potentially have similar code.
If you want a more targeted workaround without a performance cost,
in the example you posted you can force the compiler to reload the
register by replacing
return y;
with
> Is the problem with the compiler or with the C code?
It's a compiler error. The function mkvar() in reg.c is keeping track
of unique variables without taking address aliasing into account.
--
9fans: 9fans
Permalink:
> Last thing about your rpi image Richard, Is this the
> one used in the go arm builders? Can I asume that
> these are the only patches needed to have a working go?
>
Yes, and yes.
--
9fans: 9fans
Permalink:
On Thursday, 14 September 2023, adr via 9fans <9fans@9fans.net> wrote:
Hi Richard. I'm surprised by the small number of 9legacy patches you are
> using. Any reason in particular that you could share? I'm preparing a new
> installation and this is a good time to choose the starting point.
>
>
The
> the system loads into the GUI but then hangs moments later and stops
> updating the frame buffer, or the system is hung. Any thoughts on why that
> might have occurred? Is this to do with the watchdog...?
It won't be the watchdog, because this QEMU patch prevents it
from being enabled.
> The thing about 9legacy is I'm not sure what patches to pull and what is or
> isn't stable do you have any recommendations?
I've put a script in contrib/miller/build-9pi.rc which shows the complete
process of building (almost) the 9pi image from the 4th edition ISO. You
can look at that to
> Based on the diffs you supplied, it looks like my bcm
> sources (from the latest r4 ISO) are not the same as yours. I don't use
> 9front. What is the best way to make sure my bcm (and 9) kernel trees are
> the same as your current tree?
A lot has changed in the bcm kernel since the 4th edition
> I'm using version 8.0.0 of QEMU. What version are you using, Mr. Miller?
I've now reinstalled QEMU from debian unstable, which gives me v8.0.4.
Using the 9pi2.qemu in my contrib, it still boots for me, without any
loop at 0x000c.
--
9fans: 9fans
don.bai...@gmail.com:
> Hmm, I've applied the patches and built the kernel. I can see the image
> loaded at 0x8001, but it is spinning at address 0x000c; is this a
> sdmmc load loop?
I think that's a trap address. On ARM we re-map the trap vectors away from
address 0 to a high segment.
>
don.bai...@gmail.com:
> So to get this back on the track of RPI emulated in QEMU … has anyone
> successfully used the Miller image with Q?
After a bit of experimentation, I have done so, for some value of
"successfully".
A few tweaks are required first, because QEMU's emulation of Pi hardware
> ; read -c 72 /dev/wctl
Or, if your chosen flavour of Plan 9 doesn't have the 'read -c'
option, one of these will do:
dd -if /dev/wctl -bs 72 -count 1 -quiet 1
syscall -o read 0 buf 72 [2]/dev/null
--
9fans: 9fans
Permalink:
> Is there a version of kencc somewhere that can be easily built
> and installed on Linux and used as a plain C compiler?
>
> I'd prefer for x86_64 but I'll take one that only compiles 32 bit.
https://github.com/inferno-os/inferno-os/tree/master/utils/6c
There are also various forks on github
I said:
> If you want to boot the pi4 completely from a USB drive, with no
> SD card present (I've never tried this), you'll need an alternative
> place for a fs(3) configuration (maybe in the built-in bootdir in
> the kernel?), or the boot code will need tweaking to get the partfs(8)
> partitions
> But many thanks for the fs(3) hint. I’m looking into it.
Apologies. To configure a usb disk using fs(3) at boot time, you need
this change to /sys/src/9/boot/local.c which hasn't gone into the
9legacy tree yet:
/sys/src/9/boot/local.c:277,286 - local.c:277,286
if(bind("#p", "/proc",
ma...@germteig.com:
> I am running the Dec 22 9legacy on a machine, and now want to create a
> bootable USB on it.
> The USB is for a raspberry pi 4 4GB, acting as a standalone auth only.
When you say "bootable USB", do you want to boot the pi4 without an
SD card, and just a USB drive?
If
Deleting an open file on ramfs(4) can have surpising results.
Here's how it's supposed to behave. When a file is removed, the
Ram struct which represents the in-memory file has its busy flag
reset, so a subsequent i/o will see that it's been deleted.
cpu% ramfs
cpu% echo this is x >/tmp/x
cpu% {
> I don't know any reliable server with good bandwidth serving without tls
I am able to connect to your example arch.mirror.constant.com using
both http and https.
Something is going on with usb ethernet and tls which I don't understand.
Could it be as simple as different block sizes interacting
> By the way Richard, should I take the last rpi image at 9legacy as
> the more recent with your work? Are you going to abandon
> https://plan9.io/sources/contrib/miller/?
9legacy should always have up to date patches for the Raspberry Pi, and
the 9legacy SD card image will usually be fresher
>> See the difference? That's a little more than 19Mb/s, some 2MiB/s almost 50%
>> slower.
>
> That was a typo, is almost five times slower (~80% slower). Just
> to be clear, it is really worst!
Unless your "small arm linux machine" is a raspberry pi, you are changing
too many variables to make
> Shouln't the usb type be documented in the ethernet section of plan9ini(8),
It should be documented somewhere, but at present it's only implemented
for the bcm kernel, and raspberry pi doesn't have a plan9.ini. (It sould be
possible to move etherusb.c to /sys/src/9/port and use it on other
> So bad maxpkt... etherusb check for maxpkt < 512 which is the max for
> bulk transfers in usb2 high speed. Using 1024 instead fixes the problem.
Thanks, the code was correct when written but the world has moved on!
Is your adapter transmitting packets successfully now?
> Should it chek for the
> Other programs expect the devices mounted in
> /net. I'm binding the device inside a directory in /tmp and then
> binding this directory to /net. I would appreciate if someone shares
> the correct way of doing this.
Two ideas come to mind:
% mount -a /srv/usb /net
(then all usb devices
What you're trying to do should work. I've just checked an ASIX usb2 ether
dongle on a pi4 as '#l1', usbd recognises it and I can mount '#l1' on /net
and configure it. I did have to add etherusb to the kernel config and rebuild
first, as you did.
The tricky part is that the real usb ether driver
There's a new patch bcm-lpae which uses the 64-bit page table format to
allow 32-bit ARM kernels to support more than 4GB of physical memory. At
present this is mainly of interest for the 8GB Raspberry Pi 4, but there's
nothing Pi-specific in the MMU code so it may have future application for
Hi there-
Please pardon the dumb question if this has been covered before. I did some
brief searches of the archive and couldn't find it...
I'm running plan9port on macOS. I noticed that in acme, (and also sam) if I
select part of a string and p delete, the selection gets deleted and
lyn...@orthanc.ca:
> Bluetooth (and BLE) support woould be *very* nice to have.
I have a native bluetooth host implementation for Plan 9, not ported
from anything (it's written from scratch based on published bt specs.)
I don't regard it as sufficiently debugged for a release ... it's
missing
> !rc (and the rest of the boot) is one of the first things implemented
> uniquely by 9front.
I think there's a little bit of confusion about different stages of booting.
The 9boot program loads the kernel. The original Plan 9 9boot is driven
by configuration variables in a plan9.ini file.
Hello Yakku -
I couldn't reply to the email you sent me off-list.
The returned error was "User unknown in virtual mailbox table"
-- Richard
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/Tb5aaf646618a421a-M6db08da236580ae316905718
> Sorry that doesn't seem to work either. I've tried sdB0, sdB1,
> sdC0, sdC1, sdD0, sdD1, sdE0, sdE1 . . . but the issue persists.
That appears to be a dead end.
To answer your earlier question, you could use dd (or pump(1)) to
copy the usb image to your hard drive, if you're happy to sacrifice
> I've tried to boot via CD again (mind it's from a USB CD drive
> in case that makes any difference)
Yes, that makes a difference. It may appear as sdB0 or sdB1.
--
9fans: 9fans
Permalink:
> I've also tried to boot it from a CD, but I always get stuck at the 'Boot
> from:' prompt
Try sdC0!cdboot!9pcflop.gz
And local!/boot/bzroot for the root filesystem prompt.
If your hard drive is configured in AHCI mode by the BIOS, it
should be seen as sdE0. If it's in ATA compatibility mode,
> In the meantime I have some low-level programming work with your compiler
> and tinyemu running on a Raspberry Pi 2B.
That's good to know. My original motivation for developing the
riscv toolchain was to use in "bare metal" programming of riscv
soft cores implemented on FPGA.
> It can't find *9tecpu.bin*.
> I presume that it's the Plan9 kernel.
> Any suggestions as to what steps to take in order to generate it?
Up to now the procedure for getting the 9k riscv kernel source
is to ask its author (Geoff Collyer) for a copy.
--
> Self-inflicted confusion : I'm running 9vx and forgot that I was mk'ing an
> emulator to run within an emulator.
Part of the confusion was my fault: I should maybe have removed the
Makefile (and other linux-only components) instead of leaving them
in as reference material.
> The make command failed with dependency on slirp module.
I don't think plan 9 has a 'make' command. If you just run 'mk'
on plan 9 in the tinyemu directory, it uses the mkfile there
and there's no slirp dependency.
--
9fans: 9fans
Permalink:
> I had difficulty in getting tinyEmu from contrib/miller/tinyemu.tar
> working.
Can you be a bit more specific about your difficulty? How far did you
get, what exactly didn't work?
To use networking, your Plan 9 kernel needs bridge(3) configured in.
In tinyemu.tar there's an example bridge.rc
> $ uname -a
> Linux dell 5.4.0-89-generic #100-Ubuntu SMP Fri Sep 24 14:50:10 UTC
> 2021 x86_64 x86_64 x86_64 GNU/Linux
That's impressively up to date. I'll see if I can do likewise.
--
9fans: 9fans
Permalink:
> Go built successfully after enabling the v9fs mmap caching on mount!
OK, that's good news. What linux kernel are you running?
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/Tb065f4df67a8bab9-M8354696be6c4a677c85e819b
Delivery
>> 1. Some of the fpga tools are closed-source so I can't check with
>> confidence that they will never try to use mmap.
>
> Um, nm(1) on the binary to see what it calls?
If you were distributing closed-source proprietary tools, would you leave
the symbol tables intact to assist reverse
> But is it not possible that the FPGA tools don't
> have the same issues with mmap that e.g. Go does?
1. Some of the fpga tools are closed-source so I can't check with
confidence that they will never try to use mmap.
2. The go compiler is open-source so it was a simple matter to make
an
> What, precisely, is your use case?
As I said, the go cross-compile was just an example task to
test the viability of v9fs. I don't *need* to cross-compile
on linux: the 9pi image, for example, comes with native
go binaries which I can use for bootstrapping.
The real use case is to have some
> Skip, did you specify -o cache=mmap when mounting diod service
> for the go build experiment?
I tried it myself using local diod and cache=mmap. I get a similar
SIGBUS on instruction fetch again. Conclusion: as Bakul says, now
I'm debugging linux. Not going there, thanks.
Going further
> I think the question is why mmap works over 9p from linux up to a point but
> then fails in some context: what's the difference?
Skip, did you specify -o cache=mmap when mounting diod service
for the go build experiment?
--
9fans: 9fans
Permalink:
> there is a 9P2000.L variant that seems to
> kitchen-sink all Linux fs calls into 9P. There's a file server
> (https://github.com/chaos/diod) that implements it. It would be
> interesting to know if your case fails using it.
Sorry, I've cloned & built diod but I can't quite see how to
deploy it
> if you just want to make forward
> progress in the short term, perhaps consider using the local Linux
> filesystem and exporting that to plan9 using a user-space 9p server?
Sure, that's what I did years ago to bring up go-plan9 without an
existing native go-plan9 to bootstrap from. The
> Can anyone suggest other mount options I should tweak?
I have tried cache=fscache and cache=loose. In both cases I see startling
cases of incoherency: ie reading file X returns contents of file Y (neither
of which has been modified for months).
Maybe my linux kernel is too old? (4.9.0-5-amd64)
> what you did was compile pprof (not shown...) great!, and then when you ran
> it,
> it failed... on the same machine?? but surely a cross plan 9, cross
> compiler/lnker/env
> is for getting plan 9 binaries going...
> or is your prompt modified??
I'll annotate the error message a bit for
> adding 'cache=mmap' to the mount options
> makes it work beautifully!
Not quite beautifully, it turns out. The build proceeds a lot further,
but ends with a memory fault as reported below.
Can anyone suggest other mount options I should tweak?
$ GOOS=plan9 GOARCH=386
> Should this be expected to work? Or is mmap not supported over v9fs?
OK, found the answer: adding 'cache=mmap' to the mount options
makes it work beautifully! I suppose there's a good reason this
isn't the default ... (?)
--
9fans: 9fans
Permalink:
I'm trying to cross-compile go for plan9-386 using go-linux-amd64
(on a linux laptop) with the source tree mounted from a plan 9 server
via v9fs (mount -t 9p).
All goes well up to a point, then this happens:
/mnt/sys/lib/go1.17/pkg/tool/linux_amd64/link: mapping output file failed:
invalid
> If you really need to work with extremely
> complex codebases you likely won't find success using plan9 at all.
When I need to scrabble around in the go source tree, I usually have
something like this in a window (it could go in an acme guide file)
grep -n 'func XXX' `{du -a | awk
> Of course I haven't done this yet, but is there any information on how to
> write drivers in Plan 9?
Reading the source code of existing drivers is a good way to learn.
> And the second question: if there is a second
> raspberry already connected to the Internet, how can you distribute the
>
> if there is a usb wifi adapter, how can
> it be run in plan 9?
By writing a driver to go in /sys/src/cmd/usb/ether ☺
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T3464a8c7bad3062a-M1c77c726db10ebeba6260989
Delivery options:
> I have Raspberry Pi 4B (1 Gb RAM) and how to run wifi (and setup wifi) on
> it ?
Assuming you're running with root fs on SD card, and
no ethernet connected.
Assume your wifi ssid is MYSSID and uses wpa2 authentication,
and your wifi passwd is MYPASSWORD.
In cmdline.txt on the DOS partition,
to confirm that this your E-mail
address is still valid before giving you any further details.
Thanks for your time and welcome a positive response through My
private email: richard.mil...@mail2one.com
Thanks in anticipation.
Mr. Richard Miller
> FWIW in 9front you can jump into rc while booting and fix this sort of
> issue.
Sure, having an in-kernel file system with rc and some tools for
file system exploration and repair is another alternative to having
them on a spare partition or usb drive or whatever. One could even
imagine a
> it just becomes difficult
> to do anything when no fossil blocks can be allocated
Thinking a bit further about this: intuitively one might expect to be
able to reboot using a local file system which is completely full, and
use du and ls to find big files and rm to delete them, without the need
st...@quintile.net:
> However if fossil fills up - because more has been written to it than
> it can hold or because snapshots have been turned on without a venti
> attached, it will crash badly and can (I believe) lose user data.
No, it won't lose data (except in the sense that incoming mail,
fde...@fjrhome.net:
> Either that or you would need to replace rio with something more
> touchscreen-friendly, in the process losing much of what makes the Plan
> 9 environment as unique as it is from a user interface perspective.
>
> Most "modern" phones also lack a suitable keyboard to
> Some modern disks use the "UASP" protocol in preference to the
>> traditional bulk-only mass storage protocol supported by the Plan
>> 9 usbdisk driver...
>
> Richards that patch makes other devices to not work, have you tested
> it after compiling all usb and kernel?
No, it was an experiment
I said:
> But despite the message you won't see it in /dev/sdU9.0 when starting usb/disk
I remember now: just do 'usb/disk -m /dev' to get the sdUX.Y mounted where you
want.
adr said:
>now the sd disk appears in /dev, but I can't set up the
>plan9 partitions:
> ...
>Thanks anyway.
If you're
> No luck!, although the end points appear now after manually executing
> usb/disk.
> ...
> disk: logical block size 512, # blocks 7814037167
> usb/disk: fsadd sdU9.0
Once you've reached that point, it looks like the driver is handling the disk
ok.
But despite the message you won't see it in
> I can connect to github too, and some other places. But if you surf the web
> you'll end up with this error. Just a few If you want to do a test:
>
> https://developer.arm.com
> https://wikipedia.org
> https://marc.info
> https://www.perseus.tufts.edu
> http://mars.jpl.nasa.gov
Thanks, I did a
> Below is a patch ...
Something in the 9fans pathway has expanded the tabs in my patch into
8 spaces. Irritating. If you want to apply the patch, it will probably
be necessary to turn them back into tabs.
--
9fans: 9fans
Permalink:
To be pedantic, the troubles you describe are not strictly "9pi image problems",
you will likely find that 4e Plan 9 on any architecture will behave the same.
The usb subsystem is known to be pretty rudimentary, and indeed with respect
to power management /sys/src/cmd/usb/usbd/usbd.c:/^portattach
> The really odd part is I just moved the SD card over
> from a pi3 that was booting fine with dhcp.
Does the MAC address in the dhcp request look right?
--
9fans: 9fans
Permalink:
I have no personal experience of the pi400 but I believe the ethernet
hardware is identical to the pi4. Could it be a configuration problem?
Can you run snoopy or equivalent on the network segment and see if the
dhcp requests are being transmitted? And check the dhcp server log to
see if there's a
> Is there a list of known to fail tests?
All tests should pass, but you may need to set a longer timeout than the
default if your virtual environment is slow.
--
9fans: 9fans
Permalink:
> go tool dist: Failed: exit status: 'go 6839: 1'
> all.rc 165: go 6566: 1
> ===to here==
>
> It took about half a day to accomplish!
Some things that can make go tools and test suite quicker:
- use ramfs for /tmp
- use a local file server, with local disk or aoe on a fast connection
-
> srv net!9p.io!9fs: mount failed: fossil authCheck: auth protocol not finished
>
> I have no account on 9p.io...
srv -n 9p.io sources /n/sources
--
9fans: 9fans
Permalink:
I need my phone rooted.could u hop
> is there an email address to contact p9f directly?
bo...@p9f.org goes to everyone on the board.
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/Ta6a7f3df36695764-M9c6490d4e2b4b5bb43a88ce9
Delivery options:
>> I declare that the old bcm kernel found in the p9f code is OK
>> to be redistributed under the MIT license.
> Is the new one in your contrib directory OK to be redistributed under
> the MIT license too?
That's what it says on the index webpage, and I know no reason to
believe otherwise. I'm
> Richard Miller being in this very thread, you could presumably get him
> to say "I declare that the old bcm kernel found in the p9f code is OK
> to be redistributed under the MIT license" and be done with it.
I declare that the old bcm kernel found in the p9f code is OK
> The code under discussion
> in Richard Miller's contributed bcm kernel.
The web page http://9p.io/sources/contrib/miller/9/bcm says
"Distributed under the MIT License" with a link to the p9f text.
Is that not explicit enough?
That's the whole bcm kernel (a superset of what appears in an
> I'm talking about things like the bcm kernel contributed by Richard Miller in
> the 4e-latest tarball, they weren't written at Bell Labs but were contributed
> back to Plan 9.
I would have thought any third party code in the /sys/src tree is considered
to be a "Contributi
> I want to use Plan9 compiler (8c) on my windows 10 system.
Not possible except by running Plan 9 on a virtual machine.
You can, however, use the inferno version of 8c on some windows platforms.
I don't know if windows 10 is one of them.
--
9fans: 9fans
> I'm new to plan9 and don't know
Yes, all of us have been at that stage originally.
The way to progress is by reading ... man pages, contents of /sys/doc, and
if you really want to understand things well, the source code.
lookman is a useful command to suggest which man pages might be
> 1. Dual booting is not possible
> 2. UEFI introduced vulnerabilities ...
Don't these two things cancel each other out? Can we not use
the same vulnerabilities to induce the firmware to boot our
own choice of operating system? It wouldn't be the first time
Plan 9 was installed using ... shall
> I want it as a dual booted os on my system
The standard CD works best to install Plan 9 as the first or only
operating system on a machine. Do you have an empty hard disk? Or
an empty primary partition? If installing on a partition of a shared
disk, it's safest to use your existing operating
> don't I need to burn it?
You need a CD with exactly the contents of plan9.iso beginning at sector zero.
How you make that depends on what operating system you're using. (I only know
how to do it on Plan 9, which won't help you much.)
--
9fans: 9fans
> I want to install Plan9. Can you please tell me the right way to do that.
The traditional way is from the CD image. If you expand plan9.iso.bz2
with the bunzip2 utility to produce plan9.iso, and make a CD of that
expanded image, you should have a bootable installer.
> I downloaded the USB Disk image from there
> https://9p.io/plan9/download/usbdisk.bz2
I think that's not an installer image. It's a self-contained Plan 9 system
(CPU kernel and fossil filesystem) which you can run from a USB flash drive
without having to "install" anything ... provided, that
> That is, if I plug into a ~10 year old Vizio television
> everything works fine at a reasonable resolution (1280x1024? I haven't yet
> figured
> out which utility to use to query display properties)
Here's a simple way:
term% echo `{dd -if /dev/screen -bs 64 -count 1}
> , but if I plug it
1 - 100 of 1676 matches
Mail list logo
