Alleged OpenSSH bug
To me it looks like a mistimed April Fools' joke, but hope somebody more knowledgeable will respond: https://kingcope.wordpress.com/2015/07/16/openssh-keyboard-interactive-authentication-brute-force-vulnerability-maxauthtries-bypass/
Some SSH clients unable to connect to latest snapshot
When using the latest snapshot, some ssh clients are unable to connect. I don't know whether this is due to a problem with the client or the server, but hope someone can point me in the right direction. If it is a server problem, I will of course send a proper bug report. I first noticed the problem when using an older version of putty on a Windows terminal server. After updating it to the latest version it worked fine, so I'm thinking it's a client problem. However, later I see that both Xming and X-win32 get the same error, though both are using the latest version of putty. This is the snapshot: OpenBSD 5.5-current (GENERIC.MP) #44: Mon Mar 31 11:14:26 MDT 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP This is the error on X-Win32: Looking up host herakles.walkertx.com Connecting to 192.168.60.74 port 22 Using SSPI from SECUR32.DLL Server version: SSH-2.0-OpenSSH_6.6 Using SSH protocol version 2 We claim version: SSH-2.0-PuTTY_Local:_Aug_17_2012_15:07:42 GSSAPI key-exchange initialisation failed No credentials are available in the security package. Doing Diffie-Hellman group exchange Server unexpectedly closed network connection FATAL ERROR: Server unexpectedly closed network connection This is from /var/log/authlog: Apr 1 11:20:03 herakles sshd[9594]: Server listening on 0.0.0.0 port 22. Apr 1 11:20:03 herakles sshd[9594]: Server listening on :: port 22. Apr 1 11:35:53 herakles sshd[27087]: fatal: no matching mac found: client hmac-sha1,hmac-sha1-96,hmac-md5 server umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512 [preauth] Apr 1 11:40:47 herakles sshd[28093]: Accepted publickey for eperea from 192.168.61.11 port 57192 ssh2: ECDSA 81:3b:89:f2:25:23:09:a1:16:8b:de:08:57:83:b4:20 Apr 1 11:45:22 herakles sshd[20497]: Accepted publickey for eperea from 192.168.61.11 port 57151 ssh2: RSA ea:de:cc:6a:87:83:d1:39:fd:44:8b:28:a5:46:1e:87 The failure was from X-Win32, the following three two were from an OpenBSD 5.5 VM and the latest putty.
Re: Some SSH clients unable to connect to latest snapshot
On Tue, Apr 01, 2014 at 11:06:44AM -0700, Chris Cappuccio wrote: Emilio Perea [epe...@walkereng.com] wrote: When using the latest snapshot, some ssh clients are unable to connect. I don't know whether this is due to a problem with the client or the server, but hope someone can point me in the right direction. If it is a server problem, I will of course send a proper bug report. I first noticed the problem when using an older version of putty on a Windows terminal server. After updating it to the latest version it worked fine, so I'm thinking it's a client problem. However, later I see that both Xming and X-win32 get the same error, though both are using the latest version of putty. http://marc.info/?l=openbsd-cvsm=139596131723206w=2 http://marc.info/?l=openbsd-cvsm=139574041614940w=2 Thanks, Chris!
Re: xenocara not building on amd64-current
On Mon, Sep 10, 2012 at 07:25:08AM +0200, Matthieu Herrb wrote: On Sun, Sep 09, 2012 at 11:56:28PM -0500, Emilio Perea wrote: On Sun, Sep 09, 2012 at 12:34:58PM +0200, Matthieu Herrb wrote: Afacit, it does build. What error are you getting ? *** cc -O2 -pipe -I/usr/X11R6/include -I/usr/xenocara/app/fvwm/fvwm -I/usr/xenocara/app/fvwm/fvwm/.. -I/usr/xenocara/app/fvwm/fvwm/../libs -DFVWM_MODULEDIR=\/usr/X11R6/lib/X11/fvwm\ -DFVWMRC=\.fvwmrc\ -DFVWM_CONFIGDIR=\/usr/X11R6/lib/X11/fvwm\ -c /usr/xenocara/app/fvwm/fvwm/windows.c cc -o fvwm add_window.o bindings.o borders.o builtins.o colormaps.o colors.o complex.o decorations.o events.o focus.o functions.o fvwm.o fvwmdebug.o icons.o menus.o misc.o modconf.o module.o move.o placement.o read.o resize.o style.o virtual.o windows.o -L/usr/X11R6/lib -L/usr/xenocara/app/fvwm/fvwm/../libs/obj -lfvwm -lXpm -lXt -lICE -lSM -lXext -lX11 -lxcb -lXdmcp -lXau /usr/bin/ld: /usr/X11R6/lib/libfvwm.a(ClientMsg.o): relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC /usr/X11R6/lib/libfvwm.a: could not read symbols: Bad value ^^ Where does this library come from ? It's not installed by normal xenocara builds. Remove it and it should fix your issue. I'm not sure where it came from (it was dated 2007) but as you said, it fixed the issue. Thanks!
Re: xenocara not building on amd64-current
On Sun, Sep 09, 2012 at 12:34:58PM +0200, Matthieu Herrb wrote: On Sat, Sep 08, 2012 at 10:58:55PM -0500, Emilio Perea wrote: I am very grateful for the effort the developers put into the snapshots, so I don't mean this as criticism. But it is possible for somebody reading the thread to believe that the latest snapshot would allow xenocara to build. As far as I can tell, it does not (yet) on amd64. Afacit, it does build. What error are you getting ? Sorry about the delay in responding! This is what I get: *** cc -O2 -pipe -I/usr/X11R6/include -I/usr/xenocara/app/fvwm/fvwm -I/usr/xenocara/app/fvwm/fvwm/.. -I/usr/xenocara/app/fvwm/fvwm/../libs -DFVWM_MODULEDIR=\/usr/X11R6/lib/X11/fvwm\ -DFVWMRC=\.fvwmrc\ -DFVWM_CONFIGDIR=\/usr/X11R6/lib/X11/fvwm\ -c /usr/xenocara/app/fvwm/fvwm/windows.c cc -o fvwm add_window.o bindings.o borders.o builtins.o colormaps.o colors.o complex.o decorations.o events.o focus.o functions.o fvwm.o fvwmdebug.o icons.o menus.o misc.o modconf.o module.o move.o placement.o read.o resize.o style.o virtual.o windows.o -L/usr/X11R6/lib -L/usr/xenocara/app/fvwm/fvwm/../libs/obj -lfvwm -lXpm -lXt -lICE -lSM -lXext -lX11 -lxcb -lXdmcp -lXau /usr/bin/ld: /usr/X11R6/lib/libfvwm.a(ClientMsg.o): relocation R_X86_64_32 can not be used when making a shared object; recompile with -fPIC /usr/X11R6/lib/libfvwm.a: could not read symbols: Bad value collect2: ld returned 1 exit status *** Error code 1 Stop in /usr/xenocara/app/fvwm/fvwm (line 95 of /usr/share/mk/bsd.prog.mk). *** Error code 1 Stop in /usr/xenocara/app/fvwm (line 48 of /usr/share/mk/bsd.subdir.mk). *** Error code 1 Stop in /usr/xenocara/app/fvwm (line 6 of Makefile). *** Error code 1 Stop in /usr/xenocara/app (line 48 of /usr/share/mk/bsd.subdir.mk). *** Error code 1 Stop in /usr/xenocara (line 39 of Makefile). *** Error code 1 Stop in /usr/xenocara (line 32 of Makefile).
Re: xenocara not building on amd64-current
On Tue, Sep 04, 2012 at 03:44:35AM -0400, Ted Unangst wrote: A lot of effort is expended trying to get snapshots out quickly after toolchain changes, precisely to make things easy for people. Even if you think you can figure out building from the source, the polite thing to do is to use the snapshots anyway. :) I am very grateful for the effort the developers put into the snapshots, so I don't mean this as criticism. But it is possible for somebody reading the thread to believe that the latest snapshot would allow xenocara to build. As far as I can tell, it does not (yet) on amd64. Since I'm sure it will be fixed by another snapshot soon, this is no big deal.
g77 g95 conflict
I have usually had both g77 and g95 ports installed in i386 and amd64 PCs, but the last batch of -current ports fails with this message: # pkg_add -ui [gcc-3.3.6p5v0]gcc-4.6.3p9: internal conflict between gcc-4.6.3p9 and gcc-3.3.6p5v0 Can't install g95-4.6.3p4-g95-4.6.3p9: can't resolve gcc-4.6.3p9 Couldn't find updates for g95-4.6.3p4 # This is on i386. No conflict on amd64 (which uses gcc 3.3.5 for g77). I don't suppose it is very important, but I would like to know whether this is a temporary conflict or I should plan to stick with g95 from now on.
Re: g77 g95 conflict
Sorry, that should have been addressed to ports@ On Mon, Sep 03, 2012 at 03:56:20PM -0500, Emilio Perea wrote: I have usually had both g77 and g95 ports installed in i386 and amd64 PCs, but the last batch of -current ports fails with this message: # pkg_add -ui [gcc-3.3.6p5v0]gcc-4.6.3p9: internal conflict between gcc-4.6.3p9 and gcc-3.3.6p5v0 Can't install g95-4.6.3p4-g95-4.6.3p9: can't resolve gcc-4.6.3p9 Couldn't find updates for g95-4.6.3p4 # This is on i386. No conflict on amd64 (which uses gcc 3.3.5 for g77). I don't suppose it is very important, but I would like to know whether this is a temporary conflict or I should plan to stick with g95 from now on.
Re: libc.so.64.1?
On Wed, May 16, 2012 at 02:22:34PM +0200, Manuel Giraud wrote: I've just tried to update and it seems that the current snapshots/i386/base51.tgz doesn't contains /usr/lib/libc.so.64.1. If that's to be expected following -current, i'll wait a couple of day before re-update. There does not seem to be any libc.so.* on the current snapshot, so it would be a good idea to wait. (Wish I had! :-)
Re: libc.so.64.1?
On Wed, May 16, 2012 at 10:21:58AM -0500, Emilio Perea wrote: On Wed, May 16, 2012 at 02:22:34PM +0200, Manuel Giraud wrote: I've just tried to update and it seems that the current snapshots/i386/base51.tgz doesn't contains /usr/lib/libc.so.64.1. If that's to be expected following -current, i'll wait a couple of day before re-update. There does not seem to be any libc.so.* on the current snapshot, so it would be a good idea to wait. (Wish I had! :-) I should have clarified this is only on the i386 snapshot. The amd64 snapshot (and I assume all others) are fine.
Publickey authentication stopped working on -current
Since installing yesterday's snapshot on amd64: OpenBSD 4.9-current (GENERIC.MP) #111: Wed May 11 10:41:28 MDT 2011 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP I lost the ability to login to sshd using publickey: $ ssh hermes Permission denied (publickey,keyboard-interactive). A kernel compiled from -current source behaves the same way. I had PasswordAuthentication no in /etc/ssh/sshd_config, which I had to remove in order to login. Is this due to a change in configuration file syntax that I missed, or a bug?
Re: Publickey authentication stopped working on -current
On Thu, May 12, 2011 at 10:21:33AM -0500, Emilio Perea wrote: Since installing yesterday's snapshot on amd64: OpenBSD 4.9-current (GENERIC.MP) #111: Wed May 11 10:41:28 MDT 2011 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP I lost the ability to login to sshd using publickey: $ ssh hermes Permission denied (publickey,keyboard-interactive). A kernel compiled from -current source behaves the same way. I had PasswordAuthentication no in /etc/ssh/sshd_config, which I had to remove in order to login. Is this due to a change in configuration file syntax that I missed, or a bug? Sorry for the previous... This is what I missed: - Forwarded message from Damien Miller d...@cvs.openbsd.org - Date: Tue, 10 May 2011 22:47:06 -0600 (MDT) From: Damien Miller d...@cvs.openbsd.org To: source-chan...@cvs.openbsd.org Subject: CVS: cvs.openbsd.org: src CVSROOT:/cvs Module name:src Changes by: d...@cvs.openbsd.org2011/05/10 22:47:06 Modified files: usr.bin/ssh: servconf.h servconf.c pathnames.h auth2-pubkey.c auth.h auth.c Log message: remove support for authorized_keys2; it is a relic from the early days of protocol v.2 support and has been undocumented for many years; ok markus@ - End forwarded message - I have been using authorized_keys2 for quite a while...
Re: Anyone ran Dnscurve on OpenBSD?
On Tue, Jul 27, 2010 at 05:30:40PM +0100, Kevin Chadwick wrote: I noticed a thread where someone had problems compiling dnscurve (nacl) on OpenBSD. http://old.nabble.com/dnscurve-updates-td24333543.html; Has anyone ran dnscurve on OpenBSD? I believe Matthew Dempsky matt...@dempsky.org was working on dnscurve implementations and he's a regular here.
Re: dvd drives causes boot to hang
On Mon, Jan 04, 2010 at 07:20:16PM +0100, Markus Hennecke wrote: So I am not the only one... The breakage happens with the commits that introduce scsi_xs_sync (rev. 1.150 from src/sys/scsi/scsi_base.c etc.). If I check out the files in the scsi directory from before that commit the kernel boots fine, it hangs with the version mentioned above. I see the same thing on a Dell laptop using i386-GENERIC and a desktop using amd64-GENERIC.MP, when using IDE CD or DVD drives. With SCSI drives there are no problems.
CVSync problems?
There seems to be a problem with CVSync updates (at least anoncvs1.usa.openbsd.org and anoncvs3.usa.openbsd.org). I believe this started about the time a large number of changes to gcc were made. After updating the tree with csup, run cvsync: - Forwarded message from Cron Daemon r...@hermes.walkereng.com - Date: 18 Oct 2009 13:30:01 - From: Cron Daemon r...@hermes.walkereng.com To: epe...@hermes.walkereng.com Subject: Cron epe...@hermes /home/eperea/Bin/cvsupdate Starting /home/eperea/Bin/cvsupdate: Sun Oct 18 08:30:01 CDT 2009 Connecting to anoncvs3.usa.openbsd.org port Connected to 192.43.244.161 port Running... Updating (collection openbsd/rcs) /open/anoncvs/cvs/ports/databases/py-storm/patches/patch-test,v: No such file or directory Socket Error: send: Broken pipe Mux(SEND) Error: send FileScan(RCS): UPDATE /open/anoncvs/cvs/ports/devel/gconf-editor/Makefile,v FileScan: RCS Error Socket Error: recv: Connection reset by peer Receiver Error: recv Mux(RECV) Error: not running: 1 Updater: RCS Error Mux(SEND) Error: not running: 0 DirScan: RCS Error Failed Finished updating cvs: Sun Oct 18 08:30:33 CDT 2009 - End forwarded message - Csup still runs without errors: - Forwarded message from Cron Daemon r...@hermes.walkereng.net - Date: 18 Oct 2009 13:45:01 - From: Cron Daemon r...@hermes.walkereng.net To: epe...@hermes.walkereng.net Subject: Cron epe...@hermes /home/eperea/Bin/old.cvsupdate Starting /home/eperea/Bin/cvsupdate: Sun Oct 18 08:45:01 CDT 2009 Connected to 194.45.27.107 Updating collection OpenBSD-all/cvs Append to CVSROOT/ChangeLog Append to CVSROOT/ChangeLog.37 Append to CVSROOT/val-tags Edit ports/infrastructure/build/libtool,v Finished successfully Finished updating cvs: Sun Oct 18 08:47:56 CDT 2009 - End forwarded message -
Re: ALIX and PC Engines CompactFlash
On Fri, Oct 09, 2009 at 05:35:35PM +0200, Jan Stary wrote: Sadly, I have never seen any multi-sector PIO card. And obviuosly, I will be upgrading soon (ALICes, actually). Can people recommend some quality multi-sector PIO CF cards? I've had excellent results with SanDisk cards. This one is on a Soekris 5500: wd0 at pciide0 channel 0 drive 0: SanDisk SDCFX4-8192 wd0: 4-sector PIO, LBA, 7815MB, 16007040 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 root on wd0a swap on wd0b dump on wd0b This one is on an early Soekris 4801 which does not support DMA modes in the CF socket, so had to disable that in kernel: wd0 at pciide0 channel 0 drive 0: SanDisk SDCFX-2048 wd0: 4-sector PIO, LBA, 1953MB, 4001760 sectors wd0(pciide0:0:0): using PIO mode 4 root on wd0a swap on wd0b dump on wd0b In this case the fancy new card did not perform any better than the cheap old one, but you should not run into that problem with recent hardware.
/var/spool/lpd in -current
Possibly a dumb question, but... What are the proper [ownership and] permissions for /var/spool/lpd/?
Re: openbsd binary update
On Tue, Jul 21, 2009 at 07:28:52PM +0200, Maciej Jan Broniarz wrote: I have installed openbsd on a 2 gb cf card. Is there a way to update my system and install all patches for my release using binaries? I have no free space to recompile the system from sources, still i would like to do an update if necessary. You can upgrade to -current snapshots using the normal methods or if you prefer running -stable you can build a release in another computer and install from that. A standard binary upgrade followed by sysmerge is relatively quick and easy.
Re: current /root/.login question
On Sun, Jul 12, 2009 at 05:04:58PM -0700, Philip Guenther wrote: On Fri, Jul 10, 2009 at 10:12 AM, Emilio Pereaepe...@walkereng.com wrote: There have been some changes to the default /root/.login recently that I don't understand, and hope someone can enlighten me. On my oldest server, the root shell is still csh, so the change is very noticeable: Using the /root/.login from the 4.5 CD, when I login there is a terminal type prompt which has always included the proper terminal type as default. The /root/.login from the current snapshot always results in an unknown terminal type, so I have to type in the terminal type myself before proceeding. Is this as intended? ... Last login: Fri Jul 10 11:35:12 2009 from herakles.walkereng.net OpenBSD 4.6 (GENERIC) #58: Thu Jul 9 21:24:42 MDT 2009 ... tset: unknown terminal type !* Terminal type? nxterm Erase is delete. Kill is control-U (^U). Interrupt is control-C (^C). Read the afterboot(8) man page for administration advice. Something is weird about your 4.6-almost system: - the error from tset implies that it was passed !* on the command line - the Erase is.../Kill is.../Interrupt is... output implies that tset was *not* passed the -Q option The latter would seem to imply that the tset in the /root/.login file has either been changed or it is not the tset invocation that's causing that output. Do you perhaps have anything in your /etc/csh.* files? That was it! The line alias tset 'set noglob histchars=; eval `\tset -s \!*`; unset noglob histchars' which was removed in version 1.9 (25-Apr-1998!) was somehow still in root's .cshrc. My apologies... I'm ashamed to say that I thought .login was executed ahead of .cshrc and didn't check the man page.
current /root/.login question
There have been some changes to the default /root/.login recently that I don't understand, and hope someone can enlighten me. On my oldest server, the root shell is still csh, so the change is very noticeable: Using the /root/.login from the 4.5 CD, when I login there is a terminal type prompt which has always included the proper terminal type as default. The /root/.login from the current snapshot always results in an unknown terminal type, so I have to type in the terminal type myself before proceeding. Is this as intended? *--* Last login: Fri Jul 10 11:32:12 2009 from herakles.walkereng.net OpenBSD 4.6 (GENERIC) #58: Thu Jul 9 21:24:42 MDT 2009 Welcome to OpenBSD: The proactively secure Unix-like operating system. Please use the sendbug(1) utility to report bugs in the system. Before reporting a bug, please try to reproduce it with the latest version of the code. With bug reports, please try to ensure that enough information to reproduce the problem is enclosed, and if a known fix for it exists, include that as well. Terminal type? [xterm-color] hermes# *--* Last login: Fri Jul 10 11:35:12 2009 from herakles.walkereng.net OpenBSD 4.6 (GENERIC) #58: Thu Jul 9 21:24:42 MDT 2009 Welcome to OpenBSD: The proactively secure Unix-like operating system. Please use the sendbug(1) utility to report bugs in the system. Before reporting a bug, please try to reproduce it with the latest version of the code. With bug reports, please try to ensure that enough information to reproduce the problem is enclosed, and if a known fix for it exists, include that as well. tset: unknown terminal type !* Terminal type? nxterm Erase is delete. Kill is control-U (^U). Interrupt is control-C (^C). Read the afterboot(8) man page for administration advice. hermes# diff old.login new.login 1c1 # $OpenBSD: dot.login,v 1.11 2005/03/30 19:50:07 deraadt Exp $ --- # $OpenBSD: dot.login,v 1.13 2009/05/06 22:02:05 millert Exp $ 5,12c5,16 set tterm='?'$TERM set noglob onintr finish eval `tset -s -Q $tterm` finish: unset noglob unset tterm onintr --- if ( -x /usr/bin/tset ) then set noglob histchars= onintr finish if ( $?XTERM_VERSION ) then eval `tset -IsQ '-munknown:?vt220' $TERM` else eval `tset -sQ '-munknown:?vt220' $TERM` endif finish: unset noglob histchars onintr endif hermes# *--*
Re: vi line wrap.
On Thu, Apr 16, 2009 at 04:31:51PM +0200, Jan Stary wrote: On Apr 16 09:59:29, Stuart VanZee wrote: I've read the man page No you haven't: wraplen, wl [0] vi only. Break lines automatically, the specified number of columns from the left-hand margin. If both the wraplen and wrapmargin edit options are set, the wrapmargin value is used. wrapmargin, wm [0] vi only. Break lines automatically, the specified number of columns from the right-hand margin. If both the wraplen and wrapmargin edit options are set, the wrapmargin value is used. I don't think that's what he was looking for. He was looking for a toggle for the lines wrapping in the vi display, nothing in the file contents. As I understand it he wanted to see only a part of any lines longer than the display rather than have them wrap so as to appear to be on the lines below.
Thar she blows!
4.5 is on the way! - Forwarded message from OpenBSD Shipping shipp...@qubit.computershop.ca - Date: Mon, 13 Apr 2009 09:14:41 -0700 (MST) From: OpenBSD Shipping shipp...@qubit.computershop.ca To: /home/shipping/mail/shipc...@qubit.computershop.ca, epe...@walkereng.com Subject: USPS OpenBSD Order:2009/3/5-22:5:56-7333: USPS tracking number...
Re: RES: OpenBSD on IBM 3550
On Mon, Apr 06, 2009 at 07:11:33PM -0300, Ricardo Augusto de Souza wrote: Really? So http://www.openbsd.org/i386.html is wrong? No, but you are not reading the whole thing. See this note: (*) Support for devices marked with (*) is not included on the distribution media or in the GENERIC kernel, and will require you to compile a custom kernel to enable it. You need a custom kernel for the aac driver. It is NOT in GENERIC. Cause we can see this there: RAID and Cache Controllers ICP-Vortex and Intel GDT series (gdt) (A) (C) Adaptec FSA-based RAID controllers (aac), including: (*) Note: In the past years Adaptec has lied to us repeatedly about forthcoming documentation which would have allowed us to stabilize, improve and manage RAID support for these (rather buggy) raid controllers. As a result, we do not recommend the Adaptec cards for use. Adaptec AAC-2622, AAC-364, AAC-3642, 2130S, 2200S, 2230SLP, 2410SA, 2610SA, 2810SA, 21610SA Dell CERC-SATA, PERC 320/DC Dell PERC 2/QC, PERC 2/Si, PERC 3/Si, PERC 3/D HP NetRaid-4M IBM ServeRAID-8i/8k/8s As i cant install openbsd on IBM 3550, I installed FreeBSD 7.1. This is dmesg: http://ti.cmtsp.com.br:810/logs/dmesg_FreeBSD7.1_IBM3550.txt FreeBSD shows: aac0: IBM ServeRAID-8k port 0x4000-0x40ff mem 0xcce0-0xccff,0xcafe-0xcaff irq 17 at device 0.0 on pci2 aac0: Enable Raw I/O aac0: Enable 64-bit array aac0: New comm. interface enabled aac0: [ITHREAD] aac0: ServeRAID 8k-l , aac driver 2.0.0-1
Re: SOEKRIS - How to install MTR to a Flashdist image
On Thu, Mar 26, 2009 at 01:12:52AM +0100, Henning Brauer wrote: the key is not to have coffee (or anything that is claimed to be coffee) in mouth when reading these ridiculous statements Black coffee is not too bad, but Coca Cola Classic makes a really sticky mess in your laptop. Tip: if you remove the battery quickly and rinse the keyboard in distilled water, using a wet rag on other affected parts, and let it dry 24 hours, even an apparently hopeless case can be rescued: OpenBSD 4.5-current (GENERIC) #1: Mon Mar 23 23:28:11 MDT 2009 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium III (GenuineIntel 686-class) 601 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real mem = 200765440 (191MB) avail mem = 185712640 (177MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 01/21/02, BIOS32 rev. 0 @ 0xfe708, SMBIOS rev. 2.3 @ 0xbff (48 entries) bios0: vendor TOSHIBA version Version 1.40 date 01/21/2002 bios0: TOSHIBA PORTEGE 3480CT apm0 at bios0: Power Management spec V1.2 apm0: battery life expectancy 100% apm0: AC on, battery charge high, estimated 1:28 hours acpi at bios0 function 0x0 not configured ...
Re: bgpd crashes on long AS-path
On Wed, Feb 18, 2009 at 03:38:11PM -0500, Daniel Ouellet wrote: May be, you should run current and there is yet an other fresh commit on the subject just done a few minutes ago: clau...@cvs.openbsd.org 2009/02/18 13:30:36 http://marc.info/?l=openbsd-cvsm=123498913126874w=2 Daniel, I believe there were commits for 4.3 and 4.4 -stable, so those are also valid options.
Re: Displaying the list of known FTP servers during installation broken?
On Wed, Feb 18, 2009 at 10:46:16PM +0200, turha turha wrote: Hey, There might be something I'm missing, but I was unable to get the list of known FTP servers during the installation. I used the cd44.iso, and everything else went fine, except where it asks if I want a list of FTP servers displayed to choose a FTP server close to me. Display the list of known ftp servers? [no], I answered yes, and it hangs there, nothing happened for maybe 10-15 minutes, so I shut it down and started installation again. This time answering no, and typing in a ftp server manually. Everything worked just fine, so it's not my connection that's broken. Later on I noticed similar (maybe same) issue, trying to use ports, some of the FTP servers it tried to use failed (too many users, etc), but again ftp.openbsd.org hangs. One thing that I did notice was that it tries to ftp ftp://ftp.openbsd.org/pub/... when I tried that from command line it also hangs, if I tried with just ftp ftp.openbsd.org it asks for username and works just fine. The result from command line: $ ftp ftp://ftp.openbsd.org/ Connected to openbsd.sunsite.ualberta.ca. 220 openbsd.srv.ualberta.ca FTP server ready. 331 Guest login ok, send your email address as password. 230- Welcome to ftp.openbsd.org at the University of Alberta Not sure if this is just me, but it's a bit weird that I faced this same issue when trying to freshly install OpenBSD 4.4, and it couldn't fetch the list of mirrors, not much I could have broken at that point I think. It may have been a temporary problem with the main ftp server, since it seems to be working fine now.
Re: usr.sbin/wake removal
On Mon, Feb 09, 2009 at 09:05:13PM +1300, Richard Toohey wrote: On 9/02/2009, at 6:31 PM, Thomas Pfaff wrote: I think this could use some explaining for those of us that are not intimately involved in development or have been around here for that long. Keeping it small and simple by saying no to adding one file at 7.2K? I'd really like to know the rationale on this one. Thanks. My guess would be that I want this 10K util, you want that 7.2K util, Fred wants that 20K util, and every Tom, Dick, and Harry wants their n K ... who gets to make the rules, who gets to administer it, etc.? (Who gets to listen to everyone arguing why this or that should go in?) And guess there may be ramifications for install media? If there is no room in base, it would be nice to have it in ports. Or is there something else in ports already that does the same thing? I've found wake extremely useful for turning on remote desktop computers from the Soekris firewall rather than leaving them on all the time.
Re: Missing security announcements
On Thu, Nov 13, 2008 at 11:19:45AM -0600, Brian Drain wrote: So I am curious, what IS the best way to stay up to date? Is manually checking the errata page every day really correct (seems like there would be an automated solutuion such as the lynx dump aforementioned)? It seems to me that even if there is a security flaw in OpenBSD most of them (from reading prior patches) would be exceedingly hard to exploit anyway so maybe it's not as big of a deal as, say, Windows B.S. (which is exactly the reason I am learning something else). I'm not sure this is the best way, but what I do to keep up with -stable is to have a cronjob do a cvs (or csup) update every day. Most days there is nothing updated, so it's quite noticeable when there's a change. These are the two changes since 4.4 release: - Forwarded message from Cron Daemon [EMAIL PROTECTED] - Date: 2 Nov 2008 11:00:02 - From: Cron Daemon [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Cron [EMAIL PROTECTED] /home/eperea/Bin/updsrc Starting /home/eperea/Bin/updsrc: Sun Nov 2 05:00:02 CST 2008 P sys/conf/newvers.sh P sys/dev/pci/if_vr.c P sys/netinet6/in6.c P sys/netinet6/in6_var.h P sys/netinet6/nd6_nbr.c Finished updating source: Sun Nov 2 05:15:24 CST 2008 *==* Date: 6 Nov 2008 11:00:02 - From: Cron Daemon [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Cron [EMAIL PROTECTED] /home/eperea/Bin/updsrc Starting /home/eperea/Bin/updsrc: Thu Nov 6 05:00:02 CST 2008 P sys/netinet/tcp_input.c P usr.sbin/httpd/src/ap/ap_hook.c P usr.sbin/httpd/src/modules/proxy/proxy_http.c Finished updating source: Thu Nov 6 05:14:56 CST 2008 - End forwarded message - When I see these, I check to see if it's something that requires patching immediately (but haven't seen any of those yet). Otherwise, I build a release and install it after hours on the remote sites.
Re: Missing security announcements
On Wed, Nov 12, 2008 at 06:57:19PM +0100, Peer Janssen wrote: I subscribed to security-announce a long time ago and thought I would receive information about security annoucements, but contrary to what is stated on http://openbsd.org/mail.html: security-announce - Security announcements. This low volume list receives OpenBSD security advisories and pointers to security patches as they become available., FWIW, I received the Welcome to the security-announce mailing list! message on 9/4/2002 and nothing since. I don't think it's a big deal since there are other ways of getting the information.
Re: Missing security announcements
On Wed, Nov 12, 2008 at 11:36:10PM -0500, Ted Unangst wrote: On Wed, Nov 12, 2008 at 10:32 PM, Emilio Perea [EMAIL PROTECTED] wrote: FWIW, I received the Welcome to the security-announce mailing list! message on 9/4/2002 and nothing since. I don't think it's a big deal since there are other ways of getting the information. Maybe you mean 2008, because I personally sent several messages to the list in the years since. No, I meant 2002. But as Rod suggested, it's quite possible I got unsubscribed accidentally. I see there are quite a few messages in the mailing list archives... In any case, I've seen announcements of all errata on misc or source-changes, so it's no big deal.
Re: U-DMA mode problems with OpenBSD 4.3 and above + SATA controllers + CF card
On Tue, Oct 21, 2008 at 06:11:07PM +0900, Stephane Lapie wrote: I am currently working with a Portwell NAR-5530 (network appliance running off Intel hardware, can use regular HDs or CF cards as boot device). We want to use this at work for network appliances, but end up bumping in the following problem : the kernel detects any device plugged to the controller (SATA or CF) as UltraDMA-5, even though the BIOS specifies otherwise clearly. I had the same problem with an early Soekris 4801 which was not wired to support DMA or U-DMA on the CF slot. The solution was to disable both with the 0x0ff0 flag to wd (see the wd man page): *--* frisco# config -o new -e bsd.rd OpenBSD 4.4 (RAMDISK_CD) #857: Tue Aug 12 17:31:49 MDT 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD Enter 'help' for information ukc change wd 32 wd* at wdc0|wdc1|wdc*|wdc*|pciide*|pciide* channel -1 flags 0x0 change [n] y channel [-1] ? flags [0] ? 0x0ff0 32 wd* changed 32 wd* at wdc0|wdc1|wdc*|wdc*|pciide*|pciide* channel -1 flags 0xff0 ukc q Saving modified kernel. frisco# mv new bsd.rd frisco# *--* Do the same with bsd and it should install fine. Once you have it working properly you might be able to fine tune it to use a DMA mode it supports, but this will get you going.
Re: U-DMA mode problems with OpenBSD 4.3 and above + SATA controllers + CF card
On Wed, Oct 22, 2008 at 12:10:40AM +, Stuart Henderson wrote: You missed the part lower down in Stephane's email (read down past the dmesg), showing exactly what's happening in the source code and why changing flags does not have an effect. Not to mention the other two replies... Sorry about that!
Re: snapshots/packages/i386 newer than snapshot/i386
On Sat, Sep 13, 2008 at 01:34:58PM -0600, Anathae Townsend wrote: Just an fyi. I am unable to install a package as the libs installed by the iso are older than the libs required by the package. That seems strange, since the last packages I see are dated Aug 13 and the current install sets are dated Sep 10. What mirror are you using?
Re: compile 4.3 source tree on a 4.2 system
On Tue, Aug 12, 2008 at 04:48:04AM +0200, Jesus Sanchez wrote: can I compile a 4.3 source tree with also xenocara on a 4.2 installation?? No. Why would you want to? Do a binary upgrade and then either patch or compile the stable tree.
Re: config GENERIC error
On Sun, Aug 03, 2008 at 02:54:17PM -0500, pezking wrote: Hello, This is my first OpenBSD mailing list post so I hope I am in the correct place, and if I am not I apologize in advance. I'm having some trouble upgrading from OpenBSD 4.2 to 4.3 - particularly at the config GENERIC stage. I am a little bit stumped as I have not edited the kernel in any way in my previous install, or in this one (thus just using GENERIC). I've followed the steps in the handbook but this is the error I get when I do config GENERIC inside /usr/src/sys/arch/i386/conf/: I believe config changed in between releases. You should upgrade to 4.3 release and then update to stable.
Re: Problem with current i386 snapshot
On Sun, Aug 03, 2008 at 10:26:54PM +0200, Paul de Weerd wrote: OpenBSD 4.4-beta (GENERIC) #1011: Sat Aug 2 21:46:49 MDT 2008 (the latest and greatest from ftp.openbsd.org) boots fine. Yes, that fixed the problem. (I was not able to try bsd.rd on my 4801 since I seem to have screwed up my settings and don't get a boot prompt. It's time to fix that now! :-)
Re: config GENERIC error
On Sun, Aug 03, 2008 at 03:33:26PM -0500, pezking wrote: Thanks for the fast replies guys. I'll try your suggestion Emilio, just to make sure, for the tag option in my supfile, do I just do . as I would with FreeBSD to get the current release? Yes, but as Dorian noted, that is the 4.4-beta current, so you would download the current snapshot first. My suggestion was to download the 4.3 release and then update it to -stable with OPENBSD_4_3, which is wrong if you want -current. The i386 snapshot on the ftp sites earlier today had a corrupt kernel file (build 1010). The latest (1011) is fine.
Problem with current i386 snapshot
This build seems to go into an endless reboot cycle, rebooting before anything shows up in the console of a Soekris net4801. The previous snapshot (build #1004) works fine. Unfortunately I have nothing to show for it as far as filing a proper bug report. BIOS screen followed by the changing console to com0 message followed by the BIOS screen etc. Problem build: OpenBSD 4.4-beta (GENERIC) #1010: Sat Aug 2 12:39:46 MDT 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC Last working version dmesg: OpenBSD 4.4-beta (GENERIC) #1004: Thu Jul 31 00:42:16 MDT 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Geode(TM) Integrated Processor by National Semi (Geode by NSC 586-class) 267 MHz cpu0: FPU,TSC,MSR,CX8,CMOV,MMX cpu0: TSC disabled real mem = 133787648 (127MB) avail mem = 120946688 (115MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 20/80/03, BIOS32 rev. 0 @ 0xf7840 pcibios0 at bios0: rev 2.0 @ 0xf/0x1 pcibios0: pcibios_get_intr_routing - function not supported pcibios0: PCI IRQ Routing information unavailable. pcibios0: PCI bus #0 is the last bus bios0: ROM list: 0xc8000/0x9000 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Cyrix GXm PCI rev 0x00 sis0 at pci0 dev 6 function 0 NS DP83815 10/100 rev 0x00, DP83816A: irq 10, address 00:00:24:c2:9e:30 nsphyter0 at sis0 phy 0: DP83815 10/100 PHY, rev. 1 sis1 at pci0 dev 7 function 0 NS DP83815 10/100 rev 0x00, DP83816A: irq 10, address 00:00:24:c2:9e:31 nsphyter1 at sis1 phy 0: DP83815 10/100 PHY, rev. 1 sis2 at pci0 dev 8 function 0 NS DP83815 10/100 rev 0x00, DP83816A: irq 10, address 00:00:24:c2:9e:32 nsphyter2 at sis2 phy 0: DP83815 10/100 PHY, rev. 1 gscpcib0 at pci0 dev 18 function 0 NS SC1100 ISA rev 0x00 gpio0 at gscpcib0: 64 pins NS SC1100 SMI rev 0x00 at pci0 dev 18 function 1 not configured pciide0 at pci0 dev 18 function 2 NS SCx200 IDE rev 0x01: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: SanDisk SDCFX-2048 wd0: 4-sector PIO, LBA, 1953MB, 4001760 sectors wd0(pciide0:0:0): using PIO mode 4 geodesc0 at pci0 dev 18 function 5 NS SC1100 X-Bus rev 0x00: iid 6 revision 3 wdstatus 0 ohci0 at pci0 dev 19 function 0 Compaq USB OpenHost rev 0x08: irq 11, version 1.0, legacy support isa0 at gscpcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com0: console com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 nsclpcsio0 at isa0 port 0x2e/2: NSC PC87366 rev 9: GPIO VLM TMS gpio1 at nsclpcsio0: 29 pins gscsio0 at isa0 port 0x15c/2: SC1100 SIO rev 1: npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 usb0 at ohci0: USB revision 1.0 uhub0 at usb0 Compaq OHCI root hub rev 1.00/1.00 addr 1 biomask fbe5 netmask ffe5 ttymask softraid0 at root root on wd0a swap on wd0b dump on wd0b
Re: /usr/bin/ssh: can't load library 'libcrypto.so.14.0' on ALIX board
On Fri, Jul 25, 2008 at 07:52:51PM -0700, Bryan wrote: After I rebooted, the following came up when the server attempted to create the SSH keys (RSA, RSA1, DSA): ssh-keygen: generating new DSA host key... /usr/bin/ssh-keygen: can't load library 'libcrypto.so.14.0' failed. ssh-keygen: generating new RSA host key... /usr/bin/ssh-keygen: can't load library 'libcrypto.so.14.0' failed. ssh-keygen: generating new RSA1 host key... /usr/bin/ssh-keygen: can't load library 'libcrypto.so.14.0' failed. openssl: generating new isakmpd RSA key... failed. starting network daemons: sendmail inetd sshd/usr/sbin/sshd: can't load library 'libcrypto.so.14.0' --- Should wait for the next snapshot and try again, or is there another issue? I imagine the next snapshot will fix that (the one currently available does not contain libcrypto.so.14.0). If you have another PC available to build a current release, that should also work. I just did that myself on an amd64. (If you try that, note there are some additional library building steps before the final build as shown on http://www.openbsd.org/faq/current.html.)
Re: sshd_config(5) PermitRootLogin yes
On Fri, Jul 11, 2008 at 12:19:27AM -0400, Brian A. Seklecki wrote: On Thu, 10 Jul 2008, Jacob Yocom-Piatt wrote: maybe if people actually READ THE ARCHIVES, they'd be better informed. i wish this mailing list had I didn't want to rehash it all again. Everyone knows the issues. However, with respect to the right to disagree, if Marco's and Darrin's belief that if remote-network-postinstall configuration is the standing reason, then I consider myself in disagreement. ... Either way, its a healthy discussion worth having. I believe you may be overlooking the fact that while we might have a healthy discussion on this subject and decide what the default will be for BASBSD, the people who make the decisions for OpenBSD have already decided. We don't get to vote on that. We may decide how to handle our own installations, but unless you've read through the archives and found an argument that has not been considered, it is best to leave it at that.
Re: Can you contribute code under anonymous under ISC License?
On Mon, Jun 23, 2008 at 04:01:57PM -0700, Predrag Punosevac wrote: The demise of his qmail is a wonderful example of interesting project which died because of the bad licence. I know that lots of people here like his djbdns but just imagine what could have happened with his projects if they were released under BSD license. I started using OpenBSD in version 2.7 in order to run qmail and djbdns due to DJB's suggestion, and have not found any reason to regret either choice. His weird ideas about licensing as well as hier (7) made it impossible to keep his stuff in ports, but it is by no means dead. Unfortunately, BSD licensing would never work for a part-time amateur programmer who insisted on total control. (But you know how crazy those mathematicians are. :-)
Re: dhcpd dying
On Fri, May 09, 2008 at 11:52:57PM -0400, Nick Holland wrote: Just came home to find virtually all my machines had fallen off the network with the same problem. Restarting dhcpd seems to have it run just long enough to answer one query, then it dies quietly. For the moment, might want to try backing your usr.sbin/dhcpd directory in the source tree back a few days (or even to OPENBSD_4_3), and recompile until the problem is fixed. I moved the service temporarily to an old laptop running 4.3 stable. I had intended to update more often, but the tree seems to have been broken this evening (I assume this was intentional). (I was wondering why you spotted the problem days ago, when I just spotted it this evening. I forgot it took my 100MHz sparc a while to build. :) Oh yes, I remember well those days! :)
Re: dhcpd dying
On Sat, May 10, 2008 at 08:47:06AM +0300, Denis Doroshenko wrote: dhcpd seems to be being intensively worked on. there is some new stuff in the tree to sync several dhcpd or something. perhaps you might want to look for CVS log messages for dhcpd sources and update the tree more frequently, even more so 'cause there's the hackaton happening right now. fresh stuff almost always comes with bugs :-) The current tree doesn't build, so I'll wait a bit longer. :-)
Re: dhcpd dying
On Sat, May 10, 2008 at 09:37:10AM +0200, Paul de Weerd wrote: Maybe this has something to do with it : -- From: Bob Beck [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Wed, 7 May 2008 23:38:26 -0600 (MDT) Subject: CVS: cvs.openbsd.org: src CVSROOT:/cvs Module name:src Changes by: [EMAIL PROTECTED]2008/05/07 23:38:26 Modified files: usr.sbin/dhcpd : sync.c sync.h Log message: don't break dhcpd when not using synch mechanisms.. -- Try your mirror again to see if the above has been mirrored yet. Unfortunately, that did not fix it. The last checkout that actually built was on 9 May 2008 07:30:02 -0600 (MDT). The next checkout deleted several files which prevented a build. I thought that might have been intentional because of known problems, but now think it was due to a problem with the mirror. This was this morning's update on a -stable PC: - Forwarded message from Cron Daemon [EMAIL PROTECTED] - Date: 10 May 2008 12:00:02 - From: Cron Daemon [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Cron [EMAIL PROTECTED] /home/eperea/Bin/updsrc Starting /home/eperea/Bin/updsrc: Sat May 10 07:00:02 CDT 2008 ? etc/tee cvs server: distrib/sets/lists/base/md.zaurus is no longer in the repository P lib/libc/gen/readdir.c P lib/libc/gen/telldir.c cvs server: share/man/man4/Makefile is no longer in the repository cvs server: share/man/man4/pci.4 is no longer in the repository cvs server: sys/arch/i386/conf/GENERIC is no longer in the repository cvs server: sys/dev/pci/files.pci is no longer in the repository cvs server: usr.sbin/relayd/parse.y is no longer in the repository cvs server: usr.sbin/relayd/pfe_filter.c is no longer in the repository cvs server: usr.sbin/relayd/relayd.conf.5 is no longer in the repository cvs server: usr.sbin/relayd/relayd.h is no longer in the repository Finished updating source: Sat May 10 07:11:41 CDT 2008 - End forwarded message - I'll try a different mirror. Thanks! Emilio
Re: Broken CF or what?
On Sat, May 10, 2008 at 12:48:10PM +0300, Timo Myyr? wrote: I was trying to install 4.3 to a SanDisk 1GB CF disk but the installer aborts when it tries to create the partitions to the disk I get following when the creating partitions: pciide:0:0:0: timeout waiting for DRQ, st=0x51 DRDY,DSC,ERR, err=0x00 wd0e: device timeout writing fsbn 47908 (wd0 bn 2100672, cn 521 tn 0 sn 0) retrying .. newfs: wtfs: write error on block 47908 Input/Output error I updated the Soekris BIOS, tested it with 4.2,4.3 and -current but all give the same results. I also tried to change the wd* flags to '0xffc' to disable DMA. Is there anything else to try or is the card just broken? You might try changing the wd* flags to '0x0ff0'. That's what I had to do on an early 4801 when I got a new CF card.
dhcpd dying
I have been running amd64 GENERIC.MP -current on my home server for a about 2-1/2 years. Two or three days ago dhcpd started dying without any error message. Since I see that there have been quite a few changes in the last few days, it is possible that this is a known problem that is being worked on. If this is not a known problem, is there something I can do to provide a more useful bug report? I assume dmesg, rc.conf.local, dhcpd.conf and /var/log/daemon. But the last shows nothing when dhcpd dies, and the conf files have not changed in over two years...
Re: Editing C with...
On Wed, May 07, 2008 at 10:46:33AM +1000, Rich Healey wrote: for the record, it's VERY broken in Vista. running edit in cmd or powershell, gives, |=== |16 bit MS-DS Subsytem |x| |=== | |Windows PowerShell |NTVDM has encountered a system Error |The Specified service does not exist |Choose Close to Terminate the application = |Close | Ignore | |== Although I've never had to deal with Vista, previous versions of Windows had a Resource Kit available which includes vi. With some Vista versions you can install SUA (Subsystem for UNIX Applications) which includes tcsh and ksh with vi (packages for vim, emacs and other editors are also available). Even with straight Windows it makes no sense to use Microsoft's shells when JPSoft's are available.
Re: Upgrading 4.1-4.3
On Thu, Apr 24, 2008 at 08:03:18AM +0930, Damon McMahon wrote: I avoided the 4.1-4.2 upgrade due to the libexpat issue - using several packages which use libexpat and not wanting to install xbase on my system. I have read through upgrade43.html and just want to make sure that I can upgrade 4.1-4.2, skip the Upgrading packages step and then upgrade 4.2-4.3 without having to install xbase? I did it without problems when the 4.3 CDs arrived last week. As long as you are careful, you should not have a problem (as usual around here).
Re: configuring the GENERIC kernel (was Re: Issue compiling a program on OpenBSD)
On Sun, Mar 30, 2008 at 11:04:34PM -0400, Nick Holland wrote: HOWEVER, the 80386sx was a non-starter for a long time: these machines only had 24 bit address buses, so it had a max of 16M, and being they were cheap machines, the actual potential of most of the hardware they were used in was 12M, 8M, or way, way less. I don't know that I have ever seen an 80387SX chip -- kinda bizarre thing, an expensive accelerator for a machine you bought because you didn't need much speed... I think it more likely that most people bought the 386SX because they didn't have much money rather than they didn't need much speed. That's certainly the reason I and a couple of friends did. There was also the 80386SL variation which used less power and was particularly good for laptops. As it happens I bought three 80387SL FP co-processors, for my Toshiba T3300SL laptop, for my desktop and one as a Christmas gift. It made a huge difference in number-crunching times. (The 80387SL seems to have replaced the 387SX rather early.) The laptop dual-booted DOS and COHERENT, a commercial 16-bit UNIX-like operating system. When there were no readily-available 32-bit OSs, the 386SX/SL processors seemed to make sense. No good reason for them later... Emilio
Re: i have lost /etc
On Thu, Mar 27, 2008 at 08:56:41PM -0500, Rafael Morales wrote: Please someone help me I have deleted my /etc dir (rm -rf /etc), is there any way to recover it, or there is a way to recover my data stored in /home ??? For /etc look in /var/backups/ (for /home you're on your own).
Re: That whole Linux stealing our code thing
On Sun, Sep 02, 2007 at 12:59:39AM +0530, Siju George wrote:
Could somebody please explain about Running Strings?
The usual explanation is man strings. But for example:
*--*
artemis:~
{20} % strings /dev/fs/C/WINDOWS/system32/nslookup.exe | tail -n 30
@(#) Copyright (c) 1985,1989 Regents of the University of California.
All rights reserved.
@(#)nslookup.c 5.39 (Berkeley) 6/24/90
A.ROOT-SERVERS.NET.
@(#)commands.l 5.13 (Berkeley) 7/24/90
-*-**
**
**
@(#)debug.c 5.22 (Berkeley) 6/29/90
@(#)list.c 5.20 (Berkeley) 6/1/90
@(#)subr.c 5.22 (Berkeley) 8/3/90
@(#)skip.c 5.9 (Berkeley) 8/3/90
@(#)getinfo.c 5.22 (Berkeley) 6/1/90
@(#)send.c 5.17 (Berkeley) 6/29/90
!#$%'()*+,-./0123456789:;=[EMAIL PROTECTED]|}~
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/
0123456789abcdef.
QISKNU?
\Registry\Machine\System\CurrentControlSet\Services\Tcp\VParameters
\Registry\Machine\System\CurrentControlSet\Services\Tcp\Parameters
\Registry\Machine\System\CurrentControlSet\Services\Tcpip\Parameters
\Registry\Machine\System\CurrentControlSet\Services\Tcpip\Parameters\Transient
\Registry\Machine\Software\Policies\Microsoft\Windows NT\DNSClient
[EMAIL PROTECTED]@DDD@
[EMAIL PROTECTED]@
DDD@
,[EMAIL PROTECTED]
b
[EMAIL PROTECTED]@
artemis:~
{21} %
*--*
This is on Windows XP, using the strings from Microsoft Services for
UNIX.
Re: OT Strange Punishment
On Tue, Aug 28, 2007 at 12:49:56PM -0400, Dave Anderson wrote: But, as I understand the issue, this is _not_ part of his specified punishment -- it's just a side-effect of the manner in which the government wants to impose a portion of his punishment. There appears to be no real reason for it other than the government's convenience. As I understand the issue, he agreed to have the goverment monitor all his computer activity. This requires that he run an operating system that will allow that. Does Ubuntu? I guess it's possible, and in that case it would be reasonable to request that the goverment monitor his current OS. Otherwise he needs to change OS or go back to jail. Wasn't that what he agreed to? I'm sorry to say that I suspect him to have known all the time that his parole officer would not be able to monitor his current system, and therefore had no intention to keep his side of the bargain. Emilio
CVS repository problems
I just noticed that after a csup update from rt.fm xenocara is gone and src is getting there. Current df vs this morning's daily output: 2,4c2,4 /dev/sd1j 9262808 4116710 468295847%/public/file/0 /dev/sd1l 101182217607678515618%/usr/src /dev/sd1m 1035470 1052982646 0%/usr/xenocara --- /dev/sd1j 9262808 4116694 468297447%/public/file/0 /dev/sd1l 101182267928028195271%/usr/src /dev/sd1m 103547049881448488451%/usr/xenocara The main cvsweb seems to confirm the problem is not just in the mirror.
Invalid partition table (was /usr/obj partition AWOL)
On Thu, Jun 07, 2007 at 04:58:18PM -0500, Emilio Perea wrote: On Thu, Jun 07, 2007 at 07:50:24PM +0200, Otto Moerbeek wrote: I have thinking a bit more about the problem, and it is very likely the following scenario happened: 1. Kernel upgrade by source. 2. Reboot 3. Kernel reads old disklabel format and converts it in-memory to the new v1 format. 4. Run a newfs using the old executable that does not know about the new disklabel format. newfs writes the block and fragment size info the old way, on a spot that is used in v1 labels to store the high 16 bits of the offset and size of a partition. The label is written with version = 1, since the in-memory copy is v1. 5. Reboot, the kernel now sees a v1 disklabel with very high offset and/or size, the new consistency code (which is now disabled) kicks in and marks the partition as unused. So the lesson here is: keep userland and kernel in sync, or use a snapshot to upgrade. I believe that's exactly what happened the first time. The catch is that kernel and userland were being built from the same cvs update, and I thought I was keeping them in sync. In this case it would probably have been better to skip the reboot between building the kernel and the userland. It might have been better to start a whole new thread, but it seemed logical to believe that the problems might be related. Using recent snapshots, last night's insecurity output showed another disklabel change: == sd1 diffs (-OLD +NEW) == --- /var/backups/disklabel.sd1.current Fri Apr 20 01:31:19 2007 +++ /var/backups/disklabel.sd1 Fri Jun 8 01:31:55 2007 @@ -1,4 +1,4 @@ -# Inside MBR partition 0: type A6 start 63 size 71681967 +disklabel: warning, DOS partition table with no valid OpenBSD partition # /dev/rsd1c: type: SCSI disk: da0s1 *--* The full output of disklabel and dmesg follow, but as I was getting ready to send it, I remembered that this same disk had problems with the disklabel changes last October. For some reason it was shown as having a FreeBSD disklabel. Most of correspondence regarding it was off-list, but involved several developers and ended with Ken Westerback suggesting some tests before setting it to OpenBSD. This was fdisk then: Disk: sd1 geometry: 4462/255/63 [71682030 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: idC H S -C H S [ start: size ] *0: A60 1 1 - 4461 254 63 [ 63:71681967 ] OpenBSD 1: 000 0 0 -0 0 0 [ 0: 0 ] unused 2: 000 0 0 -0 0 0 [ 0: 0 ] unused 3: 000 0 0 -0 0 0 [ 0: 0 ] unused This is now: Disk: sd1 geometry: 4462/255/63 [71687370 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: idC H S -C H S [ start: size ] 0: 000 0 0 -0 0 0 [ 0: 0 ] unused 1: 000 0 0 -0 0 0 [ 0: 0 ] unused 2: 000 0 0 -0 0 0 [ 0: 0 ] unused *3: A50 0 1 -3 28 41 [ 0: 5 ] FreeBSD *--* It is currently working fine. Should I just change the partition ID to A6, or is there something else I should try first? *--* disklabel: warning, DOS partition table with no valid OpenBSD partition # /dev/rsd1c: type: SCSI disk: da0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 4462 total sectors: 71687370 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 15 partitions: # sizeoffset fstype [fsize bsize cpg] c: 7168196763 unused 0 0 # Cyl 0*- 4461 d: 210445263 4.2BSD 2048 16384 132 # Cyl 0*- 130 e: 8385930 2104515 4.2BSD 2048 16384 328 # Cyl 131 - 652 f: 23294250 48387780 4.2BSD 2048 16384 328 # Cyl 3012 - 4461 h: 4112640 15936480 4.2BSD 2048 16384 256 # Cyl 992 - 1247 i: 2104515 40933620 4.2BSD 2048 163841 # Cyl 2548 - 2678 j: 18828180 20049120 4.2BSD 2048 16384 328 # Cyl 1248 - 2419 k: 5349645 43038135 4.2BSD 2048 16384 16 # Cyl 2679 - 3011 l: 2056320 38877300 4.2BSD 2048 16384 128 # Cyl 2420 - 2547 m: 2104515 10490445 4.2BSD 2048 16384 132 # Cyl 653 - 783
Re: Invalid partition table (was /usr/obj partition AWOL)
On Fri, Jun 08, 2007 at 10:41:40PM -0400, Kenneth R Westerback wrote: This is very odd on several fronts. First, someone has obviously been writing on the MBR for no good reason. I just tested an fdisk compiled to day and noticed no oddities on my i386. Second, the fact that you find a disklabel. Since we no longer store or look for disklabels in FreeBSD partitions it is being read from sector 1 if I recall the code correctly. But it should not have been writing the disklabel there when there was an OpenBSD partition to store it in. Do you know if this is exactly the same disklabel you were using before? Have you changed anything in the disklabel recently that would identify this as an artifact that just happened to be lying in sector 1 for a while? Other than reducing the size of the last partition a couple of months ago, there has been no (intentional) change to that disklabel since: On Wed, Oct 11, 2006 at 08:09:08AM -0700, K WESTERBACK wrote: Darn. A perfectly good theory shot to hell. :-). It would seem that you have a 'valid' disklabel at sector 1 of that disk. First, if you could save the first two sectors of the disk with dd if=/dev/rsd1c of=SaveMySectors bs=512 count=2 and send me that file, and do two experiments, I would appreciate it. If you can run fdisk against the disk and change the partition type to 'A6' (OpenBSD) the correct disklabel should be read in and you should get the 'old' info back again. Second, if you are the risk taking type, change partition type back to 'A5' (FreeBSD) and zero out sector 1 on the disk with something like dd if=/dev/zero of=/dev/rsd1c bs=512 count=1 seek=1 Then see what disklabel says. You should get a simple spoofed disklabel with 'c' and 'i' partitions. Finally, changing the partition type to 'A6' again should give you access to the data. That was the last change I'm aware of. Can you copy the MBR and send it to me. There might be a clue as to what overwrote it. Then I would do fdisk -i and see what happens. This will move the OpenBSD partition to partition 3, but cover the entire disk as your original MBR did. Then see if the disklabel, which should be read from the OpenBSD partition says. I'll send the file attached to the next message, since I assume it would be stripped from the mailing list. After running fdisk -i sd1: # fdisk sd1 Disk: sd1 geometry: 4462/255/63 [71687370 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: idC H S -C H S [ start: size ] 0: 000 0 0 -0 0 0 [ 0: 0 ] unused 1: 000 0 0 -0 0 0 [ 0: 0 ] unused 2: 000 0 0 -0 0 0 [ 0: 0 ] unused *3: A60 1 1 - 4461 254 63 [ 63:71681967 ] OpenBSD It's back as an OpenBSD disklabel, but the c partition still starts at 63 rather than 0: # disklabel sd1 # Inside MBR partition 3: type A6 start 63 size 71681967 # /dev/rsd1c: type: SCSI disk: da0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 4462 total sectors: 71687370 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 15 partitions: # sizeoffset fstype [fsize bsize cpg] c: 7168196763 unused 0 0 # Cyl 0*- 4461 d: 210445263 4.2BSD 2048 16384 132 # Cyl 0*- 130 e: 8385930 2104515 4.2BSD 2048 16384 328 # Cyl 131 - 652 f: 23294250 48387780 4.2BSD 2048 16384 328 # Cyl 3012 - 4461 h: 4112640 15936480 4.2BSD 2048 16384 256 # Cyl 992 - 1247 i: 2104515 40933620 4.2BSD 2048 163841 # Cyl 2548 - 2678 j: 18828180 20049120 4.2BSD 2048 16384 328 # Cyl 1248 - 2419 k: 5349645 43038135 4.2BSD 2048 16384 16 # Cyl 2679 - 3011 l: 2056320 38877300 4.2BSD 2048 16384 128 # Cyl 2420 - 2547 m: 2104515 10490445 4.2BSD 2048 16384 132 # Cyl 653 - 783 n: 2056320 12594960 4.2BSD 2048 163841 # Cyl 784 - 911 Emilio
Re: /usr/obj partition AWOL
On Thu, Jun 07, 2007 at 07:50:24PM +0200, Otto Moerbeek wrote: I have thinking a bit more about the problem, and it is very likely the following scenario happened: 1. Kernel upgrade by source. 2. Reboot 3. Kernel reads old disklabel format and converts it in-memory to the new v1 format. 4. Run a newfs using the old executable that does not know about the new disklabel format. newfs writes the block and fragment size info the old way, on a spot that is used in v1 labels to store the high 16 bits of the offset and size of a partition. The label is written with version = 1, since the in-memory copy is v1. 5. Reboot, the kernel now sees a v1 disklabel with very high offset and/or size, the new consistency code (which is now disabled) kicks in and marks the partition as unused. So the lesson here is: keep userland and kernel in sync, or use a snapshot to upgrade. I believe that's exactly what happened the first time. The catch is that kernel and userland were being built from the same cvs update, and I thought I was keeping them in sync. In this case it would probably have been better to skip the reboot between building the kernel and the userland. I'll take newfs out of my build script (back to rm -rf /usr/obj/*) and try to remember to use newfs before rebooting with a new kernel if I want to avoid the wait. Thanks again! Emilio
Re: /usr/obj partition AWOL
On Tue, Jun 05, 2007 at 07:51:48AM +0200, Otto Moerbeek wrote: There were some validations checkc added to partitions. If a bad partition is found, it will be marked unused. The checks were a little to strict for some cases. A fix for that went in yesterday, so try a new snap. If the problem persists, please report with full disklabel output. The problem showed up on the latest snapshot as of now, which may well have been built before the fix you mention was incorporated. The home PC running -current has not had a problem since Saturday afternoon. The daily insecurity reports show four changes in this partition during the last couple of months. (Note that since this is on /usr/obj on a PC running -current, newfs is run just about every day.) It seems funny that on May 29 the fsize and bsize were changed to 0, but nothing weird happened until the day after they were changed to what appeared to be more reasonable numbers. Anyhow, in case the information is useful, the insecurity messages and current disklabel follow: == sd0 diffs (-OLD +NEW) == --- /var/backups/disklabel.sd0.current Fri Apr 21 01:31:35 2006 +++ /var/backups/disklabel.sd0 Tue Apr 17 01:31:10 2007 @@ -26,4 +26,4 @@ d: 1048128 3144384 4.2BSD 2048 16384 416 # Cyl 1236 - 1647 e: 1048128 4192512 4.2BSD 2048 16384 416 # Cyl 1648 - 2059 f: 8387568 5240640 4.2BSD 2048 16384 480 # Cyl 2060 - 5356 - g: 4139682 13628208 4.2BSD 2048 16384 480 # Cyl 5357 - 6984* + g: 4139682 13628208 4.2BSD 2048 163841 # Cyl 5357 - 6984* == sd0 diffs (-OLD +NEW) == --- /var/backups/disklabel.sd0.current Tue Apr 17 01:31:10 2007 +++ /var/backups/disklabel.sd0 Wed May 30 01:32:08 2007 @@ -26,4 +26,4 @@ d: 1048128 3144384 4.2BSD 2048 16384 416 # Cyl 1236 - 1647 e: 1048128 4192512 4.2BSD 2048 16384 416 # Cyl 1648 - 2059 f: 8387568 5240640 4.2BSD 2048 16384 480 # Cyl 2060 - 5356 - g: 4139682 13628208 4.2BSD 2048 163841 # Cyl 5357 - 6984* + g: 4139682 13628208 4.2BSD 0 01 # Cyl 5357 - 6984* == sd0 diffs (-OLD +NEW) == --- /var/backups/disklabel.sd0.current Wed May 30 01:32:08 2007 +++ /var/backups/disklabel.sd0 Fri Jun 1 01:32:15 2007 @@ -26,4 +26,4 @@ d: 1048128 3144384 4.2BSD 2048 16384 416 # Cyl 1236 - 1647 e: 1048128 4192512 4.2BSD 2048 16384 416 # Cyl 1648 - 2059 f: 8387568 5240640 4.2BSD 2048 16384 480 # Cyl 2060 - 5356 - g: 4139682 13628208 4.2BSD 0 01 # Cyl 5357 - 6984* + g: 4139682 13628208 4.2BSD 2048 81921 # Cyl 5357 - 6984* == sd0 diffs (-OLD +NEW) == --- /var/backups/disklabel.sd0.current Fri Jun 1 01:32:15 2007 +++ /var/backups/disklabel.sd0 Tue Jun 5 01:32:10 2007 @@ -26,4 +26,4 @@ d: 1048128 3144384 4.2BSD 2048 16384 416 # Cyl 1236 - 1647 e: 1048128 4192512 4.2BSD 2048 16384 416 # Cyl 1648 - 2059 f: 8387568 5240640 4.2BSD 2048 16384 480 # Cyl 2060 - 5356 - g: 4139682 13628208 4.2BSD 2048 81921 # Cyl 5357 - 6984* + g: 4139682 13628208 4.2BSD 2048 163841 # Cyl 5357 - 6984* # Inside MBR partition 3: type A6 start 63 size 17767827 # /dev/rsd0c: type: SCSI disk: SCSI disk label: ST39102LW flags: bytes/sector: 512 sectors/track: 212 tracks/cylinder: 12 sectors/cylinder: 2544 cylinders: 6962 total sectors: 17783240 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: # sizeoffset fstype [fsize bsize cpg] a: 209619363 4.2BSD 2048 16384 480 # Cyl 0*- 823 b: 1048128 2096256swap # Cyl 824 - 1235 c: 17783240 0 unused 0 0 # Cyl 0 - 6990* d: 1048128 3144384 4.2BSD 2048 16384 416 # Cyl 1236 - 1647 e: 1048128 4192512 4.2BSD 2048 16384 416 # Cyl 1648 - 2059 f: 8387568 5240640 4.2BSD 2048 16384 480 # Cyl 2060 - 5356 g: 4139682 13628208 4.2BSD 2048 163841 # Cyl 5357 - 6984*
/usr/obj partition AWOL
I follow -current on an i386 at work and an amd64 at home, and rarely run into any problem which is not self-inflicted. So when I had a weird experience this weekend, I assumed it was my fault. What happened was that after the usual sequence of [build kernel; reboot; build userland; reboot] the system complained that it could not fsck wd1j and dropped into single-user mode. wd1j is mounted on /usr/obj, and I thought that something in the last build had messed it up, so I ran newfs wd1j and got newfs: /dev/rwd1j: Device not configured disklabel wd1 showed partitions d-i and k-p, but no j. I added the partition, ran newfs, and everything seemed fine. This afternoon I installed the i386 snapshot downloaded this morning (dated Jun 3 19:19) on the work pc, and after reboot it was missing the /usr/obj partition (sd0g in this case). Everything seems to be working fine on both computers, but I didn't expect the partitions to disappear. Did nobody else run into this problem? Or did everybody else who saw it thought it was too obvious to mention it to the mailing list? Emilio
Re: The British
On Fri, Jun 01, 2007 at 11:52:06AM -0700, Bryan Irvine wrote: In the UK we are not all of this intellect. I'm certain this guy is joking. At least I hope so. ;) I ran a whois on his email, and he appears to be located in Essex. Though the name seems Spanish, so perhaps he's still upset over Cadiz? I think you are all misunderstanding the poor fellow (OP). The name qw er [EMAIL PROTECTED] seems to be derived from a US slang term for his sexual orientation. So it seems likely that sucks slow is intended as a compliment. Let's just say thanks politely and move on. Emilio
Re: Upgrade question
On Mon, May 28, 2007 at 10:13:48PM -0500, Denny White wrote: I've been running a snapshot from several months back got my new 4.1 cds finally. Uname shows OpenBSD 4.1 Generic#0. I want to keep my existing /home /data partitions, delete all the rest, recreate them finish the install. After I reboot, I was hoping I could copy over the old users from the old /etc/group into the new one, copy the old passwd over run pwd_mkdb. Just want to know if I've reasoned it out correctly or not, if it is right if there's anything else I need to run to synchronize things, so on. I've tried looking up that kind of scenario with google, in the mail archives so forth just don't seem to come up with what I need. The point of what I'm trying to accomplish is not to have to copy so much from the 2 aforementioned partitions to another drive then copy it all back after recreating users. Thanks for any help. In these situations I usually keep a copy of /etc in /home/etc.tgz and just do a new install, skipping the /home and /data partitions when running disklabel. It's never a bad idea to have a full backup, though!
Re: CVS hosed
On Thu, May 24, 2007 at 11:33:15AM -0500, Travers Buda wrote: Well since nobody has posted this to misc@ yet, I suppose I will. It's obvious that CVS is currently in a state of being completely hosed. The email I got from the cron job for this morning's csup update has 64,633 Delete lines and 4,611 Rmdir lines. That was a fairly good sign of a hosing. A quick check of http://www.openbsd.org gave a 403 Forbidden message, so I suspect that's the problem. As I understand it, that server is located in Edmonton, and everything there has been hosed since they traded Smyth to the Rangers. :-) I was able to able to get the source from cvsup.usa.openbsd.org before they updated, but it may be too late now. Emilio
Re: General Question about OpenBSD
On Thu, May 24, 2007 at 03:45:37PM -0400, Suzuki Kawasaki wrote: If OpenBSD is the most uber secure why does it run on Solaris? http://www.openbsd.org was running Apache on Solaris when last queried at 18-May-2007 19:52:41 GMT - refresh now Site Report RTFFAQ: http://openbsd.org/faq/faq8.html#wwwsolaris
Re: Troubleshooting NFS/SFU
On Tue, May 15, 2007 at 12:11:00PM -0300, John Nietzsche wrote: i am trying to get my windows boxes access nfs directly by means of SFU, too! I would like to have a global mount, say drive g: to mount from my home directories. Is it possible? How have you been doing in order to get a global drive mapping? I think it might be better to ask in the forums at the SFU website: http://www.interopsystems.com/tools (Unless you are having problems on the OpenBSD side.)
Re: www.openbsd.org (and vs openbsd.org)
On Fri, May 11, 2007 at 12:10:13AM +0200, Martin Toft wrote: Nobody answered my second question though :) Maybe nobody knows the answer? :) Summary: I was once told not to use openbsd.org; it was said that www.openbsd.org was the only valid site (ignoring mirror sites). Is this just bullshit? I think the question was answered indirectly when he mentioned www.openbsd.org being a mirror site. As I understand it, openbsd.org is the root site (probably in Theo's house) but www.openbsd.org is the main mirror located at the university. It has much higher bandwidth so it should be used instead. As a matter of courtesy as well as practicality, you should use www.openbsd.org instead.
Re: make obj broken?
On Fri, May 11, 2007 at 02:43:51AM +0100, Edd Barrett wrote: Just checked out -current sources from rt.fm. It doesn't look like any of the cvs mirrors have recovered. If you think src is bad, take a look at xenocara /dev/wd1i 102963055859041956057%/usr/src /dev/wd1n 2063222 630 1959432 0%/usr/xenocara
Re: OpenBSD 4.0 and ASUS A8V motherboards
On Mon, Jan 01, 2007 at 10:27:55AM +0100, Federico Giannici wrote: I suspect there is some kind of incompatibility between OpenBSD 4.0 (i386 and amd64) and ASUS A8V motherboards. We have a few of these motherboards in use and since we upgraded to OpenBSD 4.0 they freeze from time to time, usually during high IO load (disk or network). I have had similar symptoms with my home PC, which I believe were due to the SATA controller. However, my problems started when I bought it about a year ago, then running 3.8-stable, so they were definitely not due to the 4.0 upgrade. Also, they occurred only when using the amd64 GENERIC.MP kernel (dual core cpu). Unfortunately I have not had the time to troubleshoot it properly. My problem was temporarily resolved by changing the boot drive to a standard IDE drive, and I have not had a lockup for several months. Now I have upgraded my desktop PC (again with ASUS A8V motherboard) that never had any stability problem. Now from time to time the PC goes crazy: it usually freezes for a few seconds and then the mouse start to rapidly move and click by itself. And a couple of time the PC completely freezed. I saw this a couple of times with one X snapshot a few months ago, but not since then. FWIW, this is my dmesg: OpenBSD 4.0-current (GENERIC.MP) #1074: Mon Jan 1 19:26:30 MST 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 2146758656 (2096444K) avail mem = 1834516480 (1791520K) using 22937 buffers containing 214884352 bytes (209848K) of memory mainbus0 (root) bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xf0530 (67 entries) bios0: ASUSTeK Computer Inc. A8V acpi at mainbus0 not configured mainbus0: Intel MP Specification (Version 1.1) cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+, 2002.94 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: apic clock running at 200MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+, 2002.56 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative mpbios: bus 0 is type PCI mpbios: bus 1 is type PCI mpbios: bus 2 is type ISA ioapic0 at mainbus0 apid 2 pa 0xfec0, version 3, 24 pins pci0 at mainbus0 bus 0: configuration mode 1 pchb0 at pci0 dev 0 function 0 VIA K8HTB Host rev 0x00 pchb1 at pci0 dev 0 function 1 VIA K8HTB Host rev 0x00 pchb2 at pci0 dev 0 function 2 VIA K8HTB Host rev 0x00 pchb3 at pci0 dev 0 function 3 VIA K8HTB Host rev 0x00 pchb4 at pci0 dev 0 function 4 VIA K8HTB Host rev 0x00 pchb5 at pci0 dev 0 function 7 VIA K8HTB Host rev 0x00 ppb0 at pci0 dev 1 function 0 VIA K8HTB AGP rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 NVIDIA GeForce FX 5200 rev 0xa1 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) skc0 at pci0 dev 10 function 0 Marvell Yukon 88E8001/8003/8010 rev 0x13, Marvell Yukon Lite (0x9): apic 2 int 17 (irq 11) sk0 at skc0 port A, address 00:13:d4:e3:eb:2a eephy0 at sk0 phy 0: Marvell 88E1011 Gigabit PHY, rev. 5 fxp0 at pci0 dev 13 function 0 Intel 8255x rev 0x05, i82558: apic 2 int 18 (irq 10), address 00:90:27:9c:6e:88 inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 0 pciide0 at pci0 dev 15 function 0 VIA VT6420 SATA rev 0x80: DMA pciide0: using apic 2 int 20 (irq 11) for native-PCI interrupt wd0 at pciide0 channel 0 drive 0: Maxtor 7Y250M0 wd0: 16-sector PIO, LBA48, 239372MB, 490234752 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 wd1 at pciide0 channel 1 drive 0: WDC WD740GD-00FLA2 wd1: 16-sector PIO, LBA48, 70910MB, 145223999 sectors wd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 5 pciide1 at pci0 dev 15 function 1 VIA VT82C571 IDE rev 0x06: ATA133, channel 0 configured to compatibility, channel 1 configured to compatibility wd2 at pciide1 channel 0 drive 0: Maxtor 6L250R0 wd2: 16-sector PIO, LBA48, 239372MB, 490234752 sectors wd2(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 6 atapiscsi0 at pciide1 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: _NEC, DVD_RW ND-3550A, 1.05 SCSI0 5/cdrom removable cd0(pciide1:1:0): using PIO mode 4, Ultra-DMA mode 2 uhci0 at pci0 dev 16 function 0 VIA VT83C572 USB rev 0x81: apic 2 int 21 (irq 5) usb0 at
Re: dhcpd question
On Fri, Dec 15, 2006 at 10:47:32PM +, Craig Skinner wrote: Don't do that. DJB junk is not in ports for good reasons. As far as I know, DJB software is not in ports because his opinions on licensing and filesystem hierarchy are very different from Theo's (and most everybody else's) not because it's junk. There's no reason to avoid it if you know what you are doing and do your homework.
Re: dhcpd question
On Thu, Dec 14, 2006 at 01:47:36PM -0600, Jacob Yocom-Piatt wrote: after having used djbdns for a while i must suggest you not use it. when i used to use it there was some problem where windows machines could not query the server and i would have to restart it. the commands to manipulate djbdns, which do not have manpages AFAICR, and its logs totally suck, IMO. just one more thing to remember when doing admin work. The problem you ran into was probably due to dnscache giving up on long CNAME chains. There is a trivial fix as shown in http://marc.theaimsgroup.com/?t=10942216221r=1w=2 but DJB refuses to fix it on the ground that only idiots would use that method of serving DNS. He is undoubtedly correct, but since the idiots at Akamai have clients such as Microsoft and Yahoo, it is a real problem for those unfortunate enough to have to deal with them. However, as I said before the fix seems to be trivial. I don't know why DJB stopped using man pages, but a couple of people have translated his html docs to man pages, for those of us who prefer them. I don't find the management or log file format to be a problem, but that's just where our personal preferences differ. i've been using the BIND that comes with openbsd for ~6 months now and it works great. not to mention there's also a systrace policy for it sitting in /etc/systrace, in case you're paranoid. there are no superfluous commands to remember either. I haven't had any problem with the OpenBSD version of BIND either. can't say i've tried qmail, but after running djbdns for a while (~1.5 years) i'm very much disinclined to use any of DJB's software. also, if i'm not mistaken, there have been very few updates to djbdns's source during the past 2 years. AFAIK, there haven't been ANY updates in over 5 years. No big deal. Emilio
Re: OpenBSD with Yahoo DSL
On Tue, Nov 21, 2006 at 09:13:30AM -0800, Pawel S. Veselov wrote: I was wondering if anyone was able to create Yahoo login/password without running their CD. As I understand, the DSL installation CD just knows which servers to go to to associate the phone line with the account information, lets you create the user/password, and then stores user/password into the modem (it's a new modem that handles pppoe internally). I guess this shouldn't be impossible, as long as one knows which web site to go to for that account creation part... You have probably been online for a week now, but just in case somebody else runs into this problem, you can use https://sbcreg.sbcglobal.net/ to pick a user name and password to register the DSL line. It will then attempt to install their software, at which point you bail out. That does not have to be done on the DSL line, but if that's the only connection you have and it's pppoe, you can use the temporary registration-only user name and password which is probably already in your modem: Username: [EMAIL PROTECTED] Password: sbcyahooreg After the line is registered go back and put in the username and password you chose. Emilio
Re: Modemsupport?
On Tue, Oct 24, 2006 at 08:23:06PM -0400, STeve Andre' wrote: I have a cardbus modem that I've used for years. The relevant line in the dmesg data is pccom3 at pcmcia1 function 0 U.S. Robotics, XJ/CC1560, Megahertz 56kbps \ Modem port 0xa3f8/8: ns16550a, 16 byte fifo I started to reply to this a month ago, but was interrupted and only now noticed the draft. The variation I've used on several laptops was made by 3Com for Toshiba America, model 3CXM056-BNW and sold by Toshiba under the NoteWorthy name as well as being bundled with many of their laptops. This is an excellent modem, but AFAIK only the Toshiba versions were real modems. The apparently indentical version sold by 3Com themselves was merely a winmodem. Only (some of?) their cellular-interface card modems were real modems. The relevant dmesg line: Toshiba America, 3CXM056-BNW, 3COM/NoteWorthy 56K Modem \ port 0xa3f8/8: ns16550a, 16 byte fifo
Re: Modemsupport?
On Wed, Nov 22, 2006 at 10:29:30AM -0600, Emilio Perea wrote: The relevant dmesg line: Toshiba America, 3CXM056-BNW, 3COM/NoteWorthy 56K Modem \ port 0xa3f8/8: ns16550a, 16 byte fifo Sorry. That should have been: pccom3 at pcmcia1 function 0 Toshiba America, 3CXM056-BNW,\ 3COM/NoteWorthy 56K Modem port 0xa3f8/8: ns16550a, 16 byte fifo
Re: Oldest Server you run
On Thu, Oct 12, 2006 at 08:54:35PM +0200, Falk Husemann wrote: Hello List! We're trying to put an old server to good use again and would like to know what's exactly the oldest machine running OpenBSD? As machine we defined something with processor, ram, network, hard disk and a connection to the internet. So no Newton or toaster (at least not if there's no disk being toasted). The oldest one I have is a 486DX33 with 48Mb of RAM and 2 small IDE drives. It's an old PC which was never intended to be a server, and all it does is dhcp and dns on a small field office. (ISC dhcp and djbdns.) I bought a Soekris net4801 to replace it last year, but took it home instead, since the old one keeps working fine. It's still running 3.6. I'm sure there are older ones (particularly non-i386 hardware) still running.
Disk problem with -current kernel
I ran into a problem when rebooting to a current kernel (i386 GENERIC) due to a secondary disk without an 'a' partition. Disk sd0 checked out fine, but all the partitions on sd1 had bad magic numbers and failed fsck: /dev/rsd1d: BAD SUPER BLOCK: MAGIC NUMBER WRONG /dev/rsd1d: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY. ... /dev/rsd1n: BAD SUPER BLOCK: MAGIC NUMBER WRONG /dev/rsd1n: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY. Old disklabel sd1: # Inside MBR partition 0: type A5 start 63 size 71681967 # /dev/rsd1c: type: SCSI disk: da0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 4462 total sectors: 71687370 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 15 partitions: # sizeoffset fstype [fsize bsize cpg] c: 7168196763 unused 0 0 # Cyl 0*- 4461 d: 210445263 4.2BSD 2048 16384 132 # Cyl 0*- 130 e: 8385930 2104515 4.2BSD 2048 16384 328 # Cyl 131 - 652 f: 23294250 48387780 4.2BSD 2048 16384 328 # Cyl 3012 - 4461 h: 4112640 15936480 4.2BSD 2048 16384 256 # Cyl 992 - 1247 i: 2104515 40933620 4.2BSD 2048 16384 132 # Cyl 2548 - 2678 j: 18828180 20049120 4.2BSD 2048 16384 328 # Cyl 1248 - 2419 k: 5349645 43038135 4.2BSD 2048 16384 16 # Cyl 2679 - 3011 l: 2056320 38877300 4.2BSD 2048 16384 128 # Cyl 2420 - 2547 m: 2104515 10490445 4.2BSD 2048 16384 132 # Cyl 653 - 783 n: 3341520 12594960 4.2BSD 2048 16384 208 # Cyl 784 - 991 New disklabel sd1: # Inside MBR partition 0: type A5 start 63 size 71681967 # /dev/rsd1c: type: SCSI disk: SCSI disk label: ST336705LW flags: bytes/sector: 512 sectors/track: 470 tracks/cylinder: 8 sectors/cylinder: 3760 cylinders: 19036 total sectors: 71687370 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: # sizeoffset fstype [fsize bsize cpg] c: 71687370 0 unused 0 0 # Cyl 0 - 19065* d: 2097000 34314840 4.2BSD 1024 8192 16 # Cyl 9126*- 9683 e: 1049040 36411840 4.2BSD 1024 8192 16 # Cyl 9684 - 9962 f: 4196160 37460880 4.2BSD 1024 8192 16 # Cyl 9963 - 11078 g: 4196160 41657040 4.2BSD 1024 8192 16 # Cyl 11079 - 12194 h: 8388560 45853200 4.2BSD 1024 8192 16 # Cyl 12195 - 14425 i:53008263 ext2fs # Cyl 0*- 140* j: 1060290 16466625 unknown # Cyl 4379*- 4661* k: 16787925 17526915 ext2fs # Cyl 4661*- 9126* l: 15936480530145 ext2fs # Cyl 140*- 4379* I assume this is due to using the new kernel with the old fsck and that installing the next snapshot will fix it. If this is unexpected, please let me know if you want additional information. Last dmesg, just in case... OpenBSD 4.0-current (GENERIC) #1141: Sun Oct 8 13:54:04 MDT 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) 4 CPU 1500MHz (GenuineIntel 686-class) 1.50 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM real mem = 804384768 (785532K) avail mem = 725274624 (708276K) using 4256 buffers containing 40341504 bytes (39396K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(00) BIOS, date 06/06/01, BIOS32 rev. 0 @ 0xffe90, SMBIOS rev. 2.3 @ 0xf0450 (97 entries) bios0: Dell Computer Corporation Precision 330 apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown apm0: flags 30102 dobusy 0 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfbbb0/176 (9 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82801BA LPC rev 0x00) pcibios0: PCI bus #2 is the last bus bios0: ROM list: 0xc/0xa800 0xca800/0x5800 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82850 Host rev 0x02 ppb0 at pci0 dev 1 function 0 Intel 82850/82860 AGP rev 0x02 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 NVIDIA Vanta rev 0x15 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ppb1 at pci0 dev 30 function 0 Intel 82801BA AGP rev 0x04 pci2 at ppb1 bus 2 fxp0 at pci2 dev 8 function 0 Intel 8255x rev 0x05, i82558: irq 10, address 00:90:27:86:21:9c inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 0 ahc0 at pci2 dev 10 function 0 Adaptec AHA-2940U2 U2 rev 0x00: irq 11
Re: Disk problem with -current kernel
On Tue, Oct 10, 2006 at 07:01:21PM -0400, Nick Holland wrote: Emilio Perea wrote: I ran into a problem when rebooting to a current kernel (i386 GENERIC) due to a secondary disk without an 'a' partition. I don't think the lack of an 'a' partition is your problem. Goodness knows, I've got a lot of machines with no 'a' partition on the second and later disks. No, the problem was due to sd1's MBR partition type being A5 rather than A6. My apologies for not checking that before posting. Last night's change to disksubr.c broke it. Thanks to Thordur and Pedro and Ken and you for help in tracking this down. I borrowed this disk from a dead server over five years ago and had forgotten that I had not fdisk'd it at the time. It's been running OpenBSD since 2.8... Mea culpa! Emilio
Re: Custom kernel for Soekris net4801-50
On Wed, Oct 04, 2006 at 11:44:30AM -0700, Richard P. Koett wrote: Based on other people's responses it sounds like no kernel customization is even required on this device. I started out using flashdist on mine, but switched to a standard installation on a 1G flash card (/ mounted rw,noatime,softdep). I really couldn't tell the difference using standard DSL speed tests so I saw no point in using a special kernel. OpenBSD 3.9-stable (EP) #627: Sat Aug 19 21:22:41 CDT 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/EP cpu0: Geode(TM) Integrated Processor by National Semi (Geode by NSC 586-class) 267 MHz cpu0: FPU,TSC,MSR,CX8,CMOV,MMX cpu0: TSC disabled real mem = 133799936 (130664K) avail mem = 115363840 (112660K) using 1658 buffers containing 6791168 bytes (6632K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(00) BIOS, date 20/50/29, BIOS32 rev. 0 @ 0xf7840 pcibios0 at bios0: rev 2.0 @ 0xf/0x1 pcibios0: pcibios_get_intr_routing - function not supported pcibios0: PCI IRQ Routing information unavailable. pcibios0: PCI bus #0 is the last bus bios0: ROM list: 0xc8000/0x9000 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Cyrix GXm PCI rev 0x00 sis0 at pci0 dev 6 function 0 NS DP83815 10/100 rev 0x00, DP83816A: irq 10, address 00:00:24:c2:9e:30 nsphyter0 at sis0 phy 0: DP83815 10/100 PHY, rev. 1 sis1 at pci0 dev 7 function 0 NS DP83815 10/100 rev 0x00, DP83816A: irq 10, address 00:00:24:c2:9e:31 nsphyter1 at sis1 phy 0: DP83815 10/100 PHY, rev. 1 sis2 at pci0 dev 8 function 0 NS DP83815 10/100 rev 0x00, DP83816A: irq 10, address 00:00:24:c2:9e:32 nsphyter2 at sis2 phy 0: DP83815 10/100 PHY, rev. 1 gscpcib0 at pci0 dev 18 function 0 NS SC1100 ISA rev 0x00 gpio0 at gscpcib0: 64 pins NS SC1100 SMI rev 0x00 at pci0 dev 18 function 1 not configured pciide0 at pci0 dev 18 function 2 NS SCx200 IDE rev 0x01: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: SanDisk SDCFH-1024 wd0: 1-sector PIO, LBA, 977MB, 2001888 sectors wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 geodesc0 at pci0 dev 18 function 5 NS SC1100 X-Bus rev 0x00: iid 6 revision 3 wdstatus 0 ohci0 at pci0 dev 19 function 0 Compaq USB OpenHost rev 0x08: irq 11, version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: Compaq OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered isa0 at gscpcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 nsclpcsio0 at isa0 port 0x2e/2: NSC PC87366 rev 9: GPIO VLM TMS gpio1 at nsclpcsio0: 29 pins gscsio0 at isa0 port 0x15c/2: SC1100 SIO rev 1: npx0 at isa0 port 0xf0/16: using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom0: console pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo biomask fbe5 netmask ffe5 ttymask ffe7 pctr: no performance counters in CPU dkcsum: wd0 matches BIOS drive 0x80 root on wd0a rootdev=0x0 rrootdev=0x300 rawdev=0x302
Re: mbuf leak with rl
On Thu, Sep 14, 2006 at 10:38:35AM -0500, Karle, Chris wrote: If you're using a rl* can you take a look at your mbuf usage (netstat -m)? Me and another person both see something similar. OpenBSD 3.9-stable (i386 GENERIC) % dmesg | grep rl rl0 at pci0 dev 14 function 0 Realtek 8139 rev 0x10: irq 11, address 00:30:1b:0f:e1:aa rlphy0 at rl0 phy 0: RTL internal PHY % netstat -m 75 mbufs in use: 69 mbufs allocated to data 2 mbufs allocated to packet headers 4 mbufs allocated to socket names and addresses 68/146/6144 mbuf clusters in use (current/peak/max) 344 Kbytes allocated to network (44% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines
Re: Anyone using a Asus K8N-VM or A8V-VM?
On Thu, Jun 22, 2006 at 09:01:07AM +0200, Jasper Lievisse Adriaanse wrote: just a quick question, anyone running OpenBSD/amd64 on an Asus A8N-VM or A8V-VM motherboard? Things that work/don't work? I have been using an Asus A8V since February. Had lots of problems at first, which seem to have been due to the use of the multiprocessor kernel with a PS/2 keyboard and mouse. Had no problems with the plain bsd kernel, but it would freeze frequently with bsd.mp. Changed memory, disk drives, video card and NIC, finally motherboard. Nothing helped. Changing my favorite Keytronic keyboard for a cheap Dell USB keyboard, and have had no problems since. I have noticed reports of problems with some servers with PS/2 keyboards and bsd.mp on this list, so whatever caused this may have been fixed in current, but I have not tried switching back to PS/2 keyboards. May do that this weekend if I get a chance. I have not used the sound card, so can't tell you if it works well, but everything else does now. dmesg follows (EP is just a link to GENERIC.MP): OpenBSD 3.9-current (EP) #857: Fri Jun 23 08:25:59 CDT 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/EP real mem = 2146758656 (2096444K) avail mem = 1846722560 (1803440K) using 22937 buffers containing 214884352 bytes (209848K) of memory mainbus0 (root) bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xf0530 (67 entries) bios0: ASUSTeK Computer Inc. A8V mainbus0: Intel MP Specification (Version 1.1) (ASUSTeK ) cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+, 2002.93 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: apic clock running at 200MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+, 2002.56 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative mpbios: bus 0 is type PCI mpbios: bus 1 is type PCI mpbios: bus 2 is type ISA ioapic0 at mainbus0 apid 2 pa 0xfec0, version 3, 24 pins pci0 at mainbus0 bus 0: configuration mode 1 pchb0 at pci0 dev 0 function 0 VIA K8HTB Host rev 0x00 pchb1 at pci0 dev 0 function 1 VIA K8HTB Host rev 0x00 pchb2 at pci0 dev 0 function 2 VIA K8HTB Host rev 0x00 pchb3 at pci0 dev 0 function 3 VIA K8HTB Host rev 0x00 pchb4 at pci0 dev 0 function 4 VIA K8HTB Host rev 0x00 pchb5 at pci0 dev 0 function 7 VIA K8HTB Host rev 0x00 ppb0 at pci0 dev 1 function 0 VIA K8HTB AGP rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 NVIDIA GeForce FX 5200 rev 0xa1 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) skc0 at pci0 dev 10 function 0 Marvell Yukon 88E8001/8003/8010 rev 0x13, Marvell Yukon Lite (0x9): apic 2 int 17 (irq 11) sk0 at skc0 port A, address 00:13:d4:e3:eb:2a eephy0 at sk0 phy 0: Marvell 88E1011 Gigabit PHY, rev. 5 fxp0 at pci0 dev 13 function 0 Intel 8255x rev 0x05, i82558: apic 2 int 18 (irq 10), address 00:90:27:9c:6e:88 inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 0 pciide0 at pci0 dev 15 function 0 VIA VT6420 SATA rev 0x80: DMA pciide0: using apic 2 int 20 (irq 11) for native-PCI interrupt wd0 at pciide0 channel 0 drive 0: Maxtor 7Y250M0 wd0: 16-sector PIO, LBA48, 239372MB, 490234752 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 wd1 at pciide0 channel 1 drive 0: WDC WD740GD-00FLA2 wd1: 16-sector PIO, LBA48, 70910MB, 145223999 sectors wd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 5 pciide1 at pci0 dev 15 function 1 VIA VT82C571 IDE rev 0x06: ATA133, channel 0 configured to compatibility, channel 1 configured to compatibility atapiscsi0 at pciide1 channel 0 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: _NEC, DVD_RW ND-3550A, 1.05 SCSI0 5/cdrom removable cd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 2 pciide1: channel 1 disabled (no drives) uhci0 at pci0 dev 16 function 0 VIA VT83C572 USB rev 0x81: apic 2 int 21 (irq 5) usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: VIA UHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1 at pci0 dev 16 function 1 VIA VT83C572 USB rev 0x81: apic 2 int 21 (irq 5) usb1 at uhci1: USB revision 1.0 uhub1 at usb1 uhub1: VIA UHCI root hub, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2 at pci0
Re: Feb 13 X snapshot
On Wed, Feb 15, 2006 at 03:38:32PM -0700, Peter Valchev wrote: The Feb 15 X snapshot should have this fixed. The keyboard issue is fixed, but now mouse buttons don't work. #dmesg OpenBSD 3.9-beta (GENERIC) #602: Wed Feb 15 17:33:53 MST 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) 4 CPU 1500MHz (GenuineIntel 686-class) 1.50 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM real mem = 804397056 (785544K) avail mem = 726593536 (709564K) using 4278 buffers containing 40321024 bytes (39376K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(00) BIOS, date 06/06/01, BIOS32 rev. 0 @ 0xffe90 apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown apm0: flags 30102 dobusy 0 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfbbb0/176 (9 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82801BA LPC rev 0x00) pcibios0: PCI bus #2 is the last bus bios0: ROM list: 0xc/0xa800 0xca800/0x5800 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82850 Host rev 0x02 ppb0 at pci0 dev 1 function 0 Intel 82850/82860 AGP rev 0x02 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 NVIDIA Vanta rev 0x15 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ppb1 at pci0 dev 30 function 0 Intel 82801BA AGP rev 0x04 pci2 at ppb1 bus 2 fxp0 at pci2 dev 8 function 0 Intel 8255x rev 0x05, i82558: irq 10, address 00:90:27:86:21:9c inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 0 ahc0 at pci2 dev 10 function 0 Adaptec AHA-2940U2 U2 rev 0x00: irq 11 scsibus0 at ahc0: 16 targets sd0 at scsibus0 targ 0 lun 0: SEAGATE, ST39102LW, 0005 SCSI2 0/direct fixed sd0: 8683MB, 6962 cyl, 12 head, 212 sec, 512 bytes/sec, 17783240 sec total sd1 at scsibus0 targ 2 lun 0: SEAGATE, ST336705LW, 5063 SCSI3 0/direct fixed sd1: 35003MB, 19036 cyl, 8 head, 470 sec, 512 bytes/sec, 71687370 sec total cd0 at scsibus0 targ 4 lun 0: YAMAHA, CRW8824S, 1.00 SCSI2 5/cdrom removable cd1 at scsibus0 targ 6 lun 0: TEAC, CD-ROM CD-532S, 1.0A SCSI2 5/cdrom removable ichpcib0 at pci0 dev 31 function 0 Intel 82801BA LPC rev 0x04 pciide0 at pci0 dev 31 function 1 Intel 82801BA IDE rev 0x04: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: IC35L040AVER07-0 wd0: 16-sector PIO, LBA, 38166MB, 78165360 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 pciide0: channel 1 ignored (disabled) uhci0 at pci0 dev 31 function 2 Intel 82801BA USB rev 0x04: irq 11 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ichiic0 at pci0 dev 31 function 3 Intel 82801BA SMBus rev 0x04: irq 10 iic0 at ichiic0 uhci1 at pci0 dev 31 function 4 Intel 82801BA USB rev 0x04: irq 9 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 uhub1: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered auich0 at pci0 dev 31 function 5 Intel 82801BA AC97 rev 0x04: irq 10, ICH2 AC97 ac97: codec id 0x41445360 (Analog Devices AD1885) ac97: codec features headphone, Analog Devices Phat Stereo audio0 at auich0 isa0 at ichpcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pmsi0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pmsi0 mux 0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 npx0 at isa0 port 0xf0/16: using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec biomask ef65 netmask ef65 ttymask ffe7 pctr: user-level cycle counter enabled ahc0: target 0 using 16bit transfers ahc0: target 0 synchronous at 20.0MHz, offset = 0xf dkcsum: sd0 matches BIOS drive 0x80 ahc0: target 2 using 16bit transfers ahc0: target 2 synchronous at 20.0MHz, offset = 0x3f dkcsum: sd1 matches BIOS drive 0x82 wd0: no disk label dkcsum: wd0 matches BIOS drive 0x81 root on sd0a rootdev=0x400 rrootdev=0xd00 rawdev=0xd02 #/var.log/Xorg.0.log (--) checkDevMem: using aperture driver /dev/xf86 (--) Using wscons driver in pcvt compatibility mode (version 3.32) (WW) GARTInit: AGPIOC_INFO failed (Device not configured) X Window System Version 6.9.0 (for OpenBSD) Release Date: 21 December 2005 X Protocol Version 11, Revision 0, Release 6.9 Build Operating System: OpenBSD 3.9 i386 [ELF] Current Operating System: OpenBSD herakles.walkereng.net 3.9 GENERIC#602 i386 Build Date: 15 February 2006 Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version.
Feb 13 X snapshot
Installing the latest (Feb 13) i386 x*tgz on two different computers caused the keyboard to lock up. Mouse continued to work, but I was not able to type anything or switch consoles. The systems involved were a Dell Precision 330 workstation (upgrade) and a Toshiba 3480CT laptop (new install to see if the problem could be duplicated). Both are several years old and had run X without problems until today. Going back to the Feb 4 snapshot restored full functionality. It seems extremely unlikely that this could be a real bug, since nobody else has mentioned it, so I suspect operator error. Did I miss a required change in configuration between these two versions?
Re: OpenBSD on Dell Dimension 2400 or 3000?
On Tue, Aug 16, 2005 at 11:32:49PM -0500, Emilio Perea wrote: I've run OpenBSD on a Dimension 2400 for a short time without problems. Will send you a dmesg if I find one available in the morning. Unfortunately, I was not able to find an unused one to install OpenBSD on, but this is the dmesg from the 3.7 boot CD: OpenBSD 3.7 (RAMDISK_CD) #573: Sun Mar 20 00:27:05 MST 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD cpu0: Intel(R) Celeron(R) CPU 2.40GHz (GenuineIntel 686-class) 2.40 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,CNXT-ID real mem = 266399744 (260156K) avail mem = 237285376 (231724K) using 3277 buffers containing 13422592 bytes (13108K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(00) BIOS, date 12/02/03, BIOS32 rev. 0 @ 0xffe90 apm0 at bios0: Power Management spec V1.2 pcibios0 at bios0: rev 2.1 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfeae0/144 (7 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82801DB LPC rev 0x00) pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc/0xb800 0xcb800/0x1800! 0xcd000/0x3000 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82845G/GL rev 0x01 vga1 at pci0 dev 2 function 0 Intel 82845G/GL Video rev 0x01 wsdisplay0 at vga1: console (80x25, vt100 emulation) uhci0 at pci0 dev 29 function 0 Intel 82801DB USB rev 0x01: irq 11 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1 at pci0 dev 29 function 1 Intel 82801DB USB rev 0x01: irq 10 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2 at pci0 dev 29 function 2 Intel 82801DB USB rev 0x01: irq 9 usb2 at uhci2: USB revision 1.0 uhub2 at usb2 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0 at pci0 dev 29 function 7 Intel 82801DB USB rev 0x01: irq 5 ehci0: EHCI version 1.0 ehci0: companion controllers, 2 ports each: uhci0 uhci1 uhci2 usb3 at ehci0: USB revision 2.0 uhub3 at usb3 uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: single transaction translator uhub3: 6 ports with 6 removable, self powered ppb0 at pci0 dev 30 function 0 Intel 82801BA AGP rev 0x81 pci1 at ppb0 bus 1 bce0 at pci1 dev 9 function 0 Broadcom BCM4401 rev 0x01: irq 3, address 00:0d:56:62:3b:67 bmtphy0 at bce0 phy 1: BCM4401 10/100baseTX PHY, rev. 0 ichpcib0 at pci0 dev 31 function 0 Intel 82801DB LPC rev 0x01 pciide0 at pci0 dev 31 function 1 Intel 82801DB IDE rev 0x01: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: ST380011A wd0: 16-sector PIO, LBA48, 76293MB, 15625 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: SAMSUNG, CD-ROM SC-148A, B402 SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 Intel 82801DB SMBus rev 0x01 at pci0 dev 31 function 3 not configured Intel 82801DB AC97 rev 0x01 at pci0 dev 31 function 5 not configured isa0 at ichpcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0 (mux 1 ignored for console): console keyboard, using wsdisplay0 npx0 at isa0 port 0xf0/16: using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec biomask ffe5 netmask ffed ttymask ffef rd0: fixed, 3800 blocks wd0: no disk label root on rd0a rootdev=0x1100 rrootdev=0x2f00 rawdev=0x2f02
Re: OpenBSD on Dell Dimension 2400 or 3000?
On Tue, Aug 16, 2005 at 09:59:24PM -0500, Kevin wrote: Looking at the Dell Dimension line (probably the 2400 or 3000) one concern is that I don't see *any* reports, success or failure, running OpenBSD on this particular product? I've run OpenBSD on a Dimension 2400 for a short time without problems. Will send you a dmesg if I find one available in the morning.
Re: The windows world is catching on!
On Thu, Jul 21, 2005 at 09:48:21PM -0400, Steve Shockley wrote: On Thu, Jul 21, 2005 at 07:34:01PM +0100, Sevan / Venture37 wrote: http://support.microsoft.com/default.aspx?scid=kb;en-us;555372 You could post a URL that actually works.. They took it down, but the KB article was How to ask a question. The text of the article seems to be reproduced at http://www.petri.co.il/how_to_ask_a_question.htm. Those darned hackers and open source enthusiasts. They also list the current URL: http://support.microsoft.com/kb/555375 It seems like an excellent article for Windows sufferers, and is quite readable with lynx. My favorite point is: Do you have current backups? Why not?
Re: djbdns DNS server? Status, Pros and Cons?
On Tue, May 24, 2005 at 11:25:35PM +0200, Anders Jvnsson wrote: Hello folks. I recently bought a very good book: Mastering FreeBSD and OpenBSD security They have a chapter dealing with DNS servers and there they mention djbdns, they think it has some strong point s so I am somewhat curios about if anybody out there has any viewpoint about using this instead of BIND, especially since the last version djbdns I found was from 2001??! I can't believe that it is so good that it is no need to patch it now and then? I use djbdns on OpenBSD, and don't know anything that needs patching for my uses. However, I don't do ipv6. There is a patch to do that, but if I needed ipv6 support I'd probably stick with OpenBSD's version of BIND. (At least until djb gets around to supporting ipv6.) It will never be part of OpenBSD due to license and hier conflicts, but it's trivial to add it if you'd like to try it.
Re: daily output
On Sat, Apr 30, 2005 at 03:00:40PM +0500, [EMAIL PROTECTED] wrote: a portion of daily output: ... mail: 27 Apr 2005 02:24:28 GMT #1834485 9664 remote [EMAIL PROTECTED] 24 Apr 2005 00:16:13 GMT #1834467 3474 remote [EMAIL PROTECTED] 27 Apr 2005 02:25:39 GMT #1834491 9652 remote [EMAIL PROTECTED] ... what is that is someone injecting mail to me? i use qmail as mailer Those are queued bounce messages. Most likely, somebody is sending spam to a non-existent user in your domain using [EMAIL PROTECTED] as the envelope sender address. The delivery fails, so qmail bounces them, but the yahoo.co.kr mail server does not accept them. If you need more information, the qmail list would be a good place to ask.
