Re: [9fans] Multi-domain authentication?
On Tue, Oct 21, 2008 at 4:29 AM, Eric Van Hensbergen [EMAIL PROTECTED] wrote: Good general problem, I'd also like to add my personal pain point that only the file server knows about the relationship between groups and users. It'd be nice to have a more general service to take care of this, and include some ability to assign remote delegated user names to local groups. this would indeed be nice. i believe some of the stuff that forsyth was working on at one time to put SPKI into inferno could have helped in this context.
Re: [9fans] mount followed by srvfs needs a sleep?
2008/10/21 Micah Stetson [EMAIL PROTECTED]: local mount /srv/penelopa $home/shared/penelopa #sleep 1 # --- see the text bellow; this pertains to my main question local srvfs CALC $home/shared/penelopa/home/ruda/CPA-CALC # local mount /srv/CALC $home/shared/CALC I haven't actually tried this, so I probably shouldn't be writing it, but How about this: local 'rc -c ''mount blah blah srvfs blah blah mount blah blah''' Well, this seems really nice. I wonder why this did not come to my mind too... :) I guess sth like this will work... Thanks loginpassword. Only then I execute my 'local mount ...' command. If I executed this right away (without mount unmount) I would end in a situation when the plumber shell needs to talk to me. But this shell writes to the /dev/kprint... What is the better way? I think this is the problem auth/fgui is supposed to solve. See factotum(4). (and, actually, is this kind of authentication any safe?) In what way? Have you read /sys/doc/auth.ps? Micah I read auth.ps some time ago, I will read it again as well as factotum(4). Hopefully I will find the answers. Thanks Ruda
[9fans] How to go about doing screen reading
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 In pseudocode: when mouse has not been moved for at least 1 second find cursor position if cursor has moved stop find window where cursor is if cursor has moved or no text window underneath stop find line of text in the window device where the cursor is say the text when F1 is hit read out line already typed at open rio window Any technical problems with this approach? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkj9sOAACgkQuv7AVNQDs+y/aQCeIuuTrAdNar5BTXXa7oZQNMu7 9XMAn0qmnR5jup2t7cO8GeczROTOYu70 =r7hM -END PGP SIGNATURE-
Re: [9fans] Multi-domain authentication?
Does that make sense? yes. very good explaination. however, i can't see how i could use this. while i do manage 2 auth domains (and growing), i still have the requirement that everyone have an @tld address, so the administration needs to be centralized, regardless. conversely, leaf nodes can't depend on the main auth server, since this would mean no work could be done if they can't contact the main auth server. perhaps i just lack imagination. - erik
Re: [9fans] How to go about doing screen reading
[EMAIL PROTECTED] (Pietro Gagliardi) writes: In pseudocode: when mouse has not been moved for at least 1 second find cursor position if cursor has moved *SNIP* Any technical problems with this approach? I think there is an easier way to do screen reading within Acme. Here's a quote from the Acme paper: quote The last file, event, is the most unusual. A program reading a window's eventfile is notified of all changes to the text of the window, and is asked to interpret all middle- and right-button actions. The data passed to the program is fixed-format and reports the source of the action (keyboard, mouse, external program, etc.), its location (what was pointed at or modified), and its nature (change, search, execution, etc.). This message, for example, MI15 19 0 4 time reports that actions of the mouse (M) inserted in the body (capital I) the 4 characters of timeat character positions 15 through 19; the zero is a flag word. Programs may apply their own interpretations of searching and execution, or may simply reflect the events back to Acme, by writing them back to the eventfile, to have the default interpretation applied. Some examples of these ideas in action are presented below. /quote A screenreader can obtain information about changes to the state of the system by reading the event file. Do other parts of the window system provide this sort of interface? -- Chris
[9fans] bitsy anyone?
Does anyone happen to have a working bitsy kernel and paqdisk? I've tried both compiling myself and the kernel/paqdisk that used to be on nemo's contrib, both to no avail. Either way, I get a kernel panic on the iPaq. The various instructions around on the wiki and such have the user partition too small for the paqdisk that gets built out of the box from a fresh Plan 9 install... so I did increase the partition sizes accordingly. I'm hoping that's not the problem... Thanks in advance! -Ben winmail.dat
Re: [9fans] bitsy anyone?
I can dig in the dump to find out our last kernel/paqdisk. But we don´t use that anymore. On Tue, Oct 21, 2008 at 7:21 PM, Benjamin Huntsman [EMAIL PROTECTED] wrote: Does anyone happen to have a working bitsy kernel and paqdisk? I've tried both compiling myself and the kernel/paqdisk that used to be on nemo's contrib, both to no avail. Either way, I get a kernel panic on the iPaq. The various instructions around on the wiki and such have the user partition too small for the paqdisk that gets built out of the box from a fresh Plan 9 install... so I did increase the partition sizes accordingly. I'm hoping that's not the problem... Thanks in advance! -Ben
Re: [9fans] Multi-domain authentication?
On Mon, Oct 20, 2008 at 10:29:17PM -0500, Eric Van Hensbergen wrote: Good general problem, I'd also like to add my personal pain point that only the file server knows about the relationship between groups and users. It'd be nice to have a more general service to take care of this, and include some ability to assign remote delegated user names to local groups. I also like the idea of having user-context groups where users can create their own groups and assign local and remote users to them for the purposes of accessing file servers they own. My internalized model of how this should work is AFS's ACL system (if that's not a dirty word...) and the associated PTS group system. Between them, they provide excellent ability to talk about users from remote cells and allow users to create and manage their own groups. --nwf; pgp8shDM38XJ5.pgp Description: PGP signature
Re: [9fans] Multi-domain authentication?
My internalized model of how this should work is AFS's ACL system (if that's not a dirty word...) and the associated PTS group system. Between them, they provide excellent ability to talk about users from remote cells and allow users to create and manage their own groups. just use afs if that's what you want. - erik
Re: [9fans] bitsy anyone?
Does anyone happen to have a working bitsy kernel and paqdisk? I've tried both compiling myself and the kernel/paqdisk that used to be on nemo's contrib, both to no avail. Either way, I get a kernel panic on the iPaq. The various instructions around on the wiki and such have the user partition too small for the paqdisk that gets built out of the box from a fresh Plan 9 install... so I did increase the partition sizes accordingly. I'm hoping that's not the problem... Hello, I am currently using Plan 9 on a Compaq iPaq h3650. I compiled the kernel and the paqdisk in May 2008 from a current Plan 9. It worked really fine, except with the Wi-Fi. However, I had some problems when uploading the paqdisk on the iPaq when the image file is larger than 4 MB. The image seems to be corrupted during the upload on the iPaq and Plan 9 crash during boot. This problem does not appear with a smaller paqdisk. Also, as you said, If you leave the armpaqproto configuration file as it is, the image file created will be larger than the partition, so you must modify it. In fact, I read in a documentation you cannot easily resize the partition since it is apparently hard coded in the kernel. One of the kernel and paqdisk I made is available on my website [1]. I also put the concerning armpaqproto file online. It was compiled in May 2008. I also tried from old Nemo's and John's [2], and it worked fine too. But they are really old. [1] http://www.9grid.fr/misc/plan9/ipaq_h3650/work-mine [2] http://www.9grid.fr/misc/plan9/ipaq_h3650/work-other -- David du Colombier
Re: [9fans] bitsy anyone?
However, I had some problems when uploading the paqdisk on the iPaq when the image file is larger than 4 MB. The image seems to be corrupted during the upload on the iPaq and Plan 9 crash during boot. This problem does not appear with a smaller paqdisk. I don't have a Plan 9 system or a bitsy at hand but I remember running into this. The hard coded partition definition is fparts in /sys/src/9/boot/paq.c. The ramdisk partition is defined to be 4 MB although the various documents imply it should be 6 MB. I recall simply changing the ramdisk entry to, add ramdisk0x020 0x080, allowed me to use larger images. Hope this helps, eoghan
Re: [9fans] bitsy anyone?
add ramdisk0x020 0x080, I believe the command in question is: partition define ramdisk 0x20 0x60 0 I had changed it to 0x80 too, but still got the kernel panic... I'll take a look in paq.c and see if I can fix the hard-coded sizes. Thanks!! -Ben -Original Message- From: [EMAIL PROTECTED] on behalf of Eoghan Sherry Sent: Tue 10/21/2008 2:09 PM To: Fans of the OS Plan 9 from Bell Labs Subject: Re: [9fans] bitsy anyone? However, I had some problems when uploading the paqdisk on the iPaq when the image file is larger than 4 MB. The image seems to be corrupted during the upload on the iPaq and Plan 9 crash during boot. This problem does not appear with a smaller paqdisk. I don't have a Plan 9 system or a bitsy at hand but I remember running into this. The hard coded partition definition is fparts in /sys/src/9/boot/paq.c. The ramdisk partition is defined to be 4 MB although the various documents imply it should be 6 MB. I recall simply changing the ramdisk entry to, add ramdisk0x020 0x080, allowed me to use larger images. Hope this helps, eoghan winmail.dat
Re: [9fans] bitsy anyone?
2008/10/21 Benjamin Huntsman [EMAIL PROTECTED]: add ramdisk0x020 0x080, I believe the command in question is: partition define ramdisk 0x20 0x60 0 I had changed it to 0x80 too, but still got the kernel panic... I'll take a look in paq.c and see if I can fix the hard-coded sizes. The boot loader command, partition define ramdisk 0x20 0x60 0 is correct. The change is to paq.c. The boot loader uses start+size while Plan 9 uses [start,end) to define partitions. The instructions on the wiki describe a 6 MB ramdisk starting 2 MB into the flash. To the boot loader that is 0x20+0x60 but to Plan 9 it is [0x20,0x80). The problem is paq.c defines a [0x20,0x60) ramdisk which is only 4 MB in size. Comparing the values in paq.c with those on the wiki should make things clear. eoghan
