[9fans] DNS server domain
Moin, how do I set the "defaultdomain" an a Plan 9 DNS server? % ndb/dnsquery > cab !dns: resource does not exist > cab.mteege.de cab.mteege.de ip10.18.47.11 Would be nice if I can get % ndb/dnsquery > cab cab ip 10.18.47.11 Many thanks Matthias
Re: [9fans] Plan 9 system behind firewall
I tryed Richard's suggestion, and got very good success. Thank you very much, Richard. Now I can drawterm from other IP domain than Plan 9-2 domain on Windows or Debian Linux. The last one, the long time delay of getting rio bootup remaines unsolved. However, it takes at doing /usr/okamoto/lib/profile, especially a line of mount -c /srv/boot /n/duniteother other, which is mounting 'other' file system to the main file system from the file server dunite withing Plan 9-2 system. I think I know why this happens, probably as John wrote yesterday. >From outside the firewall, we have to target the fileserver as the fierewall machine, but after loged in we have to target dunite fileserver withing the domain... I'll try it next week. I don't know I can solve it cleanly or not, though. Kenji
Re: [9fans] DNS server domain
how do I set the "defaultdomain" an a Plan 9 DNS server? dnsdomain pairs (in ndb(6)). -Josh
Re: [9fans] DNS server domain
> Moin, > > how do I set the "defaultdomain" an a Plan 9 DNS server? > ndb(6) didn't clear everything up for me. then again, i haven't had any coffee yet. the dnsdomain attribute is well-documented. what i didn't see is the convention for where to hang it in the database. generally, i do this by setting ipnet in /lib/ndb/local. e.g. ipnet=athensnat ip=192.168.0.0 ipmask=/120 fs=buda.quanstro.net ipgw=192.168.0.4 dns=192.168.0.136 dnsdomain=quanstro.net authdom=plan9.quanstro.net auth=ladd - erik
Re: [9fans] Kernel Compiling Problem
I said: > I don't understand this, because as > far as I can see the mtime should be taken from the actual mtime of > the file being copied from the CD (install) ... I've now traced the problem to a leap-year bug in the Plan 9 ISO9660 file server. Several files in the distribution (including /386/bin/fossil/fossil) were made on 29 February this year. A logic error in 9660srv rejects this as an impossible date, so it sets mtime for those files to zero. Patch 9660srv-leapyear should fix the error.
Re: [9fans] DNS server domain
> the dnsdomain attribute is well-documented. what i didn't see > is the convention for where to hang it in the database. > generally, i do this by setting ipnet in /lib/ndb/local. e.g. I put it in my ndb/local and it works for the Plan 9 server % ndb/dnsquery > cab cab.mteege.de ip10.8.47.11 But if I query the server from other clients on the same network I've got empty results. Is dnsdomain only usefull for "internal" querys? Matthias
Re: [9fans] DNS server domain
> > the dnsdomain attribute is well-documented. what i didn't see > > is the convention for where to hang it in the database. > > generally, i do this by setting ipnet in /lib/ndb/local. e.g. > > I put it in my ndb/local and it works for the Plan 9 server > > % ndb/dnsquery > > cab > cab.mteege.de ip 10.8.47.11 > > But if I query the server from other clients on the same network I've > got empty results. Is dnsdomain only usefull for "internal" querys? > > Matthias by "other clients" do you mean plan 9 systems or non-plan9 systems? the default domain is not communicated via dns mechanisms. - erik
Re: [9fans] DNS server domain
> by "other clients" do you mean plan 9 systems or non-plan9 systems? > the default domain is not communicated via dns mechanisms. I mean non-plan9 systems. Matthias
Re: [9fans] DNS server domain
When I used my plan9 server as dns server, it was also my dhcp server, which is quite handy. it communicates some info to the dhcp clents, for example the default search domain, which, in my understanding does just what you want. It firsq querys the dns server for the domain, then tries to prefix it to the default search domain, and query that. worked for me :-) Cheers Johnny On Fri, 28 Mar 2008 15:54:55 +0100 Matthias Teege <[EMAIL PROTECTED]> wrote: > > the dnsdomain attribute is well-documented. what i didn't see > > is the convention for where to hang it in the database. > > generally, i do this by setting ipnet in /lib/ndb/local. e.g. > > I put it in my ndb/local and it works for the Plan 9 server > > % ndb/dnsquery > > cab > cab.mteege.de ip 10.8.47.11 > > But if I query the server from other clients on the same network I've > got empty results. Is dnsdomain only usefull for "internal" querys? > > Matthias > >
[9fans] tiff(1) for page(1)
I have borrowed much of jpg(1) to produce a similar tiff(1) that I successfully integrated with page(1) (more or less: it disobeys the injunction: /* * N.B. These commands need to read stdin if %a is replaced * with an empty string. */ and I don't think I can sensibly address that aspect). There are many sample TIFF images it can't render, I need to understand the TIFF library better before being able to comment or, preferably, fix these problems. One problem this mailing list may be able to assist me with involves producing image files. I can successfully generate RGB24 (also labelled CMAP8 within jpg(1) - three colour channels, no alpha) files from RGBV images, but any attempts at dumping what look like perfectly reasonable RGBA32 images that happen to be the "natural" format delivered by libtiff, results in, apparently, blank images or, in the one FAX instance I used for testing, at best some blue text where it ought to be black. This would be using -9 or -c and making RGBA32 the default target format. Displaying the generated RGBA32 images (allocimage(), loadimage()) works just fine for RGBA32 and, to the extent that I tested things, even for the monochrome, colour-mapped and three-colour formats, I'm not sure that I have successfully covered all the jpg(1) options. I borrowed code from /sys/src/cmd/jpg/^(torgbv totruecolor) quite liberally so tiff(1) can display or write to stdout all the jpg(1) output formats I manged to grasp, but I cannot find a valid, functional example of writing an RGBA32 "frame buffer" to stdout. The temptation now is to display the image and writeimage(2) the produced structure, but that abuses a window, while using the memdraw(2) facilities is not readily available until someone actually ports memdraw(2) to APE (I think I already did this, but I didn't want to go off on yet another tangent, I've been hacking at this way too long already). Even with memdraw(2), I think the approach - allocmemimage(), loadmemimage(), writememimage() - would seem at best inelegant. Anyone who wants to improve this tiff(2), please let me know; give or take the need for the libtiff library, it is pretty much a standalone application, anything I borrowed from /sys/src/cmd/jpg/ I incorporated into the source rather than attempt to link to an alien directory. I changed enough in an attempt to simplify things to the point I could understand them that the relationship will be hard to maintain. But having the code more or less self-contained seems like a good thing in this instance. At 929 lines, it is tempting (but futile) to include it in this message. ++L PS: Sorry if the above is a bit rambling, there were so many different code paths, options and possibilities, it's been very hard for me to keep track of all the issues. I'm hoping the source will speak for itself.
Re: [9fans] Does sam accepts interrupt signal
OK, I see. It's helpful. Thank you~ On Thu, Mar 27, 2008 at 11:46 PM, Charles Forsyth <[EMAIL PROTECTED]> wrote: > it has been some time since i last used sam interactively, > but your description > > sam appears to forget the state (in fact it's I that forget > it) and treat my input as plain text. In this case, no matter putting > a single dot or completing with a `/' could not save me. As a result, > sounds as though you've ended up typing behind the point where sam > is actually reading input (ie, in the transcript). > try snarfing and sending a newline (or perhaps a .) to resynchronise. > > > -- HZ
