Re: Alpha Disklabel Question
On Fri, Dec 16, 2005 at 07:48:36PM -0500, Nick Holland wrote: Well, I guess I know how I'll be spending my Friday night... (once I get the lasagna out of the keyboard) Nick. heh heh heh. thanks, jmc
CM9 problems with 802.11g (mode 11g)
Hello, I believe this report is related to the one archived on: http://marc.theaimsgroup.com/?l=openbsd-miscm=113292366519249w=2 Where Robert Stepanek reports an issue with 11ag modes. However, my report is limited to 11g by itself, since I cannot verify the 11a mode. The issue is simple. I configure the Wistron NeWeb CM9 card for 11b mode in hostap, and NetStumbler picks it up just fine. I can connect, pass data, all that good stuff. The instant that I switch it to 11g mode (be it live or after a fresh reboot's initial config) the AP goes off the air (or doesn't get on the air in the case of fresh boot). I'm using the OBSD 3.8 WRAP image available at: http://www.yawarra.com.au/sw-osimages.php Can anyone with CM9 hardware duplicate or refute this claim? Thanks, Bart Kus
Re: finding duplicate files
On 2005-12-16 17:18:09 -0800, Smith wrote: Is there any unix utility or script or OpenBSD port that will find duplicate binary files within a directory? Google for uniqleaf Best Martin -- http://www.tm.oneiros.de
Re: CM9 problems with 802.11g (mode 11g)
On Sat, Dec 17, 2005 at 02:23:00AM -0600, Bart Kus wrote: Hello, I believe this report is related to the one archived on: http://marc.theaimsgroup.com/?l=openbsd-miscm=113292366519249w=2 Where Robert Stepanek reports an issue with 11ag modes. However, my report is limited to 11g by itself, since I cannot verify the 11a mode. The issue is simple. I configure the Wistron NeWeb CM9 card for 11b mode in hostap, and NetStumbler picks it up just fine. I can connect, pass data, all that good stuff. The instant that I switch it to 11g mode (be it live or after a fresh reboot's initial config) the AP goes off the air (or doesn't get on the air in the case of fresh boot). I'm using the OBSD 3.8 WRAP image available at: http://www.yawarra.com.au/sw-osimages.php Can anyone with CM9 hardware duplicate or refute this claim? 11g modes are not yet supported on ath, 11b or 11a only iirc.
Re: stuck on upgrading from 3.7 to 3.8 - Exception handling flag day
Oh give it up. You are clearly not skilled enough to even compile code, let alone provide consulting services. Everytime Theo speaks, I have some new quote materal. woo
root / wheel login incorrect ??
Hi, .. I gotta very confusing problem running OpenBSD. I've installed OpenBSD at a mashine and where able to do anything I wanted to ( just have added an user in the wheel group an another in the user group ) Then I tried to log in from network as root via ssh. Didn't work since I've forgotten to allow root-login in sshd_config. As I wanted to locally log in as root to change the configuration file - it doesn't work.. I wasn't able to log in any more .. even not locally.. Login: root Password: Login incorrect ... tried it a few times without any success... I really didn't forget my password. I've searched for any solutions in the internet a whole day. I tried empty password, I tried Root instead of root no success. The user in the wheel group - same story. Only the user in the user group works. WTF?? (I cannot su or /usr/bin/login for root with that user, since it is not in the wheel group..) Just used OpenBSD for 10 minutes and destroed it... that makes me sad ;-) - Sarah Connor, Moshammer oder Papst Benedikt die Top-Suchen 2005.
Re: Alpha Disklabel Question
On 12/16/05, Nick Holland [EMAIL PROTECTED] wrote: On i386, that statement is STILL wrong, though you will be digging up either some unusual historic hardware or some really unusual devices for there to be an issue. Still, that's just wrong. On i386, it is NOT 63 sectors, it is one (logical) track. On modern (500M) hard disks, one logical track is 63 sectors, but that was not always the case, and I don't think it has to be the case now for small storage devices. This is true -- I have a 32MB USB key which reports its (fake) geometry as 'sd2: 31MB, 31 cyl, 64 head, 32 sec, 512 bytes/sec, 64000 sec total'. Funny thing is, the FAT partition on it still starts at a 63-sector offset. I suppose I could repartition it to gain an extra 16kB if I really wanted to. :-) I was about to enclose dmesg/fdisk/disklabel, but I see you have already described a similar device (also 32 sec/track) in 14.17. -Andrew
Re: root / wheel login incorrect ??
On Sat, Dec 17, 2005 at 11:12:40AM +0100, Stefan Wvhrer wrote: Hi, .. I gotta very confusing problem running OpenBSD. I've installed OpenBSD at a mashine and where able to do anything I wanted to ( just have added an user in the wheel group an another in the user group ) Then I tried to log in from network as root via ssh. Didn't work since I've forgotten to allow root-login in sshd_config. As I wanted to locally log in as root to change the configuration file - it doesn't work.. I wasn't able to log in any more .. even not locally.. Login: root Password: Login incorrect ... tried it a few times without any success... I really didn't forget my password. I've searched for any solutions in the internet a whole day. I tried empty password, I tried Root instead of root no success. The user in the wheel group - same story. Only the user in the user group works. WTF?? (I cannot su or /usr/bin/login for root with that user, since it is not in the wheel group..) Just used OpenBSD for 10 minutes and destroed it... that makes me sad ;-) boot OpenBSD in single user mode and change root password or search for changes( maybe /var/backups will help). P.S. remember to mount root partition in r/w( or even mount -a) while in single user mode. - Lukasz Sztachanski -- 0x058B7133 // 16AB 4EBC 29DA D92D 8DBE BC01 FC91 9EF7 058B 7133 http://szati.blogspot.com http://szati.entropy.pl
Re: Odd routing problem ?
On 12/16/05, Bryan Irvine [EMAIL PROTECTED] wrote: traceroute is your friend. I'm sure you've tried it, just didn't post the results? It doesn't show any hop. Like ping, we only see packets coming into wireless interface of gwA, and they don't ever come out of it. -- Fernando M. Braga
Re: stuck on upgrading from 3.7 to 3.8 - Exception handling flag day
Hello! On Fri, Dec 16, 2005 at 03:46:21PM -0700, Theo de Raadt wrote: [...] What do you suggest? Because the only other alternative is to DELETE the upgrade faq. Please don't. There're people who use the upgrade FAQ as it's intended (i.e. one may try it out, but one is on one's own, if things fail and one can't fix it, use binaries to get close to the revision(s) one wants to compile, i.e. the release binaries to get to stable, the latest snapshot to possibly get to current). [...] Kind regards, Hannah.
Re: Alpha Disklabel Question
J.C. Roberts [EMAIL PROTECTED] wrote: On Fri, 16 Dec 2005 23:36:34 +0100 (CET), Tamas TEVESZ [EMAIL PROTECTED] wrote: On Fri, 16 Dec 2005, J.C. Roberts wrote: (1) When booting the cd38.iso with either bsd or bsd.rd you go into UKC rather than directly into the installation. I'm guessing this is normal since I'm sure there might be some things that need doing for some of the more esoteric alpha hardware but it's worth asking to make sure. you probably have a rogue `-s' in boot_osflags (try `show boot_osflags' or even `show boot*' in srm). Without an OS installed and booting from CD through the SRM the INSTALL.alpha file suggests/requires overriding the both the SRM boot file (-fi switch) and the SRM boot flags (-fl switch): boot -fi bsd -fl ac dka0 Frightening... I added the c to the boot flags as instructed and didn't even notice it. Eventually, the boot_osflags in the SRM needs to be set to a but the default is A -The case would make no difference for some OS's but OpenBSD probably won't like it. ;-) SRM specification requires us to handle the flags equally, regardless of case.
OpenBSD beep
I've installed OpenBSD on my small server, before on server was linux, and 2-3 times a day my server beeps (3 times)... What does it mean? And how I can control this beeps?
Re: OpenBSD beep
On Sat, 17 Dec 2005 17:12:58 +0300 dimaz [EMAIL PROTECTED] wrote: I've installed OpenBSD on my small server, before on server was linux, and 2-3 times a day my server beeps (3 times)... What does it mean? And how I can control this beeps? Have you checked your logs for anything out of the normal? Maybe a dmesg might be helpfull? Jasper -- Security is decided by quality -- Theo de Raadt [demime 1.01d removed an attachment of type application/pgp-signature]
Re: Alpha Disklabel Question
On Fri, 16 Dec 2005 13:50:48 -0800, J.C. Roberts [EMAIL PROTECTED] wrote: (2) When doing the installation disklabel, the suggested starting offset for the 'a' partition is 0? I know using an offset of 0 is discouraged on i386 and other systems (default is 63), so I figured I'd ask if using a 0 offset is the best/correct way for alpha? Just for those searching the misc@ archives... I received info off-list that disklabel is doing the right thing by using an offset of 0 on the alpha architecture. -- jcr
Re: OpenBSD beep
Jasper Lievisse Adriaanse wrote: On Sat, 17 Dec 2005 17:21:39 +0300 dimaz [EMAIL PROTECTED] wrote: Jasper Lievisse Adriaanse wrote: On Sat, 17 Dec 2005 17:12:58 +0300 dimaz [EMAIL PROTECTED] wrote: I've installed OpenBSD on my small server, before on server was linux, and 2-3 times a day my server beeps (3 times)... What does it mean? And how I can control this beeps? Have you checked your logs for anything out of the normal? Maybe a dmesg might be helpfull? Jasper I've checked my root mailbox my /var/log/secure and /var/log/messages and nothing found... Please say so too on [EMAIL PROTECTED] It would help _a lot_ if you also posted your dmesg to misc@ so we know at least what platform you are using! Sorry... :) dmesg: OpenBSD 3.8 (GENERIC) #138: Sat Sep 10 15:41:37 MDT 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Celeron (GenuineIntel 686-class, 128KB L2 cache) 501 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real mem = 200908800 (196200K) avail mem = 176447488 (172312K) using 2478 buffers containing 10149888 bytes (9912K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(2a) BIOS, date 12/28/99, BIOS32 rev. 0 @ 0xfb010 apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown apm0: flags 70102 dobusy 1 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xf/0xb648 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf00/144 (7 entries) pcibios0: PCI Exclusive IRQs: 11 15 pcibios0: PCI Interrupt Router at 000:07:0 (Intel 82371SB ISA rev 0x00) pcibios0: PCI bus #1 is the last bus cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82443BX AGP rev 0x03 ppb0 at pci0 dev 1 function 0 Intel 82443BX AGP rev 0x03 pci1 at ppb0 bus 1 pcib0 at pci0 dev 7 function 0 Intel 82371AB PIIX4 ISA rev 0x02 pciide0 at pci0 dev 7 function 1 Intel 82371AB IDE rev 0x01: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: SAMSUNG SP0802N wd0: 16-sector PIO, LBA48, 76351MB, 156368016 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 pciide0: channel 1 ignored (disabled) uhci0 at pci0 dev 7 function 2 Intel 82371AB USB rev 0x01: 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 Intel 82371AB Power rev 0x02 at pci0 dev 7 function 3 not configured vr0 at pci0 dev 14 function 0 VIA VT6105 RhineIII rev 0x86: irq 15 address 00:0d:88:b3:61:46 ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface ukphy0: OUI 0x004063, model 0x0034, rev. 4 xl0 at pci0 dev 15 function 0 3Com 3c905B 100Base-TX rev 0x30: irq 11, address 00:50:04:9f:ce:5e exphy0 at xl0 phy 24: 3Com internal media interface isa0 at pcib0 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 pcdisplay0 at isa0 port 0x3b0/16 iomem 0xb/32768 wsdisplay0 at pcdisplay0 mux 1: console (80x25, vt100 emulation), using wskbd0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 sysbeep0 at pcppi0 npx0 at isa0 port 0xf0/16: using exception 16 biomask 7ffd netmask fffd ttymask pctr: 686-class user-level performance counters enabled mtrr: Pentium Pro MTRR support dkcsum: wd0 matches BIOS drive 0x80 root on wd0a rootdev=0x0 rrootdev=0x300 rawdev=0x302 arp info overwritten for 192.168.1.2 by 00:0b:cd:a7:55:0b on vr0 arp info overwritten for 192.168.1.2 by 00:11:2f:69:bf:9a on vr0 arp info overwritten for 192.168.1.2 by 00:0b:cd:a7:55:0b on vr0 arp info overwritten for 192.168.1.2 by 00:11:2f:69:bf:9a on vr0
Re: stuck on upgrading from 3.7 to 3.8 - Exception handling flag day
Hannah == Hannah Schroeter [EMAIL PROTECTED] writes: Hannah Please don't. There're people who use the upgrade FAQ as it's intended Hannah (i.e. one may try it out, but one is on one's own, if things fail and Hannah one can't fix it, use binaries to get close to the revision(s) one wants Hannah to compile, i.e. the release binaries to get to stable, the latest Hannah snapshot to possibly get to current). And it successfully worked for the past five upgrades. That's why I was surprised when it didn't work *immediately* this time. Now that I know that using source to leap from one release to the next is *less* supported than a binary leap, I understand the risk better. Prior to that, I had equated the risk. So thank you all. I learned, but I also spent the time to learn. By the way, I was thinking through my workaround, and have a hypothesis that binary cross-platform builds may actually be tainted... because that part of the build step must have been looking at *installed* include files, not just in-build-area include files, which is why it more or less works now, after the first bootstrap installation. Thus, there may be a bug there. Might deserve some investigation. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 merlyn@stonehenge.com URL:http://www.stonehenge.com/merlyn/ Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
VIA fanless motherboard - NICS
Hello. I'm looking at a VIA motherboard with the following NICS. 3 x INTEL 82551QM 1x 82540EM (Gigabit) Any issues with these ? M Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: X snaps headsup
On Sun, Dec 11, 2005 at 07:37:36AM -0600, Todd T. Fries wrote: New X snaps with a 'dlopen X server' diff are heading out to the mirrors today and tomorrow as they get built. I have put this into snapshots to get wide testing before Matthieu commits this diff. When you test, simply verify your X server starts and operates normally. When you do this update to a newer X snap, be sure to remove /usr/X11R6/lib/modules before doing so, as the names of the modules have changed, and the X server will not load the right ones if you have the old ones around. Tested on -current i386, working fine. Kind regards Simon
Re: VIA fanless motherboard - NICS
On Sat, 17 Dec 2005, martin wrote: Hello. I'm looking at a VIA motherboard with the following NICS. 3 x INTEL 82551QM 1x 82540EM (Gigabit) Any issues with these ? M Sounds like a Commell board? Which VIA processor?
Re: Odd routing problem ?
On 12/16/05, Joachim Schipper [EMAIL PROTECTED] wrote: Every attempt to access any host on the Internet gets to gwA int_wireless, but doesn't goes out on ext_if. gwB can't even ping gwA external address 1.2.3.2. I assume gwA and gwB can ping each other on the internal interface, at least. Yes. That's correct. In fact, I can connect to gwB from the Internet. Anything coming from the Internet gets routed correctly. gwB's - gwB:24$ cat /etc/hostname.sis0 inet 10.10.10.250 255.255.255.0 NONE inet alias 1.2.3.65 255.255.255.192 NONE gwB:25$ Okay, should work. I assume you've set gwA as default gateway? yes. 10.10.10.254 is the default gateway for gwB gwA's - gwA:511$ cat /etc/hostname.xl0 inet 10.10.10.254 255.255.255.0 NONE !/sbin/route add -net 1.2.3.64/26 10.10.10.250 Okay, should work, too. Wireless is a bitch, but I suppose everything works, where the hardware is concerned. gwA:512$ cat /etc/hostname.sis0 inet 1.2.3.2 255.255.255.192 NONE gwA:513$ Are you certain that gwA-sis0 should have that netmask? If it is indeed internet-connected, it probably shouldn't. Yes. The other /26 block was designed to be in gwB's domain. gwA:514$ sysctl -a net.inet.ip.forwarding net.inet.ip.forwarding=1 Has anyone a clue ? Nothing definitive, but (unless the above solves it) I'd like to see the routing tables. I'm not entirely certain where the default route goes, in particular. gwB -- gwB:4$ netstat -rnf inet ; netstat -rnf encap Routing tables Internet: DestinationGatewayFlags Refs UseMtu Interface default10.10.10.254 UGS 8 247617 - sis0 10.10.10/24link#1 UC 10 - sis0 10.10.10.254 0:2:6f:3c:59:9cUHLc1 15 - sis0 10.101.2/24link#2 UC 40 - rl0 10.101.2.101 0:11:5b:6:9a:1fUHLc110752 - rl0 10.101.2.102 0:50:be:56:3f:d5 UHLc099043 - rl0 10.101.2.105 0:7:95:dd:ad:c5UHLc012737 - rl0 10.101.2.120 0:7:95:31:8e:b8UHLc428001 - rl0 127/8 127.0.0.1 UGRS00 33224 lo0 127.0.0.1 127.0.0.1 UH 3 106 33224 lo0 1.2.3.64/26 link#1 UC 00 - sis0 1.2.3.65 127.0.0.1 UGHS00 33224 lo0 224/4 127.0.0.1 URS 00 33224 lo0 Routing tables Encap: Source Port DestinationPort Proto SA(Address/Proto/Type/Direction) 10.101.99/24 0 10.101.2/240 0 1.5.6130/50/use/in 10.101.2/240 10.101.99/24 0 0 1.5.6.130/50/require/out gwB:5$ gwA --- gwA:530$ netstat -rnf inet;netstat -rnf encap Routing tables Internet: DestinationGatewayFlags Refs UseMtu Interface default1.2.3.1 UGS 7 1598443 - sis0 10.10.10/24link#2 UC 10 - xl0 10.10.10.250 0:2:6f:3a:bc:c7UHLc3 95 - xl0 10.101.1/24link#3 UC 100 - vr0 10.101.1.5 0:40:33:aa:68:b0 UHLc0 2675 - vr0 10.101.1.110:d:87:1:a3:55 UHLc113323 - vr0 10.101.1.101 0:11:5b:12:59:72 UHLc0 4401 - vr0 10.101.1.102 0:30:21:a0:7c:16 UHLc0 3136 - vr0 10.101.1.105 0:e0:7d:b3:85:6e UHLc020417 - vr0 10.101.1.106 0:d0:9:f1:13:44UHLc015656 - vr0 10.101.1.120 0:a:e6:86:16:a7UHLc1 2212 - vr0 10.101.1.121 0:e0:4c:e1:e1:cd UHLc016732 - vr0 10.101.1.123 0:d:87:ce:f9:deUHLc020775 - vr0 10.101.1.254 0:8:54:32:b2:7fUHLc0 128 - lo0 10.101.2/2410.10.10.250 UGS 00 - xl0 10.101.5/24link#3 UC 40 - vr0 10.101.5.101 0:e0:7d:b2:ec:4c UHLc0 8005 - vr0 10.101.5.106 0:e:a6:7d:4a:f8UHLc0 1705 - vr0 10.101.5.107 0:0:e8:ec:94:bbUHLc1 8337 - vr0 10.101.5.120 0:e0:7d:73:55:cb UHLc0 3630 - vr0 10.101.5.254 127.0.0.1 UGHS00 33224 lo0 10.101.99.11.2.3.1 UGHD0 1594991 1444 sis0 10.101.99.80 1.2.3.1 UGHD0 1587957 1444 sis0 127/8 127.0.0.1 UGRS00 33224 lo0 127.0.0.1 127.0.0.1 UH 2 152 33224 lo0 1.2.3.0/26 link#1 UC 10 - sis0 1.2.3.1 0:60:2e:0:a4:99
Re: Help w/ install image on compactflash(cdrom38.fs or floppy38.fs)
There are a couple of ways to do this: 1) if you have a Windoze machine: a. get a *.fs from OpenBSD b. get physdiskwrite from m0n0wall c. plug CF-USB adapter into PC, write *.fs using physdiskwrite 2) you can also do this from Linux. I use a USB-CF device and dd... I don't recall off top of my head whether I used a *.fs or *.rd. If you're still stuck, email me I'll dig up the details. Jay On Wed, Dec 14, 2005 at 10:44:05PM -0500, the unit calling itself Nick Holland wrote: kyle wrote: Hi all, Im running into a (silly) problem where I am seem not to be writing the boot install images properly to a compact flash card. Ive been trying cdrom38.fsand floppy38.fs. I write the image under linux to the compact flash(seen as hde device) as so: cat floppy38.fs /dev/hde or: dd if=floppy38.fs of=/dev/hde bs=512 But, whenever I boot off of the compactflash I get the: ERR R error when it tries to load. yep. I read up that that message is due to disk geometry not seen properly by the BIOS..But, not sure how to work around it. uh..you are trying to treat a floppy disk image like a hard disk. Bad plan. :) If I boot a linux boot image on the flash, it works w/o issue(example bootnet.img from older redhat distros). this isn't Linux :) bootnet.img doesn't sound like a floppy image, anyway. (ok, a bit of googling seems to indicate that it is.) Now, this is pretty much my only install option(via compactflash). PXE timesout(the arp timeout issue, on older intel eepro), and I dont have any ide ports(this machine is a nokia ip650 and no onboard eide, it's all compactpci). It does have a floppy controller, but I of course dont have the correct floppy drive for it..heh. So, compactflash is my only option(or, if someone can recommend a way to bootstrap via a linux install on the box). There are several things you could do. Dumping a floppy image to a hard-disk-like device is not one of them. 1: Get a CF - IDE adapter, plug it into another computer, install OpenBSD on that system to the flash device, move to the ip650. Reconfigure. 2: mount the CF on another OpenBSD machine (anyway you can -- IDE-CF adapter, USB adapter, PCMCIA adapter, whatever). fdisk the CF, do a reinit from within fdisk to make sure it has a valid MBR. Disklabel it, create a small a partition. newfs the a partition, copy over bsd.rd and boot to the a partition (maybe rename bsd.rd to bsd at this point). Do an installboot. Move CF to target machine, if you did everything right, it should boot, if you didn't rename bsd.rd to bsd, you will need to manually do a boot bsd.rd when the boot prompt comes up, install. For extra credit, do this from the boot media, without actually having OpenBSD installed on the machine you are doing the config on -- should be possible. I'd suggest option #1, esp. if you needed more advice than create a bootable disk on another machine, or wish I had provided more detail. However, you would need a IDE to CF adapter, and they aren't the easiest thing to buy at the corner electronics store, and you may be miffed by the lack of utility after this one use. Option #2 is only for those willing to re-try things a few times until they get it right -- I doubt I'd do all the steps right the first time...but then, there is a reason I'm not into sky-diving. :) Anyway, can someone give me a pointer on what I am doing incorrectly? I definitely would love to get openbsd on these boxes and not linux(I have a couple w/ linux on them already, but I only installed linux on them since Ive been running into this problem w/ openbsd). It is certainly doable. I've installed OpenBSD to a number of machines without floppy or CDROMs It does take a little help from another machine, however. Nick.
Re: Alpha Disklabel Question
On Sat, 17 Dec 2005 18:03:21 +0100, Martin Reindl [EMAIL PROTECTED] wrote: J.C. Roberts [EMAIL PROTECTED] wrote: On Fri, 16 Dec 2005 13:50:48 -0800, J.C. Roberts [EMAIL PROTECTED] wrote: (2) When doing the installation disklabel, the suggested starting offset for the 'a' partition is 0? I know using an offset of 0 is discouraged on i386 and other systems (default is 63), so I figured I'd ask if using a 0 offset is the best/correct way for alpha? Just for those searching the misc@ archives... I received info off-list that disklabel is doing the right thing by using an offset of 0 on the alpha architecture. I wonder anyway how you got the impression it was doing wrong and the offset would be 63 for the first slice. FAQ 14.1 only talks about i386 and amd64 under 'Disklabel tricks and tips/Leave first track free'. It's clear imo. There's a difference between thinking disklabel is doing the wrong thing and just making sure it's doing the right thing. ;-) The alpha PSW is a weird beast with it's Dual BIOS where the first AlphaBIOS/ARC is for running WinNT4 with x86 BIOS emulation support and the second, the SRM Console, is for running Tru64 and OpenVMS. The guys I've talked to at Digital/Compaq/HP told me the multitude of alpha SRM's are very much closed source (due to the fact they control VMS licensing/revenue) and obviously, each SRM is specifically built for each machine model. On the weird machines like the PSW where multi/dual-booting NT, VMS and OSF/1 can be done, there *might* be some mad hackery in this particular SRM with a requirement for keeping the first (logical) track free for the MBR. From what I've read, I think the way the linux guys have hacked a way into supporting the use of AlphaBIOS/ARC on the PSW is by having the MBR and a small FAT partition for lilo and such. This same approach is used on the PSW when running WinNT4 with NTFS. In a situation where you are *only* running OpenBSD, using a offset of 0 is probably just fine. On the other hand, if you happen to have WinNT installed someplace (i.e. installed on another disk), the supposedly harmless tag that NT writes on all disks might make a real mess of your OBSD install. The problem is not so much that the OpenBSD docs are unclear, instead, the problem is the setup of particular machine, particularly in muti-boot configs, can be very convoluted. I only asked because I'm just trying to *understand* what the heck I'm doing and what all the possible ramifications are. -In other words, curiosity. ;-) kind regards, jcr
Re: VIA fanless motherboard - NICS
--- Diana Eichert [EMAIL PROTECTED] wrote: On Sat, 17 Dec 2005, martin wrote: Hello. I'm looking at a VIA motherboard with the following NICS. 3 x INTEL 82551QM 1x 82540EM (Gigabit) Any issues with these ? M Sounds like a Commell board? Which VIA processor? Commell LE-564 - Eden 533MHz Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: root / wheel login incorrect ??
Stefan Wvhrer wrote: Hi, .. I gotta very confusing problem running OpenBSD. I've installed OpenBSD at a mashine and where able to do anything I wanted to ( just have added an user in the wheel group an another in the user group ) Then I tried to log in from network as root via ssh. Didn't work since I've forgotten to allow root-login in sshd_config. As I wanted to locally log in as root to change the configuration file - it doesn't work.. I wasn't able to log in any more .. even not locally.. Login: root Password: Login incorrect ... tried it a few times without any success... I really didn't forget my password. I've searched for any solutions in the internet a whole day. I tried empty password, I tried Root instead of root no success. The user in the wheel group - same story. Could be related to keyboard layout. Do you have the same layout now as when you installed the OS? Otherwise, go single user (as mentioned in another reply). /Alexander
Re: Alpha Disklabel Question
J.C. Roberts [EMAIL PROTECTED] wrote: On Sat, 17 Dec 2005 18:03:21 +0100, Martin Reindl [EMAIL PROTECTED] wrote: J.C. Roberts [EMAIL PROTECTED] wrote: On Fri, 16 Dec 2005 13:50:48 -0800, J.C. Roberts [EMAIL PROTECTED] wrote: (2) When doing the installation disklabel, the suggested starting offset for the 'a' partition is 0? I know using an offset of 0 is discouraged on i386 and other systems (default is 63), so I figured I'd ask if using a 0 offset is the best/correct way for alpha? Just for those searching the misc@ archives... I received info off-list that disklabel is doing the right thing by using an offset of 0 on the alpha architecture. I wonder anyway how you got the impression it was doing wrong and the offset would be 63 for the first slice. FAQ 14.1 only talks about i386 and amd64 under 'Disklabel tricks and tips/Leave first track free'. It's clear imo. There's a difference between thinking disklabel is doing the wrong thing and just making sure it's doing the right thing. ;-) The alpha PSW is a weird beast with it's Dual BIOS where the first AlphaBIOS/ARC is for running WinNT4 with x86 BIOS emulation support and the second, the SRM Console, is for running Tru64 and OpenVMS. The guys I've talked to at Digital/Compaq/HP told me the multitude of alpha SRM's are very much closed source (due to the fact they control VMS licensing/revenue) and obviously, each SRM is specifically built for each machine model. On the weird machines like the PSW where multi/dual-booting NT, VMS and OSF/1 can be done, there *might* be some mad hackery in this particular SRM with a requirement for keeping the first (logical) track free for the MBR. From what I've read, I think the way the linux guys have hacked a way into supporting the use of AlphaBIOS/ARC on the PSW is by having the MBR and a small FAT partition for lilo and such. This same approach is used on the PSW when running WinNT4 with NTFS. In a situation where you are *only* running OpenBSD, using a offset of 0 is probably just fine. On the other hand, if you happen to have WinNT installed someplace (i.e. installed on another disk), the supposedly harmless tag that NT writes on all disks might make a real mess of your OBSD install. The problem is not so much that the OpenBSD docs are unclear, instead, the problem is the setup of particular machine, particularly in muti-boot configs, can be very convoluted. I only asked because I'm just trying to *understand* what the heck I'm doing and what all the possible ramifications are. -In other words, curiosity. ;-) So they only problem now is documenting how to multiboot OpenBSD and WinNT on alpha? Pardon me, but i don't expect Nick to put up a section about this in the FAQ. Especially since it would involve explaining AlphaBIOS fiddling which has nothing to do with OpenBSD and is a major PITA anyway. martin
Re: Alpha Disklabel Question
Martin Reindl wrote: J.C. Roberts [EMAIL PROTECTED] wrote: On Sat, 17 Dec 2005 18:03:21 +0100, Martin Reindl [EMAIL PROTECTED] wrote: J.C. Roberts [EMAIL PROTECTED] wrote: On Fri, 16 Dec 2005 13:50:48 -0800, J.C. Roberts [EMAIL PROTECTED] wrote: (2) When doing the installation disklabel, the suggested starting offset for the 'a' partition is 0? I know using an offset of 0 is discouraged on i386 and other systems (default is 63), so I figured I'd ask if using a 0 offset is the best/correct way for alpha? Just for those searching the misc@ archives... I received info off-list that disklabel is doing the right thing by using an offset of 0 on the alpha architecture. I wonder anyway how you got the impression it was doing wrong and the offset would be 63 for the first slice. FAQ 14.1 only talks about i386 and amd64 under 'Disklabel tricks and tips/Leave first track free'. It's clear imo. There's a difference between thinking disklabel is doing the wrong thing and just making sure it's doing the right thing. ;-) The alpha PSW is a weird beast with it's Dual BIOS where the first AlphaBIOS/ARC is for running WinNT4 with x86 BIOS emulation support and the second, the SRM Console, is for running Tru64 and OpenVMS. The guys I've talked to at Digital/Compaq/HP told me the multitude of alpha SRM's are very much closed source (due to the fact they control VMS licensing/revenue) and obviously, each SRM is specifically built for each machine model. On the weird machines like the PSW where multi/dual-booting NT, VMS and OSF/1 can be done, there *might* be some mad hackery in this particular SRM with a requirement for keeping the first (logical) track free for the MBR. From what I've read, I think the way the linux guys have hacked a way into supporting the use of AlphaBIOS/ARC on the PSW is by having the MBR and a small FAT partition for lilo and such. This same approach is used on the PSW when running WinNT4 with NTFS. In a situation where you are *only* running OpenBSD, using a offset of 0 is probably just fine. On the other hand, if you happen to have WinNT installed someplace (i.e. installed on another disk), the supposedly harmless tag that NT writes on all disks might make a real mess of your OBSD install. The problem is not so much that the OpenBSD docs are unclear, instead, the problem is the setup of particular machine, particularly in muti-boot configs, can be very convoluted. I only asked because I'm just trying to *understand* what the heck I'm doing and what all the possible ramifications are. -In other words, curiosity. ;-) So they only problem now is documenting how to multiboot OpenBSD and WinNT on alpha? Pardon me, but i don't expect Nick to put up a section about this in the FAQ. Especially since it would involve explaining AlphaBIOS fiddling which has nothing to do with OpenBSD and is a major PITA anyway. martin Lighten up a bit man. There is nothing in J.C.'s post that implies he expects a section about this in the FAQ. Maybe there ought to be a section in the FAQ about how even the most tangential reference to it on misc is like kicking a chicken coop.
Re: X snaps headsup
In message [EMAIL PROTECTED] Todd T. Fries [EMAIL PROTECTED] wrote: New X snaps with a 'dlopen X server' diff are heading out to the mirrors today and tomorrow as they get built. I have put this into snapshots to get wide testing before Matthieu commits this diff. When you test, simply verify your X server starts and operates normally. I'd originally assumed that the x* sets (dated 9 Dec) were not those mentioned above (on 11 Dec) but have now installed them. Everything seems to be working as it should be (i386). -- Andy Wingate URL:http://www.sparse.net OpenPGP key 0xC642BF8A There is no cabal.
Re: Alpha Disklabel Question
On Sat, Dec 17, 2005 at 06:03:21PM +0100, Martin Reindl wrote: J.C. Roberts [EMAIL PROTECTED] wrote: On Fri, 16 Dec 2005 13:50:48 -0800, J.C. Roberts [EMAIL PROTECTED] wrote: (2) When doing the installation disklabel, the suggested starting offset for the 'a' partition is 0? I know using an offset of 0 is discouraged on i386 and other systems (default is 63), so I figured I'd ask if using a 0 offset is the best/correct way for alpha? Just for those searching the misc@ archives... I received info off-list that disklabel is doing the right thing by using an offset of 0 on the alpha architecture. I wonder anyway how you got the impression it was doing wrong and the offset would be 63 for the first slice. FAQ 14.1 only talks about i386 and amd64 under 'Disklabel tricks and tips/Leave first track free'. It's clear imo. It's clear now, because the paragraph is _new_ :-) http://www.openbsd.org/cgi-bin/cvsweb/www/faq/faq14.html.diff?r1=1.143r2=1.145f=h Tobias
Re: Alpha Disklabel Question
Richard P. Koett [EMAIL PROTECTED] wrote: Martin Reindl wrote: J.C. Roberts [EMAIL PROTECTED] wrote: On Sat, 17 Dec 2005 18:03:21 +0100, Martin Reindl [EMAIL PROTECTED] wrote: J.C. Roberts [EMAIL PROTECTED] wrote: On Fri, 16 Dec 2005 13:50:48 -0800, J.C. Roberts [EMAIL PROTECTED] wrote: (2) When doing the installation disklabel, the suggested starting offset for the 'a' partition is 0? I know using an offset of 0 is discouraged on i386 and other systems (default is 63), so I figured I'd ask if using a 0 offset is the best/correct way for alpha? Just for those searching the misc@ archives... I received info off-list that disklabel is doing the right thing by using an offset of 0 on the alpha architecture. I wonder anyway how you got the impression it was doing wrong and the offset would be 63 for the first slice. FAQ 14.1 only talks about i386 and amd64 under 'Disklabel tricks and tips/Leave first track free'. It's clear imo. There's a difference between thinking disklabel is doing the wrong thing and just making sure it's doing the right thing. ;-) The alpha PSW is a weird beast with it's Dual BIOS where the first AlphaBIOS/ARC is for running WinNT4 with x86 BIOS emulation support and the second, the SRM Console, is for running Tru64 and OpenVMS. The guys I've talked to at Digital/Compaq/HP told me the multitude of alpha SRM's are very much closed source (due to the fact they control VMS licensing/revenue) and obviously, each SRM is specifically built for each machine model. On the weird machines like the PSW where multi/dual-booting NT, VMS and OSF/1 can be done, there *might* be some mad hackery in this particular SRM with a requirement for keeping the first (logical) track free for the MBR. From what I've read, I think the way the linux guys have hacked a way into supporting the use of AlphaBIOS/ARC on the PSW is by having the MBR and a small FAT partition for lilo and such. This same approach is used on the PSW when running WinNT4 with NTFS. In a situation where you are *only* running OpenBSD, using a offset of 0 is probably just fine. On the other hand, if you happen to have WinNT installed someplace (i.e. installed on another disk), the supposedly harmless tag that NT writes on all disks might make a real mess of your OBSD install. The problem is not so much that the OpenBSD docs are unclear, instead, the problem is the setup of particular machine, particularly in muti-boot configs, can be very convoluted. I only asked because I'm just trying to *understand* what the heck I'm doing and what all the possible ramifications are. -In other words, curiosity. ;-) So they only problem now is documenting how to multiboot OpenBSD and WinNT on alpha? Pardon me, but i don't expect Nick to put up a section about this in the FAQ. Especially since it would involve explaining AlphaBIOS fiddling which has nothing to do with OpenBSD and is a major PITA anyway. martin Lighten up a bit man. There is nothing in J.C.'s post that implies he expects a section about this in the FAQ. Maybe there ought to be a section in the FAQ about how even the most tangential reference to it on misc is like kicking a chicken coop. Obviously you know so much more than me. Reminds my i should go back to hacking and quit this short digression to [EMAIL PROTECTED]
Re: Alpha Disklabel Question
On Sat, 17 Dec 2005 21:17:02 +0100, Martin Reindl [EMAIL PROTECTED] wrote: So they only problem now is documenting how to multiboot OpenBSD and WinNT on alpha? Pardon me, but i don't expect Nick to put up a section about this in the FAQ. Especially since it would involve explaining AlphaBIOS fiddling which has nothing to do with OpenBSD and is a major PITA anyway. Very much agreed. The currently unproven *possibility* of making a mess by multi-booting an alpha PSW is, at best, a rare corner case that most people will never face -assuming the issue actually exists. I seriously doubt people are installing WinNT4 on alpha these days but the folks running linux through AlphaBIOS who want to dual-boot with OpenBSD might have a problem. I'll look into it further and prove it either way; mainly because data/disk loss sucks. Only if the problem turns out to be real, would a small FAQ warning/pointer be appropriate and even then, the info should really be in the INSTALL.alpha file. kind regards, jcr
Re: VIA fanless motherboard - NICS
--On Saturday, December 17, 2005 10:42:05 -0800 martin [EMAIL PROTECTED] wrote: Sounds like a Commell board? Which VIA processor? Commell LE-564 - Eden 533MHz No problems running OpenBSD 3.8 on this board. Here is a dmesg. OpenBSD 3.8-stable (GENERIC) #2: Fri Nov 25 23:29:35 PST 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: VIA Samuel 2 (CentaurHauls 686-class) 533 MHz cpu0: FPU,DE,TSC,MSR,MTRR,PGE,MMX real mem = 259633152 (253548K) avail mem = 230027264 (224636K) using 3194 buffers containing 13082624 bytes (12776K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(51) BIOS, date 11/24/03, BIOS32 rev. 0 @ 0xfb590 apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown apm0: flags 70102 dobusy 1 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xf/0xdef4 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfde50/160 (8 entries) pcibios0: PCI Exclusive IRQs: 5 10 11 12 pcibios0: PCI Interrupt Router at 000:07:0 (VIA VT82C596A ISA rev 0x00) pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc/0xc000 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 VIA VT8601 PCI rev 0x05 ppb0 at pci0 dev 1 function 0 VIA VT82C601 AGP rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 Trident CyberBlade i1 rev 0x6a wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) pcib0 at pci0 dev 7 function 0 VIA VT82C686 ISA rev 0x40 pciide0 at pci0 dev 7 function 1 VIA VT82C571 IDE rev 0x06: ATA100, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: SanDisk SDCFB-256 wd0: 1-sector PIO, LBA, 244MB, 500400 sectors wd0(pciide0:0:0): using PIO mode 4 pciide0: channel 1 disabled (no drives) uhci0 at pci0 dev 7 function 2 VIA VT83C572 USB rev 0x1a: irq 12 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 7 function 3 VIA VT83C572 USB rev 0x1a: irq 12 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 viaenv0 at pci0 dev 7 function 4 VIA VT82C686 SMBus rev 0x40 em0 at pci0 dev 16 function 0 Intel PRO/1000MT (82540EM) rev 0x02: irq 11, address: 00:03:1d:00:f8:d0 fxp0 at pci0 dev 17 function 0 Intel 82557 rev 0x10, i82551: irq 5, address 00:03:1d:00:f8:d1 inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 4 fxp1 at pci0 dev 18 function 0 Intel 82557 rev 0x10, i82551: irq 12, address 00:03:1d:00:f8:d2 inphy1 at fxp1 phy 1: i82555 10/100 PHY, rev. 4 fxp2 at pci0 dev 19 function 0 Intel 82557 rev 0x10, i82551: irq 10, address 00:03:1d:00:f8:d3 inphy2 at fxp2 phy 1: i82555 10/100 PHY, rev. 4 hifn0 at pci0 dev 20 function 0 Hifn 7955/7954 rev 0x00: LZS 3DES ARC4 MD5 SHA1 RNG AES PK, 32KB dram, irq 11 isa0 at pcib0 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 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 sysbeep0 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 pccom0: console pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 biomask f345 netmask ff65 ttymask ffe7 pctr: user-level cycle counter enabled dkcsum: wd0 matches BIOS drive 0x80 root on wd0a rootdev=0x0 rrootdev=0x300 rawdev=0x302
openbgpd + neighbor configuration
Hello If I add prepend-self etc to a neighbor while openbgpd is running and then doing I a reload, should openbgpd understand that this has changed and manipulate the routingtable accordingly ? It does not seem to do this. // Philip
http://www.openbsd-support.com/jp/en/htm/orders.shtml
Hi all. http://www.openbsd-support.com/jp/en/htm/orders.shtml says that *All CD sales go back to help fund the ongoing development of OpenBSD.*. Is this true?
Re: http://www.openbsd-support.com/jp/en/htm/orders.shtml
Hi all. http://www.openbsd-support.com/jp/en/htm/orders.shtml says that *All CD sales go back to help fund the ongoing development of OpenBSD.*. Is this true? You could use the official website no? http://www.openbsd.org/goals.html#funding http://www.openbsd.org/orders.html
Ruby queries
Hello misc@openbsd.org, I have been tinkering with ruby on OpenBSD recently, and I have come across the following troubles, which I have researched on google and marc, but no cigar: a) I have been unable to configure mod_ruby. First if all I jumped in and added a LoadModule line and also an AddType line to my httpd.conf, and hoped it would work. It didnt. Secondly I constulted the mod_ruby webpage, which offers a more complicated solution, which also didnt work. Then I stumbled across mod_ruby-enable in the packing list, which pretty much does what I did in the first case, but copies the .so to another dir (is this neccessary? Unaccounted for files are not good). So my basic question is how do you set up mod_ruby, and could it be documented someplace? b) Which pkg holds tcltklib? If I try to run any program that requires tk, then I get an error like this: /usr/local/lib/ruby/1.8/tk.rb:7:in `require': No such file to load -- tcltklib I have tcl, tk, tcllib installed. Heres a dmesg for luck: OpenBSD 3.8-current (GENERIC) #0: Thu Dec 15 18:17:09 GMT 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Celeron(R) M processor 1500MHz (GenuineIntel 686-class) 1.50 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,ACPI,MMX,FXSR ,SSE,SSE2,TM,SBF real mem = 258449408 (252392K) avail mem = 228962304 (223596K) using 3180 buffers containing 13025280 bytes (12720K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(d8) BIOS, date 02/21/05, BIOS32 rev. 0 @ 0xfd740 pcibios0 at bios0: rev 2.1 @ 0xfd6d0/0x930 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdeb0/256 (14 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82371FB ISA rev 0x00) pcibios0: PCI bus #2 is the last bus bios0: ROM list: 0xc/0xd000! 0xcd000/0x1000 0xce000/0x1000 0xdc000/0x4000! 0xe/0x1 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82852GM Hub-PCI rev 0x02 Intel 82852GM Memory rev 0x02 at pci0 dev 0 function 1 not configured Intel 82852GM Configuration rev 0x02 at pci0 dev 0 function 3 not configured vga1 at pci0 dev 2 function 0 Intel 82852GM AGP rev 0x02: aperture at 0xe000, size 0x800 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) Intel 82852GM AGP rev 0x02 at pci0 dev 2 function 1 not configured 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, 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 11 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 uhci2 at pci0 dev 29 function 2 Intel 82801DB USB rev 0x01: irq 11 usb2 at uhci2: USB revision 1.0 uhub2 at usb2 uhub2: Intel UHCI root hub, 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 11 usb3 at ehci0: USB revision 2.0 uhub3 at usb3 uhub3: Intel EHCI root hub, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered ppb0 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0x81 pci1 at ppb0 bus 1 cbb0 at pci1 dev 0 function 0 Texas Instruments PCI1510 CardBus rev 0x00: irq 11 iwi0 at pci1 dev 2 function 0 Intel PRO/Wireless 2200BG rev 0x05: irq 11, address 00:12:f0:79:36:41 fxp0 at pci1 dev 8 function 0 Intel PRO/100 VE rev 0x81: irq 11, address 00:0a:e4:33:68:74 inphy0 at fxp0 phy 1: i82562ET 10/100 PHY, rev. 0 cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 2 device 0 cacheline 0x8, lattimer 0xb0 pcmcia0 at cardslot0 ichpcib0 at pci0 dev 31 function 0 Intel 82801DBM LPC rev 0x01: SpeedStep pciide0 at pci0 dev 31 function 1 Intel 82801DBM IDE rev 0x01: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: HTS424030M9AT00 wd0: 16-sector PIO, LBA, 28615MB, 58605120 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: TEAC, DW-225, 2.6A 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 auich0 at pci0 dev 31 function 5 Intel 82801DB AC97 rev 0x01: irq 11, ICH4 AC97 ac97: codec id 0x41445374 (Analog Devices AD1981B) ac97: codec features headphone, 20 bit DAC, No 3D Stereo audio0 at auich0 Intel 82801DB Modem rev 0x01 at pci0 dev 31 function 6 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: console keyboard, using wsdisplay0 pms0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pms0 mux 0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC
Re: http://www.openbsd-support.com/jp/en/htm/orders.shtml
http://www.openbsd-support.com/jp/en/htm/orders.shtml says that *All CD sales go back to help fund the ongoing development of OpenBSD.*. Is this true? Yes. If you want, check out wikipedia for hackathon. Now add up the price of these events, year after year...
Re: stuck on upgrading from 3.7 to 3.8 - Exception handling flag day
On 17 Dec 2005 08:51:01 -0800, Randal L. Schwartz merlyn@stonehenge.com wrote: By the way, I was thinking through my workaround, and have a hypothesis that binary cross-platform builds may actually be tainted... because that part of the build step must have been looking at *installed* include files, not just in-build-area include files, which is why it more or less works now, after the first bootstrap installation. which aren't supported either.
Re: Ruby queries
Regarding tcl and tk, few days ago i had to compile PIL (Python Imaging Library) for my Zope/Plone server. Since it also requires tcl and tk, this information may be useful for you trouble. I installed both using openbsd packages method, but when I tried to run setup.py, tk complained about Xlib.h header file. I realized that packages xshare38.tgz and xserver38.tgz were missing (duh), and installed them. After a updatedb/locate Xlib.h I found it had been correctly installed, so compilation should be OK. However, tk still was complaining about X libraries, so something ought to be wrong. After some search, I found that it was looking for libraries in the default place, /usr/include, but it was in /usr/X11R6/include/X11/Xlib.h . So I symlinked /usr/X11R6/include/X11 to /usr/include/X11, and evertything went just fine. Not sure if this is your problem (probably not), but if anyone runs on this, they will find answers here. By the way, if anyone is asking why didn't I simply use openbsd's PIL package, it's because Plone 2.1.1 sorta requires PIL 1.1.5, and only PIL 1.1.4p0 is available at present. On 12/17/05, Edd Barrett [EMAIL PROTECTED] wrote: Hello misc@openbsd.org, I have been tinkering with ruby on OpenBSD recently, and I have come across the following troubles, which I have researched on google and marc, but no cigar: a) I have been unable to configure mod_ruby. First if all I jumped in and added a LoadModule line and also an AddType line to my httpd.conf, and hoped it would work. It didnt. Secondly I constulted the mod_ruby webpage, which offers a more complicated solution, which also didnt work. Then I stumbled across mod_ruby-enable in the packing list, which pretty much does what I did in the first case, but copies the .so to another dir (is this neccessary? Unaccounted for files are not good). So my basic question is how do you set up mod_ruby, and could it be documented someplace? b) Which pkg holds tcltklib? If I try to run any program that requires tk, then I get an error like this: /usr/local/lib/ruby/1.8/tk.rb:7:in `require': No such file to load -- tcltklib I have tcl, tk, tcllib installed. Heres a dmesg for luck: OpenBSD 3.8-current (GENERIC) #0: Thu Dec 15 18:17:09 GMT 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Celeron(R) M processor 1500MHz (GenuineIntel 686-class) 1.50 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,ACPI,MMX,FXSR ,SSE,SSE2,TM,SBF real mem = 258449408 (252392K) avail mem = 228962304 (223596K) using 3180 buffers containing 13025280 bytes (12720K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(d8) BIOS, date 02/21/05, BIOS32 rev. 0 @ 0xfd740 pcibios0 at bios0: rev 2.1 @ 0xfd6d0/0x930 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdeb0/256 (14 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82371FB ISA rev 0x00) pcibios0: PCI bus #2 is the last bus bios0: ROM list: 0xc/0xd000! 0xcd000/0x1000 0xce000/0x1000 0xdc000/0x4000! 0xe/0x1 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82852GM Hub-PCI rev 0x02 Intel 82852GM Memory rev 0x02 at pci0 dev 0 function 1 not configured Intel 82852GM Configuration rev 0x02 at pci0 dev 0 function 3 not configured vga1 at pci0 dev 2 function 0 Intel 82852GM AGP rev 0x02: aperture at 0xe000, size 0x800 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) Intel 82852GM AGP rev 0x02 at pci0 dev 2 function 1 not configured 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, 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 11 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 uhci2 at pci0 dev 29 function 2 Intel 82801DB USB rev 0x01: irq 11 usb2 at uhci2: USB revision 1.0 uhub2 at usb2 uhub2: Intel UHCI root hub, 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 11 usb3 at ehci0: USB revision 2.0 uhub3 at usb3 uhub3: Intel EHCI root hub, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered ppb0 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0x81 pci1 at ppb0 bus 1 cbb0 at pci1 dev 0 function 0 Texas Instruments PCI1510 CardBus rev 0x00: irq 11 iwi0 at pci1 dev 2 function 0 Intel PRO/Wireless 2200BG rev 0x05: irq 11, address 00:12:f0:79:36:41 fxp0 at pci1 dev 8 function 0 Intel PRO/100 VE rev 0x81: irq 11, address 00:0a:e4:33:68:74 inphy0 at fxp0 phy 1: i82562ET 10/100 PHY, rev. 0 cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 2 device 0 cacheline 0x8, lattimer
Notifica�ao de Pendencia
[IMAGE] Verificar Cridito: Online ao (CPF ou CNPJ) Serasa Central de atendimento ao cliente: [IMAGE][IMAGE] Prezado Cliente, Comunicamos que consta em nosso banco de dados varias pendjncias financeiras em seu CPF / CNPJ, das quais nco foram quitadas nas respectivas datas de vencimento. Dia 2 8/10/2005 No valor de R$ 1.500,12 Detalhes [IMAGE] Dia 2 5/10/2005 No valor de R$ 1.977,56 Detalhes[IMAGE] Pedimos a vossa atengco a este comunicado, pois, medidas legais serco adotadas, tais como a inclusco no Sistema de Protegco ao Cridito (SPC) e Serasa. A Check Check i a primeira empresa de informagco de cridito que disponibiliza pela Internet uma Central de Atendimento on-line, onde o cliente, conectado a uma atendente por meio do chat, tira todas as suas dzvidas. Conhega esse sistema agora mesmo!!! Visualizar extrato Atenciosamente: Simone Mantovanelli cobranga extrajudicial [IMAGE] Copyright ) 2003. Todos os direitos reservados
Re: OpenBSD beep
PC speaker beep (something action on the console?) Or possibly hardware alarm? ~BAS On Sat, 2005-12-17 at 09:12, dimaz wrote: I've installed OpenBSD on my small server, before on server was linux, and 2-3 times a day my server beeps (3 times)... What does it mean? And how I can control this beeps?
Pf question
Just a quick question I hope. I have the following setup: 1 internal interface 1 external interface 3 static routable IP's assigned to external interface (one primary, two aliases) I want to use one IP for NAT and some port redirection to a client system and a web server, another IP for a second web server, and the remaining IP for a FTP server. I've been playing with the rules and reading documentation on this for several days now and haven't gotten anywhere. I know about BINAT and would prefer not to use it in favor of RDR'ing the ports that are common between servers to the respective server based on the IP address that is connected to from the outside world. Can someone give me some idea of what RDR and PASS IN/OUT rules I'd need for just a portion of this (say the web servers) and I can figure out the rest on my own? I can make the ftp server work, but I don't know how to say that traffic to a specific IP should be directed to it. Thanks, Logical_1
ruby on rails derailed, chroot httpd reported DOA
A confusing mess I gather . however, I will do my best to explain. v. OpenBSD 3.8-stable I compiled RoR from source, as well as fastcgi ... I created directories from my RoR apps in /var/www/users/mike/rails and copied all the nescessary libs to the apropriate newly created directories . possible bug, evertime I start/restart httpd (httpd 1.3.29) it creates the etag-state log below. any ideas? [Sun Dec 18 00:50:23 2005] [notice] Initializing etag from /var/www/logs/etag-state [Sun Dec 18 00:50:23 2005] [notice] chrooted in /var/www [Sun Dec 18 00:50:23 2005] [notice] changed to uid 1, gid 1 [Sun Dec 18 00:50:23 2005] [notice] Apache/1.3.29 (Unix) mod_fastcgi/2.4.2 mod_ssl/2.8.1 [Sun Dec 18 00:50:23 2005] [notice] Accept mutex: sysvsem (Default: sysvsem) [Sun Dec 18 05:50:23 2005] [notice] FastCGI: process manager chrooted in /var/www [Sun Dec 18 05:50:23 2005] [notice] FastCGI: process manager initialized (pid 6924) [Sun Dec 18 05:50:23 2005] [warn] FastCGI: server /var/www/users/mike/rails/public/disp FastCGI: can't start server /var/www/users/mike/rails/public/dispatch.fcgi (pid 5872), [Sun Dec 18 05:50:23 2005] [warn] FastCGI: server /var/www/users/mike/rails/public/disp -bash-3.00$ tail /var/www/logs/error_log [Sun Dec 18 05:50:28 2005] [warn] FastCGI: server /var/www/users/mike/rails/public/dispatch.fcgi restarted (pid 14621) FastCGI: can't start server /var/www/users/mike/rails/public/dispatch.fcgi (pid 14621), chdir() failed: No such file or directory [Sun Dec 18 05:50:28 2005] [warn] FastCGI: server /var/www/users/mike/rails/public/dispatch.fcgi (pid 14621) terminated by calling exit with status ' [Sun Dec 18 05:50:33 2005] [warn] FastCGI: server /var/www/users/mike/rails/public/dispatch.fcgi restarted (pid 3310) FastCGI: can't start server /var/www/users/mike/rails/public/dispatch.fcgi (pid 3310), chdir() failed: No such file or directory [Sun Dec 18 05:50:33 2005] [warn] FastCGI: server /var/www/users/mike/rails/public/dispatch.fcgi (pid 3310) terminated by calling exit with status '2 [Sun Dec 18 05:50:38 2005] [warn] FastCGI: server /var/www/users/mike/rails/public/dispatch.fcgi restarted (pid 9195) FastCGI: can't start server /var/www/users/mike/rails/public/dispatch.fcgi (pid 9195), chdir() failed: No such file or directory [Sun Dec 18 05:50:38 2005] [warn] FastCGI: server /var/www/users/mike/rails/public/dispatch.fcgi (pid 9195) terminated by calling exit with status '2 [Sun Dec 18 05:50:38 2005] [warn] FastCGI: server /var/www/users/mike/rails/public/dispatch.fcgi has failed to remain running for 30 seconds given 3 -bash-3.00$ tail /var/www/logs/error_log [Sun Dec 18 05:50:28 2005] [warn] FastCGI: server /var/www/users/mike/rails/public/dispatch.fcgi restarted (pid 14621) FastCGI: can't start server /var/www/users/mike/rails/public/dispatch.fcgi (pid 14621), chdir() failed: No such file or directory [Sun Dec 18 05:50:28 2005] [warn] FastCGI: server /var/www/users/mike/rails/public/dispatch.fcgi (pid 14621) terminated by calling exit with status '255' [Sun Dec 18 05:50:33 2005] [warn] FastCGI: server /var/www/users/mike/rails/public/dispatch.fcgi restarted (pid 3310) FastCGI: can't start server /var/www/users/mike/rails/public/dispatch.fcgi (pid 3310), chdir() failed: No such file or directory [Sun Dec 18 05:50:33 2005] [warn] FastCGI: server /var/www/users/mike/rails/public/dispatch.fcgi (pid 3310) terminated by calling exit with status '255' [Sun Dec 18 05:50:38 2005] [warn] FastCGI: server /var/www/users/mike/rails/public/dispatch.fcgi restarted (pid 9195) FastCGI: can't start server /var/www/users/mike/rails/public/dispatch.fcgi (pid 9195), chdir() failed: No such file or directory [Sun Dec 18 05:50:38 2005] [warn] FastCGI: server /var/www/users/mike/rails/public/dispatch.fcgi (pid 9195) terminated by calling exit with status '255' [Sun Dec 18 05:50:38 2005] [warn] FastCGI: server /var/www/users/mike/rails/public/dispatch.fcgi has failed to remain running for 30 seconds given 3 attempts, its restart interval has been backed off to 600 -bash-3.00$ --mike
Re: Pf question
Logical One wrote: Can someone give me some idea of what RDR and PASS IN/OUT rules I'd need for just a portion of this (say the web servers) and I can figure out the rest on my own? Read here: http://www.bgnett.no/~peter/pf/en/pf-firewall.pdf in PDF or http://www.bgnett.no/~peter/pf/en/ in html. Page 16 of th PDF for example for web server. Daniel
Apache not following symlinks
Seems to me I solved this one before about four years ago, but ... OBSD 3.8 w/ the installed Apache httpd doesn't follow my symlinks, e.g., /var/www/htdocs/doc/ is a link to /usr/local/doc but no love on http://localhost:/doc FollowSymLinks is there in httpd.conf ... all the dirs and fiels seem to have okay permissions. What obvious thing that I figured out already years ago am I forgetting, please? -- Jack J. Woehr # I never played fast and loose with the PO Box 51, Golden, CO 80402 # Constitution. Never did and never will. http://www.well.com/~jax # - Harry S Truman
Re: Pf question
Daniel Ouellet wrote: Logical One wrote: Can someone give me some idea of what RDR and PASS IN/OUT rules I'd need for just a portion of this (say the web servers) and I can figure out the rest on my own? Read here: http://www.bgnett.no/~peter/pf/en/pf-firewall.pdf in PDF or http://www.bgnett.no/~peter/pf/en/ in html. Page 16 of th PDF for example for web server. Sorry, page 33! I was reading something else and was on page 16. Confuse the two... Anyway, read it all, it's good learning anyway. Daniel
Digital Camera Bundle
[IMAGE][IMAGE] [IMAGE] [IMAGE] [IMAGE] [IMAGE] [IMAGE] You are subscribed as [EMAIL PROTECTED] To unsubscribe please click here. [IMAGE] [IMAGE]
Re: Apache not following symlinks
Jack Woehr wrote: Seems to me I solved this one before about four years ago, but ... OBSD 3.8 w/ the installed Apache httpd doesn't follow my symlinks, e.g., /var/www/htdocs/doc/ is a link to /usr/local/doc but no love on http://localhost:/doc FollowSymLinks is there in httpd.conf ... all the dirs and fiels seem to have okay permissions. What obvious thing that I figured out already years ago am I forgetting, please? In chroot apache will not follow symlinks outside of jail. apache by default run chroot in /var/www and you try to access something in /usr/local/doc, not going to go there, or you will need to run apache -u, not something I would do. Daniel
Re: Apache not following symlinks
Jack Woehr wrote: Seems to me I solved this one before about four years ago, but ... OBSD 3.8 w/ the installed Apache httpd doesn't follow my symlinks, e.g., /var/www/htdocs/doc/ is a link to /usr/local/doc but no love on http://localhost:/doc FollowSymLinks is there in httpd.conf ... all the dirs and fiels seem to have okay permissions. What obvious thing that I figured out already years ago am I forgetting, please? More information here: http://openbsd.org/faq/faq10.html#httpdchroot And specifically in the FaQ as this You can, of course, use symbolic links in the user's home directories pointing to subdirectories in /var/www, but you can NOT use links in /var/www pointing to other parts of the file system -- that is prevented from working by the chroot(2)ing. Daniel
perl - problem 'checksum mismatch' almost solved
[You find this repeatedly in the archive] Since I had this throughout the versions, including 3.8, I looked into this a bit deeper: cpan -MCPAN -e shell and everything subsequent bombs out with a checksum mismatch. Here is why, and how to solve it [and why some didn't experience it]: 0. It is a tar problem 1. run cpan fearlessly as you would. When you hit checksum mismatch: I'd recommend removing /root/.cpan/sources/foo/bar-2.0.tar.gz. Its MD5 checksum is incorrect. simply exit cpan and mv /root/.cpan/sources/foo/bar.tar /root/.cpan/sources/foo/bar.tar.gz (That is, mv the file without .gz to the file with .gz. It does exist; but overwrite is okay !) Start cpan again, until it bombs out. Rinse and repeat: exit - mv - cpan - exit - mv -cpan. Be intelligent and run 'install Bundle::CPAN' in cpan, because the fifths or sixths install of the Bundle will install Compress-Zlib. From now on, cpan will not resort to the helper applications that you defined earlier (tar, gunzip), but use its own Compress-Zlib. From here on everything works fine. Without any rinse repeat. A shortcut to this: you install p5-Compress-Zlib from the ports or packages, and cpan will use this as its native application early on. (Which explains why some have never experienced this problem: all those who had it installed from ports or packages before attempting cpan). Uwe, who considers this 'almost' solved because he didn't look into the underlying problem of gunzip/tar that manifests itself as long as Compress-Zlib is unused
Re: OpenBSD beep
Brian A. Seklecki wrote: PC speaker beep (something action on the console?) Or possibly hardware alarm? ~BAS On Sat, 2005-12-17 at 09:12, dimaz wrote: I've installed OpenBSD on my small server, before on server was linux, and 2-3 times a day my server beeps (3 times)... What does it mean? And how I can control this beeps? Nothing on console, nothing on /var/log/messages; /var/log/secure; I don't think that it's hardware alarm, my hardware seems to be ok :) last messages in dmesg: arp info overwritten for 192.168.3.79 by 00:80:48:b7:97:79 on vr0 arp info overwritten for 192.168.3.79 by 00:11:95:d1:79:0a on vr0 arp info overwritten for 192.168.3.79 by 00:80:48:b7:97:79 on vr0 arp info overwritten for 192.168.3.79 by 00:11:95:d1:79:0a on vr0 Dbt I don't think that it can cause pc speaker beeps :)
