9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] 9front-8963.f84cf1e60427675514fb056cc1723e45da01e043.amd64.iso vs thinkpad x61t
Date: Thu, 27 Oct 2022 10:39:11 -0400	[thread overview]
Message-ID: <D5737FDB-6DAF-474E-808A-9F5BF52A4C69@stanleylieber.com> (raw)
In-Reply-To: <3d80bfc1-d3c9-0e8e-5216-1ae9b92b32cd@posixcafe.org>

[-- 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 --]

  reply	other threads:[~2022-10-27 14:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26 18:38 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 [this message]
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

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=D5737FDB-6DAF-474E-808A-9F5BF52A4C69@stanleylieber.com \
    --to=sl@stanleylieber.com \
    --cc=9front@9front.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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).