44.html - few minor typos
(I reported these on www@ but they don't seem to have been picked up.) rtadvd(8) now revoces it's privileges and runs as it's own user _rtadvd. --- Should be revokes its ... and runs as its own scsi(4) probing makes better use of the TEST UNIT READY command to clear errors and allow successfull attachments. --- That should be successful Thanks to everyone concerned for the work on 4.4, off to order now!
Re: make update stores twice the packages
Hi Ben Calvert, Ben Calvert wrote: On Aug 28, 2008, at 1:36 PM, Stuart Henderson wrote: I don't think they are links, they are real copies. I am checking this with konqueror as su and it show clearly when the file is a link or a real file. That's not a good way to check. Try ls(1). It's likely that he doesn't know the difference between a soft and hard link. I'm very busy so I am not currently checking my threads, till next week t least. But I have just accidentally read your (this) posting. I am quickly learning more about soft and hard links, and there is a thread at kde-dev to create a patch for konqueror (+ kdedirstats + other KDE tools) to avoid confusing people when dealing with files hard linked to different folders (as crazily OpenBSD does in the /usr/ports/packages folder ), which happened to me causing an erroneously information about my system space getting eaten by ghost duplicated files. mac - you need a basic unix book. for now, read man ln man ln on my night sleep table, as some unix pdf books I found online as Introduction to Unix 1998 by Frank G. Fiamingo and Unix for Dummies - 2004 - Wiley Publishing Any advice here? Mac.
Re: make update stores twice the packages
On Sat, 06 Sep 2008 02:42:59 -0600, macintoshzoom wrote: Any advice here? Yep. Make sure brain is engaged before putting mouth in gear. For somebody who obviously doesn't know very much you're a quite offensive little prick. And in so much of a hurry you can't take the advice given by experts. Accusing OpenBSD developers of acting crazily is pretty stupid really. They know what they are doing and you don't have a clue. You have (I assume) two ears, two eyes and only one mouth (for which your keyboard is a proxy): Try using them in something like the proportion in which they exist. Don't bother replying. Your messages are routed to /dev/null. Rod/ In the beginning was The Word and The Word was Content-type: text/plain The Word of Rod.
OpenBSD WiFi tutorial
Hi, Is there a simple tutorial or howto on setting up wireless for OpenBSD? Especially setting up OpenBSD as a WiFi hub? thanks Siju
Re: OpenBSD WiFi tutorial
On Sat, 6 Sep 2008 17:59:00 +0530 Siju George [EMAIL PROTECTED] wrote: Hi, Is there a simple tutorial or howto on setting up wireless for OpenBSD? Especially setting up OpenBSD as a WiFi hub? There is even better: manpages. man ifconfig man insert your device name here: ral, iwi... Eric.
Re : Formating errors on XkbBell man page [from [EMAIL PROTECTED]
Hi,
After having spend some time reading man (1) code, the following
proposal
comes :
Create a keyword for man.conf (5) - _ibuild for example - for lines
like : ``_ibuild - a letter - - associated command -''
The letter
would appear on the first line of the manpage file and
would be separated from
the leading ``{.,'}\'' by white spaces and single.
man (1) would accept both
(in fact, it would go to the first blank character
and start from there). This
would be triggered only in case of a
.[1-9n]{,[a-z]}{,.{gz,Z}} extension. man
(1) would insert the command
given by the ``_ibuild'' line right before the ``
{,|} /usr/bin/nroff -man'',
removing the trailing ``%s'' as needed.
Triggering
the in-file inquiry would be more easily implemented as
a config file setting
- a ``_iext (extension list)'' line -
As an additionnal possibility, why not
allow skipping in-file inquiry
for some directories - those in ``base'' mostly
- using an ``_iskip''
keyword in man.conf (5).
Suggestions ?
Personnaly I find
it a bit intrusive for man.conf (5).
Cheers.
Re: 44.html - few minor typos
On Sat, Sep 06, 2008 at 07:05:02PM +1200, Richard Toohey wrote: (I reported these on www@ but they don't seem to have been picked up.) rtadvd(8) now revoces it's privileges and runs as it's own user _rtadvd. --- Should be revokes its ... and runs as its own scsi(4) probing makes better use of the TEST UNIT READY command to clear errors and allow successfull attachments. --- That should be successful Thanks to everyone concerned for the work on 4.4, off to order now! all fixed now. thanks for the mail, jmc
Re: Re : Formating errors on XkbBell man page [from [EMAIL PROTECTED]
On Sat, Sep 06, 2008 at 12:37:49PM +, hyjial wrote:
Hi,
After having spend some time reading man (1) code, the following
proposal comes :
i think you will find you have a better chance of things getting
accepted if you submit a diff.
if you can;t code, like me, there's not much point submitting
descriptions of how to do stuff. probably lots of developers could do
this, if they wanted, and had the time, motivation, etc.
marc espie told me the escape sequence stuff comes from linux (or gnu,
or whatever), so you could start by looking there to see how it's done.
jmc
Create a keyword for man.conf (5) - _ibuild for example - for lines
like : ``_ibuild - a letter - - associated command -''
The letter would appear on the first line of the manpage file and
would be separated from the leading ``{.,'}\'' by white spaces and single.
man (1) would accept both (in fact, it would go to the first blank character
and start from there). This would be triggered only in case of a
.[1-9n]{,[a-z]}{,.{gz,Z}} extension. man (1) would insert the command
given by the ``_ibuild'' line right before the `` {,|} /usr/bin/nroff -man'',
removing the trailing ``%s'' as needed.
Triggering the in-file inquiry would be more easily implemented as
a config file setting - a ``_iext (extension list)'' line -
As an additionnal possibility, why not allow skipping in-file inquiry
for some directories - those in ``base'' mostly - using an ``_iskip''
keyword in man.conf (5).
Suggestions ?
Personnaly I find it a bit intrusive for man.conf (5).
Cheers.
ntpd can hang on boot
I stupidly screwed up my pf.conf, as a result ntpd -s which is invoked in /etc/rc (as a result of my /etc/rc.conf.local) could not resolve the names of the time servers. ntpd hangs and cannot be interrupted. The only way to continue is to do a hardware reset. I realize that it was my mistake but most of the other processes started by /etc/rc can be interrupted. I really do not like doing hardware resets. As an aside, it was on my firewall. My firewall makes use of my dns which is on the inside of my network, but during the booting process the pf.conf cannot refer to a dns name that are define on the outside. The startup pf.conf built into /etc/rc allows dns requests originating from machine being booted only. For an external name, my dns has to pass a request though the firewall to the outside dns server. That cannot be done until the system is fully booted, The solutions are: 1) don't use any external dns names in your pf.conf 2) have three stage bootstrap of pf, First stage, the code in /etc/rc Second stage, /etc/rc.conf.local has pf.conf to allow the inside nameservers to pass though Third stage, /etc/rc.local has code to set the final pf.conf file 3) put all external dns names in tables that have their contents defined in /etc/rc.local (this is the one I currently use) 4) Modify /etc/rc to allow pass through of dns requests. The ones that should be allowed pass though would be the nameservers defined in /etc/resolv.conf (this is what I would like)
Re: OpenBSD WiFi tutorial
--- Siju George [EMAIL PROTECTED] wrote: Hi, Is there a simple tutorial or howto on setting up wireless for OpenBSD? http://home.nuug.no/~peter/pf/en/wireless.simple.html Especially setting up OpenBSD as a WiFi hub? WiFi hub ? thanks Siju --- Therefore, if anyone is in Christ, he is a new creation; the old has gone, the new has come! - 2 Corinthians 5:17 (NIV) --- Francisco Valladolid Hdez. http://blog.bsdguy.net - http://flickr.com/photos/sigueme/
Re: Can OpenBSD run in 24 MB of RAM?
On Wed, Sep 3, 2008 at 10:00 PM, [EMAIL PROTECTED] wrote: I've searched the FAQ and the Web for any guidance on what the minimum RAM is for OpenBSD, with and without X. I just acquired a Compaq Armada 1125 laptop that maxes out at 24 MB of RAM, and I'm wondering whether or not it's feasible to run OpenBSD on it. My router for several years was an IBM PS/2E, model 9533 with a 50MHz 486 SLC2 + 25MHz 387SX FPU(not a typo) and 16MB RAM. I haven't run anything newer than about 3.8 or 3.9 on it, but it worked fine then, including the install. I'm sure I've posted in more detail about it before -- check the archives. Heck, I even ran X on it as a see if it works thing, but it wasn't good for anything more than opening a couple xterms. The reason I abandoned it is that when faster connections became available, the CPU couldn't keep up. It would only pass about 2Mbit of traffic before the interrupts from the ethernet cards (16-bit PCMCIA, essentially ISA) consumed 90% CPU.
Re: ntpd can hang on boot
On Sep 06 13:08:33, Peter Fraser wrote: ntpd hangs and cannot be interrupted. The only way to continue is to do a hardware reset. Doesn't it time out eventually? As an aside, it was on my firewall. My firewall makes use of my dns which is on the inside of my network, but during the booting process the pf.conf cannot refer to a dns name that are define on the outside. Use IP addresses in pf.conf, not names. The startup pf.conf built into /etc/rc There is no startup pf.conf built into /etc/rc allows dns requests originating from machine being booted only. The default is to NOT run pf at all, so it allows everything. For an external name, my dns has to pass a request though the firewall to the outside dns server. That cannot be done until the system is fully booted, Whether the system is the inside dns client or the firewall, this is not necessarily true. As soon as the firewall routes packets and does NAT correctly, inside machine can use it as a gateway (while other processes are still starting on the firewall). If I read /etc/rc right, pf is already running when booting gets to ntpd. The solutions are: 1) don't use any external dns names in your pf.conf Don't use ANY names in pf.conf 2) have three stage bootstrap of pf, First stage, the code in /etc/rc Second stage, /etc/rc.conf.local has pf.conf to allow the inside nameservers to pass though Third stage, /etc/rc.local has code to set the final pf.conf file No. Set pf.conf to do what you want, allow pf in rc.conf.local, and let /etc/rc do the rest as it's supposed to. 3) put all external dns names in tables that have their contents defined in /etc/rc.local (this is the one I currently use) That is, duplicate external DNS information locally? No. 4) Modify /etc/rc Whoa, stop right here! to allow pass through of dns requests. The ones that should be allowed pass though would be the nameservers defined in /etc/resolv.conf (this is what I would like) Setting up your firewall happens in pf.conf, NOT in /etc/rc. You should never touch /etc/rc. Jan (You _have_ read man rc, right?)
Re: ntpd can hang on boot
The time out for ntpd is definitely more that 10 minutes. I didn't wait any
longer.
The text of the startup pf.conf in /etc/rc is
RULES=block all
RULES=$RULES\npass on lo0
RULES=$RULES\npass in proto tcp from any to any port 22 keep state
RULES=$RULES\npass out proto { tcp, udp } from any to any port 53
keep state
RULES=$RULES\npass out inet proto icmp all icmp-type echoreq keep
state
if ifconfig lo0 inet6 /dev/null 21; then
RULES=$RULES\npass out inet6 proto icmp6 all icmp6-type
neighbrsol
RULES=$RULES\npass in inet6 proto icmp6 all icmp6-type
neighbradv
RULES=$RULES\npass out inet6 proto icmp6 all icmp6-type
routersol
RULES=$RULES\npass in inet6 proto icmp6 all icmp6-type
routeradv
fi
RULES=$RULES\npass proto carp
case `sysctl vfs.mounts.nfs 2/dev/null` in
*[1-9]*)
# don't kill NFS
RULES=scrub in all no-df\n$RULES
RULES=$RULES\npass in proto { tcp, udp } from any port { 111,
2049 } to any
RULES=$RULES\npass out proto { tcp, udp } from any to any
port { 111, 2049 }
;;
esac
echo $RULES | pfctl -f -
pfctl -e
Ok, I admit I had
pf=Yes
in my /etc/rc.conf.local
The rest of your comment are based on the believe that /etc/rc does not have
A startup pf.conf.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jan
Stary
Sent: Saturday, September 06, 2008 2:51 PM
To: Peter Fraser
Cc: misc@openbsd.org
Subject: Re: ntpd can hang on boot
On Sep 06 13:08:33, Peter Fraser wrote:
ntpd hangs and cannot be interrupted. The only way to continue is to do a
hardware reset.
Doesn't it time out eventually?
As an aside, it was on my firewall. My firewall makes use of my dns which
is
on the inside of my network, but during the booting process the pf.conf
cannot
refer to a dns name that are define on the outside.
Use IP addresses in pf.conf, not names.
The startup pf.conf built into /etc/rc
There is no startup pf.conf built into /etc/rc
allows dns requests originating from machine being booted only.
The default is to NOT run pf at all, so it allows everything.
For an external name, my dns has to pass a request though the firewall to
the
outside dns server. That cannot be done until the system is fully booted,
Whether the system is the inside dns client or the firewall, this is not
necessarily true. As soon as the firewall routes packets and does NAT
correctly, inside machine can use it as a gateway (while other
processes are still starting on the firewall).
If I read /etc/rc right, pf is already running when booting gets to ntpd.
The solutions are:
1) don't use any external dns names in your pf.conf
Don't use ANY names in pf.conf
2) have three stage bootstrap of pf,
First stage, the code in /etc/rc
Second stage, /etc/rc.conf.local has pf.conf to allow the inside
nameservers to pass though
Third stage, /etc/rc.local has code to set the final pf.conf file
No. Set pf.conf to do what you want, allow pf in rc.conf.local,
and let /etc/rc do the rest as it's supposed to.
3) put all external dns names in tables that have their contents
defined in /etc/rc.local (this is the one I currently use)
That is, duplicate external DNS information locally? No.
4) Modify /etc/rc
Whoa, stop right here!
to allow pass through of dns requests.
The ones that should be allowed pass though would be the nameservers
defined in /etc/resolv.conf (this is what I would like)
Setting up your firewall happens in pf.conf, NOT in /etc/rc.
You should never touch /etc/rc.
Jan
(You _have_ read man rc, right?)
NYCBSDCon 2008 Registration Open
We are proud to announce the release of the speaker's presentations and that registration is now open for NYCBSDCon 2008 at http://www.nycbsdcon.org NYCBSDCon 2008 will be held at Manhattan's Columbia University on October 11 and 12 in New York City. The speaker line-up is an impressive list of developers and systems administrators from all the BSD projects. http://www.nycbsdcon.org/2008/presentations.html We strongly encourage everyone to register as soon as possible at: http://www.nycbsdcon.org/2008/register.html Early registration is $95, and includes not just the meetings, but also breakfast and lunch for both Saturday and Sunday. Walk-ins will be charged $145. With valid current identification, the Columbia University staff, students and faculty rate is $50. Other full-time students can also receive this discounted rate with valid identification. On Friday, October 10th, there will be a NetBSD developers summit. Please contact JSchauma@ that project for additional details. FreeBSD developers will also be gathering outside of the conference. Please contact GNN@ that project for more details. Friday evening, attendees will be gathering at Havanna Central at 2911 Broadway between 113th and 114th streets beginning at 7 pm. The BSD Certification Group will be holding BSDA exams. There will be general Unix review cram sessions over the course of Saturday. There will also be a social gathering on Saturday evening at Havanna Central at 7 pm. Live on-site reporting of the conference happenings will be provided by BSDTalk's Will Backman. Huge thanks are due to our sponsors for keeping the conference inexpensive and accessible. Current sponsors include New York Internet, DataPipe, Everest Broadband, Datagram, USENIX, iXSystems, Pearson Education and our small business sponsors Loftmail and PC Engines. And finally, thanks to our many media sponsors, who have provided support and publicity for the conference, including Columbia University's Network Security Lab, the BSD Certification Group, BSD Magazine, New York PHP, the Industrial Technology and Assistance Corporation and Gruppo Udenti FreeBSD Italia. Without the assistance of Columbia University's Angelos Keromytis and Matthew Burnside, the conference would not be possible. Any conference profits will be donated to the BSD projects, as done in years past.
Re: OpenBSD WiFi tutorial
On Sun, 7 Sep 2008, Eric Faurot wrote: There is even better: manpages. man ifconfig man insert your device name here: ral, iwi... It looks like the AR5424 is not supported: # dmesg |grep OpenBSD OpenBSD 4.4-current (GENERIC.MP) #1829: Thu Sep 4 14:55:31 MDT 2008 # dmesg |grep ath ath0 at pci2 dev 0 function 0 Atheros AR5424 rev 0x01: apic 1 int 17 (irq 11) ath0: AR5424 10.3 phy 6.1 rf 10.2, WOR5_ETSIC, address 00:1f:5b:40:2f:61 The Atheros' site's technical information is neither. Event the product bulletin is just a sales brochure. Should I begin yammering at Atheros directly or a re-seller? Which data is needed? Regards, -Lars
Re: OpenBSD WiFi tutorial
http://marc.info/?l=openbsd-miscm=119611252029773w=2 2008/9/6 Lars D. Nooden [EMAIL PROTECTED]: On Sun, 7 Sep 2008, Eric Faurot wrote: There is even better: manpages. man ifconfig man insert your device name here: ral, iwi... It looks like the AR5424 is not supported: # dmesg |grep OpenBSD OpenBSD 4.4-current (GENERIC.MP) #1829: Thu Sep 4 14:55:31 MDT 2008 # dmesg |grep ath ath0 at pci2 dev 0 function 0 Atheros AR5424 rev 0x01: apic 1 int 17 (irq 11) ath0: AR5424 10.3 phy 6.1 rf 10.2, WOR5_ETSIC, address 00:1f:5b:40:2f:61 The Atheros' site's technical information is neither. Event the product bulletin is just a sales brochure. Should I begin yammering at Atheros directly or a re-seller? Which data is needed? Regards, -Lars
Re: ntpd can hang on boot
On Sat, Sep 6, 2008 at 3:48 PM, Peter Fraser [EMAIL PROTECTED] wrote:
The time out for ntpd is definitely more that 10 minutes. I didn't wait any
longer.
The text of the startup pf.conf in /etc/rc is
RULES=block all
RULES=$RULES\npass on lo0
RULES=$RULES\npass in proto tcp from any to any port 22 keep state
RULES=$RULES\npass out proto { tcp, udp } from any to any port 53
keep state
RULES=$RULES\npass out inet proto icmp all icmp-type echoreq keep
state
if ifconfig lo0 inet6 /dev/null 21; then
RULES=$RULES\npass out inet6 proto icmp6 all icmp6-type
neighbrsol
RULES=$RULES\npass in inet6 proto icmp6 all icmp6-type
neighbradv
RULES=$RULES\npass out inet6 proto icmp6 all icmp6-type
routersol
RULES=$RULES\npass in inet6 proto icmp6 all icmp6-type
routeradv
fi
RULES=$RULES\npass proto carp
case `sysctl vfs.mounts.nfs 2/dev/null` in
*[1-9]*)
# don't kill NFS
RULES=scrub in all no-df\n$RULES
RULES=$RULES\npass in proto { tcp, udp } from any port { 111,
2049 } to any
RULES=$RULES\npass out proto { tcp, udp } from any to any
port { 111, 2049 }
;;
esac
echo $RULES | pfctl -f -
pfctl -e
Ok, I admit I had
pf=Yes
in my /etc/rc.conf.local
The rest of your comment are based on the believe that /etc/rc does not have
A startup pf.conf.
Did you read the rest of /etc/rc? Your local pf.conf is still loaded
before ntpd is kicked off.
--david
Re: ntpd can hang on boot
I had an error in my /etc/pf.conf, that stopped the dns requests from working
Which in turn stopped ntpd from resolving the server names in /etc/ntpd.conf
which in turn caused ntdp to hang the system.
The fix for the problem was to correct my /etc/pf.conf file. My objection
was that I had to do a hardware reset in order to boot in single
user mode to fix the problem. Most other things you screw don't
require a hardware reset.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
David Higgs
Sent: Saturday, September 06, 2008 5:02 PM
To: Peter Fraser
Cc: misc@openbsd.org
Subject: Re: ntpd can hang on boot
On Sat, Sep 6, 2008 at 3:48 PM, Peter Fraser [EMAIL PROTECTED] wrote:
The time out for ntpd is definitely more that 10 minutes. I didn't wait any
longer.
The text of the startup pf.conf in /etc/rc is
RULES=block all
RULES=$RULES\npass on lo0
RULES=$RULES\npass in proto tcp from any to any port 22 keep state
RULES=$RULES\npass out proto { tcp, udp } from any to any port 53
keep state
RULES=$RULES\npass out inet proto icmp all icmp-type echoreq keep
state
if ifconfig lo0 inet6 /dev/null 21; then
RULES=$RULES\npass out inet6 proto icmp6 all icmp6-type
neighbrsol
RULES=$RULES\npass in inet6 proto icmp6 all icmp6-type
neighbradv
RULES=$RULES\npass out inet6 proto icmp6 all icmp6-type
routersol
RULES=$RULES\npass in inet6 proto icmp6 all icmp6-type
routeradv
fi
RULES=$RULES\npass proto carp
case `sysctl vfs.mounts.nfs 2/dev/null` in
*[1-9]*)
# don't kill NFS
RULES=scrub in all no-df\n$RULES
RULES=$RULES\npass in proto { tcp, udp } from any port {
111,
2049 } to any
RULES=$RULES\npass out proto { tcp, udp } from any to any
port { 111, 2049 }
;;
esac
echo $RULES | pfctl -f -
pfctl -e
Ok, I admit I had
pf=Yes
in my /etc/rc.conf.local
The rest of your comment are based on the believe that /etc/rc does not
have
A startup pf.conf.
Did you read the rest of /etc/rc? Your local pf.conf is still loaded
before ntpd is kicked off.
--david
Re: ntpd can hang on boot
On Sat, Sep 6, 2008 at 10:08 AM, Peter Fraser [EMAIL PROTECTED] wrote: I stupidly screwed up my pf.conf, as a result ntpd -s which is invoked in /etc/rc (as a result of my /etc/rc.conf.local) could not resolve the names of the time servers. ntpd hangs and cannot be interrupted. The only way to continue is to do a hardware reset. I realize that it was my mistake but most of the other processes started by /etc/rc can be interrupted. I really do not like doing hardware resets. Hardware reset? Didn't ^\ (the default 'quit' setting) work? Yeah, it makes ntpd dump core, but it's certainly interrupted it when I've had issues with ntpd -s in the past. Philip Guenther
Re: ntpd can hang on boot
Peter Fraser wrote: I stupidly screwed up my pf.conf, as a result ntpd -s which is invoked in /etc/rc (as a result of my /etc/rc.conf.local) could not resolve the names of the time servers. What version? http://kerneltrap.org/mailarchive/openbsd-misc/2007/11/16/420560
Wireless
Hello Does somebody know a link or book, related to firmware, chips: Broadcom 4311, DWL-122, and RTL-8187? I have 1 Broadcom wireless card that is recognized by OpenBSD 4.3 as bwi0, but it needs a firmware; 1 DLink DWL-122, recognized as wi0, but it doesn't work always well; and 1 rtl-8187 wich is not recognized by the system. The point is that i do instalation by the wireless way. thanks in advance. -- OpenBSD [EMAIL PROTECTED]
Re: Stop in line 888 of Makefile
ln /bsd /obsd worked after changing to noschg and rebuilding under securelevel -1. * * The most dangerous man, to any government, is the man who is able to think things out for himself, without regard to the prevailing superstitions and taboos. --Mencken --- On Thu, 9/4/08, Doug Milam [EMAIL PROTECTED] wrote: From: Doug Milam [EMAIL PROTECTED] Subject: Re: Stop in line 888 of Makefile To: Misc OpenBSD misc@openbsd.org Date: Thursday, September 4, 2008, 8:09 PM It does not, no Doug Milam wrote: ln: /obsd: Operation not permitted *** Error code 1 Stop in /usr/src/sys/arch/i386/compile/GENERIC (line 888 of Makefile). --running as root Does make install work when run outside of your script? Tom
Re: OpenBSD WiFi tutorial
Hello Lars, From [EMAIL PROTECTED] Sat Sep 6 22:43:40 2008 From: Lars D. Nooden [EMAIL PROTECTED] To: Eric Faurot [EMAIL PROTECTED] cc: Siju George [EMAIL PROTECTED], misc misc@openbsd.org Subject: Re: OpenBSD WiFi tutorial On Sun, 7 Sep 2008, Eric Faurot wrote: There is even better: manpages. man ifconfig man insert your device name here: ral, iwi... It looks like the AR5424 is not supported: I have an Atheros AR5424, and it works fine for wireless in -current. I would expect it to work for Host AP mode as well, though I have never tried it. Aaron
Re: dvorak keyboard not working still!
[demime could not interpret encoding - treating as plain text] Thanks. Now I realize: I misunderstood how this works. On Fri, 05 Sep 2008 21:43:58 -0700 Ted Unangst [EMAIL PROTECTED] wrote: The man pages for the computer you're connecting from. There are no keyboard settings for connections that don't have keyboards.
