Re: Here's a trivial question. . .
On Jun 12, 2008, at 2:43 AM, Martin Toft wrote: On Thu, Jun 12, 2008 at 02:29:41AM -0700, Sean Kamath wrote: Why is sendmail in /usr/src/gnu/usr.sbin? sendmail is patently not a GNU application, and has a modified Berkeley license? Just askin'. Sean http://marc.info/?l=openbsd-miscm=101014364523299w=2 Apologies. I have no idea how I missed that in the archives. Maybe my google-fu is weak. gnu == encumbered. I get it. Sean
Re: captivating window manager
I'm moving from dwm to cwm. I think I've never felt so comfortable with a WM, I'm very happy it's in base and I join you to thank the devs. Thanks ! Igor Zinovik [EMAIL PROTECTED] writes: Hello. Yesterday i upgraded my X and now i'm playing with new tool called cwm. I like to thank (thank you, thank you, thank you) Owain Ainsorth, Okan Demirmen and all other who brought this brilliant tool to the base! Definitely it is a fastest window manager i ever used. Very comfortable and keyboard oriented. A bit strange (no window titles), now i have to modify my shell prompt to see what machine i use, but it worth it. Bye, bye Openbox, you lacked `exec' feature. You served well, but i do not need you anymore, because there is captivating window manager in base!!! # pkg_delete openbox
Re: Let go IPv6
Paul de Weerd wrote: If your ISP doesn't offer IPv6 connectivity, be sure to ask them. And don't let them just reply a canned response... Make sure to at least put it on their radar. I changed service plans somewhat recently and posed the IPv6 support question as part of the negotiation. Sure it was play acting, but it got them quite interested. Their first response was what's that, the second response was no one uses it. So I pointed to a long list of governments requiring IPv6 and also pointed to a parallel (but not quite competing) network that already had full IPv6 support. That lead to their third response of being very interested. They actually even got back to me later with more info. It also opened an opportunity to highlight (to the three sales kids) the importance of working with modern operating systems, of which one of the examples I named was OpenBSD, rather than the electronic ebola most have encountered. It was probably the capabilities of the modern systems that got them personally interested in answering the question. regards -Lars
pf.conf comment lines
Hi, I am running OpenBSD 4.3 STABLE in an i386 machine. The man page for pf.conf says at some point: Any lines beginning with a # are treated as comments and ignored. Now, if a comment line ends with \, should the next line be also treated as comment? I noticed this behaviour and I do not know whether or not it should work like that. Many times, when we are trying to test a different setup, we duplicate a line, change something, and comment out the original line. Thanks in advance. Regards, Jose -- See Exclusive Videos: 10th Annual Young Hollywood Awards http://www.hollywoodlife.net/younghollywoodawards2008/
gnupg to add LDAP - how?
I have gnupg-1.4.8, and KDE KGpg, but no LDAP server support. It seems that this gnupg has an LDAP flavor, which I miss somehow to install. Should I have to uninstall and reinstall gnupg-1.4.8 from the command line to enable this flavor (a bit of a pain as it is binded with KDE etc), or is there an easier trick for this? I want to import to my keyring some public keys available at a private LDAP server ( ldap://keys.hush.com:389; ). Thanks.
Re: pf.conf comment lines
Jose Fragoso wrote: Now, if a comment line ends with \, should the next line be also treated as comment? I noticed this behaviour and I do not know whether or not it should work like that. Interesting. Good to know that. In a small rule set it's easy to notice, though. I'm able to duplicate the behavior on 4.3 GENERIC#698 i386: comment lines ending with backslash *are* including the subsequent line(s) as part of the comment. Regards, -Lars
Re: pf.conf comment lines
Louis V. Lambrecht wrote: rem the backslash is used as an escape character in shell world. Yes, that's quite familiar and I use it a lot, both for long lines and for escaping special characters (quotes, etc). What is new use to me is that the comment lines can be affected. I simply hadn't tried it. However, when it is explained that way, as an escape character, it makes sense: the newline character following the backslash is escaped. -Lars
Re: cwm keybindings misbehavior
Alexander Polakov wrote: * Predrag Punosevac [EMAIL PROTECTED] [080613 11:53]: Okan Demirmen wrote: On Thu 2008.06.12 at 11:28 -0700, Predrag Punosevac wrote: Daniel B. wrote: Hi, I can't get the response desired to some of the default keybindings in cwm. Some of them: M-/, C-/, M-?. With the first and the third, I just hear a beep (or a Wuff!! in screen). The second delete my window if not in screen, or just Wuff!! in screen. Any hints? Thank you. can we see your .cwmrc? I would try to arise ~/.cwmrc from your home directory. The another thing is that you should carefully read man pages for cwm and make sure you understand the meaning of M (meta key). Meta key is different on different keyboards. So I do not know what is meta key on your key board but on mine IBM (M type) it is ALT. I like CWM very, very much but I didn't ditch the OpenBox just because I thing that CWM is rapidly changing and the configuration process is not 100% bullet proof. Namely if you go to web-site CWM you will see that configuration is very different than of the one in the base of OpenBSD. So obviously it has been modified by OpenBSD developers. I must however say that CWM looks impressive to me and I hope they fix few issues and maybe introduce few new features which would probably make it one of the best WM around. yes, our cwm is now very different. can you elaborate on the few issues? there are a few, but i'm sure you can help by informing us of issues we are not yet aware ;) Disclaimer: I played with CWM little bit so my statements should not be taken too seriously. I personally had hard time trying to configure CWM to lunch applications. In another words according to documentation on CWM web site one needs to edit ~/.calmwm but OpenBSD man pages say that ~/.cwmrc is correct file to edit. Even after the editing ~/.cwmrc I could not open the menu with the right button on the mouse which according to CWM web-site should list the applications. That was on OpenBSD 4.2 release. I have not pursue the issue seriously as according to discussion on misc about WM from about 2-3 months ago CWM is in development. The only thing that I personally miss in CWM are virtual desktops. I DO know that if people start saying things like that and developers start listening the CWM will soon become bloated. I do not wish that. CWM is one of the best because it is minimalistic and gets job done. It is also great thing that is in the base. Bloated? What are you talking about? dwm [1] is less that 2000 LOC and it has virtual desktops, various tiling alghorithms, nice panel, window matching and what not. [1] http://dwm.suckless.org We were not even talking about dynamic window manager dwm. We were talking about CWM which is in the base. Those are two different things. Have you ever tried dwm? Do you know that when you try to use full screen mode in Xpdf on dwm the Xpdf will be unable to find it because of the way dwm is coded. Have you tried panel for dwm? Please do and then lets talk about it. I like dwm but it is not for everyone. One of the reasons I said what I said above about CWM is that I would like to see CWM remaining as minimal as possible which in practical terms means competing with DWM which is the king of minimal. Best, Predrag Punosevac OKO
Re: pf.conf comment lines
On Fri, Jun 13, 2008 at 04:52:45PM +0300, Lars Noodin wrote: Louis V. Lambrecht wrote: rem the backslash is used as an escape character in shell world. Yes, that's quite familiar and I use it a lot, both for long lines and for escaping special characters (quotes, etc). What is new use to me is that the comment lines can be affected. I simply hadn't tried it. However, when it is explained that way, as an escape character, it makes sense: the newline character following the backslash is escaped. It can be surprising (in a bad way) either way it works, and has some benefits either way as well. This \ that \ other Can be commented like # This \ that \ other But then there's the common idiom of commenting something out and putting in the replacement: # This \ Thus \ that \ other The above has much different behavior depending on whether comments are evaluated before the EOL escape. Which way is correct? Which will trip up more people in every day situations? -- Darrin Chandler| Phoenix BSD User Group | MetaBUG [EMAIL PROTECTED] | http://phxbug.org/ | http://metabug.org/ http://www.stilyagin.com/ | Daemons in the Desert | Global BUG Federation
Re: cwm keybindings misbehavior
On Thu, Jun 12, 2008 at 08:44:56PM +0200, Pierre Riteau wrote: On Thu, Jun 12, 2008 at 01:13:05PM -0300, Daniel B. wrote: Hi, I can't get the response desired to some of the default keybindings in cwm. Some of them: M-/, C-/, M-?. With the first and the third, I just hear a beep (or a Wuff!! in screen). The second delete my window if not in screen, or just Wuff!! in screen. Any hints? Thank you. non-US keyboard layout? I use dvorak, its not language based, but the keys differ. And cwm works like a charm for me ever since it was imported in the tree. -- [EMAIL PROTECTED] SDF Public Access UNIX System - http://sdf.lonestar.org
Re: pf.conf comment lines
Ooops! Lars answered to my mail. Means, I hadn't replied to misc@ but the lazy in me just replied. Louis V. Lambrecht wrote: Lars NoodC)n wrote: Jose Fragoso wrote: Now, if a comment line ends with \, should the next line be also treated as comment? I noticed this behaviour and I do not know whether or not it should work like that. Interesting. Good to know that. In a small rule set it's easy to notice, though. I'm able to duplicate the behavior on 4.3 GENERIC#698 i386: comment lines ending with backslash *are* including the subsequent line(s) as part of the comment. Regards, -Lars rem the backslash is used as an escape character in shell world. Must be the very last character (before the new line). You might test this echo Hello hworld echo world! hworld cat hworld Hello world! tr '\ ' ' ' hworld hworldsep cat hworldsep Hello world!
Realtek 8185 wireless
Hi, I just bought Realtek 8185 which won't work. I found some mailinglist threads about it not being supported [1]. My question is: will they ever be or shall I just get a replacement? [1] http://marc.info/?l=openbsd-miscm=121167375211277w=2 -- Antti Harri
Re: pf.conf comment lines
Darrin Chandler wrote: # This \ Thus \ that \ other Clearly this is the intuitive way that should work, since all other languages I know of parse like this. If you want to disable multiple lines you have to comment them all out. Use a decent editor if you think that is much of a hassle. # Han
Re: cwm keybindings misbehavior
Alexander Polakov wrote: * Predrag Punosevac [EMAIL PROTECTED] [080613 18:19]: Alexander Polakov wrote: * Predrag Punosevac [EMAIL PROTECTED] [080613 11:53]: Okan Demirmen wrote: On Thu 2008.06.12 at 11:28 -0700, Predrag Punosevac wrote: Daniel B. wrote: Hi, I can't get the response desired to some of the default keybindings in cwm. Some of them: M-/, C-/, M-?. With the first and the third, I just hear a beep (or a Wuff!! in screen). The second delete my window if not in screen, or just Wuff!! in screen. Any hints? Thank you. can we see your .cwmrc? I would try to arise ~/.cwmrc from your home directory. The another thing is that you should carefully read man pages for cwm and make sure you understand the meaning of M (meta key). Meta key is different on different keyboards. So I do not know what is meta key on your key board but on mine IBM (M type) it is ALT. I like CWM very, very much but I didn't ditch the OpenBox just because I thing that CWM is rapidly changing and the configuration process is not 100% bullet proof. Namely if you go to web-site CWM you will see that configuration is very different than of the one in the base of OpenBSD. So obviously it has been modified by OpenBSD developers. I must however say that CWM looks impressive to me and I hope they fix few issues and maybe introduce few new features which would probably make it one of the best WM around. yes, our cwm is now very different. can you elaborate on the few issues? there are a few, but i'm sure you can help by informing us of issues we are not yet aware ;) Disclaimer: I played with CWM little bit so my statements should not be taken too seriously. I personally had hard time trying to configure CWM to lunch applications. In another words according to documentation on CWM web site one needs to edit ~/.calmwm but OpenBSD man pages say that ~/.cwmrc is correct file to edit. Even after the editing ~/.cwmrc I could not open the menu with the right button on the mouse which according to CWM web-site should list the applications. That was on OpenBSD 4.2 release. I have not pursue the issue seriously as according to discussion on misc about WM from about 2-3 months ago CWM is in development. The only thing that I personally miss in CWM are virtual desktops. I DO know that if people start saying things like that and developers start listening the CWM will soon become bloated. I do not wish that. CWM is one of the best because it is minimalistic and gets job done. It is also great thing that is in the base. Bloated? What are you talking about? dwm [1] is less that 2000 LOC and it has virtual desktops, various tiling alghorithms, nice panel, window matching and what not. [1] http://dwm.suckless.org We were not even talking about dynamic window manager dwm. We were talking about CWM which is in the base. Those are two different things. Have you ever tried dwm? Are you joking? Of course I did. I have been using dwm since its first release. Do you know that when you try to use full screen mode in Xpdf on dwm the Xpdf will be unable to find it because of the way dwm is coded. I dunno what do you mean by full screen mode. There's 1px border around the window in fullscreen mode, you mean that by it 'being unable'? Have you tried panel for dwm? Tried? Hmmm... It just works. Please do and then lets talk about it. I like dwm but it is not for everyone. One of the reasons I said what I said above about CWM is that I would like to see CWM remaining as minimal as possible which in practical terms means competing with DWM which is the king of minimal. My point was cwm is already bigger in size but less featurish, so I can't see any way for it to be 'not bloated'. Then you have a point:-) Best, OKO
Re: Realtek 8185 wireless
I'd get a replacement and if you can afford it,... submit a hardware sample fo one of the dev's that like playing with wireless drivers. Personally I'm lucky all my hardware works (spend a fair bit of time making sure of that though) so I haven't come across something I need to submit hardware for a driver for. On Fri, Jun 13, 2008 at 4:55 PM, Antti Harri [EMAIL PROTECTED] wrote: Hi, I just bought Realtek 8185 which won't work. I found some mailinglist threads about it not being supported [1]. My question is: will they ever be or shall I just get a replacement? [1] http://marc.info/?l=openbsd-miscm=121167375211277w=2 -- Antti Harri
Re: Realtek 8185 wireless
On Fri, 13 Jun 2008, Ross Cameron wrote: I'd get a replacement and if you can afford it,... submit a hardware sample fo one of the dev's that like playing with wireless drivers. Personally I'm lucky all my hardware works (spend a fair bit of time making sure of that though) so I haven't come across something I need to submit hardware for a driver for. Usually I make sure too but this time there wasn't a selection at the store, the package didn't say what chip it had so I couldn't verify and also I thought wireless OpenBSD just works no matter what el'cheapo cards I get :-) PS. if it *had* said it was Realtek I would have gotten it anyway, I have the impression that they give away documentation quite nicely. Guess I was wrong about that. -- Antti Harri
Re: captivating window manager
On Fri, Jun 13, 2008 at 10:08:47AM +, Nicolas Legrand wrote: Igor Zinovik [EMAIL PROTECTED] writes: I'm moving from dwm to cwm. I think I've never felt so comfortable with a WM, I'm very happy it's in base and I join you to thank the devs. Thanks ! Really..? So a tilling window manager was not your thing?
Re: gnupg to add LDAP - how?
Hi, On Fri, 13.06.2008 at 06:52:00 -0600, macintoshzoom [EMAIL PROTECTED] wrote: I have gnupg-1.4.8, and KDE KGpg, but no LDAP server support. It seems that this gnupg has an LDAP flavor, which I miss somehow to install. Should I have to uninstall and reinstall gnupg-1.4.8 from the command line to enable this flavor (a bit of a pain as it is binded with KDE etc), or is there an easier trick for this? I don't use KDE and also not GnuPG together with LDAP (yet), but my reading of all of this stuff is this (take with two grains of salt): * You need to build gnupg from ports. While you are at it, make sure that you grab the 1.4.9 update. * Your KDE bindings should be completely unaffected, imho. * You might need to configure LDAP access directly in your config file, outside of KDE's tools. Kind regards, --Toni++
Re: cwm keybindings misbehavior
On Fri, Jun 13, 2008 at 08:52:16AM -0700, Predrag Punosevac wrote: Alexander Polakov wrote: * Predrag Punosevac [EMAIL PROTECTED] [080613 18:19]: Alexander Polakov wrote: * Predrag Punosevac [EMAIL PROTECTED] [080613 11:53]: Okan Demirmen wrote: On Thu 2008.06.12 at 11:28 -0700, Predrag Punosevac wrote: Daniel B. wrote: Hi, I can't get the response desired to some of the default keybindings in cwm. Some of them: M-/, C-/, M-?. With the first and the third, I just hear a beep (or a Wuff!! in screen). The second delete my window if not in screen, or just Wuff!! in screen. Any hints? Thank you. can we see your .cwmrc? I would try to arise ~/.cwmrc from your home directory. The another thing is that you should carefully read man pages for cwm and make sure you understand the meaning of M (meta key). Meta key is different on different keyboards. So I do not know what is meta key on your key board but on mine IBM (M type) it is ALT. I like CWM very, very much but I didn't ditch the OpenBox just because I thing that CWM is rapidly changing and the configuration process is not 100% bullet proof. Namely if you go to web-site CWM you will see that configuration is very different than of the one in the base of OpenBSD. So obviously it has been modified by OpenBSD developers. I must however say that CWM looks impressive to me and I hope they fix few issues and maybe introduce few new features which would probably make it one of the best WM around. yes, our cwm is now very different. can you elaborate on the few issues? there are a few, but i'm sure you can help by informing us of issues we are not yet aware ;) Disclaimer: I played with CWM little bit so my statements should not be taken too seriously. I personally had hard time trying to configure CWM to lunch applications. In another words according to documentation on CWM web site one needs to edit ~/.calmwm but OpenBSD man pages say that ~/.cwmrc is correct file to edit. Even after the editing ~/.cwmrc I could not open the menu with the right button on the mouse which according to CWM web-site should list the applications. That was on OpenBSD 4.2 release. I have not pursue the issue seriously as according to discussion on misc about WM from about 2-3 months ago CWM is in development. The only thing that I personally miss in CWM are virtual desktops. I DO know that if people start saying things like that and developers start listening the CWM will soon become bloated. I do not wish that. CWM is one of the best because it is minimalistic and gets job done. It is also great thing that is in the base. Bloated? What are you talking about? dwm [1] is less that 2000 LOC and it has virtual desktops, various tiling alghorithms, nice panel, window matching and what not. [1] http://dwm.suckless.org We were not even talking about dynamic window manager dwm. We were talking about CWM which is in the base. Those are two different things. Have you ever tried dwm? Are you joking? Of course I did. I have been using dwm since its first release. Do you know that when you try to use full screen mode in Xpdf on dwm the Xpdf will be unable to find it because of the way dwm is coded. I dunno what do you mean by full screen mode. There's 1px border around the window in fullscreen mode, you mean that by it 'being unable'? Have you tried panel for dwm? Tried? Hmmm... It just works. Please do and then lets talk about it. I like dwm but it is not for everyone. One of the reasons I said what I said above about CWM is that I would like to see CWM remaining as minimal as possible which in practical terms means competing with DWM which is the king of minimal. My point was cwm is already bigger in size but less featurish, so I can't see any way for it to be 'not bloated'. Then you have a point:-) Best, OKO Holy crap, this is bad quoting.
Re: enable uvideo(4)
http://linux-uvc.berlios.de/#footnote-4
{iSight webcams require a proprietary firmware that can't be redistributed.
Tools to extract the firmware from the MacOS X driver and load it into the
device are available at http://bersace03.free.fr/ift/.}
-Nix Fan.
Re: enable uvideo(4)
yes, not only that. reading through the linux
uvc driver i found the following comment.
---
/* Built-in iSight webcams are completely broken. They implement most
* of UVC 1.0, but the Apple engineers decided to use a completely
* different packet format, although the video data is in YUV. Were
* they on crack or just lazy ? As the hardware is 8051-based, it
* might be interesting to write an open-source firmware.
*
* Instead of sending a header at the beginning of each isochronous
* transfer payload, the webcam sends a single header per image (on
* its own in a packet), followed by packets containing data only.
---
http://svn.berlios.de/svnroot/repos/linux-uvc/linux-uvc/trunk/
so, i guess, isight wont be one of the goals for uvideo(4).
sorry for the noise...
Unix Fan schrieb:
http://linux-uvc.berlios.de/#footnote-4
{iSight webcams require a proprietary firmware that can't be redistributed. Tools
to extract the firmware from the MacOS X driver and load it into the device are available
at http://bersace03.free.fr/ift/.}
-Nix Fan.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Re: captivating window manager
Pieter Verberne [EMAIL PROTECTED] writes: On Fri, Jun 13, 2008 at 10:08:47AM +, Nicolas Legrand wrote: Igor Zinovik [EMAIL PROTECTED] writes: I'm moving from dwm to cwm. I think I've never felt so comfortable with a WM, I'm very happy it's in base and I join you to thank the devs. Thanks ! Really..? So a tilling window manager was not your thing? kind of, tought you can use dwm without tilling. I like the idea I don't have to care about sizing or placing the windows. Anyway at the end they where never where I wanted them nor did they have the size I wanted. And I realize having no bits of my screen unused was nice on the paper but didn't meet my needs. So I finally wanted to change. I had a look on CWM first cause it was in base, and finaly I found it more attractive. Taste matter.
openbgp: operation not permitted
Greetings, I set up 2 routers running openbgpd. The first one is working well. The 2nd one is not. I am seeing these errors in the syslog Jun 13 14:18:13 router2 bgpd[9453]: neighbor xxx.191.188.137: write error: Operation not permitted Jun 13 14:22:23 router2 bgpd[9453]: neighbor xxx.191.188.137: connect: Operation not permitted I am not yet sure whether the problem is with the peer or with my server. Because I set both servers up in the same manner, I am stumped as to why it is complaining about permission issue: # ps -ax | grep bgp 24233 ?? I 0:03.75 bgpd: route decision engine (bgpd) 9453 ?? I 0:00.25 bgpd: session engine (bgpd) 14094 ?? Is 0:04.78 bgpd: parent (bgpd) 1255 p0 R+/00:00.00 grep bgp # bgpctl show neighbor BGP neighbor is xxx.191.188.137, remote AS 15290 BGP version 4, remote router-id xxx.191.66.21 BGP state = Active, down for 00:26:13 Last read 00:30:13, holdtime 240s, keepalive interval 80s Message statistics: Sent Received Opens1 1 Notifications0 0 Updates 1 45502 Keepalives 16 17 Route Refresh0 0 Total 18 45520 Update statistics: Sent Received Updates 0 0 Withdraws0 0 Local host: xxx.191.188.139, Local port: 16342 Remote host: xxx.191.188.137, Remote port: 179 If you have seen this, please share your experience. thanks. Lu
detection of machines behind PF firewall
Hi all Is there currently any known method for detecting information about a machine behind a PF firewall? Specifically, if I have a machine with two IP addresses, is it possible for a remote attacker to detect that these two IP addresses are bound on the same machine (this machine would be behind a PF firewall with the scrubbing option). The two IP addresses would be known to the attacker. Thanks Alec
Re: detection of machines behind PF firewall
On Fri, Jun 13, 2008 at 04:05:12PM -0400, alexander lind wrote: Hi all Is there currently any known method for detecting information about a machine behind a PF firewall? Specifically, if I have a machine with two IP addresses, is it possible for a remote attacker to detect that these two IP addresses are bound on the same machine (this machine would be behind a PF firewall with the scrubbing option). The two IP addresses would be known to the attacker. Nobody will answer your question without seeing your ruleset and other detailed information. Thanks Alec
Re: how long does pftop track state?
On 6/12/08 9:14 PM, Tim Donahue wrote: Quoting David Newman [EMAIL PROTECTED]: Looking for info on seeing near-real-time or real-time info on TCP connection states using pftop. A 4.3-release box has pf rules that allow Windows Remote Desktop connections from a handful of sources. pftop shows entries something like the following: PRD SRC DEST STATE AGE EXP PKTS BYTES tcp I 666.1.2.3:2048666.4.5.6:3389 4:4 32387 57663 40930 10M tcp O 666.1.2.3:2048666.4.5.6:3389 4:4 32397 57653 40930 10M Problem is, this RDC session ended more than two hours ago. The pftop(8) manpage says the EXP column means there are more than 40,000 seconds left until these entries expire. Is there some better way of monitoring current TCP connection states? Perhaps the connection didn't close cleanly? You can use `pfctl -ss -v` to show all the states and their ages, etc. Yes, that may be the issue. IE (along with some but not all other apps in Windows XP) close TCP connections with a RST rather than a FIN. In some cases I'm seeing a mismatch between pfctl and pftop readings, with the latter claiming a TCP connection is still around even after it's long gone. At least for me, pfctl provides more up-to-date reporting. ps. Tangential, but where can I learn more about the STATE column above? I don't see anything in the manpage about the meaning of 4:4 but perhaps I missed it. It seems to be the numerical representation of the state's status in pf's state table, i.e. 4:4 == ESTABLISHED:ESTABLISHED. Grab putty or something and maximize the window to see the descriptive versions. Yes, that works, thanks. I'm going to contact Can Acar offlist to see about contributing more detail to the manpage. dn
in-kernel pppoe problems
Hello,
it looks like the in-kernel pppoe causes systems to hang up sometimes. I
testet with two systems (completly different hardware) and two different
dsl-modems (I'm from germany - standard tcom modems).
Did someone else notice such problems?
Here is my hostname.pppoe0:
#cat /etc/hostname.pppoe0
inet 0.0.0.0 255.255.255.255 NONE \
pppoedev bge1 authproto pap \
authname 'USERNAME' authkey 'PASSWORD' up
dest 0.0.0.1
!/sbin/route add default 0.0.0.1
# cat /etc/hostname.bge1
up
Here is the output from the kernel panic:
cached lines from terminal server:
ddb{0} start of buffer
13/6/2008 11:49:39pppoe0: LCP keepalive timeout
13/6/2008 11:49:39kernel: page fault trap, code=0
13/6/2008 11:49:41Stopped at softclock+0x2d: movl
%edx,0x4(%eax)
13/6/2008 11:49:41ddb{0}
13/6/2008 18:29:27ddb{0}
end of buffer
output from ddb commands:
ddb{0} trace
softclock(58,de8a0010,10,de8a0010,de8ae000) at softclock+0x2d
Bad frame pointer: 0xde8aff20
ddb{0} ps
PID PPID PGRPUID S FLAGS WAIT COMMAND
26917 24357 32309220 3 0x2004080 selectqmail-smtpd
19628 22976 22976 0 3 0x282 netio tcpdump
22976 3048 22976 76 3 0x2004182 bpf tcpdump
28819 15851 28819 0 3 0x2004082 ttyin ksh
15851 13411 15851 0 3 0x2004180 selectsshd
3048 1164 3048 0 3 0x2004082 pause ksh
1164 13411 1164 0 3 0x2004080 selectsshd
26129 27247 32309200 3 0x2004080 piperdmultilog
10965 19992 32309201 3 0x2004180 poll dnscache
1687 11010 10844 0 3 0x2800082 netio tcpdump
11010 10844 10844 76 3 0x2804182 bpf tcpdump
10844 1 10844 0 3 0x2805082 pause sh
12506 22056 12506515 3 0x2004080 piperdunlinkd
22056 15607 15607515 3 0x2004180 kqreadsquid
6061 24437 32309225 3 0x2004080 piperdqmail-clean
12394 24437 32309226 3 0x2004080 selectqmail-rspawn
23031 24437 32309 0 3 0x2004080 selectqmail-lspawn
24357 12238 32309220 3 0x2004180 netcontcpserver
14976 11484 32309222 3 0x2004080 piperdmultilog
24437 30067 32309227 3 0x2004080 selectqmail-send
20754 31587 32309222 3 0x2004080 piperdmultilog
27247 17401 32309 0 3 0x2004080 poll supervise
19992 17401 32309 0 3 0x2004080 poll supervise
11484 17401 32309 0 3 0x2004080 poll supervise
12238 17401 32309 0 3 0x2004080 poll supervise
31587 17401 32309 0 3 0x2004080 poll supervise
30067 17401 32309 0 3 0x2004080 poll supervise
22921 32309 32309 0 3 0x2004080 piperdreadproctitle
17401 32309 32309 0 3 0x2004080 nanosleep svscan
5641 1 5641 0 3 0x2004082 ttyin getty
9200 1 9200 0 3 0x2004082 ttyin getty
11008 1 11008 0 3 0x2004082 ttyin getty
30618 1 30618 0 3 0x2004082 ttyin getty
32099 1 32099 0 3 0x2004082 ttyin getty
12115 1 12115 0 3 0x2004082 ttyin getty
8185 1 8185 0 3 0x280 selectcron
32309 1 32309 0 3 0x2004082 pause sh
15607 1 15607 0 3 0x280 wait squid
13411 1 13411 0 3 0x280 selectsshd
5549 1 5549 0 3 0x2000180 selectinetd
14162 2559 2559 83 3 0x2000180 poll ntpd
2559 1 2559 0 3 0x280 poll ntpd
22633 3798 3798 68 3 0x2000180 selectisakmpd
3798 1 3798 0 3 0x280 netio isakmpd
6099 5809 5809 74 3 0x2000180 bpf pflogd
5809 1 5809 0 3 0x280 netio pflogd
30348 17649 17649 73 3 0x2000180 poll syslogd
17649 1 17649 0 3 0x288 netio syslogd
17 0 0 0 3 0x2100200 crypto_wait crypto
16 0 0 0 3 0x2100200 aiodoned aiodoned
15 0 0 0 3 0x2100200 syncerupdate
14 0 0 0 3 0x2100200 cleaner cleaner
13 0 0 0 30x100200 reaperreaper
12 0 0 0 3 0x2100200 pgdaemon pagedaemon
11 0 0 0 3 0x2100200 pftm pfpurge
10 0 0 0 3 0x2100200 usbevtusb3
9 0 0 0 3 0x2100200 usbevtusb2
8 0 0 0 3 0x2100200 usbevtusb1
7 0 0 0 3 0x2100200 usbtskusbtask
6 0 0 0 3 0x2100200 usbevtusb0
5 0
Re: in-kernel pppoe problems
On Fri, Jun 13, 2008 at 11:24:32PM +0200, misc(at)openbsd.org wrote:
Hello,
it looks like the in-kernel pppoe causes systems to hang up sometimes. I
testet with two systems (completly different hardware) and two different
dsl-modems (I'm from germany - standard tcom modems).
Did someone else notice such problems?
Here is my hostname.pppoe0:
#cat /etc/hostname.pppoe0
inet 0.0.0.0 255.255.255.255 NONE \
pppoedev bge1 authproto pap \
authname 'USERNAME' authkey 'PASSWORD' up
dest 0.0.0.1
!/sbin/route add default 0.0.0.1
# cat /etc/hostname.bge1
up
Here is the output from the kernel panic:
cached lines from terminal server:
ddb{0} start of buffer
13/6/2008 11:49:39pppoe0: LCP keepalive timeout
13/6/2008 11:49:39kernel: page fault trap, code=0
13/6/2008 11:49:41Stopped at softclock+0x2d: movl
%edx,0x4(%eax)
13/6/2008 11:49:41ddb{0}
13/6/2008 18:29:27ddb{0}
end of buffer
You don't provide information about which version of OpenBSD you are
running. Anyway, this seems identical to PR 5794 which was fixed in
-current on May 17.
Re: 4.3: netstat question
On Thu, Jun 12, 2008 at 3:47 PM, Toni Mueller [EMAIL PROTECTED] wrote: as of today (I didn't notice it earlier), I see this problem on one of my machines: # netstat -rnf inet netstat: sysctl of routing table: Cannot allocate memory netstat -r dumps the routing table by calling sysctl() twice, once to get the size of the table so that it can allocate enough memory to hold it, and then a second call to actually fill it in. That error means the routing table grew between the two calls, so the second call could return the entire table. Any idea about how to combat this, please? The code will need to be changed to a) add a fudge factor to the size that was returned, and b) retry the pair of calls if the second returns ENOMEM I'll try to send you a patch this weekend. Philip Guenther
Re: 4.3: netstat question
On Fri, Jun 13, 2008 at 04:20:45PM -0700, Philip Guenther wrote: On Thu, Jun 12, 2008 at 3:47 PM, Toni Mueller [EMAIL PROTECTED] wrote: as of today (I didn't notice it earlier), I see this problem on one of my machines: # netstat -rnf inet netstat: sysctl of routing table: Cannot allocate memory netstat -r dumps the routing table by calling sysctl() twice, once to get the size of the table so that it can allocate enough memory to hold it, and then a second call to actually fill it in. That error means the routing table grew between the two calls, so the second call could return the entire table. Nope. That is not the problem. The main issues is that a full view will need a lot of memory for the sysctl. This memory needs to be available as real memory because it is wired into the kernel. If you run bgpd with full views on a box with less then 512MB of RAM you're most probably run out of memory. Theo and I had a look at this and bailing out in this situation is the right thing to do. The right fix is to just spend 50 bucks on 1-2GB of additional RAM. Any idea about how to combat this, please? The code will need to be changed to a) add a fudge factor to the size that was returned, and There is already enough fudge in the sysctl itself. The estimate done by the sysctl in the first run is 10% over the needed memory. b) retry the pair of calls if the second returns ENOMEM Will not help either. c) work around (ugly but works) netstat -rnfinet -M /dev/mem d) the route sysctl needs to be rewritten to be fully restartable and so small chunks of the table can be fetched one after the other. This is a massive change and it will not happen for the upcomming release. -- :wq Claudio
rpc.lockd doesn't build in current
Freshly checked out -current doesn't build: === usr.sbin/rpc.lockd cc -O2 -pipe -I. -DSYSLOG -c nlm_prot_svc.c cc -O2 -pipe -I. -DSYSLOG -c /usr/src/usr.sbin/rpc.lockd/procs.c cc -O2 -pipe -I. -DSYSLOG -c /usr/src/usr.sbin/rpc.lockd/lockd.c nroff -Tascii -mandoc /usr/src/usr.sbin/rpc.lockd/rpc.lockd.8 rpc.lockd.cat8 cc -o rpc.lockd nlm_prot_svc.o lockd.o procs.o -lrpcsvc nlm_prot_svc.o(.text+0x4e9): In function `nlm_prog_4': : undefined reference to `nlm4_test_4_svc' nlm_prot_svc.o(.text+0x574): In function `nlm_prog_4': : undefined reference to `nlm4_lock_4_svc' nlm_prot_svc.o(.text+0x58b): In function `nlm_prog_4': : undefined reference to `nlm4_cancel_4_svc' nlm_prot_svc.o(.text+0x5a2): In function `nlm_prog_4': : undefined reference to `nlm4_unlock_4_svc' nlm_prot_svc.o(.text+0x5b9): In function `nlm_prog_4': : undefined reference to `nlm4_granted_4_svc' nlm_prot_svc.o(.text+0x5d0): In function `nlm_prog_4': : undefined reference to `nlm4_test_msg_4_svc' nlm_prot_svc.o(.text+0x5e7): In function `nlm_prog_4': : undefined reference to `nlm4_lock_msg_4_svc' nlm_prot_svc.o(.text+0x5fe): In function `nlm_prog_4': : undefined reference to `nlm4_cancel_msg_4_svc' nlm_prot_svc.o(.text+0x615): In function `nlm_prog_4': : undefined reference to `nlm4_unlock_msg_4_svc' nlm_prot_svc.o(.text+0x62c): In function `nlm_prog_4': : undefined reference to `nlm4_granted_msg_4_svc' nlm_prot_svc.o(.text+0x643): In function `nlm_prog_4': : undefined reference to `nlm4_test_res_4_svc' nlm_prot_svc.o(.text+0x65a): In function `nlm_prog_4': : undefined reference to `nlm4_lock_res_4_svc' nlm_prot_svc.o(.text+0x671): In function `nlm_prog_4': : undefined reference to `nlm4_cancel_res_4_svc' nlm_prot_svc.o(.text+0x688): In function `nlm_prog_4': : undefined reference to `nlm4_unlock_res_4_svc' nlm_prot_svc.o(.text+0x69f): In function `nlm_prog_4': : undefined reference to `nlm4_granted_res_4_svc' nlm_prot_svc.o(.text+0x6c3): In function `nlm_prog_4': : undefined reference to `nlm4_share_4_svc' nlm_prot_svc.o(.text+0x6da): In function `nlm_prog_4': : undefined reference to `nlm4_unshare_4_svc' nlm_prot_svc.o(.text+0x6f1): In function `nlm_prog_4': : undefined reference to `nlm4_nm_lock_4_svc' nlm_prot_svc.o(.text+0x708): In function `nlm_prog_4': : undefined reference to `nlm4_free_all_4_svc' collect2: ld returned 1 exit status Stop in /usr/src/usr.sbin/rpc.lockd: Exit status 1 (rpc.lockd, line 95 of /usr/share/mk/bsd.prog.mk) Stop in /usr/src/usr.sbin: Exit status 2 (all, line 48 of /usr/share/mk/bsd.subdir.mk) *** Error code 1 *** Error code 2 *** Error code 2 Stop in /usr/src: Exit status 2 (all, line 48 of /usr/share/mk/bsd.subdir.mk) *** Error code 2 Stop in /usr/src: Exit status 2 (build, line 73 of Makefile)
Son Kayitlar Yonetici Asistanligi Zirvesi
S 0 N K A Y I T L A R = 3. Yvnetici Asistanl}p} Zirvesi Zirve Konu~mac}lar}: TANJU ARGUN -(Yonetim Danismani), PERIHAN YAZICI -(Northel Telecom - Ingiltere), SERAP OZAY -(Alsim Alarko Yon. Asst.), KELLY HEVEL -(Yasam Kocu - ABD), CANAN CETIN -(STM Savunma Teknolojileri Gn. Md. Asst.), Dr. SELIN AYGEN -(Akdeniz Uni. Buro Yon. ve Sekreterlik Bolum Baskani), ERDAL GULMEZ -(THY Egitim Baskanligi Program Muduru), ZULAL GUNAL(THY Egitim Baskanligi Yon. Asst. Egitmeni), Yrd. Doc. Dr. EBRU NURLUOGLU -(Yeditepe Un. Ogr. Uyesi, ENRP Iletisim, NECDET UYGURER -(ODTU ve Yeditepe Un. Ogr. Gor.), Psk. Dr. MURAT BILGILI -(Is Yasami ve Savasan Kadinlar Yazari), ALMILA DALKILIC -(Iletisim Danismani), NILGUN KARATOPRAKLI -(Imaj Danismani), EMEL ULU -(Beykent Uni. Buro Yonetimi ve Sekreterlik Bolum Baskani), Av. CEYDA CIMILLI AKAYDIN 1. Gun: 20 Haziran 2008 / Cuma 08:30 09:00 Kayit ve Yerlesme 09:00 09:45 Yoneticinin Arkasindaki GUC - Yonetimde Yonetici Asistaninin Rolu ve Onemi Perihan YAZICI 09:45 10:00 Kahve Arasi 10:00 10:45 Yonetici Gozuyle Yonetici Asistani - Yonetimin Asistandan Beklentileri Tanju ARGUN 10:45 11:00 Kahve Arasi 11:00 11:45 Yonetici Asistanliginda Birimler Arasi Koordinasyon Erdal GULMEZ 11:45 12:00 Kahve Arasi 12:00 12:45 Is Hayatinda Yonetici Asistanligi-Yonetici Asistaninin Gorev Pratikleri Emel ULU 12:45 14:00 Yemek Arasi 14:00 14:45 Zor Insan Iliskileri, Problem Cozme ve Stres Yonetim Teknikleri Psk. Dr. Murat BILGILI 14:45 15:00 Kahve Arasi 15:00 15:45 Yonetici Asistani Gozu Ile Basari ve Mukemmellik Serap OZAY 15:45 16:00 Kahve Arasi 16:00 16:45 Yuzyuze ve Telefonda Iletisimde Basari Ipuclari - Genel Protokol Kurallari Almila DALKILIC 16:45 17:00 Kahve Arasi 17:00 17:45 Mukemmel Organizasyonlarin Planlanmasi, Denetimi ve Yonetimi Canan CETIN 17:45 18:00 Kahve Arasi 18:00 18:45 Kisisel Imaj, Dis Gorunum ve Kurum Kulturu Iliskisi Nilgun KARATOPRAKLI 2. Gun: 21 Haziran 2008 / Cumartesi 09:15 10:00 Mukemmel Asistan ve Mukemmel Kocluk Zulal GUNAL 10:00 10:15 Kahve Arasi 10:15 11:00 Yonetici Asistanlari Icin Halkla Iliskiler ve Sosyal Iletisim Yrd. Doc. Dr. Ebru NURLUOGLU 11:00 11:15 Kahve Arasi 11:15 12:00 Yonetici Asistanlari Icin Genel Isletme Yonetim Pratikleri - Is Hayati Etkilesimi Necdet UYGURER 12:00 13:00 Yemek Arasi Paralel Oturumlarla Egitim Seminerleri Grup I. Oturum (13:00-15:15) II. Oturum (15:30-17:15) A Yonetici Asistanlari icin Genel Isletme Yonetimi (Finans, Muhasebe, Kalite Sistemleri, Uretim ve Pazarlama Surecleri) Necdet UYGURER Yonetici Asistanlari Icin Genel Hatlari ile Ticaret ve Is Hukuku Av. Ceyda CIMILLI AKAYDIN B Yonetici Asistanliginda Duygusal Zekanin Kullanimi Dr. Selin AYGEN Yuzyuze Iletisim ve Beden Dili Etkili ve Guzel Konusma Tekniklerini Almila DALKILIC C Bireysel Gelisim - Sevgi Dolu Iliskiler ve Is Hayatinda Karsilasilan Sorunlar Perihan YAZICI Psikososyal Olarak Insani Tanimak Yoneticinin Cevresini Tanimak Yoneticiyi Tanimak ve Degisimlere En Suratli Adaptasyonu Gostermek Psk. Dr. Murat BILGILI D Lead Yourself To Success (Ingilizce Sunum) Kelly HEVEL Yonetici Asistanlari Icin Etkili Yazisma (Ingilizce-Turkce) ve Raporlama Teknikleri Necdet UYGURER Detayli Bilgi Icin: O216 486 3O95 pbx FINANS SEMINERLER] S O N K A Y I T L A R KURESEL SERMAYE HAREKETLERI VE OZEL SERMAYE FONLARI Konusmacilar: Dr. Fikri ORAN / Lutfu KADIRGAN / Namik Kemal KEMER EKONOMI SOHBETLERI EKONOMIDE GELISMELER, BEKLENTILER ve STRATEJILER Konusmacilar: Gazi ERCEL (T.C. Merkez Bankasi E. Bsk.), Doc. Dr. Sevket SAYILGAN (Ekonomist) 19 Haziran 2008 / Istanbul Hilton Persembe / 13.00 - 18.00/ Katilim Bedeli 500 YTL+KDV Content Sponsor: sovereigngroup 26 Haziran 2008 / Istanbul Hilton Persembe / 13.00 - 18.00/ Katilim Bedeli 500 YTL+KDV Detayli Bilgi Icin: O216 486 3O95 pbx
Re: 4.3: netstat question
On Fri, Jun 13, 2008 at 5:39 PM, Claudio Jeker [EMAIL PROTECTED] wrote: ... Nope. That is not the problem. The main issues is that a full view will need a lot of memory for the sysctl. This memory needs to be available as real memory because it is wired into the kernel. If you run bgpd with full views on a box with less then 512MB of RAM you're most probably run out of memory. Theo and I had a look at this and bailing out in this situation is the right thing to do. The right fix is to just spend 50 bucks on 1-2GB of additional RAM. Yuck. For now, how about the following patch? Index: sysctl.3 === RCS file: /cvs/src/lib/libc/gen/sysctl.3,v retrieving revision 1.181 diff -u -r1.181 sysctl.3 --- sysctl.330 May 2008 19:09:42 - 1.181 +++ sysctl.314 Jun 2008 03:26:26 - @@ -2176,6 +2176,12 @@ The length pointed to by .Fa oldlenp is too short to hold the requested value. +.It Bq Er ENOMEM +There isn't enough real memory available to pin the buffers specified by +.Fa oldp +and +.Fa newp +in the kernel. .It Bq Er ENOTDIR The .Fa name Philip Guenther
Call for testing - uvideo(4)
I see on undeadly a call for testing uvideo(4) in CURRENT which seems to require UVC (USB Video Class) compatible webcams. Would that include the webcam built into last year's models of MacBook Pro? What options, if any, are there for IEEE 1394? I have one such web cam lying around. Regards, -Lars
Re: pf.conf comment lines
On Fri, Jun 13, 2008 at 1:14 PM, Theo de Raadt [EMAIL PROTECTED] wrote: ... Now, if a comment line ends with \, should the next line be also treated as comment? I noticed this behaviour and I do not know whether or not it should work like that. Well, because you used \ to end the line, that # is not at the start of a line. It is in the middle of a split line. And the previously described behaviour therefore hapens. Sadly, this varies among languages and file-formats. You just have to know how the one you're working in behaves. Languages and file-formats where comment removal occurs before backslash-newline removal: sh csh perl python awk /etc/sudoers /etc/ipsec.conf Languages and file-formats where backslash-newline removal occurs before comment removal: tcl C C++ getcap(3)-style files /etc/pf.conf Philip Guenther
