Re: alix 1e - 2,4/5 GHz Wifi card
On Sunday 07 June 2015 17:55:16 s...@asm68k.org wrote: Hello mailing list users, I was asked to repeat this question here. I am searching a wifi network card, which has the following properties: - provide a network in the 2,4 GHz and the 5 GHz bandwidths at the same time - has just one antenna (the alix 1e has just one slot for antenna) - is supported by OpenBSD (obviously, version does not matter) - fits into a mini-pci slot Can someone help me to find such a card? `man rel(4)` did not show any useable cards. Thank you in advance and kind regards, Dirk Hi Dirk: As an AP or as a client? PCEngines offers the Wistron CM9. Unfortunately I found that the RF-output power is far too low to be useful as an AP. The Compex WLM200X works better. Both cards need a dual band antenna. Both card's layout is for two antennas. I don't know of any card with only one. My trials with the WLM200X are not over. Clients connect fine to the AP on 2.4GHz and 5GHz but I didn't manage to assign an IP to the clients with DHCP although my DHCP server is working fine via wire in the same network. Up to now I couldn't manage to find out if that is a shortcoming of my understanding/setup or a shortcoming of the athn driver or a shortcoming of the hardware. Setup: Bridge--with--athn0---vether0---vr1 Dhcp server listens on vether0 Cheers Eike -- Eike Lantzsch ZP6CGE
Re: Problem with pftop
With the latest version of ~current/amd64 (#1050 as of June 7th, 2015) I get the following error trying to run pftop (noticed on two different PCs, one of the dmesgs below): ~ $ sudo pftop Error Reading status (DIOCGETSTATUS): Permission denied Did I miss any significant changes here? Any ideas or should I just wait for the next update of ~current? the pf status ioctl ABI changed. Wait for a pkg tree which matches base on the other side of this.
Re: Problem with pftop
On Sun, 07 Jun 2015 10:48:29 -0600 Theo de Raadt dera...@cvs.openbsd.org wrote: ~ $ sudo pftop Error Reading status (DIOCGETSTATUS): Permission denied Did I miss any significant changes here? Any ideas or should I just wait for the next update of ~current? the pf status ioctl ABI changed. Wait for a pkg tree which matches base on the other side of this. OK - will stick closely to ~current anyway. Thanks for the quick info!
Re: sudoers documentation bug?
On Sat, Jun 06, 2015 at 10:42:16PM +0200, Max Fillinger wrote: Then user can do sudo echo test, but sudo -l prints (root) /bin/echo te st. Sorry, I was talking nonsense here. Line continuation is treated as a space in the sense that it seperates two arguments, so the output of sudo -l is correct.
Re: alix 1e - 2,4/5 GHz Wifi card
On Sun, Jun 07, 2015 at 05:55:16PM +0200, s...@asm68k.org wrote: - provide a network in the 2,4 GHz and the 5 GHz bandwidths at the same time We don't support this. To fulfill this requirement you'll need two cards. - has just one antenna (the alix 1e has just one slot for antenna) And you'll need at least two antennas. - is supported by OpenBSD (obviously, version does not matter) - fits into a mini-pci slot Can someone help me to find such a card? `man rel(4)` did not show any useable cards. Sorry, it's not going to work exactly how you imagine. I would recommend you try hunting down 2 supported athn(4) cards. Search for the chips listed in the athn(4) man page (i.e. up to AR9287, anything more recent won't work yet). Finding them is not very easy unfortunately but it's the best supported hardware for access points right now. And along with that get a suitable board with either 2 minipci slots (e.g. some alix boards do) or 2 minipcie slots (e.g. APU) depending on which kind of cards you found. And plug one antenna onto each card. There are cases that come with 2 antenna holes drilled, if drilling them yourself is not an option.
Re: sudoers documentation bug?
It is far too late in the game to change this behavior as you will break people's working sudoers files. - todd
alix 1e - 2,4/5 GHz Wifi card
Hello mailing list users, I was asked to repeat this question here. I am searching a wifi network card, which has the following properties: - provide a network in the 2,4 GHz and the 5 GHz bandwidths at the same time - has just one antenna (the alix 1e has just one slot for antenna) - is supported by OpenBSD (obviously, version does not matter) - fits into a mini-pci slot Can someone help me to find such a card? `man rel(4)` did not show any useable cards. Thank you in advance and kind regards, Dirk
Problem with pftop
Hi misc@! With the latest version of ~current/amd64 (#1050 as of June 7th, 2015) I get the following error trying to run pftop (noticed on two different PCs, one of the dmesgs below): ~ $ sudo pftop Error Reading status (DIOCGETSTATUS): Permission denied Did I miss any significant changes here? Any ideas or should I just wait for the next update of ~current? Best, STEFAN ## OpenBSD 5.7-current (GENERIC.MP) #1050: Sun Jun 7 01:19:03 MDT 2015 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 3203203072 (3054MB) avail mem = 3102314496 (2958MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (68 entries) bios0: vendor LENOVO version 79ETC9WW (2.09 ) date 12/22/2006 bios0: LENOVO 2007VG2 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET SLIC BOOT SSDT SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) LURT(S3) DURT(S3) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) PCI1(S4) USB0(S3) USB1(S3) USB2(S3) USB7(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1994.69 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36, CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR cpu0: 4MB 64b/line 16-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 166MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1994.34 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36, CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR cpu1: 4MB 64b/line 16-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 2, remapped to apid 1 acpimcfg0 at acpi0 addr 0xf000, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus 4 (EXP2) acpiprt5 at acpi0: bus 12 (EXP3) acpiprt6 at acpi0: bus 21 (PCI1) acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpipwrres0 at acpi0: PUBS, resource for USB0, USB2, USB7 acpitz0 at acpi0: critical temperature is 127 degC acpitz1 at acpi0: critical temperature is 99 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model 92P1139 serial 2887 type LION oem Panasonic acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 acpidock0 at acpi0: GDCK not docked (0) cpu0: Enhanced SpeedStep 1994 MHz: speeds: 2000, 1667, 1333, 1000 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel 82945GM Host rev 0x03 ppb0 at pci0 dev 1 function 0 Intel 82945GM PCIE rev 0x03: msi pci1 at ppb0 bus 1 radeondrm0 at pci1 dev 0 function 0 ATI Radeon Mobility X1300 M52-64 rev 0x00 drm0 at radeondrm0 radeondrm0: apic 1 int 16 azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x02: msi azalia0: codecs: Analog Devices AD1981HD, Conexant/0x2bfa, using Analog Devices AD1981HD audio0 at azalia0 ppb1 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x02: msi pci2 at ppb1 bus 2 em0 at pci2 dev 0 function 0 Intel 82573L rev 0x00: msi, address 00:15:58:81:15:fb ppb2 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x02: msi pci3 at ppb2 bus 3 wpi0 at pci3 dev 0 function 0 Intel PRO/Wireless 3945ABG rev 0x02: msi, MoW2, address 00:19:d2:85:6f:4d ppb3 at pci0 dev 28 function 2 Intel 82801GB PCIE rev 0x02: msi pci4 at ppb3 bus 4 xhci0 at pci4 dev 0 function 0 Renesas uPD720202 xHCI rev 0x02: msi usb0 at xhci0: USB revision 3.0 uhub0 at usb0 Renesas xHCI root hub rev 3.00/1.00 addr 1 ppb4 at pci0 dev 28 function 3 Intel 82801GB PCIE rev 0x02: msi pci5 at ppb4 bus 12 uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x02: apic 1 int 16 uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x02: apic 1 int 17 uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x02: apic 1 int 18 uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x02: apic 1 int 19 ehci0 at pci0 dev 29 function 7 Intel 82801GB USB rev 0x02: apic 1 int 19 usb1 at ehci0: USB revision 2.0 uhub1 at usb1 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb5 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0xe2 pci6 at ppb5 bus 21 cbb0 at pci6 dev 0 function 0 TI PCI1510 CardBus rev 0x00: apic 1 int 16 cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 22 device 0 cacheline 0x8, lattimer 0xb0 pcmcia0 at cardslot0 pcib0 at
Re: AnonCVS and -rHEAD
On Sun, 07 Jun 2015 22:27:05 -0400 Nick Holland n...@holland-consulting.net wrote: On 06/07/15 20:14, bytevolc...@safe-mail.net wrote: Hello all, I noticed on http://www.openbsd.org/faq/faq5.html#BldGetSrc that there is information about preloading the tree, but does not mention that getting to -current requires -rHEAD at least the first time using 'cvs update' after pre-loading the tree with the source files from the last release. I discovered (the semi-hard way) that to get to -current, I needed -rHEAD to be specified in the command line. This is after pre-loading the tree, because the (src/sys/xenocara).tar.gz files all have a check out of OPENBSD_5_7 (or whatever -stable release), Where did you get these source files? Just checked the ones on the mirrors, they do not have such a tag on them. I'll check the CDs..um...not tonight. I would much prefer using the -A option over -rHEAD, as your goal is to clear and ignore any release tags. I am quite certain the ones I got were from the ftp mirror. I've had them for almost a month, but I recall getting them from ftp.iinet.net.au. Now that you mention it, this is actually the first time I've encountered such a thing while updating my copy of the source tree to -current; I've never had to do this with tarballs of earlier releases. frozen to that point at the time of releasing. Running cvs up simply gets me to the latest -stable. which...isn't a bad default, really (assuming the CDs shipped as you indicated) I am in some agreement with this; it would certainly make it easier not having to change the -rOPENBSD_x_x option in the .cvsrc every time you upgrade. My .cvsrc (between the hyphen lines): # $OpenBSD: dot.cvsrc,v 1.1 2013/04/01 16:55:26 espie Exp $ # cvs -q -danon...@anoncvs.au.openbsd.org:/cvs diff -up update -Pd for your purposes, I'd make that -PAd to clear the release tag. Sounds like a plan to me. checkout -P It seems the (src/sys/xenocara).tar.gz files are not in the snapshots directory of any of the FTP mirrors I've seen. correct. This would wrongly imply that This tar file was used to build these snapshots, and that would be wrong. And...if you want to download the entire -current source tree, just do it with cvs(1). True. I've always just been preloading the tree with the release and running cvs update anyway. Should this be mentioned in the documentation or is it just me? 5.1, under Snapshots kinda covers this, I think. Nick. No mention of the sort of thing I was talking about over there; just a description of -release, -current, -stable. Anyway, thanks for the information. It's given me some food for thought.
Re: Mount point for ntfs_3g mounted drive missing after failed umount
On Sun, Jun 07, 2015 at 07:46:43PM -0500 or thereabouts, Theodore Wynnychenko wrote: Hello I have been trying to use the ntfs_3g fuse package to get write access to an ntfs drive. While I have had no issues mounting the drive and writing to it, occasionally I have problems when trying to unmount the drive. I used to see something similar with 5.6-stable with a usb drive but no longer with 5.7-stable. On 5.6 # mount still listed the drive as mounted. # umount fusefs unmounted for me perfectly well. Good Luck Moss Basically, I want to make a more portable copy of my data. I have an external eSata drive. The drive is NOT mounted during boot. I have a cron job that runs a script and makes a copy of my data to the external drive. The script is simple: --- #!/bin/sh /usr/local/bin/ntfs-3g /dev/sd2i /home/backup /usr/local/bin/rsync --recursive --archive --delete /home/data/ /home/backup/data /sbin/umount /home/backup --- It appears that when there aren't many new or changed files, everything is fine. However, if there is a lot of new data to copy, the umount command at the end returns an error, and the mount point for the drive is missing. Running the commands manual produces the same error. E.g.: # /usr/local/bin/ntfs-3g /dev/sd2i /home/backup no errors # /usr/local/bin/rsync --recursive --archive --delete /home/data/ /home/backup/data no errors # /sbin/umount /home/backup umount: /home/backup: Device busy But, if I check with df, the fusefs mounted as /home/backup is gone. And: # ls /home/backup/ ls: /home/backup/: No such file or directory But: # mkdir /home/backup mkdir: /home/backup: File exists Reboot the system, and the missing mount point (/home/backup) reappears. I was thinking that maybe this has something to do with the writing of data to the ntfs volume not being complete when the umount command is executed. So, I did add a sleep 600 into the shell script; and it seemed to unmount cleanly (although, I am not sure if it was the time delay, or just a lack of new data for rsync to copy). However, that doesn't address the underlying issue. Also I don't understand why the mount point being used by ntfs_3g would be missing with ls but exists with mkdir. I have gone through the package's man pages and could find nothing that appears relevant. I would appreciate any ideas on how to proceed. Thanks [demime 1.01d removed an attachment of type application/x-pkcs7-signature which had a name of smime.p7s]
(Potentially dangerous) ATA timeout with 'atactl secerase'
Hello, I am not sure if this should go into tech@ since I cannot work out a decent fix for this yet, but atactl secerase has a potentially dangerous 1000mS timeout set. Potentially dangerous, because this timeout results in some misinformation being provided to the caller or user: # atactl wd1 secerase user User password: wd1 (pciide1:1:0): timeout type: ata c_bcount: 512 c_skip: 0 atactl: ATA command timed out wd1: flush cache command timeout # The HDD light remains solid ON for a long period of time, suggesting the erase is continuing despite the command returning early, with error. I was fortunate to be able to recover the current 160GB drive by using atactl secunlock and atactl secdisable. My 80GB test drive, as it seems, wasn't so lucky. I have found part of the problem in src/sbin/atactl/atactl.c in the device_sec_erase() function: ... req.command = ATA_SEC_ERASE_UNIT; req.timeout = 1000; req.flags = ATACMD_WRITE; req.databuf = (caddr_t)pwd; req.datalen = sizeof(pwd); ... req.timeout = 1000; One problem is I don't know what this value should be, to provide no timeout. Given that a SECURITY ERASE UNIT command may not return until several minutes, or even hours, depending on how long the actual erase is, and given the potential to brick a drive, it seems that the timeout here does more harm than good. Running -current (cvs update performed 7/6/15; built 7/6/15). I have not modified any source files from the originals. This is a long-running regression; I have tested this back to 5.5-release, although in earlier releases, I noticed it seems to cancel the erase once the timeout is up. = OpenBSD 5.7-current (GENERIC.MP) #0: Sun Jun 7 17:53:51 UTC 2015 r...@m.my.domain:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 2120744960 (2022MB) avail mem = 2052657152 (1957MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xdc010 (36 entries) bios0: vendor LENOVO version 2OKT48AUS date 11/13/2008 bios0: LENOVO 8982A48 acpi0 at bios0: rev 0 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP TCPA MCFG APIC BOOT SSDT acpi0: wakeup devices EXP1(S4) EXP2(S4) PCIB(S5) KBC0(S4) MSE0(S4) COMA(S5) AC97(S1) PWRB(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) EUSB(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimcfg0 at acpi0 addr 0xe000, bus 0-9 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Pentium(R) Dual CPU E2140 @ 1.60GHz, 1596.26 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR cpu0: 1MB 64b/line 4-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 199MHz cpu0: mwait min=64, max=64, C-substates=0.2.2, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Pentium(R) Dual CPU E2140 @ 1.60GHz, 1596.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF,SENSOR cpu1: 1MB 64b/line 4-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (PEG_) acpiprt2 at acpi0: bus 2 (EXP1) acpiprt3 at acpi0: bus 4 (EXP2) acpiprt4 at acpi0: bus 10 (PCIB) acpicpu0 at acpi0: PSS acpicpu1 at acpi0: PSS acpibtn0 at acpi0: PWRB cpu0: Enhanced SpeedStep 1596 MHz: speeds: 800, 600 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel 82946GZ Host rev 0x02 ppb0 at pci0 dev 1 function 0 Intel 82946GZ PCIE rev 0x02: msi pci1 at ppb0 bus 1 vga1 at pci0 dev 2 function 0 Intel 82946GZ Video rev 0x02 intagp0 at vga1 agp0 at intagp0: aperture at 0xc000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 inteldrm0: 1024x768 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x01: msi azalia0: codecs: Analog Devices/0x1986 audio0 at azalia0 ppb1 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x01: msi pci2 at ppb1 bus 2 ppb2 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x01: msi pci3 at ppb2 bus 4 bge0 at pci3 dev 0 function 0 Broadcom BCM5786 rev 0x02, BCM5754/5787 A2 (0xb002): msi, address 00:01:6c:9d:47:eb brgphy0 at bge0 phy 1: BCM5787 10/100/1000baseT PHY, rev. 0 uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x01: apic 2 int 23 uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x01: apic 2 int 19 uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x01: apic 2 int 18 uhci3 at pci0 dev 29 function 3
AnonCVS and -rHEAD
Hello all, I noticed on http://www.openbsd.org/faq/faq5.html#BldGetSrc that there is information about preloading the tree, but does not mention that getting to -current requires -rHEAD at least the first time using 'cvs update' after pre-loading the tree with the source files from the last release. I discovered (the semi-hard way) that to get to -current, I needed -rHEAD to be specified in the command line. This is after pre-loading the tree, because the (src/sys/xenocara).tar.gz files all have a check out of OPENBSD_5_7 (or whatever -stable release), frozen to that point at the time of releasing. Running cvs up simply gets me to the latest -stable. My .cvsrc (between the hyphen lines): # $OpenBSD: dot.cvsrc,v 1.1 2013/04/01 16:55:26 espie Exp $ # cvs -q -danon...@anoncvs.au.openbsd.org:/cvs diff -up update -Pd checkout -P It seems the (src/sys/xenocara).tar.gz files are not in the snapshots directory of any of the FTP mirrors I've seen. Should this be mentioned in the documentation or is it just me?
Mount point for ntfs_3g mounted drive missing after failed umount
Hello I have been trying to use the ntfs_3g fuse package to get write access to an ntfs drive. While I have had no issues mounting the drive and writing to it, occasionally I have problems when trying to unmount the drive. Basically, I want to make a more portable copy of my data. I have an external eSata drive. The drive is NOT mounted during boot. I have a cron job that runs a script and makes a copy of my data to the external drive. The script is simple: --- #!/bin/sh /usr/local/bin/ntfs-3g /dev/sd2i /home/backup /usr/local/bin/rsync --recursive --archive --delete /home/data/ /home/backup/data /sbin/umount /home/backup --- It appears that when there aren't many new or changed files, everything is fine. However, if there is a lot of new data to copy, the umount command at the end returns an error, and the mount point for the drive is missing. Running the commands manual produces the same error. E.g.: # /usr/local/bin/ntfs-3g /dev/sd2i /home/backup no errors # /usr/local/bin/rsync --recursive --archive --delete /home/data/ /home/backup/data no errors # /sbin/umount /home/backup umount: /home/backup: Device busy But, if I check with df, the fusefs mounted as /home/backup is gone. And: # ls /home/backup/ ls: /home/backup/: No such file or directory But: # mkdir /home/backup mkdir: /home/backup: File exists Reboot the system, and the missing mount point (/home/backup) reappears. I was thinking that maybe this has something to do with the writing of data to the ntfs volume not being complete when the umount command is executed. So, I did add a sleep 600 into the shell script; and it seemed to unmount cleanly (although, I am not sure if it was the time delay, or just a lack of new data for rsync to copy). However, that doesn't address the underlying issue. Also I don't understand why the mount point being used by ntfs_3g would be missing with ls but exists with mkdir. I have gone through the package's man pages and could find nothing that appears relevant. I would appreciate any ideas on how to proceed. Thanks [demime 1.01d removed an attachment of type application/x-pkcs7-signature which had a name of smime.p7s]
Re: sudoers documentation bug?
On Sun, Jun 07, 2015 at 07:20:39AM +0900, Joel Rees wrote:
Okay, I took the bait.
You need to to test for 1 in two places to avoid an out of bounds
read (even when just experimenting ;-)
tech@ is a better place for this, I don't think millert reads misc@
-Otto
On Sat, Jun 6, 2015 at 6:29 PM, Joel Rees joel.r...@gmail.com wrote:
I'm not sure what your question is, or even if you have one.
On Fri, Jun 5, 2015 at 6:58 PM, ertetlen barmok
ertetlenbar...@safe-mail.net wrote:
Hello!
http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man5/sudoers.5?query=sudoers
Long lines can be continued with a backslash (???\???) as the last
character on the line.
problem: but sudoers allows me to put an ex.: space character after the
\, so the documentation is not correct?
it still lists it in sudo -l
Are you saying that sudo will recognize a line with \ as the last
two characters before the newline as a continued line?
I have an included sudoers file that I can conveniently split and
continue a line on.
Burying a backslash in the line makes both visudo and sudo complain
about the syntax, of course.
Backslash as the final character on the line continues the line, per the spec.
Backslash followed by whitespace also continues the line.
So I poked around in the code for sudo and made this trivial edit to
fileops,c:
--
$ diff -u fileops_orig.c fileops.c
--- fileops_orig.c Sun Jun 7 06:48:07 2015
+++ fileops.c Sun Jun 7 06:26:51 2015
@@ -168,7 +168,8 @@
/* Trim leading and trailing whitespace/newline */
len = strlen(buf);
- while (len 0 isspace((unsigned char)buf[len - 1]))
+ while (len 0 isspace((unsigned char)buf[len - 1])
+ (buf[len - 2] != '\\'))
buf[--len] = '\0';
for (cp = buf; isblank(*cp); cp++)
continue;
--
make induces compiling with no errors, make install results in new
binaries under /usr/bin , so I assume the edit has some effect. But it
does not change the behavior of sudo.
So I try this, assuming that it will also reveal no change:
--
$ diff -u fileops_orig.c fileops.c
--- fileops_orig.c Sun Jun 7 06:48:07 2015
+++ fileops.c Sun Jun 7 06:40:53 2015
@@ -157,7 +157,7 @@
sudo_parseln(fp)
FILE *fp;
{
-size_t len;
+size_t len, mark;
char *cp = NULL;
static char buf[LINE_MAX];
@@ -168,8 +168,16 @@
/* Trim leading and trailing whitespace/newline */
len = strlen(buf);
- while (len 0 isspace((unsigned char)buf[len - 1]))
- buf[--len] = '\0';
+ mark = len;
+ while (len 0 isspace((unsigned char)buf[len - 1])) {
+ if ( buf[len - 2] == '\\' ) {
+ len = mark;
+ break;
+ }
+ else
+ --len;
+ }
+ buf[len] = '\0';
for (cp = buf; isblank(*cp); cp++)
continue;
}
--
and my assumption proves correct.
In one careful interpretation, backslash is a continuation character,
not a general character escape, in sudo's grammar. (No true character
string type in the spec.) Whitespace has no specific effect. So
whitespace after a backslash would be a valid continuation.
It appears that this is the interpretation implemented in sudo, and
I'd really prefer to work on my wifi problem, over digging into toke.l
and gram.y over a quibble about the spec.
Unless someone can find a true vulnerability that can be fixed by
making the spec conform to the interpretation of a backslash as a
general character escape, at any rate. I'm having a hard time
imagining any such vulnerability right now.
--
Joel Rees
Be careful when you look at conspiracy.
Look first in your own heart,
and ask yourself if you are not your own worst enemy.
Arm yourself with knowledge of yourself, as well.
SAMBA CIFS/SMBMOUNT
Hi guys! Question about OpenBSD 5.7 amd64. How to mount shared device via samba fs? I tried in this way: # mount -t cifs //192.168.2.111/raid5/download /BACKUP -o username=user,password=passwd and this returns: mount: no mount helper program found for cifs: No such file or directory Thank You for reply.
Re: SAMBA CIFS/SMBMOUNT
Max Power said: How to mount shared device via samba fs? You may use sharity-light package. -- Dmitrij D. Czarkoff
Re: AnonCVS and -rHEAD
On 06/07/15 20:14, bytevolc...@safe-mail.net wrote: Hello all, I noticed on http://www.openbsd.org/faq/faq5.html#BldGetSrc that there is information about preloading the tree, but does not mention that getting to -current requires -rHEAD at least the first time using 'cvs update' after pre-loading the tree with the source files from the last release. I discovered (the semi-hard way) that to get to -current, I needed -rHEAD to be specified in the command line. This is after pre-loading the tree, because the (src/sys/xenocara).tar.gz files all have a check out of OPENBSD_5_7 (or whatever -stable release), Where did you get these source files? Just checked the ones on the mirrors, they do not have such a tag on them. I'll check the CDs..um...not tonight. I would much prefer using the -A option over -rHEAD, as your goal is to clear and ignore any release tags. frozen to that point at the time of releasing. Running cvs up simply gets me to the latest -stable. which...isn't a bad default, really (assuming the CDs shipped as you indicated) My .cvsrc (between the hyphen lines): # $OpenBSD: dot.cvsrc,v 1.1 2013/04/01 16:55:26 espie Exp $ # cvs -q -danon...@anoncvs.au.openbsd.org:/cvs diff -up update -Pd for your purposes, I'd make that -PAd to clear the release tag. checkout -P It seems the (src/sys/xenocara).tar.gz files are not in the snapshots directory of any of the FTP mirrors I've seen. correct. This would wrongly imply that This tar file was used to build these snapshots, and that would be wrong. And...if you want to download the entire -current source tree, just do it with cvs(1). Should this be mentioned in the documentation or is it just me? 5.1, under Snapshots kinda covers this, I think. Nick.
