[9fans] Removing a nedmail -c box
Hi, once I created a mailbox with nedmail upas/nedmail -c AListBox to store some mails from mailings lists, I made some error and want to get rid of that file again ls -l /mail/box/glenda/qemu -lrw-rw-rw- M 23 glenda glenda 0 Nov 10 06:53 /mail/box/glenda/qemu/L.mbox alrw--w--w- M 23 glenda glenda 0 Nov 10 06:53 /mail/box/glenda/qemu/mbox But `rm` fails to remove anything there: term% rm /mail/box/glenda/qemu/L.mbox rm: /mail/box/glenda/qemu/mbox: '/mail/box/glenda/qemu/mbox' does not exist term% rm /mail/box/glenda/qemu/L.mbox rm: /mail/box/glenda/qemu/L.mbox: '/mail/box/glenda/qemu/L.mbox' does not exist term% rm /mail/box/glenda/qemu rm: /mail/box/glenda/qemu: directory not empty term% rm -rf /mail/box/glenda/qemu term% ls -l /mail/box/glenda/qemu -lrw-rw-rw- M 23 glenda glenda 0 Nov 10 06:53 /mail/box/glenda/qemu/L.mbox alrw--w--w- M 23 glenda glenda 0 Nov 10 06:53 /mail/box/glenda/qemu/mbox What can I do here? How do I reverse the effect of `upas/nedmail -c Somthing` ? Regards Ingo
Re: [9fans] p9p sed vs linux sed
| sed 's/^//' | sed 's/$//' Why would you pipe text data in acme through sed and not use Edit x/^.*$/s/.*// ?
Re: [9fans] p9p sed vs linux sed
You mean perseus=; is your prompt? Strange. Actually sed is a line based command and should add a newline, imho. You can simply use tr -d '\n'. There are several quoting differences between plan9 sed and linux sed and I think the \+ operator doesn't work anyway in linux sed, but I might be wrong with this statement. cheers, ingo Hello, is this as expected? perseus=; echo -n aaa | 9 sed 's/^//' |tr -d '\n' aaa perseus=; echo -n aaa | sed 's/^//' aaaperseus=; For me the linux sed does what I expect, but not the p9p one (it adds a newline). Why? Thanks! Ruda
Re: [9fans] p9p sed vs linux sed
Luckily plan9 is not POSIX and actually sed does not really add a newline character, it just puts a newline to the end of each pattern buffer, that is done line-wise anyway. Also sed's little brother ed behaves the same, which makes the behaviour even more convenient term% echo -n 'abc' inp term% cat inp abcterm% ed inp '\n' appended 4 wq 4 term% And that is even consistent with (POSIX?) ed on linux systems or anywhere else. There is a very good reason to do so: The rule just applies to the end-of-input! So when you output a pattern from the sed buffer, you would need to check each time if we are at the end or not and add the newline or not, if it has been there or not. All those branches for just one character at the end of the input that can be easily removed if you really don't want it. So for simplicity there are very good reasons to state that any output from sed will end in a newline, even if the input doesn't. If you seek for a sed like thing that does not work line oriented, use ssam, as sam and the streamed version ssam, process input in another way, that is not line oriented. cheers ingo On Wed, Aug 12, 2015 at 09:57:18AM +0200, Rudolf Sykora wrote: On 12 August 2015 at 09:48, Ingo Krabbe ikrabbe@gmail.com wrote: Actually sed is a line based command and should add a newline, imho. I don't think it should add anything. For itself it should be able to count newlines (because of the possible use of addresses), but otherwise it should not do anything extra (it should be possible to pipe through two seds, for instance).
[9fans] github blob exchange
Hi Plan9ers, I wrote a little rc script for my personal use. I want to share it with you, as it look quite usefull to me (why would I have wrote it otherwise). https://github.com/ikrabbe/github.rc Check it out and tell me your thoughts. Regards, ingo
[9fans] Problem with imaps/imap.gmail.com
Hi, I'm using plan9 legacy and I have a problem with the tls certificate or with the handshake when I try to connect to the gmail.com account. It used to work for some time now. Today something went wrong with the imaps connection. I can't remember what, but there was some output on the console. Now, when I try to reconnect to the gmail box with echo -n 'open /imaps/imap.gmail.com/NAME/INBOX gmail' /mail/fs/ctl echo: write error: imap.gmail.com/imaps:tlsClient: tls: local invalid x509/rsa certificate I had a similar error a few weeks ago but eventually it went away. Does anyone know how to solve this? regards, ingo
Re: [9fans] Problem with imaps/imap.gmail.com
Great, after patching libsec and reinstall of tlsclient and upas both command work with gmail. Maybe I should run a system update 2015-07-30 22:19 GMT+02:00 David du Colombier 0in...@gmail.com: echo -n 'open /imaps/imap.gmail.com/NAME/INBOX gmail' /mail/fs/ctl echo: write error: imap.gmail.com/imaps:tlsClient: tls: local invalid x509/rsa certificate It works for me: % tlsclient tcp!imap.gmail.com!imaps * OK Gimap ready for requests from 88.164.189.37 z20mb397773409wjy I notice the certificate is signed with SHA-256. Maybe you're running an older release of 9legacy. Please apply this patch and give a try: http://9legacy.org/9legacy/patch/libsec-x509-sha256rsa.diff -- David du Colombier
Re: [9fans] Has Linux jumped the shark?
I don't think that anyone on this list really got what you want/-ed. At least I didn't. But maybe I already jumped the shark too. Regards ingo I sent a message to this list a short while ago suggesting that interested parties contact me about my startup. Sorry if it was too cryptic. Consider the message decrypted. brucee On Fri, Jul 24, 2015 at 7:05 PM, Tiago Natel tiago.na...@neoway.com.br wrote: Make a random commit and call it 4.0? Yes, I think that it jumped the shark as well as all competitors (BSD. win, osx). But unfortunate we don't have any other good production-ready choice at the moment. My hope is that someone is hard working on a new better tech for the next 20 years. But I know that this is pretty much utopia. Some company will introduce an old shit idea, call it 'new', make a lot of money and fuck ours next 20 years of software... []'s i4k Em 24/07/2015 02:10, Prof Brucee prof.bru...@gmail.com escreveu: You are not helping at all. We know that Peter has done *everything*. brucee On Fri, Jul 24, 2015 at 2:49 PM, cinap_len...@felloff.net wrote: http://9front.org/img/pjwshark.png -- cinap
Re: [9fans] Has Linux jumped the shark?
Actually not all bugs are fixed, some are introduced as a feature http://intellivisionlives.com/bluesky/games/credits/space.html#hawk On 24 July 2015 at 04:54, Prof Brucee prof.bru...@gmail.com wrote: has Linux with the release of 4.0 finally jumped the shark. Since it's called Hurr Durr I'ma Sheep, I thought I'd ask a celebrity what he thought of it. The response was much as I'd expected: http://goo.gl/ZefDFV Others simply said that it was baaad. I'm amused that as usual, dynamic patching of kernel source, like replacing dynamic libraries, is presented uniformly as a way to fix bugs everywhere quickly, because we all know that bugs always are fixed and never introduced, and being able to capture a kernel without rebooting is never of practical interest.
Re: [9fans] Has Linux jumped the shark?
Look what I started. And All That Clever Code ... Maybe I'm dumb but, where should I look at all that clever code and the things you started?
Re: [9fans] Trying to override 'cd' command
try whatis cd to test if the function as active at all btw: I just saw your signature. Great :D -- Ryan [ERROR]: Your autotools build scripts are 200 lines longer than your program. Something’s wrong. http://kirbyfan64.github.io/ -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: [9fans] Trying to override 'cd' command
try it with
fn cd{
builtin cd $1
prompt=(`{pwd}^'% ' '')
}
the difference is `{pwd} not '{pwd}.
Coming from a bash world, I really like knowing what directory I'm in at
the prompt. I tried putting this at the end of 'lib/profile':
fn cd{
builtin cd $1
prompt=('{pwd}^'% ' '')
}
cd $HOME
However, it doesn't work! The 'cd' command seems to do what it normally
does. The prompt stays at 'term% '. Does nothing.
--
Ryan
[ERROR]: Your autotools build scripts are 200 lines longer than your
program. Something’s wrong.
http://kirbyfan64.github.io/
Re: [9fans] ssh2 (at least the legacy version) seems incompatible
Actually openssh-6.7 disabled some insecure key exchange algorithms and
ciphers and the pln9 netssh command seems to offer some key exchange that it
does not support fully.
To allow communication with openssh-6.7 servers, as used to with =openssh-6.6
servers, it seems most convenient to me, to setup /etc/ssh/sshd_config of the
openssh server to allow the insecure algorithms that are wiped out of the
default algorithms the openssh servers offer.
The sshd_config lines that allow the needed algorithms and honour the defaults
of the new version of the openssh-6.7 server (as described on the manual page)
are:
# Ciphers and keying
Ciphers
aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc
KexAlgorithms
curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
regards,
ingo
ok, i found some more diagnostic messages in /sys/log/sshdebug:
p9 Jan 21 10:55:48 netssh: client user nil@192.168.1.12 id 0 id
string `SSH-2.0-OpenSSH_6.7p1-hpn14v5
p9 Jan 21 10:55:48 netssh: client user nil@192.168.1.12 id 0 sent KEX
algs: diffie-hellman-group1-sha1,diffie-hellman-group14-sha1
…
p9 Jan 21 10:55:49 netssh: client user nil@192.168.1.12 id 0 using
diffie-hellman-group14-sha1 Kex algorithm and ssh-rsa PKA
in contrast to:
p9 Jan 21 10:57:31 netssh: client user nil@192.168.122.6 id 0 id
string `SSH-2.0-OpenSSH_6.6.1p1-hpn14v5
…
p9 Jan 21 10:57:31 netssh: client user nil@192.168.122.6 id 0 using
diffie-hellman-group1-sha1 Kex algorithm and ssh-rsa PKA
The problem might be that `dh.c` has an empty implementation of `dh_client142`
Kex dh1sha1 = {
diffie-hellman-group1-sha1,
dh_server1,
dh_client11,
dh_client12
};
Kex dh14sha1 = {
diffie-hellman-group14-sha1,
dh_server14,
dh_client141,
dh_client142
};
Hi,
the netssh key exchange seems to be incompatible with openssh-6.7.
I installed a new version of openssh on a gentoo host recently, that
automatically came in as a stable update package for a gentoo-amd64 system:
OpenSSH_6.7p1-hpn14v5, OpenSSL 1.0.1k 8 Jan 2015
When calling this system with a plan9 (legacy) ssh2, the netssh process does
not provide any data in /net/ssh/keys. The read at
/sys/src/cmd/ssh2/ssh2.c:/^keyproc/+19, reads n=0 bytes when connecting to
the version of OpenSSH above.
I don't understand enough of the netssh keyfile infrastructure to debug this
logistic behaviour of /net/ssh/keys.
A downgrade to
OpenSSH_6.6p1-hpn14v4, OpenSSL 1.0.1k 8 Jan 2015
gives me ssh access to the gentoo system again.
If I find out more, I will post a followup. But maybe it would be helpfull
if someone with more insight into netssh tries to resolve this bug.
regards,
ingo krabbe
Re: [9fans] ssh2 (at least the legacy version) seems incompatible with
ok, i found some more diagnostic messages in /sys/log/sshdebug:
p9 Jan 21 10:55:48 netssh: client user nil@192.168.1.12 id 0 id
string `SSH-2.0-OpenSSH_6.7p1-hpn14v5
p9 Jan 21 10:55:48 netssh: client user nil@192.168.1.12 id 0 sent KEX
algs: diffie-hellman-group1-sha1,diffie-hellman-group14-sha1
…
p9 Jan 21 10:55:49 netssh: client user nil@192.168.1.12 id 0 using
diffie-hellman-group14-sha1 Kex algorithm and ssh-rsa PKA
in contrast to:
p9 Jan 21 10:57:31 netssh: client user nil@192.168.122.6 id 0 id
string `SSH-2.0-OpenSSH_6.6.1p1-hpn14v5
…
p9 Jan 21 10:57:31 netssh: client user nil@192.168.122.6 id 0 using
diffie-hellman-group1-sha1 Kex algorithm and ssh-rsa PKA
The problem might be that `dh.c` has an empty implementation of `dh_client142`
Kex dh1sha1 = {
diffie-hellman-group1-sha1,
dh_server1,
dh_client11,
dh_client12
};
Kex dh14sha1 = {
diffie-hellman-group14-sha1,
dh_server14,
dh_client141,
dh_client142
};
Hi,
the netssh key exchange seems to be incompatible with openssh-6.7.
I installed a new version of openssh on a gentoo host recently, that
automatically came in as a stable update package for a gentoo-amd64 system:
OpenSSH_6.7p1-hpn14v5, OpenSSL 1.0.1k 8 Jan 2015
When calling this system with a plan9 (legacy) ssh2, the netssh process does
not provide any data in /net/ssh/keys. The read at
/sys/src/cmd/ssh2/ssh2.c:/^keyproc/+19, reads n=0 bytes when connecting to
the version of OpenSSH above.
I don't understand enough of the netssh keyfile infrastructure to debug this
logistic behaviour of /net/ssh/keys.
A downgrade to
OpenSSH_6.6p1-hpn14v4, OpenSSL 1.0.1k 8 Jan 2015
gives me ssh access to the gentoo system again.
If I find out more, I will post a followup. But maybe it would be helpfull if
someone with more insight into netssh tries to resolve this bug.
regards,
ingo krabbe
[9fans] ssh2 (at least the legacy version) seems incompatible with openssh-6.7
Hi, the netssh key exchange seems to be incompatible with openssh-6.7. I installed a new version of openssh on a gentoo host recently, that automatically came in as a stable update package for a gentoo-amd64 system: OpenSSH_6.7p1-hpn14v5, OpenSSL 1.0.1k 8 Jan 2015 When calling this system with a plan9 (legacy) ssh2, the netssh process does not provide any data in /net/ssh/keys. The read at /sys/src/cmd/ssh2/ssh2.c:/^keyproc/+19, reads n=0 bytes when connecting to the version of OpenSSH above. I don't understand enough of the netssh keyfile infrastructure to debug this logistic behaviour of /net/ssh/keys. A downgrade to OpenSSH_6.6p1-hpn14v4, OpenSSL 1.0.1k 8 Jan 2015 gives me ssh access to the gentoo system again. If I find out more, I will post a followup. But maybe it would be helpfull if someone with more insight into netssh tries to resolve this bug. regards, ingo krabbe
[9fans] authentication, factotum and p9p
Good Morning, I have a running cpu/file server (legacy plan9 with venti backed fossil) and a plan9 terminal through qemu in my linux laptop and I want to mount the 9p filesystem from the cpu/file server with linux now. The 9p2000 protocol itself should be simple, but authentication might be a problem. When I try # 9 9pfuse -D CPU-ADDR MNTPT I get - Tversion tag 0 msize 8192 version '9P2000' - Rversion tag 65535 msize 8192 version '9P2000' - Tattach tag 0 fid 0 afid -1 uname ingo aname - Rerror tag 0 ename cannot attach as none before authentication 9pfuse: fsmount: cannot attach as none before authentication So how can I tell 9pfuse about the authentication tokens it needs. Any ideas? regards ingo
Re: [9fans] The Best way (easiest) of sending E-MAIL in Plan 9.
basically sending mail in plan9 depends on a command chain that looks a bit different, when you change perspective, but that's common to using any mail system. Of course other mail utilities are much more integrated. To understand the mail process I recommend the manual pages mail(1), marshal(1), rewrite(6), send(8) and smtp(8). Check the command /mail/lib/qmail, that should handle external mails, based on the results of rewrite. When you talk about the users point of view, I would recommend the acme Mail command, that is very useful and simple to use. But problems shouldn't rise from using acme, as its a very simple interface. It's more likely that you have a problem with the mailhub configuration. If you want to debug the process of sending mail, check some /sys/log/ files (smtp.fail, smtp, mail). Actually as smtp is called the Simple mail transport protocol, it's really simple to use a mailhub's smtp service through telnet — check rfc821 to see how to and remeber to end your lines with crnl, when communicating with a smtp service directly. That's what the command smtp(8) is for: The communication with another smtp service. I found it most challenging in plan9 to configure the /lib/ndb/local, but finally it reduced to define the local ipnet (the plan9 machine lives in) and set the smtp value to the mailhub's ip for that network. regards ingo What could be considered to be the best (userfriendliness is of importance) way of sending e-mail from Plan 9? I haven't cracked that nut yet although I've gotten a lot of help. Would be very grateful for your point of view in this matter (especially if it helps me to work this issue out and leave it behind me). I have a lot to learn about Plan 9 anyway. It's a very special OS and I just love it! Perfect for the Raspberry Pi in my opinion. Kind Regards, Mats
Re: [9fans] Persistent font in Acme.
The default font in acme is compiled in. So to change that you need to edit the source code and recompile the binary. Another option is to write an own command #!/bin/rc acme -f YOUR_FONT -F YOUR_FIXED_FONT $* or add an rc function. If you use dump files (you should), the fonts are written to the dump files. regards ingo Hi guys! Is there a way to get a persistent font in Acme? I'm using a Raspberry Pi and usually invoke Acme this way; acme -f /lib/font/bit/lucidasans/latin1.10.font and that gives me a font that looks good on my 32 TV. Grateful for any hint! Kind regards, Mats
Re: [9fans] [acme] Edit command -- More than one argument?
but you can't do this on a acme headline. So how would you apply such multiline
commands to a range you marked in the buffer?
Edit {
s/^/\[/
s/\:\ /\]/
}
On Mon, Oct 27, 2014 at 8:28 AM, Eduardo Alvarez astrochelon...@gmail.com
wrote:
Hello, everyone,
I'm in the process of learning acme via Russ Cox's p9p port. Recently, I
found
myself editing some text to use with markdown, and needed to make more
than one
modification to a list. I wanted to know if it's possible to give the Edit
command more than one argument. For example, I found myself needing to
replace
colons with a close bracket (]), and inserting an open bracket at the
beginning
of the line. So I did this:
Edit s/^/\[/
Edit s/\:\ /\]/
And I was hoping to combine these into a single line, so, for example:
Edit s/^/\[/ s/\:\ /\]/
(Not sure if escaping was necessary, but I was playing it safe)
Doing exactly what I did above resulted in the error
Edit: newline expected (saw f)
So that's obviously not it. But I'm not sure if it's at all possible.
Thank you in advance.
--
Eduardo Alvarez
Stercus, Stercus, Stercus, moriturus sum
-- Rincewind The Wizzard
Re: [9fans] [acme] Edit command -- More than one argument?
Yes you can. That's how I verified this works. Open up the tag to
multiple lines (just type newline in the tag).
I use the plan9 legacy version, that seems to ignore typed newlines. With the
p9p it works and possible with the 9front version too.
Actually I can echo 'Edit {…
}'/mnt/acme/{winid}/tag
with newlines and use that.
Edit {
s/^/\[/g
s/$/\]/g
}
Or you can use the 2-1 chord to apply and use the Edit command in-place. But
you need a confident mouse hand to use that effectively.
[9fans] plan9 legacy tcs -t unicode sucks last char
term% echo 'öäü'| tcs -t unicode| tcs -f unicode; echo öä term% this looks quite wrong! I will post a fix tomorrow noone else feels guilty. Regards, Ingo Krabbe
Re: [9fans] Annyoing modified by boyd
Hey Steve, actually I assume there is not further trace into cifs, as acme shows this message by asking cifs about the filestatus, when putfile is called, as I showed in the putfile function. Symbolically the full call is: cmd/acme/exec.c:/put\(/ cmd/acme/exec.c:/putfile\(/ libc/9sys/dirstat.c:/dirstat\(/ which will call cmd/cifs/main.c:/fsstat\(/ to get the file status before writing the file. I will trace the actual values that are fetched from this fsstat call, but I wonder why noone else ever stumbled across this. IMHO, plan9 with acme is the most powerfull tool when working with multiple machines and cifs is useful for sharing across the different OSses in use in our days. I don't have any other problems with cifs and I use it daily too, but with acme, which is extremely useful to browse remote directories and to show several files or parts of them on one screen. If you want to see the problem yourself its quite easy: Just acme A_FILE_ON_YOUR_FAVOURITE_CIFS_SHARE Change something in that file and try to Put it back. And yes, I can't reproduce this error with sam. So the point of failure must be the code in acme! When I call cifs with -D I get the following trace from a test.txt that I load into acme to produce the wrong warning (I just show some P9 traces not all). 1. Open the file: -6- Ropen tag 20 qid (75b35fd9e54fbee0 1411027197 ) iounit 0 -6- Rstat tag 20 stat 'test.txt' 'bill' 'trog' 'boyd' q (75b35fd9e54fbee0 1411027197 ) m 0666 at 1411027176 mt 1411027197 l 500 t 67 d 4 2. Put the changes, 1st without a warning -6- Ropen tag 38 qid (75b35fd9e54fbee0 1411027197 ) iounit 0 -6- Rwrite tag 38 count 498 -6- Rstat tag 38 stat 'test.txt' 'bill' 'trog' 'boyd' q (75b35fd9e54fbee0 1411027197 ) m 0666 at 1411027241 mt 1411027197 l 498 t 67 d 4 3. Try to Put another change, that shows the warning -6- Rstat tag 39 stat 'test.txt' 'bill' 'trog' 'boyd' q (75b35fd9e54fbee0 1411027295 ) m 0666 at 1411027241 mt 1411027295 l 498 t 67 d 4 It seems here that the first write sequence leads to the error -6- Ropen tag 38 qid (75b35fd9e54fbee0 1411027197 ) iounit 0 -6- Tstat tag 38 fid 646 -6- Rstat tag 38 stat 'test.txt' 'bill' 'trog' 'boyd' q (75b35fd9e54fbee0 1411027197 ) m 0666 at 1411027241 mt 1411027197 l 0 t 67 d 4 -6- Twrite tag 38 fid 646 offset 0 count 498/* … */ -6- Rwrite tag 38 count 498 -6- Tstat tag 38 fid 646 -6- Rstat tag 38 stat 'test.txt' 'bill' 'trog' 'boyd' q (75b35fd9e54fbee0 1411027197 ) m 0666 at 1411027241 mt 1411027197 l 498 t 67 d 4 as the stat after the write shows the same timestamp as the open (before the write), which seems wrong. When the file is changed in the acme buffer and should be put again, the stat reports the right timestamp from the first put, which leads to the warning. Regards Ingo Krabbe Can you trace this a bit more into cifs? cifs is one of mine and I use it daily without problems, though I never migrated from sam to acme, so perhaps I just don't see your issue. I remember that smb/cifs does have weird timestamps some of which are only changed on 2 second boundries - though the code you show should cope happily with that. The server has its own timestamp which cifs reads at startup and uses that to convert the server's localtime to utc, but I think this time is read only once per session so that is unlikely to be the problem. Sorry if I'am a bit vague but it was 10 years ago now, but I am happy to dig if you can provide a bit more info. -Steve
Re: [9fans] Annyoing modified by boyd
FILE modified by boyd since last read strikes me as more useful than most
error messages I see these days. My only question is what particular weapon
Boyd would have used to modify the file.
Hey Winston,
I agree that the message itself would be extremely useful if it would be
reported correctly. But acutally when its just me who modifies a remote file
with acme in a editing session, I get these modified by boyd warnings and I
will get the same warning if someone else had modified the file, in the end
this really useful message gets useless, as most times it is wrong and gets
auto-ignored by the chair-to-keyboard-interface.
FYI: boyd is the unknown modifiying user of any file on cifs, who is a friend
of bill and trog. I always think of boyd to be the younger brother of void.
Regards
Ingo Krabbe
On 17 September 2014 23:18, Ingo Krabbe ikrabbe@gmail.com wrote:
Hey,
using legacy bell-labs plan9 (I don't know the others), I often, that
converges to always, get FILE modified by boyd since last read when
editing a file on a cifs share with acme.
The cifs main.c defines boyd as the modifying user (muid) in I2D and
V2D, which are from fs.stat.
From /sys/src/cmd/acme/exec.c:/putfile/+14
if(d!=nil runeeq(namer, nname, f-name, f-nname)){
/* f-mtime+1 because when talking over NFS it's often off
by a second */
if(f-dev!=d-dev || f-qidpath!=d-qid.path ||
f-mtime+1d-mtime){
f-dev = d-dev;
f-qidpath = d-qid.path;
f-mtime = d-mtime;
if(f-unread)
warning(nil, %s not written; file already
exists\n, name);
else
warning(nil, %s modified%s%s since last
read\n, name, d-muid[0]? by :, d-muid);
goto Rescue1;
}
}
Hmm, possibly this is another time quirk, like that one from NFS. Does
anyone know a good solution to that problem?
Regards
ikrabbe
[9fans] Annyoing modified by boyd
Hey,
using legacy bell-labs plan9 (I don't know the others), I often, that converges
to always, get FILE modified by boyd since last read when editing a file on a
cifs share with acme.
The cifs main.c defines boyd as the modifying user (muid) in I2D and V2D,
which are from fs.stat.
From /sys/src/cmd/acme/exec.c:/putfile/+14
if(d!=nil runeeq(namer, nname, f-name, f-nname)){
/* f-mtime+1 because when talking over NFS it's often off by a
second */
if(f-dev!=d-dev || f-qidpath!=d-qid.path ||
f-mtime+1d-mtime){
f-dev = d-dev;
f-qidpath = d-qid.path;
f-mtime = d-mtime;
if(f-unread)
warning(nil, %s not written; file already
exists\n, name);
else
warning(nil, %s modified%s%s since last
read\n, name, d-muid[0]? by :, d-muid);
goto Rescue1;
}
}
Hmm, possibly this is another time quirk, like that one from NFS. Does anyone
know a good solution to that problem?
Regards
ikrabbe
Re: [9fans] Using webfs from rc
Hey riddler, that has something to do with the way how you open the connection. I'm not 100% sure if its a perfect description what happens, but when you % echo -n url http://www.google.co.uk ctl the ctl will open and close the connection to 0/ctl. But you can read the body only while the 0/ctl device is open. (Or it might be differnet that you need to open body for reading before you open and send to ctl). Best is to check the code of hget to understand how this works. I'm not sure if it's possible or in any way convenient to use webfs through rc. I think hget is your friend. cheers ingo ---BeginMessage--- Hey guys, Been toying with webfs/abaco and I'm attempting to try to use it (webfs) from rc without much luck. I've been doing the following: % cat clone 0 acceptcookies on sendcookies on redirectlimit 10 useragent webfs/2.0 (plan 9) % cd 0 % echo -n url http://www.google.co.uk ctl % cat body cat: can't open body: 'body' url is not yet set I'm unsure why this doesn't seem to be working. I took a look at the abaco source and it looks like this is all it does as well when POST data is not involved. I've tried various forms of url with trailing slashes and pages I know result in content but still nothing. Any idea where I'm going wrong? ---End Message---
Re: [9fans] (no subject)
In my experience a VESA BIOS will sometimes report
different available modes depending on the detected
EDID.
I have no problem believing this is true, but I'm also sure there's more
to it than that.
I agree. One problem is that these things are all different,
almost completely undocumented, and implement non-standard
modes seemingly at random. Some people involved with various
OSX86[0] efforts have developed methods for probing (and in
some cases, modifiying) the VESA BIOS on some cards. All
kinds of strange behaviors have been observed.
In qemu the emulated controller seems to support 1920x1200x{16,24,32} as well
as some other modes
term% aux/vga -m vesa -p
warning: reading edid: VBE error 0x0100
vesa flagUlinear|Hlinear
vesa sigVESA 2.0
vesa oemBochs/Plex86 VBE(C) 2003
http://savannah.nongnu.org/projects/vgabios/ 0.2
vesa vendor Bochs/Plex86 Developers
vesa productBochs/Plex86 VBE Adapter
vesa rev$Id: vbe.c,v 1.64 2011/07/19 18:25:05 vruppert Exp $
vesa cap 8-bit-dac
vesa mem16777216
[...]
vesa mode 0x187 1920x1200x16 r5g6b5 direct
vesa mode 0x188 1920x1200x24 r8g8b8 direct
vesa mode 0x189 1920x1200x32 x8r8g8b8 direct
vesa mode 0x18a 2560x1600x16 r5g6b5 direct
vesa mode 0x18b 2560x1600x24 r8g8b8 direct
vesa mode 0x18c 2560x1600x32 x8r8g8b8 direct
[...]
you may be able to try these with your monitors as a start.
I'd be interested in a survey with broader results
than just dueling anecdotes
I haven't made any attempt to catalogue VESA vs EDID
discrepancies, but I do keep a small archive of hardware
info here:
http://plan9.stanleylieber.com/hardware
We try to collect the sysinfo[1] output for as many
systems as possible, for later reference.
sl
[0] http://www.osx86project.org
[1] http://man.aiju.de/1/sysinfo
Re: [9fans] Remote auth server
Yes it is possible and usefull too. All you should have on a fast lan is a fileserver. But: 1. the plan9 terminal must configure the network before it connects to the auth server either through dhcp or through a static configuration in the boot configuration 2. somewhere in the setup of the terminal or the auth server you have to use a hostname that goes into the nvram, that can be reached at boot time. I can't remember where it was, but it was one of my bigger struggles with the plan9 setup. Hi! I'm trying to setup my first multi-host Plan 9 system. I was thinking about running file server/auth server on a VPS so that I can access it from anywhere. I configured cpu service on my VPS and I can connect to it via drawterm. But when I try to boot a terminal that is configured to use it as auth server, the terminal stops with a message: mount: auth_proxy: authread: auth protocol not finished. But is it actually possible to have the auth server and terminal not on the same LAN? Every configuration example I've seen has all the resources on the same IP address block. Thanks! -- Paul Anokhin
Re: [9fans] sam resizing
Hey Mark, as you wrote, sam window configuration depends on the situation. But for me its not the number of files that changes the resize options, but the base size of the whole sam workspace. If it's big enough, its resonable to resize the ~~sam~~ command window to an upper left rectangle (view this mail with fixed font): +--+ ! ~~sam~~ ! ! ! ! a1 ! +---+--+ ! ! ! ! a2 ! a3 ! ! ! ! +---+--+ If you resize your windows by clicking(B3) in area a1 your window will resize to a1+a3. If you choose a2 the window goes to a2+a3 and if you choose a3 the window covers a3 only. You can even place the ~~sam~~ window somewhere in the middle, to have eight different auto-resize-options. But that window configuration is a bit academic. But its quite easy to start a manual window resize at the lower right edge of ~~sam~~ and drag towards the lower left edge, so that a window covers a2 only. I think these resize options and window layout is quite good to work with even in quite complex situations and zerox buffers. cheers, ingo On Mon Oct 21 22:18:54 CES 2013, vanattenm...@gmail.com wrote: I would find it useful if a sam window resize could be undone one step, i.e. resize the window again to its size and position before the last resize. Perhaps by clicking B1, just as clicking B3 enlarges it. That would help keeping windows arranged a bit while enlarging one after the other as I see fit for my work. One can of course do without the visual clue of such an arrangement and rely on just the file list in the menu. When there are many files, there is no choice, and that works well enough. But when working on only a handful, it might be convenient to have this additional possibility by just one click. Have people experimented with this, or at least entertained the same wish? Mark.
Re: [9fans] sam resizing
On Tue Oct 22 08:19:47 CES 2013, quans...@quanstro.net wrote: so i'm wondering. acme does a good job of auto layout. the thing acme lacks is a edit buffer (~~sam~~). so maybe it would be fruitful to add edit buffer(s) to acme? - erik I don't think its good to compare acme and sam as the approaches are quite different and both tools are useful. Actually I use acme sometimes as a file browser or remote command windowBut when I work on source code I don't like, for example, that my mouse cursor in acme needs to float over the window I type in. cheers, ingo
[9fans] my mails to 9fans
Hmm, direct mx is blocked by spamhouse too. Seems I need an own smtp server in the internet with a static IP. As my mails sometimes don't reach the list, I want to test to send it direct to the mx now. If this arrives, I will keep this practice. If it doesn't I might need another tele-communications provider, as I found out, that some of their outgoing smtp servers are blacklisted by spamhouse. cheers, ingo PS.: I hope I can freely post to this list soon.
[9fans] my mails to 9fans
Seems I found a mail relay that works. thanks for your audience ingo
[9fans] cifs fails on nodes named aux
Hey, I found a quite strange effect with cifs (plan9 bell labs edition). I use cifs to mount werc installations from p9p linux servers. Cifs is needed here, as the virtual hosted machine does not support nfs. Maybe I should switch to another userspace filesystem, but for now its cifs. Any node named `aux` is translated into `AHY9U3~9`, of course one-way only, such that I cannot use the `AHY9U3~9` node in my plan9 mount. Renaming to aux2 for example, solves the problem. I found this when looking at werc/bin/aux, which is a directory. So I tried this in werc/tpl: term% ed aux ?aux i This is a test . wq 15 term% ls -l --rw-rw-rw- M 166 bill trog 15 Aug 24 11:29 AHY9U3~9 --rw-rw-rw- M 166 bill trog 683 Mar 29 10:03 _debug.tpl d-rwxrwxrwx M 166 bill trog0 Mar 29 10:03 _users --rw-rw-rw- M 166 bill trog 1919 Mar 29 10:03 sitemap.tpl Maybe I will hunt this further down next weeks... ... Ah I just found out, that ls 'aux' does actually work. Any hints for debugging this might help. cheers ingo krabbe
Re: [9fans] cifs fails on nodes named aux
Ingo Krabbe ikrabbe@gmail.com wrote: |Hey, | |I found a quite strange effect with cifs (plan9 bell labs edition). \ |I use cifs to mount werc installations from p9p linux servers. \ |Cifs is needed here, as the virtual hosted machine does not \ |support nfs. Maybe I should switch to another userspace filesystem,\ | but for now its cifs. cifs is Windows, i think. If this is the case, then you may run into the issue of implicit filenames. Search «aux tale», or browse heirloom.sourceforge.net/mailx_aux_c.html. Yes, cifs is used often to mount windows shares, but in this special case I just chose cifs, as NFS has no current user space server and I want to share some filesystems of a virtual host, where I can't add kernel modules. So actually in my setup I use a Linux CIFS Server (aka. smbd, samba) and the cifs client from plan9. The shared filesystem originally is a ext2 (or 3 or 4). Should I really have managed to step over a system design bug that is imported from 1978 till now, through all systems and versions. Actually, mounting the cifs with a linux mount -t cifs command maps the aux filename correctly. So the bug might just have been imported into the plan9 cifs client. Funny bug. [.] |Any hints for debugging this might help. Maybe. Ciao |cheers | |ingo krabbe --steffen---BeginMessage--- Ingo Krabbe ikrabbe@gmail.com wrote: |Hey, | |I found a quite strange effect with cifs (plan9 bell labs edition). \ |I use cifs to mount werc installations from p9p linux servers. \ |Cifs is needed here, as the virtual hosted machine does not \ |support nfs. Maybe I should switch to another userspace filesystem,\ | but for now its cifs. cifs is Windows, i think. If this is the case, then you may run into the issue of implicit filenames. Search «aux tale», or browse heirloom.sourceforge.net/mailx_aux_c.html. [.] |Any hints for debugging this might help. Maybe. Ciao |cheers | |ingo krabbe --steffen---End Message---
Re: [9fans] cifs fails on nodes named aux
not sure why FAT32 would be relevant here, since he's using a linux cifs server from an ext fs. samba mangles reserved names much as it mangles long filenames -- check mangle_hash2.c for examples. when samba is deciding if a filename needs to be mangled, it checks for reserved words along with filename length and prohibited characters. so if samba decides it nees to serve a file named aux, it's going to ruin it, unless you specifically disable this behavior. for the record, windows itself does this nonsense as well, unless you've got the 'cifs extensions for unix' garbage slathered on. the curse of bad design lives on. I'm not sufficiently intimate with the cifs server he's using, or plan 9's cifs client, to explain why the behavior is different using the linux client. There's generally a lot of magic involved with cifs deciding how best to vomit its guts across the wire, and I've deliberately avoided learning it where possible. Were this my system, I'd just switch to 9p. khm I would like to switch to a 9p distribution of files, but how Do I tell this other people who want to access files on the servers too: Here I have a better filesystem you never heard of and likely will never hear, as it is used only by the coolest freaks, whom you are no one of.? As long as you don't have a solution like: Take this package, install it to your windows and ignore all license security checks. Anything from then on will be done automatically on your system and all systems you are going to install in the future. So you don't need to care, just access these files. (Which is kind of what people think, Windows Filesharing is). But taking into account that windows is still the refence system, files that are named aux, con, nul and prn aren't supported by windows and its very easy to show that this is so. So files don't need to exist or shown correctly, that are named this way, as long as I know about that fact and can easily demonstrate that windows truly fails to work and still contains design faults that are a quarter of a century old. BTW.: The cifs server I use is the debian squeeze samba package (Version ~3.5.6). I'm not sure about all these versions and names, some call it cifs, some call it samba, I still like raider, though it's called twix now. (raider was the name for this twix chocolate, caramel bar, in germany in the 80's ;). Maybe I will debug this further when I find some time... Cheers, Ingo Krabbe
[9fans] page fit to window does not work on large jpegs
Hey 9fans, Today I tried to open a quite large jpeg. About 2400x1800 pixel. So first I want an overview of that image. So I choose Fit in Window from the page window. All that this command does is page: unloadimage, which was not the expected function. Actually I found no way to scale the image down and just get an overview of it. regards, ingo -- i don't do signatures
Re: [9fans] page fit to window does not work on large jpegs
On Thu, Apr 12, 2012 at 11:47:49AM -0600, andrey mirtchovski wrote: change line 452 of /sys/src/cmd/page/rotate.c to 'sysfatal(unloadimage: %r);', compile and run your program again. Yes, that was expected somehow: page: unloadimage: unloadimage: image too wide Maybe I will take a closer look later. the code will now print what the exact error is and we can take it from there. -- i don't do signatures
Re: [9fans] page fit to window does not work on large jpegs
On Thu, Apr 12, 2012 at 02:31:05PM -0400, erik quanstrom wrote: On Thu Apr 12 14:24:25 EDT 2012, ikrabbe@gmail.com wrote: On Thu, Apr 12, 2012 at 11:47:49AM -0600, andrey mirtchovski wrote: change line 452 of /sys/src/cmd/page/rotate.c to 'sysfatal(unloadimage: %r);', compile and run your program again. Yes, that was expected somehow: page: unloadimage: unloadimage: image too wide Maybe I will take a closer look later. /sys/src/libdraw/unloadimage.c:31 you could start by making that constant 12000 or some such. that will probablly violate some other assumption, but at least it's a start. I assume that might be related to Displaybufsize=8000 in draw.h - erik -- i don't do signatures
