From: email@example.com To: firstname.lastname@example.org Subject: Re: [9front] Re: Rio on cpu|Share files to unix on terminal Date: Thu, 03 Jun 2021 12:02:28 -0700 Message-ID: <8BD65D8EFD7859408E52D54A24B04FCD@fulton.software> (raw) In-Reply-To: <YLhPy97UKb1AZIJZ@SDF.ORG> Quoth adr@SDF.ORG: > On Wed, Jun 02, 2021 at 01:56:06AM +0000, adr@SDF.ORG wrote: > > Hi, > > I have a terminal configured (rpi4) and I want to shared a file > > system with another unix machine. I changed the service to cpu and > > configured it to start rio, mounting the draw device and mouse first. > > > > All good but after creating some windows, rio will go crazy, windows > > will be resized randomly and the display will not represent the > > contents of the windows anymore. > > > > The console message when the party starts is > > > > rio: setname failed: unknown id for draw image > > > > If one is able to kill rio you can start it again and all will be > > normal until the mess starts again. > > > > It puzzled me because I'm pretty sure I had this very same issue > > the last time I used 9front a lot of years ago on a pc. > > > > I would appreciate if someone points me to a reason of this behavior. > > > > Regards, > > adr. > > After following the boot process it's clear that the constrains are in the kernel, > I suppose is here /sys/src/9/bcm/main.c#245 > if(!cpuserver) > /* > * give terminals lots of image memory, too; the dynamic > * allocation will balance the load properly, hopefully. > * be careful with 32-bit overflow. > */ > imagmem->maxsize = kpages; > > Instead of changing the service variable on bootargs and configuring the cpuserver to run rio, > I'll configure the terminal to run the cpu services. > > Just in case someone is thinking about this. > Have you tried sshfs(1) - thats what I use for transfering files to and from UNIX.
next prev parent reply other threads:[~2021-06-04 4:16 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-02 1:56 [9front] " adr 2021-06-03 3:43 ` [9front] " adr 2021-06-03 19:02 ` fulton [this message] 2021-06-04 15:51 ` adr 2021-06-04 16:29 ` Sigrid Solveig Haflínudóttir 2021-06-04 18:42 ` adr 2021-06-04 19:02 ` Stanley Lieber
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=8BD65D8EFD7859408E52D54A24B04FCD@fulton.software \ --email@example.com \ --firstname.lastname@example.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
9front - general discussion about 9front This inbox may be cloned and mirrored by anyone: git clone --mirror http://inbox.vuxu.org/9front # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V1 9front 9front/ http://inbox.vuxu.org/9front \ email@example.com public-inbox-index 9front Example config snippet for mirrors. Newsgroup available over NNTP: nntp://inbox.vuxu.org/vuxu.archive.9front AGPL code for this site: git clone https://public-inbox.org/public-inbox.git