headers
Ethan Grammatikidis | 1 Oct 2009 02:19

Re: 9vx as a perfect proto environment

On Wed, 30 Sep 2009 14:45:18 -0400
erik quanstrom <quanstro <at> coraid.com> wrote:

> > USB eth works well for me.  I use it between my desktop & PDA, both
> > Linux machines, and have successfully (if a little slowly) dumped the
> > PDA's 6GB micro-hard-drive over the connection.  I think I measured
> > the speed at 4Gb/s once, but that could have been limited by the PDA's
> > drive.
> 
> over a 480mbit connection?  that's a trick.
> 
> - erik
> 

Yeah indeed, LOL.  All I can do on that one is apologise and curse my
memory, I'm sorry.  It's possible I calculated the transfer was
'about' or 'a bit over' 400Mbit/s.  It's not a slow link for the
occasional transfer of a big file or two, nor for VNC or Drawterm at
640x480x16bit.

--

-- 
Ethan Grammatikidis

Those who are slower at parsing information must
necessarily be faster at problem-solving.
Permalink | Reply | 0 comments |
headers
Ethan Grammatikidis | 1 Oct 2009 02:32

Re: 9vx is really excellent, link it on the bell-labs pages?

On Wed, 30 Sep 2009 17:54:52 +0100
matt <maht-9fans <at> maht0x0r.net> wrote:

> 
> > I've had "/bin/rc: not found" twice from Qemu with clean shutdowns
> 
> I've also *just* had the disk go bad during the install to a qcow2 disk, 
> at 90%+ too :(
> 
> (or at least I think it went bad, I had lots of /n/newfs not found based 
> errors)
> 
> I started over with a raw disk instead
> 

Owwwww!  You know one thing..  I've had trouble getting qemu to build
in the past and ended up using qemu 0.9.1 long after 1.0 was out, and
it's rock solid.  I've had no trouble from qemu at all.  I think I'll
stick with 0.9.1 now!  Oh btw the man pages for 0.9.1 seemed to imply
that qcow2 was really only to be used where the host OS doesn't
support holes.  (Holes are long runs of 0, and can be stored as a
simple length.) Maybe it's not tested very well any more.

As to drawterm, I've held xorg-server back too.  It's at 1.4.2, and
I'm having no trouble with drawterm.  I really hate the careless
changes in recent xorg-server versions, several old-but-good functions
don't work right any more.

--

-- 
Ethan Grammatikidis
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ethan Grammatikidis | 1 Oct 2009 02:44

Re: acme without a heavy grid (SFW)

On Wed, 30 Sep 2009 15:43:28 -0500
Jack Norton <jack <at> 0x6a.com> wrote:

> Jason Catena wrote:
> > A quick edit frees acme from its "heavy grid prison", a la Tufte.
> > https://dl.getdropbox.com/u/502901/acmenogrid.jpg
> >
> > Jason Catena
> >
> >   
> How about no grid whatsoever (while you're at it)?  There is plenty of 
> contrast there to forego any kind of hard devisions.
> 
> However, I end up with the same conclusion: why?  Is the 'grid' that 
> distracting?  

To provide an additional perspective, I don't think the grid bothers
me directly, but something about acme irritates me so much I strongly
avoid acme for anything creative and generally loathe starting it up
even though I appreciate it's great technical qualities and excelent
interface _ideas_.  I thought my problem was with the tag text, but
Jason's screenshot made me think again.  Maybe my problem is with how
the tag text interacts with the grid and I could get away with just
removing the thick black bars, or maybe I should try the Times font.
I think the former more likely.

--

-- 
Ethan Grammatikidis

Those who are slower at parsing information must
(Continue reading)

Permalink | Reply | 0 comments |
headers
lucio | 1 Oct 2009 05:53
Picon

Re: 9vx as a perfect proto environment

> USB eth works well for me.

I have two oldish systems where OHCI works erratically or not at all
with up to date distributions (give or take some skepticism towards
replica/pull).  Are there any suggestions on how to approach
debugging?  I can focus on that over the coming weekend.

++L
Permalink | Reply | 0 comments |
headers
Jason Catena | 1 Oct 2009 07:06
Picon
Gravatar

remedial sources auth, connect, and mount in plan9port

Geoff was kind enough to provide to me a contrib directory on sources,
so I'm now trying to write into it.

I can't seem to get the hang of the authorization, connection, and
mount steps necessary for an authorized mount of sources in plan9port,
so I can just copy files into my contrib directory.  Over several
dozen attempts to understand factotum, it never saves any actual data
for me, so I apparently have some serious misunderstandings.

For the mount, I can use the following to mount sources read-only, but
I can't save anything into it.
sudo 9mount 'tcp!sources.cs.bell-labs.com' /n/sources

9fs sources also doesn't seem to provide an authenticated connection,
or a mount.

Would someone be kind enough to chant the few magic plan9(port)
incantations with which I can store my sources-server username and
password with factotum, connect to sources, and mount sources
(specifically, my directory) as a writable filesystem?   I promise
diligent study, to understand what the commands do.

Jason Catena
Permalink | Reply | 10 comments |
headers
Venkatesh Srinivas | 1 Oct 2009 09:44

Re: remedial sources auth, connect, and mount in plan9port

Hi,

In order to construct an authenticated mount of sources, you will need
to start factotum, use srv -a to create an auth-ed connection to the
server and to "post" it, and to mount the "posted" connection.

(assuming you have a working plan9port install and are on a unix):
$ 9 factotum
(start factotum in the current 'namespace'. p9p's current namespace is
the value of the NAMESPACE environmental variable).

$ srv -a sources.cs.bell-labs.com
(I am prompted for my userid and password on the server)
user[venkatesh]: <my sources username>

[mount step; I use v9fs.You will have to adapt if you're using 9pfuse or 9mount]
$ sudo mount -t 9p $NAMESPACE/sources.cs.bell-labs.com <mountpath> -o trans=unix

Good luck,
-- vs
Permalink | Reply | 9 comments |
headers
baux80 | 1 Oct 2009 09:55
Picon

Re: 9atom.iso

On 29 September 2009 at 14:21, erik quanstrom <quanstro <at> quanstro.net> wrote:
> there's a new one at ftp://ftp.quanstro.net/other/9atom.iso.gz
> unfortunately it won't solve baux80's problem, i don't think.

exact. Doesn't boot anymore.

but on qemu plan9 installs well :) 

Now, I run it on my personal laptop. Should I install cpu server and auth or 
use it as a simple terminal. What's the best practice for a personal machine ?

thanks

bye
Permalink | Reply | 2 comments |
headers
hugo rivera | 1 Oct 2009 10:26
Picon

handling output

I've been wondering for a while if there's some way to multiplex (if
this is the correct term) stdout for a given program:
% ls  <at>  {grep regexp1 > file1 }  <at>  {grep regexp2 > file2}
where  <at>  is an operator that would copy ls stdout to two (maybe more)
different file descriptors. Probably some syntax is required
(something like  <at> [1=3]).
I think a c program can be written to accomplish this, but I'd like to
hear your opinion about it. Am I on the right path or just talking
rubbish?
Saludos

--

-- 
Hugo
Permalink | Reply | 6 comments |
headers
roger peppe | 1 Oct 2009 10:38
Picon
Gravatar

Re: handling output

2009/10/1 hugo rivera <uair00 <at> gmail.com>:
> I've been wondering for a while if there's some way to multiplex (if
> this is the correct term) stdout for a given program:

that's what tee does.

e.g.
ls | tee >{grep regexp1 > file1} >{grep regexp2 > file2}
Permalink | Reply | 3 comments |
headers
Richard Miller | 1 Oct 2009 10:45

Re: handling output

> I've been wondering for a while if there's some way to multiplex (if
> this is the correct term) stdout for a given program:
> % ls  <at>  {grep regexp1 > file1 }  <at>  {grep regexp2 > file2}

ls | tee >{grep regexp1 >file1} | grep regexp2 >file2
Permalink | Reply | 0 comments |

Gmane