Why I left OpenBSD
http://www.trollaxor.com/2010/06/why-i-left-openbsd.html
Re: Why I left OpenBSD
Man, it's not me. Just wanted to share that with you all. On 10 June 2010 11:40, Dunceor dunc...@gmail.com wrote: On Thu, Jun 10, 2010 at 10:28 AM, Dexter Tomisson dexterto...@gmail.com wrote: http://www.trollaxor.com/2010/06/why-i-left-openbsd.html Ok why write a long text and the only reason you have is that you are unhappy with driver support and with Theo? I was looking for some more indepth discussion on why you choose not to use OpenBSD anymore but it was just another worthless post. This feels more like the usual troll post of people that got hurt while dealing with Theo. Like somebody said, is this the year of trolls?
Re: Why I left OpenBSD
What a waste of bytes.. Which planet did you come from? Well, at least, are you able to read? On 10 June 2010 12:10, S H sahservi...@gmail.com wrote: Dexter, I'm still relatively new to OpenBSD and the community, however a few days ago you had asked about why large memory support still wasn't enabled by default. Asking if the developers needed hardware, funding or what not to get it working properly. If you were in fact a developer as your latest rant states and large memory was such a concern for you, it would stand to reason that you would be well aware of why it hasn't made it into the default install. Also, a developer likely wouldn't piss and moan about it on the mailing lists, rather they would just start working to rectify the situation. Your obviously full of shit IMO, FreeBSD 7.2 came out quite some time ago. If you havent been using OpenBSD since your change than why did you inquire about large memory support three days ago? On Thu, Jun 10, 2010 at 4:45 AM, Dexter Tomisson dexterto...@gmail.com wrote: Man, it's not me. Just wanted to share that with you all. On 10 June 2010 11:40, Dunceor dunc...@gmail.com wrote: On Thu, Jun 10, 2010 at 10:28 AM, Dexter Tomisson dexterto...@gmail.com wrote: http://www.trollaxor.com/2010/06/why-i-left-openbsd.html Ok why write a long text and the only reason you have is that you are unhappy with driver support and with Theo? I was looking for some more indepth discussion on why you choose not to use OpenBSD anymore but it was just another worthless post. This feels more like the usual troll post of people that got hurt while dealing with Theo. Like somebody said, is this the year of trolls?
It is 2010. Still no 3GB support by default?
I'd really, really like to know what's the matter with a larger memory support? Why is 'bigmem' still not default? What faults/bugs does it still has? What do you need to make it ok? Do you need a hardware donation to make that better, do you need few bucks, do you need a good coder to improve that, or again some license problems perhaps?, what's the problem, share with us please, I'd really like to help with everything i can. I hope, maybe someday, our beloved Puffy will catch up to the 21st century. Regards. deX
Re: It is 2010. Still no 3GB support by default?
No, 640k ought to be enough for anybody On 7 June 2010 22:12, Bret S. Lambert bret.lamb...@gmail.com wrote: On Mon, Jun 07, 2010 at 09:52:50PM +0300, Dexter Tomisson wrote: It's the future, where's my goddamn flying car?
Re: Installer bug? - Upgrade 4.6 to 4.7 failed to upgrade base47, on i386 and amd64
what a totally useless bunch of misc traffic only because a drunk OpenBSD user did not remove /usr/obj before building shit
wrong sshd log alert
my steps: login as: root t...@xx.xx.xx.xx's password: [valid password entered] [logged in] # exit sshd log output: Jun 4 12:03:12 sys sshd[1235]: Connection from MY.IP.AD.DR port 3894 Jun 4 12:03:15 sys sshd[1235]: Failed none for root from MY.IP.AD.DR port 3894 ssh2 Jun 4 12:03:17 sys sshd[1235]: Accepted password for root from MY.IP.AD.DR port 3894 ssh2 Jun 4 12:03:19 sys sshd[1235]: Connection closed by MY.IP.AD.DR Jun 4 12:03:19 sys sshd[1235]: Transferred: sent 3784, received 1928 bytes Jun 4 12:03:19 sys sshd[1235]: Closing connection to MY.IP.AD.DR port 3894 I don't see any reason why i get Failed none for root from alert. I didn't enter any wrong user/password. OpenBSD 4.7-stable.
Re: wrong sshd log alert
Yes, my bad.. Using Putty. I've no idea what it does while trying to log in.. On 4 June 2010 16:15, Kenneth Gober kgo...@gmail.com wrote: I wouldn't call it wrong, necessarily. what ssh client are you using? does it attempt to use authentication-type none in order to get a list of supported authentication types from the server? or because it only wants to prompt you for a password if authentication is required? perhaps confusing or misleading would be a better description for this entry. -ken On Fri, Jun 4, 2010 at 7:11 AM, Dexter Tomisson dexterto...@gmail.comwrote: my steps: login as: root t...@xx.xx.xx.xx's password: [valid password entered] [logged in] # exit sshd log output: Jun 4 12:03:12 sys sshd[1235]: Connection from MY.IP.AD.DR port 3894 Jun 4 12:03:15 sys sshd[1235]: Failed none for root from MY.IP.AD.DR port 3894 ssh2 Jun 4 12:03:17 sys sshd[1235]: Accepted password for root from MY.IP.AD.DR port 3894 ssh2 Jun 4 12:03:19 sys sshd[1235]: Connection closed by MY.IP.AD.DR Jun 4 12:03:19 sys sshd[1235]: Transferred: sent 3784, received 1928 bytes Jun 4 12:03:19 sys sshd[1235]: Closing connection to MY.IP.AD.DR port 3894 I don't see any reason why i get Failed none for root from alert. I didn't enter any wrong user/password. OpenBSD 4.7-stable.
Re: unknown i686 model 0x1e, can't get bus clock (0x0)
On 4 June 2010 14:25, Andreas Gerdd kryptos...@gmail.com wrote: And should we expect having a better support for Intel Core i5/i7 CPUs in the near future, maybe for the next release cycle? Sounds no; Changes by: j...@cvs.openbsd.org 2010/06/04 09:03:35 Modified files: sys/arch/amd64/amd64: est.c sys/arch/i386/i386: machdep.c Log message: Don't warn about not knowing what the bus clock is on core i7/i5/i3 as the high/low guessing won't be done on these processors due to MSR differences. Just 'hide' them. Such a great solution!
Re: unknown i686 model 0x1e, can't get bus clock (0x0)
weird... Maybe OpenBSD doesn't support Intel Core i5 750? cool mainboard, btw.. On 2 June 2010 13:54, kryptos...@gmail.com kryptos...@gmail.com wrote: Hi, On OpenBSD 4.7, my dmesg output has the following alerts: cpu1: unknown i686 model 0x1e, can't get bus clock (0x0) cpu2: unknown i686 model 0x1e, can't get bus clock (0x0) cpu3: unknown i686 model 0x1e, can't get bus clock (0x0) Is this a normal alert? Any idea? My CPU is an Intel Core i5 750 @ 2.67 Ghz, It is a ASUS P7H55-M SI computer. I've sent the following details to dm...@openbsd.org; dmesg, sysctl hw, sysctl hw.sensors outputs are here: http://pastebin.com/raw.php?i=BUm5ENvv Thanks.
Re: low httpd performance. Apache 2.2 as default? never? *sighs
On 3 May 2010 03:31, VICTOR TARABOLA CORTIANO vt...@c3sl.ufpr.br wrote: I will print this mail and laugh everyday with it. :) This is especially for you, Victor. Print that too please, and laugh everyday :): ab -n 1 -c 10 127.0.0.1/1.tar.gz Apache 1.3.29 Requests per second:149.23 [#/sec] (mean) Apache 2.2.2 Requests per second:375.02 [#/sec] (mean)
low httpd performance. Apache 2.2 as default? never? *sighs
Hi. OpenBSD's stock httpd is very slow and outdated. It is about 6 years old. Almost an abandonware. Is it that impossible to see OpenBSD coming with (chroot'ed) Apache 2.2.x by the default? That would be great! The license problem would be solved by discussing it with the Apache community, imho. http://old.nabble.com/OpenBSD---the-Apache-license-problem.-Why--td28387885.html Thanks
