I wrote:
> I don't see how this can be fixed in unix without breaking umpteen million
> shell scripts.
On Sun, Oct 04, 2009 at 06:12:15AM +0200, lu...@proxima.alt.za wrote:
> By creating new commands with distinct new names.
I thought of a better way. We can fix the commands without breaking
com
> What do you think of this proposal?
I think the saying is "the game is not worth the candle". I doubt
anyone should invest the time and effort to implement this, specially
as few will adopt its use. Of course, fifty years from now everyone
would be savvy to it, but by then one expects a differ
> cat -
cat /fd/0
>> cat -
>
> cat /fd/0
cat
:-)
++L
> `--' ends options, forces consistent multi-file mode, allows empty lists
Hey, yeah, great idea. And why not use '---' to force switching to
Linux compatible mode, and '' to switch to BSD syntax, and '-'
for System V syntax (5 hyphens, System 5, easy to remember). Oh, and we
might nee
2009/10/4 Sam Watkins :
> I wrote:
>> I don't see how this can be fixed in unix without breaking umpteen million
>> shell scripts.
>
> On Sun, Oct 04, 2009 at 06:12:15AM +0200, lu...@proxima.alt.za wrote:
>> By creating new commands with distinct new names.
>
> I thought of a better way. We can fi
9fans,
I'm using a VIA SN18000G booting off a fileserver, everything seems
to be working relatively well, however it seems that the video card is not
recognized. My 'pci -bv' and 'vga -lvp' are as follows:
cpu% pci -bv
0.0.5: --- 08.00.20 1106/5364 0
VIA Technology
0.15.0: disk 01.01.
> Is there any way to force this card to use the VESA driver? Please note
> that I'm booting using "*norealmode=" in my plan9.ini.
>
VESA requires realmode.
- erik
> 13293 mkdir("/mnt/sdb1/tc/plan9/9vx-0.12/sys/lib/texmf/bibtex/bst", 0)
> = -1 EACCES (Permission denied)
>
perhaps replica is expecting specific error messages
and they're not getting translated
; cd /n/sources/plan9/`{pwd}
; g strstr
applylog.c:161: if(strstr(buf, "entry not found") |
On Sun, Oct 4, 2009 at 8:22 AM, erik quanstrom wrote:
>> 13293 mkdir("/mnt/sdb1/tc/plan9/9vx-0.12/sys/lib/texmf/bibtex/bst", 0)
>> = -1 EACCES (Permission denied)
>>
>
> perhaps replica is expecting specific error messages
> and they're not getting translated
>
> ; cd /n/sources/plan9/`{pwd}
> ; g
perhaps the elimination of all traces of IL is a little too thorough?
it seems easier to leave Logil, Logilmsg in place rather than require
an extra (periodic) merge. one can't get by simply with bind
before/after.
> perhaps the elimination of all traces of IL is a little too thorough?
I see no real harm in IL but, just a suggestion, you could do a pull -s,
and then use diff3 (in my contrib) to do a merge between ip.h.orig,
yesterday(1)'s version and the newly pulled code.
having said this I still have it o
> I don't see this explaining a
> mkdir with mode of 0 however.
Does the file/dir actually have a mode of zero on the source machine?
Plan9 can happily create an object with mode zero but a posix
emulation of wstat() must do the rename()/chmod()/chown()/chgrp()
etc in a fixed order which is bound
> Plan9 can happily create an object with mode zero but a posix
> emulation of wstat() must do the rename()/chmod()/chown()/chgrp()
> etc in a fixed order which is bound to make some combinations
> mutually exclusive.
i'd be willing to bet that posix doesn't guarentee anything
even with the conto
On Sun Oct 4 12:47:55 EDT 2009, 9...@9netics.com wrote:
> perhaps the elimination of all traces of IL is a little too thorough?
> it seems easier to leave Logil, Logilmsg in place rather than require
> an extra (periodic) merge. one can't get by simply with bind
> before/after.
+1.
i haven't do
> cat -s - -s '' -v
>
> prints the contents of file named '-v', squeezing multiple empty lines
> (BSD -s) and silencing error message (System V -s).
classic!
- erik
just a friendly schedule reminder
- wip are due tomorrow 5. oct 2009 at 21:00 gmt. this can't
be extended, but this doesn't need to be a final draft. the program this
year is pretty full, so if you'd like to talk about what you've
been working on, you'll have the best chance if you submit a
wip r
On Sun, Oct 4, 2009 at 10:20 AM, Steve Simon wrote:
>> I don't see this explaining a
>> mkdir with mode of 0 however.
>
> Does the file/dir actually have a mode of zero on the source machine?
no, it has mode 755
This is for the tex install but the problem exists in general when
using applylog on
The kernel did not compile against the most recent sources.
I've fixed this so it compiles again with current kernel source.
Haven't tried booting it on anything, though.
I successfully compiled against Xen 3.4.1 and tried to boot it on
XenServer 5.0r3, but unfortunately it failed with roug
> Now I may be way off here, but I though that perhaps the tab character
> in front of
> VIRT_BASE here may cause it to not be recognized by xenelf. I joined
> it into one line,
> and I am rewarded with a different error message:
>
> "xc_dom_alloc_segment: segment start isn't page aligned".
>
9fans,
> VESA requires realmode.
Thank you Erik, it was an oversight from my part. I was able to start rio
in 1024x768x8 and 1280x1024x8 using the VESA driver, however, the keyboard
was not working, and the pointer had no cursor.
Please note, that, while the pointer had no cursor, the mouse was
Now I may be way off here, but I though that perhaps the tab
character
in front of
VIRT_BASE here may cause it to not be recognized by xenelf. I joined
it into one line,
and I am rewarded with a different error message:
"xc_dom_alloc_segment: segment start isn't page aligned".
I really don't k
> > VESA requires realmode.
>
> Thank you Erik, it was an oversight from my part. I was able to start rio
> in 1024x768x8 and 1280x1024x8 using the VESA driver, however, the keyboard
> was not working, and the pointer had no cursor.
VESA also requires *nomp=1 in your plan9.ini. i have
seen the p
On Mon, Oct 5, 2009 at 5:15 AM, ron minnich wrote:
> On Sun, Oct 4, 2009 at 10:20 AM, Steve Simon wrote:
>>> I don't see this explaining a
>>> mkdir with mode of 0 however.
>>
>> Does the file/dir actually have a mode of zero on the source machine?
>
> no, it has mode 755
>
> This is for the tex
seems to be a bug in replica on 9vx? I'll look more tomorrow.
mkdir /sys/lib/texmf perm -200
mkdir /sys/lib/texmf/bibtex perm -200
mkdir /sys/lib/texmf/bibtex/bst perm -200
mkdir /sys/lib/texmf/bibtex/bst/base perm -200
mkdir /sys/lib/texmf/bibtex/bst/base/abbrv.bst
On Sat, Oct 3, 2009 at 1:35 AM, Skip Tavakkolian <9...@9netics.com> wrote:
> the installation completed but it is unable to get past fossil
> startup;
Do you have the CD-ROM drive attached to the VM while you boot it?
I remember Plan 9 didn't start when you have an empty CD-ROM drive
connected to
> Do you have the CD-ROM drive attached to the VM while you boot it?
>
> I remember Plan 9 didn't start when you have an empty CD-ROM drive
> connected to the VM on ESX 3.5. So I removed the CD-ROM drive from VM's
if this is the case, it seems simple enough to fix. can anyone confirm?
- erik
sqweek:
> It seems to me the obvious way to gain consistency is to do the list parsing
> in one place only:
hi sqweek,
Thanks for the thoughtful response. You are right, it could be fixed with
another tool like xargs. I wrote a similar tool "modify" which I use to modify
files in place with sta
On Sun, Oct 4, 2009 at 10:30 PM, erik quanstrom wrote:
>> Do you have the CD-ROM drive attached to the VM while you boot it?
>>
>> I remember Plan 9 didn't start when you have an empty CD-ROM drive
>> connected to the VM on ESX 3.5. So I removed the CD-ROM drive from VM's
>
> if this is the case,
> you're retaining the inconsistency, but candy-coating it.
No, I'm offering a simple syntax using which one can avoid the inconsistency.
I'm retaining the option to have inconsistent behaviour, for backward
compatibility, and because some people seem to like it for command-line use.
cat *
> On Sun, Oct 4, 2009 at 10:30 PM, erik quanstrom wrote:
>>> Do you have the CD-ROM drive attached to the VM while you boot it?
>>>
>>> I remember Plan 9 didn't start when you have an empty CD-ROM drive
>>> connected to the VM on ESX 3.5. So I removed the CD-ROM drive from VM's
>>
>> if this is t
OK, it's an incompatibility between Posix world and Plan 9 world. It's
because mkdir doesn't open the directory, and
create on Plan 9 does.
Here is what I think is the relevant code from applylog.
if(rd.mode&DMDIR){
fd = create(local, OREAD
Should have gone to bed before writing the last note.
On Sun, Oct 4, 2009 at 11:39 PM, ron minnich wrote:
> if (perm&0400 == 0) then do a mkdir with 0400, an open, and an fchmod.
> Tomorrow,
> that is. I think the work-around is pretty easy.
> I figure the 0400 might work because mode has to be
33 matches
Mail list logo
