Re: [9fans] several things
>But that assumes the shells in question _use_ cannonical mode. most of them use readline, so that might explain it.
Re: [9fans] several things
On Tue, Oct 14, 2008 at 02:15:15PM +0100, Charles Forsyth wrote: > i'm surprised at any actual name longer than 512 (or even 256), not so much > for plan 9, but > because linux systems still seem to have that tiny TTY limit on the size of > an input line, err - I seem to recall reading some linux pty/tty source that implied a larger limit in canonical mode - 4k/8k? But that assumes the shells in question _use_ cannonical mode.
Re: [9fans] iwp9 hotel info
twin single? On Tue, Oct 14, 2008 at 11:42 AM, Anant Narayanan <[EMAIL PROTECTED]> wrote: > On 14-Oct-08, at 4:43 PM, Rodolfo kix García wrote: >> >> I have the room in the Phillipos too. Is cheaper than the Park Hotel with >> or without the IWP9 offer. On the other hand, probably the Park Hotel is >> better. >> >>> On Tue, Oct 14, 2008 at 4:03 PM, Noah Evans <[EMAIL PROTECTED]> wrote: What kind of deal did you guys get at Park hotel? I settled on a double twin at the Phillipos for 75 euros. >>> >>> I can't remember, but whatever the price for a single room was with the >>> IWP9 thing. > > The Park hotel offers rooms for 68 Euros/night (includes breakfast and the > IWP9 discount). > Reservations are accepted either by email or phone. > > Regards, > Anant > > >
Re: [9fans] starting 9vx in FreeBSD :Shared object "libthr.so.3" not found
> Looks like the binary is for FreeBSD ?7.0. And you can't build it for FreeBSD 6 because the architecture of the thread library is different. Time to upgrade anyway, at least for me. Dave Eckhardt
Re: [9fans] iwp9 hotel info
On 14-Oct-08, at 4:43 PM, Rodolfo kix García wrote: I have the room in the Phillipos too. Is cheaper than the Park Hotel with or without the IWP9 offer. On the other hand, probably the Park Hotel is better. On Tue, Oct 14, 2008 at 4:03 PM, Noah Evans <[EMAIL PROTECTED]> wrote: What kind of deal did you guys get at Park hotel? I settled on a double twin at the Phillipos for 75 euros. I can't remember, but whatever the price for a single room was with the IWP9 thing. The Park hotel offers rooms for 68 Euros/night (includes breakfast and the IWP9 discount). Reservations are accepted either by email or phone. Regards, Anant
Re: [9fans] iwp9 hotel info
I have the room in the Phillipos too. Is cheaper than the Park Hotel with or without the IWP9 offer. On the other hand, probably the Park Hotel is better. > On Tue, Oct 14, 2008 at 4:03 PM, Noah Evans <[EMAIL PROTECTED]> wrote: >> What kind of deal did you guys get at Park hotel? I settled on a >> double twin at the Phillipos for 75 euros. > > I can't remember, but whatever the price for a single room was with the > IWP9 thing. > > > > -- > - curiosity sKilled the cat > > -- Rodolfo García AKA kix http://www.kix.es/ EA4ERH (@IN80ER)
[9fans] Snoopy OS X
I was hoping to use snoopy from p9p under OS X. MK fails with: mk: no recipe to make 'Darwin.o' Has anyone out there a patch to make this work? Ian
Re: [9fans] iwp9 hotel info
On Tue, Oct 14, 2008 at 4:03 PM, Noah Evans <[EMAIL PROTECTED]> wrote: > What kind of deal did you guys get at Park hotel? I settled on a > double twin at the Phillipos for 75 euros. I can't remember, but whatever the price for a single room was with the IWP9 thing. -- - curiosity sKilled the cat
Re: [9fans] several things
erik quanstrom wrote:
Are these limitations listed in some document?
I don't believe they are.
It might bve nice to think there are no arbitary limits in plan9
as the GNU mantra, however there are not many and personally,
working with remote servers with very long paths, I have never
(knowingly) hit this limit.
Having said this we could probably afford to up the size of pwd's
buffer to, say, 8k to be sixteen times as sure.
if you're going to all that trouble, why not make sure?
(i don't think this is worth it, personally, but if you do ...)
#include
#include
void
main(void)
{
char *p;
int n, s;
for(s = 128; ; s <<= 1){
p = malloc(s);
if(p == nil)
sysfatal("malloc");
p[s-1] = 1;
if((getwd(p, s)) == 0)
sysfatal("pwd: %r");
if(p[s-1] == 1)
break;
}
print("%s\n", p);
exits(0);
}
- erik
AAArgg!!! We leak for a fraction of micro seconds! we should
do realloc() here of course and free() the memory before exits()
just to make it even more complex ;-)
cinap
Re: [9fans] iwp9 hotel info
What kind of deal did you guys get at Park hotel? I settled on a double twin at the Phillipos for 75 euros. On Mon, Oct 13, 2008 at 11:39 PM, Jeff Sickel <[EMAIL PROTECTED]> wrote: > Go directly to http://www.amhotels.gr/index_ENG.htm. It's a flash site that > can through browsers off, but there is a link to a form that you may want to > use: > > http://www.volosnet.gr/amhoteliers/Reservation%5FENG/ > > > I used that and got a response in email within a few hours. Now I just need > to figure out how to call and make sure everything is confirmed. > > -jas > > > On Oct 13, 2008, at 9:34 PM, erik quanstrom wrote: > >> is there any way to contact or get reservation information for the >> the park hotel, recommended by the iwp9 website, via email >> or over the web? neither method has worked for me. >> no answer to the email, and the web site appears nonfunctional >> with multiple browsers. >> >> - erik >> >> > > >
Re: [9fans] several things
fd2path should probably complain if the buffer is too small. i'm surprised at any actual name longer than 512 (or even 256), not so much for plan 9, but because linux systems still seem to have that tiny TTY limit on the size of an input line, or it did the last time i tried to use the mouse to snarf and send a command line printed by make.--- Begin Message --- > But at least it means that the 'pwd' function returns a wrong answer > _without_warning_ when the path is longer. I tried it. This is not a nice > thing. Are these limitations listed in some document? The pwd(1) utility has this limitation for simplicity. The getwd(2) function and fd2path(2) syscall can work on arbitrary-sized buffers. So, to overcome the limit, you have few choices: 1) modify the pwd.c to allocate more memory; or 2) bind not-so-long parts of your path to /n/something to construct a namespace with shorter absolute paths; or 3) blame the tree holders. -- Best regards, Yaroslav.--- End Message ---
Re: [9fans] several things
> > Are these limitations listed in some document?
>
> I don't believe they are.
>
> It might bve nice to think there are no arbitary limits in plan9
> as the GNU mantra, however there are not many and personally,
> working with remote servers with very long paths, I have never
> (knowingly) hit this limit.
>
> Having said this we could probably afford to up the size of pwd's
> buffer to, say, 8k to be sixteen times as sure.
if you're going to all that trouble, why not make sure?
(i don't think this is worth it, personally, but if you do ...)
#include
#include
void
main(void)
{
char *p;
int n, s;
for(s = 128; ; s <<= 1){
p = malloc(s);
if(p == nil)
sysfatal("malloc");
p[s-1] = 1;
if((getwd(p, s)) == 0)
sysfatal("pwd: %r");
if(p[s-1] == 1)
break;
}
print("%s\n", p);
exits(0);
}
- erik
Re: [9fans] several things
> But at least it means that the 'pwd' function returns a wrong answer > _without_warning_ when the path is longer. I tried it. This is not a nice > thing. Are these limitations listed in some document? The pwd(1) utility has this limitation for simplicity. The getwd(2) function and fd2path(2) syscall can work on arbitrary-sized buffers. So, to overcome the limit, you have few choices: 1) modify the pwd.c to allocate more memory; or 2) bind not-so-long parts of your path to /n/something to construct a namespace with shorter absolute paths; or 3) blame the tree holders. -- Best regards, Yaroslav.
Re: [9fans] starting 9vx in FreeBSD :Shared object "libthr.so.3" not found
Looks like the binary is for FreeBSD ≥7.0. 2008/10/14 <[EMAIL PROTECTED]>: > Hi, > on starting 9vx inside FreeBSD with the command"./9vx.FreeBSD -u glenda" > I get the following error: > /libexec/ld-elf.so.1: Shared object "libthr.so.3" not found, required by > "9vx.FreeBSD" > > I came up with a blank on searches in 9fans lists and on the net generally > for a solution. > > Would welcome any help to solve this. > > Thanks, > > Alasdair > > > -- Best regards, Yaroslav.
[9fans] starting 9vx in FreeBSD :Shared object "libthr.so.3" not found
Hi, on starting 9vx inside FreeBSD with the command"./9vx.FreeBSD -u glenda" I get the following error: /libexec/ld-elf.so.1: Shared object "libthr.so.3" not found, required by "9vx.FreeBSD" I came up with a blank on searches in 9fans lists and on the net generally for a solution. Would welcome any help to solve this. Thanks, Alasdair
Re: [9fans] several things
> Are these limitations listed in some document? I don't believe they are. It might bve nice to think there are no arbitary limits in plan9 as the GNU mantra, however there are not many and personally, working with remote servers with very long paths, I have never (knowingly) hit this limit. Having said this we could probably afford to up the size of pwd's buffer to, say, 8k to be sixteen times as sure. -Steve
Re: [9fans] several things
> > 2) Reading pwd.c I can see 'char pathname[512]' at the beginning of the > main > > function. Does it mean plan9 paths are thus limited? > > no. fileservers evaludate the path one element at a time. > - erik > But at least it means that the 'pwd' function returns a wrong answer _without_warning_ when the path is longer. I tried it. This is not a nice thing. Are these limitations listed in some document? Ruda ps.: thanks otherwise for your other answers.
