From: thinktankworkspaces@gmail.com
To: 9front@9front.org
Subject: Re: [9front]
Date: Wed, 12 Jan 2022 06:59:57 -0800 [thread overview]
Message-ID: <CD2B63B7FCBEF6C0ECC64BAFF6980663@gmail.com> (raw)
In-Reply-To: <CAFSF3XNCiHtVyg=p7jnjuRYWA3LvfMceRH__gqOq-y97oc9LzA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1256 bytes --]
No. Is it that easy. can I just swap out vmlinuz with 9bootfat and 9pc I feel like when an EC2 is
launched for the first time its amazon linux or ubuntu which ever you pick. By default it picks up
a t3.micro which also includes an EBS of about 2G. Kind of small but you can resize it. The mbr is
is already written and the bootlaoder is vmlinuz.
If I swap it out I'm still in an ext2 or ext3/4 file system so it wouldn't matter. So basically
I create another EBS then tell linux to format it fdisk and set fat then format it. I can set mbr. But
then its a matter of placing the files in the right directories on that new EBS. Then telling my ec2 linux
to reboot but on a different ebs volume and boom! I'm booting in 9front. I still feel this is a waste or
I'm doing it in the wrong order.
So right now I have my ec2 running qemu and its working fine. I could also try and tell AWS to spin
up another EBS volume and creatively mount it then run dd if=/mnt/9front.img of=/dev/to_new_volume etc...
with the right flags.
Then tell ec2 to boot on a new volume.
I guess the only benefit is speed because qemu works but I was hoping to retire it. At this moment I'm
starting to feel lazy do I push forward or settle. I need to think.
Thanks again!
[-- Attachment #2: Type: message/rfc822, Size: 6202 bytes --]
From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front]
Date: Wed, 12 Jan 2022 14:40:09 +0100
Message-ID: <CAFSF3XNCiHtVyg=p7jnjuRYWA3LvfMceRH__gqOq-y97oc9LzA@mail.gmail.com>
correct, and the plan 9 kernel supports being directly loaded by linux
bootloaders just like a linux kernel (where you would have vmlinuz for
example).
On 1/12/22, sirjofri <sirjofri+ml-9front@sirjofri.de> wrote:
>
> 12.01.2022 10:29:48 Eckard Brauer <eckard.brauer@gmx.de>:
>
>>> 9front has its own bootloader, at least for x86/amd64 standard
>>> machines. However, some people got 9front booting with other linux
>>> bootloaders.
>>
>> correct, but IMO that works like:
>>
>> BIOS -> "other bootloader" -> 9pc/9pc64 -> plan9 kernel
>>
>> where the 9pc/9pc64 plan9 bootloader still needs to be in a given
>> position or to be contiguous on disk - refer "bootloader magic" or the
>> like somewhere in the fqa.
>
> Afaik the 9pc/64 is the kernel. At least that's what is compiled when cd
> /sys/src/9/pc64 && mk install.
>
> But there's also the minimal initial disk or something like that,
> containing some basic programs for networking etc.
>
> sirjofri
>
next prev parent reply other threads:[~2022-01-12 15:05 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 8:44 [9front] thinktankworkspaces
2022-01-10 10:21 ` [9front] sirjofri
2022-01-10 17:25 ` [9front] thinktankworkspaces
2022-01-10 23:33 ` [9front] sirjofri
2022-01-12 1:16 ` [9front] thinktankworkspaces
2022-01-12 8:30 ` [9front] sirjofri
2022-01-12 9:29 ` [9front] Eckard Brauer
2022-01-12 13:09 ` [9front] sirjofri
2022-01-12 13:40 ` [9front] hiro
2022-01-12 14:59 ` thinktankworkspaces [this message]
2022-01-12 16:56 ` [9front] hiro
2022-01-14 11:45 ` [9front] cinap_lenrek
2022-01-12 14:40 ` [9front] thinktankworkspaces
2022-01-12 14:18 ` [9front] Stanley Lieber
2022-01-12 15:04 ` [9front] thinktankworkspaces
2022-01-10 12:10 ` [9front] mkf
-- strict thread matches above, loose matches on Subject: below --
2022-06-22 12:28 [9front] roy niang
2022-06-22 12:32 ` [9front] stefncb
2021-09-16 22:17 [9front] Drew Fargo
2021-08-24 19:25 [9front] Jonas
2021-06-09 14:33 [9front] adr
2021-03-31 16:32 [9front] cinap_lenrek
2021-04-01 18:33 ` [9front] Romano
2021-04-01 18:54 ` [9front] Romano
2021-04-01 19:03 ` [9front] cinap_lenrek
2021-04-01 23:16 ` [9front] Romano
2021-04-02 14:31 ` [9front] cinap_lenrek
2021-04-02 18:31 ` [9front] cinap_lenrek
2021-04-03 0:41 ` [9front] Romano
2021-04-02 21:24 ` [9front] Romano
2021-04-02 21:54 ` [9front] cinap_lenrek
2021-01-22 16:32 [9front] Марко М. Костић
2021-01-22 23:41 ` [9front] Tanami Muller
2021-01-23 0:29 ` [9front] Stuart Morrow
2021-01-23 13:38 ` [9front] Thaddeus Woskowiak
2021-01-23 14:12 ` [9front] hiro
2018-08-20 19:42 [9front] umbraticus
2018-08-20 12:11 [9front] Alex Musolino
2018-06-06 12:30 Stanislav Paskalev
2018-06-06 15:50 ` [9front] Kurt H Maier
2018-02-17 4:53 [9front] kokamoto
2016-12-28 23:31 sl
2016-12-28 23:33 ` [9front] cinap_lenrek
2015-10-02 11:43 Holger Sebert
2015-10-02 14:32 ` [9front] Kurt H Maier
2015-10-04 21:18 ` [9front] 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=CD2B63B7FCBEF6C0ECC64BAFF6980663@gmail.com \
--to=thinktankworkspaces@gmail.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).