From: Steve Simon <steve@quintile.net>
To: 9front@9front.org
Subject: Re: [9front] 9front-8963.f84cf1e60427675514fb056cc1723e45da01e043.amd64.iso vs thinkpad x61t
Date: Fri, 28 Oct 2022 08:34:45 +0100 [thread overview]
Message-ID: <936DD50B-EBAB-405C-97C1-23E96E1B8081@quintile.net> (raw)
In-Reply-To: <68C45E59-7FF7-43E2-9554-9C945A5C7CF8@stanleylieber.com>
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
>>
>
next prev parent reply other threads:[~2022-10-28 7:36 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
2022-10-27 16:59 ` umbraticus
2022-10-27 18:13 ` Stanley Lieber
2022-10-28 7:34 ` Steve Simon [this message]
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=936DD50B-EBAB-405C-97C1-23E96E1B8081@quintile.net \
--to=steve@quintile.net \
--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).