9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio.dere@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Someone made a Wayland compositor based on Rio, Wio
Date: Sun,  5 May 2019 15:53:37 +0200	[thread overview]
Message-ID: <CAJQ9t7hpU-8PYrsVbJ6hJqewVpw7RWnm=774DQOGftuH_8snOg@mail.gmail.com> (raw)
In-Reply-To: <616024001E26AD68C762898601C3723C@felloff.net>

Gotcha, it is amd64, so I will look at that and report back.

Next plan9.ini's "rootdir". It is no longer documented in
plan9.ini(8), but the little code that uses it in bootrc is odd as
well as at odds with the legacy documentation. My hope was to give it
"9front" as a value and have Fossil serve that as the root for a
diskless 9front workstation, as in

      bind -b $rootdir /

Instead, I find "mount -c /srv/boot $rootdir" which is definitely not
it. I'm not sure under what circumstances one target a different
location for the ROOT directory, I would be interested to hear. Of
course, this conflict needs to be resolved.

This is starting to get interesting.

Lucio.

PS: Thanks a bunch for the support, both you and Hiro.

On 5/5/19, cinap_lenrek@felloff.net <cinap_lenrek@felloff.net> wrote:
>> It's the 3Com that baffles me. I suspect the two-stage boot (I know
>> dangerously little about 9front's boot process) somehow fails to pick
>> up a supported device (3c905b - etherelink3).
>
> is this the amd64 kernel or 386 one? the amd64 one does not include
> the etherelnk3 driver. the reason is that the amd64 kernel shares its
> drivers with the pc kernel, but not all drivers might be ready for
> 64 bit pointers. so we only include what we can test and verify.
>
> you can try to add the etherelnk3 line to the pc64 config and
> rebuild.
>
> if you have this issue with the 386 kernel, then knowing the pci
> device id would be a start.
>
> the boot process is nothing special. we have a bootloader that loads
> the kernel. the loader uses BIOS/EFI calls to get the kernel from the
> boot media so that it does not need drivers. once the kernel
> is taking over, it needs a driver.
>
> --
> cinap
>
>


--
Lucio De Re
2 Piet Retief St
Kestell (Eastern Free State)
9860 South Africa

Ph.: +27 58 653 1433
Cell: +27 83 251 5824
FAX: +27 58 653 1435



  parent reply	other threads:[~2019-05-05 13:53 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-05 12:32 cinap_lenrek
2019-05-05 13:50 ` Jens Staal
2019-05-05 17:16   ` hiro
2019-05-05 13:53 ` Lucio De Re [this message]
2019-05-05 15:14 ` Lucio De Re
2019-05-07  4:15 ` Lucio De Re
2019-05-08 12:32   ` Ethan Gardener
2019-05-09  7:39     ` Lucio De Re
2019-05-09  9:37       ` hiro
  -- strict thread matches above, loose matches on Subject: below --
2019-05-07  5:40 cinap_lenrek
2019-05-07 14:15 ` Lucio De Re
2019-05-05 15:22 cinap_lenrek
2019-05-05 15:32 ` Lucio De Re
2019-05-05 15:11 cinap_lenrek
2019-05-05 14:14 cinap_lenrek
2019-05-05 15:59 ` Jens Staal
2019-05-04 22:53 umbraticus
2019-05-04 22:47 umbraticus
2019-05-05  7:53 ` hiro
2019-05-05  9:33   ` Lucio De Re
2019-05-05 10:01     ` hiro
2019-05-05 10:15       ` Lucio De Re
2019-05-05 11:09         ` hiro
2019-05-02  4:12 Ryan Gonzalez
2019-05-02  4:17 ` Rodrigo G. López
2019-05-02  4:36 ` Skip Tavakkolian
2019-05-02  4:56   ` David Arnold
2019-05-02  7:13   ` Fazlul Shahriar
2019-05-02 11:15     ` hiro
2019-05-02 11:10   ` hiro
2019-05-02 14:07     ` hiro
2019-05-03  0:47     ` Skip Tavakkolian
2019-05-03  1:27       ` Dan Cross
2019-05-03  7:59         ` hiro
2019-05-03  8:20           ` hiro
2019-05-03 11:52             ` Lucio De Re
2019-05-03 12:32               ` hiro
2019-05-03 12:35                 ` hiro
2019-05-03 17:01                 ` Lucio De Re
2019-05-04 20:53                   ` hiro
2019-05-05  3:19                     ` Lucio De Re
2019-05-05  7:51                       ` hiro
2019-05-05  8:34                         ` Lucio De Re
2019-05-03 23:08                 ` Ethan Gardener
2019-05-04  5:55                   ` Jens Staal
2019-05-04  7:04                     ` hiro
2019-05-07  3:48       ` 岡本健二
2019-05-03  2:06     ` Bakul Shah

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='CAJQ9t7hpU-8PYrsVbJ6hJqewVpw7RWnm=774DQOGftuH_8snOg@mail.gmail.com' \
    --to=lucio.dere@gmail.com \
    --cc=9fans@9fans.net \
    /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).