i believe that assumes a state exists in the universe where they are "in step"
On Tue, Oct 1, 2024 at 2:14 AM Alyssa M via 9fans <9fans@9fans.net> wrote:
>
> 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
> Also, classical tutorials don't work for plan 9. They barely work for linux
> (everyone has a different HDD, for example) and Plan 9 as a network system is
> more complex, usually (do you have two cpus, one, or fifty? How many
> terminals, how many networks, ...).
I was never convinced whethe
> I didn't get it wrong, I was asked to send money if I wanted help, which I
> found unusual.
yeah, nobody owes you anything. capitalist joke. don't get hung up on it.
> I am using the Plan 9 wiki (https://9p.io/wiki/plan9/plan_9_wiki/) for
> information. I've read the manual and docs there, bu
save yourself, run.
On Thu, Aug 1, 2024 at 3:59 AM Noam Preil wrote:
>
> This is... strictly better, I suppose. New list of mistakes:
>
> - The usage of venti/conf is incorrect. Frankly, I don't know why you'd
> even be showing instructions for configuring a venti when the question
> was about mi
wrong
On Thu, Aug 1, 2024 at 6:53 AM wrote:
>
> Kurt, whining implies a sound. If you hear sounds, you're hallucinating like
> an LLM. ;-)
>
> Thank you. It’s good practice to post the copyright.
>
> Copyright 2024 by Kalona Ayeliski. All rights reserved.
>
> 9fans / 9fans / see discussions + pa
nobody here has this goal and this is not a peer review process, go
away you waste of time.
On Wed, Jul 31, 2024 at 3:02 AM wrote:
>
> Peer review involves presenting a claim, research, or work to others who are
> experts in the same field. These peers critically evaluate the work, test its
> a
can you please put disclaimers when you distribute AI generated content?
even better: if possible distribute your used prompt, too.
On Tue, Jul 30, 2024 at 8:19 AM wrote:
>
> ᎦᎦᏐᎩ ᏚᎵᏍᏗ,
> ᏓᏟᎶᏍᏛ ᎢᎦᏍᏗᎢ,
> ᏴᏫ ᎤᏍᏗᏁᎸ.
>
> Setting Up and Managing Venti with Automatic Mirroring in Plan 9
>
> Plan 9 from
as much as we all hate xml, i see no reason not to ship it as long as
it works well and there's something generally useful that depends on
it.
the same happened with other questionable legacy technology before,
e.g. TCP and http, so there's some precedence.
never forget that the majority of plan9 c
> Finally,. SSDs just die over time.
i can confirm.
> Keep backups.
i just hope i will be able to restore them, too. i'm too lazy to check
every year if stuff is still readable, and i fear it will wear out the
heads anyways ;)
most recent interesting read:
https://www.lto.org/wp-content/uploads
> you’re right, i apologize. big difference between being a total knob vs
> exhibiting knob behavior in certain instances. and there’s no excuse for
> aspersion.
i would not add html to your email.
thank you.
--
9fans: 9fans
Permalink:
https://9fans.topi
> This mailing list pre-dates the evident new philosophy of cancel-culture.
> Back when this was still an only mildly hostile place the policy was "don't
> feed the troll". We did indeed believe that ignoring (at worst adding their
> address to an "ignore" list) was sufficient to deal with it. B
> Why can’t we remove these losers from the mailing list? Look at this mess. If
> you want to ask ChatGPT about 9front, by all means, it’s your computer. But
> dumping walls of verbal diarrhea into the ML and onto LinkedIn and making
> everyone fight over it is such a waste of time. I understand
he already admitted he's using grammarly.
On Fri, May 17, 2024 at 7:00 PM Noam Preil wrote:
>
> There's a clear pattern, though. The document is blatantly AI-generated,
> and I believe that the author acknowledged it as such ("the model was
> confirmed as trained on 9front sources"); even if it
ng.
>
> Mike
>
> On Fri, May 17, 2024, 10:21 AM hiro <23h...@gmail.com> wrote:
>>
>> or rename that linkedin garbage to "using AI to disincentivize open
>> discussion communities"
>>
>> On Fri, May 17, 2024 at 4:16 PM Jacob Moody wrote:
>&
ntext of what an open source community can provide)
>
> Another won't fix issue is that it seems that they're unsure if they can port
> some 9front code for 9legacy because it might not survive a closed source
> audit for resale.
>
> It doesn't seem th
or rename that linkedin garbage to "using AI to disincentivize open
discussion communities"
On Fri, May 17, 2024 at 4:16 PM Jacob Moody wrote:
>
> https://www.linkedin.com/pulse/critical-analysis-9front-community-conflict-vester-thacker-htt3f/
>
> This linked-in article is frankly disgusting, I s
still you have not disclaimed anywhere that this is machine generated.
i expect a warning, bec. otherwise this low quality garbage is going
to be interpreted by future humans and AI alike as possibly factual,
which it clearly is not.
but i give you bonuspoint for making it in quotation marks.
On F
Great that you're building AI prompts instead of operating systems.
More trollfactories for "cyber" "warfare" will mean that all our
trolls will be out of a job soon. Vic, what you post on linkedin
sounds mainly like a big "fuck you" towards 9front, not a fair answer
given the technical contributio
now an AI generated book? and you're blaming 9front of having invented
new syscalls? what? oh come on!
On Fri, May 17, 2024 at 12:07 PM samuel.reader via 9fans
<9fans@9fans.net> wrote:
>
> Someone asked about the differences between 9front and 9legacy. This first
> draft provides a brief overview
all i can say is in my experience i have not hit any since the
> ephemeral snapshot fix. Honestly fosdil has been solid for me; i hope i have
> not just jinx’ed it :-)
>
> -Steve
>
>
> > On 15 May 2024, at 11:18 pm, hiro <23h...@gmail.com> wrote:
> >
> &g
noam said there's also some well-known issues with locks that still
keeps happening in fossil. did you watch the outcome of last iwp9? he
has the best description of the state of venti and fossil to date.
On Thu, May 16, 2024 at 12:08 AM Steve Simon wrote:
>
>
> Just a little first hand experie
about venti: probably nobody got around to removing it.
send a patch.
more seriously: i have no clue what might be wrong with venti, cause i
haven't used it for decades.
the papers for venti and fossil are nice btw, i have nothing against
the concept, rather i'm all for it, in theory.
On Wed, May
> The presumption you're making is based on the fact that it is easy /for you/.
That is correct.
> A valid reason is, for those that don't know what Fossil is, and what to
> understand the history of 9fans decision making, there is no way to know that
> decision was made, or why.
A valid reaso
> In the commit messages is not sufficient, either. One still must search
> through the commit messages and identify the branch/context/etc. Plus, you
> have to /know/ about what you are looking for, if something was removed. A
> separate document that outlines these removed/altered/added items,
> I don't understand the difference between code being included in the
> distribution and being "back in 9front". These are the same thing. If we ship
> code we maintain it.
there are some exceptions :)
--
9fans: 9fans
Permalink:
https://9fans.topicbox.c
> This is part of the issue I've had with 9front. If there are valid reasons
> for things to disappear or not be used, that's OK. But please document them
> and provide rationale/evidence for their removal.
and i agree that we should hold everybody to this standard. Preferably
a big change like
> I suggested that the sources could be included in the distribution, so they
> would not fork-rot as they are doing presently. It's always been the case
> that the Plan 9 distribution included "broken" sources that could not be
> compiled without external support, but were interesting enough to
> That said, I have been excited by the developments in the 9front and 9legacy,
> etc, groups, even if I don't fully agree with all the decision making. It at
> least means people are still interested in building, and that's a good
> start...
to agree with the decision making it helps to be par
it's not much of a degree if they don't require you to read Strunk & White
On Wed, May 15, 2024 at 11:18 AM wrote:
>
> On Wed, May 15, 2024, at 16:39, pl...@room3420.net wrote:
> > It doesn't. I don't know if you're a troll or just not clever enough to
> > understand that you make everybody uncom
> I have asked precisely NOTHING and have only pointed out the consequences of
> omitting sources from the 9front distribution because it leads to undesirable
> divisions.
there's only one division, not in my control, between the people that
actually run plan 9 (that includes 9front), and the pe
> has an active community all working on the same fork. The most eye
> opening thing about this whole long exchange is that the old Plan9
> people are largely working alone on private forks.
apart from the ones who moved to plan9port on mac os.
--
9fans: 9
On Mon, May 13, 2024 at 5:56 PM ibrahim via 9fans <9fans@9fans.net> wrote:
>
>
> On Monday, 13 May 2024, at 4:39 PM, Jacob Moody wrote:
>
> Fine my dude, you don't have to call us Plan 9, you don't have to want to use
> our code. However I ask that you be mindful in how you talk to new users and
> As others have pointed out I think an "official" classification is of little
> pragmatic benefit, but it would be nice
> to not have this tired conversation every email thread. Of course I have
> reason to believe that even if the p9f were
> to recognize 9front as being a "Plan 9" it still woul
> 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 broken, by suggesting that the
One error in our naming is that it might imply dp9ik completely replaced p9sk1.
quic
> If we want to share contributions between forks we need a compatibility layer
> if we don't want to we don't have to.
adding more compatibility layers doesn't generally makes sharing of
contributions easier.
the more forks diverge the harder it will be, no matter how many
layers you add. unless
citation needed
On Mon, May 13, 2024 at 1:58 PM wrote:
>
> On Mon, May 13, 2024, at 18:38, hiro wrote:
> > how did you find out about this company, i never saw it mentioned
> > anywhere before?
>
> I don't spend my time
ibrahim you're further inventing misleading terms and definitions that
contribute nothing useful to any reader.
the "means of porting" is something that you have to go and invest the
work into, that's it. it's time, sweat, work. technology cannot help
you much with this, renaming the forks also cha
> I personally prefer to call my fork based on plan9. I didn't write or invent
> plan9. Nor is my version a replacement or a continuation of plan9 it is fork
> based on plan9.
can you please share it with us? i couldn't find a plan9 distribution
named "based on plan9" in my google assistant.
>
> Note that 9front never claimed to be a continuation, but a fork. The people
> who desperately cry for a continuation of plan 9 either claim 9front as a
> continuation, or explicitly not.
yeah, I did, but that's just me. for me 9front is the perfect
continuation of plan9, both in code and in sp
ing to join the team?
On Mon, May 13, 2024 at 11:45 AM ibrahim via 9fans <9fans@9fans.net> wrote:
>
> On Monday, 13 May 2024, at 11:39 AM, hiro wrote:
>
> are you contributing the team? and paying the team?
>
> If you asked me. I don't use 9front or any of your contrib
> Have a look at authsrv(6) in the manual. The authenticator sends a
> pair of tickets to the client, one encrypted with the client's own
> key and one encrypted with the server's key. That's what allows
> both the client and server to authenticate each other.
i stand corrected. also i confused cp
> So, if you have an authentication service exposed to the ipv4
> internet (or to the ipv6 internet with a findable address), and
> your authid or a known or guessable userid has a weak enough
> password to succumb to a dictionary search, it's probably right
> to say that a random attacker could ma
> namespaces. A few of the commands have changed, like rimport and rcpu
> , instead of import and cpu.
and just in case some readers might not know, since this topic came up:
the reason why it's not called import and cpu is explicitly for
backwards(4th ed./legacy/other forks) comaptibility.
person
> I was trying to communicate that for the purposes of using hardware made this
> millennia (as any "professional" would do), 9front clearly has better code
> for doing so.
> I trust that the licensing in 9front has been handled correctly.
are you trying to imply 9front wouldn't have better code
On Mon, May 13, 2024 at 5:53 AM ibrahim via 9fans <9fans@9fans.net> wrote:
...
> The reasoning is simple : p9f owns the rights for the final release and Nokia
> has made this release available under a MIT license. Every one who uses plan9
> not only to toy around or his/her personal use but als
are you contributing the team? and paying the team?
On Mon, May 13, 2024 at 2:22 AM wrote:
>
> The complexity of communication in this medium often necessitates detailed
> discussions. You highlighted the need for additional personnel to manage the
> workload (e.g. do the work). From my persp
how did you find out about this company, i never saw it mentioned
anywhere before?
On Mon, May 13, 2024 at 10:43 AM wrote:
>
> Thank you, Sirjofri, nice idea.
>
> There are two private U.S. companies that are investing, developing, and
> using a closed source Plan 9 distribution called ᴁOS (aka
to answer my own question:
> Who is Eric Grosse?
>
author = "Russ Cox and Eric Grosse and Rob Pike and Dave
Presotto and Sean Quinlan",
title ="Security in {Plan 9}",
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com
> I thought of 3DES in the first instance because of this desire to be
> minimally disruptive. Support for DES is already there and tested.
> 3DES only needs extra keys in /mnt/keys, and because 3DES encryption
> with all three keys the same becomes single DES, there's a graceful
> fallback when u
this is mostly wild speculation. further, the numbers are not
representative at all.
since the import of the (possibly redundent) 9k amd64 work from "labs"
(which in this case might mean geoff+charles?) 2 years ago there were
zero active developers contributing to 9legacy.
please note, that stuff
best is here on the mailinglist as you can attach the patches easily,
and even if david doesn't have time to respond, others here might help
you on the path, others might appreciate taking part in your adventure
and others might learn from it, too. i guess you can cc david if
getting into 9legacy i
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.
On Sun, May 12, 2024 at 3:17 PM Richard Mill
why step back. step forward and put your money where your mouth is.
On Sun, May 12, 2024 at 2:42 PM wrote:
>
> Thank you for sharing your thoughts. I want to clarify that my intention is
> not to exert control or disrupt, but to foster better collaboration between
> communities. I understand t
d for the Plan 9 community?
>
> Vic
>
>
> On Sun, May 12, 2024, at 20:53, hiro wrote:
> >> How can we ensure that everyone feels valued and heard?
> >
> > easy. stop spamming LLM garbage and start contributing concise code
> > and documentation, not this bl
> How can we ensure that everyone feels valued and heard?
easy. stop spamming LLM garbage and start contributing concise code
and documentation, not this blabber.
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/Tcf128fa955b8aafc-M991bbf5
etuate more discord.
> In my mind, seeking to improve collaboration between communities seemed, and
> still seems, worthwhile.
>
> As a hobbyist, I find myself pondering: What motivates individuals to
> participate in 9fans if not for a genuine interest in supporting the Plan 9
> co
i do mind. please do not. but thanks for this medium-to-low-quality
trolling attempt.
On Sat, May 11, 2024 at 11:00 PM Skip Tavakkolian
wrote:
>
> Hiro, I hope you don't mind if I use your correspondence on 9fans to train a
> very annoying LLM.
>
> On Sat, May 11, 202
> Hey! It's a nice day out. A bit chilly with some wind, but sunny. I
> don't know about you, but I'm going fishing.
oh, i guess you are not Fish? i confused you. why are you speaking for
Fish though, it's his decision to put it into 9legacy, no?
--
9fans:
are you discontinuing 9legacy?
On Sat, May 11, 2024 at 10:01 PM Dan Cross wrote:
>
> On Sat, May 11, 2024 at 3:52 PM hiro <23h...@gmail.com> wrote:
> > it's YOUR fork, why aren't you doing it?
>
> For a simple reason: time.
>
> The work to integrate it
it's YOUR fork, why aren't you doing it?
On Sat, May 11, 2024 at 11:47 AM David du Colombier <0in...@gmail.com> wrote:
>
> I'd be very pleased if someone could port the
> dp9ik authentication protocol to 9legacy.
>
> --
> David du Colombier
--
9fans: 9fan
> explanation of dp9ik, which while useful, only
> addresses what (I believe) Richard was referring to in passing, simply
> noting the small key size of DES and how the shared secret is
> vulnerable to dictionary attacks.
i don't remember what richard was mentioning, but the small key size
wasn't
On Fri, May 10, 2024 at 12:59 PM Richard Miller <9f...@hamnavoe.com> wrote:
> > From: o...@eigenstate.org
> > ...
> > keep in mind that it can literally be brute forced in an
> > afternoon by a teenager[1][2]; even a gpu isn't needed to do
> > this in a reasonable amount of time.[1]
>
> [citation n
> I suspect no-one wanted to maintain it (in 9front)
I think you meant: I suspect no-one wanted to maintain it.
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/Tde2ca2adda383a3a-Mc64391ded8c1eeadfa19aa14
Delivery options: https://9fans.t
congrats for teaching the bot to create more email threads with new
subjects. just what we need as a community.
On Fri, May 10, 2024 at 4:55 PM Lucio De Re wrote:
>
> I guess we're on the same page, right up and including the fist fight(s). But
> I think we are all entitled to be treated more co
at all. what hardware does anybody have
where 9front doesn't work but plan9 4th edition does?!
On Wed, May 8, 2024 at 11:53 PM wrote:
>
> Hi Hiro et al,
>
> This mailing list is focused on Plan 9 discussions. Noticing conflicts
> between the 9legacy and 9front communities
4k@59hz works here.
but only if i disable bluetooth.
On Wed, May 8, 2024 at 9:56 PM wrote:
>
> Thanks, that’s promising. What’s your monitor?
> 9fans / 9fans / see discussions + participants + delivery options Permalink
--
9fans: 9fans
Permalink:
https://
vester, why do you recommend all these things so overly
methodologically that are all already a reality in the 9front
community? are you a bot?
On Wed, May 8, 2024 at 9:18 PM wrote:
>
> Dear Members of the 9legacy and 9front Communities,
>
> This message is intended to share thoughts on potential
> i dont see vmx causing kernel crashes for me.
> however, i think the author meant to express is lack
> of confidence in the air-tightiness of vmx giving
> the zillions of architectual registers you have to
> setup to contain a guest. it is easy to forget
> to set some bit and everything works unt
all this makes sense. thank you.
i might be dense, but what's the problem with inetd exactly?
On 3/5/24, a...@9srv.net wrote:
> I wonder what percentage of people who reply are going to be running a
> finger server they wrote. :-) My tcp79 comes from my implementation,
> here: http://txtpunk.com/
the few remaining "original Labs' Plan 9" people anyways all went to
concentrate on golang. so if you wanna hang out with them, they have a
very big and active community, too.
it keeps a lot of the core spirit behind plan9 alive, just that it
abstracts away the operating system layer. i might not l
> People use 9front, which is not plan 9. Many good things
> started as forks, and that's ok.
mostly i agreed. but to me plan9 is just an old 9front version without
the bootloader.
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T8d27241
> This was a simple comment on why I strongly disagreed with VT’s request for
it didn't get displayed as just a simple comment here. maybe you
should fix your email program.
> a 5th Release. I explained myself. I did not get emotional, nor am I
> emotional now.
How is this relevant to the techni
> I trust the sources that come from 9legacy/9pio but I don't have any
> interest in the mess of whatever 9front is supposed to be.
Nobody asked for your trust. Can you please elaborate which part of
9front you consider "messy" ?
--
9fans: 9fans
Permalink:
> [...] then it is not surprising that people
> misunderstand your intentions.
and otherwise, too. you'll just have to adapt your predictions (or
expectations?) a little if you're so frequently surprised.
--
9fans: 9fans
Permalink:
https://9fans.topicbox.c
ake what caused awe in me and
keep them alive and infect others with all that. Maybe you can submit
another patch to sources some day soon.
hiro
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T42f11e0265bcfa18-Md70d852f7
no.
remove yourself yourself.
On 11/9/23, yourlitlen1g@national.shitposting.agency
wrote:
> Hello, I never participate in the mailing list, please remove me from
> the mailing list, thank you.
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9
btw it's very common on unix to share FDs in multi-threaded programs.
and all the pain resulting from un-synchronised FD access is available
as expected :)
On 10/4/23, hiro <23h...@gmail.com> wrote:
> file descriptors describe to the kernel which of the files you
> previously ope
file descriptors describe to the kernel which of the files you
previously open()'ed (a syscall) you want to operator on.
it's not about security: if you want to operate on a file that another
process might have opened before, you have to be careful that the
other process isn't writing to the same
> I didn't realize 9legacy actually had a distribution for some reason I
> thought it was only a patch set applied against the old main line. Glad I
> don't have to pick apart the patch set that (works)...
yes. i was expecting this confusion will arise some day. officially
it's a spoon, nor a fork
ah no i was wrong. first google result "KVM support is available only
for 64-bit ARM architecture (AArch64"
oh well
On Sat, Aug 26, 2023 at 1:45 PM mkf wrote:
>
> I believe KVM on aarch64 would help aarch64 guests.
> i could be wrong.
>
> On Sat, 26 Aug 2023 1
why do you assume kvm helps with emulating a raspberry?
kvm helps virtualize amd64 on amd64, and shouldn't be usable for much else.
On Sat, Aug 26, 2023 at 11:25 AM Philip Silva via 9fans <9fans@9fans.net> wrote:
>
> Hi,
>
> I've only tried qemu with 9front and this got me to a console (the file
why don’t you follow the fqa
these port forwarding sound tedious
On 8/23/23, Sebastian Higgins wrote:
> i'm assuming you're using QEMU + drawterm. if you're using QEMU you might
> need to add command line arguments for port forwarding. here's mine after
> tons of trial and error:
>
>> qemu-system
AM Don Bailey wrote:
>
> forgot to respond to this but fwiw, running plan9 on virtualbox seems to work
> peachy. Hiro what was the bug(s) you were running into before? I've never ran
> into an issue with it, but I've only used vbox on Linux; maybe it's a
> host/CPU issue?
&
I suppose hyper-v works on windows.
On Thu, Aug 17, 2023 at 9:09 AM Peter Hull wrote:
>
> On Thu, 17 Aug 2023 at 03:18, Don Bailey wrote:
> >
> > forgot to respond to this but fwiw, running plan9 on virtualbox seems to
> > work peachy. Hiro what was the bug(s) you
oh you don't want to know, but i'm telling you anyway: smartos.
On 8/2/23, redhatuser wrote:
> So according to you, which one do you use?
--
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/Tce33a832621fe5a5-M59f2dfce9b5d4cbe73769c32
Delive
not knowing how to use a VM is unusual. hard to beleive tbh. good
shitpost. will buy again.
virtualbox otoh is a usual error. avoid that solution.
On 8/2/23, yourlitlen1g@national.shitposting.agency
wrote:
> I want to use plan9 in a virtual machine but I don't know how to install it
in case somebody else is wondering what Stuart is talking about, he's
referencing a specific text passage using one of these google chrome
specific features:
https://web.dev/text-fragments/
On 6/26/23, Stuart Morrow wrote:
>> Another interesting project would be seeing if it could be
>> modified
fixing another couple deadlocks makes you finally consider ditching fossil?
zfs storage isn't always permanent either, for example if you use
encryption or deduplication.
On 4/6/23, Lucio De Re wrote:
> On 4/6/23, n...@pixelhero.dev wrote:
>> Quoth Charles Forsyth :
>>> fussing about certain thi
it's not that bad IMO, but you will have to live with having to redo
everything and lose all the data.
i have installed to usb flash drives before for some short temporary
tests. no big deal, if you don't need to keep anything of it...
--
9fans: 9fans
Perma
> Sorry hiro, I mean that I imported the acme version of 9front to
> my system (based on 9legacy) because it has been updated along the
> plan9port repo.
h, sorry for missing the other direction :D
> One thing I can't understand is why the text window
> is always redrawn
9front has a p9p version? i was not aware... can you link to it?
On 2/20/23, adr wrote:
> Hi,
>
> this patch adds code from p9p to support spaces in file or dir
> names. I use the 9front version because it has been mantained, but
> there are more fixes in p9p to be imported.
>
> adr
> diff -Nur
(VE7TFX/VE6BBM) wrote:
> hiro writes:
>> > should each system role get his own user?
>> > Like one user for file servers, one for auth, one for venti, and one for
>> cpu
>> > servers.
>
> My was has always been to have a file system user and an auth server
> should each system role get his own user?
> Like one user for file servers, one for auth, one for venti, and one for cpu
> servers.
> Is there any point in doing that
Yes, if you share one authserver, then you'd have to use different
users in order to be allowed to use different passwords. If yo
why not get a used apu2 instead.
it comes with 3 real ethernet ports
On 11/10/22, fig wrote:
> i did think of this, but i was unsure of its compatibility with 9front. the
> FQA only
> lists two usb to ethernet adapters which did not look popular or generic
> when i looked them up. i will buy the
> course, but maybe FreeBSD needs a 9p client or you want to get ffmpeg
> building on Plan 9 again. :-)
https://sr.ht/~ft/treason/
i know it's not the same, but i thought linking it here might help
somebody in the future
--
9fans: 9fans
Permalink:
https:/
"Esta página no existe :("
On 7/31/22, a...@sdf.org wrote:
> https://es.aliexpress.com/item/1005003167747779.html
>
> First time using usb/ether, so let me share my experience for other users.
>
> This is on the last 9pi image at 9legacy.
>
> First, I added a line with did=0x8153 to /sys/src/c
On 6/1/22, Steve Simon wrote:
> for performance testing why not copy from ramfs on one machine to ramfs on
> another?
ramfs is single-process and thus quite slow.
> the suggestion from a 9con passim was to have fossil/cwfs/hjfs etc add a Qid
> type flag to files indicating they are from backing
t get infinitely slow as a
result to this.
Right now huge streams don't get huge unfair advantages unless the rtt
is very small or the parallelism very high
On 6/1/22, hiro <23h...@gmail.com> wrote:
> I don't think the reason nobody is doing this is that it's difficult per
> se.
&
31, 2022 at 11:29 AM hiro <23h...@gmail.com> wrote:
>>
>> so virtiofs is not using 9p any more?
>>
>> and with 10 million parallel requests, why shouldn't 9p be able to
>> deliver 10GB/s ?!
>
> Everyone always says this. I used to say it too.
>
And fcp?
On 6/1/22, Bakul Shah wrote:
> On May 31, 2022, at 9:14 AM, ron minnich wrote:
>>
>> On Mon, May 30, 2022 at 12:21 AM Bakul Shah wrote:
>>> 9p itself is low performance but that is a separate issue.
>>
>> Bakul, what are the units? It might be helpful to quantify this
>> statement. Are
1 - 100 of 892 matches
Mail list logo
