Re: Help
Hi, part 2 and 3 will help you. http://www.openbsd.org/mail.html On Sun, Dec 20, 2009 at 5:57 AM, A.I. wrote: > Hi > > I am OpenBSD user. I have new computer AMD 4 core + 16G ram . I install > OpenBSD amd 64bit 4.6 version . I find out openbsd work with 2.6G ram by > dmesg. How to let OpenBSD work with 16G Ram. > > Suen > > -- http://www.openbsd.org/lyrics.html
Re: Help
On Sat, 19 Dec 2009 20:57:54 -0800 (PST) "A.I." wrote: > Hi > > I am OpenBSD user. I have new computer AMD 4 core + 16G ram . I > install OpenBSD amd 64bit 4.6 version . I find out openbsd work with > 2.6G ram by dmesg. How to let OpenBSD work with 16G Ram. > > Suen Very descriptiv subject you have there. :) OpenBSD by default behaves like other 32bit os in regards to addressable memory. The keyword you are looking for is "bigmem". You will have to recompile your kernel with that option set to _try_ if it works for you. It does not work in every case, that's why it isn't enabled by default. Read up on it, give it a try, report back and include a dmesg. :) - Robert
Re: Help
On 12/20/09, A.I. wrote: > Hi > > I am OpenBSD user. I have new computer AMD 4 core + 16G ram . I install > OpenBSD amd 64bit 4.6 version . I find out openbsd work with 2.6G ram by > dmesg. How to let OpenBSD work with 16G Ram. > > Suen The following thread should help: http://marc.info/?t=12456707794&r=1&w=2 Fred
Help
Hi I am OpenBSD user. I have new computer AMD 4 core + 16G ram . I install OpenBSD amd 64bit 4.6 version . I find out openbsd work with 2.6G ram by dmesg. How to let OpenBSD work with 16G Ram. Suen
Re: vi in /bin
On Sat, 19 Dec 2009 23:17 -0600, "Adam Thompson" wrote: > In article <20091219090128.gb...@bramka.kerhand.co.uk>, > j...@kerhand.co.uk says... > > > "braw wee editor" means "small, but fine editor"? Because then you > > yes, it really means "a great little editor". although putting "great" > > and "little" together sounds all wrong. > > anyway, i was drunk when i wrote that. otherwise i would have ignored > > this stupid thread. > > jmc > > Och, ye were nae twa sott'd t'ave spake false; the highlands are a- > bursting wi' braw wee tykes. Now, if we cannae but ken a plan to have > them all using OpenBSD by the time they've grown... > > > (Yes, the thread just got even stupider :-) > When are the Scots not drunk? (says I who is Irish/German) (speaking of such, I need to go get drunk now) (stupider and stupider) :)
Re: vi in /bin
In article <20091219122141.5ce04...@poof.my.domain>, eagir...@cox.net says... > > Ingo Schwarze wrote on Sat., Dec. 19 at 17:51:19 > > >Matthew Szudzik wrote on Sat, Dec 19, 2009 at 05:34:23PM +: > > > >> But if you're going to learn just one of them, then I vote for sed. > > > >Marc, rewrite pkg* in sed. Please... :) > > Herr Schwarze, please get help before you injure yourself or someone > else. ;-) Well, there's really no reason the entire pkg_* system couldn't be accomplished with pure Bourne Shell syntax (or, god forbid, csh syntax - after all, it did originate at UCB wtih 2BSD) with a little bit of helper awk and sed embedded in it. Of course, it would probably be nearly unmaintainable, and quite possibly significantly slower and more memory-hungry than what we have now, but I seriously doubt that it would cause any actual injuries. (Mental and emotional injury aside, obviously.) :-) -Adam
Re: vi in /bin
In article <20091219090128.gb...@bramka.kerhand.co.uk>, j...@kerhand.co.uk says... > > "braw wee editor" means "small, but fine editor"? Because then you > yes, it really means "a great little editor". although putting "great" > and "little" together sounds all wrong. > anyway, i was drunk when i wrote that. otherwise i would have ignored > this stupid thread. > jmc Och, ye were nae twa sott'd t'ave spake false; the highlands are a- bursting wi' braw wee tykes. Now, if we cannae but ken a plan to have them all using OpenBSD by the time they've grown... (Yes, the thread just got even stupider :-)
Re: OT: Python (was Re: vi in /bin)
On Sat, Dec 19, 2009 at 4:00 PM, Marco Peereboom wrote: > > There is no limit to shit code produced by amateurs and "professionals". Out of this whole thread this is the only statement I agree with completely.
Re: OT: Python (was Re: vi in /bin)
On Sat, Dec 19, 2009 at 06:00:14PM -0600, Marco Peereboom wrote: > ... > > Really? then why do you use scrotwm? Because it kicks the balls out of every other wm.
Re: OT: Python (was Re: vi in /bin)
On Sat, Dec 19, 2009 at 03:18:55PM -0500, Ryan Flannery wrote: > On Sat, Dec 19, 2009 at 2:51 PM, Nick Guenther wrote: > > Python is about thinking about what you're doing. It's one of those > > languages that forces you to work on a higher level (not that there > > aren't lots of places where python is used as a scripting > > language--that code tends to come out badly, but that's because it's > > written just to get the job done). > > > > Ideal code is abstracted code, what possible use does repeating > > yourself in the tree have? I know drivers have to declare a common set > > of globals and make some macro calls and various entry-points are > > found by sticking to a naming scheme, but that's trivia, hardly enough > > to justify "valid uses for copied code". Anytime I find myself wanting > > to copy some code it's always meant I've stumbled over an abstraction > > I haven't made yet, so what in the world is src/ doing that -requires- > > copied code? > > I must disagree here... there's nothing about *any* programming > language [1] that forces one to work on a higher level. That's up to > the programmer. I've seen even the simplest tasks, or ones that > scream for a nice, simple abstraction, done horribly (if at all) in > any language, including python. My experience grading countless > programs from freshman-senior students, which are increasingly written > in python, show it's not the programming language... it's the > programmer. There is no limit to shit code produced by amateurs and "professionals". Python suffers from the same lib catastrophe that java has. > > Good design + good coding practices + tons-o-work forces one to think > more and come up with a better design, not the language. > > -ryan > > [1] except of course for Haskell, the ONE TRUE GOD of proper programming :P Really? then why do you use scrotwm?
Re: OT: Python (was Re: vi in /bin)
On Sat, Dec 19, 2009 at 02:51:32PM -0500, Nick Guenther wrote: > and just to add to the pyre... > > On Sat, Dec 19, 2009 at 8:38 AM, Claudio Jeker > wrote: > > > > Ugh, a programming language where you can't copy paste from xterm to xterm > > without fucking up the program is just way to much pain to work on. > > > >On Sat, Dec 19, 2009 at 10:03 AM, Ted Unangst wrote: > > for many people who are a little suspicious of the whole > > whitespace thing, when your first taste of the language is hours spent > > fixing the whitespace, you aren't inclined to use it any more than > > necessary. > > Your losses then. Python isn't so much a language of recipes, it's a > language of ideas. Bwahahahahaha! ok that is the funniest thing I heard in a couple of days. Thanks for the laugh. > > On Sat, Dec 19, 2009 at 2:06 PM, Henning Brauer wrote: > > * Floor Terra [2009-12-19 19:10]: > >> > >> In my experience (mostly python and c), code that has been pasted has > >> a higher bug density. > >> > >> It's worse with Python because of the indentation (tabs vs. spaces), > >> but as a general rule I would say never copy/paste code. > > > > boo hoo. > > > > there are very valid uses of copied code, or extremely similiar code > > (copy & paste and change a few things). we have that many times in the > > tree. > > Python is about thinking about what you're doing. It's one of those > languages that forces you to work on a higher level (not that there > aren't lots of places where python is used as a scripting > language--that code tends to come out badly, but that's because it's > written just to get the job done). So when I am writing some sort of wire protocol I am not thinking about what I am doing? C isn't that forgiving. > > Ideal code is abstracted code, what possible use does repeating > yourself in the tree have? I know drivers have to declare a common set > of globals and make some macro calls and various entry-points are > found by sticking to a naming scheme, but that's trivia, hardly enough > to justify "valid uses for copied code". Anytime I find myself wanting > to copy some code it's always meant I've stumbled over an abstraction > I haven't made yet, so what in the world is src/ doing that -requires- > copied code? Abstracted code is usually gratuitously complex for no other reason than abstraction. Abstraction is useful when used in its problem domain. It is hell on earth when it isn't. > > -Nick
Re: OT: Python (was Re: vi in /bin)
On Sat, Dec 19, 2009 at 04:37:08PM +0100, Floor Terra wrote: > On Sat, Dec 19, 2009 at 2:38 PM, Claudio Jeker > wrote: > > Ugh, a programming language where you can't copy paste from xterm to xterm > > without fucking up the program is just way to much pain to work on. > > I agree that copy/paste is a big problem in Python. > But in my experience copy/paste of code in any language is dangerous. > If you want to re-use code, write a function. If you're copying and pasting, you're probably doing something wrong. If it's a small example that you're using as a tutorial or as inspiration to understand how something works, you probably should type it. By typing it the information makes another pass through your brain which can improve comprehension. If it's large and part of something functional, it should have been in a tarball or under source control and there shouldn't be any copy/paste. If your coding style involves a lot of copy and paste, you're repeating yourself and probably should not do that. With that said my python grumbles have been. 1) Developers that refuse to understand the packaging utilities available and how they work with source control systems. 2) Packaging libraries that were written with CVS and subversion in mind that completely break on current versions of subversion. 3) Inattention to detail in libraries. IE the python ldap libraries where results can be retrieved without a message id, but an exception doesn't return the message-id for which it was raised. > > > > -- > Floor Terra > www: http://brobding.mine.nu/ > -- Chris Dukes
Re: devede-3.15.0 problem
On Sat, Dec 19, 2009 at 09:46:23PM +, Jacob Meuser wrote: > On Sat, Dec 19, 2009 at 02:23:17PM -0600, nealHogan wrote: > > > montagueneal# mlayer -loop 1 -identify -ao null -vo null -frames 0 > > /usr/local/share/devede/silence.ogg > > > > Notice that ID_LENGTH is reported as 'inf'. > > hmm. is ogg playback with mplayer broken on amd64? can people with > amd64 try 'mplayer -identify | grep ID_LENGTH' and say > whether it's always "inf"? > A test on another .ogg file: montagueneal mplayer -loop 1 -identify Tromboon-sample.ogg | grep ID_LENGTH > < DEMUX_OGG: header n. 0 broken! len=30, code: -132 DEMUX_OGG: header n. 1 broken! len=140, code: -132 DEMUX_OGG: header n. 2 broken! len=4140, code: -132 ID_LENGTH=inf Compiler did not align stack variables. Libavcodec has been miscompiled and may be very slow or crash. This is not a bug in libavcodec, but in the compiler. You may try recompiling using gcc >= 4.2. Do not report crashes to FFmpeg developers. P.S. -- Sorry about starting this on misc@ . . . habit ;-) I'll be more careful from now on.
symon mbuf on 4.6
Hi, I've just upgraded to 4.6 and symon/symux don't seem to record any mbuf data -- no error messages, there's just nothing in the rrd file. Did I miss something in my configuration? Thanks, Lars
Re: devede-3.15.0 problem
On Sat, Dec 19, 2009 at 02:23:17PM -0600, nealHogan wrote: > montagueneal# mlayer -loop 1 -identify -ao null -vo null -frames 0 > /usr/local/share/devede/silence.ogg > > Notice that ID_LENGTH is reported as 'inf'. hmm. is ogg playback with mplayer broken on amd64? can people with amd64 try 'mplayer -identify | grep ID_LENGTH' and say whether it's always "inf"? -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org
Re: devede-3.15.0 problem
On Sat, Dec 19, 2009 at 01:26:26PM -0600, nealHogan wrote: > FWIW - I had devede working on my amd64 system prior to the upgrade to > 3.15.0. I'm not exactly sure how to deal with devede's suggestion > involving gcc 4.2 (or greater), given that the base compiler is not > that. > > I realize there is a 4.2 pkg, but, again, am unsure what devede would > like me to try. that's mplayer. ignore it. the mplayer port doesn't even build wih gcc4 on x86 anyway. ports/packages issues belong on ports@, btw. -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org
Re: devede-3.15.0 problem
On Sat, Dec 19, 2009 at 07:33:55AM -0600, nealHogan wrote: > Hello, > > The following is the output I get from starting devede and choosing any > one of the disc type options on the initial screen. I just updated to > the latest amd64 snaps and pkgs (17 Dec). > > montagueneal# devede > DeVeDe 3.15.0 > Using package-installed files > /home/neal/ > Entro en fonts > Salgo de fonts > /home/neal/ > Temp Directory is: /var/tmp > home load: /home/neal/.devede > Creating window /usr/local/share/devede/wdisk_type.ui > /usr/local/lib/python2.5/site-packages/devede/devede_other.py:419: > GtkWarning: Could not load image 'devede.svg': Co > tree.add_from_file(filename) > Creating window /usr/local/share/devede/wmain.ui > Launching program: mplayer -loop 1 -identify -ao null -vo null -frames > 0 /usr/local/share/devede/silence.ogg can you run that (mplayer ... devede/silence.ogg) on the command line and paste the output? > elemento: /usr/local/bin > DEMUX_OGG: header n. 0 broken! len=30, code: -132 > DEMUX_OGG: header n. 1 broken! len=73, code: -132 > DEMUX_OGG: header n. 2 broken! len=3437, code: -132 > Traceback (most recent call last): > File > "/usr/local/lib/python2.5/site-packages/devede/devede_disctype.py", line > 71, in on_disctype_dvd > self.set_disk_type() > File > "/usr/local/lib/python2.5/site-packages/devede/devede_disctype.py", line > 101, in set_disk_type > self.main_window=devede_main.main_window(self.global_vars,self.show_again) > File "/usr/local/lib/python2.5/site-packages/devede/devede_main.py", > line 75, in __init__ > self.set_default_global() > File "/usr/local/lib/python2.5/site-packages/devede/devede_main.py", > line 121, in set_default_global > check,channels=test.read_file_values(self.global_vars["menu_sound"],True) > File > "/usr/local/lib/python2.5/site-packages/devede/devede_newfiles.py", line > 138, in read_file_values > length=int(float(linea[10:])) > OverflowError: cannot convert float infinity to long > Compiler did not align stack variables. Libavcodec has been miscompiled > and may be very slow or crash. This is not a bug in libavcodec, > but in the compiler. You may try recompiling using gcc >= 4.2. > Do not report crashes to FFmpeg developers. -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org
Re: OT: Python (was Re: vi in /bin)
On Sat, Dec 19, 2009 at 02:51:32PM -0500, Nick Guenther wrote: > and just to add to the pyre... python sucks because people think it's great. ever try to port a program written in C that uses Scons as it's build system? for me, the C is easy, fixing the damn Scons (python) build scripts is a *royal PITA*. autohell sucks but at least it uses old school UNIX tools as it's backend (shell, awk, sed, perl). -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org
Re: Xorg -br option does not work anymore
On Sat, Dec 19, 2009 at 10:56:59AM -0500, Philippe Meunier wrote: > Hello, > > Xorg's -br option does not seem to work anymore. When I try it I get > the standard X grey pattern on the root window instead of getting > solid black. The option '-nolisten tcp' still works, and I have not > tried to test other options. I noticed the change after upgrading a > desktop PC from 4.5-current to 4.6-current about a month and a half > ago (recompiling OpenBSD and Xenocara from source) and saw the same > change again yesterday when doing the same upgrade using the same > homemade release on a Thinkpad laptop (T43). Can anyone confirm this > or is it just me? I know about 'xsetroot -solid black', I just would > like to know whether this is an Xorg bug or a problem with the way my > machines are configured and / or upgraded. -br is the default now. Some developers don't seem to be pleased with that change, which is why OpenBSD patches it. This breaks -br. http://cgit.freedesktop.org/xorg/xserver/commit/?id=0bb317a78b96fddcdac319c9706b3a12f931ea44 http://www.openbsd.org/cgi-bin/cvsweb/xenocara/xserver/os/utils.c.diff?r1=1.8;r2=1.9;f=h Sending a diff is your job now :) > > $ Xorg -version > [...] > X.Org X Server 1.6.3.901 (1.6.4 RC 1) > Release Date: 2009-8-25 > X Protocol Version 11, Revision 0 > Build Operating System: OpenBSD 4.6 i386 > Current Operating System: OpenBSD akpatok.ungava.bay 4.6 GENERIC#4 i386 > Build Date: 28 October 2009 04:45:26PM > [...] > $ dmesg | head -1 > OpenBSD 4.6-current (GENERIC) #4: Wed Oct 28 15:35:02 ICT 2009 > > Thanks, > > Philippe
Re: OT: Python (was Re: vi in /bin)
On Sat, Dec 19, 2009 at 3:19 PM, Claudio Jeker wrote: > On Sat, Dec 19, 2009 at 02:51:32PM -0500, Nick Guenther wrote: >> and just to add to the pyre... >> >> On Sat, Dec 19, 2009 at 8:38 AM, Claudio Jeker >> wrote: >> > >> > Ugh, a programming language where you can't copy paste from xterm to xterm >> > without fucking up the program is just way to much pain to work on. >> >> >> >On Sat, Dec 19, 2009 at 10:03 AM, Ted Unangst wrote: >> > for many people who are a little suspicious of the whole >> > whitespace thing, when your first taste of the language is hours spent >> > fixing the whitespace, you aren't inclined to use it any more than >> > necessary. >> >> Your losses then. Python isn't so much a language of recipes, it's a >> language of ideas. >> > > Python is a bit like mother russia, it is thinking for you. > >> On Sat, Dec 19, 2009 at 2:06 PM, Henning Brauer >> wrote: >> > * Floor Terra [2009-12-19 19:10]: >> >> >> >> In my experience (mostly python and c), code that has been pasted has >> >> a higher bug density. >> >> >> >> It's worse with Python because of the indentation (tabs vs. spaces), >> >> but as a general rule I would say never copy/paste code. >> > >> > boo hoo. >> > >> > there are very valid uses of copied code, or extremely similiar code >> > (copy & paste and change a few things). we have that many times in the >> > tree. >> >> Python is about thinking about what you're doing. It's one of those >> languages that forces you to work on a higher level (not that there >> aren't lots of places where python is used as a scripting >> language--that code tends to come out badly, but that's because it's >> written just to get the job done). >> > > Yeah, we C-programmers are just mastrubating monkeys poking the typewrite > till it produces compiling code. If you don't think about what your doing > you get the crap code you see everywhere and it is not depending on the > language used. > >> Ideal code is abstracted code, what possible use does repeating >> yourself in the tree have? I know drivers have to declare a common set >> of globals and make some macro calls and various entry-points are >> found by sticking to a naming scheme, but that's trivia, hardly enough >> to justify "valid uses for copied code". Anytime I find myself wanting >> to copy some code it's always meant I've stumbled over an abstraction >> I haven't made yet, so what in the world is src/ doing that -requires- >> copied code? >> > > Code abstraction is nice until you have to update a vendor driver or some > other highly abstracted nightmare. Been there, done that, got the > nightmares. Sometimes it is far better to copy a few lines instead of > abstracting an interface until it is unusable. > > No programming language will redeem people from thinking and designing > their projects correctly. I should make it more clear what I was saying: knowing the basics of python can't force you to write good code (in fact the python stdlib is full of shitty shitty code--the web stuff is particularly terrible) but there's something about working in it that lets me approach problems in a different way then I would have otherwise. (of course the near-ultimate end of this line of thinking is lisp, where you can define syntax for any construct you want to abstract, but lisp personally I find lisp too wordy--that's just me though) And I didn't mean "abstracting" in the way that C++/Java people mean it. I've fought tooth and nail against indirection in the name of "simplification" before. Come on. On Sat, Dec 19, 2009 at 3:30 PM, Darrin Chandler wrote: > Python is regularly used by myself and others for scripting and it > comes out just fine. Sometimes I work at a higher level and other times > not, as the situation calls for. Doing things The UNIX Way(tm) means > some programs are simple filters that do not benefit from large numbers > of abstraction layers. Far from forcing me, Python allows me to write in > a way appropriate to the task at hand. I'm sorry, I didn't mean to imply that scripting people wrote bad code. I was thinking more like the add-ons to QuantumGIS. >> Your losses then. Python isn't so much a language of recipes, it's a >> language of ideas. > > Oh my. > > A language of ideas should mean that ideas are concisely expressible in > code, and that reading the code should convey the meaning. So you see an > idea on the web somewhere and paste the idea into your code and it's > broken? Idea fail! > > I like Python, but this "language of ideas" bit is silly. Ideas as in the structure of the program, not as in "communication". Yes you can write any data/dependency/etc structure in any language, but some languages let you do it easier, and I've found python to be the easiest that I've tried (which is, afterall, their stated goal). > Oh my. > > Python didn't invent abstraction. There's a lot of abstraction in the > tree, you know, in plain old C. Some kinds of abstraction are easier in > some languages, but there
Re: OT: Python (was Re: vi in /bin)
On Sat, Dec 19, 2009 at 02:51:32PM -0500, Nick Guenther wrote: > and just to add to the pyre... > > On Sat, Dec 19, 2009 at 8:38 AM, Claudio Jeker > wrote: > > > > Ugh, a programming language where you can't copy paste from xterm to xterm > > without fucking up the program is just way to much pain to work on. > > > >On Sat, Dec 19, 2009 at 10:03 AM, Ted Unangst wrote: > > for many people who are a little suspicious of the whole > > whitespace thing, when your first taste of the language is hours spent > > fixing the whitespace, you aren't inclined to use it any more than > > necessary. > > Your losses then. Python isn't so much a language of recipes, it's a > language of ideas. Oh my. A language of ideas should mean that ideas are concisely expressible in code, and that reading the code should convey the meaning. So you see an idea on the web somewhere and paste the idea into your code and it's broken? Idea fail! I like Python, but this "language of ideas" bit is silly. > On Sat, Dec 19, 2009 at 2:06 PM, Henning Brauer wrote: > > * Floor Terra [2009-12-19 19:10]: > >> > >> In my experience (mostly python and c), code that has been pasted has > >> a higher bug density. > >> > >> It's worse with Python because of the indentation (tabs vs. spaces), > >> but as a general rule I would say never copy/paste code. > > > > boo hoo. > > > > there are very valid uses of copied code, or extremely similiar code > > (copy & paste and change a few things). we have that many times in the > > tree. > > Python is about thinking about what you're doing. It's one of those > languages that forces you to work on a higher level (not that there > aren't lots of places where python is used as a scripting > language--that code tends to come out badly, but that's because it's > written just to get the job done). Python is regularly used by myself and others for scripting and it comes out just fine. Sometimes I work at a higher level and other times not, as the situation calls for. Doing things The UNIX Way(tm) means some programs are simple filters that do not benefit from large numbers of abstraction layers. Far from forcing me, Python allows me to write in a way appropriate to the task at hand. > Ideal code is abstracted code, what possible use does repeating > yourself in the tree have? I know drivers have to declare a common set > of globals and make some macro calls and various entry-points are > found by sticking to a naming scheme, but that's trivia, hardly enough > to justify "valid uses for copied code". Anytime I find myself wanting > to copy some code it's always meant I've stumbled over an abstraction > I haven't made yet, so what in the world is src/ doing that -requires- > copied code? Oh my. Python didn't invent abstraction. There's a lot of abstraction in the tree, you know, in plain old C. Some kinds of abstraction are easier in some languages, but there are often trade-offs. How many times per second does an ethernet driver get called when there's a lot of traffic? Really, Python doesn't paste well from the web and this can be a problem for newbies. This isn't about Python being a language of ideas, it's about Python choosing indent as meaningful and how sucky copying from a web page is in practice. Meaningful indent works really, REALLY well when writing python or reading python, but it sucks bad in this one instance. Not because Python sucks, but because embedding code in forum posts sucks. Tough cookies for python, because that's the shape of the world right now. -- Darrin Chandler| Phoenix BSD User Group | MetaBUG dwchand...@stilyagin.com | http://phxbug.org/ | http://metabug.org/ http://www.stilyagin.com/ | Daemons in the Desert | Global BUG Federation
devede-3.15.0 problem
Chris and Antoine, The first attempt didn't make it to the list. On Sat, Dec 19, 2009 at 12:25:29PM -0600, Chris Bennett wrote: > Antoine Jacoutot wrote: > >On Sat, 19 Dec 2009, Chris Bennett wrote: > >>I have yet to get devede to work on i386. > > > >It works for me, and it always did. > > > How can I figure out what the problem is? > I don't mind command line use. It looks to me that perhaps devede > just uses a collection of different packages for each set of steps. > I wouldn't mind at all doing it by hand. > Chris > > A friend and I did a bit more snooping and have the following info. that may assist in fixing the problem. First, the error mentions that libavcodec is miscompiled. When I searched for that library, I did not find it. FFmpeg was also not present in my system. I added them. Second, the follwoing is the output of montagueneal# mlayer -loop 1 -identify -ao null -vo null -frames 0 /usr/local/share/devede/silence.ogg Notice that ID_LENGTH is reported as 'inf'. 1 MPlayer SVN-r29414-snapshot-3.3.5 (C) 2000-2009 MPlayer Team 2 3 Playing /usr/local/share/devede/silence.ogg. 4 ID_AUDIO_ID=0 5 [Ogg] stream 0: audio (Vorbis), -aid 0 6 Ogg file format detected. 7 ID_FILENAME=/usr/local/share/devede/silence.ogg 8 ID_DEMUXER=ogg 9 ID_AUDIO_FORMAT=vrbs 10 ID_AUDIO_BITRATE=0 11 ID_AUDIO_RATE=48000 12 ID_AUDIO_NCH=2 13 ID_LENGTH=inf 14 ID_SEEKABLE=1 15 ID_CHAPTERS=0 16 == 17 Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders 18 AUDIO: 48000 Hz, 2 ch, s16le, 64.0 kbit/4.17% (ratio: 8000->192000) 19 ID_AUDIO_BITRATE=64000 20 ID_AUDIO_RATE=48000 21 ID_AUDIO_NCH=2 22 Selected audio codec: [ffvorbis] afm: ffmpeg (FFmpeg Vorbis) 23 == 24 AO: [null] 48000Hz 2ch s16le (2 bytes per sample) 25 ID_AUDIO_CODEC=ffvorbis 26 Video: no video 27 Starting playback... 28 29 30 Exiting... (End of file) 31 ID_EXIT=EOF 32 MPlayer SVN-r29414-snapshot-3.3.5 (C) 2000-2009 MPlayer Team 33 34 Playing /usr/local/share/devede/silence.ogg. 35 ID_AUDIO_ID=0 36 [Ogg] stream 0: audio (Vorbis), -aid 0 37 Ogg file format detected. 38 ID_FILENAME=/usr/local/share/devede/silence.ogg 39 ID_DEMUXER=ogg 40 ID_AUDIO_FORMAT=vrbs 41 ID_AUDIO_BITRATE=0 42 ID_AUDIO_RATE=48000 43 ID_AUDIO_NCH=2 44 ID_LENGTH=inf 45 ID_SEEKABLE=1 46 ID_CHAPTERS=0 47 == 48 Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders 49 AUDIO: 48000 Hz, 2 ch, s16le, 64.0 kbit/4.17% (ratio: 8000->192000) 50 ID_AUDIO_BITRATE=64000 51 ID_AUDIO_RATE=48000 52 ID_AUDIO_NCH=2 53 Selected audio codec: [ffvorbis] afm: ffmpeg (FFmpeg Vorbis) 54 == 55 AO: [null] 48000Hz 2ch s16le (2 bytes per sample) 56 ID_AUDIO_CODEC=ffvorbis 57 Video: no video 58 Starting playback... 59 60 61 Exiting... (End of file) 62 ID_EXIT=EOF 63 MPlayer SVN-r29414-snapshot-3.3.5 (C) 2000-2009 MPlayer Team 64 65 Playing /usr/local/share/devede/silence.ogg. 66 ID_AUDIO_ID=0 67 [Ogg] stream 0: audio (Vorbis), -aid 0 68 Ogg file format detected. 69 ID_FILENAME=/usr/local/share/devede/silence.ogg 70 ID_DEMUXER=ogg 71 ID_AUDIO_FORMAT=vrbs 72 ID_AUDIO_BITRATE=0 73 ID_AUDIO_RATE=48000 74 ID_AUDIO_NCH=2 75 ID_LENGTH=inf 76 ID_SEEKABLE=1 77 ID_CHAPTERS=0 78 == 79 Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders 80 AUDIO: 48000 Hz, 2 ch, s16le, 64.0 kbit/4.17% (ratio: 8000->192000) 81 ID_AUDIO_BITRATE=64000 82 ID_AUDIO_RATE=48000 83 ID_AUDIO_NCH=2 84 Selected audio codec: [ffvorbis] afm: ffmpeg (FFmpeg Vorbis) 85 == 86 AO: [null] 48000Hz 2ch s16le (2 bytes per sample) 87 ID_AUDIO_CODEC=ffvorbis 88 Video: no video 89 Starting playback... 90 91 92 Exiting... (End of file) 93 ID_EXIT=EOF
Re: OT: Python (was Re: vi in /bin)
On Sat, Dec 19, 2009 at 02:51:32PM -0500, Nick Guenther wrote: > and just to add to the pyre... > > On Sat, Dec 19, 2009 at 8:38 AM, Claudio Jeker > wrote: > > > > Ugh, a programming language where you can't copy paste from xterm to xterm > > without fucking up the program is just way to much pain to work on. > > > >On Sat, Dec 19, 2009 at 10:03 AM, Ted Unangst wrote: > > for many people who are a little suspicious of the whole > > whitespace thing, when your first taste of the language is hours spent > > fixing the whitespace, you aren't inclined to use it any more than > > necessary. > > Your losses then. Python isn't so much a language of recipes, it's a > language of ideas. > Python is a bit like mother russia, it is thinking for you. > On Sat, Dec 19, 2009 at 2:06 PM, Henning Brauer wrote: > > * Floor Terra [2009-12-19 19:10]: > >> > >> In my experience (mostly python and c), code that has been pasted has > >> a higher bug density. > >> > >> It's worse with Python because of the indentation (tabs vs. spaces), > >> but as a general rule I would say never copy/paste code. > > > > boo hoo. > > > > there are very valid uses of copied code, or extremely similiar code > > (copy & paste and change a few things). we have that many times in the > > tree. > > Python is about thinking about what you're doing. It's one of those > languages that forces you to work on a higher level (not that there > aren't lots of places where python is used as a scripting > language--that code tends to come out badly, but that's because it's > written just to get the job done). > Yeah, we C-programmers are just mastrubating monkeys poking the typewrite till it produces compiling code. If you don't think about what your doing you get the crap code you see everywhere and it is not depending on the language used. > Ideal code is abstracted code, what possible use does repeating > yourself in the tree have? I know drivers have to declare a common set > of globals and make some macro calls and various entry-points are > found by sticking to a naming scheme, but that's trivia, hardly enough > to justify "valid uses for copied code". Anytime I find myself wanting > to copy some code it's always meant I've stumbled over an abstraction > I haven't made yet, so what in the world is src/ doing that -requires- > copied code? > Code abstraction is nice until you have to update a vendor driver or some other highly abstracted nightmare. Been there, done that, got the nightmares. Sometimes it is far better to copy a few lines instead of abstracting an interface until it is unusable. No programming language will redeem people from thinking and designing their projects correctly. -- :wq Claudio
Re: OT: Python (was Re: vi in /bin)
On Sat, Dec 19, 2009 at 2:51 PM, Nick Guenther wrote: > Python is about thinking about what you're doing. It's one of those > languages that forces you to work on a higher level (not that there > aren't lots of places where python is used as a scripting > language--that code tends to come out badly, but that's because it's > written just to get the job done). > > Ideal code is abstracted code, what possible use does repeating > yourself in the tree have? I know drivers have to declare a common set > of globals and make some macro calls and various entry-points are > found by sticking to a naming scheme, but that's trivia, hardly enough > to justify "valid uses for copied code". Anytime I find myself wanting > to copy some code it's always meant I've stumbled over an abstraction > I haven't made yet, so what in the world is src/ doing that -requires- > copied code? I must disagree here... there's nothing about *any* programming language [1] that forces one to work on a higher level. That's up to the programmer. I've seen even the simplest tasks, or ones that scream for a nice, simple abstraction, done horribly (if at all) in any language, including python. My experience grading countless programs from freshman-senior students, which are increasingly written in python, show it's not the programming language... it's the programmer. Good design + good coding practices + tons-o-work forces one to think more and come up with a better design, not the language. -ryan [1] except of course for Haskell, the ONE TRUE GOD of proper programming :P
Re: No RTF_UP after route change to an interface that is up
On Fri, Dec 18, 2009 at 02:22:11PM +, Stuart Henderson wrote:
> On 2009/12/18 12:31, Claudio Jeker wrote:
> > > So it seems that any host routes, even RTP_DOWN, take priority over
> > > higher priority net routes for the same address.
> >
> > Host routes are allways more specific then network routes (even /32 ones).
> > So they will used in that case. Currently the lookup will not try less
> > specific routes in case their RTP_DOWN (or actually not RTF_UP). This
> > could be regarded as bug -- the code is just too insane to fix it easily.
>
> Hmmm... given this, would it make any kind of sense to have the routing
> daemons install /32 as host rather than network routes?
>
No I don't think this is a good decision. I prefer having them different
from the dynamic host routes generated by arp and icmp.
This is a very simple way to ensure that this those special routes are a
best match and work (or don't work) in all cases.
> > > This explains a little trouble I've been having when I restart ospfd
> > > (which I do a bit more often than is good for me, but haven't been able
> > > to put my finger on exactly why I have to...)
> >
> > Hmm. If you know what goes wrong I will try to fix it :)
>
> The relevant machines were running old code, but this week I've finally
> got them over the nat-to bump, so I'll be able to do some meaningful
> testing with -current soon (I hate reporting problems unless I know
> I've collected enough information to at least point someone in
> approximately the right direction ;)
>
I know a few things especially with new interface addresses are still not
perfect. I will try to unslack on ospfd and ospf6d in the next days.
> > This is PMTU fucking around because TCP is no longer getting ACKs back and
> > so it goes and tries to disable PMTU by creating a dynamic route cloned
> > from the parent route. In your case that's the default reject route.
> > Now that's totaly stupid I know and especially the created route is
> > wrong in so far that the reject bit is dropped. It is also questionable
> > why we should create a dynamic route cloned from a reject or blackhole
> > route.
>
> aha...yes this does indeed seem to be the explanation, and certainly
> for disabling PMTU, cloning a reject or blackhole route makes no sense.
>
See attached diff. Not seriously tested but until now no flames are
exiting my laptop...
> > As a workaround I would try to use blackhole routes instead of reject ones
> > and see if this will make the event of TCPs PMTU magic kicking in less
> > probable.
>
> This doesn't noticably help. But now I remember that since I started
> sending full BGP tables everywhere I don't actually need a default route
> to redist into OSPF any more...and after removing the route completely,
> this does work as expected, fixing my immediate problem.
>
--
:wq Claudio
Index: netinet/ip_icmp.c
===
RCS file: /cvs/src/sys/netinet/ip_icmp.c,v
retrieving revision 1.86
diff -u -p -r1.86 ip_icmp.c
--- netinet/ip_icmp.c 13 Nov 2009 20:54:05 - 1.86
+++ netinet/ip_icmp.c 18 Dec 2009 14:41:42 -
@@ -881,6 +881,11 @@ icmp_mtudisc_clone(struct sockaddr *dst,
if (rt == 0)
return (NULL);
+ /* Check if the route is actually usable */
+ if (rt->rt_flags & (RTF_REJECT | RTF_BLACKHOLE) ||
+ (rt->rt_flags & RTF_UP) == 0)
+ return (NULL);
+
/* If we didn't get a host route, allocate one */
if ((rt->rt_flags & RTF_HOST) == 0) {
Re: OT: Python (was Re: vi in /bin)
and just to add to the pyre... On Sat, Dec 19, 2009 at 8:38 AM, Claudio Jeker wrote: > > Ugh, a programming language where you can't copy paste from xterm to xterm > without fucking up the program is just way to much pain to work on. >On Sat, Dec 19, 2009 at 10:03 AM, Ted Unangst wrote: > for many people who are a little suspicious of the whole > whitespace thing, when your first taste of the language is hours spent > fixing the whitespace, you aren't inclined to use it any more than > necessary. Your losses then. Python isn't so much a language of recipes, it's a language of ideas. On Sat, Dec 19, 2009 at 2:06 PM, Henning Brauer wrote: > * Floor Terra [2009-12-19 19:10]: >> >> In my experience (mostly python and c), code that has been pasted has >> a higher bug density. >> >> It's worse with Python because of the indentation (tabs vs. spaces), >> but as a general rule I would say never copy/paste code. > > boo hoo. > > there are very valid uses of copied code, or extremely similiar code > (copy & paste and change a few things). we have that many times in the > tree. Python is about thinking about what you're doing. It's one of those languages that forces you to work on a higher level (not that there aren't lots of places where python is used as a scripting language--that code tends to come out badly, but that's because it's written just to get the job done). Ideal code is abstracted code, what possible use does repeating yourself in the tree have? I know drivers have to declare a common set of globals and make some macro calls and various entry-points are found by sticking to a naming scheme, but that's trivia, hardly enough to justify "valid uses for copied code". Anytime I find myself wanting to copy some code it's always meant I've stumbled over an abstraction I haven't made yet, so what in the world is src/ doing that -requires- copied code? -Nick
Re: OT: Python (was Re: vi in /bin)
On Sat, Dec 19, 2009 at 08:32:08PM +0100, Jonathan Schleifer wrote: > Darrin Chandler wrote: > > > You're doing testing wrong and the wrongness has nothing to do with > > python. ;-) > > Erm, since when is it wrong to change code for testing, to make sure it > even works under strange circumstances? oO When you can write your code to remain testable. If you've changed code, then you're only testing test code instead of production code. If you change it back for production, did you change it back correctly? Better to call the same code from both production and testing. Yes, I have used your approach. I only use that approach when I must. -- Darrin Chandler| Phoenix BSD User Group | MetaBUG dwchand...@stilyagin.com | http://phxbug.org/ | http://metabug.org/ http://www.stilyagin.com/ | Daemons in the Desert | Global BUG Federation
Re: OT: Python (was Re: vi in /bin)
Darrin Chandler wrote: > You're doing testing wrong and the wrongness has nothing to do with > python. ;-) Erm, since when is it wrong to change code for testing, to make sure it even works under strange circumstances? oO -- Jonathan [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: devede-3.15.0 problem
On Sat, Dec 19, 2009 at 09:20:31AM -0600, Chris Bennett wrote: > nealHogan wrote: > >Hello, > > > > File > >"/usr/local/lib/python2.5/site-packages/devede/devede_newfiles.py", line > >138, in read_file_values > >length=int(float(linea[10:])) > >OverflowError: cannot convert float infinity to long > >Compiler did not align stack variables. Libavcodec has been miscompiled > >and may be very slow or crash. This is not a bug in libavcodec, > >but in the compiler. You may try recompiling using gcc >= 4.2. > >Do not report crashes to FFmpeg developers. > > > > > I have yet to get devede to work on i386. > It starts and then hangs (but not crash) before finishing > I thought it might have been my system, but I just tried a new > system and it does the same > > I also could not get dvdstyler to work either > FWIW - I had devede working on my amd64 system prior to the upgrade to 3.15.0. I'm not exactly sure how to deal with devede's suggestion involving gcc 4.2 (or greater), given that the base compiler is not that. I realize there is a 4.2 pkg, but, again, am unsure what devede would like me to try.
Re: OT: Python (was Re: vi in /bin)
On Sat, Dec 19, 2009 at 07:29:00PM +0100, Jonathan Schleifer wrote: > Darrin Chandler wrote: > > > I agree that copy/paste from the web would be challenging for > > newcomers. Pastes from the web do horrible things to indenting. If > > you aren't comfortable with Python it'd be a huge pain. > > Well, enforced whitespaces are a double-edges sword: While enforcing > newcomes to indent their code correctly and thus getting them used to > the right style and avoiding bad behaviour, it is really a pain in the > ass for testing. If you are just going to test something, you often > have to reindent code. Luckily, vim can do that for you, but still, > it's rather annoying that I have to reformat the code then. You're doing testing wrong and the wrongness has nothing to do with python. ;-) -- Darrin Chandler| Phoenix BSD User Group | MetaBUG dwchand...@stilyagin.com | http://phxbug.org/ | http://metabug.org/ http://www.stilyagin.com/ | Daemons in the Desert | Global BUG Federation
Re: OpenBSD book
On Saturday 19 December 2009 02:10:24 ropers wrote: > 2009/12/19 Eric Furman : > > Does anyone have any info on this book? > > http://www.amazon.com/OpenBSD-Frederic-P-Miller/dp/6130089511/ref=sr_1_6?ie=UTF8&s=books&qid=1261193825&sr=1-6 > > > > The title is simply "OpenBSD". > > I ask because it seems to be pretty new, > > Published in October of 2009, and most of the > > other OBSD books I've seen are fairly old. > > Amazon gives remarkably little info on it. > > Does this answer your question? > > http://i.imgur.com/ggkB5.png > > regards, > --ropers Wow--a book of wikipedia reprints. I'd say that there is still some useful possiblity for it, but the price tag is nuts. Remember, not all books on a subject are useful. Sounds like the OpenSBD library has its first weak book, but thats ok--it might prod others into creating something better. --STeve Andre'
Re: OpenBSD book
On Sat, Dec 19, 2009 at 2:10 AM, ropers wrote: > > > Does this answer your question? > > http://i.imgur.com/ggkB5.png > > regards, > --ropers > > That is funny. I was wondering why someone would sell a book that is only 96 pages. :) -- Thx Joshua Gimer
Re: OT: Python (was Re: vi in /bin)
* Floor Terra [2009-12-19 19:10]: > On Sat, Dec 19, 2009 at 6:08 PM, Henning Brauer wrote: > > * Floor Terra [2009-12-19 16:47]: > >> But in my experience copy/paste of code in any language is dangerous. > > > > [ ] you have ever seriously used C > > > > heck, even perl. > > > > In my experience (mostly python and c), code that has been pasted has > a higher bug density. > > This is because most of the copy/paste goes like this: > 1) Write some loop > 2) Need similar loop > 3) copy/paste old loop > 4) Modify pasted loop (but forget one tiny change) > 5) New loop has bug > > It's worse with Python because of the indentation (tabs vs. spaces), > but as a general rule I would say never copy/paste code. boo hoo. there are very valid uses of copied code, or extremely similiar code (copy & paste and change a few things). we have that many times in the tree. the enforced indentation is completely nuts. i purposefully indent extremely incorrectly when adding debug code that i intend to remove again, to spot it faster. just one example, there are many more. python doesn't solve a problem. perl's been there already. oh, and the 80s sed, i use it a lot. as well as shell scripts. -- Henning Brauer, h...@bsws.de, henn...@openbsd.org BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting
Re: re1: watchdog timeout
On Thu, Dec 17, 2009 at 10:16:41AM +, Stefan Olsson wrote: > I have an intermittent problem on one of my firewalls. It has worked well for > years with different openbsd-releases but a few days after installing a > snapshot a few months ago it sometimes just stops taking traffic on the > internal nic. And all you get at the console is "watchdog timeout on re1". I had that behavior when running openbsd (and netbsd) in qemu, which was fixed (hacked around) by disabling mpbios: For OpenBSD, we need to disable mpbios (for full details, see http://scie.nti.st/2009/10/4/running-openbsd-4-5-in-kvm-on-ubuntu-linux-9-04). In brief, login to OpenBSD as root and type the following, then reboot: config -ef /bsd disable mpbios quit So give that a try, maybe it will work for you too? If you follow the link it also describes how to disable mpbios for a single boot. Sam
Re: devede-3.15.0 problem
Antoine Jacoutot wrote: On Sat, 19 Dec 2009, Chris Bennett wrote: I have yet to get devede to work on i386. It works for me, and it always did. How can I figure out what the problem is? I don't mind command line use. It looks to me that perhaps devede just uses a collection of different packages for each set of steps. I wouldn't mind at all doing it by hand. Chris -- A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -- Robert Heinlein
Re: OT: Python (was Re: vi in /bin)
Darrin Chandler wrote: > I agree that copy/paste from the web would be challenging for > newcomers. Pastes from the web do horrible things to indenting. If > you aren't comfortable with Python it'd be a huge pain. Well, enforced whitespaces are a double-edges sword: While enforcing newcomes to indent their code correctly and thus getting them used to the right style and avoiding bad behaviour, it is really a pain in the ass for testing. If you are just going to test something, you often have to reindent code. Luckily, vim can do that for you, but still, it's rather annoying that I have to reformat the code then. -- Jonathan [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: OT: Python (was Re: vi in /bin)
Floor Terra wrote: > This is because most of the copy/paste goes like this: > 1) Write some loop > 2) Need similar loop > 3) copy/paste old loop > 4) Modify pasted loop (but forget one tiny change) > 5) New loop has bug This is why I never just copy code, but type it. While you type, you also think about whether it makes sense to just copy the code and you will notice if you have to adjust something. Saved me quite a few times and doesn't take too long if you copy only short code. And long code should never be copied anyway. -- Jonathan [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: vi in /bin
Ingo Schwarze wrote on Sat., Dec. 19 at 17:51:19 >Matthew Szudzik wrote on Sat, Dec 19, 2009 at 05:34:23PM +: > >> But if you're going to learn just one of them, then I vote for sed. > >Marc, rewrite pkg* in sed. Please... :) Herr Schwarze, please get help before you injure yourself or someone else. ;-) -- Edward Ahlsen-Girard Ft Walton Beach, FL
Re: OT: Python (was Re: vi in /bin)
On Sat, Dec 19, 2009 at 6:08 PM, Henning Brauer wrote: > * Floor Terra [2009-12-19 16:47]: >> But in my experience copy/paste of code in any language is dangerous. > > [ ] you have ever seriously used C > > heck, even perl. > In my experience (mostly python and c), code that has been pasted has a higher bug density. This is because most of the copy/paste goes like this: 1) Write some loop 2) Need similar loop 3) copy/paste old loop 4) Modify pasted loop (but forget one tiny change) 5) New loop has bug It's worse with Python because of the indentation (tabs vs. spaces), but as a general rule I would say never copy/paste code. -- Floor Terra www: http://brobding.mine.nu/
Re: vi in /bin
Matthew Szudzik wrote on Sat, Dec 19, 2009 at 05:34:23PM +: > But if you're going to learn just one of them, then I vote for sed. Marc, rewrite pkg* in sed. Please... :)
Re: vi in /bin
On Fri, Dec 18, 2009 at 03:27:07PM -0800, Randal L. Schwartz wrote: > Everything I used to know about sed, I've forgotten once learning Perl. It seems that every decade has its own fashionable Unix scripting language. The original scripting language, used in the 1970's was sed. But awk became the fashionable language in the 1980's, then perl in the 1990's, and now python in the 2000's. Who knows what will be next? If you have time to spare, it certainly could be useful to learn all of these languages. But if you're going to learn just one of them, then I vote for sed. You will still encounter environments where sed is the only one of these languages available (as Ingo pointed out, the OpenBSD installer is one such example). It isn't really necessary to keep up with fashion, you can just stick with the historical standards.
Re: Merry christmas - ExploreCN
Glad to contact with you . this is lanie from ExploreCN that specialize in promotional gift. Here attached mine best wish of christams day and new year-2010 to you. hope you will have good time in your holiday. With Best regards, Lanie 2009-12-19 Add: 6-4-801,Shengshi Qiantang Bvldo< No.899 Fuchun Rd, 31, Hangzhou,Zhejiang, P.R.China TEL: +86-571-87040510 | FAX: +86-571-86851085 | MOB: +86-137 5717 0425 Skype: Lanie00143 | MSN: la...@hotmail.com | Trademanager : CN209673847 E-mail: la...@explorecn.com | www.ExploreCN.com [demime 1.01d removed an attachment of type image/jpeg which had a name of lanie.jpg]
Re: OT: Python (was Re: vi in /bin)
* Floor Terra [2009-12-19 16:47]: > But in my experience copy/paste of code in any language is dangerous. [ ] you have ever seriously used C heck, even perl. -- Henning Brauer, h...@bsws.de, henn...@openbsd.org BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting
Xorg -br option does not work anymore
Hello, Xorg's -br option does not seem to work anymore. When I try it I get the standard X grey pattern on the root window instead of getting solid black. The option '-nolisten tcp' still works, and I have not tried to test other options. I noticed the change after upgrading a desktop PC from 4.5-current to 4.6-current about a month and a half ago (recompiling OpenBSD and Xenocara from source) and saw the same change again yesterday when doing the same upgrade using the same homemade release on a Thinkpad laptop (T43). Can anyone confirm this or is it just me? I know about 'xsetroot -solid black', I just would like to know whether this is an Xorg bug or a problem with the way my machines are configured and / or upgraded. $ Xorg -version [...] X.Org X Server 1.6.3.901 (1.6.4 RC 1) Release Date: 2009-8-25 X Protocol Version 11, Revision 0 Build Operating System: OpenBSD 4.6 i386 Current Operating System: OpenBSD akpatok.ungava.bay 4.6 GENERIC#4 i386 Build Date: 28 October 2009 04:45:26PM [...] $ dmesg | head -1 OpenBSD 4.6-current (GENERIC) #4: Wed Oct 28 15:35:02 ICT 2009 Thanks, Philippe
Re: devede-3.15.0 problem
On Sat, 19 Dec 2009, Chris Bennett wrote: > I have yet to get devede to work on i386. It works for me, and it always did. -- Antoine
Re: OT: Python (was Re: vi in /bin)
On Sat, Dec 19, 2009 at 2:38 PM, Claudio Jeker wrote: > Ugh, a programming language where you can't copy paste from xterm to xterm > without fucking up the program is just way to much pain to work on. I agree that copy/paste is a big problem in Python. But in my experience copy/paste of code in any language is dangerous. If you want to re-use code, write a function. -- Floor Terra www: http://brobding.mine.nu/
Re: devede-3.15.0 problem
nealHogan wrote: Hello, The following is the output I get from starting devede and choosing any one of the disc type options on the initial screen. I just updated to the latest amd64 snaps and pkgs (17 Dec). montagueneal# devede DeVeDe 3.15.0 Using package-installed files /home/neal/ Entro en fonts Salgo de fonts /home/neal/ Temp Directory is: /var/tmp home load: /home/neal/.devede Creating window /usr/local/share/devede/wdisk_type.ui /usr/local/lib/python2.5/site-packages/devede/devede_other.py:419: GtkWarning: Could not load image 'devede.svg': Co tree.add_from_file(filename) Creating window /usr/local/share/devede/wmain.ui Launching program: mplayer -loop 1 -identify -ao null -vo null -frames 0 /usr/local/share/devede/silence.ogg elemento: /usr/local/bin DEMUX_OGG: header n. 0 broken! len=30, code: -132 DEMUX_OGG: header n. 1 broken! len=73, code: -132 DEMUX_OGG: header n. 2 broken! len=3437, code: -132 Traceback (most recent call last): File "/usr/local/lib/python2.5/site-packages/devede/devede_disctype.py", line 71, in on_disctype_dvd self.set_disk_type() File "/usr/local/lib/python2.5/site-packages/devede/devede_disctype.py", line 101, in set_disk_type self.main_window=devede_main.main_window(self.global_vars,self.show_again) File "/usr/local/lib/python2.5/site-packages/devede/devede_main.py", line 75, in __init__ self.set_default_global() File "/usr/local/lib/python2.5/site-packages/devede/devede_main.py", line 121, in set_default_global check,channels=test.read_file_values(self.global_vars["menu_sound"],True) File "/usr/local/lib/python2.5/site-packages/devede/devede_newfiles.py", line 138, in read_file_values length=int(float(linea[10:])) OverflowError: cannot convert float infinity to long Compiler did not align stack variables. Libavcodec has been miscompiled and may be very slow or crash. This is not a bug in libavcodec, but in the compiler. You may try recompiling using gcc >= 4.2. Do not report crashes to FFmpeg developers. I have yet to get devede to work on i386. It starts and then hangs (but not crash) before finishing I thought it might have been my system, but I just tried a new system and it does the same I also could not get dvdstyler to work either -- A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -- Robert Heinlein
Re: OT: Python (was Re: vi in /bin)
On Sat, Dec 19, 2009 at 10:03:00AM -0500, Ted Unangst wrote: > It's very hard to fix the indenting when you're copying code from a > web forum/email archive/whatnot that mangled it. Been there done > that. Pythons behavior in this regard makes it very aggravating to > work with as a newcomer, and for many people who are a little > suspicious of the whole whitespace thing, when your first taste of > the language is hours spent fixing the whitespace, you aren't > inclined to use it any more than necessary. I agree that copy/paste from the web would be challenging for newcomers. Pastes from the web do horrible things to indenting. If you aren't comfortable with Python it'd be a huge pain. -- Darrin Chandler| Phoenix BSD User Group | MetaBUG dwchand...@stilyagin.com | http://phxbug.org/ | http://metabug.org/ http://www.stilyagin.com/ | Daemons in the Desert | Global BUG Federation
Re: vi in /bin
Real men use DEBUG.EXE --Original Message-- From: Gregory Edigarov Sender: owner-m...@openbsd.org To: misc@openbsd.org Subject: Re: vi in /bin Sent: 18 Dec 2009 11:15 On Fri, 18 Dec 2009 10:28:25 +0100 Igor Sobrado wrote: > On Fri, Dec 18, 2009 at 6:07 AM, David Gwynne > wrote: > > On 18/12/2009, at 1:26 PM, Raymond Lillard wrote: > >> > >> Real men use cat. :-) > > > > real men use COPY CON PROGRAM.EXE > > real men use EDIT/TECO. > real men use XEDIT. -- With best regards, Gregory Edigarov
Re: OT: Python (was Re: vi in /bin)
It's very hard to fix the indenting when you're copying code from a web forum/email archive/whatnot that mangled it. Been there done that. Pythons behavior in this regard makes it very aggravating to work with as a newcomer, and for many people who are a little suspicious of the whole whitespace thing, when your first taste of the language is hours spent fixing the whitespace, you aren't inclined to use it any more than necessary. On Dec 19, 2009, at 9:21 AM, Darrin Chandler wrote: On Sat, Dec 19, 2009 at 02:38:20PM +0100, Claudio Jeker wrote: On Sat, Dec 19, 2009 at 06:17:50AM -0700, Darrin Chandler wrote: On Sat, Dec 19, 2009 at 01:54:54PM +0100, ropers wrote: 2009/12/19 Henning Brauer : any excuse to not know python is a good and valid one. any. If you have the time, I'd love to hear you elaborate. So far most people whose opinion I value have only said good things about Python. You're the first person whose opinion I respect to go against that. You just need to talk to more people, then. Lots of people don't like Python. Same for Perl, Ruby, or anything else. I've heard several devs say they don't like Python but I have yet to hear any of them actually give a reason. Ask them why they don't like C++ and you get a big list of everything that's wrong with it. Ask about Python and you get "it sucks" or "it's awful" or something. So I think it's just a matter of taste. Or maybe Henning has actual reasons. I haven't heard him talk about Python before so I don't know. Henning? Ugh, a programming language where you can't copy paste from xterm to xterm without fucking up the program is just way to much pain to work on. The indenting of code is an optical help but should not change the behaviour of the program. For me it is important to be able to write code with style(9) in mind (and I think most other BSD developpers think similar because our code all looks similar). I have often done copy/paste with Python code between xterms. Of course you must fix indenting. If you naively copy/paste C you will also have issues of syntax and meaning, but if you are so used to looking at C code that the meaning in the new context is immediately obvious without thinking then you will not notice. Instead you just fix/adjust it in place and move on. Some people will never like indent having meaning. But there is value in having an 'else' that *looks* like it belongs with an 'if' actually belong to that 'if', *because* it looks like it does. You don't ever have to like Python, but indenting to make blocks is perfectly cromulent. It's not a deficiency, it's just different. -- Darrin Chandler| Phoenix BSD User Group | MetaBUG dwchand...@stilyagin.com | http://phxbug.org/ | http://metabug.org/ http://www.stilyagin.com/ | Daemons in the Desert | Global BUG Federation
Re: OT: Python (was Re: vi in /bin)
The rules for scoping are utterly fucked. On Dec 19, 2009, at 7:54 AM, ropers wrote: 2009/12/19 Henning Brauer : any excuse to not know python is a good and valid one. any. If you have the time, I'd love to hear you elaborate. So far most people whose opinion I value have only said good things about Python. You're the first person whose opinion I respect to go against that. regards, --ropers
Re: Root file system is growing strangely
I found it, it was pflogd who was filling the root. Strange thing is that
/var is on separate partition from / and acording to man
FILES
/var/run/pflogd.pid Process ID of the currently running pflogd.
/var/log/pflog Default log file.
can I chroot pflogd to /var and is that a good idea? Is this and incident
due to problem with my pf.conf which is:
set skip on lo0
block in all
block out all
block in quick log on nfe0 proto tcp flags FUP/WEUAPRSF
block in quick log on nfe0 proto tcp flags WEUAPRSF/WEUAPRSF
block in quick log on nfe0 proto tcp flags SRAFU/WEUAPRSF
block in quick log on nfe0 proto tcp flags /WEUAPRSF
block in quick log on nfe0 proto tcp flags SR/SR
block in quick log on nfe0 proto tcp flags SF/SF
antispoof log quick for lo0
antispoof log quick for nfe0
antispoof log quick for fxp0
set loginterface nfe0
set loginterface fxp0
# pass out
pass out quick log on nfe0 proto { icmp, tcp, udp } from IP to any
pass out quick log on fxp0 proto { icmp, tcp, udp } from 10.168.2.3 to
10.168.2.4
pass out quick log on fxp0 proto { icmp, tcp, udp } from 10.168.2.3 to
10.168.2.5
# httpd on external net
pass in on nfe0 proto tcp from any to nfe0 port 80 flags S/SA synproxy state
(source-track rule, max-src-conn-rate 150/10, max-src-states 500,
max-src-nodes 400)
# SSH on internal net
pass in log on fxp0 proto tcp from 10.168.2.4 to fxp0 port someport
pass in log on fxp0 proto tcp from 10.168.2.5 to fxp0 port someport
# Samba on local net
pass in log on fxp0 proto tcp from 10.168.2.4 to fxp0 port 139
pass in log on fxp0 proto tcp from 10.168.2.5 to fxp0 port 139
I didn`t do any configuration of pflog.
2009/12/19 Bret S. Lambert
> On Sat, Dec 19, 2009 at 12:33:00PM +0200, Daniel Zhelev wrote:
> > Well, that was a good idea thanks for it, but no luck. I`ve killed and
> start
> > again every process listed in fstat but the amount of
> > used space has not drop. I`ve forgot to mention that I use 4.6-stable
> with
> > GENERIC kernel.
>
> Then start snapshotting via du -s k
>
> Rinse, lather, and repeat until you find out what the actual thing
> that keeps growing is.
>
> Had to do this myself earlier this week, as someone had
> a) decided that logging to /root/somefile was a good idea
> b) decided that logging on verbose was a good idea
>
> >
> > /dev/wd0a 1005M274M680M29%/
> >
> >
> >
> > 2009/12/18 Joachim Schipper
> >
> > > On Fri, Dec 18, 2009 at 10:36:46AM +0200, Daniel Zhelev wrote:
> > > > Hello list.
> > > > I`ve set up a little bash script to tell me when some file system is
> > > > over 95% full and after a month I got a mail about my root file
> system
> > > > ( / ) after log in I sow that the root file system is over 100%. That
> > > > is fine I tried to do a search for big and nasty files and so on but
> > > > after a hour magically the file system was at 20%. That got me very
> > > > worried about any security issue, but nothing was missing and so on.
> > > > The issue is that the file system continues to grow about a 2
> presents
> > > > a day, which is strange.
> > >
> > > > Here is some output:
> > > >
> > > > Filesystem SizeUsed Avail Capacity Mounted on
> > > > /dev/wd0a 1005M251M704M26%/
> > > > /dev/wd0k 46.7G 26.0K 44.4G 0%/home
> > > > /dev/wd0d 3.9G8.0K3.7G 0%/tmp
> > > > /dev/wd0f 2.0G615M1.3G32%/usr
> > > > /dev/wd0g 1005M145M809M15%/usr/X11R6
> > > > /dev/wd0h 5.4G206M5.0G 4%/usr/local
> > > > /dev/wd0i 2.0G619M1.3G32%/usr/src
> > > > /dev/wd0e 8.9G585M7.8G 7%/var
> > > > /dev/wd0j 2.0G961M951M50%/usr/obj
> > > > /dev/wd1a 295G562M280G 0%/storage/storages
> > > > /dev/wd1b 110G 20.7G 83.7G20%/storage/windows
> > > >
> > > > r...@sgate:/root# find / -xdev -size +1000 -type f | xargs ls -laSh
> > > > -rwxr-xr-x 1 root wheel 6.9M Nov 25 16:39 /bsd
> > > > -rw-r--r-- 1 root wheel 6.9M Nov 25 14:16 /obsd
> > > > -rw-r--r-- 1 root wheel 5.8M Nov 25 14:16 /bsd.rd
> > > > -r-xr-xr-x 1 root bin 1.2M Dec 7 15:05 /sbin/isakmpd
> > > > -r--r--r-- 1 root bin 526K Dec 7 15:06 /etc/magic
> > > >
> > > > r...@sgate:/root# find / -xdev -mtime -1 -type f | xargs ls -laSh
> > > > -rw--- 1 root wheel 2.0K Dec 18 03:09 /etc/pf.conf
> > > > -rw-r--r-- 1 root wheel 507B Dec 18 03:08 /etc/hosts
> > > > -rw-r--r-- 1 root wheel 0B Dec 18 02:49 /etc/resolv.conf
> > >
> > > > The other strange thing is that I`ve set up the /etc/daily root
> backup
> > > > and here is the compare between two discs:
> > > >
> > > > /dev/wd1d 1005M 42.2M912M 4%/altroot
> > > > /dev/wd0a 1005M251M704M26%/
> > > >
> > > > since /altroot is exact dd copy of / isn`t they at the same size?
> > >
> > > It's quite possible that some process is holding open a file descriptor
> > > to a
Re: OT: Python (was Re: vi in /bin)
On Sat, Dec 19, 2009 at 02:38:20PM +0100, Claudio Jeker wrote: > On Sat, Dec 19, 2009 at 06:17:50AM -0700, Darrin Chandler wrote: > > On Sat, Dec 19, 2009 at 01:54:54PM +0100, ropers wrote: > > > 2009/12/19 Henning Brauer : > > > > any excuse to not know python is a good and valid one. any. > > > > > > If you have the time, I'd love to hear you elaborate. So far most > > > people whose opinion I value have only said good things about Python. > > > You're the first person whose opinion I respect to go against that. > > > > You just need to talk to more people, then. Lots of people don't like > > Python. Same for Perl, Ruby, or anything else. I've heard several devs > > say they don't like Python but I have yet to hear any of them actually > > give a reason. Ask them why they don't like C++ and you get a big list > > of everything that's wrong with it. Ask about Python and you get "it > > sucks" or "it's awful" or something. So I think it's just a matter of > > taste. > > > > Or maybe Henning has actual reasons. I haven't heard him talk about > > Python before so I don't know. Henning? > > > > Ugh, a programming language where you can't copy paste from xterm to xterm > without fucking up the program is just way to much pain to work on. > The indenting of code is an optical help but should not change the > behaviour of the program. For me it is important to be able to write code > with style(9) in mind (and I think most other BSD developpers think > similar because our code all looks similar). I have often done copy/paste with Python code between xterms. Of course you must fix indenting. If you naively copy/paste C you will also have issues of syntax and meaning, but if you are so used to looking at C code that the meaning in the new context is immediately obvious without thinking then you will not notice. Instead you just fix/adjust it in place and move on. Some people will never like indent having meaning. But there is value in having an 'else' that *looks* like it belongs with an 'if' actually belong to that 'if', *because* it looks like it does. You don't ever have to like Python, but indenting to make blocks is perfectly cromulent. It's not a deficiency, it's just different. -- Darrin Chandler| Phoenix BSD User Group | MetaBUG dwchand...@stilyagin.com | http://phxbug.org/ | http://metabug.org/ http://www.stilyagin.com/ | Daemons in the Desert | Global BUG Federation
Re: tcpdump "kills" terminal by dumping RADIUS traffic
On 12/19/09, Stuart Henderson wrote:
> On 2009-12-17, Denis Doroshenko wrote:
> > RFC2865 WRT Class field content says the following:
> >
> > The String field is one or more octets.
>
>
> So the RD_STRING is correct,
If you take "STRING" in RD_STRING points to "string" in the RFC, then
that may be the case. The RFC defines the following types:
text 1-253 octets containing UTF-8 encoded 10646 [7]
characters. Text of length zero (0) MUST NOT be sent;
omit the entire attribute instead.
string1-253 octets containing binary data (values 0 through
255 decimal, inclusive). Strings of length zero (0)
MUST NOT be sent; omit the entire attribute instead.
address 32 bit value, most significant octet first.
integer 32 bit unsigned value, most significant octet first.
time 32 bit unsigned value, most significant octet first --
seconds since 00:00:00 UTC, January 1, 1970. The
standard Attributes do not use this data type but it is
presented here for possible use in future attributes.
So there's no type that is straight printable. For me, when and
attribute type described as "octets containing binary data", better be
printed as hexadecimal. But it is IMHO.
> and the same problem could occur with other strings. How about running
> them through strvisx() instead?
You are completely correct the same may occur with other strings while
they would be perfectly in accordance with the RFC.
> Index: print-radius.c
> ===
> RCS file: /cvs/src/usr.sbin/tcpdump/print-radius.c,v
>
> retrieving revision 1.8
> diff -u -p -r1.8 print-radius.c
> --- print-radius.c 23 May 2006 21:57:15 - 1.8
>
> +++ print-radius.c 19 Dec 2009 13:04:46 -
> @@ -32,7 +32,9 @@
> #include
>
> #include
> +#include
> #include
> +#include
>
> /* RADIUS support for tcpdump, Thomas Ptacek */
>
> @@ -206,6 +208,7 @@ static void r_print_address(int code, in
>
> static void r_print_string(int code, int len, const u_char *data) {
> char string[128];
> + char vis[128*4];
Just curious here, why128*4? Do you try to align stack here? As per
vis(3) the buffer should be 127*4+1, isn;t it a task of a compiler to
place the variables in the stack no matter what their sizes are?
Then again, the RFC defines maximum length of the string type is 253.
Is it okay to print 127 first octets of it? May be for -v mode we
could print all of it?
> if(!len) {
> fputs(" ?", stdout);
> @@ -218,7 +221,8 @@ static void r_print_string(int code, int
> memset(string, 0, 128);
> memcpy(string, data, len);
>
> - fprintf(stdout, " %s", string);
> + strvisx(vis, string, len, 0);
Do we still need that string and memset/memcpy? Why not removing
variable string and here just doing strvisx(vis, data, len, 0)?
> + fprintf(stdout, " %s", vis);
> }
>
> static void r_print_hex(int code, int len, const u_char *data) {
Re: OT: Python (was Re: vi in /bin)
On Sat, Dec 19, 2009 at 06:17:50AM -0700, Darrin Chandler wrote: > On Sat, Dec 19, 2009 at 01:54:54PM +0100, ropers wrote: > > 2009/12/19 Henning Brauer : > > > any excuse to not know python is a good and valid one. any. > > > > If you have the time, I'd love to hear you elaborate. So far most > > people whose opinion I value have only said good things about Python. > > You're the first person whose opinion I respect to go against that. > > You just need to talk to more people, then. Lots of people don't like > Python. Same for Perl, Ruby, or anything else. I've heard several devs > say they don't like Python but I have yet to hear any of them actually > give a reason. Ask them why they don't like C++ and you get a big list > of everything that's wrong with it. Ask about Python and you get "it > sucks" or "it's awful" or something. So I think it's just a matter of > taste. > > Or maybe Henning has actual reasons. I haven't heard him talk about > Python before so I don't know. Henning? > Ugh, a programming language where you can't copy paste from xterm to xterm without fucking up the program is just way to much pain to work on. The indenting of code is an optical help but should not change the behaviour of the program. For me it is important to be able to write code with style(9) in mind (and I think most other BSD developpers think similar because our code all looks similar). -- :wq Claudio
devede-3.15.0 problem
Hello, The following is the output I get from starting devede and choosing any one of the disc type options on the initial screen. I just updated to the latest amd64 snaps and pkgs (17 Dec). montagueneal# devede DeVeDe 3.15.0 Using package-installed files /home/neal/ Entro en fonts Salgo de fonts /home/neal/ Temp Directory is: /var/tmp home load: /home/neal/.devede Creating window /usr/local/share/devede/wdisk_type.ui /usr/local/lib/python2.5/site-packages/devede/devede_other.py:419: GtkWarning: Could not load image 'devede.svg': Co tree.add_from_file(filename) Creating window /usr/local/share/devede/wmain.ui Launching program: mplayer -loop 1 -identify -ao null -vo null -frames 0 /usr/local/share/devede/silence.ogg elemento: /usr/local/bin DEMUX_OGG: header n. 0 broken! len=30, code: -132 DEMUX_OGG: header n. 1 broken! len=73, code: -132 DEMUX_OGG: header n. 2 broken! len=3437, code: -132 Traceback (most recent call last): File "/usr/local/lib/python2.5/site-packages/devede/devede_disctype.py", line 71, in on_disctype_dvd self.set_disk_type() File "/usr/local/lib/python2.5/site-packages/devede/devede_disctype.py", line 101, in set_disk_type self.main_window=devede_main.main_window(self.global_vars,self.show_again) File "/usr/local/lib/python2.5/site-packages/devede/devede_main.py", line 75, in __init__ self.set_default_global() File "/usr/local/lib/python2.5/site-packages/devede/devede_main.py", line 121, in set_default_global check,channels=test.read_file_values(self.global_vars["menu_sound"],True) File "/usr/local/lib/python2.5/site-packages/devede/devede_newfiles.py", line 138, in read_file_values length=int(float(linea[10:])) OverflowError: cannot convert float infinity to long Compiler did not align stack variables. Libavcodec has been miscompiled and may be very slow or crash. This is not a bug in libavcodec, but in the compiler. You may try recompiling using gcc >= 4.2. Do not report crashes to FFmpeg developers.
Re: Web Browsers
ropers wrote: > > Finally, if you use Adblock Plus, you owe it to yourself to also use > Element Hiding Helper. > --regards, > ropers Wow, thank you, I've always wanted an addon like this.
Re: tcpdump "kills" terminal by dumping RADIUS traffic
On Sat, Dec 19, 2009 at 01:06:02PM +, Stuart Henderson wrote:
> On 2009-12-17, Denis Doroshenko wrote:
> > RFC2865 WRT Class field content says the following:
> >
> > The String field is one or more octets.
>
> So the RD_STRING is correct,
>
> > string1-253 octets containing binary data (values 0 through
> > 255 decimal, inclusive). Strings of length zero (0)
> > MUST NOT be sent; omit the entire attribute instead.
>
> and the same problem could occur with other strings. How about running
> them through strvisx() instead?
>
I had the same idea. So I like this idea.
> Index: print-radius.c
> ===
> RCS file: /cvs/src/usr.sbin/tcpdump/print-radius.c,v
> retrieving revision 1.8
> diff -u -p -r1.8 print-radius.c
> --- print-radius.c23 May 2006 21:57:15 - 1.8
> +++ print-radius.c19 Dec 2009 13:04:46 -
> @@ -32,7 +32,9 @@
> #include
>
> #include
> +#include
> #include
> +#include
>
> /* RADIUS support for tcpdump, Thomas Ptacek */
>
> @@ -206,6 +208,7 @@ static void r_print_address(int code, in
>
> static void r_print_string(int code, int len, const u_char *data) {
> char string[128];
> + char vis[128*4];
>
> if(!len) {
> fputs(" ?", stdout);
> @@ -218,7 +221,8 @@ static void r_print_string(int code, int
> memset(string, 0, 128);
> memcpy(string, data, len);
>
> - fprintf(stdout, " %s", string);
> + strvisx(vis, string, len, 0);
> + fprintf(stdout, " %s", vis);
I think this can be simplified further. The memset() and memcpy() can be
skipped since you can call strvisx() directly with data.
> }
>
> static void r_print_hex(int code, int len, const u_char *data) {
>
--
:wq Claudio
Re: Root file system is growing strangely
ropers wrote: 2009/12/18 Daniel Zhelev : after log in I sow that the root file system is over 100%. *Over* 100%? How is that even possible? FAQ 14.14
Re: OT: Python (was Re: vi in /bin)
2009/12/19 ropers : > 2009/12/19 Henning Brauer : >> any excuse to not know python is a good and valid one. any. > > If you have the time, I'd love to hear you elaborate. So far most It's religion. The python followers say the same about perl. :-) Best Martin
Re: Root file system is growing strangely
On Sat, Dec 19, 2009 at 08:02:59AM -0500, Kenneth Westerback wrote: > On Sat, Dec 19, 2009 at 7:50 AM, ropers wrote: > > 2009/12/18 Daniel Zhelev : > >> after log in I sow that the root file system > >> is over 100%. > > > > *Over* 100%? How is that even possible? > > > > > > Because this is Unix? Not a sarcastic reply, pointing out that this is > a well known feature of ffs. Although finding a nice Goggle phrase to > pull up an historical discussion seem unexpectedly difficult. http://www.openbsd.org/faq/faq14.html#NegSpace But yes, such things are almost impossible to Google up. Anything with small numbers or symbols doesn't search well at all. -- Darrin Chandler| Phoenix BSD User Group | MetaBUG dwchand...@stilyagin.com | http://phxbug.org/ | http://metabug.org/ http://www.stilyagin.com/ | Daemons in the Desert | Global BUG Federation
Re: OT: Python (was Re: vi in /bin)
On Sat, Dec 19, 2009 at 01:54:54PM +0100, ropers wrote: > 2009/12/19 Henning Brauer : > > any excuse to not know python is a good and valid one. any. > > If you have the time, I'd love to hear you elaborate. So far most > people whose opinion I value have only said good things about Python. > You're the first person whose opinion I respect to go against that. You just need to talk to more people, then. Lots of people don't like Python. Same for Perl, Ruby, or anything else. I've heard several devs say they don't like Python but I have yet to hear any of them actually give a reason. Ask them why they don't like C++ and you get a big list of everything that's wrong with it. Ask about Python and you get "it sucks" or "it's awful" or something. So I think it's just a matter of taste. Or maybe Henning has actual reasons. I haven't heard him talk about Python before so I don't know. Henning? -- Darrin Chandler| Phoenix BSD User Group | MetaBUG dwchand...@stilyagin.com | http://phxbug.org/ | http://metabug.org/ http://www.stilyagin.com/ | Daemons in the Desert | Global BUG Federation
Re: Web Browsers
On Fri, 18 Dec 2009, Bob Beck wrote: 2009/12/18 nixlists : On Fri, Dec 18, 2009 at 9:07 PM, Marco Peereboom wrote: firefox + adsuck [...] and at the moment I haven't seen anything that works as an effective selective javascript blocker for chrome like noscript - they just expect you to let google decide what sites are safe so far. Can anybody comment on privoxy? Junkbuster used to be simple, but privoxy seems to be quite complex to set up. Regards, David
Re: Handling HTTP virtual hosts with relayd
On 19 Dec 2009, at 12:18, Lars Nooden wrote: > Ben Calvert wrote: >> This is what squid is for. >> >> On Dec 18, 2009, at 10:01 AM, James Stocks wrote: >> >>> Hello everyone, >>> >>> I'm presently using Apache to reverse-proxy HTTP connections through to our >>> Microsoft IIS servers so that we don't have to expose IIS directly to >> Internet >>> hosts. Recently, I've been testing relayd in this role. > > The vulnerable machines are still accessible via the proxy, squid. > Don't fiddle with half measures, move what you have over to Apache. > Say what you have the machine for and it will be easier to find the > right software for you. > > /Lars > The IIS servers have a fair number of ASP.net based applications, to be honest I don't know what 50% of them do but they are needed. Nothing would please me more than to get rid of these machines and indeed this is what I advocate whenever my opinion is sought. However, I don't have the authority to tell the software development department what to do, so I'm stuck with it for now. I know that IIS isn't ideal from a security point of view, but I want to do everything we can to safeguard them from attack. My view is that placing Apache, relayd, squid et. al. between the server and the Internet at least helps to strip out some attacks. Anyway, somebody has replied to me off-list indicating that relayd can't presently handle virtual hosts in the same way Apache does, so I'll stick with this for now. Thanks to all who advised. James.
Re: tcpdump "kills" terminal by dumping RADIUS traffic
On 2009-12-17, Denis Doroshenko wrote:
> RFC2865 WRT Class field content says the following:
>
> The String field is one or more octets.
So the RD_STRING is correct,
> string1-253 octets containing binary data (values 0 through
> 255 decimal, inclusive). Strings of length zero (0)
> MUST NOT be sent; omit the entire attribute instead.
and the same problem could occur with other strings. How about running
them through strvisx() instead?
Index: print-radius.c
===
RCS file: /cvs/src/usr.sbin/tcpdump/print-radius.c,v
retrieving revision 1.8
diff -u -p -r1.8 print-radius.c
--- print-radius.c 23 May 2006 21:57:15 - 1.8
+++ print-radius.c 19 Dec 2009 13:04:46 -
@@ -32,7 +32,9 @@
#include
#include
+#include
#include
+#include
/* RADIUS support for tcpdump, Thomas Ptacek */
@@ -206,6 +208,7 @@ static void r_print_address(int code, in
static void r_print_string(int code, int len, const u_char *data) {
char string[128];
+ char vis[128*4];
if(!len) {
fputs(" ?", stdout);
@@ -218,7 +221,8 @@ static void r_print_string(int code, int
memset(string, 0, 128);
memcpy(string, data, len);
- fprintf(stdout, " %s", string);
+ strvisx(vis, string, len, 0);
+ fprintf(stdout, " %s", vis);
}
static void r_print_hex(int code, int len, const u_char *data) {
Re: Handling HTTP virtual hosts with relayd
On 2009-12-19, Lars Nooden wrote: > The vulnerable machines are still accessible via the proxy, squid. > Don't fiddle with half measures, move what you have over to Apache. > Say what you have the machine for and it will be easier to find the > right software for you. It could equally be "I have a webserver running apache, I want to split vhosts onto separate (machines|httpd instances) and keep them on a single IP address without using something which is total overkill". And sometimes it's simply not possible to move things to a different platform. On 2009-12-19, Ben Calvert wrote: > This is what squid is for. Or www/pound, or www/varnish, or apache mod_proxy, or lighttpd mod_proxy, or... pound is probably the simplest of these, but each have their advantages and disadvantages. On 2009-12-18, James Stocks wrote: > I'm presently using Apache to reverse-proxy HTTP connections through to our > Microsoft IIS servers so that we don't have to expose IIS directly to Internet > hosts. Recently, I've been testing relayd in this role. > > Apache can reverse-proxy requests for several internal HTTP servers through a > single internet-routable IP address by using virtual hosts. I've not yet > discovered a way of getting relayd to forward the request to a different host > depending on the content of the 'Host:' header. Does relayd have this > capability? If so how do I do it? It would make a lot of sense to be able to do this, but it doesn't seem possible (if it actually is possible, it's very well hidden in the docs).
Re: Root file system is growing strangely
On Sat, Dec 19, 2009 at 7:50 AM, ropers wrote: > 2009/12/18 Daniel Zhelev : >> after log in I sow that the root file system >> is over 100%. > > *Over* 100%? How is that even possible? > > Because this is Unix? Not a sarcastic reply, pointing out that this is a well known feature of ffs. Although finding a nice Goggle phrase to pull up an historical discussion seem unexpectedly difficult. Ken
OT: Python (was Re: vi in /bin)
2009/12/19 Henning Brauer : > any excuse to not know python is a good and valid one. any. If you have the time, I'd love to hear you elaborate. So far most people whose opinion I value have only said good things about Python. You're the first person whose opinion I respect to go against that. regards, --ropers
Re: Root file system is growing strangely
2009/12/18 Daniel Zhelev : > after log in I sow that the root file system > is over 100%. *Over* 100%? How is that even possible?
Re: Handling HTTP virtual hosts with relayd
Ben Calvert wrote: > This is what squid is for. > > On Dec 18, 2009, at 10:01 AM, James Stocks wrote: > >> Hello everyone, >> >> I'm presently using Apache to reverse-proxy HTTP connections through to our >> Microsoft IIS servers so that we don't have to expose IIS directly to > Internet >> hosts. Recently, I've been testing relayd in this role. The vulnerable machines are still accessible via the proxy, squid. Don't fiddle with half measures, move what you have over to Apache. Say what you have the machine for and it will be easier to find the right software for you. /Lars
Re: vi in /bin
* Randal L. Schwartz [2009-12-19 00:34]: > There's really no excuse for not knowing Perl and Python these days. any excuse to not know python is a good and valid one. any. -- Henning Brauer, h...@bsws.de, henn...@openbsd.org BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting
Re: Root file system is growing strangely
On Sat, Dec 19, 2009 at 12:33:00PM +0200, Daniel Zhelev wrote: > Well, that was a good idea thanks for it, but no luck. I`ve killed and start > again every process listed in fstat but the amount of > used space has not drop. I`ve forgot to mention that I use 4.6-stable with > GENERIC kernel. Then start snapshotting via du -s k Rinse, lather, and repeat until you find out what the actual thing that keeps growing is. Had to do this myself earlier this week, as someone had a) decided that logging to /root/somefile was a good idea b) decided that logging on verbose was a good idea > > /dev/wd0a 1005M274M680M29%/ > > > > 2009/12/18 Joachim Schipper > > > On Fri, Dec 18, 2009 at 10:36:46AM +0200, Daniel Zhelev wrote: > > > Hello list. > > > I`ve set up a little bash script to tell me when some file system is > > > over 95% full and after a month I got a mail about my root file system > > > ( / ) after log in I sow that the root file system is over 100%. That > > > is fine I tried to do a search for big and nasty files and so on but > > > after a hour magically the file system was at 20%. That got me very > > > worried about any security issue, but nothing was missing and so on. > > > The issue is that the file system continues to grow about a 2 presents > > > a day, which is strange. > > > > > Here is some output: > > > > > > Filesystem SizeUsed Avail Capacity Mounted on > > > /dev/wd0a 1005M251M704M26%/ > > > /dev/wd0k 46.7G 26.0K 44.4G 0%/home > > > /dev/wd0d 3.9G8.0K3.7G 0%/tmp > > > /dev/wd0f 2.0G615M1.3G32%/usr > > > /dev/wd0g 1005M145M809M15%/usr/X11R6 > > > /dev/wd0h 5.4G206M5.0G 4%/usr/local > > > /dev/wd0i 2.0G619M1.3G32%/usr/src > > > /dev/wd0e 8.9G585M7.8G 7%/var > > > /dev/wd0j 2.0G961M951M50%/usr/obj > > > /dev/wd1a 295G562M280G 0%/storage/storages > > > /dev/wd1b 110G 20.7G 83.7G20%/storage/windows > > > > > > r...@sgate:/root# find / -xdev -size +1000 -type f | xargs ls -laSh > > > -rwxr-xr-x 1 root wheel 6.9M Nov 25 16:39 /bsd > > > -rw-r--r-- 1 root wheel 6.9M Nov 25 14:16 /obsd > > > -rw-r--r-- 1 root wheel 5.8M Nov 25 14:16 /bsd.rd > > > -r-xr-xr-x 1 root bin 1.2M Dec 7 15:05 /sbin/isakmpd > > > -r--r--r-- 1 root bin 526K Dec 7 15:06 /etc/magic > > > > > > r...@sgate:/root# find / -xdev -mtime -1 -type f | xargs ls -laSh > > > -rw--- 1 root wheel 2.0K Dec 18 03:09 /etc/pf.conf > > > -rw-r--r-- 1 root wheel 507B Dec 18 03:08 /etc/hosts > > > -rw-r--r-- 1 root wheel 0B Dec 18 02:49 /etc/resolv.conf > > > > > The other strange thing is that I`ve set up the /etc/daily root backup > > > and here is the compare between two discs: > > > > > > /dev/wd1d 1005M 42.2M912M 4%/altroot > > > /dev/wd0a 1005M251M704M26%/ > > > > > > since /altroot is exact dd copy of / isn`t they at the same size? > > > > It's quite possible that some process is holding open a file descriptor > > to a file which has no links from the filesystem. To see this, run 'vi > > bigfile', suspend, and run 'rm bigfile'. The space is still used. Then > > quit vi, and optionally run 'sync', and you'll see the space has been > > reclaimed. > > > > To see which process is the culprit, try fstat. > > > > (Note that this is only one possibility!) > > > >Joachim
Re: Root file system is growing strangely
Well, that was a good idea thanks for it, but no luck. I`ve killed and start again every process listed in fstat but the amount of used space has not drop. I`ve forgot to mention that I use 4.6-stable with GENERIC kernel. /dev/wd0a 1005M274M680M29%/ 2009/12/18 Joachim Schipper > On Fri, Dec 18, 2009 at 10:36:46AM +0200, Daniel Zhelev wrote: > > Hello list. > > I`ve set up a little bash script to tell me when some file system is > > over 95% full and after a month I got a mail about my root file system > > ( / ) after log in I sow that the root file system is over 100%. That > > is fine I tried to do a search for big and nasty files and so on but > > after a hour magically the file system was at 20%. That got me very > > worried about any security issue, but nothing was missing and so on. > > The issue is that the file system continues to grow about a 2 presents > > a day, which is strange. > > > Here is some output: > > > > Filesystem SizeUsed Avail Capacity Mounted on > > /dev/wd0a 1005M251M704M26%/ > > /dev/wd0k 46.7G 26.0K 44.4G 0%/home > > /dev/wd0d 3.9G8.0K3.7G 0%/tmp > > /dev/wd0f 2.0G615M1.3G32%/usr > > /dev/wd0g 1005M145M809M15%/usr/X11R6 > > /dev/wd0h 5.4G206M5.0G 4%/usr/local > > /dev/wd0i 2.0G619M1.3G32%/usr/src > > /dev/wd0e 8.9G585M7.8G 7%/var > > /dev/wd0j 2.0G961M951M50%/usr/obj > > /dev/wd1a 295G562M280G 0%/storage/storages > > /dev/wd1b 110G 20.7G 83.7G20%/storage/windows > > > > r...@sgate:/root# find / -xdev -size +1000 -type f | xargs ls -laSh > > -rwxr-xr-x 1 root wheel 6.9M Nov 25 16:39 /bsd > > -rw-r--r-- 1 root wheel 6.9M Nov 25 14:16 /obsd > > -rw-r--r-- 1 root wheel 5.8M Nov 25 14:16 /bsd.rd > > -r-xr-xr-x 1 root bin 1.2M Dec 7 15:05 /sbin/isakmpd > > -r--r--r-- 1 root bin 526K Dec 7 15:06 /etc/magic > > > > r...@sgate:/root# find / -xdev -mtime -1 -type f | xargs ls -laSh > > -rw--- 1 root wheel 2.0K Dec 18 03:09 /etc/pf.conf > > -rw-r--r-- 1 root wheel 507B Dec 18 03:08 /etc/hosts > > -rw-r--r-- 1 root wheel 0B Dec 18 02:49 /etc/resolv.conf > > > The other strange thing is that I`ve set up the /etc/daily root backup > > and here is the compare between two discs: > > > > /dev/wd1d 1005M 42.2M912M 4%/altroot > > /dev/wd0a 1005M251M704M26%/ > > > > since /altroot is exact dd copy of / isn`t they at the same size? > > It's quite possible that some process is holding open a file descriptor > to a file which has no links from the filesystem. To see this, run 'vi > bigfile', suspend, and run 'rm bigfile'. The space is still used. Then > quit vi, and optionally run 'sync', and you'll see the space has been > reclaimed. > > To see which process is the culprit, try fstat. > > (Note that this is only one possibility!) > >Joachim
Re: smtpd(8) local delivery failure - help needed with diagnosis
On 2009-12-19, Adam Thompson wrote: > > Bang on. The manpages in -current have the writeup. I tend to refer > only to manpages that match the release I'm using, as I've been bitten a > few times by new functionality documented in the man page that doesn't > actually exist on my -stable system. You should be running -current if you're using smtpd.
Re: vi in /bin
On Sat, Dec 19, 2009 at 09:30:29AM +0100, Otto Moerbeek wrote: > > I'm aftraid my English (Scottish?) idiom falls short here. But I guess > "braw wee editor" means "small, but fine editor"? Because then you are right, > of course. > > -Otto (who learned ed before any other editor) yes, it really means "a great little editor". although putting "great" and "little" together sounds all wrong. anyway, i was drunk when i wrote that. otherwise i would have ignored this stupid thread. jmc
Re: vi in /bin
On Fri, Dec 18, 2009 at 11:17:51PM +0001, Jason McIntyre wrote: > On Fri, Dec 18, 2009 at 11:30:13AM -0600, Chris Bennett wrote: > > I would like to learn to use sed, however, I did not find that the man > > page was sufficient as a tutorial. I was not able to find any sed > > tutorials that were consistent with OpenBSD's variation. > > > > Does anyone know of any sed tutorials that work with OpenBSD's version? > > > > the man page is not a tutorial, but it does document everything. you > can use google and SEE ALSO for other stuff. actually the man page is > surprisingly complete, though i wouldn;t blame you for googling. > > everyone else has joked about it, but ed(1) is a braw wee editor... real > mem tire of comparisons. > > jmc I'm aftraid my English (Scottish?) idiom falls short here. But I guess "braw wee editor" means "small, but fine editor"? Because then you are right, of course. -Otto (who learned ed before any other editor)
