chroot /emul/linux /bin/sh
Hi, Can someone make a comment about this behaviour.. # date Wed Aug 30 07:33:32 IST 2006 # chroot /emul/linux /bin/sh ..and music in my speakers stops (mplayer).. # date Thu Jan 1 01:00:01 IST 1970 # rdate -n vega.cbk.poznan.pl Wed Aug 30 07:34:36 IST 2006 # date Wed Aug 30 07:34:38 IST 2006 # sysctl kern.emul.linux kern.emul.linux = 1 ps. I'm not on misc@, please CC me. -- best regards q#
Re: OpenBSD artwork website wording
On Mon, Aug 28, 2006 at 02:08:48PM -0600, Theo de Raadt wrote: It is personal use, because it is not corporate... If you want to put it on the OpenBSD artwork webpage, you can download it here: http://ronja.twibright.com/grx/tools/openbsd.png I think it looks much better than the improperly sampled (see Nyquist-Shannon sampling theorem http://en.wikipedia.org/wiki/Nyquist%E2%80%93Shannon_sampling_theorem) and alpha-crippled GIF images. I just wonder if I start bragging on Ronja mailing list how the audio in OpenBSD kernel regularly deadlocks for me and how I can freeze the machine as ordinary user by running non-suid-exec wine, if this stops being represent OpenBSD in a positive light (http://openbsd.org/art1.html) and I'll go to a court ;-) It reminds me the EULA terms of some proprietary software you can use this program only as long as you are not going to publish any benchmarks about it ;-) I would personally see terms you can use the logo to represent your usage of OpenBSD or compatibility with OpenBSD more appropriate for a free software project logo than the band-aid-over-mouth represent OpenBSD in a positive light. CL On Mon, Aug 28, 2006 at 11:25:29AM -0600, Theo de Raadt wrote: [...] I already asked Theo about this in a reply to his reply, but he didn't reply :( Sure, you can convert them for your personal use. But I want to display it on a website to illustrate the fact that at least one project developer (the main one) is using OpenBSD on the development machine. Does this classify as a personal use when it's for a public display? CL
Printing on both sides
Do you know how to tell the /etc/printcap that it should print on both sides of paper with a laserjet postscript printer? I looked into the printcap manpage and there is nothing about sides or duplex. CL
Migrating from ipfw to pf
Good day How can I configure pf in case with 2 external interfaces? There is no binding to interface at all in ipfw. I just divert 42345 ip from 192.168.0.0/16 to any fwd 194.185.178.126 ip from 194.185.178.125 to any divert 42345 ip from any to 194.185.178.125 In pf I have to set external interface, like this nat on sk0 inet from 192.168.0.0/16 to any - 194.185.178.125 But traffic by default go to another interface - em1 -- Wed Aug 30 14:20:16 MSD 2006
Re: Migrating from ipfw to pf
On 2006/08/30 14:21, AstraSerg wrote: How can I configure pf in case with 2 external interfaces? Read http://www.openbsd.org/faq/pf/pools.html load-balancing outgoing traffic.
Re: sasyncd and ISAKMP SA
On Tue, Aug 08, 2006 at 08:23:39PM +0200, Floroiu, John Williams wrote: does sasyncd enable the IPsec failover gateways to also share the ISAKMP SA (so that DPD exchanges can proceed despite failures)? the ISAKMP SA is not explicitly mentioned in the help page (and is actually distinct from the IPsec SAs). no, it doesn't. HJ.
Re: Migrating from ipfw to pf
On Wednesday 30 August 2006 14:50, Stuart Henderson wrote: On 2006/08/30 14:21, AstraSerg wrote: How can I configure pf in case with 2 external interfaces? Read http://www.openbsd.org/faq/pf/pools.html load-balancing outgoing traffic. Thanks a lot. -- Wed Aug 30 15:17:38 MSD 2006
Dell 1650 serial console
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi All, I'm trying to pxeboot a Dell 1650 with OpenBSD 3.9. Console redirection of the BIOS is running without problems and pxeboot gets transmitted via tftp too. When I type in set tty com0, I get the following message: com0 console not present And of course when I say boot bsd.rd, bsd.rd is fetched via tftp but I have no output. That's kinda strange, because the BIOS is already redirected to the serial port and on the very same box I can install Debian Linux remotely, console always working flawlessly, from BIOS to Lilo and system itself. Now, obviously, I want to install OpenBSD 3.9 and not Debian Linux. Any idea why OpenBSD (pxeboot) is complaining about no com0 ? I can send debugging output as long as its required, 'cause like I said, I have remote serial access until I try to set tty com0 at the OpenBSD boot prompt ;) Thanks in advance, Marian iD8DBQFE9Xx4gAq87Uq5FMsRAiOeAKCP7FrE+kdUwkidfZzG0uZVWJBxegCghiLe VXkocOSyfOTc+nQd0IhqFyo= =6P3v -END PGP SIGNATURE-
SSH login slow troubleshoot Techniques
Hi, My OpenBSD 3.9 on an amd64 is very very slow for SSH login. Could some one give me steps I can follow to troubleshoot the problem? I pinged differrent computers from a linux machine Below are the Statistics Pinging OpenBSD 3.9 - This is the system that shows the trouble # ping -c 5 172.16.2.25 PING 172.16.2.25 (172.16.2.25) 56(84) bytes of data. 64 bytes from 172.16.2.25: icmp_seq=1 ttl=255 time=0.102 ms 64 bytes from 172.16.2.25: icmp_seq=2 ttl=255 time=0.110 ms 64 bytes from 172.16.2.25: icmp_seq=3 ttl=255 time=0.119 ms 64 bytes from 172.16.2.25: icmp_seq=4 ttl=255 time=0.115 ms 64 bytes from 172.16.2.25: icmp_seq=5 ttl=255 time=0.114 ms --- 172.16.2.25 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 3999ms rtt min/avg/max/mdev = 0.102/0.112/0.119/0.005 ms === Pinging a FreeBSD 6.1 System # ping -c 5 172.16.2.26 PING 172.16.2.26 (172.16.2.26) 56(84) bytes of data. 64 bytes from 172.16.2.26: icmp_seq=1 ttl=64 time=0.121 ms 64 bytes from 172.16.2.26: icmp_seq=2 ttl=64 time=0.108 ms 64 bytes from 172.16.2.26: icmp_seq=3 ttl=64 time=0.103 ms 64 bytes from 172.16.2.26: icmp_seq=4 ttl=64 time=0.118 ms 64 bytes from 172.16.2.26: icmp_seq=5 ttl=64 time=0.108 ms --- 172.16.2.26 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 3999ms rtt min/avg/max/mdev = 0.103/0.111/0.121/0.013 ms === Pinging a Debian Etch # ping -c 5 172.16.2.0 PING 172.16.2.0 (172.16.2.0) 56(84) bytes of data. 64 bytes from 172.16.2.0: icmp_seq=1 ttl=64 time=1.72 ms 64 bytes from 172.16.2.0: icmp_seq=2 ttl=64 time=0.092 ms 64 bytes from 172.16.2.0: icmp_seq=3 ttl=64 time=0.097 ms 64 bytes from 172.16.2.0: icmp_seq=4 ttl=64 time=0.372 ms 64 bytes from 172.16.2.0: icmp_seq=5 ttl=64 time=0.096 ms --- 172.16.2.0 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4000ms rtt min/avg/max/mdev = 0.092/0.476/1.725/0.633 ms = Pinging a Debian Sarge # ping -c 5 172.16.2.1 PING 172.16.2.1 (172.16.2.1) 56(84) bytes of data. 64 bytes from 172.16.2.1: icmp_seq=1 ttl=64 time=0.215 ms 64 bytes from 172.16.2.1: icmp_seq=2 ttl=64 time=0.101 ms 64 bytes from 172.16.2.1: icmp_seq=3 ttl=64 time=0.100 ms 64 bytes from 172.16.2.1: icmp_seq=4 ttl=64 time=0.107 ms 64 bytes from 172.16.2.1: icmp_seq=5 ttl=64 time=0.105 ms --- 172.16.2.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 3998ms rtt min/avg/max/mdev = 0.100/0.125/0.215/0.046 ms === Except to the OpenBSD 3.9 system ( 172.16.2.25 ) I can logon to all other *nx systems very fast. OpenBSD 3.9 on amd64 seems to be very slow. Could Some one help me troubleshoot it? dmesg below Thankyou so much KInd Regards Siju OpenBSD 3.9 (GENERIC) #462: Thu Mar 2 03:52:16 MST 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 1039593472 (1015228K) avail mem = 879325184 (858716K) using 22937 buffers containing 104165376 bytes (101724K) of memory mainbus0 (root) cpu0 at mainbus0: (uniprocessor) cpu0: AMD Athlon(tm) 64 Processor 3400+, 2193.99 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,NXE,MMXX,FFXSR,LONG,3D NOW2,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 pci0 at mainbus0 bus 0: configuration mode 1 pchb0 at pci0 dev 0 function 0 ATI RS480 Host rev 0x10 ppb0 at pci0 dev 1 function 0 ATI RS480 PCIE rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 5 function 0 ATI Radeon XPRESS 200 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) pciide0 at pci0 dev 17 function 0 ATI IXP400 SATA rev 0x80: DMA pciide0: using irq 11 for native-PCI interrupt pciide0: port 0: device present, speed: 1.5Gb/s wd0 at pciide0 channel 0 drive 0: ST3120827AS wd0: 16-sector PIO, LBA48, 114473MB, 234441648 sectors wd0(pciide0:0:0): using BIOS timings, Ultra-DMA mode 6 pciide0: port 1: device present, speed: 1.5Gb/s wd1 at pciide0 channel 1 drive 0: ST3120827AS wd1: 16-sector PIO, LBA48, 114473MB, 234441648 sectors wd1(pciide0:1:0): using BIOS timings, Ultra-DMA mode 6 pciide1 at pci0 dev 18 function 0 ATI IXP400 SATA rev 0x80: DMA pciide1: using irq 5 for native-PCI interrupt ohci0 at pci0 dev 19 function 0 ATI IXP400 USB rev 0x80: irq 4, version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: ATI OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ohci1 at pci0 dev 19 function 1 ATI
Re: SSH login slow troubleshoot Techniques
On Wed, 30 Aug 2006, Siju George wrote: Hi, My OpenBSD 3.9 on an amd64 is very very slow for SSH login. Could some one give me steps I can follow to troubleshoot the problem? First on the openbsd machine check reserve name lookup of the client machine you're coming from. Also check how the ip of the openbsd machine resolves on the client machine. It might have multiple (IPv6?) ip's, some of which are unreachable. ssh -v might give more clues on that. -Otto
Re: SSH login slow troubleshoot Techniques
On Wed, Aug 30, 2006 at 05:54:31PM +0530, Siju George wrote: My OpenBSD 3.9 on an amd64 is very very slow for SSH login. Could some one give me steps I can follow to troubleshoot the problem? There's a few suggestions here: http://www.openssh.com/faq.html#3.3 From your description, my guess would be that the delay is due to the server attempting to do a reverse name lookup on the client's IP address (you can test this quickly by putting it into the server's host into the /etc/hosts file). If none of that helps, try running the client in debug mode (ssh -vvv ...) and see where the pauses are. -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.
CPAN error
Hi all, Yesterday I installed Openbsd3.9 and wanted to install Digest::SHA1 using CPAN I get an error complaining the MD5 checksum is incorrect and to delete it from /root/.cpan../../etc etc (which I did). This happens with other modules too. I can download the modules manually and run perl Makefile.pl, make make install, but was wandering why I'm having this problem. Thanks BSD Networking, Microsoft Notworking
Re: SSH login slow troubleshoot Techniques
On 8/30/06, Jonas Thambert [EMAIL PROTECTED] wrote: Check your resolv.conf/hosts file. Might be reverse-lookup that fails. Bull's eye! you hit it right on target Jonas. The 3.9 had an outdated nameserver entry. I updated it and it logs in through SSH real fast :-) Thanks a million :-))) Kind Regards Siju
Re: SSH login slow troubleshoot Techniques
Siju George wrote: Hi, My OpenBSD 3.9 on an amd64 is very very slow for SSH login. As already mentioned, if reverse lookup doesn't work your login will pause for a substantial amount of time before you are prompted. Assuming this is a network under your control, if your LAN is small you could just update the hosts files on your machines. If you have more than a few machines on the network, or a heterogeneous network where it isn't as simple as copying around a hosts file, you might want to look into using DNS internally. There have been a few times where my ISP has had DNS trouble which downed large numbers of their customers, but my machines were able to continue right along with no problems because of my internal DNS server. There's a little more work involved in setting it up, but once you read the man page for named and the BIND 9 Administrator Reference Manual (free PDF download) it comes together pretty quickly. I use an invalid TLD of .int to make sure I don't collide with a domain in the outside world, which has never failed me for internal use. You may even want to use DHCP to assign static IPs by using host declarations which assign a fixed-address to each host based on the MAC address. But I digress. Breeno
Re: Dell 1650 serial console
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hej David, David Golden wrote: On Wednesday 30 August 2006 13:00, Marian Hettwer wrote: Don't have a Dell 1650 specifically, but most pre-boot console redirection I've seen on PCs is basically screen-scraping the VGA text buffer. When you are running Debian linux, is login via a getty on [linux] ttyS0 once that system has booted, or is the system perhaps still actually screen-scraping VGA text, so logging in on the serial port is actually via a getty on [linux] tty1 ? Actually, I suspect the latter, because usually you have to edit the inittab post-install to enable a getty on ttyS0... Nay. If I do a pxeboot of Linux, I use the CONSOLE=ttyS0,9600n81 as a Kernel Parameter and do get serial console output. getty is afterwards started on ttyS0 So it's from BIOS to full boot always ttyS0 in Linux... However, On our PC systems with redirection, there is a BIOS setting for when the redirection cuts out, something like: always pre-boot shared disabled I'll check that... maybe something is interfering. regards, Marian iD8DBQFE9ZJNgAq87Uq5FMsRAiQSAJ45GeI2owiWCSDtCDcHMfwICibbBQCgyNwT i4auwGJpcQ1BVXOi/PvY+KQ= =P+xM -END PGP SIGNATURE-
Re: CPAN error
On Wed, Aug 30, 2006 at 08:46:25AM -0400, Monah Baki wrote: Hi all, Yesterday I installed Openbsd3.9 and wanted to install Digest::SHA1 using CPAN asking because you don't mention having a reason for trying CPAN rather than ports, but you could just pkg_add(1) the p5-Digest-SHA package and not worry about CPAN. lftp ftp.cse.buffalo.edu:/pub/OpenBSD/3.9/packages/i386 ls p5-Digest* -r--r--r-- 1 546 3864 Mar 4 12:40 p5-Digest-BubbleBabble-0.01.tgz -r--r--r-- 1 546 4209 Mar 4 12:40 p5-Digest-HMAC-1.01.tgz -r--r--r-- 1 546 9335 Mar 4 12:40 p5-Digest-MD2-2.03.tgz -r--r--r-- 1 546 9741 Mar 4 12:40 p5-Digest-MD5-M4p-0.01.tgz -r--r--r-- 1 54612244 Mar 4 12:40 p5-Digest-Nilsimsa-0.06.tgz -r--r--r-- 1 54633843 Mar 4 12:40 p5-Digest-SHA-5.32.tgz -r--r--r-- 1 54614597 Mar 4 12:40 p5-Digest-SHA1-2.10p0.tgz -- jared [ openbsd 4.0-beta GENERIC ( aug 3 ) // i386 ]
Re: Dell 1650 serial console
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hej David, second reply, after checking the BIOS settings. David Golden wrote: On our PC systems with redirection, there is a BIOS setting for when the redirection cuts out, something like: always pre-boot shared disabled The Dell only knows 3 Parameters for console redirection to serial port: enabled / disabled (is set do on obviously) Remote Terminal Type: ANSI or VT100 (is set to VT100) Redirection After Boot When I set the last paramter to disabled, I don't even see the pxeboot (pxe bootloader) of OpenBSD. Logically, I can't type in set tty com0. If I set this parameter to enabled, I can see the OpenBSD pxeboot and can type in stuff like set tty com0. But as mentioned earlier, the command is returned with com0 console not present. Damn... set tty com0 -- switching console to com0, com0 console not present Any more ideas? The server is remote, so I only have remote serial console and remote power. No KVM (and frankly, I don't want to have KVM for Unix systems anyway) ./Marian iD8DBQFE9ZUBgAq87Uq5FMsRAgL0AJsHvg5krFRWaP3NaCDM10DiTxBHdwCdG0xp r/C4VluNfZXvjcRmMwSUXdQ= =K/a1 -END PGP SIGNATURE-
Re: Dell 1650 serial console
On 2006/08/30 15:39, Marian Hettwer wrote: Redirection After Boot When I set the last paramter to disabled, I don't even see the pxeboot (pxe bootloader) of OpenBSD. Logically, I can't type in set tty com0. the console redirection is probably not sharing the serial port with the OS - try setting this to disabled and place set tty com0 in /etc/boot.conf (as is done when you answer yes to the do you want a serial console? question in the installer).
Re: Dell 1650 serial console
On Wednesday 30 August 2006 14:39, Marian Hettwer wrote: Redirection After Boot Any more ideas? Well, I guess, set redirection after boot to no, but tell obsd pxeboot to default to com0 with a /etc/boot.conf on the tftp server (see pxeboot man page...)
Re: Dell 1650 serial console
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stuart Henderson wrote: On 2006/08/30 15:39, Marian Hettwer wrote: Redirection After Boot When I set the last paramter to disabled, I don't even see the pxeboot (pxe bootloader) of OpenBSD. Logically, I can't type in set tty com0. the console redirection is probably not sharing the serial port with the OS - try setting this to disabled and place set tty com0 in /etc/boot.conf (as is done when you answer yes to the do you want a serial console? question in the installer). Did that. And also set image bsd.rd and boot bsd.rd, as I can't see anything at this point of my installation if I disabled the console redirection after boot. I wouldn't consider disabled the console redirection altogether, 'cause then you wouldn't have a chance to get into the BIOS. And you do want to get into the BIOS. See my other mail and thanks for the (same) idea ;) ./Marian iD8DBQFE9ZxegAq87Uq5FMsRAkT0AKCUh7junbXAkBeg6XURH9ujEkrrvQCg48Vo KBcZp/TWoVqw6i1l/BE4xFg= =aske -END PGP SIGNATURE-
Re: Dell 1650 serial console
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Replying to myself for the archives: Marian Hettwer wrote: The Dell only knows 3 Parameters for console redirection to serial port: enabled / disabled (is set do on obviously) Remote Terminal Type: ANSI or VT100 (is set to VT100) Redirection After Boot When I set the last paramter to disabled, I don't even see the pxeboot (pxe bootloader) of OpenBSD. Logically, I can't type in set tty com0. If I set this parameter to enabled, I can see the OpenBSD pxeboot and can type in stuff like set tty com0. But as mentioned earlier, the command is returned with com0 console not present. Damn... set tty com0 -- switching console to com0, com0 console not present Any more ideas? Yeah, I have more ideas to my own question... I disabled the Redirection After Boot again and created a etc/boot.conf in my tfptroot, consisting of the following lines set tty com0 set image bsd.rd boot bsd.rd files in my tftproot are now looking like that bsd.rd etc/boot.conf openbsd-pxe (aka pxeboot) bootet the Dell via pxe and see... - - no serial output while PXE asked for a DHCP server - - serial output seen as soon as bsd.rd bootet thus I'd say, the set tty com0 was successfull and before the BIOS was blocking the serial port. Linux can cope with this situation and OpenBSD can't. That's not particulary beautiful, as I am now missing the PXE output (which has some information available), but at least I can pxeboot the Dell and install OpenBSD via network. All in All, I'd say: Was easy with Linux, was a bit harder with OpenBSD, and as I'm now reading the FreeBSD docs on PXE... ugh! wtf and omfg. Why making easy things hard?? ./Marian iD8DBQFE9Zv/gAq87Uq5FMsRAkFfAKDf2NDYJMFtEeRjCmlIHCXwartDFgCeKBOk vF1/Nvxytf5d+3vUSfiMhBM= =LeND -END PGP SIGNATURE-
Re: Dell 1650 serial console
On 2006/08/30 16:10, Marian Hettwer wrote: When I set the last paramter to disabled, I don't even see the pxeboot (pxe bootloader) of OpenBSD. Logically, I can't type in set tty com0. the console redirection is probably not sharing the serial port with the OS - try setting this to disabled and place set tty com0 in /etc/boot.conf (as is done when you answer yes to the do you want a serial console? question in the installer). Did that. And also set image bsd.rd and boot bsd.rd, as I can't see anything at this point of my installation if I disabled the console redirection after boot. ah, this is pre-install then? are you sure boot.conf is being loaded from the tftp server? (I'm probably stating the obvious here, but it should be in /tftpboot/etc/boot.conf not in /tftpboot/boot.conf, and of course needs to be readable by the tftp server) you only need set image, not boot, it should just timeout after 5 seconds and load whatever image is set. I wouldn't consider disabled the console redirection altogether, 'cause then you wouldn't have a chance to get into the BIOS. And you do want to get into the BIOS. well, depends where you expect to have a problem... if it's a choice of only one or the other, I'd rather have OS than BIOS, but BIOS is nice to have too.
Re: Dell 1650 serial console
On Wednesday 30 August 2006 15:09, Marian Hettwer wrote: Linux can cope with this situation and OpenBSD can't. Hmph. Could well just be because linux (or at least syslinux) blindly assumes something that openbsd (probably correctly) checks, though?
[/tmp partition secure]
Friends, I'm needing to mount a /tmp partition in a secure mode. Which is the best way to fstab file configuration? Thanks in advance, Denis
Sparc64 3.9 issue
This may or may not be related to the NIC adaptor, but I will try to describe the problem as best I can. Hardware: SunBlade 100- Sparc64 NIC: Gem0 Issue: About every 2-3 weeks the NIC stops working, issueing an ifconfig down followed by an ifconfig up does something to wake the interface up, and all works... for another coupple of weeks. The last time this happend was about 9-10 days ago. Ideas? Let me know! Dmesg output follows: console is keyboard/display Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2006 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 3.9 (GENERIC) #759: Wed Mar 1 01:32:54 MST 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/sparc64/compile/GENERIC total memory = 536870912 avail memory = 478429184 using 3276 buffers containing 26836992 bytes of memory bootpath: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 mainbus0 (root): Sun Blade 100 (UltraSPARC-IIe) cpu0 at mainbus0: SUNW,UltraSPARC-IIe @ 502 MHz, version 0 FPU cpu0: physical 32K instruction (32 b/l), 16K data (32 b/l), 1024K external (64 b/l) psycho0 at mainbus0 pci108e,a001: impl 0, version 0: ign 7c0 bus range 0 to 1; PCI bus 0 DVMA map: c000 to e000 IOTDB: 26a8000 to 2728000 pci0 at psycho0 ebus0 at pci0 dev 12 function 0 Sun PCIO Ebus2 (US III) rev 0x01 flashprom at ebus0 addr 0-f not configured clock1 at ebus0 addr 0-1fff: mk48t59: hostid 830b72de ebus_attach: idprom: incomplete gem0 at pci0 dev 12 function 1 Sun ERI Ether rev 0x01: ivec 3006, address 00:03:ba:0b:72:de ukphy0 at gem0 phy 1: Generic IEEE 802.3u media interface, rev. 1: OUI 0x0010dd, model 0x0002 Sun FireWire rev 0x01 at pci0 dev 12 function 2 not configured ohci0 at pci0 dev 12 function 3 Sun USB rev 0x01: ivec 24, version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: Sun OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ebus1 at pci0 dev 7 function 0 Acer Labs M1533 ISA rev 0x00 dma at ebus1 addr 0- ipl 42 not configured power at ebus1 addr 800-82f ipl 32 not configured com0 at ebus1 addr 3f8-3ff ipl 43: ns16550a, 16 byte fifo com1 at ebus1 addr 2e8-2ef ipl 43: ns16550a, 16 byte fifo alipm0 at pci0 dev 3 function 0 Acer Labs M7101 Power rev 0x00: 223KHz clock, disabling to avoid hardware failure autri0 at pci0 dev 8 function 0 Acer Labs M5451 Audio rev 0x01: ivec 23 ac97: codec id 0x41445348 (Analog Devices AD1881A) ac97: codec features headphone, Analog Devices Phat Stereo audio0 at autri0 midi0 at autri0: 4DWAVE MIDI UART pciide0 at pci0 dev 13 function 0 Acer Labs M5229 UDMA IDE rev 0xc3: DMA, channel 0 configured to native-PCI, channel 1 configured to native-PCI pciide0: using ivec 180c for native-PCI interrupt wd0 at pciide0 channel 0 drive 0: IC35L060AVV207-0 wd0: 16-sector PIO, LBA48, 38146MB, 78125000 sectors atapiscsi0 at pciide0 channel 0 drive 1 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: LITEON, CD-ROM LTN486S, YSU1 SCSI0 5/cdrom removable wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 cd0(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2 pciide0: channel 1 disabled (no drives) vgafb0 at pci0 dev 19 function 0 ATI Rage XL rev 0x27 wsdisplay0 at vgafb0: console (std, sun emulation) ppb0 at pci0 dev 5 function 0 DEC 21152 PCI-PCI rev 0x03 pci1 at ppb0 bus 1 pcons at mainbus0 not configured No counter-timer -- using %tick at 502MHz as system clock. uhub1 at uhub0 port 4 uhub1: Texas Instruments TUSB2046 hub, rev 1.10/1.25, addr 2 uhub1: 4 ports with 4 removable, self powered uhidev0 at uhub1 port 1 configuration 1 interface 0 uhidev0: ATEN 4 Port USB KVM B V1.30, rev 1.10/1.00, addr 3, iclass 3/1 ukbd0 at uhidev0: 8 modifier keys, 6 key codes wskbd0 at ukbd0: console keyboard, using wsdisplay0 uhidev1 at uhub1 port 1 configuration 1 interface 1 uhidev1: ATEN 4 Port USB KVM B V1.30, rev 1.10/1.00, addr 3, iclass 3/1 ums0 at uhidev1: 5 buttons and Z dir. wsmouse0 at ums0 root on wd0a rootdev=0xc00 rrootdev=0x1a00 rawdev=0x1a02 WARNING: / was not properly unmounted gem0: receive error: CRC error gem0: receive error: CRC error uhub1: at uhub0 port 4 (addr 2) disconnected uhidev0: at uhub1 port 1 (addr 3) disconnected ukbd0: was console keyboard wskbd0 detached ukbd0 detached uhidev0 detached uhidev1: at uhub1 port 1 (addr 3) disconnected wsmouse0 detached ums0 detached uhidev1 detached uhub1 detached gem0: receive error: CRC error gem0: receive error: CRC error gem0: receive error: CRC error gem0: receive error: CRC error gem0: receive error: CRC error gem0: receive error: CRC error gem0: receive error: CRC error gem0: receive error: CRC error gem0: receive error: CRC error gem0: receive error: CRC error gem0: receive error: CRC error gem0: receive error: CRC error gem0: receive error: CRC error gem0: receive error: CRC error gem0: receive error: CRC error gem0: receive error: CRC error gem0: receive error: CRC
Re: Dell 1650 serial console
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Golden wrote: On Wednesday 30 August 2006 15:09, Marian Hettwer wrote: Linux can cope with this situation and OpenBSD can't. Hmph. Could well just be because linux (or at least syslinux) blindly assumes something that openbsd (probably correctly) checks, though? In this specific case it's pxelinux.0 which gets loaded via PXE and then loads the kernel (linux itself) with some parameters for serial console output. In this regards, it's Linux itself doing something different than OpenBSD. What it is? Dunno... In an administrator standpoint, Linux is doing the better thing, attaching a serial console, although the BIOS is already using that serial port. (And no, this is not a flame bait. I do prefer OpenBSD (and FreeBSD) over Linux, a lot!) ./Marian iD8DBQFE9a1HgAq87Uq5FMsRAku6AJ9B1aVtwINGH3ve0yIFksatiYqeFQCdE/lf GetE/G4ke7ryYBfRdnZ/Ktw= =8EAx -END PGP SIGNATURE-
Re: Dell 1650 serial console
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hej Stuart, Stuart Henderson wrote: On 2006/08/30 16:10, Marian Hettwer wrote: Did that. And also set image bsd.rd and boot bsd.rd, as I can't see anything at this point of my installation if I disabled the console redirection after boot. ah, this is pre-install then? pre-install? Well, consider it a machine with a brand new hard disk with nothing one it what so ever :) are you sure boot.conf is being loaded from the tftp server? It is... (I'm probably stating the obvious here, but it should be in /tftpboot/etc/boot.conf not in /tftpboot/boot.conf, and of course needs to be readable by the tftp server) Of course it is $TFTPROOT/etc/boot.conf (in my case TFTPBOOT is /boot/fai) you only need set image, not boot, it should just timeout after 5 seconds and load whatever image is set. Okay... so my machine is booting 5 seconds earlier ;) As I can't access the bootloader to type in commands anyway, I'd rather force him too boot bsd.rd than wait 5 seconds, seeing nothing :( I wouldn't consider disabled the console redirection altogether, 'cause then you wouldn't have a chance to get into the BIOS. And you do want to get into the BIOS. well, depends where you expect to have a problem... if it's a choice of only one or the other, I'd rather have OS than BIOS, but BIOS is nice to have too. Well, if I want to check within the BIOS to play around with Console Redirection I need my BIOS output redirected to serial... so BIOS is not just a nice to have. Think further: SCSI controllers which you can access just after POST, but before OS... I'm still wondering, why OpenBSD complains about com0 and linux doesn't if console redirection after BOOT is enabled. hm hm hm... not 100% satisfying :-/ hopefully I can find enough arguments pro OpenBSD (in our company), as we are using Debian Linux only and I'd like to force alternatives (OpenBSD) :) ./Marian PS.: And since we are using FAI to automatically setup our servers, Debian already has a huge advantage. FAI is, to be honest, a beautiful piece of software (shell scripts) to do Fully Automated Installations. Unluckily it only supports Debian Linux... iD8DBQFE9ay/gAq87Uq5FMsRAmh0AJwOK+WPhwm2OsL+R1QFnA8PQx69FACgjIXW Tbl7V3XsE0iiH6e8B+bibr8= =ky0B -END PGP SIGNATURE-
Re: Sparc64 3.9 issue
I have replaced the network cable, and the hub that it is attached to... Do we have case of bit rot here? Or maybe different NIC chip sets... I'm getting a lot of CRC errors, but nothing shows up in netstat -ni... gem01500 Link 00:03:ba:0b:72:de 9525295 0 1733115 0 167809 gem01500 fe80::%gem0 fe80::203:baff:fe 9525295 0 1733115 0 167809 gem01500 192.168.0/ 192.168.0.52 9525295 0 1733115 0 167809 fv wrote: Hello, I'im using the same hardware (sun blade 100) and obsd version 3.9. I have no such problem. Maybe it's your network cable. Have you other strange problems. Maybe it can be your RAM. Here is my dmesg: [EMAIL PROTECTED]/var/log% dmesg console is keyboard/display Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2006 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 3.9-stable (GENERIC) #0: Wed Jul 5 11:55:19 CEST 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/sparc64/compile/GENERIC total memory = 1342177280 avail memory = 1212760064 using 8192 buffers containing 67108864 bytes of memory bootpath: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 mainbus0 (root): Sun Blade 100 (UltraSPARC-IIe) cpu0 at mainbus0: SUNW,UltraSPARC-IIe @ 502 MHz, version 0 FPU cpu0: physical 32K instruction (32 b/l), 16K data (32 b/l), 1024K external (64 b/l) psycho0 at mainbus0 pci108e,a001: impl 0, version 0: ign 7c0 bus range 0 to 1; PCI bus 0 DVMA map: c000 to e000 IOTDB: 61b8000 to 6238000 pci0 at psycho0 ebus0 at pci0 dev 12 function 0 Sun PCIO Ebus2 (US III) rev 0x01 flashprom at ebus0 addr 0-f not configured clock1 at ebus0 addr 0-1fff: mk48t59: hostid 830ced19 ebus_attach: idprom: incomplete gem0 at pci0 dev 12 function 1 Sun ERI Ether rev 0x01: ivec 3006, address 00:03:ba:0c:ed:19 ukphy0 at gem0 phy 1: Generic IEEE 802.3u media interface, rev. 1: OUI 0x0010dd, model 0x0002 Sun FireWire rev 0x01 at pci0 dev 12 function 2 not configured ohci0 at pci0 dev 12 function 3 Sun USB rev 0x01: ivec 24, version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: Sun OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ebus1 at pci0 dev 7 function 0 Acer Labs M1533 ISA rev 0x00 dma at ebus1 addr 0- ipl 42 not configured power at ebus1 addr 800-82f ipl 32 not configured com0 at ebus1 addr 3f8-3ff ipl 43: ns16550a, 16 byte fifo com1 at ebus1 addr 2e8-2ef ipl 43: ns16550a, 16 byte fifo alipm0 at pci0 dev 3 function 0 Acer Labs M7101 Power rev 0x00: 223KHz clock, disabling to avoid hardware failure autri0 at pci0 dev 8 function 0 Acer Labs M5451 Audio rev 0x01: ivec 23 ac97: codec id 0x41445348 (Analog Devices AD1881A) ac97: codec features headphone, Analog Devices Phat Stereo audio0 at autri0 midi0 at autri0: 4DWAVE MIDI UART pciide0 at pci0 dev 13 function 0 Acer Labs M5229 UDMA IDE rev 0xc3: DMA, channel 0 configured to native-PCI, channel 1 configured to native-PCI pciide0: using ivec 180c for native-PCI interrupt wd0 at pciide0 channel 0 drive 0: ST320414A wd0: 16-sector PIO, LBA, 19458MB, 39851760 sectors atapiscsi0 at pciide0 channel 0 drive 1 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: LITEON, CD-ROM LTN486S, YSU1 SCSI0 5/cdrom removable wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 cd0(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2 pciide0: channel 1 disabled (no drives) ppb0 at pci0 dev 5 function 0 DEC 21152 PCI-PCI rev 0x03 pci1 at ppb0 bus 1 vr0 at pci1 dev 1 function 0 VIA VT6105 RhineIII rev 0x86: ivec a, address 00:11:95:e4:2c:79 ukphy1 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 4: OUI 0x004063, model 0x0034 vgafb0 at pci0 dev 19 function 0 ATI Rage XL rev 0x27 wsdisplay0 at vgafb0: console (std, sun emulation) pcons at mainbus0 not configured No counter-timer -- using %tick at 502MHz as system clock. uhidev0 at uhub0 port 4 configuration 1 interface 0 uhidev0: Sun Microsystems Type 6 Keyboard, rev 1.00/1.01, addr 2, iclass 3/1 ukbd0 at uhidev0: 8 modifier keys, 6 key codes wskbd0 at ukbd0: console keyboard, using wsdisplay0 root on wd0a rootdev=0xc00 rrootdev=0x1a00 rawdev=0x1a02 WARNING: / was not properly unmounted ural0 at uhub0 port 1 ural0: ANI 802.11g W, rev 2.00/0.01, addr 3 ural0: MAC/BBP RT2570 (rev 0x03), RF RT2526, address 00:11:95:86:e3:35 --- David Bryan wrote: This may or may not be related to the NIC adaptor, but I will try to describe the problem as best I can. Hardware: SunBlade 100- Sparc64 NIC: Gem0 Issue: About every 2-3 weeks the NIC stops working, issueing an ifconfig down followed by an ifconfig up does something to wake the interface up, and all works... for another
Re: Any modern wireless injection tools for OpenBSD?
Hi all. When it comes to auditing wireless networks, I notice that linux users lives happily with aireplay from aircrack suite. Unfortunately, it seems like there is no any tool similar to aireplay in BSD world. In past days, we had wnet suite, with reinj and dinject, but those days are all gone now, and it doesn't work with OpenBSD solid wireless stack. So while doing wireless audit or wireless network penetration testing, I should reboot into linux livecd. It annoys me. Does anybody aware of tool which can inject arbitrary packets and wireless frames into wireless network, and works under OpenBSD? have a look at hostapd(8) and bpf(4). The OpenBSD HostAPD supports some kind of packet injection and uses our extended BPF interface to send raw 802.11 frames. you can also find a example for the BPF interface here: http://team.vantronix.net/~reyk/deauth.c reyk
Re: pf + os detection - How to block a Host if it does a nmap scan?!
On 8/29/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hello everybody, OpenBSDs PF is able to block Packets by the passiv OS fingerprint. For example you can block packets from nmap. I4ve a little problem witht hat: How to block a host if it does/did a nmap-Scan?! I can block the nmap-scan but not automaticly the host because the overload-rule does not know about blocking by OSs. I know of only a means to block nmap scans if used with the -i parameter. It continaully connects to your ident port for each open port discovered to attempt to identify the owner of the service. (Does the webserver run as root?) You could do a 3/30 overload rule on port 113 and add to a table to drop and log. Let them scan, what are you worried about? If you have something you are worried about nmap discovering, blocking an nmap scan isn't going to help. If I were a cracker and scanned your netblock, and your host is the only one that stopped responding half-way through a scan, I would use other means to begin looking at yours immediatly. (Or you may be a winbox I just crashed...) Block drop as a default policy may be better for your needs. It annoys inpatient nmap scanners to give up quickly. nmap is getting quicker at scanning hosts that drop blocked packets, especialy when options are fine-tuned for it. Also by default nmap skips hosts that don't reply to icmp pings. Whatever.
STP over an IPSEC bridge?
Is it possible? brconfig man pages says: The bridge has support for 802.1D Spanning Tree Protocol (STP), which can be used to detect and remove loops in a network topology. Using the stp or -stp commands to brconfig, STP can be enabled or disabled on each port. STP will not work on gif(4) members because they lack a hardware MAC address. So I assume that it isn't, but in case anybody knows any workable solution over OpenBSD I would like to know. I would prefer this solution instead of having to fight with Cisco gear and L2TP which seems much more complex (and expensive!). I need a bridge over the internet in case the long fiber link between our main and secondary datacenter fails (bandwidth difference is huge, but it would suffice for our critical apps). STP is necessary for obvius reasons. Thanks in advance, Samuel
Re: [/tmp partition secure]
On 8/30/06, Denis Augusto Araujo de Souza [EMAIL PROTECTED] wrote: Friends, I'm needing to mount a /tmp partition in a secure mode. Which is the best way to fstab file configuration? chmod 0 /tmp ? that's a pretty secure mode. not too useful though.
Re: STP over an IPSEC bridge?
A solution which works across several operation systems might be openvpn (http://www.openvpn.net) Openvpn creates tap/tun interfaces which have ethernet addresses and support bridging. Its track record security wise has been pretty good afaik. And its implementation crypto wise is ok (from heresay though, not an expert here). Regards - Bolke Samuel Moqux wrote: Is it possible? brconfig man pages says: The bridge has support for 802.1D Spanning Tree Protocol (STP), which can be used to detect and remove loops in a network topology. Using the stp or -stp commands to brconfig, STP can be enabled or disabled on each port. STP will not work on gif(4) members because they lack a hardware MAC address. So I assume that it isn't, but in case anybody knows any workable solution over OpenBSD I would like to know. I would prefer this solution instead of having to fight with Cisco gear and L2TP which seems much more complex (and expensive!). I need a bridge over the internet in case the long fiber link between our main and secondary datacenter fails (bandwidth difference is huge, but it would suffice for our critical apps). STP is necessary for obvius reasons. Thanks in advance, Samuel
Re: How to mail attachments from the comand line?
On 30 Aug 2006, at 19:51, Torsten Geile wrote: mail -a file -s test recepient . would do it, but actually in my case it doesn't. I think you have to send it in base64 encoded form, with a few added headers. What's simpler would be to put it in some publicly accessible place (like a website) and send the URL to the file rather than the file itself. Gaby -- Junkets for bunterish lickspittles since 1998! http://www.playr.co.uk/sudoku/ http://weblog.vanhegan.net/
Re: How to mail attachments from the comand line?
On 30 Aug 2006, at 20:08, Gaby Vanhegan wrote: I think you have to send it in base64 encoded form, with a few added headers. What's simpler would be to put it in some publicly accessible place (like a website) and send the URL to the file rather than the file itself. Sorry, wrong list... :) Gaby -- Junkets for bunterish lickspittles since 1998! http://www.playr.co.uk/sudoku/ http://weblog.vanhegan.net/
Re: OpenBSD artwork website wording
:( I wanted to also give OpenBSD a little free marketing (the monthly traffic of the Ronja website http://ronja.twibright.com is IIRC around 10GB) by proudly stating we use it on the project (well, me on my devel machine), but it looks like every time I discuss OpenBSD on the Ronja mailing list I would have to take care whether I already put OpenBSD into negative light or not yet, and possibly remove the logo. Which is a bit impractical to keep on my mind for indefinite future so I am better removing the picture now and leaving just a textual link. [EMAIL PROTECTED]:~/creat/ronja/trunk/grx/tools$ svn rm openbsd.png D openbsd.png At least I don't have to have a special paragraph dedicated to OpenBSD logo on the Ronja copyright page :) CL On Wed, Aug 30, 2006 at 11:27:26AM -0600, Theo de Raadt wrote: Yes, it means that if you are an asshole towards OpenBSD we withdraw your right to use *OUR* artwork. That is EXACTLY what it means. That's how every COPYRIGHT and TRADEMARK holder in the world does this, and how we will. We have to. There are laws which demand that we protect our image, because if we don't protect it, noone will help us protect it. Now please, I have way more important things to do. Return-Path: [EMAIL PROTECTED] Delivery-Date: Wed Aug 30 11:25:22 2006 Received: from twin.jikos.cz (twin.jikos.cz [213.151.79.26]) by cvs.openbsd.org (8.13.6/8.12.1) with ESMTP id k7UHPKtM012419 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=FAIL) for [EMAIL PROTECTED]; Wed, 30 Aug 2006 11:25:21 -0600 (MDT) Received: from kestrel.twibright.com (zux221-122-143.adsl.green.ch [81.221.122.143]) (authenticated bits=0) by twin.jikos.cz (8.13.6/8.13.6) with ESMTP id k7UHPDah011103 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Aug 2006 19:25:14 +0200 Received: from clock by kestrel.twibright.com with local (Exim 4.60) (envelope-from [EMAIL PROTECTED]) id 1GIToP-0006Ko-FE; Wed, 30 Aug 2006 19:25:13 +0200 Date: Wed, 30 Aug 2006 19:25:13 +0200 From: Karel Kulhavy [EMAIL PROTECTED] To: Theo de Raadt [EMAIL PROTECTED] Cc: Twibright Ronja [EMAIL PROTECTED] Subject: Re: OpenBSD artwork website wording Message-ID: [EMAIL PROTECTED] References: [EMAIL PROTECTED] [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: [EMAIL PROTECTED] X-Orientation: Gay X-Stance: Goofy User-Agent: Mutt/1.5.11 On Wed, Aug 30, 2006 at 10:42:04AM -0600, Theo de Raadt wrote: I would personally see terms you can use the logo to represent your usage of OpenBSD or compatibility with OpenBSD more appropriate for a free software project logo than the band-aid-over-mouth represent OpenBSD in a positive light. except those are not the types of terms that we can reasonably do, and still be protecting our rights. i've researched what we can do. i've researched the downsides. please don't lecture me... i'm trying to do the best for everyone. But does it then mean that I cannot criticize OpenBSD in connection with Ronja? CL
Re: SSH login slow troubleshoot Techniques
Siju George [EMAIL PROTECTED] writes: My OpenBSD 3.9 on an amd64 is very very slow for SSH login. One very common cause of slow response to ssh login requests is some sort of error in name resolution. Reverse lookups which do not complete or does not return the expected result is one of several conditions which could lead to the observed symptoms. -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/ First, we kill all the spammers The Usenet Bard, Twice-forwarded tales 20:11:56 delilah spamd[26905]: 146.151.48.74: disconnected after 36099 seconds
Re: chroot /emul/linux /bin/sh
I didn't send to mutch valuable information. I'm testing Linux compatibility layer under OpenBSD, and was to lazy to put full path of commands under /emu/linux (/usr/local/emul/redhat). Found some issue with rename() probably but that's is other story[1]. I was quite surprise when I put this command: chroot /emul/linux /bin/sh This is full example: # pwd /root # ls -ilhd . 81 drwx-- 4 root wheel 1.0K Aug 30 08:03 . # date Wed Aug 30 22:39:30 IST 2006 # chroot /emul/linux /bin/sh Here I noticed that mplayer, which played local mp3 (today I tested it again on http streaming, same result) stops, but this is not a problem, it's just symptom of.. # pwd /root # ls -ilhd . 81 drwx-- 4 root wheel 1.0K Aug 30 08:03 . # date Thu Jan 1 01:00:02 IST 1970 And that why I sending this mail, I was really surprise here. # rdate -n vega.cbk.poznan.pl Wed Aug 30 22:40:20 IST 2006 # date Wed Aug 30 22:40:21 IST 2006 I'm attaching output of pkg_info and dmesg. Package redhat_base is mine production, but there are just few additional rpms[1]. I'm not on misc@ so please CC me. References 1. http://marc.theaimsgroup.com/?l=openbsd-portsm=115691903407456w=2 -- best regards q# OpenBSD 4.0-beta (GENERIC) #1079: Sat Aug 19 14:01:09 MDT 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) M processor 1.86GHz (GenuineIntel 686-class) 1.87 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,SBF,EST,TM2 cpu0: unknown Enhanced SpeedStep CPU, msr 0x06120e2906000e29 cpu0: using only highest and lowest power states cpu0: Enhanced SpeedStep 1867 MHz (1356 mV): speeds: 1867, 800 MHz real mem = 1073119232 (1047968K) avail mem = 970907648 (948152K) using 4256 buffers containing 5376 bytes (52500K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(00) BIOS, date 10/02/05, BIOS32 rev. 0 @ 0xffe90, SMBIOS rev. 2.3 @ 0xf7860 (60 entries) bios0: Dell Inc. Latitude D610 pcibios0 at bios0: rev 2.1 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfb2c0/192 (10 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82371 ISA and IDE rev 0x00) pcibios0: PCI bus #4 is the last bus bios0: ROM list: 0xc/0x1 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82915GM/PM/GMS Host rev 0x03 ppb0 at pci0 dev 1 function 0 Intel 82915PM/GM PCIE rev 0x03 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 ATI Radeon Mobility M300 M22 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ppb1 at pci0 dev 28 function 0 Intel 82801FB PCIE rev 0x03 pci2 at ppb1 bus 2 bge0 at pci2 dev 0 function 0 Broadcom BCM5751 rev 0x01, BCM5750 A1 (0x4001): irq 11, address 00:14:22:d9:e8:14 brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0 uhci0 at pci0 dev 29 function 0 Intel 82801FB USB rev 0x03: 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 82801FB USB rev 0x03: irq 10 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 82801FB USB rev 0x03: irq 9 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 uhci3 at pci0 dev 29 function 3 Intel 82801FB USB rev 0x03: irq 5 usb3 at uhci3: USB revision 1.0 uhub3 at usb3 uhub3: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0 at pci0 dev 29 function 7 Intel 82801FB USB rev 0x03: irq 11 usb4 at ehci0: USB revision 2.0 uhub4 at usb4 uhub4: Intel EHCI root hub, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered ppb2 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0xd3 pci3 at ppb2 bus 3 cbb0 at pci3 dev 1 function 0 TI PCI6515 CardBus rev 0x00: irq 5 TI PCI6515 CardBus (Smart Card mode) rev 0x00 at pci3 dev 1 function 5 not configured cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 4 device 0 cacheline 0x10, lattimer 0x20 pcmcia0 at cardslot0 auich0 at pci0 dev 30 function 2 Intel 82801FB AC97 rev 0x03: irq 11, ICH6 AC97 ac97: codec id 0x83847650 (SigmaTel STAC9750/51) ac97: codec features headphone, 20 bit DAC, 20 bit ADC, SigmaTel 3D audio0 at auich0 Intel 82801FB Modem rev 0x03 at pci0 dev 30 function 3 not configured ichpcib0 at pci0 dev 31 function 0 Intel 82801FBM LPC rev 0x03: PM disabled pciide0 at pci0 dev 31 function 2 Intel 82801FBM SATA rev 0x03: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: ST960822A wd0: 16-sector PIO, LBA48, 57231MB, 117210240 sectors wd0(pciide0:0:0): using PIO mode 4,
Re: [/tmp partition secure]
On Wed, 30 Aug 2006, Ted Unangst wrote: I'm needing to mount a /tmp partition in a secure mode. Which is the best way to fstab file configuration? chmod 0 /tmp ? that's a pretty secure mode. not too useful though. You can always try 'chmod 1733 /tmp' though. -- Antoine
Re: [/tmp partition secure]
Denis Augusto Araujo de Souza wrote on 30/08/2006 17:11: I'm needing to mount a /tmp partition in a secure mode. Which is the best way to fstab file configuration? it depends on what secure is for you ? no /tmp maybe ? or restricting to root access ? or using noexec,nodev,nosuid flags ? or using default openbsd flags ... (write your own) Regards Julien note: first two may/will break some apps ...
Re: chroot /emul/linux /bin/sh
chroot /emul/linux /bin/sh # date Thu Jan 1 01:00:02 IST 1970 I ran in this problem, before, too. But back then I found out that others had similar problems, and in the end I gave up on running Linux executables chroot'ed OTOH, according to this message, you might be successful, if you are more careful: http://marc.theaimsgroup.com/?l=openbsd-miscm=111980607406780w=2
Re: Soekris
Nick Holland [EMAIL PROTECTED] wrote: Not really. However a 2Mbps DSL line is not the fastest out there... a friend of mine is griping about his 200MHz PPro (which will probably run circles around the 4801) being unable to keep up with his 6Mbps DSL line with PPPoE. I haven't investigated personally, but I've got some reason to not ignore his warnings. A few other people have run into problems with PPPoE on hardware that would have giggled at a simple Ethernet connection, so throwing underpowered hardware at a DSL line would not be my first choice. Weren't these types of issues solved by the in-kernel PPPoE? -- Do you even send e-mails? I told you, I'm from the Wild West. I write by hand. -- Chuck Norris
Re: Soekris
Chris Cappuccio wrote: Nick Holland [EMAIL PROTECTED] wrote: Not really. However a 2Mbps DSL line is not the fastest out there... a friend of mine is griping about his 200MHz PPro (which will probably run circles around the 4801) being unable to keep up with his 6Mbps DSL line with PPPoE. I haven't investigated personally, but I've got some reason to not ignore his warnings. A few other people have run into problems with PPPoE on hardware that would have giggled at a simple Ethernet connection, so throwing underpowered hardware at a DSL line would not be my first choice. Weren't these types of issues solved by the in-kernel PPPoE? I've been informed that's the case. I've also since found out the friend who was griping about his PPro and PPPoE wasn't even running OpenBSD. (oops! Gotta pick my friends better!). So..disregard that part of my comments. The thing could still be a frustrating first OpenBSD system for someone. It's a great machine for what it is...but not as a Welcome to OpenBSD system. My overall recommendation stands. Get used to OpenBSD on familiar hardware, then get used to unusual hardware with an OS you are familiar with (preferably, OpenBSD. :) Nick.
Re: The future of NetBSD
On 8/30/06, Charles M. Hannum [EMAIL PROTECTED] wrote: The NetBSD Project has stagnated to the point of irrelevance. It has gotten to the point that being associated with the project is often more of a liability than an asset. I will attempt to explain how this happened, what the current state of affairs is, and what needs to be done to attempt to fix the situation. [snip] Much of this early structure (CVS, web site, cabal, etc.) was copied verbatim by other open source (this term not being in wide use yet) projects -- even the form of the project name and the term core. This later became a kind of standard template for starting up an open source project. That's very interesting history, if true (and I don't see why it wouldn't be)! Don't feel bad then, if you have accomplished that. [snip] -- At this point most readers are probably wondering whether I'm just writing a eulogy for the NetBSD project. In some ways, I am -- it's clear that the project, as it currently exists, has no future. It will continue to fall further behind, and to become even less relevant. This is a sad conclusion to a project that had such bright prospects when it started. I admit that I may be wrong about this, but I assume that most people who have contributed to NetBSD, and/or continue to do so, do not desire to see the project wallow away like this. So I will outline what I think is the only way out: [snip] *cough*Most of these ideas have been in the OpenBSD culture from the beginning*cough* - Charles Hannum - past founder, developer, president and director of The NetBSD Project and The NetBSD Foundation; sole proprietor of The NetBSD Mission; proprietor of The NetBSD CD Project. [I'm CCing this to FreeBSD and OpenBSD lists in order to share it with the wider *BSD community, not to start a flame war. I hope that people reading it have the tact to be respectful of their peers, and consider how some of these issues may apply to them as well.] Um. Wow. I think Theo wins. -Nick
Re: The future of NetBSD
On 31/08/06, Charles M. Hannum [EMAIL PROTECTED] wrote: The NetBSD Project has stagnated to the point of irrelevance. If true, unfortunate. A sad day. Jeff.
The future of NetBSD
The NetBSD Project has stagnated to the point of irrelevance. It has gotten to the point that being associated with the project is often more of a liability than an asset. I will attempt to explain how this happened, what the current state of affairs is, and what needs to be done to attempt to fix the situation. As one of the 4 originators of NetBSD, I am in a fairly unique position. I am the only one who has continuously participated and/or watched the project over its entire history. Many changes have taken place, and at the same time many things have remained the same -- including some of our early mistakes. I'd like to say that I'm some great visionary, who foresaw the whole OSS market, but the fact is that's BS. When we started the project, Linux and 386BSD were both little hobbyist systems, both pretty buggy, and both lacking a lot of important hardware support. Mostly we were scratching an itch: there was no complete package of 386BSD plus the necessary patches to make it run on more systems and fix bugs, and there was no sign that Bill Jolitz was going to resurface and do anything. Much of the project structure evolved because of problems we had early on. Probably our best choice was to start using central version control right off; this has enabled a very wide view of the code history and (eventually) made remote collaboration with a large number of developers much easier. Some other things we fudged; e.g. Chris got tired of being the point man for everything, and was trying to graduate college, so we created an internal cabal for managing the project, which became known as the core group. Although the web was very new, we set up a web site fairly early, to disseminate information about the project and our releases. Much of this early structure (CVS, web site, cabal, etc.) was copied verbatim by other open source (this term not being in wide use yet) projects -- even the form of the project name and the term core. This later became a kind of standard template for starting up an open source project. Unfortunately, we made some mistakes here. As we've seen over the years, one of the great successes of Linux was that it had a strong leader, who set goals and directions, and was able to get people to do what he wanted -- or find someone else to do it. This latter part is also a key element; there was no sense that anyone else owned a piece of Linux (although de facto ownership has happened in some parts); if you didn't produce, Linus would use someone else's code. If you wanted people to use your stuff, you had to keep moving. NetBSD did not have this. Partly due to lack of people, and partly due to a more corporate mentality, projects were often locked. One person would say they were working on a project, and everyone else would be told to refer to them. Often these projects stagnated, or never progressed at all. If they did, the motivators were often very slow. As a result, many important projects have moved at a glacial pace, or never materialized at all. I'm sorry to say that I helped create this problem, and that most of the projects which modeled themselves after NetBSD (probably due to its high popularity in 1993 and 1994) have suffered similar problems. FreeBSD and XFree86, for example, have both forked successor projects (Dragonfly and X.org) for very similar reasons. Unfortunately, these problems still exist in the NetBSD project today, and nothing is being done to fix them. -- I won't attempt to pin blame on any specific people for this, except to say that some of it is definitely my fault. It's only in retrospect that I see so clearly the need for a very strong leader. Had I pursued it 10 years ago, things might be very different. Such is life. But let's talk about the situation today. Today, the project is run by a different cabal. This is the result of a coup that took place in 2000-2001, in which The NetBSD Foundation was taken over by a fraudulent change of the board of directors. (Note: It's probably too late for me to pursue any legal remedy for this, unfortunately.) Although The NetBSD Project and The NetBSD Foundation were intended from the start to be separate entities -- the latter supplying support infrastructure for the former -- this distinction has been actively blurred since, so that the current board of TNF has rather tight control over many aspects of TNP. Were TNF comprised of a good set of leaders, this situation might be somewhat acceptable -- though certainly not ideal. The problem is, there are really no leaders at this point. Goals for releases are not based on customer feedback or looking forward to future needs, but solely on the basis of what looks like it's bubbled up enough that it might be possible to finish in time. There is no high-level direction; if you ask what about the problems with threads or will there be a flash-friendly file system, the best you'll get is we'd love to have both -- but no work is done to recruit
Re: The future of NetBSD
Hello Charles, Some parts of your message seemed to be flames resulting from some past personality conflict that I know nothing about, so I won't comment further on those. Clearly you are more familiar with BSD internals than I am. I imagine others will pickup various technical points such as LFS and threading. I can only write from my own personal perspective as just one ordinary user of NetBSD. CMH The NetBSD Project has stagnated to the point of irrelevance. Relevance to whom? It's relevant to me because I use it every day. CMH As one of the 4 originators of NetBSD, I am in a fairly unique position. I am the only one who has continuously participated and/or watched the project over its entire history. Sincere thanks for the contributions you have made to my favorite operating system. CMH Power management is very primitive. Etc. I'm not sure what this means. All I can say is that it works for me: suspend and resume work on my laptop. I know that work is being done on PowerNow! for AMD K6-2+, Athlon etc. I don't presently use Intel chips, so I don't know about SpeedStep. Hopefully someone who knows will clarify this point. You make several references to a flash-friendly file system, which I assume means one that somehow spreads out data to avoid wearing the carpet too thin. NetBSD works well with my flash cards and JumpDrive, but I would not want to use either for something heavy like swap because the nature of the technology (its finite number of write/erase cycles) does not suit that. That's not NetBSD's fault and does not pose a problem for me in any case. CMH terrible support for kernel modules; I understand that other operating systems have loadable kernel modules. Perhaps NetBSD has them too. I don't know because I have never needed one. If I need a special device driver, I compile a new custom kernel. It's quick, easy (once you know how) and in my experience both painless and beneficial. NetBSD works very well for my modest server-side needs: it's fast, light, absolutely rock solid, consistent and does not make assumptions about the work that I need to do or the software that I will choose to install. As a desktop operating system it's not quite there yet (depending on the application). I understand that support for hardware accelleration of things like MPEG decode and 3D graphics are not yet working. I will be happy if someone corrects me on this point. One very underestimated assett of NetBSD is its user and developer community. The mailing lists and #netbsd on the freenode.net IRC network have provided me with far superior support than I have received from any proprietary software vendor and also better than other open-source products that I use. I have found the people there friendly, patient and very, very helpful. This is just my inital reaction to your post, which I fealt like sharing. - Andy Ball
Re: The future of NetBSD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Charles, Charles M. Hannum wrote: popularity in 1993 and 1994) have suffered similar problems. FreeBSD and XFree86, for example, have both forked successor projects (Dragonfly and X.org) for very similar reasons. I don't agree that Dragonfly is a successor of FreeBSD. Not yet. Dragonfly is nowhere near the state of FreeBSD 6.x Will it get there? Time will tell... Were TNF comprised of a good set of leaders, this situation might be somewhat acceptable -- though certainly not ideal. The problem is, there are really no leaders at this point. Goals for releases are not based on customer feedback or looking forward to future needs, but solely on the basis of what looks like it's bubbled up enough that it might be possible to finish in time. There is no high-level direction; if you ask what about the problems with threads or will there be a flash-friendly file system, the best you'll get is we'd love to have both -- but no work is done to recruit people to code these things, or encourage existing developers to work on them. This would be the very same with Linux, if there would be the same amount of developers as in NetBSD. I promise that. I do know this attidute from reading FreeBSD mailing lists. However, this is pretty natural for OSS projects. If you don't have a guy/girl who's doing the job, the wishlist gets long and the manpower gets short. It is like that... and it's hard to change. Myself, I would like to have an easy to setup fully automated, serial console controlled, installation system of FreeBSD and OpenBSD. This doesn't exists. So it's in the end up to me to make up my mind, if nobody else does. This vacuum has contributed materially to the project's current stagnation. Indeed, NetBSD is very far behind on a plethora of very important projects. Threading doesn't really work across multiple CPUs -- and is even somewhat buggy on one CPU. There is no good flash file It is like that in Linux too, more or less. So don't worry ;-) For these reasons and others, the project has fallen almost to the point of irrelevance. (Some people will probably argue that it's beyond that point, but I'm trying to be generous.) This is unfortunate, especially since NetBSD usage -- especially in the embedded space -- was growing at a good rate in 2000 and 2001, prior to the aforementioned coup. Avocent's KVM over IP boards are based on NetBSD for instance :) 5) There are a number of aspects of the NetBSD architecture that are flat out broken, and need serious rehabilitation. Again, the leadership needs to recruit people to do these things. Some of them include: * serious problems with the threading architecture (including the user-kernel interface), as mentioned earlier; * terrible support for kernel modules; * the horrible mess that is 32/64-bit compatibility, resulting in 32-bit apps often not working right on 64-bit kernels; and * unbounded maintenance work due to inappropriate and rampant use of quirk tables and chip-specific tables; e.g. in SCSI, ATAPI, IDE, ACPI and SpeedStep support. (I actually did much of this work for SCSI, but am not currently able to commit it.) You really don't want to compare these facts against Linux. I promise you, despite how popular Linux is, they have the very same problems, and IMHO it's even worse. Much worse. The only luck the Linux project has, is a whole lot of more developers than any of the BSD's projects have. Does this produce better code? No! Does this produce more features? Yes. Does this produce a faster OS? Probably Yes. But under the hood, Linux is completely screwed. Ever tried to set up bonding (aka trunk(4)) ? You don't want to! It works, okay, but it's a rocky road... [I'm CCing this to FreeBSD and OpenBSD lists in order to share it with the wider *BSD community, not to start a flame war. I hope that people reading it have the tact to be respectful of their peers, and consider how some of these issues may apply to them as well.] I hope people did. Although I doubt that much read that far. You said true words, and false, and sometimes it looked like a flame war. But all in all, it was very sad to read. Go back to your work, and start changing things. Don't stop.. Keep on! best regards, Marian, FreeBSD and OpenBSD user/advocate (but payed at work to use Debian GNU/Linux...) iD8DBQFE9jJPgAq87Uq5FMsRAlSrAJ9ZTsNd8bh/szNUFooKe7EHugvDEQCgjs5w c3g8J3xKio5/zRnKkE1bjdA= =0PPc -END PGP SIGNATURE-
Re: The future of NetBSD
On Thursday 31 August 2006 07:27, Charles M. Hannum wrote: At this point most readers are probably wondering whether I'm just writing a eulogy for the NetBSD project. At this point i was wondering why I was reading this on [EMAIL PROTECTED] --- Lars Hansson
Re: The future of NetBSD
On Wed, 30 Aug 2006 20:31:49 -0400 Nick Guenther [EMAIL PROTECTED] wrote: Um. Wow. I think Theo wins. What? Are you kidding? Theo _always_ wins. =) As for Charles M. Hannum: fork! Travers Buda
Re: The future of NetBSD
On 8/30/06, Lars Hansson [EMAIL PROTECTED] wrote: On Thursday 31 August 2006 07:27, Charles M. Hannum wrote: At this point most readers are probably wondering whether I'm just writing a eulogy for the NetBSD project. At this point i was wondering why I was reading this on [EMAIL PROTECTED] kids these days -- just can't seem to read to the bottom. ;)
Re: Soekris
Nick Holland wrote: The thing could still be a frustrating first OpenBSD system for someone. It's a great machine for what it is...but not as a Welcome to OpenBSD system. My overall recommendation stands. Get used to OpenBSD on familiar hardware, then get used to unusual hardware with an OS you are familiar with (preferably, OpenBSD. :) I'd also say you are right in that assessment, with the possible exception - if the original poster is using a hard drive with a Soekris then the only functional difference between it and a desktop computer will be the lack of a video card in the Soekris. As stated before, an older used system will cost next to nothing, which will more than offset the additional costs incurred due to higher power requirements. Unless you NEED the Soekris it is just an overly expensive toy. Breeno
Firefox port
Am I overlooking something? I can't seem to find a firefox port in the ports tree. -- Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: Firefox port
try mozilla-firefox instead then. On Wed, Aug 30, 2006 at 11:47:21PM -0400, stan wrote: Am I overlooking something? I can't seem to find a firefox port in the ports tree. -- Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie)
Re: Firefox port
On 8/30/06, stan [EMAIL PROTECTED] wrote: Am I overlooking something? I can't seem to find a firefox port in the ports tree. -- Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie) You might want to learn how to search the tree. And btw.. it's listed under mozilla-firefox of course in www -- Messages can't be intercepted if they aren't sent Curtis Gallant
Re: Firefox port
On Wed, 30 Aug 2006, stan wrote: Am I overlooking something? I can't seem to find a firefox port in the ports tree. [EMAIL PROTECTED]:/usr/ports$ make search name=firefox Port: mozilla-firefox-1.5.0.1 Path: www/mozilla-firefox Please check the mailing list archives and the documentation on openbsd.org next time. -- Antti Harri
Re: The future of NetBSD
Charles M. Hannum wrote: [I'm CCing this to FreeBSD and OpenBSD lists in order to share it with the wider *BSD community, not to start a flame war. I hope that people reading it have the tact to be respectful of their peers, and consider how some of these issues may apply to them as well.] This is completely irrelevant to OpenBSD, except in that it seems to vindicate Theo de Raadt for the crap he went through when he was ousted from the NetBSD project. What possessed you to post this to an OpenBSD list? Now, thanks to the cross posting, the misc@openbsd.org list gets to endure a bunch of cross posts from NetBSD users and FreeBSD users on topics which are completely outside the scope of this list. Great. If you don't like the direction (or lack of it) that the NetBSD project is taking, and since your post indirectly talks up nearly every aspect of OpenBSD that Theo implemented to escape the problems he encountered with NetBSD, while simultaneously talking down a lot of the politics within NetBSD that Theo has complained about, maybe you need to take your reasoning one step further and follow Theo's lead - fork NetBSD. Whining on *BSD lists is not going to get you where you want to go. You might as well pray to a god to send NetBSD a messiah. If you want a leader then be a leader. I could go on, but then I am just exacerbating the problem. This really isn't relevant to OpenBSD, and I urge other lists' users to consider whether CCing your reply back to misc@openbsd.org is relevant. Thanks in advance for your consideration. Breen Ouellette
Re: The future of NetBSD
Breen Ouellette wrote on Wed, Aug 30, 2006 at 08:22:59PM -0600: This really isn't relevant to OpenBSD, [EMAIL PROTECTED] $ head -n2 /var/run/dmesg.boot OpenBSD 3.9-stable (GENERIC) #2: Wed Aug 30 16:53:43 CEST 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC [EMAIL PROTECTED] $ cd /usr/src/sys/dev [EMAIL PROTECTED] $ cvs log cvs.log 21 [EMAIL PROTECTED] $ grep -ic 'from.*netbsd' cvs.log 2382 [EMAIL PROTECTED] $ cvs log -d \2001-09-01 cvs-new.log 21 [EMAIL PROTECTED] $ grep -ic 'from.*netbsd' cvs-new.log 1156 [EMAIL PROTECTED] $ grep -c ^revision cvs-new.log 21719 I'm not quite sure _major_ disruptions to one *BSD are irrelevant to the others. By the way, [EMAIL PROTECTED] $ grep -ic 'from.*freebsd' cvs-new.log 469 [EMAIL PROTECTED] $ grep -ic 'from.*linux' cvs-new.log 90 [EMAIL PROTECTED] $ grep -ic 'netbsd' cvs-new.log 2024 [EMAIL PROTECTED] $ grep -ic 'freebsd' cvs-new.log 784 [EMAIL PROTECTED] $ grep -ic 'linux' cvs-new.log 193 In any case, it would hardly be good news should any other free project fail, whatever may have happened in the past. Even if there is some competition among various projects, one's loss rarely is anybody else's win, when free software is concerned. Ok, i'm not a developer; so i shall go back to lurking now. -- Ingo Schwarze [EMAIL PROTECTED] Serverbetrieb usta.de / studis.de
Re: The future of NetBSD
On 8/30/06, Charles M. Hannum [EMAIL PROTECTED] wrote: The NetBSD Project has stagnated to the point of irrelevance. It has Let me start by saying I'm probably not qualified to reply to this thread, but I was never worried about making a fool out of myself before so here goes... I am a former user of FreeBSD and occasional user of OpenBSD. Haven't had much experience with either in the last year or so. So... Stagnant? Yes. Irrelevance? Possibly. But, BUT, can anyone tell me where I can get an OS that I can build easily from the same place to run on my NEC PDA as well as an old IBM PowerPC box I just happened to have sitting around and doing nothing else? And I'm typing this now on an AMD64 box that ran stably long before FreeBSD did (yes, I tested both). Nobody else can say that. Is it relevant? It's funny how much more relevant NetBSD's philosophy becomes as i386 becomes irrelevant. While the others (FreeBSD in particular) seemed to be scrambling for another architecture, NetBSD just quietly supported them without any fanfare (IA-64 excluded, but it's more irrelevant than NetBSD!). There are strengths that go right down to the core of the project. They are still there. They won't ever be irrelevant. They just need to be built upon. The cleanliness, portability, and ease of use is there. So you're probably right. A strong leader is needed to recruit people to complete new projects and generally keep things relevant. If it's a people problem, I hope someone can fix it. Too bad the guy who used to say I probably don't know what I'm talking about isn't here to comment. Andy
Re: Firefox port
Had anyone try to make mozilla? Any success. I tried without any success. Brgds, Riwan At 07:08 AM 8/31/2006 +0300, Antti Harri wrote: On Wed, 30 Aug 2006, stan wrote: Am I overlooking something? I can't seem to find a firefox port in the ports tree. [EMAIL PROTECTED]:/usr/ports$ make search name=firefox Port: mozilla-firefox-1.5.0.1 Path: www/mozilla-firefox Please check the mailing list archives and the documentation on openbsd.org next time. -- Antti Harri
