Re: accessing webcam as normal user

2017-02-13 Thread Neil Telford
Just to clarify, what was the exact line you added to /etc/fstab ?

Thanks.



--
View this message in context: 
http://openbsd-archive.7691.n7.nabble.com/accessing-webcam-as-normal-user-tp313074p313091.html
Sent from the openbsd user - misc mailing list archive at Nabble.com.



Re: accessing webcam as normal user

2017-02-13 Thread Mihai Popescu
> I'm wondering how to access my webcam as a normal user.

I have added /dev/video0 in file /etc/fbtab after all the existing devices.
I'm not sure this is the best option.



Re: accessing webcam as normal user

2017-02-13 Thread Alexander Hall

On 02/13/17 20:46, Neil Telford wrote:

Just to clarify, what was the exact line you added to /etc/fstab ?


It's fbtab, not fstab.

$ man fbtab

/Alexander



Thanks.



--
View this message in context: 
http://openbsd-archive.7691.n7.nabble.com/accessing-webcam-as-normal-user-tp313074p313091.html
Sent from the openbsd user - misc mailing list archive at Nabble.com.




Re: accessing webcam as normal user

2017-02-13 Thread Raf Czlonka
On Mon, Feb 13, 2017 at 01:22:30PM GMT, Neil Telford wrote:
> Hi,
> 
> I'm wondering how to access my webcam as a normal user. I verified that it
> does work, but I can only access it as root. Therefore, it is currently not
> available for web-based video calls.
> 
> If I run ls -la /dev/video0, it shows:
> 
> crw-r-  1 root  wheel   44,   0 Feb  5 13:35 /dev/video
> 
> As I am a member of the wheel group, I should in theory be able to access
> it, What am I missing here ?

Group write permission.

> Thanks, Neil,.

Raf



Re: Can't install -current on a Dell precision t3500

2017-02-13 Thread Adam Thompson

On 2017-02-13 07:11, STeve Andre' wrote:

I'm puzzled and am asking for help.  I'm attempting to install
the -current snapshot (feb 12) on a Dell precision t3500.  The
install formats a 6T disk very quickly, like in 25 seconds.  Hmm.

   After installing the tar files, installboot fails with a
"Bad magic number in superblock".  If I mount the a partition I
see real data.  Changing to a 160G disk everything works & boots,
but not with the 6T disk.

   The t3500 is a sata 2 machine, as is the 160G disk. The 6T disk
is sata 3, but since I see the OS written to the 6T disk it's been
written out OK so thats not it.  I'm missing something with regards
the size of the disk?   Probably I'm forgetting to include something
relevant but I've been dealing with this last night and am tired.
Clues?


You're missing the fact that a T3500 cannot boot off a disk larger than 
2TB, because it supports legacy BIOS boot only, not UEFI.  It is 
possible you might occasionally get lucky but AFAIK the disk geometry 
messes up the BIOS bootloader pretty much 100% of the time.


The Precision line didn't gain UEFI (i.e. >2TB boot disk support) until 
the Tx6xx series, AFAIK.
If your T3500 has a UEFI boot option, then I'm wrong, and you should be 
able to solve your problem by switching to UEFI.


In theory, creating a 2TB partition would be sufficient, but in practice 
it usually isn't.


My solution to these problems is to leave a small USB stick permanently 
installed and boot off that; the easiest way to manage that in OpenBSD 
that I know of is to mount it at /boot and replace /bsd with a symlink 
to /boot/bsd (after moving /bsd, of course).  This will require some 
manual work before rebooting off the ramdisk, naturally, and works IMHO 
best if you use diskids instead of device paths.


-Adam



Can't install -current on a Dell precision t3500

2017-02-13 Thread STeve Andre'

   I'm puzzled and am asking for help.  I'm attempting to install
the -current snapshot (feb 12) on a Dell precision t3500.  The
install formats a 6T disk very quickly, like in 25 seconds.  Hmm.

   After installing the tar files, installboot fails with a
"Bad magic number in superblock".  If I mount the a partition I
see real data.  Changing to a 160G disk everything works & boots,
but not with the 6T disk.

   The t3500 is a sata 2 machine, as is the 160G disk. The 6T disk
is sata 3, but since I see the OS written to the 6T disk it's been
written out OK so thats not it.  I'm missing something with regards
the size of the disk?   Probably I'm forgetting to include something
relevant but I've been dealing with this last night and am tired.
Clues?

Thanks to all -- STeve Andre'

dmesg
OpenBSD 6.0-current (RAMDISK_CD) #164: Sun Feb 12 14:02:22 MST 2017
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
RTC BIOS diagnostic error 11
real mem = 12865998848 (12269MB)
avail mem = 12472324096 (11894MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xf0450 (77 entries)
bios0: vendor Dell Inc. version "A17" date 05/28/2013
bios0: Dell Inc. Precision WorkStation T3500
acpi0 at bios0: rev 2
acpi0: tables DSDT FACP SSDT APIC BOOT ASF! MCFG HPET TCPA  SLIC SSDT
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Xeon(R) CPU W3680 @ 3.33GHz, .73 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AES,NXE,PAGE1GB,LONG,LAHF,PERF,ITSC,SENSOR,ARAT

cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 731530 Hz
cpu0: apic clock running at 133MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins
ioapic1 at mainbus0: apid 9 pa 0xfec8, version 20, 24 pins
acpiprt0 at acpi0: bus 1 (PCI1)
acpiprt1 at acpi0: bus 2 (PCI2)
acpiprt2 at acpi0: bus 3 (PCI3)
acpiprt3 at acpi0: bus 4 (PCI4)
acpiprt4 at acpi0: bus 5 (PCI5)
acpiprt5 at acpi0: bus 6 (PCI6)
acpiprt6 at acpi0: bus 0 (PCI0)
acpicpu at acpi0 not configured
"PNP0C0C" at acpi0 not configured
"*pnp0c14" at acpi0 not configured
"PNP0401" at acpi0 not configured
"PNP0501" at acpi0 not configured
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel X58 Host" rev 0x22
ppb0 at pci0 dev 1 function 0 "Intel X58 PCIE" rev 0x22: msi
pci1 at ppb0 bus 1
ppb1 at pci0 dev 3 function 0 "Intel X58 PCIE" rev 0x22: msi
pci2 at ppb1 bus 2
vga1 at pci2 dev 0 function 0 "ATI FirePro V4800" rev 0x00
wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation)
"ATI Radeon HD 5600 Audio" rev 0x00 at pci2 dev 0 function 1 not configured
ppb2 at pci0 dev 7 function 0 "Intel X58 PCIE" rev 0x22: msi
pci3 at ppb2 bus 3
"Intel X58 Misc" rev 0x22 at pci0 dev 20 function 0 not configured
"Intel X58 GPIO" rev 0x22 at pci0 dev 20 function 1 not configured
"Intel X58 RAS" rev 0x22 at pci0 dev 20 function 2 not configured
uhci0 at pci0 dev 26 function 0 "Intel 82801JI USB" rev 0x00: apic 8 int 16
uhci1 at pci0 dev 26 function 1 "Intel 82801JI USB" rev 0x00: apic 8 int 17
uhci2 at pci0 dev 26 function 2 "Intel 82801JI USB" rev 0x00: apic 8 int 22
ehci0 at pci0 dev 26 function 7 "Intel 82801JI USB" rev 0x00: apic 8 int 22
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev 
2.00/1.00 addr 1ppb3 at pci0 dev 28 function 0 "Intel 82801JI PCIE" rev 
0x00: msi

pci4 at ppb3 bus 4
ppb4 at pci0 dev 28 function 5 "Intel 82801JI PCIE" rev 0x00
pci5 at ppb4 bus 5
bge0 at pci5 dev 0 function 0 "Broadcom BCM5761" rev 0x10, BCM5761 A1 
(0x5761100): msi, address b8:ac:6f:96:76:63

brgphy0 at bge0 phy 1: BCM5761 10/100/1000baseT PHY, rev. 0
uhci3 at pci0 dev 29 function 0 "Intel 82801JI USB" rev 0x00: apic 8 int 23
uhci4 at pci0 dev 29 function 1 "Intel 82801JI USB" rev 0x00: apic 8 int 17
uhci5 at pci0 dev 29 function 2 "Intel 82801JI USB" rev 0x00: apic 8 int 18
ehci1 at pci0 dev 29 function 7 "Intel 82801JI USB" rev 0x00: apic 8 int 23
usb1 at ehci1: USB revision 2.0
uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev 
2.00/1.00 addr 1

ppb5 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0x90
pci6 at ppb5 bus 6
"Intel 82801JIR LPC" rev 0x00 at pci0 dev 31 function 0 not configured
ahci0 at pci0 dev 31 function 2 "Intel 82801JI AHCI" rev 0x00: msi, AHCI 1.2
ahci0: port 0: 3.0Gb/s
ahci0: PHY offline on port 1
ahci0: port 2: 1.5Gb/s
ahci0: PHY offline on port 3
ahci0: PHY offline on port 4
scsibus0 at ahci0: 32 targets
sd0 at scsibus0 targ 0 lun 0:  SCSI3 
0/direct fixed naa.5000c500676a6709

sd0: 5723166MB, 512 bytes/sector, 

accessing webcam as normal user

2017-02-13 Thread Neil Telford
Hi,

I'm wondering how to access my webcam as a normal user. I verified that it
does work, but I can only access it as root. Therefore, it is currently not
available for web-based video calls.

If I run ls -la /dev/video0, it shows:

crw-r-  1 root  wheel   44,   0 Feb  5 13:35 /dev/video

As I am a member of the wheel group, I should in theory be able to access
it, What am I missing here ?

Thanks, Neil,.






--
View this message in context: 
http://openbsd-archive.7691.n7.nabble.com/accessing-webcam-as-normal-user-tp313074.html
Sent from the openbsd user - misc mailing list archive at Nabble.com.



Re: fmt replaces utf8 spaces for ascii ones

2017-02-13 Thread Walter Alejandro Iglesias
On Sun, Feb 12, 2017 at 10:21:11PM -0800, Eric Pruitt wrote:
> Unfortunately I do not have access to an OpenBSD machine to verify
> whether or not its fmt does the correct thing.

By the way, if you try your example in openbsd take in care obsd printf
won't recognize \u00a0.  Use '\xc2\xa0' instead.

I was trying your example in a linux machine obtaining your same results.
But I did it mostly because I was curious about the other difference: the
GNU version inserts the new line 'in' the number assigned by -w, giving
you in this case a 19 wide line as result.  The obsd version breaks the
line in the following character giving you a 20 chars wide line.

Back to the original topic.  What made me hesitate if 'feature' or 'bug'
was the man page.  The following two paragraphs made me think converting
all spaces to ascii could be desired as a practical solution:

 fmt is meant to format mail messages prior to sending, but may also
 be useful for other simple tasks...

 The program was designed to be simple and fast – for more complex
 operations, the standard text processors are likely to be more
 appropriate.



build libtorrent fail

2017-02-13 Thread Thuban
Hello,
I try again to build libtorrent [1].
I can't have ./configure to find the boost-python library.

The .configure file has been modified like this :

- CXXFLAGS="$CXXFLAGS -ftemplate-depth=120"
+ CXXFLAGS="$CXXFLAGS"

Then, I try to build like this :

export LDFLAGS="-L /usr/lib -L/usr/local/lib"
export CXXFLAGS="-I /usr/include -I/usr/local/include"

./configure \
--with-boost=/usr/local/ \
--with-boost-system=boost_system-mt \
--enable-python-binding \
--with-boost-python=boost_python-mt \
--disable-static \
--enable-dht \
--enable-pool-allocators \
--with-libiconv \
--disable-debug

Here is the error message :

checking for Python include path... -I/usr/local/include/python3.6m
checking for Python library path... -L/usr/local/lib -lpython3.6m
checking for Python site-packages path...
/usr/local/lib/python3.6/site-packages
checking python extra libraries... -lintl -lpthread  -lutil -lm
checking python extra linking flags... -Wl,--export-dynamic
checking consistency of all components of python development
environment... yes
checking whether the Boost::Python library is available... no
configure: error: Boost.Python library not found. Try using
--with-boost-python=lib.

You may find the full ./configure log here : http://pastebin.com/Ac4SkrEG


Any advice ?

Regards.

[1] : http://libtorrent.org/

--
/Thuban/

[demime 1.01d removed an attachment of type application/pgp-signature which had 
a name of signature.asc]



Re: OpenBSD's HTTPD - I can't figure out how to disable the chroot

2017-02-13 Thread Solène Rapenne

Le 2017-02-13 00:03, tec...@protonmail.com a écrit :

Hello,

I have a special use case for the HTTPD server, I would like to
disable the chroot but can't seem to get it working correctly. Within
httpd.conf, I have tried to set:

chroot "/" ## Instead of default which is: /var/www


root "/var/www/htdocs/web"
#root "/htdocs/web" # Disabled

location "/" {
directory {
index "index.html"
}
}



But I can't access my page until I put it back to normal (uncomment
the # lines and remove the new ones)


Any help would be greatly appreciated. Thanks


hello
the following works for me on -current

chroot "/"
logdir "/var/www/logs/"

server "*" {
listen on * port 8080
root "/var/www/htdocs/"

location "/solene/" {
directory auto index
}
}



Re: OpenBSD's HTTPD - I can't figure out how to disable the chroot

2017-02-13 Thread Kenneth Gober
On Sun, Feb 12, 2017 at 6:03 PM,   wrote:
> I have a special use case for the HTTPD server, I would like to disable
> the chroot but can't seem to get it working correctly.

While I can't help you with your httpd chroot issue, I can suggest that
if you need to access a part of the filesystem outside of /var/www, you
can NFS mount it from yourself.

For example, suppose you have a directory /nfs/archive/dist/OpenBSD, and
you want to serve it via httpd.  You can do something like this:

1. add a line to /etc/exports:
   /nfs/archive/dist/OpenBSD -ro 127.0.0.1

2. start nfsd:
   # rcctl start nfsd

3. remount your data under /var/www:
   # mkdir -p /var/www/htdocs/pub/OpenBSD
   # mount -r 127.0.0.1:/nfs/archive/dist/OpenBSD /var/www/htdocs/pub/OpenBSD

At this point you should be able to chroot to /var/www, and still be able
to access files under /htdocs/pub/OpenBSD.

This may not be the prettiest way to achieve your goal but it's simple
and it works for ftpd.  I assume it would work just as well for httpd.

-ken



Re: Libperl 18?

2017-02-13 Thread Stuart Henderson
On 2017-02-13, Bryan C. Everly  wrote:
> Hi all
>
> I have been trying to nuke and pave my daily driver's OpenBSD partition
> since Feb 5. Trying to install libproxy failed on a bad major (I have 17.1
> and it wants 18.0) for libperl.
>
> I figured this was the normal behavior I have seen from time to time
> running snapshots and I would just wait for the next refresh of the
> snapshot. I did and I reinstalled the bad and userland tools from it but
> I'm still seeing the problem.
>
> Are we having problems with perl in the userland build?

We're not. Where are you getting your snapshot from?