9front - general discussion about 9front
 help / color / mirror / Atom feed
* [9front] 9front-8963.f84cf1e60427675514fb056cc1723e45da01e043.amd64.iso vs thinkpad x61t
@ 2022-10-26 18:38 Stanley Lieber
  2022-10-26 20:04 ` Jacob Moody
  0 siblings, 1 reply; 11+ messages in thread
From: Stanley Lieber @ 2022-10-26 18:38 UTC (permalink / raw)
  To: 9front

[-- Attachment #1: Type: text/plain, Size: 2 bytes --]




[-- Attachment #2: IMG_7418.jpg --]
[-- Type: image/jpeg, Size: 1551597 bytes --]

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [9front] 9front-8963.f84cf1e60427675514fb056cc1723e45da01e043.amd64.iso vs thinkpad x61t
  2022-10-26 18:38 [9front] 9front-8963.f84cf1e60427675514fb056cc1723e45da01e043.amd64.iso vs thinkpad x61t Stanley Lieber
@ 2022-10-26 20:04 ` Jacob Moody
  2022-10-26 20:24   ` sl
  0 siblings, 1 reply; 11+ messages in thread
From: Jacob Moody @ 2022-10-26 20:04 UTC (permalink / raw)
  To: 9front

My guess is your paqfs is missing /rc/lib/rcmain.
At least that's the only time I see rc just exit like this.

Speaking of which it would probably be nice to print an error
when that is the case. So its not a guess.

This may be my fault, I added /rc to devroot which required
some changes to how the namespace is built. Things should work,
but if your userspace has fallen out of sync with your kernel
it may cause this.

- moody


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [9front] 9front-8963.f84cf1e60427675514fb056cc1723e45da01e043.amd64.iso vs thinkpad x61t
  2022-10-26 20:04 ` Jacob Moody
@ 2022-10-26 20:24   ` sl
  2022-10-27  4:05     ` william
  0 siblings, 1 reply; 11+ messages in thread
From: sl @ 2022-10-26 20:24 UTC (permalink / raw)
  To: 9front

> but if your userspace has fallen out of sync with your kernel
> it may cause this.

yes, i finally figured out this was down to the 9pc64 on my
fat-formatted usb stick was... old. the .iso dd'd to a usb
stick directly booted fine.

thanks,

sl

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [9front] 9front-8963.f84cf1e60427675514fb056cc1723e45da01e043.amd64.iso vs thinkpad x61t
  2022-10-26 20:24   ` sl
@ 2022-10-27  4:05     ` william
  2022-10-27 12:14       ` Jacob Moody
  0 siblings, 1 reply; 11+ messages in thread
From: william @ 2022-10-27  4:05 UTC (permalink / raw)
  To: 9front

I forget

cd /sys/src/
mk install

will that install everything including the kernel. Or do I have to manually 
copy the kernel. I just don't want this to happen on my remote server


Quoth sl@stanleylieber.com:
> > but if your userspace has fallen out of sync with your kernel
> > it may cause this.
> 
> yes, i finally figured out this was down to the 9pc64 on my
> fat-formatted usb stick was... old. the .iso dd'd to a usb
> stick directly booted fine.
> 
> thanks,
> 
> sl
> 


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [9front] 9front-8963.f84cf1e60427675514fb056cc1723e45da01e043.amd64.iso vs thinkpad x61t
  2022-10-27  4:05     ` william
@ 2022-10-27 12:14       ` Jacob Moody
  2022-10-27 14:39         ` Stanley Lieber
  0 siblings, 1 reply; 11+ messages in thread
From: Jacob Moody @ 2022-10-27 12:14 UTC (permalink / raw)
  To: 9front

On 10/26/22 22:05, william@thinktankworkspaces.com wrote:
> I forget

When in doubt refer to the fqa: http://fqa.9front.org/fqa5.html#5.2.2

> 
> cd /sys/src/
> mk install
> 
> will that install everything including the kernel. Or do I have to manually 
> copy the kernel. I just don't want this to happen on my remote server
> 

No this only builds your userspace, you need to specifically build
and copy your kernel to the right place for your system. However
considering how often I see people cut themselves with that edge
perhaps there should be something that does all that, a sysbuild
script perhaps, not sure.


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [9front] 9front-8963.f84cf1e60427675514fb056cc1723e45da01e043.amd64.iso vs thinkpad x61t
  2022-10-27 12:14       ` Jacob Moody
@ 2022-10-27 14:39         ` Stanley Lieber
  2022-10-27 16:59           ` umbraticus
  0 siblings, 1 reply; 11+ messages in thread
From: Stanley Lieber @ 2022-10-27 14:39 UTC (permalink / raw)
  To: 9front

[-- Attachment #1: Type: text/plain, Size: 937 bytes --]

this was rejected years ago for [reason unknown], so i wrote my own highly specific script, which is inadequate for general use:

http://plan9.stanleylieber.com/rc/nk

sl


> On Oct 27, 2022, at 8:17 AM, Jacob Moody <moody@mail.posixcafe.org> wrote:
> 
> On 10/26/22 22:05, william@thinktankworkspaces.com wrote:
>> I forget
> 
> When in doubt refer to the fqa: http://fqa.9front.org/fqa5.html#5.2.2
> 
>> 
>> cd /sys/src/
>> mk install
>> 
>> will that install everything including the kernel. Or do I have to manually 
>> copy the kernel. I just don't want this to happen on my remote server
>> 
> 
> No this only builds your userspace, you need to specifically build
> and copy your kernel to the right place for your system. However
> considering how often I see people cut themselves with that edge
> perhaps there should be something that does all that, a sysbuild
> script perhaps, not sure.
> 
> 

[-- Attachment #2: Type: text/html, Size: 1924 bytes --]

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [9front] 9front-8963.f84cf1e60427675514fb056cc1723e45da01e043.amd64.iso vs thinkpad x61t
  2022-10-27 14:39         ` Stanley Lieber
@ 2022-10-27 16:59           ` umbraticus
  2022-10-27 18:13             ` Stanley Lieber
  0 siblings, 1 reply; 11+ messages in thread
From: umbraticus @ 2022-10-27 16:59 UTC (permalink / raw)
  To: 9front

> [reason unknown]
> ...
> my own highly specific script, which is inadequate for general use

Reason discovered. We don't know where everyone's kernels belong.
Mine need to be on 9fat on the cpu and /shr/<some string>/ on the
machine I am typing from. How do you script that generally?

umbraticus

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [9front] 9front-8963.f84cf1e60427675514fb056cc1723e45da01e043.amd64.iso vs thinkpad x61t
  2022-10-27 16:59           ` umbraticus
@ 2022-10-27 18:13             ` Stanley Lieber
  2022-10-28  7:34               ` Steve Simon
  0 siblings, 1 reply; 11+ messages in thread
From: Stanley Lieber @ 2022-10-27 18:13 UTC (permalink / raw)
  To: 9front

yeah, it was discussed. i thought an argument for the target location might be sufficient, but [reasons]. in the end we settled for documenting the process in the fqa.

sl


> On Oct 27, 2022, at 12:59 PM, umbraticus@prosimetrum.com wrote:
> 
> 
>> 
>> [reason unknown]
>> ...
>> my own highly specific script, which is inadequate for general use
> 
> Reason discovered. We don't know where everyone's kernels belong.
> Mine need to be on 9fat on the cpu and /shr/<some string>/ on the
> machine I am typing from. How do you script that generally?
> 
> umbraticus
> 


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [9front] 9front-8963.f84cf1e60427675514fb056cc1723e45da01e043.amd64.iso vs thinkpad x61t
  2022-10-27 18:13             ` Stanley Lieber
@ 2022-10-28  7:34               ` Steve Simon
  2022-10-29  4:32                 ` Jacob Moody
  0 siblings, 1 reply; 11+ messages in thread
From: Steve Simon @ 2022-10-28  7:34 UTC (permalink / raw)
  To: 9front


just throwing it in, my approach was to add a mkfile to 9fat that installs a new kernel if one exists, moving the old kernel to 9xxx.old in case i have built a broken one.

-Steve


> On 27 Oct 2022, at 19:14, Stanley Lieber <sl@stanleylieber.com> wrote:
> 
> yeah, it was discussed. i thought an argument for the target location might be sufficient, but [reasons]. in the end we settled for documenting the process in the fqa.
> 
> sl
> 
> 
>> On Oct 27, 2022, at 12:59 PM, umbraticus@prosimetrum.com wrote:
>> 
>> 
>>> 
>>> [reason unknown]
>>> ...
>>> my own highly specific script, which is inadequate for general use
>> 
>> Reason discovered. We don't know where everyone's kernels belong.
>> Mine need to be on 9fat on the cpu and /shr/<some string>/ on the
>> machine I am typing from. How do you script that generally?
>> 
>> umbraticus
>> 
> 

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [9front] 9front-8963.f84cf1e60427675514fb056cc1723e45da01e043.amd64.iso vs thinkpad x61t
  2022-10-28  7:34               ` Steve Simon
@ 2022-10-29  4:32                 ` Jacob Moody
  2022-10-29 20:40                   ` william
  0 siblings, 1 reply; 11+ messages in thread
From: Jacob Moody @ 2022-10-29  4:32 UTC (permalink / raw)
  To: 9front

While looking over our mkfiles again I do see that we have a 'kernels' target
in /sys/src that builds all of the kernels, but nothing for just the 'current'
kernel. So I thought to add that, and add it to the list of subdirs
we build on a 'install'. This defines the 'current' kernels/boot
programs to those that are for the current objtype.

Now this doesn't do anything for putting the kernel somewhere other then /$objtype.
Most kernel install targets have this notion of $EXTRACOPIES :

install:V:	$p$CONF
	cp $p$CONF /$objtype/
	for(i in $EXTRACOPIES)
		import $i / /n/$i && cp $p$CONF $p$CONF.gz /n/$i/$objtype/

This seems a bit oddly specific, perhaps EXTRACOPIES (or a rename) could be
where someone puts in wherever they need the binary installed to
You'd get something like:

cd /sys/src
KDIRS=/n/9fat mk install

Just some thoughts, maybe this still sucks.

diff c67a1784cc34ffec633b61ad3267e13d162be219 uncommitted
--- a//sys/src/9/mkfile
+++ b//sys/src/9/mkfile
@@ -19,7 +19,13 @@
 		mk
 	}

-installall install:V:
+install:V:
+	for(i in `{grep -l '^objtype='^$objtype */mkfile})@{
+		cd `{basename -d $i}
+		mk install
+	}
+
+installall:V:
 	for(i in $ARCH) @{
 		cd $i
 		mk install
--- a//sys/src/boot/mkfile
+++ b//sys/src/boot/mkfile
@@ -10,7 +10,15 @@
 		mk
 	}

-installall install:V:
+install:V:
+	if(~ $objtype 'amd64')
+		objtype=386
+	for(i in `{grep -l '^objtype='^$objtype */mkfile})@{
+		cd `{basename -d $i}
+		mk install
+	}
+
+installall:V:
 	for(i in $ARCH) @{
 		cd $i
 		mk install
--- a//sys/src/mkfile
+++ b//sys/src/mkfile
@@ -47,12 +47,15 @@
 SUBSYS=ape\
 	/acme\

+KERNS=9\
+	boot\
+
 none:VQ:
 	echo mk all, install, clean, nuke, release, kernels, or libs

 all install clean nuke:VQ:
 	date
-	for (i in $LIBS $SUBSYS $CMDS) @{
+	for (i in $LIBS $SUBSYS $CMDS $KERNS) @{
 		cd $i
 		mk $target
 	}
@@ -69,10 +72,10 @@
 	mk clean

 kernels:V:
-	for (i in 9 boot) @{
+	for (i in $KERNS) @{
 		cd $i
 		mk clean
-		mk install
+		mk installall
 		mk clean
 	}
 ---



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [9front] 9front-8963.f84cf1e60427675514fb056cc1723e45da01e043.amd64.iso vs thinkpad x61t
  2022-10-29  4:32                 ` Jacob Moody
@ 2022-10-29 20:40                   ` william
  0 siblings, 0 replies; 11+ messages in thread
From: william @ 2022-10-29 20:40 UTC (permalink / raw)
  To: 9front


I like all the ideas as long as its documented in fqa. My lazy self just simply forgets. 

I saved a copy of the shell script but twice I was on the wrong namespace while writting
to /n/9fat



Quoth Jacob Moody <moody@mail.posixcafe.org>:
> While looking over our mkfiles again I do see that we have a 'kernels' target
> in /sys/src that builds all of the kernels, but nothing for just the 'current'
> kernel. So I thought to add that, and add it to the list of subdirs
> we build on a 'install'. This defines the 'current' kernels/boot
> programs to those that are for the current objtype.
> 
> Now this doesn't do anything for putting the kernel somewhere other then /$objtype.
> Most kernel install targets have this notion of $EXTRACOPIES :
> 
> install:V:	$p$CONF
> 	cp $p$CONF /$objtype/
> 	for(i in $EXTRACOPIES)
> 		import $i / /n/$i && cp $p$CONF $p$CONF.gz /n/$i/$objtype/
> 
> This seems a bit oddly specific, perhaps EXTRACOPIES (or a rename) could be
> where someone puts in wherever they need the binary installed to
> You'd get something like:
> 
> cd /sys/src
> KDIRS=/n/9fat mk install
> 
> Just some thoughts, maybe this still sucks.
> 
> diff c67a1784cc34ffec633b61ad3267e13d162be219 uncommitted
> --- a//sys/src/9/mkfile
> +++ b//sys/src/9/mkfile
> @@ -19,7 +19,13 @@
>  		mk
>  	}
> 
> -installall install:V:
> +install:V:
> +	for(i in `{grep -l '^objtype='^$objtype */mkfile})@{
> +		cd `{basename -d $i}
> +		mk install
> +	}
> +
> +installall:V:
>  	for(i in $ARCH) @{
>  		cd $i
>  		mk install
> --- a//sys/src/boot/mkfile
> +++ b//sys/src/boot/mkfile
> @@ -10,7 +10,15 @@
>  		mk
>  	}
> 
> -installall install:V:
> +install:V:
> +	if(~ $objtype 'amd64')
> +		objtype=386
> +	for(i in `{grep -l '^objtype='^$objtype */mkfile})@{
> +		cd `{basename -d $i}
> +		mk install
> +	}
> +
> +installall:V:
>  	for(i in $ARCH) @{
>  		cd $i
>  		mk install
> --- a//sys/src/mkfile
> +++ b//sys/src/mkfile
> @@ -47,12 +47,15 @@
>  SUBSYS=ape\
>  	/acme\
> 
> +KERNS=9\
> +	boot\
> +
>  none:VQ:
>  	echo mk all, install, clean, nuke, release, kernels, or libs
> 
>  all install clean nuke:VQ:
>  	date
> -	for (i in $LIBS $SUBSYS $CMDS) @{
> +	for (i in $LIBS $SUBSYS $CMDS $KERNS) @{
>  		cd $i
>  		mk $target
>  	}
> @@ -69,10 +72,10 @@
>  	mk clean
> 
>  kernels:V:
> -	for (i in 9 boot) @{
> +	for (i in $KERNS) @{
>  		cd $i
>  		mk clean
> -		mk install
> +		mk installall
>  		mk clean
>  	}
>  ---
> 
> 
> 


^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~2022-10-29 20:41 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-10-26 18:38 [9front] 9front-8963.f84cf1e60427675514fb056cc1723e45da01e043.amd64.iso vs thinkpad x61t Stanley Lieber
2022-10-26 20:04 ` Jacob Moody
2022-10-26 20:24   ` sl
2022-10-27  4:05     ` william
2022-10-27 12:14       ` Jacob Moody
2022-10-27 14:39         ` Stanley Lieber
2022-10-27 16:59           ` umbraticus
2022-10-27 18:13             ` Stanley Lieber
2022-10-28  7:34               ` Steve Simon
2022-10-29  4:32                 ` Jacob Moody
2022-10-29 20:40                   ` william

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).