9front - general discussion about 9front
 help / color / mirror / Atom feed
From: cinap_lenrek@gmx.de
To: 9front@googlegroups.com
Subject: Re: todo
Date: Thu, 31 Mar 2011 00:39:36 +0200	[thread overview]
Message-ID: <a57dc19bedec487ff4c8e0fb635426a9@gmx.de> (raw)
In-Reply-To: <75347f55ed57fa6480e845e8639f2886@stanleylieber.com>

> - Whatever the new boot mechanism is, it should allow setting the
> same sort of variables that go into plan9.ini, but from an early prompt.
> This would aid in getting more hardware up and running without the
> need to create custom boot images.
this was a more blue sky idea... all you do in realmode from the loader
can also be done in userspace with dossrv and a rc script... but with
one set of drivers... but have to finish the work first on that making
this point low priority.

> - bichued/hg: Mercurial 1.0.2 is not able to push to BitBucket, Google
> Code, etc.
found a work arround... working on getpass.py to properly handle
plan9 /dev/cons instead of misdetecting us as windows nt :)

> - fgb/openssh is not able to scp reliably.
hm... maybe we should take a look and fix it once and for all...

> - realemu as default graphics mode, or enabled/disabled in plan9.ini.
> xga fails on many vm installs, which at this point may be the most
> common point of entry.
i would argue that it is more reliable than /dev/realmode... the delay
when setting mode is not that important in my opinion... and its better
than crashing/freezing the whole machine without any way to
debug the problem. making it optional with a plan9.ini key sounds
fine.

> - page(1)/gs(1) cannot render some PDF files.
that sounds like a old bug in page... whats the exact error?
do you have an example pdf that doesnt work?

--
cinap


  reply	other threads:[~2011-03-30 22:39 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <405d44d0ddf24c71ff94c72804f03bec@gmx.de>
2011-03-30 20:57 ` todo Stanley Lieber
2011-03-30 22:39   ` cinap_lenrek [this message]
2011-03-30 22:46     ` todo Stanley Lieber
2011-03-30 22:04 ` todo uriel
2011-04-01  0:30 ` todo Ethan Grammatikidis
2011-04-01  0:47   ` todo Jacob Todd
2011-04-01  0:59   ` todo Uriel
2011-04-01  1:12     ` todo Ethan Grammatikidis
2011-04-01  4:40     ` todo aiju
2011-04-01  7:04       ` todo Uriel
2011-04-01  7:13         ` todo cinap_lenrek
2011-04-01  9:30           ` todo Uriel
2011-04-01 10:18             ` todo cinap_lenrek
2011-04-01 10:24               ` todo Uriel
2011-04-01 11:38                 ` todo cinap_lenrek
2011-04-01 13:36                   ` todo Ethan Grammatikidis
2011-04-01 13:54                     ` todo Julius Schmidt
2011-04-01 17:41                       ` todo Uriel
2011-04-01 19:02                         ` todo Ethan Grammatikidis
2011-04-02 14:22                         ` todo aiju
2011-04-02 14:52                           ` todo Ethan Grammatikidis
2011-04-01 17:38                     ` todo Uriel
2011-04-01  7:09     ` todo cinap_lenrek
2011-04-01  6:14   ` todo Taru Karttunen
2011-05-02  7:30 TODO Uriel
2011-05-02 13:25 ` TODO Julius Schmidt
2011-05-02 17:03   ` TODO Uriel
2011-05-02 18:24     ` TODO Iruatã Souza
2011-05-02 19:33       ` TODO ron minnich
2011-05-02 13:45 ` TODO Jacob Todd
2018-02-24 19:53 TODO Kurt H Maier

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=a57dc19bedec487ff4c8e0fb635426a9@gmx.de \
    --to=cinap_lenrek@gmx.de \
    --cc=9front@googlegroups.com \
    /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).