From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9front@googlegroups.com
Subject: Re: Linuxemu and Slackware 11.0, preliminary report
Date: Sun, 8 Apr 2012 00:30:17 +0100 [thread overview]
Message-ID: <20120408003017.24035688@inari.ethans.dre.am> (raw)
In-Reply-To: <3F15F5F5-7ECB-431A-BD97-7EC7919942A3@quintile.net>
On Wed, 4 Apr 2012 10:17:31 +0100
steve <steve@quintile.net> wrote:
> i did quite a bit of work on linuxemu last year but never got it to a stage where i was happy to generally release it. for me, working with debian, the improved linuxemu will now work
> happily with the current debian distribution; i have not tried slackware.
Awesome. If it works with Debian I don't see why it wouldn't work with
Slackware.
>
> the most controversial change was in the handling of special files, which i flag using
> a combination of plan9's append and exclusive bits, rather than cinap's choice of using
> an escaped "special" filename.
>
> the change makes open, stat, and wstat cheaper as the file you a moifying is easily found,
> however it does mean you have to use mkfs/extfs of linux'tar to move files about, plan9's tar
> will not do as it does not understand these extra mode flags.
Fine by me, Plan 9's tar was no good for bootstrapping anyway.
>
> there are many other changes including a symlink cache, and wider linux systemcall coverage.
>
> i use this daily at work for svn and ghostscript, and opera but i haven't tried much else,
> what i have tried does work.
Opera is the main thing for me too, but I'm also lazy and don't want to
port puzzle games if I can have them in linuxemu.
>
> you are welcome to try mycode which is in /n/sources/contrib/linuxemu.tgz, though
> i cannot help much at the moment as i am on holiday.
uh, bad path, no? what's your user dir?
next prev parent reply other threads:[~2012-04-07 23:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 13:53 Ethan Grammatikidis
2012-04-02 14:02 ` sl
2012-04-02 14:16 ` Ethan Grammatikidis
2012-04-02 20:36 ` cinap_lenrek
2012-04-02 20:51 ` cinap_lenrek
2012-04-02 21:58 ` Ethan Grammatikidis
2012-04-02 22:09 ` sl
2012-04-02 23:00 ` Ethan Grammatikidis
2012-04-02 23:02 ` cinap_lenrek
2012-04-02 23:13 ` hiro
2012-04-02 23:21 ` cinap_lenrek
2012-04-02 23:23 ` Ethan Grammatikidis
2012-04-02 23:34 ` sl
2012-04-02 23:32 ` Anthony Martin
2012-04-03 6:36 ` cinap_lenrek
2012-04-02 22:58 ` cinap_lenrek
2012-04-02 23:18 ` Ethan Grammatikidis
2012-04-02 23:47 ` Kurt H Maier
2012-04-03 1:24 ` Ethan Grammatikidis
2012-04-03 6:03 ` cinap_lenrek
2012-04-03 8:17 ` Ethan Grammatikidis
2012-04-04 9:17 ` steve
2012-04-07 23:30 ` Ethan Grammatikidis [this message]
2012-04-08 0:22 ` sl
2012-04-08 2:27 sl
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=20120408003017.24035688@inari.ethans.dre.am \
--to=eekee57@fastmail.fm \
--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).