The problem is that samterm, which interprets keystrokes, doesn't have
access to the files. It would be a protocol change that bounces a
message off the server. Doable but not compatible.
-rob
> > gcc's different % rounding
>
> hmm?
i'm sorry. totally wrong. i thought i remembered and i
didn't. it was a different problem entirely.
i found i had to make loads of changes like the following
/sys/src/9/ip/devip.c:47,53 -
/mnt/term/home/quanstro/hg2/vx32.old/src/9vx/a/ip/devip.c:47,53
> i find development to go very fast on plan 9.
depends how many machines you have.
> gcc's different % rounding
hmm?
russ
> Ok, thats fine. But
> ;9 echo abcdefdffghi | 9 sed 's/(abc(d?f)*)(ghi)/\1/'
>
> this I don't understand...
> maybe it's too late for me...
you're re doesn't match at all. therefore no
substitutation is made. perhaps it would be
easier to see with this formulation:
9 echo abcdefdffghi | 9 sed
On 13 March 2010 00:54, erik quanstrom wrote:
>> what is going to be in $1, $2... Is ghi the contents of $2 or not?
>
> this is easy to test:
>
> ; echo abcdefghi | sed 's/(abc(def)*)(ghi)/\1/'
> abcdef
> ; echo abcdefghi | sed 's/(abc(def)*)(ghi)/\2/'
> def
> ; echo abcdefghi | sed 's/(abc(def)*)
> what is going to be in $1, $2... Is ghi the contents of $2 or not?
this is easy to test:
; echo abcdefghi | sed 's/(abc(def)*)(ghi)/\1/'
abcdef
; echo abcdefghi | sed 's/(abc(def)*)(ghi)/\2/'
def
; echo abcdefghi | sed 's/(abc(def)*)(ghi)/\3/'
ghi
- erik
> believe it or not, I even do that on 9vx. For many things, esp. things
> in port, it's good enough for me. In fact I did a "curried pipe" in
> 9vx just to try some things out.
i find development to go very fast on plan 9.
now that /dev/reboot $kern is working for me, i
can restart the kernel in
9vx crashes on me quite often, and qemu doesn't. That's the only
reason I use qemu, otherwise I'd also be stuck with 9vx too :-)
Are you running the latest from sources, or are you using
the prebuilt binary? There are important stability fixes
in the sources that aren't in the binary (unless it
Hello,
I wanted to add a plumbing rule. I added this:
type is text
data matches '[^{}]+'
data matches '(figs/([a-zA-Z0-9[\].-_]*/)*)([a-zA-Z0-9.-_]+)'
arg isdir $1
plumb start grep $2 $1/_source | sed -e 's/\.eps/.g/' | \
plumb -i -d edit
However, it doesn't work. Is there any simple way
On Fri, Mar 12, 2010 at 3:04 PM, Gorka Guardiola wrote:
> On Fri, Mar 12, 2010 at 5:53 PM, ron minnich wrote:
>> Unless there's some compelling reason to use qemu (I can't think of
>> one)
>
> Debugging the kernel.
believe it or not, I even do that on 9vx. For many things, esp. things
in port, i
On Fri, Mar 12, 2010 at 5:53 PM, ron minnich wrote:
> Unless there's some compelling reason to use qemu (I can't think of
> one)
Debugging the kernel.
--
- curiosity sKilled the cat
> The current implementation just prints the first 18 digits.
18 digits are sufficient to reconstruct exactly the same bit
representation when you run the text back through strtod.
All those extra digits may be precise but they're not necessary
and probably not accurate.
Russ
Yeah the touchbook,it can run some ported iPhone applications it seems too
interestingly.
Dave
On Fri, Mar 12, 2010 at 10:18 AM, Ethan Grammatikidis
wrote:
>
> On 12 Mar 2010, at 05:17, ron minnich wrote:
>
> http://www.alwaysinnovating.com/home/
>>
>> $400 but it has a long backlog it seems.
>
I'm working on (re)writing some utilies for geospatial work on Plan9,
there are lots of floating point numbers (a file outlining the USGS
quadrangles for the state of Maine has about 60k). With the current
implementation this takes a long time. Maybe I should switch to a binary
format (but that's p
On Fri, Mar 12, 2010 at 9:02 AM, hugo rivera wrote:
> 9vx crashes on me quite often, and qemu doesn't. That's the only
> reason I use qemu, otherwise I'd also be stuck with 9vx too :-)
GSOC proposal: build tool to make 9vx failures easier and improve the
reliability of 9vx
ron
On 12 Mar 2010, at 05:17, ron minnich wrote:
http://www.alwaysinnovating.com/home/
$400 but it has a long backlog it seems.
ron
Very nice looking little thing and the internal USB is a great idea. I
almost got to saying "I want one," but I started comparing it to my
Zaurus which was ab
Hello,
I'd appreciate if sam completed filenames with ctrl-d/Ins as rio or acme does.
Can it?
Thanks
Ruda
9vx crashes on me quite often, and qemu doesn't. That's the only
reason I use qemu, otherwise I'd also be stuck with 9vx too :-)
2010/3/12 ron minnich :
> Unless there's some compelling reason to use qemu (I can't think of
> one) why not just use 9vx exclusively? I've made a transition over the
>
Unless there's some compelling reason to use qemu (I can't think of
one) why not just use 9vx exclusively? I've made a transition over the
years:
qemu
xen
kvm
lguest
9vx
And am stuck at 9vx ...
ron
> How do other operating systems detect the available RAM? Could Plan 9
> use the same method?
plan 9 uses the same methods for detecting ram
everyone else does. perhaps we trust bios too much,
but 8mb isn't impossible, either.
try
a *noe820scan=1
at the 9load menu prompt.
- erik
2010/3/12 hugo rivera :
> But the next step I want to take is to run just a terminal with qemu,
Since it looks like you have the option, I would not suggest to use a
qemu image as your terminal. Instead, make 9vx or drawterm your
terminal and you will have access to your host file system for free
>
> I have 1600x1200x16 at work on an nvidia card.
>
i have not been able to get 32-bit modes working
with vesa, but 16 bit modes do alright. i think there
may be some sort of (frame) buffer calculation that's
off. large images can crash one's terminal, too, even
in 16-bit mode.
previously i
> I didn't use your new driver, because I'd like to check the present state
> of being distributed Plan 9 system. Why so little number of people tries it?
I am using Eriks SATA driver
> I notice another problem, too.
> The vga cannot be used as more than 8 depth, which I tested only
> nvidia an
On 12/03/2010 10:53, hugo rivera wrote:
Hello,
I have a Slackware installation running on my box. On top of it, I
often use qemu to run plan9, but it's inconvenient to constantly keep
track of the things I do there, like C programs, because many of them
are also useful under Slackware (then I com
Hi eric
> i'm frustrated with ahci problems. i think
> many of them have been fixed, but there
> are good reasons for the lag. and many
> are my fault.
Don't be so frastrated.
If you didn't work on ahci driver, we cannot use SATA drive as fast one.
I'm very thank you.
I didn't use your new dri
Hello,
I have a Slackware installation running on my box. On top of it, I
often use qemu to run plan9, but it's inconvenient to constantly keep
track of the things I do there, like C programs, because many of them
are also useful under Slackware (then I compile them under linux with
p9p's 9c). So t
26 matches
Mail list logo
