This might also help:
cd /sys/src/9
grep devattach */*.c | sed 's/(.*):.*attach\(L?''(.)'',.*;/\2 \1/' | sort
though it misses a few.
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/Tabc159d56e7ead54-M3614a029bcf71af0fb3e962e
Delivery opti
On Thursday, February 20, 2025, at 5:09 PM, ron minnich wrote:
> The next suggestion, btw, is "Go read the factotum document".
D'you mean this paper?
http://doc.cat-v.org/plan_9/4th_edition/papers/auth ("Security in Plan 9")
I confess, I've only given it a superficial read - which may be why I don'
I implemented extended attributes in my Linux 9P server:
term% echo Xuser.wow abcd >,ctl/foo
term% cat ,ctl/foo
dev 45831
inode 265868
umode 0100644
nlink 1
uid 1001
gid 1001
rdev 0
size 6
blksize 4096
blocks 16
atime 1739199962
mtime 1739199962
ctime 1740003632
atimensec 460383798
mtimensec 470383
(many months pass...)
I've recently been doing something a bit related:
While I've been refitting my old Linux 9P server, I decided to altered it to
use openat(2), and the other fd-relative *at calls. It used to keep an absolute
pathname string with each FID, so would start a file system walk f
I suppose we could have custom "Atlantic" paper size: the width of A4 and the
height of US Letter: 210mm x 11". That layout would fit on either size of
physical paper. It would also slightly increase everyone's average page count.
I have a draft WiP paper together - I think I'd want to tweak the
Quick question: does the paper size for submissions depend on the hosting
country?
I could be wrong but one of the US proceedings looks like US Letter size, and
the Irish one looks like A4...
Also, I'm hoping the three-page limit for WiPs is a little flexible? I can do
it four pages, but three
On Friday, February 14, 2025, at 3:48 PM, ron minnich wrote:
> This is very interesting, but I think the two problems you will hit are (1)
> the proliferation of these "," names everywhere and what they mean (do you
> include them in readdir? If you do, that's going to at least triple its
> leng
I've planned to pass xattrs through the ,ctl files, but haven't written the
code yet - I've only recently installed the xattr package on RPi debian and
read the man pages. It looks reasonably straightforward. It's been bottom of
the list, as I don't see a lot of things using them.
I've written
I have a complicated relationship with 9P2000.L. On the one hand it's been a
useful way to build file systems for Linux, and I've gotten some mileage out of
that. On the other hand, I'm not crazy about having a different protocol to 9P
(I've read through a lot of what's been said on 9fans about
Years ago I built an Remote Procedure Call library that used 9p as the wire
protocol. It handled event 'callbacks' by sending read requests to opened
virtual files well ahead of time and treating the eventual Rread replies as
events. As soon as it got an event it would send another Tread.
Perha
If mouse click events are queued and the keyboard modifier state changes are
not (or are queued separately), they can get out of step. By the time the
program receives a mouse click event, the keyboard may be unshifted again. This
could happen if a program is late processing mouse input.
---
On Monday, 30 September 2024, at 2:53 PM, Russ Cox wrote:
> While I'm writing, another interesting plan9port change is that I made
> shift-right-click in acme search backward from the current position. This is
> very helpful when you are cycling through many results and go one step too
> far. To
Thanks!
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/Tf4c3dc658874afea-M36739d26a8ea4c9534babbdc
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Is the presence of the duplicate names when reading a union directory actually
needed/used anywhere? Or is it just an artefact of the most straightforward
implementation for Plan 9?
I ask because I'm implementing the Plan 9 system calls on my own OS. If I don't
have to implement the name duplic
I left the oven on for my partly-baked idea.
I'm now thinking that with fd 5 as an example:
open ("#d/5dir/a/b/c", ...)
might be a practical way to do this (the syntax I suggested earlier would
require walking from a file, which wouldn't be sensible).
So I went snorkeling in the kernel to see
Well I got curious, and wrote a test program for my Linux RPi:
Doing the equivalent of what du(1) does (a recursive tree walk statting every
file) seemed to be about 15% faster with openat/fstatat than with open/lstat.
This was on a local drive (SD card).
Over 9p to my Plan 9 RPi from Linux it a
Moody wrote:
"What you _would_ want for this would be the ability to walk from the existing
fd, however the limits of 9p walk make this a bit impossible to implement in a
great way in my opinion. "
Maybe the chan could keep two fids: the original walked fid, and an opened
clone of that fid? Th
Are you thinking narrowly about "What changes to the Plan 9 kernel would you
make to emulate the Linux openat() system call" or more generally about "How
would you design a facility for plan 9 that provides an equivalent service?
As I understand it from the rationale section on the linux man pag
Oooh! More pixels!
This is wonderful, thank you!
I had the same situation, but I didn't know this was possible.
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T42a55b55ffb81417-M02cd60501c363e99ed9163bd
Delivery options: https://9fans.top
Well I had a go at this on my RPi. I altered libc.a to arrange that errstr()
removes the error string filename decoration, but print ("%r") doesn't, and
wrapped the open() call (as an example) to do its own error string decoration
and hand that back to the kernel.
Unfortunately I then looked in
(Lucio posted while I've been thinking/composing/trying things...)
Thanks for putting up with me!
I confess I've been thinking about this a bit more, as something about this
doesn't feel right:
As I understand it, the kernel is getting an error string from some file
server, and is decorating
Well, my daughter has kindly given me a couple of her spare raspberry pis - a
pi4 and a pi5.
I've put 9front on the pi4, and have been having a look at it. I had to use the
Raspberry Pi Imager program this time. windd didn't work (she thinks this might
be a feature of the later Pis). There are 5
Mystery solved: the bug was in my Ropen code. I was not returning QTDIR in the
qid.type when opening the directory.
I'd hazard a guess that because Rwalk said it was a directory, but then Ropen
said it was a file, sysfile.c:read() in the Plan 9 kernel didn't call
unionread(), so only the first d
> On Sunday, 4 February 2024, at 4:46 PM, moody wrote:
>> I would bet money on this being a bug in your walk code.
That seems entirely possible! Thanks for the pointer.
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/Tbc78d29ab04652a2-M366
Hello Plan9People!
I finally stumbled across Richard Miller's Raspberry Pi image a while back and
managed to install it on an RPi, and have been learning more about it. I've
used the 9P protocol for a couple of projects, but haven't actually used Plan 9
itself until now...
So far I've patched
I'm no expert, but I use a British keyboard on my RPi, so I have encountered
the need to change the key map.
I would expect that the 'de' key map file will be designed for this keyboard
layout: https://en.wikipedia.org/wiki/QWERTZ#Austria_and_Germany
Perhaps check whether your keyboard looks lik
26 matches
Mail list logo
