Re: [9fans] best place to be sent a patch

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 is your goal. > > On Sun, May 12, 2024 at 4:31 PM Kyohei Kadota via 9fans <9fans@9f

[9fans] best place to be sent a patch

I have a question: where is the *best* place to be sent a patch for 9legacy? replica? GitHub? or here? I'm motivated, but I don't like to get no feedback as before. -- 9fans: 9fans Permalink:

[9fans] setup-plan9port action

Hi. I have released setup-plan9port@v1 action for GitHub Actions last week. https://github.com/lufia/setup-plan9port It does: * Install pre-built plan9port to your environment * Set PLAN9 environment variable to the location of plan9port installation * Add $PLAN9/bin to your PATH Currently it

[9fans] pcc: new option to convert implicitly between char* and uchar*

Hi. I'm trying to add a new option for pcc as -u to convert implicitly between char* and uchar*. In sources of LibreSSL Portable (actually, a lot of the sources is a copy of a part of OpenBSD), there are many many assignments that is uchar* to char*, or char* to uchar* without type casting. Two

Re: [9fans] Transfer of Plan 9 to the Plan 9 Foundation

Great news! Fantastic! 2021年3月23日(火) 22:07 : > > We are thrilled to announce that Nokia has transferred the copyright of > Plan 9 to the Plan 9 Foundation. This transfer applies to all of the > Plan 9 from Bell Labs code, from the earliest days through their final > release. > > The most

Re: [9fans] IP routing problems on GCP

> ip-ipconfig-mask.diff What intentions were these changes added? Though I'm not sure why that was added, I've noticed that DHCP of the VPC sends two Classless Static Route options. (DHCP option number: 121) 1. ip=0.0.0.0 mask=/0 remote=17.xx.0.1 2. ip=17.xx.0.1 mask=/32 remote=0.0.0.0 In

Re: [9fans] Git client

handle the Makefile > (sources from git repo) > > Thanks, > -Skip > > On Sun, Apr 21, 2019 at 4:06 AM Kyohei Kadota wrote: >> >> Hi, 9fans. >> >> I ported official Git client to 9legacy. It's very early version yet, >> but it can do basic commands such as f

[9fans] IP routing problems on GCP

Hi. I'm migrating my 9legacy machines to GCP but my auth/cpu servers can't get root from the fileserver. Is there someone that is using full system Plan 9 on GCP? Notes: - DHCP of VPC network on GCP sends ipmask=/32 options to that client. - If ipmask is /32 then ip/ipconfig ignores it. -

Re: [9fans] Re: /proc/n/status's memory field

Thanks. I've misread Labs kernel's initial index to zero until now. 2020年8月15日(土) 13:51 Anthony Martin : > > Kyohei Kadota once said: > > I'm reading proc(3). It describes the status file: > > > > > the amount of memory used by the process, except its stack, in

[9fans] /proc/n/status's memory field

Hi. I'm reading proc(3). It describes the status file: > the amount of memory used by the process, except its stack, in units of 1024 > bytes In /sys/src/9/pc/port/proc.c, it seems to me that procread sums all segment's size for that. Is the above statement correct?

Re: [9fans] IWP92020 Announcement

Is the link "registration page" [http://iwp9.org/register.html] broken? 2020年1月14日(火) 11:17 : > > IWP92020 is happening. Submit papers and sign up here: > > http://iwp9.org > > Hope to see you there! > -- 9fans: 9fans Permalink:

Re: [9fans] lets encrypt

I use go-acme/lego too. Lego uses ec384 by default, so I specify -k rsa2048 option. 2019年10月17日(木) 23:41 Jeff Sickel : > > I’ve been testing lego (https://go-acme.github.io/lego/) to test wildcard > certificates. It works well, though there are some manual bits required > every 60 days to keep

Re: [9fans] Git client

I have thought it. However, first of all, I set goal to just run Git on Plan 9 even though it is clumsy. I did need Git as soon as possible because almost third party packages for Go, or interesting projects for me are hosted on GitHub. I will think about refactoring later. 2019年4月22日(月) 21:45

Re: [9fans] Git client

ectory of the git repo, > or do they all depend on some of the ancillary git commands that aren't > built? If so, I'm curious how many of the tests are passing. > > On Sun, Apr 21, 2019, 07:07 Kyohei Kadota, wrote: >> >> Hi, 9fans. >> >> I ported official Git cli

[9fans] Git client

Hi, 9fans. I ported official Git client to 9legacy. It's very early version yet, but it can do basic commands such as fetch, pull, log, add, and commit -m. Probably there are many bugs. Some of them might be results from a issue of 8c that don't initialize rest fields of struct and union with

Re: [9fans] Don't Plan 9 C compiler initialize the rest of member of a struct?

cts that are not initialized explicitly shall be initialized >> > implicitly the same as >> > objects that have static storage duration. >> >> What is "be initialized implicitly the same as objects that have >> static storage duration" mean? >

Re: [9fans] Don't Plan 9 C compiler initialize the rest of member of a struct?

ly the same as objects that have static storage duration" mean? 2019年4月2日(火) 9:27 Jeremy O'Brien : > > On Mon, Apr 1, 2019, at 11:33, Kyohei Kadota wrote: > > Hi, 9fans. I use 9legacy. > > > > About below program, I expected that flags field will initializ

Re: [9fans] Don't Plan 9 C compiler initialize the rest of member of a struct?

I ran this code on 386 machine on QEMU based public VPC service. 2019年4月2日(火) 9:27 Skip Tavakkolian : > > It should initialize to zero. 8c and 5c both do the right thing here. > > Which distribution and cputype? > > On Mon, Apr 1, 2019, 8:34 AM Kyohei Kadota wrote: >> >

Re: [9fans] Git/fs: Possibly Usable

Cool! It's very interesting what implement Git in native Plan 9 style to me. 2019年4月2日(火) 13:48 : > > It was mentioned on this list a short while ago. Now, it's > more or less at the point where it works for me. Expect > many bugs and problems, and many more missing tools, but > "the rest is just

[9fans] Don't Plan 9 C compiler initialize the rest of member of a struct?

Hi, 9fans. I use 9legacy. About below program, I expected that flags field will initialize to zero but the value of flags was a garbage, ex, "f8f7". Is this expected? ``` #include struct option { int n; char *s; int flags; }; int main(void) { struct option opt = {1, "test"};

Re: [9fans] question about #include_next directive

Thanks cinap. I know Plan 9's devtls is more useful than Unix's libraries, but finally want to use git and github.com on Plan 9. My team works frequently with git. Git-wrapper can clone but it can't merge, push, and so on. And I started to port LibreSSL because official git links some libraries

[9fans] question about #include_next directive

Hi, fans. I'm trying to port LibreSSL on native Plan 9. Some functions are works now: 1. git clone https://github.com/lufia/portable && cd portable 2. rc ./update.rc 3. ape/patch -p0 #endif ! #line 1 "/usr/lufia/" cpp: :2 Unknown preprocessor control include_next I

[9fans] why disabled -n option of secstore in plan9port

Hello fans. I'm curious why secstore's -n option is disabled. https://github.com/9fans/plan9port/blob/master/src/cmd/auth/secstore/secstore.c#L390 Does someone know?

[9fans] [ANN] shell scripts to install 9legacy patches

Hi fans. I wrote shell scripts that install 9legacy patches to the system. GitHub: https://github.com/lufia/9legacy-tool Archive: http://lufia.org/plan9/src/9legacy-tool.tgz To install stable patches and to update ape: % 9legacy/init % 9legacy/installall <{9legacy/stable} % 9legacy/apply % cd