Re: OpenCVS?
the man pages of opencvs are cvs.1, cvs.5 ans cvsintro.7 (know I remember) in the source directory of opencvs, that is : /usr/src/usr.bin/cvs/ a little mdoc -mandoc cvs.1 and there you go ! On Jan 26, 2008 8:43 AM, xavier brinon [EMAIL PROTECTED] wrote: the man pages of opencvs are cvs.1, cvs.5 (as far as I remember) in the source directory of opencvs On Jan 25, 2008 4:38 PM, Julian Leyh [EMAIL PROTECTED] wrote: On 11:57 Sun 20 Jan , Darrin Chandler wrote: On Sun, Jan 20, 2008 at 06:31:48PM +, Stuart Henderson wrote: On 2008/01/20 10:15, Unix Fan wrote: Stuart Henderson wrote: See for yourself: http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/cvs/ I'm slighly confused by something if the cvs command in OpenBSD 4.2 is OpenCVS, it isn't - not everything in source is linked to the build yet. However, those interested in using/testing OpenCVS should take a peek at their /usr/src/usr.bin/cvs/README file as a start. The binary gets installed as opencvs, but the manpages as cvs - just in case you're wondering why cvs --help still is GNU CVS, and the manpages are not ;) -- If you don't remember something, it never existed... If you aren't remembered, you never existed... I don't quite understand what love is like... But if there was someone who liked me, I'd be happy.
Re: OpenCVS?
the man pages of opencvs are cvs.1, cvs.5 (as far as I remember) in the source directory of opencvs On Jan 25, 2008 4:38 PM, Julian Leyh [EMAIL PROTECTED] wrote: On 11:57 Sun 20 Jan , Darrin Chandler wrote: On Sun, Jan 20, 2008 at 06:31:48PM +, Stuart Henderson wrote: On 2008/01/20 10:15, Unix Fan wrote: Stuart Henderson wrote: See for yourself: http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/cvs/ I'm slighly confused by something if the cvs command in OpenBSD 4.2 is OpenCVS, it isn't - not everything in source is linked to the build yet. However, those interested in using/testing OpenCVS should take a peek at their /usr/src/usr.bin/cvs/README file as a start. The binary gets installed as opencvs, but the manpages as cvs - just in case you're wondering why cvs --help still is GNU CVS, and the manpages are not ;) -- If you don't remember something, it never existed... If you aren't remembered, you never existed... I don't quite understand what love is like... But if there was someone who liked me, I'd be happy.
Re: OpenCVS?
a little mdoc -mandoc cvs.1 and there you go ! Oups, nroff -mandoc cvs.1 That works better like this On Jan 26, 2008 8:43 AM, xavier brinon [EMAIL PROTECTED] wrote: the man pages of opencvs are cvs.1, cvs.5 (as far as I remember) in the source directory of opencvs On Jan 25, 2008 4:38 PM, Julian Leyh [EMAIL PROTECTED] wrote: On 11:57 Sun 20 Jan , Darrin Chandler wrote: On Sun, Jan 20, 2008 at 06:31:48PM +, Stuart Henderson wrote: On 2008/01/20 10:15, Unix Fan wrote: Stuart Henderson wrote: See for yourself: http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/cvs/ I'm slighly confused by something if the cvs command in OpenBSD 4.2 is OpenCVS, it isn't - not everything in source is linked to the build yet. However, those interested in using/testing OpenCVS should take a peek at their /usr/src/usr.bin/cvs/README file as a start. The binary gets installed as opencvs, but the manpages as cvs - just in case you're wondering why cvs --help still is GNU CVS, and the manpages are not ;) -- If you don't remember something, it never existed... If you aren't remembered, you never existed... I don't quite understand what love is like... But if there was someone who liked me, I'd be happy.
Re: ftp.openbsd.org?
man pages too On Feb 4, 2008 3:23 PM, Alexey Vatchenko [EMAIL PROTECTED] wrote: Hi! I can't get into ftp.openbsd.org and http://www.openbsd.org/cgi-bin/cvsweb/ shows me Internal Server Error page. Is it OK? -- Alexey Vatchenko http://www.bsdua.org
Re: Window Manager
On Mon, May 5, 2008 at 3:16 AM, Douglas A. Tutty [EMAIL PROTECTED] wrote: On Sun, May 04, 2008 at 09:29:42PM -0300, Gonzalo Lionel Rodriguez wrote: I dont know if it is the place to ask it, but that window manager uses? And why? I don't understand the question. Are you asking what window manager I use? icewm: small, easy to configure, has a taskbar for frequently used apps. Works well on my low-resource systems. Doug. If indeed Doug is right about your question I'm testing e17, not so small, not that easy to configure (everything is new, it takes time), very shiny (I can show off with my OBSD now) Xavier.
pbm install 4.3 Packard Bell EasyNote
Hello to all, The install of the 4.3 is quite difficult in comparison to the 4.2 (both dmesg are attached to the mail) the wifi is not properly recognised The boot is processed completely 50% of the times. I mean each time I have the ddb prompt, I just reboot (boot reboot) (see the dmesgko4.3 and the dmesgok4.3) and that second time it completes I've attached also the trace and ps. I reinstalled the 4.2 and all works fine, 4.3 stable is booting improperly half the time and 4.3 -current also. I stil can reboot my computer two times, and keep the ethernet cable instead of my wifi, but any improvement is welcome If anyone can help, thanks in advance. 0xe6000/0x1000! 0xeb000/0x5000! cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82855GM Host rev 0x02 Intel 82855GM Memory rev 0x02 at pci0 dev 0 function 1 not configured Intel 82855GM Config rev 0x02 at pci0 dev 0 function 3 not configured vga1 at pci0 dev 2 function 0 Intel 82855GM Video rev 0x02 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) agp0 at vga1: aperture at 0xb000, size 0x800 Intel 82855GM Video rev 0x02 at pci0 dev 2 function 1 not configured uhci0 at pci0 dev 29 function 0 Intel 82801DB USB rev 0x03: irq 10 uhci1 at pci0 dev 29 function 1 Intel 82801DB USB rev 0x03: irq 11 ehci0 at pci0 dev 29 function 7 Intel 82801DB USB rev 0x03: irq 7 ehci0: reset timeout ehci0: init failed, error=13 ppb0 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0x83 pci1 at ppb0 bus 1 rtw0 at pci1 dev 1 function 0 Realtek 8180 rev 0x20: irq 11 rtw0: ver RTL8180F, rtw0: could not recall EEPROM in 1us rtw0: could not recall EEPROM in 1us rl0 at pci1 dev 2 function 0 Realtek 8139 rev 0x10: irq 3, address 00:40:d0:62:86:13 rlphy0 at rl0 phy 0: RTL internal PHY ichpcib0 at pci0 dev 31 function 0 Intel 82801DBM LPC rev 0x03 pciide0 at pci0 dev 31 function 1 Intel 82801DBM IDE rev 0x03: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: ST94019A wd0: 16-sector PIO, LBA48, 38154MB, 78140160 sectors atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: QSI, DVD+-RW SDW-082S, LX06 ATAPI 5/cdrom removable ichiic0 at pci0 dev 31 function 3 Intel 82801DB SMBus rev 0x03: irq 5 iic0 at ichiic0 iic0: addr 0x18 00=00 01=00 02=00 3e=00 4e=00 words 00= 01= 02= 03= 04= 05= 06= 07= iic0: addr 0x1b 00=00 01=00 3e=00 48=d0 words 00= 01= 02= 03= 04= 05= 06= 07= iic0: addr 0x1e 00=00 01=00 3e=00 48=d0 words 00= 01= 02= 03= 04= 05= 06= 07= iic0: addr 0x21 00=00 01=00 02=00 3e=00 words 00= 01= 02= 03= 04= 05= 06= 07= iic0: addr 0x24 00=00 01=00 3e=00 words 00= 01= 02= 03= 04= 05= 06= 07= iic0: addr 0x26 00=00 01=00 02=00 3e=00 words 00= 01= 02= 03= 04= 05= 06= 07= iic0: addr 0x29 00=00 01=00 02=00 03=00 04=00 3e=00 3f=00 words 00= 01= 02= 03= 04= 05= 06= 07= iic0: addr 0x2c 00=00 3e=00 3f=00 words 00= 01= 02= 03= 04= 05= 06= 07= iic0: addr 0x2f 00=00 01=00 3e=00 words 00= 01= 02= 03= 04= 05= 06= 07= iic0: addr 0x4a 3e=00 words 00= 01= 02= 03= 04= 05= 06= 07= iic0: addr 0x4d 3e=00 words 00= 01= 02= 03= 04= 05= 06= 07= auich0 at pci0 dev 31 function 5 Intel 82801DB AC97 rev 0x03: irq 5, ICH4 AC97 ac97: codec id not read audio0 at auich0 Intel 82801DB Modem rev 0x03 at pci0 dev 31 function 6 not configured usb0 at uhci0: USB revision 1.0 uhub0 at usb0 Intel UHCI root hub rev 1.00/1.00 addr 1 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 Intel UHCI root hub rev 1.00/1.00 addr 1 isa0 at ichpcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pms0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pms0 mux 0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 biomask edf5 netmask edfd ttymask mtrr: Pentium Pro MTRR support nvram: invalid checksum softraid0 at root OpenBSD 4.3-current (GENERIC) #0: Sun Apr 27 22:32:03 CEST 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Celeron(R) M processor 1400MHz (GenuineIntel 686-class) 1.40 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,TM,SBF real mem = 234385408 (223MB) avail mem = 218484736 (208MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 09/14/04, BIOS32 rev. 0 @ 0xe97a0, SMBIOS rev. 2.3 @ 0xec31d (38 entries) bios0:
Re: 4.2 xenocara make build problem
On Sun, Jun 8, 2008 at 9:32 PM, Jesus Sanchez [EMAIL PROTECTED] wrote: Hi, using 4.2. Today I downloaded the xenocara.tar.gz from ftp.openbsd.org and it seems to have a problem. I untared the source into /usr/src/xenocara don't go any further http://www.openbsd.org/faq/upgrade43.html#xenocaramove
Re: Open hardware.
+1 On Nov 4, 2007 7:22 AM, Mark Thomas [EMAIL PROTECTED] wrote: On Nov 3, 2007 2:47 PM, Adrian Fisher [EMAIL PROTECTED] wrote: Would you be more inclined to buy a machine based on open source hardware rather than proprietary products such as Asus, Intel and AMD? Of course! -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments
google team and the DIY way of life
from the Official Google Blog Posted by Reza Behforooz, Software Engineer In my first month at Google, I complained to a friend on the Gmail team about a couple of small things that I disliked about Gmail. I expected him to point me to the bug database. But he told me to fix it myself, pointing me to a document on how to bring up the Gmail development environment on my workstation. The next day my code was reviewed by Gmail engineers, and then I submitted it. A week later, my change was live. I was amazed by the freedom to work across teams, the ability to check in code to another project, the trust in engineers to work on the right thing, and the excitement and speed of getting things done for our users. Engineers across our offices (and across projects) have access to the same code; I didn't have to ask for anyone's permission to work on this. I know, it's obvious that it's works if you share your code and let others submit their diffs. Just a reminder... See Google ? they shut up and code !
google team and the DIY way of life
-- Forwarded message -- From: xavier brinon [EMAIL PROTECTED] Date: Nov 12, 2007 10:12 AM Subject: Re: google team and the DIY way of life To: michael hamerski [EMAIL PROTECTED] I'm working for a French ISP where the dev team seems to live in a kind of secret chamber. I tried 3 times to code my own tools, sharing it with collegues. I've been told to quickly remove them, even if the tools helped a lot my collegues and myself. It's a shame, they didn't look at it and we were all back to the old tools. It's just for me to show that sharing code inside a company and having the ability to work with it is not available for everyone. It's not what they do, it's the way they work that is important for me here. I don't know how your company deals with that kind of thing, mine just don't. you must read that post like : hey, what you do here is great ! Even big companies know that ! I can post it in every open source community list, but i'm just an openBSD fan. And Misc@ seemed the most relevant to me. Sorry if it is not. On Nov 11, 2007 11:15 PM, michael hamerski [EMAIL PROTECTED] wrote: Posted by Reza Behforooz, Software Engineer In my first month at Google, I complained to a friend on the Gmail team about a couple of small things that I disliked about Gmail. I ... Dear Google, Could you get Reza to fix contact/label whitelisting in Gmail while he's at it? thanks, mike
[AV DiD] the death of AV defense in Depth
Hi, misc ! I think this is worth reading, http://www.nruns.com/ps/The_Death_of_AV_Defense_in_Depth-Revisiting_Anti-Virus_Software.pdf If anyone know an AV that is conceptually well made, please, tell me.
Re: A very good OpenLDAP tutorial - Notes
Thanks a lot, it gives the opportunity to read something new. Now I know better about it. I think it's a good idea to share our current reading. On Dec 13, 2007 12:25 AM, badeguruji [EMAIL PROTECTED] wrote: http://www.acay.com.au/~oscarp/tutor/ for all new Openldap users. thx, and sorry if you don't need this. -BG ~~Kalyan-mastu~~
Re: A sad thread - RMS vs. OpenBSD
a famous one, let S be the set of all elements that do not belong to S On Jan 8, 2008 3:10 AM, Eliah Kagan [EMAIL PROTECTED] wrote: Just recently, I said: On the other hand, well-formed statements can talk about some of their properties in certain systems. If worse comes to worse, you can simply use a different system to evaluate the statement. This really does make sense and there is information conveyed--a parallel would be Raymond Smullyan's example of a sign that reads, This sign was made my Cellini. That sign is actually telling you something. Typographical correction: Raymond Smullyan's example is of a sign that says: This sign was made *by* Cellini. -Eliah
flamewars : 9 Tips for Dealing with Idiots on the Internet
Seems to be a must read Sent to you by Xavier Brinon via Google Reader: Online Survival Guide: 9 Tips for Dealing with Idiots on the Internet via Internet Duct Tape by engtech on 09/01/08 My first experience with online communication was bulletin board systems in the early 90s. The more things change, the more they stay the same. The experience of running a blog is almost exactly the same as it was running a BBS 15 years ago. The only difference is the sheer number of channels available for communication. Where there was once up to 100 to 200 local BBSes there are now so many online forums for communication that it might as well be infinite., New forums for communication are being created all the time. Mainstream sites like the New York Times let you comment on articles, and each person has their own discussion forum thanks to sites like Facebook and MySpace. When I was involved in the BBS/IRC scene as a teenager I was surrounded by flame wars; one-upmanship was part of the attraction. I thought it was because of the immaturity of the participants, but now I think it is a natural offshoot of digital communication. We lose all the visual and auditory cues that are a normal part of human dialog and instead focus on words that can be easy to misinterpret (especially if looking for a reason to fight). quoting myself Winter is one of the worst for flame wars because environmental conditions make people more irritable and more likely to spend more time online. Here are some tips for navigating online discussions from someone who has been participating and managing public forums for over 15 years. Tips for Administrators Tip #1: Disemvowel From Wikipedia: In the fields of Internet discussion and forum moderation, disemvoweling is the removal of vowels from text either as a method of self-censorship, or as a technique by forum moderators to censor Internet trolling and other unwanted posting. When used by a forum moderator, the net effect of disemvowelling text is to render it illegible or legible only through significant cognitive effort. Xeni Jardin, co-editor of Boing Boing says of the practice, the dialogue stays, but the misanthrope looks ridiculous, and the emotional sting is neutralized. This original sentence: In the fields of Internet discussion and forum moderation, disemvoweling (also spelled disemvowelling) is the removal of vowels from text. would be disemvowelled to look like this: n th flds f ntrnt dscssn nd frm mdrtn, Dsmvwlng (ls splld dsmvwllng) s th rmvl f vwls frm txt. You can disemvowel any text using this tool. There is also a Firefox extension that lets you disemvowel comments if you're a WordPress administrator. The same guy has a Firefox extension for handling religious trolls. Tip #2: Temporarily disable comments for that post This works well if you've been linked to from another site and it's bringing a lot of tolls (IE: Digg, Slashdot). You can turn the comments on after a day or two without having to wade through the 100+ comments telling you how much of an idiot you are because they don't agree with some minor minutiae of your argument. Tip #3: Take the discussion to email Nothing kills a flame war like removing the audience. Quoting myself: There is a different between scrawling messages on a public site and having a one on one conversation. The flame wars that are routine on some sites rarely exist in personal email. People stop being disembodied words and ideas and you remember that there is a person behind all of that typing. Comment Ninja is a handy Firefox extension for WordPress blog administrators that makes it easy to respond to commenters on your blog by email. Tip #4: Never post personal information Because you are an administrator, you have access to a commenters email address and their IP address. This information is usually enough to find out anything else you want to about who they are. (IE: put their email address into Facebook to find their real name, use their IP address to find out where they work) It can be tempting to deal with a troll by removing their anonymity, but making it personal can change a one time nuisance into someone with a grudge that won't go away. Tips for Anyone Tip #5: Let it stew If something really gets your goat, then sit on it. Come back and re-read what bothered you later on and you may find that you were reading between the lines and interpreting an emotional undertone that isn't there. The human mind is great at adding missing context, but it can also trick you into reading what you want to believe. Revisiting something that filled you with rage days latter can leave you scratching your head trying to find what it was that pulled your chain. Tip #6: Leave it where you found it As I said earlier, it is ridiculously easy to collect personal identifying information about someone and find other parts of their online identity. Other than bringing a public argument to a private means of communication, you
