Re: OpenSSH sshd -E
On Sun, Apr 28, 2013 at 08:32:39PM +0300, Lars Nooden wrote: I see a useful feature in OpenSSH 6.2(?) in current that is not in the release notes for 6.2. In the man page for sshd(1) in current there is this: -E log_file Append debug logs to log_file instead of the system log. [...] Is this something from upcoming 6.3 or was it missed in the release notes for 6.2? It was added after the 5.2 release and will be in 5.3. -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.
install fixes address in /etc/hosts
Installed yesterday's current/i386, using dhcpd and pxeboot from another machine. After the installation, I noticed that the address that was assigned to me during the install via DHCP was written into /etc/hosts. Is that intended? Should an arbitrary dhcp-assigned address be written into /etc/hosts to stay there? Should that be mentioned in afterboot? The user might want to just use DHCP during the install, and only during afterboot, while setting everything up, decide on a fixed address and put that into hostname.if - but the arbitrary dhcp-assigned address will still be in /etc/hosts, possbily conflicting. Jan
Re: Why does OpenBSD use CVS?
On 04/29/13 00:00, Hugo Osvaldo Barrera wrote: On 2013-04-20 23:32, Nick Holland wrote: On 04/20/13 03:42, Alokat MacMoneysack wrote: Hi, first, I don't want to start a flame war about why is CVS better or not better than X - it's just a question. If you say, we use it because it just works - it's okay. :) Good, 'cause it does. :) So why does OpenBSD still uses CVS and don't migrate to SVN or something like git as other OSS projekts do? * it works * migrating - and not losing history is difficult. * migrating versioning systems is something you don't want to do every few weeks (or even every few years)...so you want to make sure it is really worth it if/when you do. SVN today? GIT next week? something else next year? Please, no. * Tolerable -- and in the case of opencvs, ideal -- license. * its glitches are hated, but known (the devil you know how to subdue, vs. the devil who beats the sh*t out of you) * relatively light weight -- runs fine on a 486, hp300, or on a modern, fast machine, fits nicely into existing distribution, easy to drop into a chroot. * Infrastructure exists. To change it all would require a really good reason. * it fits the OpenBSD development model. * Many of the features of alternatives are not desired in the OpenBSD development model. Out of curiosity; what are these features? Honestly, I haven't played much with the alternatives...but usually I hear about how wonderful the branching and merging is in these other products...but that is NOT something we wish to be doing (see the presentations on the OpenBSD development process in the papers section of the website). Our model is all development is done at HEAD, if something is committed, it is supposed to be better than what was there before (which in some cases, may be nothing, in which case, the bar is more it is in a state where at least the group can work on it). Without bothering to dig up references...I recall there have been people singing the praises of how the various CVS alternatives try to handle the management of development teams, and OpenBSD developers (most of whom have day jobs related to their work) commenting along the lines of doesn't work, still need real human leadership. I think a better question, considering the pain of conversion, is what features would give OpenBSD a clear gain by converting? Want to sell OpenBSD on an alternative? Find a product that was really crappy, switched development tools, and suddenly started rivaling OpenBSD for quality for no reason other than the switch of development tools. Nick.
Re: em(4) fails to initialize for Intel i350-F2 dual-port fibre NIC
Apologies for the delayed follow-up; I was unable to test over the weekend. I plugged in both fibres this afternoon. With the diff, the hardware appears to be correctly initialized. Both ports properly find their link. Light testing today shows no surprises. Any particular things I should test additionally? Regards, Rogier
Re: install fixes address in /etc/hosts
On Mon, Apr 29, 2013 at 01:41:52PM +0200, Jan Stary wrote: Installed yesterday's current/i386, using dhcpd and pxeboot from another machine. After the installation, I noticed that the address that was assigned to me during the install via DHCP was written into /etc/hosts. Is that intended? Should an arbitrary dhcp-assigned address be written into /etc/hosts to stay there? Should that be mentioned in afterboot? The user might want to just use DHCP during the install, and only during afterboot, while setting everything up, decide on a fixed address and put that into hostname.if - but the arbitrary dhcp-assigned address will still be in /etc/hosts, possbily conflicting. Jan Aha! To quote the commit message to /usr/src/distrib/miniroot/install.sub from 2009: Sat Mar 14 14:23:05 2009 UTC (4 years, 1 month ago) by krw Branches: MAIN Diff to: previous 1.448: preferred, coloured Changes since revision 1.448: +11 -6 lines There should only be one ::1 and one 127.0.0.1 entry in the hosts file. And 'localhost' don't need no stinkin' domain names. Insert line(s) with the address(es) of last interface defined instead of duplicate ::1 and 127.0.0.1 entries, Thus dhcp configured interfaces may eventually drift away from the value in hosts file. Much discussed just before tree lock. Time to see what happens. - So what happens is that four years later somebody notices. :-) Your points are valid. I no longer recall the discussions that took place at the time, and am open to any new discussion. Ken
Re: install fixes address in /etc/hosts
On Mon, Apr 29, 2013 at 11:02, Kenneth R Westerback wrote: On Mon, Apr 29, 2013 at 01:41:52PM +0200, Jan Stary wrote: Installed yesterday's current/i386, using dhcpd and pxeboot from another machine. After the installation, I noticed that the address that was assigned to me during the install via DHCP was written into /etc/hosts. Is that intended? Should an arbitrary dhcp-assigned address be written into /etc/hosts to stay there? Should that be mentioned in afterboot? Your points are valid. I no longer recall the discussions that took place at the time, and am open to any new discussion. As I recall, Bad Things (tm) happen when the machine's hostname does not resolve, and that's why there is always an entry in hosts. If I wanted to open a giant rabbit hole, I might suggest dhclient should update hosts as it runs... But it's important that *something* be in /etc/hosts that matches what's in /etc/myname. We changed it from adding 127.0.0.1 entries for the hostname because Other Bad Things (tm) happened when forward and reverse lookups for localhost and/or the hostname didn't coordinate.
Versioning file system?
Hi fellas, I'm looking for a versioning file system or a comparative implementation. The idea is that I want to store file changes for some periods of time. I also want to be able to delete earliest few periods' file changes when the harddisk is almost full. I couldn't find information on availability of versioning file system in OpenBSD. Did I missi something? Kind regards, Xianwen
Re: Versioning file system?
2013/4/29 Xianwen Chen xianwen.c...@gmail.com Hi fellas, I'm looking for a versioning file system or a comparative implementation. The idea is that I want to store file changes for some periods of time. I also want to be able to delete earliest few periods' file changes when the harddisk is almost full. I couldn't find information on availability of versioning file system in OpenBSD. Did I missi something? CVS? RCS? Kind regards, Xianwen
Re: em(4) fails to initialize for Intel i350-F2 dual-port fibre NIC
On Mon, Apr 29, 2013 at 7:53 AM, Rogier Krieger rkrie...@gmail.com wrote: Apologies for the delayed follow-up; I was unable to test over the weekend. I plugged in both fibres this afternoon. With the diff, the hardware appears to be correctly initialized. Both ports properly find their link. Light testing today shows no surprises. ^ ha... did you do that on purpose? ... light testing :) -pk Any particular things I should test additionally? Regards, Rogier
Re: Versioning file system?
skrev Rodrigo Mosconi: CVS? RCS? Thank you. I believe CVS will work for my purpose!
Re: Versioning file system?
On Apr 29, 2013, at 5:54 PM, Xianwen Chen xianwen.c...@gmail.com wrote: Hi fellas, I'm looking for a versioning file system or a comparative implementation. The idea is that I want to store file changes for some periods of time. I also want to be able to delete earliest few periods' file changes when the harddisk is almost full. I couldn't find information on availability of versioning file system in OpenBSD. Did I missi something? Kind regards, Xianwen Not sure, but it sounds like you are looking for something like this: http://blog.interlinked.org/tutorials/rsync_time_machine.html
Re: Versioning file system?
On Mon, 29 Apr 2013, [iso-8859-1] Zé Loff wrote: Not sure, but it sounds like you are looking for something like this: http://blog.interlinked.org/tutorials/rsync_time_machine.html Much more useful than a time machine lookalike: rsnapshot http://www.rsnapshot.org/ No fancy gui (who needs it?), .. configurage for as may versions as you like - hourly, daily, weekly, yearly, and keep each as long as you wish. The key is using hardlinks on the target filesystem, so browse to any date (e.g. daly.0) and you have a complete directory listing. It's not CVS, but in some cases it is more usable. Lee
Re: Versioning file system?
skrev Zé Loff: Not sure, but it sounds like you are looking for something like this: http://blog.interlinked.org/tutorials/rsync_time_machine.html Using rsync to create snapshots is amazing. I didn't know that I could do this. Thank you very much!
Re: Versioning file system?
skrev L. V. Lammert Much more useful than a time machine lookalike: rsnapshot http://www.rsnapshot.org/ No fancy gui (who needs it?), .. configurage for as may versions as you like - hourly, daily, weekly, yearly, and keep each as long as you wish. The key is using hardlinks on the target filesystem, so browse to any date (e.g. daly.0) and you have a complete directory listing. It's not CVS, but in some cases it is more usable. Lee Thank you Lee. I would go for rsnapshot if I didn't read http://blog.interlinked.org/tutorials/rsync_time_machine.html and http://www.mikerubel.org/computers/rsync_snapshots/ for an hour before seeing your email. I now understand the method of configuring rsync to make snapshots. I think I will write my own script based on these two web pages. Xianwen
Re: logrotate error on latest snapshot
I'm still seeing these errors each time tcpdump: pcap_loop: truncated dump file tcpdump: pcap_loop: bogus savefile header simply running tcpdump -nettt -r /var/log/pflog leads to the tcpdump: pcap_loop: truncated dump file. Any ideas? Below is the content of /var/log/pf-block.log Apr 29 12:05:01 core-install pf: Apr 29 12:00:44.450168 rule 10/(match) block in on vlan310: fe80::151:6adb:4921:8e33.52856 ff02::1:3.5355: udp 22 [hlim 1] Apr 29 12:05:01 core-install pf: Apr 29 12:00:44.450178 rule 10/(match) block in on vlan310: fe80::151:6adb:4921:8e33.52856 ff02::1:3.5355: udp 22 [hlim 1] Apr 29 12:05:01 core-install pf: Apr 29 12:00:44.450541 rule 10/(match) block in on vlan310: 192.168.0.4.61394 224.0.0.252.5355: udp 22 [ttl 1] Apr 29 12:05:01 core-install pf: Apr 29 12:00:44.450552 rule 10/(match) block in on vlan310: 192.168.0.4.61394 224.0.0.252.5355: udp 22 [ttl 1] Apr 29 12:05:01 core-install pf: Apr 29 12:00:44.550100 rule 10/(match) block in on vlan310: 192.168.0.4.61394 224.0.0.252.5355: udp 22 [ttl 1] Apr 29 12:05:01 core-install pf: Apr 29 12:00:44.550107 rule 10/(match) block in on vlan310: fe80::151:6adb:4921:8e33.52856 ff02::1:3.5355: udp 22 [hlim 1] Apr 29 12:05:01 core-install pf: Apr 29 12:00:44.550114 rule 10/(match) block in on vlan310: fe80::151:6adb:4921:8e33.52856 ff02::1:3.5355: udp 22 [hlim 1] Apr 29 12:05:01 core-install pf: Apr 29 12:00:44.550125 rule 10/(match) block in on vlan310: 192.168.0.4.61394 224.0.0.252.5355: udp 22 [ttl 1] Apr 29 12:05:01 core-install pf: Apr 29 12:00:44.750482 rule 10/(match) block in on vlan310: 192.168.0.4.137 192.168.0.255.137: udp 50 Apr 29 12:05:01 core-install pf: Apr 29 12:00:44.750494 rule 10/(match) block in on vlan310: 192.168.0.4.137 192.168.0.255.137: udp 50 Apr 29 12:05:01 core-install pf: Apr 29 12:00:45.500168 rule 10/(match) block in on vlan310: 192.168.0.4.137 192.168.0.255.137: udp 50 Apr 29 12:05:01 core-install pf: Apr 29 12:00:45.500179 rule 10/(match) block in on vlan310: 192.168.0.4.137 192.168.0.255.137: udp 50 Apr 29 12:10:01 core-install pf: Apr 29 12:08:25.056424 rule 10/(match) block in on vlan310: fe80::151:6adb:4921:8e33.546 ff02::1:2.547:dhcp6 solicit [hlim 1] Apr 29 12:10:01 core-install pf: Apr 29 12:08:25.056436 rule 10/(match) block in on vlan310: fe80::151:6adb:4921:8e33.546 ff02::1:2.547:dhcp6 solicit [hlim 1] Apr 29 12:10:01 core-install pf: Apr 29 12:08:25.400461 rule 10/(match) block in on vlan310: fe80::151:6adb:4921:8e33 ff02::16: HBH multicast listener report v2, 1 group record(s) [hlim 1] Apr 29 12:10:01 core-install pf: Apr 29 12:08:25.400469 rule 10/(match) block in on vlan310: fe80::151:6adb:4921:8e33 ff02::16: HBH multicast listener report v2, 1 group record(s) [hlim 1] Apr 29 12:10:01 core-install pf: Apr 29 12:08:25.400584 rule 10/(match) block in on vlan310: 192.168.0.4 224.0.0.22: igmp-2 [v2] [ttl 1] Apr 29 12:10:01 core-install pf: Apr 29 12:08:25.400592 rule 10/(match) block in on vlan310: 192.168.0.4 224.0.0.22: igmp-2 [v2] [ttl 1] Apr 29 12:10:01 core-install pf: Apr 29 12:08:25.427442 rule 10/(match) block in on vlan310: fe80::151:6adb:4921:8e33 ff02::16: HBH multicast listener report v2, 1 group record(s) [hlim 1] Apr 29 12:10:01 core-install pf: Apr 29 12:08:25.427450 rule 10/(match) block in on vlan310: fe80::151:6adb:4921:8e33 ff02::16: HBH multicast listener report v2, 1 group record(s) [hlim 1] Apr 29 12:10:01 core-install pf: Apr 29 12:08:25.427565 rule 10/(match) block in on vlan310: 192.168.0.4 224.0.0.22: igmp-2 [v2] [ttl 1] Apr 29 12:10:01 core-install pf: Apr 29 12:08:25.427572 rule 10/(match) block in on vlan310: 192.168.0.4 224.0.0.22: igmp-2 [v2] [ttl 1] Apr 29 12:10:01 core-install pf: Apr 29 12:08:25.428080 rule 10/(match) block in on vlan310: 192.168.0.4.56486 224.0.0.252.5355: udp 24 [ttl 1] Apr 29 12:10:01 core-install pf: Apr 29 12:08:25.428088 rule 10/(match) block in on vlan310: fe80::151:6adb:4921:8e33.58621 ff02::1:3.5355: udp 24 [hlim 1] Apr 29 12:10:01 core-install pf: Apr 29 12:08:25.428095 rule 0.\M-t.0/(match) block in on vlan)\M-E~Qh\M-\: bad-ip6-version 4 - Original Message - | I do PF log rotation for blocked packets and the latest snapshot | reports the following error each time syslog is run. Is this a bug? | | tcpdump: pcap_loop: bogus savefile header | | | /etc/pflogrotate | | | #!/bin/sh | | PFLOG=/var/log/pflog | FILE=/var/log/pflog5min.$(date +%Y%m%d%H%M) | pkill -ALRM -u root -U root -t - -x pflogd | if [ -r $PFLOG ] [ $(stat -f %z $PFLOG) -gt 24 ]; then |mv $PFLOG $FILE |pkill -HUP -u root -U root -t - -x pflogd |tcpdump -n -e -s 160 -ttt -r $FILE | logger -t pf -p local0.info |rm $FILE | fi | | | /etc/syslog.conf | | | local0.info /var/log/pf-block.log | | | -- | James A. Peltier | Manager, IT Services - Research Computing Group | Simon Fraser University - Burnaby Campus | Phone : 778-782-6573
Re: panic: got error 5 while accessing filesystem
On Apr 28 18:34:07, h...@stare.cz wrote: On Apr 28 12:55:58, m...@online.fr wrote: I wasn't able to find out what error 5 is. EIO. There are probably horrible I/O error messages in your dmesg prior to this panic. Actually, there are none. Could this indicate that the USB enclosure or the cable is faulty? The disk is functioning without a glitch now. I am running dd if=/dev/sd0c of=/dev/null bs=8m to see if it reports some errors. It finished without errors.
SiS 7018 Audio Codec in current
Update to OpenBSD 5.3-current (GENERIC) #146: Thu Apr 25 16:55:16 MDT 2013 results in a dmesg with ohci1 at pci0 dev 1 function 3 SiS 5597/5598 USB rev 0x07: irq 5, version 1.0, legacy support autri0 at pci0 dev 1 function 4 SiS 7018 Audio rev 0x02: irq 11 autri0: Codec timeout. Busy writing AC97 codec autri0: Codec timeout. Busy writing AC97 codec autri0: Codec timeout. Busy writing AC97 codec autri0: Codec timeout. Busy writing AC97 codec autri0: Codec timeout. Busy writing AC97 codec autri0: Codec timeout. Busy writing AC97 codec autri0: Codec timeout. Busy writing AC97 codec autri0: Codec timeout. Busy writing AC97 codec autri0: Codec timeout. Busy writing AC97 codec autri0: Codec timeout. Busy writing AC97 codec autri0: Codec timeout. Busy writing AC97 codec autri0: Codec timeout. Busy writing AC97 codec autri0: Codec timeout. Busy writing AC97 codec autri0: Codec timeout. Busy writing AC97 codec autri0: Codec timeout. Busy writing AC97 codec autri0: Codec timeout. Busy writing AC97 codec autri0: Codec timeout. Busy writing AC97 codec autri0: Codec timeout. Busy writing AC97 codec -- J. Scott Heppler
