9front - general discussion about 9front
 help / color / mirror / Atom feed
From: kokamoto@hera.eonet.ne.jp
To: 9front@9front.org
Subject: Re: [9front] termrc and aux/realemu
Date: Sat, 16 Aug 2014 14:39:39 +0900	[thread overview]
Message-ID: <10f9671a3a07e0a917aebfa4ec61cdd8@saturn.jitaku.localdomain> (raw)
In-Reply-To: <81358912ab874d44ca873af112b18b3e@felloff.net>

> the reason you do not see the file is because termrc
> *intentionally* forks the namespace and runs aux/realemu
> and aux/vga in that namespace. so we wont clutter /dev
> with slow userspace fileservers. it also doesnt start
> realemu when you'r not using vesa. this is all intentional.

Ok, I got you intentionaly did so. Then,
I don't undestand why /dev/realmode makes the system slow.

> why do you need /dev/realmode file? why do you not just
> set monitor=vesa and vgasize= variable to set graphics mode?
> do you wish to set up graphics later in your own scripts?
> in that case, you can just run aux/realemu yourself there
> before running aux/vga. what are you trying todo?

Why we need to separate this.
You don't want user mode device should not appear in /dev?
We couldn't have /dev/realmode anytime?

If it's not good, we should make aux/vga do it automatically.
I'm wrong?

Kenji



  reply	other threads:[~2014-08-16  5:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-14  1:40 kokamoto
2014-08-14  2:17 ` [9front] " Nick Owens
2014-08-15  0:10   ` kokamoto
2014-08-15  0:28     ` Nick Owens
2014-08-15  0:46     ` sl
2014-08-16  0:14       ` kokamoto
2014-08-16  0:17       ` kokamoto
2014-08-16  0:52         ` cinap_lenrek
2014-08-16  5:39           ` kokamoto [this message]
2014-08-16  0:40 sl
2014-08-16  5:29 ` kokamoto
2014-08-16  5:55 sl
2014-08-16 23:42 ` kokamoto
2014-08-17  1:54   ` cinap_lenrek
2014-08-17  4:22     ` kokamoto

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=10f9671a3a07e0a917aebfa4ec61cdd8@saturn.jitaku.localdomain \
    --to=kokamoto@hera.eonet.ne.jp \
    --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).