Re: [9fans] troll paper
Never mind, https://iwp9.org/10iwp9proceedings.pdf > On Apr 12, 2024, at 06:56, David Arnold wrote: > > >> >> The vetting process needs some work, lads. > > More heresy than trolling, perhaps? > > It was thought-provoking for me. I wished I was there for the bar session > afterwards. > > d -- 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T51f7f5a8927e1271-M9dd436078709478f3864eb51 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Re: [9fans] troll paper
Where’s the link? I haven’t seen one yet for reading papers in advance. Still one hour to go… > On Apr 12, 2024, at 06:04, Anthony Martin wrote: > > "Do we really have to have our own kernel? What are > the benefits?" ... > > The IWP9 paper titled "centre, left and right" looks like > a complete troll. Was it generated by an LLM? I read the > whole thing and it was a waste of time. Zero stars, would > not recommend. > > Institutional Academy of the Academic Institute, lol. > > The vetting process needs some work, lads. > > Cheers, > Anthony -- 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T51f7f5a8927e1271-M73f3dc3b7bb66b0db2117c83 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Re: [9fans] nfs timeouts
> I recently set up NFS exports on a server on my local intranet. I can mount > NFS directories after running nfs(4) but when I tried to do a small dircp(1) > it invariably failed at the same point for each of the directories I tried: > > term% nfs -p 666 -u /lib/ndb/glenda.passwd /lib/ndb/glenda.group > somehost > term% mount -a /srv/somehost /n/somedir /somepath > term% dircp somelocaldir /somepath/someremotedir Sorry, meant: term% dircp somelocaldir /n/somedir/someremotedir > > [after a while...] > > tar: error writing same/path/same/file: timeout > > NetBSD, Linux, and macOS clients don't seem to have any issues. > > Am I doing something wrong or does nfs(4) not work very well? > > Thanks, > Pouya -- 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T060ac082dfe82490-M2c8b34834df52fc5f02e2afc Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[9fans] nfs timeouts
I recently set up NFS exports on a server on my local intranet. I can mount NFS directories after running nfs(4) but when I tried to do a small dircp(1) it invariably failed at the same point for each of the directories I tried: term% nfs -p 666 -u /lib/ndb/glenda.passwd /lib/ndb/glenda.group somehost term% mount -a /srv/somehost /n/somedir /somepath term% dircp somelocaldir /somepath/someremotedir [after a while...] tar: error writing same/path/same/file: timeout NetBSD, Linux, and macOS clients don't seem to have any issues. Am I doing something wrong or does nfs(4) not work very well? Thanks, Pouya -- 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T060ac082dfe82490-M97f91963d4812f828e60d92e Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Re: [9fans] Olimex: these guys are keen electronic engineers.
[tswoskow...@gmail.com] > I had a thought a while back: could one pilfer plan 9's libc and > kernel guts to build an embedded c library à la newlib? The idea is a > native hosted plan 9 microcontroller lab similar to arduino and your > microcontroller program would look like a bare metal plan 9 program. Isn't that what 'unikernels' are about? As a side note to this thread I have a slow-running (crawling would be more like it actually) side project to build a RISC-V SoC on an Atrix-7 FPGA board, and I had imagined I might one day run Plan 9 on it, although I might actually start with xv6 (if I ever get there). -- 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tef717f57ede82d4f-Mbbfc6aebfc9e41708f8185c7 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[9fans] 9p(2) and walk1
9p(2) says the following about char* (*walk1)(Fid *fid, char *name, Qid *qid); | Because implementing the full walk message is intricate and prone to | error, the helper routine walkandclone will handle the request given | pointers to two functions walk1 and (optionally) clone. [...] Walk1 | should walk fid to name, initializing fid->qid to the new path's | qid.Both should return nil on success or an error message on error. And later: | If the client provides functions srv->walk1 and (optionally) | srv->clone, the 9P service loop will call walkandclone with these | functions to handle the request. Unlike the walk1 above, srv->walk1 | must fill in both fid->qid and *qid with the new qid on a successful | walk. I think the distinction being made is that if walk1 is populated in a struct served by srv(2) it needs to set *qid, but not if it's used instead to construct a walk function explicitly using walkandclone. A quick look at the source code of lib9p seems to confirm this. I looked at the implementation of nntpfs(4) and webfs(4), which both set walk1. The former sets both fid->qid and *qid and the latter only *qid, which seems it could be ok from a quick look at the source of lib9p, but goes against the above instructions AFAICS. Are these subtle differences (the two in the man page and the third in code) intentional? It's my first time implementing a 9P file system so apologies if I'm missing something basic. Thanks, Pouya -- 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tb39d71a5497bba2d-M226ea8444212b13fc9a35ab2 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Re: [9fans] 9pi provenance
[9f...@hamnavoe.com] > A couple of people have speculated about what exactly is in the 9pi SD card > image. Many thanks for this image. I had also been wondering about it until I asked and you kindly answered. I'm very glad to have access to an image that is close to the 4th Edition, while also including carefully chosen patches and fixes/improvements I would have had to learn about and try (and possibly fail at) to ensure necessary functionality/usability. Coming back to Plan 9 and finding my bearings again (I had only known about the 4th and earlier editions) was much facilitated by the availability of the 9pi image. Perhaps someone will create a phylogenetic tree one day to help those like me re-orient themselves. -- 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T16171523f95d8656-M2d1b882d9344173612834907 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Re: [9fans] patches from 9front
[lucio.d...@gmail.com] > I think what has kept Plan 9 ticking for the past 25 years or more, is > that this community is small enough to keep connected to the "product" > in its more abstract sense. Whatever that sense is, it is what we > share and, presumably, appreciate, so we ought to preserve it, neh? Plan 9 is one of my few anchors in this growth-crazy world, and the size and quality of the team that built it, and the community that formed around it, have a lot to do with it I think. Growth beyond the point of sustainability can be very corruptive. Working with Plan 9 for me is like travelling back to a time when things made sense and the future was full of exciting possibilities. -- 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tc82939f1fda0e479-M75f3d3976db5cc17c420e7b5 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[9fans] which Plan 9 am I running?
I am very grateful for Richard Miller's ready-made 9pi image. When I first got to know about Plan 9 many years ago, there was only a single distribution of it I believe. I had assumed I was running something close to that distribution, with an updated kernel, but I have since been pleasantly surprised by some new additions, such as Go, an rc git client, etc. included in this image. I have also read up a bit on 9legacy, 9front, etc. I wonder now which, if any, of these I am running. Pouya -- 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T417f4caea0708c0a-Md08c954fab198718cc5c7c13 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Re: [9fans] Plan 9 Foundation
> We are pleased to announce the creation of the Plan 9 Foundation. This is excellent news. I am especially excited to see some familiar names in the signature (the familiarity is one-directional, partly from when I was lurking around Plan 9 lists back in the 2000s). Would be keen to learn how to support your work. Pouya -- 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T973ff41a99053355-M231ac42ed4e6cad019dcb879 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Re: [9fans] GSoC 2021 project ideas (WAS: Re: Plan 9 Applying to GSoC 2021)
[eeke...@fastmail.fm] > I specifically say "more popular" because popularity affects the number of developers available. Off-topic and perhaps unpopular view, but I *like* the fact that Plan 9 is not (significantly) more popular. Popularity has ruined many a promising creation. Although please do not take this to mean that I don't value all the work that has been going into developing the community and continuing to evolve and move forward. Luddites like me also greatly benefit from it. Pouya -- 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T1c300cdbd9941edb-Mcb25b9921961b686f430f7dc Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Re: [9fans] pi3 b+ and 5ghz wifi
[pouya+lists.9f...@nohup.io] > Worked for 2.4GHz but not for 5GHz. I stand corrected. There was a mix-up with an older 3b, which only has 2.4GHz (too many rpis lying around). Sorry about the confusion. Pouya -- 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tbb87a85e4d7ad382-M9d8e1d1420cd705fc753e7b3 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
Re: [9fans] Acme Mail editable from address
Thank you all for your feedback. I have combined my answers to a few responses below. > [pouya+lists.9f...@nohup.io] >> I was looking for a way to send emails from different addresses with >> Acme Mail [9f...@hamnavoe.com] > That's what /mail/box/$user/pipefrom is for. (Not specific to acme.) > Thank you. This seems much more elegant than my hack as a general solution. [o...@eigenstate.org] > The ability is useful, but the code to do it would be better > placed in upas/marshal. Upas/marshal already supports that by setting the upasname env variable, or did you mean to have it as a flag or taken from the headers in the input? [sirjofri+ml-9f...@sirjofri.de] > Please double-check this. When I add a From: in acme Mail it's always > converted to a destination address. I should take a closer look but I seem to recall some special handling of From: lines in acme Mail. -- 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T9469a3ec554967c5-M369ccb4d68423425cdbc7b2c Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[9fans] Acme Mail editable from address
I was looking for a way to send emails from different addresses with Acme Mail, as I use + address suffixes to sort incoming mail and occasionally need to send emails from the same (e.g. to this mailing list). Not finding a convenient way, I committed a bad hack to include an optional From: line in the header of outgoing messages. It's available at 9p.io/sources/contrib/pdt/acme/mail in case someone might find it useful (or be kind enough to tell me this is not the right way to do it). Pouya -- 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T9469a3ec554967c5-M059a7a0d5e206cd7b9c25ef2 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
