Re: Suggestion
Violating copyright laws because software should be free or I found it on the Internet!!! is dangerous if you actually have a job or your mommy and daddy aren't willing to pay your legal costs if you get caught. Like stealing money from winos, you might not get caught but it teaches dangerous habits that shouldn't be taught in your social life or professional life. OpenBSD and the other open sourced operating systems have been very good about this: Nomen should not be suggesting dangerous habits on a public mailing list. I was not suggesting anything. I was answering a rhetorical question with a rhetorical answer. Read what I wrote and don't have a cow, dude. If you want Windows you can buy a copy or rip one off. That is the reality. FreactOS isn't going to help people who want Windows. My question was retorical. So was my answer your question was based on. I'm afraid that some folks do think that pirated copies are free. Ethics can be very difficult: is it ethical to steal from a thief? Yes, see below :-) For someone who's living in the I can steal it for free, why bother with a freeware one world, explaining ethical or moral behavior can be awkward. Because freeware has to have advantages other than being free. OpenBSD is not good because it's free as in beer, it's good because it's good for technical reasons. The fact it's free as in not GPL, and doesn't cost money is just more to like about it. It is not the main thing to like about it. There's that and the twenty some odd boxes I bought in the last 20 years that had various versions of Windows forcibly installed that I paid for, most without any install media. Forgive me for not feeling like a criminal when I run bootlegged copies of XP in a VM to do stuff for $WORK since I do believe I have the right to run to run copies of the Curse of Redmond without pissing further hard earned $CURRENCY away on them. BTW Redmond assholes, if you're reading this, you shitheads owe me twenty fucking CDs with your shit-for-an-OS installation on them. Until then, FUCK YOU! Go Chinese hackers, you rock! ;-) Keep on crackin' it babe, keep on crackin' it. As far as I'm concerned, Microsoft is the criminal. The people who rip off copies are justified based on MicroPimp's criminal business practices. Don't try to extrapolate this to other issues, it's specific to MicroPimp.
Re: My OpenBSD 5.0 installation experience (long rant)
On Fri, 2012-03-09 at 13:44 -0500, Kenneth R Westerback wrote: That's interesting, as for me bsd.rd only creates sd0, so I have to find the right sdN in dmesg and then cd /dev; sh MAKEDEV sdN if I want to install OS there... That strikes me as an interesting error. The install process is supposed to create any device needed when you select a disk. i.e. the 'makedev $resp || exit' line at the end of install.sub. These days the script even automatically adjusts the list of disks when devices are plugged in or removed. Can you provide more details/confirmation of the need to manually create devices on 5.1 or -current? I installed OpenBSD 5.0 on the laptop where I originally spotted this problem, and indeed I had all the inserted hardware detected right and present in installer. Probably I missed some changes - normally I unplug everything during installation. Anyway, sorry for wasting everyone's time on this. -- Dmitrij D. Czarkoff
Re: Suggestion
On Sunday 11 March 2012 07:57:35 Nomen Nescio wrote: You wrote: On Friday 09 March 2012 13:10:13 Nomen Nescio wrote: Who in their right mind would EVER want to run this crap? You answered your own question. My guess? People who are too cheap to buy Windows and too stupid to figure out how to find a free copy of XP or Win 7 on the net and do the activation or find a password. That's a pretty small user space. Free copy's of Windows? Do they exist? The point is if you want Windows you have two ways of getting it. You can buy a copy or rip one off. Got it now? Either one runs better than FreactOS It was a retoriocal question? Got it now?
Fw: aucat problem (file_poll: negative time interval)
Hello! aucat seems to go down When running ices2, I get sudo aucat - sio(default|): created default: recording s16le,0:1,48000 default: playing s16le,0:1,48000 mix(play): newout, will use 12800 fr default: block size is 3200 frames, using 4 blocks default@default: rec=0:1 play=0:1 vol=32768 listen(/tmp/aucat/aucat0|): created sock(sock|): created sock/aut|rmsg|widl: AUTH message sock/hel|rmsg|widl: HELLO message sock/hel|rmsg|widl: hello from ices2, mode = 2, ver 5 default: option found device requested sock/hel|rmsg|widl: using mode = 2 ices0: overwritten slot 0 sock/hel|rmsg|widl: no read buffer to set volume yet ices0/ini|rmsg|widl: SETPAR message ices0/ini|rmsg|widl: using 16bits, 2 bytes per sample ices0/ini|rmsg|widl: using recording channels 0..1 ices0/ini|rmsg|widl: using 48000Hz sample rate, 3200 fr block size ices0/ini|rmsg|widl: using 35200 buffer size ices0: buffer size = 35200, rec:s16le,0:1,48000 ices0/ini|rmsg|widl: GETPAR message ices0/ini|rmsg|widl: GETPAR message ices0/ini|rmsg|widl: GETPAR message ices0/ini|rmsg|widl: START message ices0/sta|rmsg|widl: allocating 35200/48000 fr buffers, rmax = 0 ices0/run|rmsg|widl: attaching at 0 syncing device, mix(play): todo = 0: lat = 0, sub(rec): lat = 0 starting device sio(default|): started default: wrote 12800 bytes in 10021us sock: wrote 0 bytes in 10004us sock: wrote 40 bytes in 10004us sock: wrote 40 bytes in 10004us sock: wrote 4016 bytes in 10009us sock: wrote 0 bytes in 10004us file_poll: negative time interval Abort trap
dear all
On 03/09/2012 12:05 AM, Mic J wrote: Dear Fredrik Staxeng. Im sorry to hear you had a bad experience when communicating with our team. Could you please specify your exact problem, What was the question you got a snappy answer about And what was it Linus was right about. WE at OpenBSD.org works hard to provide a great customer and user experience. I assure you that we have pointed out to staff members that they have to provide precise and courteous answers to customers. Also the internal guidelines for customer communications have ben strengthened, To ensure these incidents shouldnt happen in the future. Being an opensource project is challenging to ensure conforming answers, but we have implemented a proxy where by all team members mail are forwarded and screened for accuracy and content and discussed internally before reaching the customer. Yours sincerely Chief head of OpenBSD communication department. (i did fix a typo in documentation once) On Fri, Mar 9, 2012 at 8:28 AM, Fredrik Staxeng fst...@update.uu.se wrote: Do you want users at all? Or was Linus right? -- Fredrik Stax\ang | rot13: s...@hcqngr.hh.fr This is all you need to know about vi: ESC : q ! RET trump dat - - - hey trump that just cost you trip 7 : -e -o mv $bsd $addHOOK
Re: Snappy Answers to Stupid Questions - WTF?
On 03/09/2012 12:05 AM, Mic J wrote: Dear Fredrik Staxeng. Im sorry to hear you had a bad experience when communicating with our team. Could you please specify your exact problem, What was the question you got a snappy answer about And what was it Linus was right about. WE at OpenBSD.org works hard to provide a great customer and user experience. I assure you that we have pointed out to staff members that they have to provide precise and courteous answers to customers. Also the internal guidelines for customer communications have ben strengthened, To ensure these incidents shouldnt happen in the future. Being an opensource project is challenging to ensure conforming answers, but we have implemented a proxy where by all team members mail are forwarded and screened for accuracy and content and discussed internally before reaching the customer. Yours sincerely Chief head of OpenBSD communication department. (i did fix a typo in documentation once) On Fri, Mar 9, 2012 at 8:28 AM, Fredrik Staxengfst...@update.uu.se wrote: Do you want users at all? Or was Linus right? -- Fredrik Stax\ang | rot13: s...@hcqngr.hh.fr This is all you need to know about vi: ESC : q ! RET ps - you.re an idiot
@theo
:get de raddt
Re: Suggestion
cat wtf ... On 03/09/2012 08:36 AM, Timothy Baldock wrote: Renzo Fabriek wrote: On Friday 09 March 2012 13:10:13 Nomen Nescio wrote: Who in their right mind would EVER want to run this crap? You answered your own question. My guess? People who are too cheap to buy Windows and too stupid to figure out how to find a free copy of XP or Win 7 on the net and do the activation or find a password. That's a pretty small user space. Free copy's of Windows? Do they exist? Free as in ripped off. Although the Hypervisor-only version of 2008 R2 is iirc free as in not costing any money.
Re: My OpenBSD 5.0 installation experience (long rant)
font = Droid Sans Japanese @theo smashing pumpkins mellon collie ... and ..
Re: Suggestion
On Sun, 11 Mar 2012 08:58:24 +0100 (CET) Anonymous wrote: Forgive me for not feeling like a criminal when I run bootlegged copies of XP in a VM to do stuff for $WORK since I do believe I have the right to run to run copies of the Curse of Redmond without pissing further hard earned $CURRENCY away on them. Too right, and reinstalling Xp from your own cd on an old laptop for a friend with a key on the bottom that only works with OEM crap, the worst part is they probably use that multiple activations data to their benefit in court.
Re: Which high end multichannel audio interfaces work?
On Fri, Mar 9, 2012 at 12:17 PM, Jochen Fabricius jfabric...@web.de wrote: Hi, I'm looking for a really high end multichannel (at least 2 in 8 out, breakout box) audio interface that works with OpenBSD. Obviously the M-Audio Delta 1010 does, because it is listed in envy(4). But this interface needs an external power supply, and I want to avoid it is possible. So I found the Echo Layla 3G http://www.echoaudio.com/Products/PCI/Layla3G/index.php Does anybody know if this card works with OpenBSD? Or any other interface of similar quality? I want to build a very flexible PC based digital crossover solution, with room equalizing and music playback from an internal storage (planned for later). Yes, I know that there are much cheaper and easier solutions for this task, but where is the fun with these? Processing costs power. Audio output costs power: you may be stuck with an external power fupply to do that much work with any kind of quality.
Re: Suggestion
You wrote: On Sunday 11 March 2012 07:57:35 Nomen Nescio wrote: You wrote: On Friday 09 March 2012 13:10:13 Nomen Nescio wrote: Who in their right mind would EVER want to run this crap? You answered your own question. My guess? People who are too cheap to buy Windows and too stupid to figure out how to find a free copy of XP or Win 7 on the net and do the activation or find a password. That's a pretty small user space. Free copy's of Windows? Do they exist? The point is if you want Windows you have two ways of getting it. You can buy a copy or rip one off. Got it now? Either one runs better than FreactOS It was a retoriocal question? Got it now? No and I don't think you do either. Did you mean it was a sarcastic question? If so, I got it. My comments were rhetorical, yours may have been sarcasm but I didn't get it ;-)
Strange sshd + /etc/nologin behaviour
Hello, I'm running current OpenBSD 5.1-current (GENERIC) #2: Fri Mar 9 18:02:19 CET 2012 andre@pc:/usr/src/sys/arch/amd64/compile/GENERIC and I've noticed some strange things when logging in through ssh. The sshd(8) manpage says for a login that it: checks /etc/nologin; if it exists, prints contents and quits (unless root). I have the following users: uid=0(root) gid=0(wheel) groups=0(wheel), 2(kmem), 3(sys), 4(tty), 5(operator), 20(staff), 31(guest) uid=1000(andre) gid=1000(andre) groups=1000(andre), 0(wheel) uid=1001(test) gid=1001(test) groups=1001(test) The file /etc/nologin exists and is world-readable. When PermitRootLogin is set to yes then: root: access is denied, /etc/nologin gets printed andre: has access test: access is denied, nothing gets printed Here I'd expect that only root has access. Everyone else gets the contents of /etc/nologin and will be disconnected. When PermitRootLogin is set to no root: access is denied, nothing gets printed andre: has access test: access is denied, nothing gets printed Here I'd expect that at least the user test gets the contents of /etc/nologin and will be disconnected. I don't know if it makes a difference when a user is in the group wheel, if not then the user andre should be disconnected, too. Am I missing something? Thanks a lot AndrC)
SSH, root can repeat commands with up arrow, others cannot
This started for me a while back. Login as root, I can repeat older commands with up down arrows. History command shows history. su -l otheruser Cannot use up down arrows to access history. History command shows correct history. Login remotely as otheruser. Same problem. Chris Bennett
Which automake and autoconfig versions to compile NTOP v4?
Hi, I'm trying to compile the latest NTOP version 4.1.0 on OpenBSD RELEASE 5.0 x64 but am running into issues regarding automake and autoconfig. Basically I installed: automake-1.11.1p2 autoconf-2.67 The install script comes up saying this: # ./autogen.sh Starting ntop automatic configuration system v.0.2.3 Please be patient, there is a lot to do... 1. Testing gnu tools You must have automake installed to compile ntop. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/automake We recommend version 1.6.3 or higher You must have autoconf installed to compile autogen.sh. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/autoconf We recommend version 2.53 or higher It's weird because both packages are installed and have confirmed that running: find / -name auto(conf and make). Can anyone suggest anything? I'm actually puzzled as to why the Ntop version on the public FTP servers are s old and out of date, I mean v1.x? With that there's no Web GUI and actually works more like some of the other cli packet sniffers am used to such as trafshow, jnettop, iptraf-ng etc.. It would be so awsome to see these on the FTP servers so that all one needs to do is just pkg_add them but am stuck now compiling and not sure if it's even gona work Regards, Kaya
Re: SSH, root can repeat commands with up arrow, others cannot
On 03/11/12 20:43, Chris Bennett wrote: This started for me a while back. Login as root, I can repeat older commands with up down arrows. History command shows history. su -l otheruser Cannot use up down arrows to access history. History command shows correct history. Login remotely as otheruser. Same problem. Chris Bennett check the HISTFILE variable in the shell. probably set in /root/.profile or any of the likes. /Alexander
Re: SSH, root can repeat commands with up arrow, others cannot
On Sun, Mar 11, 2012 at 12:43 PM, Chris Bennett ch...@bennettconstruction.us wrote: This started for me a while back. Login as root, I can repeat older commands with up down arrows. History command shows history. su -l otheruser Cannot use up down arrows to access history. History command shows correct history. Login remotely as otheruser. Same problem. Chris Bennett What shell are you using for the users and root? ksh? do you have HISTORY set for root? --patrick
Re: SSH, root can repeat commands with up arrow, others cannot
On Sun, Mar 11, 2012 at 02:43:42PM -0500, Chris Bennett wrote: This started for me a while back. Login as root, I can repeat older commands with up down arrows. History command shows history. su -l otheruser Cannot use up down arrows to access history. History command shows correct history. You most likely set EDITOR to something containing vi. ksh parses that and switches to vi mode. IMO it's a disgusting feature, but that appears to be just me. set -o emacs set +o vi Login remotely as otheruser. Same problem. Chris Bennett
Re: Strange sshd + /etc/nologin behaviour
On Sun, Mar 11, 2012 at 08:21:10PM +0100, Andr?? S. wrote: Am I missing something? Is your user in the staff class? It has ignorenologin set by default. See login.conf(5) and /etc/login.conf.
Re: Which automake and autoconfig versions to compile NTOP v4?
Kaya Saman wrote: Hi, I'm trying to compile the latest NTOP version 4.1.0 on OpenBSD RELEASE 5.0 x64 but am running into issues regarding automake and autoconfig. Basically I installed: automake-1.11.1p2 autoconf-2.67 The install script comes up saying this: # ./autogen.sh Starting ntop automatic configuration system v.0.2.3 Please be patient, there is a lot to do... 1. Testing gnu tools You must have automake installed to compile ntop. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/automake We recommend version 1.6.3 or higher You must have autoconf installed to compile autogen.sh. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/autoconf We recommend version 2.53 or higher It's weird because both packages are installed and have confirmed that running: find / -name auto(conf and make). Can anyone suggest anything? try: automake --version autoconf --version The messages should be self-explanatory if you didn't define certain environment variables, e.g., I have this in my environment: $ set |grep AUTO AUTOCONF_VERSION=2.65 AUTOMAKE_VERSION=1.11
Re: SSH, root can repeat commands with up arrow, others cannot
On Sun, Mar 11, 2012 at 3:32 PM, Tobias Ulmer tobi...@tmux.org wrote: On Sun, Mar 11, 2012 at 02:43:42PM -0500, Chris Bennett wrote: This started for me a while back. Login as root, I can repeat older commands with up down arrows. History command shows history. su -l otheruser Cannot use up down arrows to access history. History command shows correct history. You most likely set EDITOR to something containing vi. ksh parses that and switches to vi mode. IMO it's a disgusting feature, but that appears to be just me. set -o emacs set +o vi after `set -o emacs`, the final line is redundant Login remotely as otheruser. Same problem. Chris Bennett
Re: Which automake and autoconfig versions to compile NTOP v4?
On 03/11/2012 08:10 PM, Remco wrote: Kaya Saman wrote: Hi, I'm trying to compile the latest NTOP version 4.1.0 on OpenBSD RELEASE 5.0 x64 but am running into issues regarding automake and autoconfig. Basically I installed: automake-1.11.1p2 autoconf-2.67 The install script comes up saying this: # ./autogen.sh Starting ntop automatic configuration system v.0.2.3 Please be patient, there is a lot to do... 1. Testing gnu tools You must have automake installed to compile ntop. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/automake We recommend version 1.6.3 or higher You must have autoconf installed to compile autogen.sh. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/autoconf We recommend version 2.53 or higher It's weird because both packages are installed and have confirmed that running: find / -name auto(conf and make). Can anyone suggest anything? try: automake --version autoconf --version The messages should be self-explanatory if you didn't define certain environment variables, e.g., I have this in my environment: $ set |grep AUTO AUTOCONF_VERSION=2.65 AUTOMAKE_VERSION=1.11 automake --version autoconf --version come up with this # automake --version Provide an AUTOMAKE_VERSION environment variable, please # autoconf --version Provide an AUTOCONF_VERSION environment variable, please ?? set |grep AUTO also doesn't display anything??? However, the packages are installed in /usr/local/bin which is confirmed using **find** actually just seeing this now it turns out that automake is proceeded by a version number. So it works then I guess but why can't Ntop install script pick it out?
Re: Which automake and autoconfig versions to compile NTOP v4?
On Sun, Mar 11, 2012 at 07:42:43PM +, Kaya Saman wrote: Hi, I'm trying to compile the latest NTOP version 4.1.0 on OpenBSD RELEASE 5.0 x64 but am running into issues regarding automake and autoconfig. Basically I installed: automake-1.11.1p2 autoconf-2.67 The install script comes up saying this: # ./autogen.sh Starting ntop automatic configuration system v.0.2.3 Please be patient, there is a lot to do... 1. Testing gnu tools You must have automake installed to compile ntop. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/automake We recommend version 1.6.3 or higher You must have autoconf installed to compile autogen.sh. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/autoconf We recommend version 2.53 or higher See how the metaauto port works. autoconf and automake are actually scripts that depend on AUTOCONF_VERSION and AUTOMAKE_VERSION to select the right ones.
Re: Which automake and autoconfig versions to compile NTOP v4?
On 03/11/2012 08:20 PM, Marc Espie wrote: On Sun, Mar 11, 2012 at 07:42:43PM +, Kaya Saman wrote: Hi, I'm trying to compile the latest NTOP version 4.1.0 on OpenBSD RELEASE 5.0 x64 but am running into issues regarding automake and autoconfig. Basically I installed: automake-1.11.1p2 autoconf-2.67 The install script comes up saying this: # ./autogen.sh Starting ntop automatic configuration system v.0.2.3 Please be patient, there is a lot to do... 1. Testing gnu tools You must have automake installed to compile ntop. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/automake We recommend version 1.6.3 or higher You must have autoconf installed to compile autogen.sh. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/autoconf We recommend version 2.53 or higher See how the metaauto port works. autoconf and automake are actually scripts that depend on AUTOCONF_VERSION and AUTOMAKE_VERSION to select the right ones. Ok thankyou! .this makes sense now to me. But how to set AUTOCONF_VERSION and AUTOMAKE_VERSION??? You say metaauto port but I thought that in OpenBSD one was not supposed to used ports unlike FreeBSD which I'm used to? hmm # man metaauto man: no entry for metaauto in the manual. looks like I need to do some further Google'ing! Regards, Kaya
Re: Strange sshd + /etc/nologin behaviour
Alexander Schrijver wrote: Is your user in the staff class? It has ignorenologin set by default. See login.conf(5) and /etc/login.conf. Thanks a lot for the point, Alexander. User andre is in the staff class, so this explains why andre has always access. I still don't understand the /etc/nologin-strangeness... why is root access denied, wenn PermitRootLogin is yes and /etc/nologin exists? why are the /etc/nologin contents not printed (neither to root nor to test) when PermitRootLogin is no? Andre
Re: Which automake and autoconfig versions to compile NTOP v4?
On 03/11/2012 08:20 PM, Marc Espie wrote: On Sun, Mar 11, 2012 at 07:42:43PM +, Kaya Saman wrote: Hi, I'm trying to compile the latest NTOP version 4.1.0 on OpenBSD RELEASE 5.0 x64 but am running into issues regarding automake and autoconfig. Basically I installed: automake-1.11.1p2 autoconf-2.67 The install script comes up saying this: # ./autogen.sh Starting ntop automatic configuration system v.0.2.3 Please be patient, there is a lot to do... 1. Testing gnu tools You must have automake installed to compile ntop. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/automake We recommend version 1.6.3 or higher You must have autoconf installed to compile autogen.sh. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/autoconf We recommend version 2.53 or higher See how the metaauto port works. autoconf and automake are actually scripts that depend on AUTOCONF_VERSION and AUTOMAKE_VERSION to select the right ones. Well in mean time I found this: http://openports.se/devel/metaauto although I don't think it's installed as **find** didn't come up with anything. Does this mean that without the metaauto port that the **system** or **any** install script will not know how to handle a basic compile? Am really confused now as I don't understand anything of what's going on! This might be an easier to answer question then: how do I tell the system to use one particular version of autoconf and automake...??? Which files do I need to edit to do that? Am so sorry for being slow but am just so used to running: cd /usr/ports/*/portname make install clean and everything being done in the background for me! Regards, Kaya
Re: Which automake and autoconfig versions to compile NTOP v4?
On 03/11/2012 08:20 PM, Marc Espie wrote: On Sun, Mar 11, 2012 at 07:42:43PM +, Kaya Saman wrote: Hi, I'm trying to compile the latest NTOP version 4.1.0 on OpenBSD RELEASE 5.0 x64 but am running into issues regarding automake and autoconfig. Basically I installed: automake-1.11.1p2 autoconf-2.67 The install script comes up saying this: # ./autogen.sh Starting ntop automatic configuration system v.0.2.3 Please be patient, there is a lot to do... 1. Testing gnu tools You must have automake installed to compile ntop. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/automake We recommend version 1.6.3 or higher You must have autoconf installed to compile autogen.sh. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/autoconf We recommend version 2.53 or higher See how the metaauto port works. autoconf and automake are actually scripts that depend on AUTOCONF_VERSION and AUTOMAKE_VERSION to select the right ones. Well I actually sort-of figured this out but turned out to be a very messy hack and probably have broken other things. meaning am totally not sure of the implications of my actions! I basically moved the autoconf and automake scripts to files called auto*.scr, then symlinked the highest versions of each software to automake and autoconf respectively. i have no idea down-the-line if this will break anything but for now it works :-) Regards, Kaya
Re: Snappy Answers to Stupid Questions - WTF?
Theo never smiles. Not once. He smiles even when Linux people around https://farm1.staticflickr.com/184/465686613_9ca10e9768_o.jpg I'm still waiting for the cage grudge match between Theo and Linus. My money is on Theo by the way
Re: SSH, root can repeat commands with up arrow, others cannot
On Sun, Mar 11, 2012 at 09:02:58PM +0100, Tobias Ulmer wrote: You most likely set EDITOR to something containing vi. ksh parses that and switches to vi mode. IMO it's a disgusting feature, but that appears to be just me. Wow, that is a disgusting pile of crap! alias mutt='env EDITOR=vim mutt' does the trick. Thanks! Chris Bennett
Re: Which automake and autoconfig versions to compile NTOP v4?
On Sun, Mar 11, 2012, Kaya Saman wrote: try: automake --version autoconf --version The messages should be self-explanatory if you didn't define certain environment variables, e.g., I have this in my environment: automake --version autoconf --version come up with this # automake --version Provide an AUTOMAKE_VERSION environment variable, please # autoconf --version Provide an AUTOCONF_VERSION environment variable, please How are those messages not self explanatory? Did you read them?
Re: Which automake and autoconfig versions to compile NTOP v4?
On 03/11/2012 10:34 PM, Ted Unangst wrote:
On Sun, Mar 11, 2012, Kaya Saman wrote:
try: automake --version
autoconf --version
The messages should be self-explanatory if you didn't define certain
environment variables, e.g., I have this in my environment:
automake --version
autoconf --version
come up with this
# automake --version
Provide an AUTOMAKE_VERSION environment variable, please
# autoconf --version
Provide an AUTOCONF_VERSION environment variable, please
How are those messages not self explanatory? Did you read them?
Sure I read them it's a bit difficult not to!
I also managed to get round them by providing the versions:
eg. automake-1.11 --version
my issue was how to get the Ntop config script to understand that
automake and autoconf **are** installed on the system!!!
Luckily a friendly person did explain that I should first **export** the
versions then run the config gen script which indeed worked!!!
export AUTOMAKE_VERSION=1.11 AUTOCONF_VERSION=2.67
However, please note that am still learning OpenBSD after coming over
from Linux and FreeBSD and additionally I am NOT a programmer or even
good at programming
My main base in fact is network engineering so forgive me if I don't
know the intricate details of the OpenBSD OS
Using FreeBSD I would just do this:
cd /usr/ports/*/ntop
make install clean
and providing my **ports** tree is uptodate it will work flawlessly.
Additionally on Linux for RPM based would be yum install ntop or DEB
based would be apt-get install ntop
Now I do know these without even needing to read the documentation...
however even **IF** I tried to compile on one of those platforms which I
do all the time I never need to adjust system variables or tell the
configure script what compiler or other I'm using as it is intelligent
enough to autodetect it.
I understand OpenBSD is different and I'm trying to get used to it but
please cut new users some slack as not everyone is God's gift to
computing... {I don't say this as an attack or with any bad
intentions just frustration at how unforgiving this list is sometimes}
Regards,
Kaya
Unknown error: code 60 installing OpenBSD/macppc in iMac G3
Hi misc@, tired of using these crap CD-ROM units, I've decided to give it a try booting from a TFTP server, to install OpenBSD/macppc on one of the iMacs I have here. I configured tftpd running on a OpenBSD/amd64 machine according to section 6.10 of the FAQ, with the needed files. So, here is what I have: 0 boot enet:,ofwboot /bsd.rd CLIENT: 000a27d6afae 192.168.1.32 SERVER: 001b242e5ce6 192.168.1.7 Transfer FILE ofwboot \ TFTP-actual=fe88 TFTP-adler32=2e938515 load-size=fe88 adler32=2e938515 Loading ELF OpenBSD/macppc BOOT 1.2 open(/pci@f400/ethernet:/etc/boot.conf): Unknown error: code 60 boot After this, the same error repeats trying /bsd.rd, /bsd, etc. Anyone has any clues on this? I really don't want to ever touch an optical driver again. Thank you.
Re: Unknown error: code 60 installing OpenBSD/macppc in iMac G3
tired of using these crap CD-ROM units, I've decided to give it a try booting from a TFTP server, to install OpenBSD/macppc on one of the iMacs I have here. I configured tftpd running on a OpenBSD/amd64 machine according to section 6.10 of the FAQ, with the needed files. So, here is what I have: 0 boot enet:,ofwboot /bsd.rd CLIENT: 000a27d6afae 192.168.1.32 SERVER: 001b242e5ce6 192.168.1.7 Transfer FILE ofwboot \ TFTP-actual=fe88 TFTP-adler32=2e938515 load-size=fe88 adler32=2e938515 Loading ELF OpenBSD/macppc BOOT 1.2 open(/pci@f400/ethernet:/etc/boot.conf): Unknown error: code 60 boot After this, the same error repeats trying /bsd.rd, /bsd, etc. Anyone has any clues on this? I really don't want to ever touch an optical driver again. In almost all cases where we print an error number, it is an errno from /sys/sys/errno.h. We'd print it by the prober name for the error, but there is no room on the bootblocks for that table. Here's the error: #define ETIMEDOUT 60 /* Operation timed out */ Likely this means that you have not setup some service that the bootloader needs for filesystem access. Different bootloaders have different network file system requirements -- check diskless(8) for more information.
Re: Which automake and autoconfig versions to compile NTOP v4?
On Sun, Mar 11, 2012 at 10:48:24PM +, Kaya Saman wrote:
On 03/11/2012 10:34 PM, Ted Unangst wrote:
On Sun, Mar 11, 2012, Kaya Saman wrote:
try: automake --version
autoconf --version
The messages should be self-explanatory if you didn't define certain
environment variables, e.g., I have this in my environment:
automake --version
autoconf --version
come up with this
# automake --version
Provide an AUTOMAKE_VERSION environment variable, please
# autoconf --version
Provide an AUTOCONF_VERSION environment variable, please
How are those messages not self explanatory? Did you read them?
Sure I read them it's a bit difficult not to!
I also managed to get round them by providing the versions:
eg. automake-1.11 --version
my issue was how to get the Ntop config script to understand that
automake and autoconf **are** installed on the system!!!
Luckily a friendly person did explain that I should first **export** the
versions then run the config gen script which indeed worked!!!
That's what providing the environment variable means.
export AUTOMAKE_VERSION=1.11 AUTOCONF_VERSION=2.67
However, please note that am still learning OpenBSD after coming over
from Linux and FreeBSD and additionally I am NOT a programmer or even
good at programming
One exclamation point is enough.
My main base in fact is network engineering so forgive me if I don't
know the intricate details of the OpenBSD OS
Those are not intricate details. Environment variables exist in virtually every
operating system available.
Using FreeBSD I would just do this:
cd /usr/ports/*/ntop
make install clean
and providing my **ports** tree is uptodate it will work flawlessly.
Additionally on Linux for RPM based would be yum install ntop or DEB
based would be apt-get install ntop
Great story.
Now I do know these without even needing to read the documentation...
however even **IF** I tried to compile on one of those platforms which I
do all the time I never need to adjust system variables or tell the
configure script what compiler or other I'm using as it is intelligent
enough to autodetect it.
The configure script is not part of the operating system, it is part of the
package/tarball, if you're using something that needs automake/autoconf you're
probably checking out development versions of software and then complaining to
the OS developers who have nothing to do with it.
I understand OpenBSD is different and I'm trying to get used to it but
please cut new users some slack as not everyone is God's gift to
computing... {I don't say this as an attack or with any bad
intentions just frustration at how unforgiving this list is sometimes}
I love this list for that.
Regards,
Kaya
Regards
Hektor Oksenberg
Re: Which automake and autoconfig versions to compile NTOP v4?
On 03/12/2012 12:21 AM, hex wrote:
On Sun, Mar 11, 2012 at 10:48:24PM +, Kaya Saman wrote:
On 03/11/2012 10:34 PM, Ted Unangst wrote:
On Sun, Mar 11, 2012, Kaya Saman wrote:
try: automake --version
autoconf --version
The messages should be self-explanatory if you didn't define certain
environment variables, e.g., I have this in my environment:
automake --version
autoconf --version
come up with this
# automake --version
Provide an AUTOMAKE_VERSION environment variable, please
# autoconf --version
Provide an AUTOCONF_VERSION environment variable, please
How are those messages not self explanatory? Did you read them?
Sure I read them it's a bit difficult not to!
I also managed to get round them by providing the versions:
eg. automake-1.11 --version
my issue was how to get the Ntop config script to understand that
automake and autoconf **are** installed on the system!!!
Luckily a friendly person did explain that I should first **export** the
versions then run the config gen script which indeed worked!!!
That's what providing the environment variable means.
I didn't know that so thanks for pointing that out.
export AUTOMAKE_VERSION=1.11 AUTOCONF_VERSION=2.67
However, please note that am still learning OpenBSD after coming over
from Linux and FreeBSD and additionally I am NOT a programmer or even
good at programming
One exclamation point is enough.
Sorry frustration got the better of me!
My main base in fact is network engineering so forgive me if I don't
know the intricate details of the OpenBSD OS
Those are not intricate details. Environment variables exist in virtually every
operating system available.
I do understand that compiling software is part of UNIX and I accept
that I don't know enough about it but the other types of OS's stated all
work without issues which ok is not the OS fault, rather that
software is mostly being designed for Linux and a really great effort to
**port** the stuff is being done by FreeBSD. But without knowing the
characteristics of an OS it's very difficult to debug issues if one
doesn't understand how it handles certain things.
Using FreeBSD I would just do this:
cd /usr/ports/*/ntop
make install clean
and providing my **ports** tree is uptodate it will work flawlessly.
Additionally on Linux for RPM based would be yum install ntop or DEB
based would be apt-get install ntop
Great story.
Uh sorry was just trying to stress or rather emphasize my point. I
think eventually the only thing that got stressed was me :-(
Now I do know these without even needing to read the documentation...
however even **IF** I tried to compile on one of those platforms which I
do all the time I never need to adjust system variables or tell the
configure script what compiler or other I'm using as it is intelligent
enough to autodetect it.
The configure script is not part of the operating system, it is part of the
package/tarball, if you're using something that needs automake/autoconf you're
probably checking out development versions of software and then complaining to
the OS developers who have nothing to do with it.
Erm I wasn't complaining. I just needed a hand to figure out how to
get the script to interact with the OS. Now it's time to take my case to
the Ntop team as the script is blocking me claiming unsupported OS.
True though it maybe I would still like to get Ntop (the current
version) working on OpenBSD as unfortunately it's not available natively.
I understand OpenBSD is different and I'm trying to get used to it but
please cut new users some slack as not everyone is God's gift to
computing... {I don't say this as an attack or with any bad
intentions just frustration at how unforgiving this list is sometimes}
I love this list for that.
Uh! :-(
Would it not just be easier and cleaner to create a new list for
newbies? That way the more advanced stuff could be taken care of on this
list and only people willing to help others could post useful comments
and help on the other list.
.actually this list may become really quiet then??? As in all of my
1 week being here not much help goes on just arguments and flames.
Regards
Hektor Oksenberg
Regards,
--K
dmesg mac mini A1347
Hi, hw.sensors.cpu0.temp0=53.00 degC Here the dmesg running OpenBSD 5.0 RELEASE: OpenBSD 5.0 (GENERIC.MP) #59: Wed Aug 17 10:19:44 MDT 2011 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP RTC BIOS diagnostic error 34config_unit,memory_size,invalid_time cpu0: Intel(R) Core(TM)2 Duo CPU P8600 @ 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,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE real mem = 2942947328 (2806MB) avail mem = 2884734976 (2751MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 07/29/05, SMBIOS rev. 2.4 @ 0xe (44 entries) bios0: vendor Apple Inc. version MM41.88Z.0042.B00.1004221740 date 04/22/10 bios0: Apple Inc. Macmini4,1 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET APIC APIC ASF! SBST ECDT SSDT SSDT MCFG SSDT SSDT acpi0: wakeup devices EC__(S3) OHC1(S3) EHC1(S3) OHC2(S3) EHC2(S3) ARPT(S5) GIGE(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 2500 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 265MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz (GenuineIntel 686-class) 2.39 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE ioapic0 at mainbus0: apid 1 pa 0xfec0, version 11, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 1 acpiec0 at acpi0 acpimcfg0 at acpi0 addr 0xf000, bus 0-5 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 5 (IXVE) acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: SLPB bios0: ROM list: 0xc/0xe400! cpu0: Enhanced SpeedStep 2390 MHz: speeds: 2394, 2128, 1862, 1596 MHz memory map conflict 0xffc0/0x40 pci0 at mainbus0 bus 0: configuration mode 1 (bios) mem address conflict 0xd350/0x8 pchb0 at pci0 dev 0 function 0 NVIDIA MCP89 Host rev 0xa1 NVIDIA MCP89 Memory rev 0xa1 at pci0 dev 0 function 1 not configured vendor NVIDIA, unknown product 0x0d6d (class memory subclass RAM, rev 0xa1) at pci0 dev 1 function 0 not configured vendor NVIDIA, unknown product 0x0d6e (class memory subclass RAM, rev 0xa1) at pci0 dev 1 function 1 not configured vendor NVIDIA, unknown product 0x0d6f (class memory subclass RAM, rev 0xa1) at pci0 dev 1 function 2 not configured vendor NVIDIA, unknown product 0x0d70 (class memory subclass RAM, rev 0xa1) at pci0 dev 1 function 3 not configured vendor NVIDIA, unknown product 0x0d71 (class memory subclass RAM, rev 0xa1) at pci0 dev 2 function 0 not configured vendor NVIDIA, unknown product 0x0d72 (class memory subclass RAM, rev 0xa1) at pci0 dev 2 function 1 not configured pcib0 at pci0 dev 3 function 0 NVIDIA MCP89 LPC rev 0xa2 NVIDIA MCP89 Memory rev 0xa1 at pci0 dev 3 function 1 not configured NVIDIA MCP89 SMBus rev 0xa1 at pci0 dev 3 function 2 not configured NVIDIA MCP89 Memory rev 0xa1 at pci0 dev 3 function 3 not configured NVIDIA MCP89 Co-processor rev 0xa1 at pci0 dev 3 function 4 not configured ohci0 at pci0 dev 4 function 0 NVIDIA MCP89 USB rev 0xa1: apic 1 int 11, version 1.0, legacy support ehci0 at pci0 dev 4 function 1 NVIDIA MCP89 USB rev 0xa2: apic 1 int 10 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 NVIDIA EHCI root hub rev 2.00/1.00 addr 1 ohci1 at pci0 dev 6 function 0 NVIDIA MCP89 USB rev 0xa1: apic 1 int 7, version 1.0, legacy support ehci1 at pci0 dev 6 function 1 NVIDIA MCP89 USB rev 0xa2: apic 1 int 5 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 NVIDIA EHCI root hub rev 2.00/1.00 addr 1 azalia0 at pci0 dev 8 function 0 NVIDIA MCP89 HD Audio rev 0xa2: msi azalia0: codecs: Cirrus Logic/0x4206, NVIDIA/0x000c, NVIDIA/0x000c, NVIDIA/0x000c, using Cirrus Logic/0x4206 audio0 at azalia0 pciide0 at pci0 dev 10 function 0 NVIDIA MCP89 SATA rev 0xa2: DMA pciide0: using apic 1 int 11 for native-PCI interrupt wd0 at pciide0 channel 0 drive 0: TOSHIBA MK3255GSXF wd0: 16-sector PIO, LBA48, 305245MB, 625142448 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: HL-DT-ST, DVDRW GA32N, KC08 ATAPI 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 5 vendor NVIDIA, unknown product 0x0d75 (class memory subclass RAM, rev 0xa1) at pci0 dev 11 function 0 not configured ppb0 at pci0 dev 14 function 0 NVIDIA MCP89 PCIE rev 0xa1: apic 1 int 16 pci1 at ppb0 bus 1 ppb1 at pci1 dev 0 function 0 vendor TI, unknown product 0x823e rev 0x01 pci2 at ppb1 bus 2 vendor TI, unknown product 0x823f (class serial bus subclass Firewire, rev 0x01) at pci2 dev 0 function 0 not configured ppb2 at pci0 dev 21 function 0 NVIDIA MCP89 PCIE
