Re: Show us your /etc/profile
On 31/07/15 21:25, listas...@dna.uba.ar wrote: > How do you customize your environment? > > What aliases or custom functions do you use? > > Here's my /etc/profile I think you can find one or two interesting things > in it. Ouch - this hits a nerve. @work, we have a Unix environment where the "powers that be" have put every little customization into /etc/profile, parsing huge scripts to setup everything "in their gusto". It takes ages to parse, just for me to 'unalias' and 'unset' every little crap they put into and setup a sane prompt. Remember, users cannot easily avoid having /etc/profile parsed during login. Thus they cannot avoid getting all the variables and aliases that you are putting into it. Please do not recommend putting too much stuff into /etc/profile, the content of that file should be limited to bare minimum that should be enforced onto users. Everything else should go into $HOME/.profile (or /etc/skel/.profile). Bernd
Re: GROUP CHANGED
Groups and users are actually just numbers, the mapping to names happens in the /etc/passwd and /etc/group files. On Linux, user 0 is 'root' and group 0 is 'root'. On BSDs, user 0 is 'root', but group 0 is 'wheel'. Check the /etc/group file on both systems, and you will see. Bernd On 14/06/15 15:46, Max Power wrote: > Thank You Gilles for Your reply. > > Only the group is changed. > But why the owner is remained the same [root]? > On OpenBSD, I can not get root:root ? > > Thanks. > >> On Sun, Jun 14, 2015 at 04:32:18PM +0200, Max Power wrote: >>> Hi guys! >>> >>> I copied my files from Debian [ext4] to my new server OpenBSD [5.7 >>> amd64], >>> and I found that all files of 'ROOT' group were imported [in OpenBSD] in >>> the 'Wheel' group. >>> Why is this? >>> >>> [Owner is the same, there is no change.] >>> >>> Thank fro reply. >>> >> >> wheel is the new root. >> >> https://en.wikipedia.org/wiki/Wheel_(Unix_term) >> >> -- >> Gilles Chehade >> >> https://www.poolp.org @poolpOrg
Re: Very-small fully-functional systems?
On 09/03/15 00:09, Adam Thompson wrote: > I'm looking for a very (physically) small (embedded) platform that can > run OpenBSD properly, including at least: > USB 2.0, > ethernet, > MIDI (presumably via USB), > OK-to-good-quality analog audio out (can be USB), > some kind of decent storage (i.e. not USB!), > and enough CPU horsepower to run a soundfont-based softsynth like > timitidy or fluidsynth (so ~500MHz+). > I am using a DM&P EBOX as print server and chat desktop. Look at: http://robosavvy.com/store/dmp-ebox-3350mx-x86-compact-pc.html They are rather cheap and work with i386 OpenBSD. I never used audio, but it is properly detected. This has 512MB. It is not exactly the box that I have, but they all are similar. The box I have is: http://robosavvy.com/store/sbc-embedded-computer/dmp-ebox-3310mx-l3u4-mini-pc-auto-power-on-sata-rs232-3xlan.html azalia0 at pci0 dev 14 function 0 "RDC R3010 HDA" rev 0x01: irq 10 azalia0: codecs: Realtek ALC262 audio0 at azalia0 Bernd
Re: Dovecot happy on 5.6?
On 16/12/14 06:11, Brad Smith wrote: > On 12/15/14 23:48, Rod Whitworth wrote: >> I have been trying out dovecot for some years and it has always had >> some irritating "bug" or >> limitation and I have seen a few gripes from others. >> >> It seems to have been very quiet lately so I thought I'd have another >> attempt to get it running >> whilst choosing options that look like ones to suit me. > > It's been quiet because the bugs in OpenBSD were fixed and it just > works. It works fine for tons of people. > +1 Bernd
Re: CUPS printer problems
On 25/11/14 04:30, Antoine Jacoutot wrote: > On Mon, Nov 24, 2014 at 10:04:59PM +0000, Bernte wrote: >> Hi - >> >> Since upgrading to 5.6, I am having problems to detect my Brother USB >> printer in CUPS. >> >> The problem is that the printer is not found by the 'usb' backend: > > Your cups package is not up to date. You need the one from 5.6 stable. Thanks Antoine, upgrading to cups-1.7.4p1 made CUPS detect my printer. Issue fixed. Bernd
CUPS printer problems
Hi - Since upgrading to 5.6, I am having problems to detect my Brother USB printer in CUPS. The problem is that the printer is not found by the 'usb' backend: # /usr/local/libexec/cups/backend/usb DEBUG: Loading USB quirks from "/usr/local/share/cups/usb". DEBUG: Loaded 68 quirks. DEBUG: list_devices DEBUG: libusb_get_device_list=8 DEBUG: Failed to check whether 04f9:001a has the "usblp" kernel module attached The error looks suspicious, though I did not find anything useful about it googling the web (it seems to be an error caused by libusb). The printer does show up in usbdevs -vd: # usbdevs -vd Controller /dev/usb0: addr 1: high speed, self powered, config 1, EHCI root hub(0x), RDC(0x17f3), rev 1.00 uhub0 port 1 powered port 2 powered Controller /dev/usb1: addr 1: high speed, self powered, config 1, EHCI root hub(0x), RDC(0x17f3), rev 1.00 uhub1 port 1 powered port 2 powered Controller /dev/usb2: addr 1: full speed, self powered, config 1, OHCI root hub(0x), RDC(0x17f3), rev 1.00 uhub2 port 1 powered port 2 addr 2: full speed, self powered, config 1, product 0x001a(0x001a), Brother Industries(0x04f9), rev 1.00 ugen0 Controller /dev/usb3: addr 1: full speed, self powered, config 1, OHCI root hub(0x), RDC(0x17f3), rev 1.00 uhub3 port 1 powered port 2 addr 2: full speed, power 100 mA, config 1, Logitech BT Mini-Receiver(0x0b04), Logitech(0x046d), rev 49.00 uhub4 port 1 powered port 2 addr 3: full speed, power 98 mA, config 1, Logitech BT Mini-Receiver(0xc713), Logitech(0x046d), rev 49.00, iSerialNumber 001F203C2558 uhidev0 port 3 addr 4: full speed, power 98 mA, config 1, Logitech BT Mini-Receiver(0xc714), Logitech(0x046d), rev 49.00, iSerialNumber 001F203C2558 uhidev1 As explained in the pkg-readme, I have disabled the ulpt driver in the kernel, as well as changed the ownership of the devices: # ls -la /dev/usb2 /dev/ugen0.* crw-rw 1 _cups wheel 63, 0 Nov 21 19:35 /dev/ugen0.00 crw-rw 1 _cups wheel 63, 1 Nov 21 19:35 /dev/ugen0.01 crw-rw 1 _cups wheel 63, 2 Nov 21 19:35 /dev/ugen0.02 crw-rw 1 _cups wheel 63, 3 Nov 21 19:35 /dev/ugen0.03 crw-rw 1 _cups wheel 63, 4 Nov 21 19:35 /dev/ugen0.04 crw-rw 1 _cups wheel 63, 5 Nov 21 19:35 /dev/ugen0.05 crw-rw 1 _cups wheel 63, 6 Nov 21 19:35 /dev/ugen0.06 crw-rw 1 _cups wheel 63, 7 Nov 21 19:35 /dev/ugen0.07 crw-rw 1 _cups wheel 63, 8 Nov 21 19:35 /dev/ugen0.08 crw-rw 1 _cups wheel 63, 9 Nov 21 19:35 /dev/ugen0.09 crw-rw 1 _cups wheel 63, 10 Nov 21 19:35 /dev/ugen0.10 crw-rw 1 _cups wheel 63, 11 Nov 21 19:35 /dev/ugen0.11 crw-rw 1 _cups wheel 63, 12 Nov 21 19:35 /dev/ugen0.12 crw-rw 1 _cups wheel 63, 13 Nov 21 19:35 /dev/ugen0.13 crw-rw 1 _cups wheel 63, 14 Nov 21 19:35 /dev/ugen0.14 crw-rw 1 _cups wheel 63, 15 Nov 21 19:35 /dev/ugen0.15 crw-rw 1 _cups wheel 61, 2 Nov 21 19:35 /dev/usb2 Any hints on how to track down my problem would be welcome. Regards, Bernd dmesg: OpenBSD 5.6 (GENERIC) #2: Tue Oct 28 16:56:54 CET 2014 r...@stable-56-i386.mtier.org:/binpatchng/work-binpatch56-i386/src/sys/arch/i386/compile/GENERIC cpu0: Vortex86 SoC (586-class) 934 MHz cpu0: FPU,TSC,CX8,MMX real mem = 1039691776 (991MB) avail mem = 1010257920 (963MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 11/26/10, BIOS32 rev. 0 @ 0xf0010 apm0 at bios0: Power Management spec V1.2 pcibios0 at bios0: rev 3.0 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf2fe0/240 (13 entries) pcibios0: no compatible PCI ICU found: ICU vendor 0x17f3 product 0x6036 pcibios0: Warning, unable to fix up PCI interrupt routing pcibios0: PCI bus #0 is the last bus bios0: ROM list: 0xc/0x8000 cpu0 at mainbus0: (uniprocessor) pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 vendor "RDC", unknown product 0x6022 rev 0x00 rl0 at pci0 dev 1 function 0 "Realtek 8139" rev 0x10: irq 11, address 44:4d:50:07:1b:19 rlphy0 at rl0 phy 0: RTL internal PHY rl1 at pci0 dev 2 function 0 "Realtek 8139" rev 0x10: irq 11, address 44:4d:50:07:1b:1a rlphy1 at rl1 phy 0: RTL internal PHY pcib0 at pci0 dev 7 function 0 vendor "RDC", unknown product 0x6036 rev 0x00 vte0 at pci0 dev 8 function 0 "RDC R6040 Ethernet" rev 0x00: irq 6, address 00:1b:eb:25:30:9e rdcphy0 at vte0 phy 1: R6040 10/100 PHY, rev. 1 ohci0 at pci0 dev 10 function 0 "RDC R6060 USB" rev 0x12: irq 7, version 1.0, legacy support ehci0 at pci0 dev 10 function 1 "RDC R6061 USB2" rev 0x03: irq 3 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "RDC EHCI root hub" rev 2.00/1.00 addr 1 ohci1 at pci0 dev 11 function 0 "RDC R6060 USB" rev 0x12: irq 5, version 1.0, legacy support ehci1 at pci0 dev 11 function 1 "RDC R6061 USB2" rev 0x03: irq 9 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 "RDC EHCI root hub" rev
Re: rc.conf issue on upgrade from 5.5 to 5.6
On 10/10/14 22:35, Stuart Henderson wrote: > Yep. You *have* to run sysmerge for this upgrade or you will have broken rc > scripts. Just wondering: now that sysmerge seems to the main supported method for upgrading the etc directories, are there any plans to have it automagically run at the end of the upgrade script? At least optionally? This would simplify the 'upgrade guide' instructions, which is always welcome. Bernd
Re: Donations to OpenBSD
On 14/08/14 16:14, Nicolai wrote: > On Thu, Aug 14, 2014 at 07:16:41AM +0100, Bernte wrote: >> Could you please just clarify: I have money and I want that to go to the >> OpenBSD project. I would like as much as possible to make it there (from >> the UK in my case), I would like to give the OpenBSD people the highest >> degree of freedom of what to do with it, and don't need any physical >> gadgets to go with it. What is the optimal way to achieve this? > > The OpenBSD Foundation. > > http://www.openbsdfoundation.org/donations.html > > Theo has mentioned it several times this year as being the preferred > route. It's as simple as possible. > > Nicolai Thanks Nicolai for the answer. A few things have been clarified off-list. I now understand the implications of the different routes to OpenBSD. Bernd
Re: Donations to OpenBSD
On 14/08/14 01:10, Theo de Raadt wrote: >> How does it compare for using the SWIFT method outlined on the website? > > The SWIFT donations go to the Project. That is spent on things which > the Foundation doesn't pay for. Gee - CDs, T-Shirts, Project, Foundation - all this discussion starts to confuse me. Theo, I am planning to donate, but I am loosing my understanding of the optimal way. Could you please just clarify: I have money and I want that to go to the OpenBSD project. I would like as much as possible to make it there (from the UK in my case), I would like to give the OpenBSD people the highest degree of freedom of what to do with it, and don't need any physical gadgets to go with it. What is the optimal way to achieve this? Thanks, Bernd
Re: Getting stylus working on Thinkpad X61 tablet
On 28/04/14 14:43, Peter Hessler wrote: > yes, my new thinkpad edge works with the tablet perfectly fine. > > > On 2014 Apr 27 (Sun) at 16:46:31 -0700 (-0700), Bryan Linton wrote: > :Ping. > : > :Can anyone confirm or deny whether or not the newer Thinkpad > :tablets' styluses work as an input device? I see that there is a > :usbtablet(4) driver in xenocara, with people reporting success > :using external tablets, so it would probably be a matter of > :whether or not the newer Thinkpads still use a serial-based wacom > :device as opposed to a USB-based one. I own an X60t, and I did not manage to get it up and running. It was a long time ago and I cannot remember the details, unfortunately. I gave up because I also considered it not to be too important at that time. I might give it another spin and see how far I get. Now, with a second potential user, we might also get a proper problem description to the developers :-) Bernd
Re: 5.4 hanging when used as hostap
On 25/03/14 11:46, Stefan Sperling wrote: > It is possible that your power supply is having issues. > > With my net5501 I was seeing hard lockups until I upgraded to a stronger > power supply (same voltage, more ampere). The default power supply couldn't > power the board, a hard disk, and a wireless minipci card (also a ral rt2661 > in my case). You seem to be using a hard disk instead of a CF card, correct? > > If you like I can look up the exact specs of the power supply I'm using > tonight. I fully agree, I had exactly the same issues with my Soerkis 4801 when I used a power supply that was too weak. I upgraded mine to a supply that could do 15W, and have been happy ever since. Bernd
Re: [patch] usr.bin/mg/theo.c
On 21/03/14 22:56, Josh Grosse wrote: > "Complaint forms are handled in another department." > + "You'd be safer using Windows than the code which was just deleted." Isn't there a comma missing ... ? Bernd
Re: TP-Link TL-WN8200ND in 5.4
On 18/01/14 13:40, Alexey E. Suslikov wrote: the source tree as part of the regular 'make' call. But this way I managed to compile the kernel and install it. you didn't tell us is your urtwn(4) variant working or not after installing new kernel. new dmesg wouldn't hurt. Sorry for the late answer. The card seems to be recognized, see dmesg below (a little censored with XX). I still have problems getting it up to run; scanning works, but I cannot seem to setup a stable WPA connection. It is probably me, so I will continue to play around. I am a little disappointed that the hostap is not supported, but that was well documented. Bernd OpenBSD 5.4 (GENERIC) #0: Sat Jan 18 06:56:40 GMT 2014 root@:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Vortex86 SoC (586-class) 934 MHz cpu0: FPU,TSC,CX8,MMX real mem = 1039724544 (991MB) avail mem = 1011290112 (964MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 11/26/10, BIOS32 rev. 0 @ 0xf0010 apm0 at bios0: Power Management spec V1.2 pcibios0 at bios0: rev 3.0 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf2fe0/240 (13 entries) pcibios0: no compatible PCI ICU found: ICU vendor 0x17f3 product 0x6036 pcibios0: Warning, unable to fix up PCI interrupt routing pcibios0: PCI bus #0 is the last bus bios0: ROM list: 0xc/0x8000 cpu0 at mainbus0: (uniprocessor) pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 vendor "RDC", unknown product 0x6022 rev 0x00 rl0 at pci0 dev 1 function 0 "Realtek 8139" rev 0x10: irq 11, address 44:4d:50:07:1b:19 rlphy0 at rl0 phy 0: RTL internal PHY rl1 at pci0 dev 2 function 0 "Realtek 8139" rev 0x10: irq 11, address 44:4d:50:07:1b:1a rlphy1 at rl1 phy 0: RTL internal PHY pcib0 at pci0 dev 7 function 0 vendor "RDC", unknown product 0x6036 rev 0x00 vte0 at pci0 dev 8 function 0 "RDC R6040 Ethernet" rev 0x00: irq 6, address 00:1b:eb:25:30:9e rdcphy0 at vte0 phy 1: R6040 10/100 PHY, rev. 1 ohci0 at pci0 dev 10 function 0 "RDC R6060 USB" rev 0x12: irq 7, version 1.0, legacy support ehci0 at pci0 dev 10 function 1 "RDC R6061 USB" rev 0x03: irq 3 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "RDC EHCI root hub" rev 2.00/1.00 addr 1 ohci1 at pci0 dev 11 function 0 "RDC R6060 USB" rev 0x12: irq 5, version 1.0, legacy support ehci1 at pci0 dev 11 function 1 "RDC R6061 USB" rev 0x03: irq 9 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 "RDC EHCI root hub" rev 2.00/1.00 addr 1 pciide0 at pci0 dev 12 function 0 "RDC R1011 IDE" rev 0x01: DMA (unsupported), channel 0 configured to compatibility, channel 1 configured to compatibility pciide0: channel 0 ignored (not responding; disabled or no drives?) wd0 at pciide0 channel 1 drive 0: wd0: 16-sector PIO, LBA48, 305245MB, 625142448 sectors vga1 at pci0 dev 13 function 0 vendor "RDC", unknown product 0x2012 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) azalia0 at pci0 dev 14 function 0 vendor "RDC", unknown product 0x3010 rev 0x01: irq 10 azalia0: codecs: Realtek ALC262 audio0 at azalia0 isa0 at pcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com0: probed fifo depth: 0 bytes 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 pcppi0 at isa0 port 0x61 spkr0 at pcppi0 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 usb2 at ohci0: USB revision 1.0 uhub2 at usb2 "RDC OHCI root hub" rev 1.00/1.00 addr 1 usb3 at ohci1: USB revision 1.0 uhub3 at usb3 "RDC OHCI root hub" rev 1.00/1.00 addr 1 umass0 at uhub0 port 1 configuration 1 interface 0 "Generic Mass Storage Device" rev 2.00/1.00 addr 2 umass0: using SCSI over Bulk-Only scsibus0 at umass0: 2 targets, initiator 0 sd0 at scsibus0 targ 1 lun 0: SCSI0 0/direct removable serial.058f6366058F0OB1 sd0: 248MB, 512 bytes/sector, 508928 sectors uhidev0 at uhub2 port 2 configuration 1 interface 0 "Logitech USB Receiver" rev 1.10/9.10 addr 2 uhidev0: iclass 3/1 ums0 at uhidev0: 5 buttons, Z dir wsmouse0 at ums0 mux 0 uhidev1 at uhub3 port 2 configuration 1 interface 0 "Cherry Mikroschalter product 0x0011" rev 2.00/1.00 addr 2 uhidev1: iclass 3/1 ukbd0 at uhidev1: 8 variable keys, 6 key codes wskbd1 at ukbd0 mux 1 wskbd1: connecting to wsdisplay0 vscsi0 at root scsibus1 at vscsi0: 256 targets softraid0 at root scsibus2 at softraid0: 256 targets root on wd0a (197b846eebaa6c90.a) swap on wd0b dump on wd0b WARNING: / was not properly unmounted sd0 detached scsibus0 detached umass0 detached urtwn0 at uhub0 port 1 "Realtek 802.11n WLAN Adapter" rev 2.00/2.00 addr 2 urtwn0: MAC/BB RTL8192CU, RF 6052 2T2R, address XX:XX:XX:XX:XX:XX
Re: TP-Link TL-WN8200ND in 5.4
On 17/01/14 06:45, Jonathan Gray wrote: > A device attaching as ugen means no driver has claimed it. > Support for your device and many other urtwn devices was added > after 5.4. > > Here is an untested patch against 5.4 that should work: Hi Jonathan, Thank you very much for the help, this was exactly what I was hoping for, great support! The only thing extra that I did (outside the FAQ) was calling 'make' in /usr/src/sys/dev/usb to re-generate the header files. Not sure if that was the right way to do it, normally I expected this to happen outside the source tree as part of the regular 'make' call. But this way I managed to compile the kernel and install it. Again, thank you, Bernd
TP-Link TL-WN8200ND in 5.4
Hello, I was hoping that my TP-Link TL-WN8200ND works in 5.4, but it looks like it is only detected as an unsupported USB device. ugen0 at uhub0 port 2 "Realtek 802.11n WLAN Adapter" rev 2.00/2.00 addr 2 While the documentation from the provider is not verbose about the chipset used, the following page claims that it is a Realtek RTL8192CU, which seems to be supported by urtwn(4). http://wikidevi.com/wiki/TP-LINK_TL-WN8200ND Assuming that the firmware was missing, I tried fw_update, but that did not download any firmware files. I would be thankful for any kind of help to get this adapter running. Bernd # usbdevs -v Controller /dev/usb0: addr 1: high speed, self powered, config 1, EHCI root hub(0x), RDC(0x17f3), rev 1.00 port 1 powered port 2 addr 2: high speed, power 500 mA, config 1, 802.11n WLAN Adapter(0x0100), Realtek(0x2357), rev 2.00, iSerialNumber 00e04c01 Controller /dev/usb1: addr 1: high speed, self powered, config 1, EHCI root hub(0x), RDC(0x17f3), rev 1.00 port 1 powered port 2 powered Controller /dev/usb2: addr 1: full speed, self powered, config 1, OHCI root hub(0x), RDC(0x17f3), rev 1.00 port 1 powered port 2 powered Controller /dev/usb3: addr 1: full speed, self powered, config 1, OHCI root hub(0x), RDC(0x17f3), rev 1.00 port 1 powered port 2 powered # dmesg OpenBSD 5.4 (GENERIC) #37: Tue Jul 30 12:05:01 MDT 2013 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Vortex86 SoC (586-class) 934 MHz cpu0: FPU,TSC,CX8,MMX real mem = 1039724544 (991MB) avail mem = 1011290112 (964MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 11/26/10, BIOS32 rev. 0 @ 0xf0010 apm0 at bios0: Power Management spec V1.2 pcibios0 at bios0: rev 3.0 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf2fe0/240 (13 entries) pcibios0: no compatible PCI ICU found: ICU vendor 0x17f3 product 0x6036 pcibios0: Warning, unable to fix up PCI interrupt routing pcibios0: PCI bus #0 is the last bus bios0: ROM list: 0xc/0x8000 cpu0 at mainbus0: (uniprocessor) pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 vendor "RDC", unknown product 0x6022 rev 0x00 rl0 at pci0 dev 1 function 0 "Realtek 8139" rev 0x10: irq 11, address 44:4d:50:07:1b:19 rlphy0 at rl0 phy 0: RTL internal PHY rl1 at pci0 dev 2 function 0 "Realtek 8139" rev 0x10: irq 11, address 44:4d:50:07:1b:1a rlphy1 at rl1 phy 0: RTL internal PHY pcib0 at pci0 dev 7 function 0 vendor "RDC", unknown product 0x6036 rev 0x00 vte0 at pci0 dev 8 function 0 "RDC R6040 Ethernet" rev 0x00: irq 6, address 00:1b:eb:25:30:9e rdcphy0 at vte0 phy 1: R6040 10/100 PHY, rev. 1 ohci0 at pci0 dev 10 function 0 "RDC R6060 USB" rev 0x12: irq 7, version 1.0, legacy support ehci0 at pci0 dev 10 function 1 "RDC R6061 USB" rev 0x03: irq 3 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "RDC EHCI root hub" rev 2.00/1.00 addr 1 ohci1 at pci0 dev 11 function 0 "RDC R6060 USB" rev 0x12: irq 5, version 1.0, legacy support ehci1 at pci0 dev 11 function 1 "RDC R6061 USB" rev 0x03: irq 9 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 "RDC EHCI root hub" rev 2.00/1.00 addr 1 pciide0 at pci0 dev 12 function 0 "RDC R1011 IDE" rev 0x01: DMA (unsupported), channel 0 configured to compatibility, channel 1 configured to compatibility pciide0: channel 0 ignored (not responding; disabled or no drives?) wd0 at pciide0 channel 1 drive 0: wd0: 16-sector PIO, LBA48, 305245MB, 625142448 sectors vga1 at pci0 dev 13 function 0 vendor "RDC", unknown product 0x2012 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) azalia0 at pci0 dev 14 function 0 vendor "RDC", unknown product 0x3010 rev 0x01: irq 10 azalia0: No codecs found isa0 at pcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com0: probed fifo depth: 0 bytes 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 pcppi0 at isa0 port 0x61 spkr0 at pcppi0 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 usb2 at ohci0: USB revision 1.0 uhub2 at usb2 "RDC OHCI root hub" rev 1.00/1.00 addr 1 usb3 at ohci1: USB revision 1.0 uhub3 at usb3 "RDC OHCI root hub" rev 1.00/1.00 addr 1 ugen0 at uhub0 port 2 "Realtek 802.11n WLAN Adapter" rev 2.00/2.00 addr 2 vscsi0 at root scsibus0 at vscsi0: 256 targets softraid0 at root scsibus1 at softraid0: 256 targets root on wd0a (197b846eebaa6c90.a) swap on wd0b dump on wd0b
Re: Looking for good, small, canadian version laptop suggestions
On 10/16/13 12:27 PM, Gilbert Sanford wrote: I have purchased over 20 machines (about 50% laptop) from dfsdirectsales.com over the last 5 years, and most of them had next day business support still in effect from Dell. I had only one machine that needed service (a Latitude E6510,) and it was repaired at no charge within 2 days. Nice advertisement for Dell here on the list, but not applicable to the original question. From the FAQ: Does DFS Export? No. DFS does not ship items purchased from www.dfsdirectsales.com outside of the 50 United States. Last time I checked, Canada was not yet among them. Bernd
Re: Dovecot, TLS and Sieve.
On 10/13/13 7:27 PM, Maxime wrote:> Hi all. > > I'm trying to use Sieve with Dovecot and imaps (OpenBSD 5.3). > > When sieve protocol is enabled I can't connect to my IMAP server > anymore; as soon as I remove sieve from the "protocols" list it works again. > Does anyone already experienced this? > Any help would be really appreciated. Dear Maxime, I am running a very similar setup, without any problems running Sieve. I have added my output of dovecot -n below, but perhaps you can see anything that is different. Also, please have a look at the /var/dovecot directory. Perhaps there are some permissions wrong. I have also added the output from my configuration below. If you want to delta-debug, I am happy to provide any more information. Regards, Bernd -- # 2.1.15: /etc/dovecot/dovecot.conf # OS: OpenBSD 5.3 amd64 first_valid_uid = 1000 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave mbox_write_locks = fcntl mmap_disable = yes namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = bsdauth } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap pop3 lmtp sieve service auth { user = $default_internal_user } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } ssl_cert = imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags mail_max_userip_connections = 30 } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } - total 64 drwxr-xr-x 4 root wheel 1024 Oct 14 06:11 . drwxr-xr-x 32 root wheel 512 Feb 27 2013 .. srw--- 1 root wheel 0 Jul 27 19:09 anvil srw--- 1 root wheel 0 Jul 27 19:09 anvil-auth-penalty srw--- 1 root wheel 0 Jul 27 19:09 auth-client srw--- 1 _dovecot wheel 0 Jul 27 19:09 auth-login srw--- 1 root wheel 0 Jul 27 19:09 auth-master srw-rw-rw- 1 _dovecot wheel 0 Jul 27 19:09 auth-userdb srw--- 1 _dovecot wheel 0 Jul 27 19:09 auth-worker srw--- 1 root wheel 0 Jul 27 19:09 config srw--- 1 root wheel 0 Jul 27 19:09 dict srw--- 1 root wheel 0 Jul 27 19:09 director-admin srw--- 1 root wheel 0 Jul 27 19:09 director-userdb srw-rw-rw- 1 root wheel 0 Jul 27 19:09 dns-client srw--- 1 root wheel 0 Jul 27 19:09 doveadm-server lrwx-- 1 root wheel25 Jul 27 19:09 dovecot.conf -> /etc/dovecot/dovecot.conf drwxr-xr-x 2 root wheel 512 Dec 30 2012 empty srw-rw-rw- 1 root wheel 0 Jul 27 19:09 indexer srw--- 1 _dovecot wheel 0 Jul 27 19:09 indexer-worker -rw-r--r-- 1 root wheel58 Oct 13 21:54 instances srw--- 1 root wheel 0 Jul 27 19:09 ipc srw-rw-rw- 1 root wheel 0 Jul 27 19:09 lmtp srw--- 1 root wheel 0 Jul 27 19:09 log-errors drwxr-x--- 2 root _dovenull 512 Jul 27 19:09 login -rw--- 1 root wheel 6 Jul 27 19:09 master.pid -rw-r--r-- 1 root wheel58 Jul 27 19:09 mounts srw--- 1 root wheel 0 Jul 27 19:09 replication-notify prw--- 1 root wheel 0 Jul 27 19:09 replication-notify-fifo srw--- 1 _dovecot wheel 0 Jul 27 19:09 replicator -rw-r--r-- 1 root wheel 230 Oct 14 02:22 ssl-parameters.dat srw--- 1 root wheel 0 Jul 27 19:09 stats prw--- 1 root wheel 0 Jul 27 19:09 stats-mail -
Re: Verified OS concerns
On 9/19/13 9:29 PM, josef.win...@email.de wrote: Does OpenBSD plan to varify its (main) components, to reach the level of zero-bug software? I do assume that you are talking about "formal verification" meaning "mathematical proof of correctness". Verify against what? Verification is a binary mathematical relation between a formal specification and an implementation. So, to start you need a specification. I have never seen a specification of a UNIX-like operating system that can claim completeness is any way. And if there was, it may contain as many bugs as the code. This is a dead end ... Instead what you normally do is formally verifying certain, small aspects, like "are all variable initialized" or "will I ever be able access unallocated parts of the memory". Interestingly enough, whenever such a formal verification becomes practical, it is call "static checking" and then put into a tool like lint or valgrind. Then, on the other hand, mindless use of such static checking itself can lead to severe bugs [1]. If not, isn't there any concern that (future) varified OS will render OBSD redundant one day? No. Bernd [1] http://research.swtch.com/openssl
Re: OpenZFS announcement
Hi assume that OpenZFS will continue to be CDDL-licensed, and just start incorporating the changes that were developed for Illumos and FreeBSD (zpool version 5000, etc). Nothing new here. Bernd On 9/18/13 7:37 AM, patric conant wrote: http://www.open-zfs.org/wiki/Announcement It supposed to be open-er. I didn't find a license, thought it might be of mild interest.
Re: OT: bitrig relation to OpenBSD
On 10/06/12 03:38, Nick Holland wrote: On 06/09/12 14:01, Jiri B wrote: Hi, is bitrig fork just because of license, goals issue or is this also because some disagreements between developers? I think you ask the wrong people. Not sure why you would ask here, rather than the people who actually DID the fork. ... Just adding to that: I think their FAQ makes it absolutely clear what they want to achieve and how they try to differentiate themselves from OpenBSD. https://www.bitrig.org/index.php?title=FAQ Bernd