Re: [Fwd: Open-Hardware]
bofh wrote: On Jan 9, 2008 1:52 PM, Jacob Meuser [EMAIL PROTECTED] wrote: On Wed, Jan 09, 2008 at 10:07:50AM -0500, Kevin Wilcox wrote: Daniel then brought up the idea of CD sales. Something you can buy and put an exact digital replica of online. are sure about that? and what about the sticker(s) that come with the CDs? and the artwork on the insert? and the preprinted installation instructions? This is beyond silly. FSF/GNU used to sell tapes of GPLed stuff too. I'm sure it came with pre-printed instructions as well. No idea about artwork or stickers however. But splitting hairs is not useful. No, he makes a very valid point. The stickers/artwork/installation instructions are all copyrighted material and the purchaser of the CD set is not licensed to redistribute that material. So, if you are making digital replicas and selling them, that's a big no-no and not what I was talking about. My quoted statement was about the content of the CD itself. I had forgotten why I had originally made my own OpenBSD CDs - the *layout* of the master set is copyrighted as well. You can't legally rip and redistribute the purchased CD set (well, unless you're Theo or he licenses it to you in such a way that you are allowed to do so). While it doesn't affect the broader scope of my argument (you can make money selling software that is already freely available), it does affect that particular statement. kmw
Re: Open Source Article Spawns Interesting Ethical Question
On Thu, Jan 10, 2008 at 01:21:04PM +0100, chefren wrote: Look around, somewhat further than your relatives and friends... If it's not programmed well, it's stupid. Stupidity implies sentience... HAL, you there? -Toby. -- [100~Plax]sb16i0A2172656B63616820636420726568746F6E61207473754A[dZ1!=b]salax
Re: Intel DQ35MP
Hello I've noticed this problem on many different INTEL motherboard models. Debugging showed that under the address where acpi structures should be are actually zeros. So there is probably some memory mapping problem. regards M.K. Marcos Laufer pisze: Hello , i tried updating the BIOS to the newest one, removed one ram stick, installed latest snapshot and also tried disabling APM as you adviced me. When booting with bsd it doesn't recognize the devices just like before. Now i also tried booting with bsd.mp instead of bsd , and i get this error: OpenBSD 4.2-current (GENERIC.MP) #539: Tue Jan 8 17:20:15 MST 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC.MP RTC BIOS diagnostic error 80clock_battery cpu0: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (GenuineIntel 686-class) 2.39 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16, xTPR real mem = 1040625664 (992mb) avail mem = 998227968 (951mb) RTC BIOS diagnostic error 80clock_battery mainbus0 at root bios0 at mainbus0: at/286+ BIOS, date 12/10/07, SMBIOS rev. 2.4 @ 0xe2440 (31 entries) bios0: vendor Intel Corp. version JOQ3510J.86A.0731.2007.1210.2204 date 12/10/2007 bios0: Intel Corporation DQ35MP acpi0 at bios0: rev 0panic: malloc: allocation too large Stopped atDebugger+0x4: leave Debugger(e3ff000,0,d0916b48,2,3ff7) at Debugger+0x4 panic(d06b38ce,d0916b64,1000,d07b0a20,) at panic+0x63 malloc(f000ff5b,2,1,d0680060) at malloc+0x76 acpi_load_table(0,f000ff53,d19cce3c,de3fe000,d19c1f80) at acpi_load_table+0x19 acpi_loadtables(d19cce00,de3fd020,5,e) at acpi_loadtables+0x95 acpi_attach(d19cbf80,d19cce00,d0916d50,d19cbf80,0) at acpi_attach+0xb2 config_attach(d19cbf80,d078b980,d0916d50,d0604eb4) at config_attach+0xfd biosattach(d19cbfc0,d19cbf80,d0916e80,d19cbfc0,d02032c9) at biosattach+0x34e config_attach(d19cbfc0,d078ab70,d0916e80,d04a6504,d06d6958) at config_attach+0xfd mainbus_attach(0,d19cbfc0,0,de3f7000,d0915334) at mainbus_attach+0x3d RUN AT LEAST ... Regards, Marcos - Original Message - From: Pierre Riteau [EMAIL PROTECTED] To: Marcos Laufer [EMAIL PROTECTED] Cc: misc@openbsd.org Sent: Thursday, December 13, 2007 8:55 PM Subject: Re: Intel DQ35MP On Dec 13, 2007 9:25 PM, Marcos Laufer [EMAIL PROTECTED] wrote: Hello, I've just installed OpenBSD current on an Intel DQ35MP motherboard with a Quad processor, this is the dmesg log. Some devices are not recognized (PCI slot, ethernet, etc) boot -c to go in UKC or config -ef /bsd and use 'disable apm' to get acpi to attach. Maybe it will help. Also, you can get a newer snapshot. OpenBSD 4.2-current (GENERIC) #558: Tue Nov 20 10:36:15 MST 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC RTC BIOS diagnostic error 80clock_battery cpu0: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (GenuineIntel 686-class) 2.39 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16, xTPR real mem = 2097643520 (2000MB) avail mem = 2020409344 (1926MB) RTC BIOS diagnostic error 80clock_battery mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 07/26/07, SMBIOS rev. 2.4 @ 0xe2460 (30 entries) bios0: vendor Intel Corp. version JOQ3510J.86A.0559.2007.0726.0425 date 07/26/2007 bios0: Intel Corporation DQ35MP apm0 at bios0: Power Management spec V1.2 apm0: battery life expectancy 0% apm0: AC off, battery charge unknown, estimated 0:00 hours pcibios at bios0 function 0x1a not configured bios0: ROM list: 0xc/0xb400! 0xcb800/0x1e00! 0xcd800/0x1000 0xce800/0x1000 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 vendor Intel, unknown product 0x29b0 rev 0x02 vga1 at pci0 dev 2 function 0 vendor Intel, unknown product 0x29b2 rev 0x02: aperture at 0x9020, size 0x800 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) vendor Intel, unknown product 0x29b4 (class communications subclass miscellaneous, rev 0x02) at pci0 dev 3 function 0 not configured pciide0 at pci0 dev 3 function 2 vendor Intel, unknown product 0x29b6 rev 0x02: DMA (unsupported), channel 0 wired to native-PCI, channel 1 wired to native-PCI pciide0: using irq 9 for native-PCI interrupt pciide0: channel 0 ignored (not responding; disabled or no drives?) pciide0: channel 1 ignored (not responding; disabled or no drives?) vendor Intel, unknown product 0x29b7 (class communications subclass serial, rev 0x02) at pci0 dev 3 function 3 not configured Intel ICH9 IGP AMT rev 0x02 at pci0 dev 25 function 0 not configured uhci0 at pci0 dev 26 function 0 Intel 82801I USB rev 0x02: irq 9 uhci1 at pci0 dev 26 function 1 Intel 82801I USB rev
Way OT:Re: Open Source Article Spawns Interesting Ethical Question
On Wed, 9 Jan 2008 19:41:44 -0500, bofh [EMAIL PROTECTED] said: On Jan 8, 2008 2:27 PM, Eric Furman [EMAIL PROTECTED] wrote: On Sun, 06 Jan 2008 23:18:15 -0500, Richard Stallman [EMAIL PROTECTED] said: Yes, that is my view of things. Using the phone could be convenient for me. (I think it would be convenient for me.) But it also perpetuates serious problems (totalitarian surveillance, as well as proprietary software). These problems continue because people tolerate them. To solve them, we have to stop tolerating them. Bwa ha ha ha. I love these replies. they just show what a freaking nutjob idiot you are. Now pleease, STFU and go away. Just curious if you know how Kevin Mitnick was tracked down and captured? And your point is? That if I'm *breaking* *the* *law* I should worry about police forces lawfully acquiring court orders to tap and trace my phone so as to gather evidence against me? Please take your paranoid delusional nonsense to La La Land where you and rms can live happily ever after.
Re: [Fwd: Open-Hardware]
On Thu, 10 Jan 2008 10:34:46 -0500, Kevin Wilcox [EMAIL PROTECTED] said: bofh wrote: On Jan 9, 2008 1:52 PM, Jacob Meuser [EMAIL PROTECTED] wrote: On Wed, Jan 09, 2008 at 10:07:50AM -0500, Kevin Wilcox wrote: Daniel then brought up the idea of CD sales. Something you can buy and put an exact digital replica of online. are sure about that? and what about the sticker(s) that come with the CDs? and the artwork on the insert? and the preprinted installation instructions? This is beyond silly. FSF/GNU used to sell tapes of GPLed stuff too. I'm sure it came with pre-printed instructions as well. No idea about artwork or stickers however. But splitting hairs is not useful. No, he makes a very valid point. The stickers/artwork/installation instructions are all copyrighted material and the purchaser of the CD set is not licensed to redistribute that material. So, if you are making digital replicas and selling them, that's a big no-no and not what I was talking about. My quoted statement was about the content of the CD itself. I had forgotten why I had originally made my own OpenBSD CDs - the *layout* of the master set is copyrighted as well. You can't legally rip and redistribute the purchased CD set (well, unless you're Theo or he licenses it to you in such a way that you are allowed to do so). While it doesn't affect the broader scope of my argument (you can make money selling software that is already freely available), it does affect that particular statement. While it doesn't affect the broader scope of my argument (you can make money selling software that is already freely available), it does affect that particular statement. OK, I will explain it to you because I am tired of you *not* *getting* *it*. The software is simultaneously available as a CD (actually DVD) set you can purchase and as a free download. There are so few people that need to buy the CD's that it is irrelevant to this point. OpenBSD is not making money from selling software. When you buy the CD's you are knowingly doing so to help support the project. You don't *have* to buy them. You can get the software for free. When you buy the CD's you are really buying an idea. This is totally different than the concept given in the GPL link that was given earlier in this thread about allowing you to sell your software that is GPL'ed. Apples and Oranges.
Re: facts about OpenBSD
Nikns Siankin wrote: I see people keep repeating nonsense like this instead of talking about topic. At least he can read. And think.
Building Finch (Pidgin), ncurses issue.
I'm attempting to build Finch (interactive textual front-end to libpurple) from the Pidgin 2.3.1 source tarball using this command: MSGFMT=`which msgfmt` ./configure --disable-gtkui --disable-gstreamer --disable-perl --prefix=$HOME/local/ --enable-gnutls=yes --enable-consoleui -with-x=no -with-gnutls-includes=/usr/local/include/ -with-gnutls-libs=/usr/local/lib/ --with-ncurses-headers=/usr/include/ The configure script goes fine up until about here: checking for X... disabled checking for initscr in -lncursesw... no checking for update_panels in -lpanelw... no checking for initscr in -lncurses... yes checking for update_panels in -lpanel... no configure: error: Finch will not be built. You need to install ncursesw (or ncurses) and its development headers. bash-3.2$ ls /usr/include/ncurses.h /usr/include/ncurses.h I see there's an ncurses header on the base system. I've looked through the package list. The three ncurses packages I find are PHP or Ruby packages. Is what I'm trying to do here not supported by the base system nor packages?
Re: [Fwd: Open-Hardware]
On Thu, 10 Jan 2008 07:20:58 -0500, Richard Stallman [EMAIL PROTECTED] said: If you want to see what we really say about this, visit that URL and read the whole three paragraphs. You mean what you say about it this week. The text in http://www.gnu.org/philosophy/words-to-avoid.html#Market has been there for years. The GNU philosophy and policies I've stated here were established years ago. So it looks like you've made a false accusation based on pure guesswork. OK, maybe I exaggerated a little. For that I'll apologize. I accidentally said something which appeared to criticize OpenBSD falsely. When I understood the confusion, I apologized and corrected it. How about making an effort to avoid such errors? This, however is a completely false statement. You didn't accidentally say anything and by your standards it did criticize OpenBSD. There was no appearance about it. Also, you have yet to apologize. All you've done is twist words just like you've done above. You have corrected nothing. All you've done is twist words. If you've apologized privatively to Theo that's great, but you have also insulted the entire OBSD community and I believe we all should see it. Thanks for your attention.
Re: facts about OpenBSD
In article [EMAIL PROTECTED], Nikns Siankin wrote: # Stable release cycle. If you want to run latest bugfree ClamAV or FireFox - upgrade to CURRENT! But don't forget to buy release CD's!!! Well, by buying the release CD you get a fairly secure method of getting the majority of the bits. (Most snail-mails take security at least a little bit serious). # Secure By Default. OpenBSD uses broken WEP for securing WiFi networks. Has no WPA/WPA2 support. Do you have a need for WPA/WPA2 support? Please feel free to submit patches to implement this functionality. I'm sure that a nuymber of people will be pleased. # Do not let serious problems sit unsolved. OpenBSD doesn't need MAC because it has their own security flawed systrace. MAC? As in mandatory access control? Sure we have it. Any unix out there has it. It's called a uid and a list of gid's. Now, if that does not fit your needs, you have options. # Use of Cryptography. OpenBSD uses file-backed encryption (svnd) which is very suited for Full-disk-encryption. NOT. Again, feel free to submit patches. # Full Disclosure. OpenBSD at first denies remote exploitable flaws. DoS flaws gets marked as reliability not security issues. If your network/systems are setup in such a way that a DoS causes a security issue, the insecure portion is your system, not the machine that happens to tank. # Easy maintainable. OpenBSD distributes source patches to make your farm of Pentium2 firewalls updated easly. I've never had a problem. If you do, feel free to build an infrastructure that you (and others?) can use that is better. # Secure Distribution. The most secure operation system gets distributed on FTP servers as unsigned binaries. Nah, we sell you real CD's. The FTP servers are there for the convenience of people much less annoying than you. :) Disclaimer: Like it or not. I'm OpenBSD user for 4 years. Shit on my head - shit on all OpenBSD supporters. Huh? I'd prefer a toilet, but if you're really in the mood, I'm sure there is a place on the internet looking for someone with your particular type of phantasy... *shrug* to each his own I guess. -Toby. PS: Nah, I won't bother CC'ing you. -- [100~Plax]sb16i0A2172656B63616820636420726568746F6E61207473754A[dZ1!=b]salax
Re: facts about OpenBSD
On Thu, 10 Jan 2008 12:33:57 -0600 Tony Abernethy [EMAIL PROTECTED] wrote: Nikns Siankin wrote: I see people keep repeating nonsense like this instead of talking about topic. At least he can read. And think. Leave the troll alone, he wants someone to play with, and he got that.
Error on make obj with read-only /usr/src
# make obj === lib === lib/csu === lib/csu/alpha /usr/src/lib/csu/alpha/obj - /usr/obj/lib/csu/alpha === lib/csu/arm /usr/src/lib/csu/arm/obj - /usr/obj/lib/csu/arm === lib/csu/hppa /usr/src/lib/csu/hppa/obj - /usr/obj/lib/csu/hppa === lib/csu/i386 /usr/src/lib/csu/i386/obj - /usr/obj/lib/csu/i386 === lib/csu/m68k /usr/src/lib/csu/m68k/obj - /usr/obj/lib/csu/m68k === lib/csu/m88k /usr/src/lib/csu/m88k/obj - /usr/obj/lib/csu/m88k === lib/csu/powerpc /usr/src/lib/csu/powerpc/obj - /usr/obj/lib/csu/powerpc === lib/csu/sh /usr/src/lib/csu/sh/obj - /usr/obj/lib/csu/sh ln: obj: Read-only file system *** Error code 1 Stop in /usr/src/lib/csu/sh (line 64 of /usr/share/mk/bsd.obj.mk). *** Error code 1 Stop in /usr/src/lib/csu. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. This happens both on CURRENT and 4.2. -- chs
Re: Intel DQ35MP
Hi! I had same problem with DQ965GF, DSDT was overwritten by msgbuf. As a quick hack I changed msgbuf size and it solved my problem. I haven't had time to debug it further. Index: sys/arch/i386/include/param.h === RCS file: /OpenBSD/src/sys/arch/i386/include/param.h,v retrieving revision 1.42 diff -u -3 -p -r1.42 param.h --- sys/arch/i386/include/param.h 1 Oct 2007 12:10:55 - 1.42 +++ sys/arch/i386/include/param.h 10 Jan 2008 19:13:18 - @@ -97,7 +97,7 @@ #defineUSPACE_ALIGN(0) /* u-area alignment 0-none */ #ifndef MSGBUFSIZE -#define MSGBUFSIZE 4*NBPG /* default message buffer size */ +#define MSGBUFSIZE 2*NBPG /* default message buffer size */ #endif -- rix http://www.ripe.net/perl/[EMAIL PROTECTED]
kernel_map out of virtual space panic on different hardware within hours of difference
Hi misc, I'm having frequent crashes on OpenBSD 4.2 (stable) on different machines with the following error: panic: pmap_pinit: kernel_map out of virtual space! Specifically, we have two carped firewalls (running pfsync) that showed the same error with a difference of around 8 hours. First the backup crashed, and then master. I could run boot dump on the first one that crashed (the backup box), and then recover the core files with savecore (bsd.0 and bsd.0.core). But now, when trying to run the gdb commands, I get to a point where it tells me this when typing target kvm bsd.0.core and hitting enter: myhost:/var/crash# gdb GNU gdb 6.3 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-unknown-openbsd4.2. (gdb) file bsd.0 Reading symbols from /u/data/crash/bsd.0...(no debugging symbols found)...done. (gdb) target kvm bsd.0.core Cannot access memory at address 0xffbe6afc (gdb) Why could this be? I'm kind of stuck at this point. I could run vmstat and ps commands with the -N and -M options, but I don't think I'm getting something very useful. I did see this with vmstat -m though: Memory statistics by bucket size Size In Use Free Requests HighWater Couldfree 16 3918 1714 2283171301280 71 32 321447 17128808 640 0 64 1222 1018 13797629 320 295030 128 405 434699894 160 0 256 229 59 14697840 80 71663 512 447 252447129 40 5629 1024 1274 30 941406 20 419326 2048 17 172263518 101768442 4096 21 61920222 5 0 8192 12 0 12 5 0 163842 0 4615 5 0 327684 0 8 5 0 Memory usage type by bucket size Size Type(s) 16 devbuf, pcb, routetbl, ifaddr, sysctl, vnodes, UFS mount, dirhash, in_multi, exec, xform_data, VM swap, UVM amap, UVM aobj, USB, USB device, temp 32 devbuf, pcb, routetbl, ifaddr, sem, dirhash, proc, VFS cluster, in_multi, ether_multi, exec, pfkey data, xform_data, VM swap, UVM amap, USB, crypto data, temp 64 devbuf, pcb, routetbl, ifaddr, vnodes, sem, dirhash, in_multi, pfkey data, UVM amap, USB, NDP, temp 128 devbuf, routetbl, ifaddr, iov, vnodes, ttys, exec, pfkey data, tdb, UVM amap, USB, USB device, crypto data, NDP, temp 256 devbuf, routetbl, ifaddr, sysctl, ioctlops, vnodes, shm, VM map, file desc, proc, NFS srvsock, NFS daemon, pfkey data, newblk, UVM amap, USB, USB device, temp 512 devbuf, pcb, ifaddr, ioctlops, mount, UFS mount, shm, dirhash, file desc, ttys, exec, UVM amap, USB device, temp 1024 devbuf, ioctlops, namecache, file desc, proc, ttys, exec, tdb, UVM amap, UVM aobj, crypto data, temp 2048 devbuf, ifaddr, ioctlops, UFS mount, pagedep, VM swap, UVM amap, temp 4096 devbuf, ioctlops, UFS mount, MSDOSFS mount, UVM amap, memdesc, temp 8192 devbuf, NFS node, namecache, UFS quota, UFS mount, ISOFS mount, inodedep, crypto data 16384 devbuf, UFS mount, VM swap, temp 32768 devbuf, namecache, VM swap, UVM amap Memory statistics by type Type Kern Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) devbuf 2397 1445K 1445K 39322K 24580 0 16,32,64,128,256,512,1024,2048,4096,8192,16384,32768 pcb95 8K 9K 39322K 4691280 0 16,32,64,512 routetbl 22020K 28K 39322K 16195540 0 16,32,64,128,256 ifaddr 11822K 22K 39322K 1200 0 16,32,64,128,256,512,2048 sysctl 2 1K 1K 39322K20 0 16,256 ioctlops 0 0K 4K 39322K 100884360 0 256,512,1024,2048,4096 iov 0 0K 1K 39322K 180 0 128 mount 4 2K 4K 39322K 1200 0 512 NFS node 1 8K 8K 39322K10 0 8192 vnodes41 7K 80K 39322K 3502240 0 16,64,128,256 namecache 341K 41K 39322K30 0 1024,8192,32768 UFS quota 1 8K 8K 39322K10 0 8192 UFS mount1733K 68K 39322K 4810 0 16,512,2048,4096,8192,16384 shm 2 1K 1K 39322K20 0 256,512 VM map 4
Re: facts about OpenBSD
In article [EMAIL PROTECTED], Nikns Siankin wrote: I don't believe anymore, that someone from side can make it better. The only people who could make it better are talking to community only when release CD needs to get sold or donations are needed. So you think that the community at large can have an effect on the actual code that gets written? Possibly. You think that the best way to do this is to shit on OpenBSD and somehow reduce the number of CD's sold? To reduce the minimal amount of funding that any of the developers could have? And to top it off, to piss them off and make coding a chore as opposed to a fun thing? While I certainly don't code as much as all the other OpenBSD developers, I can say that removing my enjoyment of spending any of my scarce time coding will be spent coding on things I enjoy first, and patches for people I enjoy working with second. People like you don't even come on the horizon. If you believe that these things need to be done, and can not be done from inside, by all means, the code is all there. Feel free to start producing this much needed code. -Toby. -- [100~Plax]sb16i0A2172656B63616820636420726568746F6E61207473754A[dZ1!=b]salax
Re: Building Finch (Pidgin), ncurses issue.
On 1/10/08, Jon [EMAIL PROTECTED] wrote: checking for X... disabled checking for initscr in -lncursesw... no checking for update_panels in -lpanelw... no checking for initscr in -lncurses... yes checking for update_panels in -lpanel... no configure: error: Finch will not be built. You need to install ncursesw (or ncurses) and its development headers. bash-3.2$ ls /usr/include/ncurses.h /usr/include/ncurses.h I see there's an ncurses header on the base system. I've looked through the package list. The three ncurses packages I find are PHP or Ruby packages. Is what I'm trying to do here not supported by the base system nor packages? libpanel isn't installed. i'm not sure if the source is included in base with curses or not, otherwise you can install curses from source and it should install panel.
SUM TOTAL OF RMS's PHILOSOPHY
On Jan 7, 2008 9:48 AM, Richard Stallman [EMAIL PROTECTED] wrote: I don't carry a mobile phone, but I don't see anything wrong in borrowing one from someone to make a call. So if it is a new model of cell phone and if the owner teaches you how to use it and make life easy for you will that be 1) Wrong on his part to encourage you to using a device you don't use? 2) Wrong on your part to take his advice and help to use it? Yes, that is my view of things. Using the phone could be convenient for me. But some where ( just like you use take help from the mobile phone owner to use it ) in the ports system are instructions to install a non-free software which is not mandatory for users to use. The cases are similar, and my view on the two cases is similar. I hope the first time you used a cell phone some body must have taught you right? or you must have read the manual? So this is something like I AM A THIEF! BUT BOY I DONT RECOMMEND STEALING!! BUT WAIT BEFORE YOU ARE SURPRISED!!! I WONT SPARE SLANDER THEM THAT USE THEIR OWN THINGS EITHER!!! EXCEPT OF COURSE IF IT IS FOR MY CONVENIENCE FOR A TIME!
ALTQ : HTB packet scheduler
Hello, Does anybody knows if an HTB packet scheduler is available on OpenBSD ? Regards,
Re: OpenBSD supported servers ?
On 12/20/07, Selva Raj [EMAIL PROTECTED] wrote: Dear Raimo, Here is the brief about the proposed setup. This would be a test bed for Information Assurance business. To summarise the lab will have Firewalls /OpenBSD 4.2 / PF VPN / OpenBSD 4.2 / Openvpn SSH / OpenBSD 4.2 / Openssh Mail Servers / OpenBSD 4.2 / Postfix, MySql, Courier-IMAPm Amavisd-new, SpamAssasin, DNS / OpenBSD 4.2 / PF, CARPm FTP, BIND WEB / OpenBSD 4.2 / TOMCAT SAMBA / Red Hat Linux (RAID 5) Except SAMPA the is no RAID configuration needed. Thanks, //Selva On Dec 20, 2007 5:04 PM, Raimo Niskanen [EMAIL PROTECTED] wrote: Any clue how large a server and what features (hw RAID, etc) you need? On Thu, Dec 20, 2007 at 04:37:34PM +0530, Selva Raj wrote: Hi all, I am looking for a HP or IBM server which can run OpenBSD Operating System out of the box? Any suggestions will be great useful to me. Regards, //Selva -- / Raimo Niskanen, Erlang/OTP, Ericsson AB -- /Selva Selva, I'm not sure how everyone feels about Foxconn hardware, but I've used one of their motherboards (661MX PRO) to deploy an OpenBSD webserver for a small business. Its been running smoothly for about a year now. No complaints. Originally purchased new through cybertronpc.com. Might be worth a look. Be glad to send you a dmesg if it helps. r/s, Luis
ssh controlling question
Hi All Just a little question on something I'm working on I have say 50 accounts on a box. 40 of which I want the users to connect from ANY IP address 10 of which I want the users to only be allowed to connect from a specific IP address that is assigned to them. Is there a feature to control SSH account from a specific ip address Thanks James
64 bit file I/O?
Does OpenBSD's base utilities support 64 bit I/O? I attempted to create a 8GB file using the dd application distributed with OpenBSD 4.2, unfortunately it fails with: dd: count: Result too large Confused, I tried making the size smaller, and noticed it bails out at exactly 4294967295 bytes, 4294967294 succeeds however.. dd: count: Undefined error: 0 What are my options? -Nix Fan.
Re: ssh controlling question
James Mackinnon wrote: Hi All Just a little question on something I'm working on I have say 50 accounts on a box. 40 of which I want the users to connect from ANY IP address 10 of which I want the users to only be allowed to connect from a specific IP address that is assigned to them. Is there a feature to control SSH account from a specific ip address In sshd_config: == AllowUsers [EMAIL PROTECTED] == kmw
Re: ssh controlling question
Check the sshd_config(5) man page for the section on Match conditional blocks. On Thu, Jan 10, 2008 at 04:53:45PM -0400, James Mackinnon wrote: Hi All Just a little question on something I'm working on I have say 50 accounts on a box. 40 of which I want the users to connect from ANY IP address 10 of which I want the users to only be allowed to connect from a specific IP address that is assigned to them. Is there a feature to control SSH account from a specific ip address Thanks James -- Darrin Chandler| Phoenix BSD User Group | MetaBUG [EMAIL PROTECTED] | http://phxbug.org/ | http://metabug.org/ http://www.stilyagin.com/ | Daemons in the Desert | Global BUG Federation
Re: 64 bit file I/O?
On 2008/01/10 14:17, Unix Fan wrote: Does OpenBSD's base utilities support 64 bit I/O? I attempted to create a 8GB file using the dd application distributed with OpenBSD 4.2, unfortunately it fails with: dd: count: Result too large Confused, I tried making the size smaller, and noticed it bails out at exactly 4294967295 bytes, 4294967294 succeeds however.. dd: count: Undefined error: 0 What are my options? Use a larger bs= so you can use a smaller count=. The limit you are bumping into is in the maximum size of arguments to dd.
Re: 64 bit file I/O?
On 10 Jan 2008 14:17:43 -0800, Unix Fan [EMAIL PROTECTED] wrote: Does OpenBSD's base utilities support 64 bit I/O? I attempted to create a 8GB file using the dd application distributed with OpenBSD 4.2, unfortunately it fails with: dd: count: Result too large Confused, I tried making the size smaller, and noticed it bails out at exactly 4294967295 bytes, 4294967294 succeeds however.. what bs are you using?
Re: 64 bit file I/O?
On Thu, 10 Jan 2008, Unix Fan wrote: Does OpenBSD's base utilities support 64 bit I/O? I attempted to create a 8GB file using the dd application distributed with OpenBSD 4.2, unfortunately it fails with: dd: count: Result too large Confused, I tried making the size smaller, and noticed it bails out at exactly 4294967295 bytes, 4294967294 succeeds however.. dd: count: Undefined error: 0 What are my options? Since you didnt show us your arguments to the command I have to guess. The following command created a file called 8g: $ dd if=/dev/zero of=8g bs=1048576 count=8192 8192+0 records in 8192+0 records out 8589934592 bytes transferred in 148.378 secs (57891904 bytes/sec) -moj -Nix Fan.
Re: Building Finch (Pidgin), ncurses issue.
Ted Unangst wrote: On 1/10/08, Jon [EMAIL PROTECTED] wrote: checking for X... disabled checking for initscr in -lncursesw... no checking for update_panels in -lpanelw... no checking for initscr in -lncurses... yes checking for update_panels in -lpanel... no configure: error: Finch will not be built. You need to install ncursesw (or ncurses) and its development headers. bash-3.2$ ls /usr/include/ncurses.h /usr/include/ncurses.h I see there's an ncurses header on the base system. I've looked through the package list. The three ncurses packages I find are PHP or Ruby packages. Is what I'm trying to do here not supported by the base system nor packages? libpanel isn't installed. i'm not sure if the source is included in base with curses or not, otherwise you can install curses from source and it should install panel. bash-3.2$ ls /usr/include/panel.h /usr/include/panel.h bash-3.2$ ls /usr/lib/libpanel* /usr/lib/libpanel.a /usr/lib/libpanel.so.3.0 /usr/lib/libpanel_p.a /usr/lib/libpanel_pic.a bash-3.2$ Turns out libpanel is installed, just the configure script won't recognize it. update_panels is referred to in panel.h too. Yet another frustrating Pidgin configure script bug. argh Thanks for helping with the first half of the solution misc.
Re: 64 bit file I/O?
On Thu, Jan 10, 2008 at 02:17:43PM -0800, Unix Fan wrote: Does OpenBSD's base utilities support 64 bit I/O? I attempted to create a 8GB file using the dd application distributed with OpenBSD 4.2, unfortunately it fails with: dd: count: Result too large Confused, I tried making the size smaller, and noticed it bails out at exactly 4294967295 bytes, 4294967294 succeeds however.. dd: count: Undefined error: 0 What are my options? -Nix Fan. nostromo:tobiasu$ dd if=/dev/zero of=test bs=1 count=1 seek=$(bc -e '512*(2^34-1)' -e quit) ls -l test uname -a 1+0 records in 1+0 records out 1 bytes transferred in 0.000 secs (3021 bytes/sec) -rw-r--r-- 1 tobiasu tobiasu 8.0T Jan 10 23:46 test OpenBSD nostromo.tmux.lan 4.2 GENERIC#638 i386 Maybe you want to be a little more specific?
Re: SUM TOTAL OF RMS's PHILOSOPHY
Enough of this FUD. Go hang yourself please. Thanks On Jan 10, 2008 9:27 PM, Siju George [EMAIL PROTECTED] wrote: On Jan 7, 2008 9:48 AM, Richard Stallman [EMAIL PROTECTED] wrote: I don't carry a mobile phone, but I don't see anything wrong in borrowing one from someone to make a call. So if it is a new model of cell phone and if the owner teaches you how to use it and make life easy for you will that be 1) Wrong on his part to encourage you to using a device you don't use? 2) Wrong on your part to take his advice and help to use it? Yes, that is my view of things. Using the phone could be convenient for me. But some where ( just like you use take help from the mobile phone owner to use it ) in the ports system are instructions to install a non-free software which is not mandatory for users to use. The cases are similar, and my view on the two cases is similar. I hope the first time you used a cell phone some body must have taught you right? or you must have read the manual? So this is something like I AM A THIEF! BUT BOY I DONT RECOMMEND STEALING!! BUT WAIT BEFORE YOU ARE SURPRISED!!! I WONT SPARE SLANDER THEM THAT USE THEIR OWN THINGS EITHER!!! EXCEPT OF COURSE IF IT IS FOR MY CONVENIENCE FOR A TIME!
SSH Brute Force Attacks Abound - and thanks!
A practical example, real life, last night. I was replacing my hard drive on my home broadband OBSD firewall, and it was taking a few minutes to copy over the old pf.conf and enable the firewall. I had installed the latest snapshot as a fresh image and restarted. It took a little while to set up the local networks, and I was connected to the Internet, so I could download packages. I copied over the pf.conf from my backup host and enabled it, not thinking much more about it. Then this morning I looked at /var/log/authlog to see stuff like this: Jan 9 18:00:01 home-fw newsyslog[6065]: logfile turned over Jan 9 18:03:03 home-fw sshd[29544]: Invalid user andrew from 125.16.26.123 Jan 9 18:03:03 home-fw sshd[240]: input_userauth_request: invalid user andrew Jan 9 18:03:03 home-fw sshd[29544]: Failed password for invalid user andrew from 125.16.26.123 port 52447 ssh2 Jan 9 18:03:03 home-fw sshd[240]: Received disconnect from 125.16.26.123: 11: Bye Bye Jan 9 18:03:06 home-fw sshd[19514]: Invalid user adam from 125.16.26.123 Jan 9 18:03:06 home-fw sshd[15864]: input_userauth_request: invalid user adam Jan 9 18:03:06 home-fw sshd[19514]: Failed password for invalid user adam from 125.16.26.123 port 52651 ssh2 Jan 9 18:03:06 home-fw sshd[15864]: Received disconnect from 125.16.26.123: 11: Bye Bye Jan 9 18:03:08 home-fw sshd[18110]: Invalid user trial from 125.16.26.123 Jan 9 18:03:08 home-fw sshd[22493]: input_userauth_request: invalid user trial Jan 9 18:03:09 home-fw sshd[18110]: Failed password for invalid user trial from 125.16.26.123 port 52821 ssh2 Jan 9 18:03:09 home-fw sshd[22493]: Received disconnect from 125.16.26.123: 11: Bye Bye Jan 9 18:03:11 home-fw sshd[20596]: Invalid user calendar from 125.16.26.123 Jan 9 18:03:11 home-fw sshd[8582]: input_userauth_request: invalid user calendar Jan 9 18:03:11 home-fw sshd[20596]: Failed password for invalid user calendar from 125.16.26.123 port 53011 ssh2 Jan 9 18:03:12 home-fw sshd[8582]: Received disconnect from 125.16.26.123: 11: Bye Bye Jan 9 18:03:14 home-fw sshd[22151]: Invalid user poq from 125.16.26.123 Jan 9 18:03:14 home-fw sshd[17137]: input_userauth_request: invalid user poq Jan 9 18:03:14 home-fw sshd[22151]: Failed password for invalid user poq from 125.16.26.123 port 53199 ssh2 I never see anything like that, since my pf rules only allow me to ssh back to home from my work IP range. In the space of about 15 minutes before I enabled pf all of the following users were tried, probably by an automated script: AaliyahAaron Aba Abel Exit Jewel Zmeu Zmeu adam adam add adm admin admin admin admin admin admin admin adminsadminsadrian alan alex alin alina alinusamanda andreiandrew angel apachearon at backupbnc bran brett cafe calendar cap cgi ch cmd com danny data david dulap fernando fluffyftpgames george getguest guest hacker haxor hk http httpd hyid ident if info info internet ircisit john kathi kaytenldap library linux lp luis mail mail mailman master maxmichael michael michi mikaelmike mike mysql mysql netnetwork news news nick octavio open oper oracle orgparty paul paul pepgsql pgsql plplay poqpostfix postmaster print psybncradu resin rex richard richardrobertrpm sales samba sara search sef sex sgisharonshell shell shop squid sshstan station stef stephen stevensunny sunsunsusan suva suzukitavi technicom telnettest test test test test trial trib uk unix unseenus user user username username users webwebadmin webmaster webmaster webpopword www-data wwwrunwwwrun yahoo za What a cesspool the internet is! Good passwords, limit access to where it is necessary, and run an ironclad OS. Thanks for making it all possible.
Re: 64 bit file I/O?
On Thu, Jan 10, 2008 at 02:36:15PM -0800, Ted Unangst wrote: On 10 Jan 2008 14:17:43 -0800, Unix Fan [EMAIL PROTECTED] wrote: Does OpenBSD's base utilities support 64 bit I/O? I attempted to create a 8GB file using the dd application distributed with OpenBSD 4.2, unfortunately it fails with: dd: count: Result too large Confused, I tried making the size smaller, and noticed it bails out at exactly 4294967295 bytes, 4294967294 succeeds however.. what bs are you using? Try to be more polite, please. -- Darrin Chandler| Phoenix BSD User Group | MetaBUG [EMAIL PROTECTED] | http://phxbug.org/ | http://metabug.org/ http://www.stilyagin.com/ | Daemons in the Desert | Global BUG Federation
Re: Intel DQ35MP
In gmane.os.openbsd.misc, you wrote: I had same problem with DQ965GF, DSDT was overwritten by msgbuf. As a quick hack I changed msgbuf size and it solved my problem. I haven't had time to debug it further. Index: sys/arch/i386/include/param.h === RCS file: /OpenBSD/src/sys/arch/i386/include/param.h,v retrieving revision 1.42 diff -u -3 -p -r1.42 param.h --- sys/arch/i386/include/param.h 1 Oct 2007 12:10:55 - 1.42 +++ sys/arch/i386/include/param.h 10 Jan 2008 19:13:18 - @@ -97,7 +97,7 @@ #defineUSPACE_ALIGN(0) /* u-area alignment 0-none */ #ifndef MSGBUFSIZE -#define MSGBUFSIZE 4*NBPG /* default message buffer size */ +#define MSGBUFSIZE 2*NBPG /* default message buffer size */ #endif Please send me the output of 'machine memory' at the boot prompt for this machine. I think I know what is causing this... -Toby. -- [100~Plax]sb16i0A2172656B63616820636420726568746F6E61207473754A[dZ1!=b]salax
Re: [Fwd: Open-Hardware]
On 1/10/08 6:18 PM, Eric Furman wrote: OK, I will explain it to you because I am tired of you *not* *getting* *it*. The software is simultaneously available as a CD (actually DVD) Please stop/halt/finish/end... It's a CD set, 3 CD's in a DVD box. set you can purchase and as a free download. There are so few people that need to buy the CD's that it is irrelevant to this point. Buying the CD set and OpenBSD goodies is =very relevant=. Please buy more or at least donate money. OpenBSD is not making money from selling software. When you buy the CD's you are knowingly doing so to help support the project. You don't *have* to buy them. You can get the software for free. When you buy the CD's you are really buying an idea. No you buy a case, CD's artwork, printed paper... And there is sofware as a bonus too. We more or less need the CD's since we develop sotware on a data isle and don't want any connections to the internet ever. When we buy the official release it's very difficult for an attacker to infiltrate the code on the CD set, that's a serious plus. +++chefren
Re: 64 bit file I/O?
Apologies, I was using a larger count size, which is restricted by a 32bit variable. (size_t). FreeBSD's dd is 64 bit safe for all options... might be worth looking into. Darrin Chandler wrote: Ted Unangst wrote: what bs are you using? Try to be more polite, please. He wasn't being rude, bs the block size option for the dd command... which I the slow idiot. had set to 1.. Sorry for the disruption all, won't happen again. -Nix Fan.
Re: 64 bit file I/O?
On Thu, Jan 10, 2008 at 04:49:42PM -0800, Unix Fan wrote: Darrin Chandler wrote: Ted Unangst wrote: what bs are you using? Try to be more polite, please. He wasn't being rude, bs the block size option for the dd command... which I the slow idiot. had set to 1.. Yes, I know. Apparently my deadpan delivery has the same effect online as it does in person. -- Darrin Chandler| Phoenix BSD User Group | MetaBUG [EMAIL PROTECTED] | http://phxbug.org/ | http://metabug.org/ http://www.stilyagin.com/ | Daemons in the Desert | Global BUG Federation
Re: facts about OpenBSD
On Thu, 10 Jan 2008 14:24:33 +0200 Nikns Siankin [EMAIL PROTECTED] wrote: On Thu, Jan 10, 2008 at 09:56:01PM +1100, Rod Whitworth wrote: On Thu, 10 Jan 2008 12:00:53 +0200, Nikns Siankin [EMAIL PROTECTED] wrote: [..] We have had several pointless trolls too many lately. As a result your pointless humour does not raise a laugh. Stay on-topic or fuck off like jacob does. Who *pays* you for this? I'd need to be paid, and well. Dhu Rod/ /earth: write failed, file system is full cp: /earth/creatures: No space left on device
Re: Real men don't attack straw men
2008/1/9, Paul de Weerd [EMAIL PROTECTED]: On Tue, Jan 08, 2008 at 02:06:56PM -0500, Richard Stallman wrote: | Yet, this firmware can be upgraded and OpenBSD will | automatically do this if it detects older firmware on your NIC. You | can choose another operating system that does not upgrade the firmware | and the hardware may work fine for your use case. Should the firmware | be free software ? It's inside the hardware and on your other | operating system you are not installing software on it. | | That is a borderline case. One possible resolution is that it is ok | to use this hardware, but updating the firmware is a bad thing. This can not seriously be what you really believe. The non-free firmware that comes pre-installed on the hardware is OK, but updating it yourself is not ? If you wanted to use this newer version of the firmware, you would buy another piece of the same hardware with the newer version installed ? In that case, buying a Windows computer would be Ok, as long as you don't update the version of Windows software that is on it... when you want a newer version of Windows, just get a new computer. That's what the average consumer does by the way, they don't 'usually install their own OS on the computer', and that they simply buy a new computer with Vista preinstalled... so much for badvista... -- Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
Re: SSH Brute Force Attacks Abound - and thanks!
Wow, I read your email and checked my authlog and was astounded by the number hack attempts. Thankfully, I configured my OpenBSD firewall with recommended access controls. Thanks to all the dedicated OpenBSD developers and community! Support the project and encourage the purchase of more OpenBSD CD's and direct donations to the Foundation! --- Ken [EMAIL PROTECTED] wrote: A practical example, real life, last night. I was replacing my hard drive on my home broadband OBSD firewall, and it was taking a few minutes to copy over the old pf.conf and enable the firewall. I had installed the latest snapshot as a fresh image and restarted. It took a little while to set up the local networks, and I was connected to the Internet, so I could download packages. I copied over the pf.conf from my backup host and enabled it, not thinking much more about it. Then this morning I looked at /var/log/authlog to see stuff like this: Jan 9 18:00:01 home-fw newsyslog[6065]: logfile turned over Jan 9 18:03:03 home-fw sshd[29544]: Invalid user andrew from 125.16.26.123 Jan 9 18:03:03 home-fw sshd[240]: input_userauth_request: invalid user andrew Jan 9 18:03:03 home-fw sshd[29544]: Failed password for invalid user andrew from 125.16.26.123 port 52447 ssh2 Jan 9 18:03:03 home-fw sshd[240]: Received disconnect from 125.16.26.123: 11: Bye Bye Jan 9 18:03:06 home-fw sshd[19514]: Invalid user adam from 125.16.26.123 Jan 9 18:03:06 home-fw sshd[15864]: input_userauth_request: invalid user adam Jan 9 18:03:06 home-fw sshd[19514]: Failed password for invalid user adam from 125.16.26.123 port 52651 ssh2 Jan 9 18:03:06 home-fw sshd[15864]: Received disconnect from 125.16.26.123: 11: Bye Bye Jan 9 18:03:08 home-fw sshd[18110]: Invalid user trial from 125.16.26.123 Jan 9 18:03:08 home-fw sshd[22493]: input_userauth_request: invalid user trial Jan 9 18:03:09 home-fw sshd[18110]: Failed password for invalid user trial from 125.16.26.123 port 52821 ssh2 Jan 9 18:03:09 home-fw sshd[22493]: Received disconnect from 125.16.26.123: 11: Bye Bye Jan 9 18:03:11 home-fw sshd[20596]: Invalid user calendar from 125.16.26.123 Jan 9 18:03:11 home-fw sshd[8582]: input_userauth_request: invalid user calendar Jan 9 18:03:11 home-fw sshd[20596]: Failed password for invalid user calendar from 125.16.26.123 port 53011 ssh2 Jan 9 18:03:12 home-fw sshd[8582]: Received disconnect from 125.16.26.123: 11: Bye Bye Jan 9 18:03:14 home-fw sshd[22151]: Invalid user poq from 125.16.26.123 Jan 9 18:03:14 home-fw sshd[17137]: input_userauth_request: invalid user poq Jan 9 18:03:14 home-fw sshd[22151]: Failed password for invalid user poq from 125.16.26.123 port 53199 ssh2 I never see anything like that, since my pf rules only allow me to ssh back to home from my work IP range. In the space of about 15 minutes before I enabled pf all of the following users were tried, probably by an automated script: AaliyahAaron Aba Abel Exit Jewel Zmeu Zmeu adam adam add adm admin admin admin admin admin admin admin adminsadminsadrian alan alex alin alina alinusamanda andrei andrew angel apachearon at backup bnc bran brett cafe calendar cap cgi ch cmd com danny data david dulap fernando fluffyftpgames george getguest guest hacker haxor hk http httpd hyid ident if info info internet ircis it john kathi kaytenldap library linux lp luis mail mail mailman master maxmichael michael michi mikael mike mike mysql mysql netnetwork news news nick octavio open oper oracle orgparty paul paul pe pgsql pgsql plplay poqpostfix postmaster print psybncradu resin rex richard richardrobertrpm sales samba sara search sef sex sgisharon shell shell shop squid sshstan station stef stephen stevensunny sunsun susan suva suzukitavi technicom telnet test test test test test trial trib uk unix unseenus user user username username users webwebadmin webmaster webmaster webpopword www-data wwwrun wwwrun yahoo za What a cesspool the internet is! Good passwords, limit access to where it is necessary, and run an ironclad OS. Thanks for making it all possible. Never
Re: kernel_map out of virtual space panic on different hardware within hours of difference
On 11/01/2008, at 7:47 AM, Martmn Coco wrote: Hi misc, I'm having frequent crashes on OpenBSD 4.2 (stable) on different machines with the following error: panic: pmap_pinit: kernel_map out of virtual space! Specifically, we have two carped firewalls (running pfsync) that showed the same error with a difference of around 8 hours. First the backup crashed, and then master. [cut] In use 540926K, total allocated 559516K; utilization 96.7% Particularly, I saw this: Memory Totals: In UseFreeRequests 2115K225K286218211 And this: In use 540926K, total allocated 559516K; utilization 96.7% Which seems to be little to spare. I also checked that a swap device is configured like this: [cut] The other thing I can think of is something related to carp or pfsync. Any input on this will be much appreciated. Thank you, Martmn. If you are running stable, it is not likely to be this (patch 4), is it? Might be worth double-checking and eliminating the obvious. http://marc.info/?l=openbsd-miscm=119798530823904w=2
Re: strftime bug?
On Jan 10, 2008 12:41 AM, Duncan Patton a Campbell [EMAIL PROTECTED] wrote: On Wed, 9 Jan 2008 21:51:01 -0700 Philip Guenther [EMAIL PROTECTED] wrote: 1) pass the same size value to malloc() and strftime(), and Ya, this is it. Needs to be the sizeof the input buffer + 2. Why? Since the output string should have the same length as the input string, I would expect it to work correctly if you pass both malloc() and strftime() the value strlen(input)+1. Why this does not [break] in FreeBSD escapes me, tho'. It doesn't appear to break because malloc() is, by happenstance, returning a buffer whose last byte is zero. If that wasn't true, then your code would access beyond the end of a malloced buffer, which has undefined behavior and may cause a SIGSEGV. For example, try running with MALLOC_OPTIONS=J in the environment. Philip Guenther
Re: Open Source Article Spawns Interesting Ethical Question
On 1/10/08 1:09 AM, Tobias Weingartner wrote: In article [EMAIL PROTECTED], chefren wrote: On 1/8/08 11:28 PM, Marco Peereboom wrote: 2. Same NIC without flash/ROM bad Eh, that's just a meaningless pile of transistors. Surely you jest? An FPGA is a meaningless pile of transistors? Weird... Without software loaded to it? Certainly. Just stupid silicon. +++chefren
Re: OpenBSD and ISDN TA
2008/1/9, Diana Eichert [EMAIL PROTECTED]: On Wed, 9 Jan 2008, Christian Weisgerber wrote: Well, you can hook up ISDN TAs with a serial port that look like a dial-up modem (AT command set etc.). However, I think these have long since disappeared from the market. -- Christian naddy Weisgerber [EMAIL PROTECTED] I just shutdown my Zyxel external ISDN TA 6 weeks ago after using it for over 10 years. You can connect to it via serial cable at least 460Kbaud, that is if you have a serial port available that can run at greater than 115k. diana Why dont you just fix an external router like Cisco 76? / 800 or something? Cant possibly cost much these days.. I can probably fix one for free. Dunno about the shipping costs from sweden though.
Re: facts about OpenBSD
On Wed, Jan 09, 2008 at 05:07:35PM -0600, Jacob Yocom-Piatt wrote: Facts about Nikns Siankin: # Whiner. He bitches incessantly about stuff and does nothing to fix it. # Jerk. He ignores that most of the development time that goes into # Misleading. He claims the system is distributed on FTP servers and # Ignorant. OpenBSD has myriad additional security technologies in it that # Idiot. By whining in a totally counterproductive fashion he alienates Hey jacob! Sorry for hurting your feelings so badly. Anyway. With this you have earned a kiss from theo. I heard you will get your cvs access now really soon ;] --
Re: OpenBSD and ISDN TA
2008/1/9, Peter N. M. Hansteen [EMAIL PROTECTED]: straightforward to use it via ppp. Otherwise, I think ISDN is one of those technologies a significant part of the OpenBSD population would be very happy to suppress any remaining memories of. Only the non-Germans. But you north-americans have probably also never expierenced the wonders of DECT or GSM... :-) Seriously: MirBSD is a fork of OpenBSD supporting isdn. Best Martin
Re: Open Source Article Spawns Interesting Ethical Question
On Thu, Jan 10, 2008 at 10:33:41AM +0100, chefren wrote: On 1/10/08 1:09 AM, Tobias Weingartner wrote: In article [EMAIL PROTECTED], chefren wrote: On 1/8/08 11:28 PM, Marco Peereboom wrote: 2. Same NIC without flash/ROM bad Eh, that's just a meaningless pile of transistors. Surely you jest? An FPGA is a meaningless pile of transistors? Weird... Without software loaded to it? Certainly. Just stupid silicon. +++chefren It has the capability to be programmed. I would not call that stupid. -Otto
Re: facts about OpenBSD
On Thu, 10 Jan 2008 12:00:53 +0200, Nikns Siankin [EMAIL PROTECTED] wrote: On Wed, Jan 09, 2008 at 05:07:35PM -0600, Jacob Yocom-Piatt wrote: Facts about Nikns Siankin: # Whiner. He bitches incessantly about stuff and does nothing to fix it. # Jerk. He ignores that most of the development time that goes into # Misleading. He claims the system is distributed on FTP servers and # Ignorant. OpenBSD has myriad additional security technologies in it that # Idiot. By whining in a totally counterproductive fashion he alienates Hey jacob! Sorry for hurting your feelings so badly. Anyway. With this you have earned a kiss from theo. I heard you will get your cvs access now really soon ;] We have had several pointless trolls too many lately. As a result your pointless humour does not raise a laugh. plonk I don't give a shit about your feelings. replies to /dev/null. Rod/ /earth: write failed, file system is full cp: /earth/creatures: No space left on device
Re: facts about OpenBSD
On Wed, 9 Jan 2008 23:03:29 +0200 Nikns Siankin [EMAIL PROTECTED] wrote: Facts about OpenBSD: # Stable release cycle. If you want to run latest bugfree ClamAV or FireFox - upgrade to CURRENT! But don't forget to buy release CD's!!! if you do not like to use CURRENT, send a patch which backports these versions to stable. you are listed as maintainer for some ports, means you should know how things work. # Secure By Default. OpenBSD uses broken WEP for securing WiFi networks. Has no WPA/WPA2 support. wpa is not much better than wep. useful alternative: ipsec, another alternative: secure your wlan with pf/authpf. # Do not let serious problems sit unsolved. OpenBSD doesn't need MAC because it has their own security flawed systrace. i do not get the point. seriously, have you ever used systrace? # Use of Cryptography. OpenBSD uses file-backed encryption (svnd) which is very suited for Full-disk-encryption. NOT. wrong. i use it on a whole raid 1 disk for example, no problems here. $ df -h Filesystem SizeUsed Avail Capacity Mounted on [...] /dev/svnd0c411G249G141G64%/media # Full Disclosure. OpenBSD at first denies remote exploitable flaws. DoS flaws gets marked as reliability not security issues. what's the problem? # Easy maintainable. OpenBSD distributes source patches to make your farm of Pentium2 firewalls updated easly. if you own such a cluster (i doubt that) you would compile the patch only once and then distriubute the binaries. # Secure Distribution. The most secure operation system gets distributed on FTP servers as unsigned binaries. buy the cd or use cvs+ssh if you do not like unsigned ftp binaries. Disclaimer: Like it or not. I'm OpenBSD user for 4 years. Shit on my head - shit on all OpenBSD supporters. why did you start such a flame-mail? it makes you look like a whiner. if you do not like openbsd, use something else. regards, joerg
Re: OpenBSD and ISDN TA
Martin Schrvder [EMAIL PROTECTED] writes: Only the non-Germans. But you north-americans have probably also never expierenced the wonders of DECT or GSM... :-) It's possible ISDN was done right in Germany. Up here in Norway, it was the last-gasp attempt at abusing a monopoly position before telecom privatisation started. Not pretty. -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.datadok.no/ http://www.nuug.no/ Remember to set the evil bit on all malicious network traffic delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: facts about OpenBSD
On Thu, Jan 10, 2008 at 09:56:01PM +1100, Rod Whitworth wrote: On Thu, 10 Jan 2008 12:00:53 +0200, Nikns Siankin [EMAIL PROTECTED] wrote: [..] We have had several pointless trolls too many lately. As a result your pointless humour does not raise a laugh. Stay on-topic or fuck off like jacob does. Rod/ /earth: write failed, file system is full cp: /earth/creatures: No space left on device
Re: Open Source Article Spawns Interesting Ethical Question
On 1/10/08 11:10 AM, Otto Moerbeek wrote: On Thu, Jan 10, 2008 at 10:33:41AM +0100, chefren wrote: On 1/10/08 1:09 AM, Tobias Weingartner wrote: In article [EMAIL PROTECTED], chefren wrote: On 1/8/08 11:28 PM, Marco Peereboom wrote: 2. Same NIC without flash/ROM bad Eh, that's just a meaningless pile of transistors. Surely you jest? An FPGA is a meaningless pile of transistors? Weird... Without software loaded to it? Certainly. Just stupid silicon. It has the capability to be programmed. I would not call that stupid. ROFL Look around, somewhat further than your relatives and friends... If it's not programmed well, it's stupid. +++chefren
Re: facts about OpenBSD
Hello, On Jan 9, 2008 9:03 PM, Nikns Siankin [EMAIL PROTECTED] wrote: Facts about OpenBSD: # Stable release cycle. If you want to run latest bugfree ClamAV or FireFox - upgrade to CURRENT! But don't forget to buy release CD's!!! # Secure By Default. OpenBSD uses broken WEP for securing WiFi networks. Has no WPA/WPA2 support. # Do not let serious problems sit unsolved. OpenBSD doesn't need MAC because it has their own security flawed systrace. # Use of Cryptography. OpenBSD uses file-backed encryption (svnd) which is very suited for Full-disk-encryption. NOT. # Full Disclosure. OpenBSD at first denies remote exploitable flaws. DoS flaws gets marked as reliability not security issues. # Easy maintainable. OpenBSD distributes source patches to make your farm of Pentium2 firewalls updated easly. # Secure Distribution. The most secure operation system gets distributed on FTP servers as unsigned binaries. A lot of this is down to manpower or lack thereof. You can make it better if you put some effort in. Failing that, If it's so bad, then why don't you use another operating system? -- Best Regards Edd --- http://students.dec.bournemouth.ac.uk/ebarrett
Re: [Fwd: Open-Hardware]
On Thu, Jan 10, 2008 at 12:11:46AM -0500, [EMAIL PROTECTED] wrote: You can stop the GPL propaganda here. We have wasted enough time rehashing it. You are not going to convince anybody here that some random person has more rights than the author of the software. The end, get over it, walk it off. I'm not out to convince anyone that anyone has any more rights than anyone else. What I *was* doing was bringing that particular portion of the conversation back to more than just baseless bashing of a particular license. It isn't baseless you are simply blind to it because you are convinced that the GPL is the best thing evah! The GPL essentially strips the author of his/her rights. So here you are slaving away writing some code that you give away and then on top of that you have to forfeit your labor in favor of users. I hate to tell you this but that is the wrong way around. If enough people realize this they will either stop giving code away or switch licenses. The only beneficiaries of such a license are large corporations. The newer the GPL version the better in fact. Now you can give away code without giving it away. You can essentially prevent other companies to use it (TiVo clause) and some more rights to be given up on the patent clauses. We can debate the merit of the people vs companies here but it was either an unforeseen circumstance or a clever business trick. I put my money on the unforeseen one. If I was to start a company that had some software I'd buy the open source crowd by making my code GPLv3 and yet keep all my patents and code safe; put real IP in hardware and sell sell sell. This is not what the RMS/FSF tells you do. They say things like it's free! you are doing society a favor! non-gpl code is evil and unethical etc. These slogans are nothing but cover ups for the growing empire that is the FSF (yes lots of people forfeit their rights to them not knowing what they are giving up and no benefit to boot). RMS tried with circle talk to convince people and lost many acolytes in the process. GNU FSF are disingenuous organizations that are and unable to read a dictionary. That makes people angry so stop parroting their manure here. Yes, there has been quite a bit of manure slung by *both* sides. I prefer to stay out of that particular gutter. I personally don't care what anyone thinks of RMS, GNU *or* FSF. I'm an ardent supporter of none of the above. That is not how I see this. One side came to slander (not the first time either) and the other side kept correcting the slanderer. There might have been some strong words going back and forth but only one side was wrong. Lets call it self-defense. A few more cronies also tried and failed at convincing anyone of the GPL teachings. Yes we get your point and we think it is stupid. No need to discuss it or try to explain it again. We get it. They're not my teachings or teachings to which I particularly subscribe. I would maintain that most of the more popular licenses have their pros - ultimately it depends on who or what you want to protect. Popular does not mean good. VHS anyone? As I said before the GPL is sold on false premises and unfortunately a lot of people stop thinking by the time they hear free as in beer, can't be closed, unethical code etc. These slogans are not true and are used to sell something that is of no benefit to the author. Roughly the same way that communism was sold to the people. That is where the FSF stands today. They outlived their usefulness and really should have closed shop but instead they reinvented themselves with new goals. This also happens in the business world. For example, In the past unions created some real benefit for workers and today are shills for someone in power. Let me quote my man Franklin: Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety. Where the GPL is temporary safety in trade of Essential Liberty. Don't paint me with the RMS/GNU brush because I refused to stand by and watch *blatantly* false accusations be made. There is a big difference between correcting those accusations and *supporting* the recipient of the accusations. Then don't stand by them by not replying to this. By adding to this thread you picked a side like it or not. kmw
Re: facts about OpenBSD
Nikns Siankin [EMAIL PROTECTED] writes: The only people who could make it better are talking to community only when release CD needs to get sold or donations are needed. This tells me mainly you don't actually read the OpenBSD mailing lists. Damn, misc@ used to have such a nice signal to noise ratio. -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.datadok.no/ http://www.nuug.no/ Remember to set the evil bit on all malicious network traffic delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: facts about OpenBSD
On Thu, Jan 10, 2008 at 11:56:15AM +0100, Joerg Zinke wrote: On Wed, 9 Jan 2008 23:03:29 +0200 Nikns Siankin [EMAIL PROTECTED] wrote: Facts about OpenBSD: # Stable release cycle. If you want to run latest bugfree ClamAV or FireFox - upgrade to CURRENT! But don't forget to buy release CD's!!! if you do not like to use CURRENT, send a patch which backports these versions to stable. you are listed as maintainer for some ports, means you should know how things work. Take a look on ports@ and see how much submited -stable patches are commited. None!? # Secure By Default. OpenBSD uses broken WEP for securing WiFi networks. Has no WPA/WPA2 support. wpa is not much better than wep. useful alternative: ipsec, another alternative: secure your wlan with pf/authpf. WPA and IPSEC secures your wlan in different layers. WPA *is* much better than wep. # Do not let serious problems sit unsolved. OpenBSD doesn't need MAC because it has their own security flawed systrace. i do not get the point. seriously, have you ever used systrace? Sure I do, but it's flawed now anyway. OpenBSD needs MAC. # Use of Cryptography. OpenBSD uses file-backed encryption (svnd) which is very suited for Full-disk-encryption. NOT. wrong. i use it on a whole raid 1 disk for example, no problems here. Me too. I'm talking about full-disk-encryption, which doesn't seem to be easy hack. $ df -h Filesystem SizeUsed Avail Capacity Mounted on [...] /dev/svnd0c411G249G141G64%/media # Full Disclosure. OpenBSD at first denies remote exploitable flaws. DoS flaws gets marked as reliability not security issues. what's the problem? Denial of Service stands for AVAILABILITY. Information security goals are confidentiality, integrity AND availability. # Easy maintainable. OpenBSD distributes source patches to make your farm of Pentium2 firewalls updated easly. if you own such a cluster (i doubt that) you would compile the patch only once and then distriubute the binaries. # Secure Distribution. The most secure operation system gets distributed on FTP servers as unsigned binaries. buy the cd or use cvs+ssh if you do not like unsigned ftp binaries. That CD gets sent by traditional mail + not all packages are on CD. Compiling everything from sources doesn't look like solution for masses. Disclaimer: Like it or not. I'm OpenBSD user for 4 years. Shit on my head - shit on all OpenBSD supporters. why did you start such a flame-mail? it makes you look like a whiner. if you do not like openbsd, use something else. Wrong. I like OpenBSD. But these are things I consider for the most secure os to be fixed. I get lot of response offlist. It seems that people are afraid to discuss these issues onlist, guess because of this YOURE WHINER or DONT LIKE DONT USE attitude. regards, joerg
Re: facts about OpenBSD
On Thu, Jan 10, 2008 at 12:43:48PM +, Edd Barrett wrote: Hello, A lot of this is down to manpower or lack thereof. You can make it better if you put some effort in. Failing that, If it's so bad, then why don't you use another operating system? Hi, I don't believe anymore, that someone from side can make it better. The only people who could make it better are talking to community only when release CD needs to get sold or donations are needed. -- Best Regards Edd --- http://students.dec.bournemouth.ac.uk/ebarrett
Re: facts about OpenBSD
On Thu, Jan 10, 2008 at 07:02:16PM +0530, Amarendra Godbole wrote: On Jan 10, 2008 6:14 PM, Nikns Siankin [EMAIL PROTECTED] wrote: [...] I get lot of response offlist. It seems that people are afraid to discuss these issues onlist, guess because of this YOURE WHINER or DONT LIKE DONT USE attitude. [...] I am relatively new to OpenBSD, I am merely a user, and I read the misc@ list always. I do my homework mostly before posting/asking for doubts, and IMHO, OpenBSD folks have been the most kind and helpful till now. The S/N ratio on these lists is very-high (unless folks like RMS topple it). The learning method here is very difficult - you do your homework, and expect no handholding at all. For people having very less patience, and who wish to always be spoon fed, and who whine without offering a solution (at least I did not see it on misc@), there are many Linux mailing lists around. Not OpenBSD for sure. Now please, if you feel something is not working, or broken, or needs improvement - send a patch to tech@, and if its worth it will be accepted (no I haven't submitted yet a single patch, heck, I don't even know 0.5% of OBSD source code. But I am learning, and I will take my own time). Ok. You are new to OpenBSD and naive. I see people keep repeating nonsense like this instead of talking about topic. Are you upset because: - your patches were not accepted - RMS paid you to topple the S/N ratio one more time - you don't get any handholding from the devs - reason unknown to me (tick one, then have a cup of coffee, take a walk in the woods, and come back). If you still don't like OpenBSD and are totally fed up with it, DON'T USE IT. -Amarendra
Re: facts about OpenBSD
On Jan 10, 2008 6:14 PM, Nikns Siankin [EMAIL PROTECTED] wrote: [...] I get lot of response offlist. It seems that people are afraid to discuss these issues onlist, guess because of this YOURE WHINER or DONT LIKE DONT USE attitude. [...] I am relatively new to OpenBSD, I am merely a user, and I read the misc@ list always. I do my homework mostly before posting/asking for doubts, and IMHO, OpenBSD folks have been the most kind and helpful till now. The S/N ratio on these lists is very-high (unless folks like RMS topple it). The learning method here is very difficult - you do your homework, and expect no handholding at all. For people having very less patience, and who wish to always be spoon fed, and who whine without offering a solution (at least I did not see it on misc@), there are many Linux mailing lists around. Not OpenBSD for sure. Now please, if you feel something is not working, or broken, or needs improvement - send a patch to tech@, and if its worth it will be accepted (no I haven't submitted yet a single patch, heck, I don't even know 0.5% of OBSD source code. But I am learning, and I will take my own time). Are you upset because: - your patches were not accepted - RMS paid you to topple the S/N ratio one more time - you don't get any handholding from the devs - reason unknown to me (tick one, then have a cup of coffee, take a walk in the woods, and come back). If you still don't like OpenBSD and are totally fed up with it, DON'T USE IT. -Amarendra
Re: facts about OpenBSD
Amen to this. On Jan 10, 2008 8:18 AM, Peter N. M. Hansteen [EMAIL PROTECTED] wrote: Damn, misc@ used to have such a nice signal to noise ratio. -- # Curt Micol Today is the tomorrow I was so worried about yesterday. -Anthony Hopkins
Re: facts about OpenBSD
On Jan 10, 2008 8:39 AM, Nikns Siankin [EMAIL PROTECTED] wrote: I see people keep repeating nonsense like this instead of talking about topic. This is due to the fact that people don't feel your thoughts are on topic. Bitch elsewhere, thats what blogs are for. Leave misc@ for those people who want to work on or with the OS. Your stupid thoughts are unimportant unless you are willing to contribute to assist with fixing what it is you think is wrong. Please unsubscribe and stop trolling. -- # Curt Micol Today is the tomorrow I was so worried about yesterday. -Anthony Hopkins
Re: facts about OpenBSD
On Thu, Jan 10, 2008 at 09:04:52AM -0500, Curt Micol wrote: On Jan 10, 2008 8:39 AM, Nikns Siankin [EMAIL PROTECTED] wrote: I see people keep repeating nonsense like this instead of talking about topic. This is due to the fact that people don't feel your thoughts are on topic. Bitch elsewhere, thats what blogs are for. Leave misc@ for those people who want to work on or with the OS. Your stupid thoughts are unimportant unless you are willing to contribute to assist with fixing what it is you think is wrong. If my stupid thoughts are unimportant for you, fuckoff and go shit elsewhere. Please unsubscribe and stop trolling. -- # Curt Micol Today is the tomorrow I was so worried about yesterday. -Anthony Hopkins
Re: facts about OpenBSD
Amarendra Godbole schrieb: On Jan 10, 2008 6:14 PM, Nikns Siankin [EMAIL PROTECTED] wrote: [...] I get lot of response offlist. It seems that people... [...] I am relatively new to OpenBSD, I am merely a user, and I read the misc@ list always. I do my homework mostly before posting/asking for doubts, and IMHO, OpenBSD folks have been the most kind and helpful till now. The S/N ratio on these lists is very-high (unless folks like RMS topple it). The learning method here is very difficult - you do your homework, and expect no handholding at all. [...] Are you upset because: - your patches were not accepted - RMS paid you to topple the S/N ratio one more time - you don't get any handholding from the devs - reason unknown to me (tick one, then have a cup of coffee, take a walk in the woods, and come back). If you still don't like OpenBSD and are totally fed up with it, DON'T USE IT. I like that post, Amarendra, I think you have written what many people are thinking. -- Michael Schmidt MIRRORS: Watcom ftp://ftp.fh-koblenz.de/pub/CompilerTools/Watcom/ OpenOffice ftp://ftp.fh-koblenz.de/pub/OpenOffice/
Re: facts about OpenBSD
On 2008/01/10 14:44, Nikns Siankin wrote: # Do not let serious problems sit unsolved. OpenBSD doesn't need MAC because it has their own security flawed systrace. i do not get the point. seriously, have you ever used systrace? Sure I do, but it's flawed now anyway. even flawed, systrace is damn useful, porters use it all the time to help detect when ports need extra work to make sure they install things to the right place. OpenBSD needs MAC. you haven't said anything to convince me about that... you might see a need for it, but plenty of people don't. # Use of Cryptography. OpenBSD uses file-backed encryption (svnd) which is very suited for Full-disk-encryption. NOT. wrong. i use it on a whole raid 1 disk for example, no problems here. Me too. I'm talking about full-disk-encryption, which doesn't seem to be easy hack. of course not. if it were easy, it would most likely be already available. it *is* being worked on though. see the last paragraph in http://www.onlamp.com/pub/a/bsd/2007/11/01/whats-new-in-bsd-42.html?page=last # Full Disclosure. OpenBSD at first denies remote exploitable flaws. DoS flaws gets marked as reliability not security issues. what's the problem? Denial of Service stands for AVAILABILITY. Information security goals are confidentiality, integrity AND availability. 'security fix' is a way of saying, look, this is *important*, read it right away, if it affects you and you can't work around, patch urgently. if you start calling every problem a security fix, people won't take the real security fixes seriously. of *course* people interested in availability should treat reliability fixes as a high priority too. and it's absolutely clear how OpenBSD errata are labelled so there's no excuse not to. but for some (I think most) people, a bug resulting in crashes is *far* less of a problem than a bug resulting in unauthorised control of your machines. so it's a good thing that they're labelled differently. I get lot of response offlist. It seems that people are afraid to discuss these issues onlist, guess because of this YOURE WHINER or DONT LIKE DONT USE attitude. maybe also because, having just had a something of a flamefest, they're wary of fanning this fire.
Re: [Fwd: Open-Hardware]
Tony Abernethy wrote: [EMAIL PROTECTED] wrote: I'm not out to convince anyone that anyone has any more rights than anyone else. HOWEVER, the original author DOES have more rights than anyone else. In particular, the original author says who has what rights. You have no say in the matter. Your opinion does not count. Hi Tony. I'm not going to argue against that. The author, as creator of the piece of work and originator of the copyright, does have more rights. It's true. I'm just not out to *convince* anyone of it. kmw
Re: [Fwd: Open-Hardware]
Tony Abernethy wrote: [EMAIL PROTECTED] wrote: I was pointing out that you could release the alpha/beta/testing software under whatever license you choose that will keep it from being re-distributed Huh??? What kind of release is not re-distributed? By redistribute I do not mean the author distributes it again, I mean the recipient then acts as a distributor. Just because I have an alpha release of some software doesn't mean I have the right to redistribute that software. Those rights are determined by my license agreement. kmw
Re: [Fwd: Open-Hardware]
Marco Peereboom wrote: On Thu, Jan 10, 2008 at 12:11:46AM -0500, [EMAIL PROTECTED] wrote: I'm not out to convince anyone that anyone has any more rights than anyone else. What I *was* doing was bringing that particular portion of the conversation back to more than just baseless bashing of a particular license. It isn't baseless you are simply blind to it because you are convinced that the GPL is the best thing evah! What have you been smoking and can a brotha get a hit? I am not a particularly large fan of the GPL. It's not my first choice of license but I can see where it has its uses. It also has its fair share of issues and those issues are fair reasons for attack. Bash it for its legitimate flaws, though, and not by making sensationalist claims that aren't true. The GPL essentially strips the author of his/her rights. So here you are slaving away writing some code that you give away and then on top of that you have to forfeit your labor in favor of users. I hate to tell you this but that is the wrong way around. I'm not making any statements to the contrary. If you choose to give your code away then that's your own mistake. Why would you hate to have to tell me that? That is not how I see this. One side came to slander (not the first time either) and the other side kept correcting the slanderer. There might have been some strong words going back and forth but only one side was wrong. Lets call it self-defense. Yes, RMS slandered. Tell him he's wrong, that the comment was incorrect and that his argument is bollocks. Rally the troops for self-defense. That's the right thing to do. Attack the GPL for its flaws. That's the right thing to do. I'm not denouncing either of these acts. What I *am* denouncing are some of the sensationalist claims that were incorrect. They're not my teachings or teachings to which I particularly subscribe. I would maintain that most of the more popular licenses have their pros - ultimately it depends on who or what you want to protect. Popular does not mean good. VHS anyone? That's why I intentionally said more popular. Lots of things are popular but complete rubbish. Somewhere along the line each of the more popular licenses scratched an itch for some developer or organization and others felt that *something* about the license was useful to them - the license had it's pros. Let me quote my man Franklin: Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety. Where the GPL is temporary safety in trade of Essential Liberty. That's quite a broad stretch to make and I both agree and disagree. I think it boils down to what it is you're trying to protect. Nice use of Ben. Don't paint me with the RMS/GNU brush because I refused to stand by and watch *blatantly* false accusations be made. There is a big difference between correcting those accusations and *supporting* the recipient of the accusations. Then don't stand by them by not replying to this. By adding to this thread you picked a side like it or not. Let's use your own quotation from Franklin. By not replying I am foregoing my own Liberty in exchange for a bit of temporary safety in not being painted with that brush. I choose, instead, to exercise the ability to reply and say that this is not an us or them situation and that I refuse to allow myself to be painted that colour. I've chosen no side. If that means I get cut down by yours because you want to make it a with us or against us argument, fine. If that means I get cut down by RMS/GNU/FSF because they want to make it a with us or against us argument, fine. *I don't care*. I choose to remain a neutral third party that can see the benefits (and detriments) of the different licenses. You can't lump someone as your enemy simply because they aren't full of fervour for your cause. kmw -- Quis custodiet ipsos custodes
Re: Intel DQ35MP
Hello , i tried updating the BIOS to the newest one, removed one ram stick, installed latest snapshot and also tried disabling APM as you adviced me. When booting with bsd it doesn't recognize the devices just like before. Now i also tried booting with bsd.mp instead of bsd , and i get this error: OpenBSD 4.2-current (GENERIC.MP) #539: Tue Jan 8 17:20:15 MST 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC.MP RTC BIOS diagnostic error 80clock_battery cpu0: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (GenuineIntel 686-class) 2.39 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16, xTPR real mem = 1040625664 (992mb) avail mem = 998227968 (951mb) RTC BIOS diagnostic error 80clock_battery mainbus0 at root bios0 at mainbus0: at/286+ BIOS, date 12/10/07, SMBIOS rev. 2.4 @ 0xe2440 (31 entries) bios0: vendor Intel Corp. version JOQ3510J.86A.0731.2007.1210.2204 date 12/10/2007 bios0: Intel Corporation DQ35MP acpi0 at bios0: rev 0panic: malloc: allocation too large Stopped atDebugger+0x4: leave Debugger(e3ff000,0,d0916b48,2,3ff7) at Debugger+0x4 panic(d06b38ce,d0916b64,1000,d07b0a20,) at panic+0x63 malloc(f000ff5b,2,1,d0680060) at malloc+0x76 acpi_load_table(0,f000ff53,d19cce3c,de3fe000,d19c1f80) at acpi_load_table+0x19 acpi_loadtables(d19cce00,de3fd020,5,e) at acpi_loadtables+0x95 acpi_attach(d19cbf80,d19cce00,d0916d50,d19cbf80,0) at acpi_attach+0xb2 config_attach(d19cbf80,d078b980,d0916d50,d0604eb4) at config_attach+0xfd biosattach(d19cbfc0,d19cbf80,d0916e80,d19cbfc0,d02032c9) at biosattach+0x34e config_attach(d19cbfc0,d078ab70,d0916e80,d04a6504,d06d6958) at config_attach+0xfd mainbus_attach(0,d19cbfc0,0,de3f7000,d0915334) at mainbus_attach+0x3d RUN AT LEAST ... Regards, Marcos - Original Message - From: Pierre Riteau [EMAIL PROTECTED] To: Marcos Laufer [EMAIL PROTECTED] Cc: misc@openbsd.org Sent: Thursday, December 13, 2007 8:55 PM Subject: Re: Intel DQ35MP On Dec 13, 2007 9:25 PM, Marcos Laufer [EMAIL PROTECTED] wrote: Hello, I've just installed OpenBSD current on an Intel DQ35MP motherboard with a Quad processor, this is the dmesg log. Some devices are not recognized (PCI slot, ethernet, etc) boot -c to go in UKC or config -ef /bsd and use 'disable apm' to get acpi to attach. Maybe it will help. Also, you can get a newer snapshot. OpenBSD 4.2-current (GENERIC) #558: Tue Nov 20 10:36:15 MST 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC RTC BIOS diagnostic error 80clock_battery cpu0: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (GenuineIntel 686-class) 2.39 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16, xTPR real mem = 2097643520 (2000MB) avail mem = 2020409344 (1926MB) RTC BIOS diagnostic error 80clock_battery mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 07/26/07, SMBIOS rev. 2.4 @ 0xe2460 (30 entries) bios0: vendor Intel Corp. version JOQ3510J.86A.0559.2007.0726.0425 date 07/26/2007 bios0: Intel Corporation DQ35MP apm0 at bios0: Power Management spec V1.2 apm0: battery life expectancy 0% apm0: AC off, battery charge unknown, estimated 0:00 hours pcibios at bios0 function 0x1a not configured bios0: ROM list: 0xc/0xb400! 0xcb800/0x1e00! 0xcd800/0x1000 0xce800/0x1000 cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 vendor Intel, unknown product 0x29b0 rev 0x02 vga1 at pci0 dev 2 function 0 vendor Intel, unknown product 0x29b2 rev 0x02: aperture at 0x9020, size 0x800 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) vendor Intel, unknown product 0x29b4 (class communications subclass miscellaneous, rev 0x02) at pci0 dev 3 function 0 not configured pciide0 at pci0 dev 3 function 2 vendor Intel, unknown product 0x29b6 rev 0x02: DMA (unsupported), channel 0 wired to native-PCI, channel 1 wired to native-PCI pciide0: using irq 9 for native-PCI interrupt pciide0: channel 0 ignored (not responding; disabled or no drives?) pciide0: channel 1 ignored (not responding; disabled or no drives?) vendor Intel, unknown product 0x29b7 (class communications subclass serial, rev 0x02) at pci0 dev 3 function 3 not configured Intel ICH9 IGP AMT rev 0x02 at pci0 dev 25 function 0 not configured uhci0 at pci0 dev 26 function 0 Intel 82801I USB rev 0x02: irq 9 uhci1 at pci0 dev 26 function 1 Intel 82801I USB rev 0x02: irq 9 uhci2 at pci0 dev 26 function 2 Intel 82801I USB rev 0x02: irq 10 ehci0 at pci0 dev 26 function 7 Intel 82801I USB rev 0x02: irq 10 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb0 at pci0 dev 28 function 0 Intel 82801I PCIE rev 0x02 pci1 at ppb0 bus 1 ppb1 at
