Re: OpenBSD runs only in RAM from a USB Flash Drive
> 30 May, 2019 > > Greetings OpenBSD aficionados, > > As a newbie to OpenBSD, I am delighted to have the chance to interact > with the OpenBSD Mailing Lists community. > Since I am about to install OpenBSD 6.5 (amd64) on a USB Flash Drive for > > the first time, I was wondering if anyone has a solution to the > following conundrum. > > In order to minimize wear on the USB Flash memory, is there a way to > command OpenBSD to always run in RAM, and at shutdown to either save or > not save the session to the USB Flash Drive. > Chris Cappuccio created flashrd https://www.nmedia.net/flashrd/flashrd-faq.html I am not sure how useful it is these days as tmpfs was disabled in the Fall of 2016 https://marc.info/?l=openbsd-misc&m=146980890627188&w=2 You also have https://stable.rcesoftware.com/resflash/ Once upon a time people used Flashboot https://www.mindrot.org/projects/flashboot/ Honestly even SMART capable SSDs are so cheap these days that the only reason I can see you running OpenBSD from a USB Flash drive is to use something like Ubiquiti Networks EdgeRouter LITE. I do use Octeon port of OpenBSD on multiple firewalls around our lab but it is all generic kernel https://www.openbsd.org/octeon.html and I am not very concern that the USB will fail due to the excessive read and write. Cheers, Predrag > For instance, Precise Puppy Linux 5.7.1 has a package called Puppy Event > > Manager. Since Precise Puppy is programmed to run in RAM, you can select > > the 'Save Session' tab and enter the span of minutes for everything in > RAM to be saved to the Precise Puppy SaveFile. > > Best of all, you can enter 0 minutes to only do a save at shutdown. > Perfect for minimizing wear on a USB Flash Drive. > > Please accept my apologies if this issue has already been solved. My > search so far in sites like https://marc.info has come up empty. > > I thank you for your support. > > Best regards, > Hugh >
OpenBSD runs only in RAM from a USB Flash Drive
30 May, 2019 Greetings OpenBSD aficionados, As a newbie to OpenBSD, I am delighted to have the chance to interact with the OpenBSD Mailing Lists community. Since I am about to install OpenBSD 6.5 (amd64) on a USB Flash Drive for the first time, I was wondering if anyone has a solution to the following conundrum. In order to minimize wear on the USB Flash memory, is there a way to command OpenBSD to always run in RAM, and at shutdown to either save or not save the session to the USB Flash Drive. For instance, Precise Puppy Linux 5.7.1 has a package called Puppy Event Manager. Since Precise Puppy is programmed to run in RAM, you can select the 'Save Session' tab and enter the span of minutes for everything in RAM to be saved to the Precise Puppy SaveFile. Best of all, you can enter 0 minutes to only do a save at shutdown. Perfect for minimizing wear on a USB Flash Drive. Please accept my apologies if this issue has already been solved. My search so far in sites like https://marc.info has come up empty. I thank you for your support. Best regards, Hugh
Re: Prefered manpage idioms?
On Thu, May 30, 2019 at 01:37:41PM -0600, Theo de Raadt wrote: > Jason McIntyre wrote: > > > i don;t think we can (or should) attempt to police this. > > Ouch, that typo really triggered my ADD, let's hope you don't make > similar errors in our manual pages. Yep, let's stick to seperate or implimentation as admissible typos.
Re: mirroring firmware.openbsd.org
Lyndon Nerenberg wrote: > Our firewalls can't connecto to firmware.openbsd.org (by design). Always a choice to make. > Is there a way to mirror the contents of firmware.openbsd.org? They are just web servers, so a wget will collect everything. > It would be nice if these files were available in the usual OpenBSD > mirrors, since we already mirror those and could just point fw_update > at our internal mirror host. firmware.openbsd.org is independent and segregated from official OpenBSD upstream and mirroring since we don't own the data in the files and logistics of getting that resolved for all files (and maintained for the future) is implausible. > But something like an rsync- or ftp-able > firmware.openbsd.org source would be just fine. They answer to http just fine.
mirroring firmware.openbsd.org
Our firewalls can't connecto to firmware.openbsd.org (by design). Is there a way to mirror the contents of firmware.openbsd.org? It would be nice if these files were available in the usual OpenBSD mirrors, since we already mirror those and could just point fw_update at our internal mirror host. But something like an rsync- or ftp-able firmware.openbsd.org source would be just fine. --lyndon
Re: How to synchronise 2 spamd instances
Hello, I'm back again with spamd synchronisation. I made further tests and it seems to me that only new entries in spamd are synchronised. All existing entries before the synchronisation and not sent to the other spamd instance. Is it supposed to work like that ? Thank you Le dimanche 26 mai 2019 à 22:49:25 UTC+2, Sean Kamath a écrit : On May 26, 2019, at 04:41, Mik J wrote: > > Hello, > > I'm coming back on this topic. I added the -K option > # /usr/libexec/spamd -v -s 5 -S 5 -w 1 -G5:24:2400 -l 127.0.0.1 -h > myhost.mydomain.org -y vmx0 -Y myhost2.mydomain.org -K /etc/mail/spamd.key -n > ABCD > # spamd: need key and certificate for TLS > > So it seems it expects some kind of certificat/privatekey rather than a key > > Does anyone uses the -K option successfully ? Yes. :-). Looks like you forgot the '-C /etc/ssl/.crt’ option. Granted, this is on 6.3. My full args are: -h -v -G 2:4:864 -y vio0 -Y -K /etc/ssl/private/.key -C /etc/ssl/.crt Works fine. Sean > So far I didn't manage to make the synchro to work. udp packets on port 8025 > are not dropped. > However spamd doesn't seem to send any 8025/udp packet at all. > > Regards > > Le mardi 23 avril 2019 à 02:57:31 UTC+2, Rudy Baker >a écrit : > > On Mon, Apr 22, 2019, 10:43 AM Thuban, wrote: > >> * Otto Moerbeek le [21-04-2019 12:49:07 +0200]: >>> On Sun, Apr 21, 2019 at 09:53:52AM +, Mik J wrote: >>> Hello, I read the man but it's not so clear to me https://man.openbsd.org/spamd#SYNCHRONISATION a) I chose unicast synchronisation but I don't know which port should >> I open on the firewall ? Is it going to use the spamd-cfg service ? >>> >>> It will use spamd-sync (udp port 8025) >> >> Good to know, I was blocking this traffic. It might be interesting to >> add a word about this in the manpage, what do you think? >> > > tcpdump -nettti pflog0 > > That command tells you if anything is being blocked. I normally start > there. You would have seen port 8025 being blocked right away > >> >> >
Re: firefox, sndiod and pledge
On 2019-05-30, Hrvoje Popovski wrote: > Hi all, > > i'm not sure is this intended or not, but if sndiod isn't running and if > i want to open youtube video with firefox i got this log > firefox[54192]: pledge "tty", syscall 54 and firefox crashes > when sndiod is running everything seems fine .. Similar with chromium's main process and audio. Maybe it would be nice if libsndio had an option to say "I'm a pledged program, error out instead of trying to talk to the device direct and killing the process" ... But then again, in both cases (chromium/firefox) the main process already has a "kitchen-sink" pledge.
Re: Prefered manpage idioms?
Jason McIntyre wrote: > i don;t think we can (or should) attempt to police this. Ouch, that typo really triggered my ADD, let's hope you don't make similar errors in our manual pages.
Re: Prefered manpage idioms?
On Thu, May 30, 2019 at 09:09:58PM +0200, Marc Espie wrote: > On Thu, May 30, 2019 at 07:29:55PM +0100, Jason McIntyre wrote: > > i think any of man page, manual page, or manual is fine. > > > > > 2. Standard output > > > > > > Is it: > > > Print to standard output/error > > > tee(1) > > > Print to the standard output/error > > > cat(1), echo(1) > > > Print to stdout/stderr > > > bzcat(1) > > > > > > > these are all fine, i think. > > IMO, these are highly contextual. > agreed. > "End user commands" will tend to say standard output or error. > > stdout and stderr *are* programmer's idioms, so I would be surprised > to see them in less technical commands. > i'm pretty sure you'll find stdout/stderr scattered all over userland docs. the post itself quoted bzcat. i don;t think we can (or should) attempt to police this. jmc
Re: Prefered manpage idioms?
On Thu, May 30, 2019 at 07:29:55PM +0100, Jason McIntyre wrote: > i think any of man page, manual page, or manual is fine. > > > 2. Standard output > > > > Is it: > > Print to standard output/error > > tee(1) > > Print to the standard output/error > > cat(1), echo(1) > > Print to stdout/stderr > > bzcat(1) > > > > these are all fine, i think. IMO, these are highly contextual. "End user commands" will tend to say standard output or error. stdout and stderr *are* programmer's idioms, so I would be surprised to see them in less technical commands.
Re: Prefered manpage idioms?
On Thu, May 30, 2019 at 10:16:12PM +1000, Stephen Gregoratto wrote: > When I'm writing new manpages, I like to draw inspiration from the > documentation of similar programs. The problem is that many manpages > have different ways of saying the same thing, probably due to their > authors and time period they were written in. > > So, I'd like to ask what your preferred choice is of the following > common idioms I keep finding: > hi. > 1. Manpage > > Is it: > man page > man-page > manpage > reference > manual > UNIX??? Programmers Manual > ...on second thought, maybe not > i think any of man page, manual page, or manual is fine. > 2. Standard output > > Is it: > Print to standard output/error > tee(1) > Print to the standard output/error > cat(1), echo(1) > Print to stdout/stderr > bzcat(1) > these are all fine, i think. > Bonus Round: > Print to ... > Write to ... > Print on ... > readlink(1) > > 3. Program arguments > > Is it: > Argument > echo(1) > Operand > printf(1), also echo(1)? also fine. i think we just have to accept that there's more than one way to write things. we try to keep things consistent where it makes sense, but i think we need to allow for some variation too. jmc
Re: Modern browser for OpenBSD powerpc
Hi Jordan, Jordan Geoghegan wrote: If you're going down that path, you should see if you can get TenFourFox to compile. TenFourFox does have a jit and supports altivec. http://www.floodgap.com/software/tenfourfox/ https://github.com/classilla/tenfourfox I do know, having contributed to TenFourFox myself. However, things are not so easy: TFF is optimized specifically for one Mac version, 10.4 and PowerPC. While I assume that the JIT can be generalized and implanted into ArcticFox (or maybe even into official FireFox?) it is added and #ifdef'd specifically for Mac, so not easy at all. ArcticFox, while intending to target also older macs (but not 10.4) intends to remain Unix compatible and portable! We are already importing endian fixes and AltiVec optimizations, but the JIT will be harder. So, in case, patches for ArcticFox are appreciated. Riccardo
Re: Modern browser for OpenBSD powerpc
Hi Henry, Henry Bonath wrote: Here's my build info for 6.5 PowerPC: pkg list: autoconf--%2.13 dbus-glib-- g++--%4.9 gcc--%4.9 gmake-- python--%2.7 py-pip-- yasm-- unzip-- zip-- And my .mozconfig: # This Source Code Form is subject to the terms of the Mozilla Public # License, v. 2.0. If a copy of the MPL was not distributed with this # file, You can obtain one at http://mozilla.org/MPL/2.0/. export CC="egcc -O3 -mcpu=7450 -mtune=7450 -maltivec -mabi=altivec -falign-loops=16 -falign-functions=16 -falign-labels=16 -falign-jumps=16" export CXX="eg++ -fpermissive -O3 -mcpu=7450 -mtune=7450 -maltivec -mabi=altivec -falign-loops=16 -falign-functions=16 -falign-labels=16 -falign-jumps=16" mk_add_options MOZ_OBJDIR=/usr/local/src/afbuild/ mk_add_options MOZ_MAKE_FLAGS="-s -j2" ac_add_options --disable-crashreporter ac_add_options --disable-tests ac_add_options --disable-debug ac_add_options --disable-updater ac_add_options --enable-mozril-geoloc ac_add_options --disable-webrtc ac_add_options --disable-safe-browsing ac_add_options --disable-parental-controls ac_add_options --enable-release ac_add_options --disable-necko-wifi ac_add_options --disable-eme ac_add_options --disable-gamepad ac_add_options --enable-dbus ac_add_options --disable-gio ac_add_options --disable-pulseaudio ac_add_options --enable-strip ac_add_options --enable-install-strip ac_add_options --enable-application=browser ac_add_options --with-branding=browser/branding/arcticfox ac_add_options --enable-optimize="-O2" After about 11 hours, the build failed, I *think* it was my machine as I got the error about Virtual memory exhausted.. (I attempted on a Powerbook G4 w/512MB of RAM) I have some XServe G5's around here somewhere, I might load one of those up to see if I can get it to build on that. Yes, you exhausted your RAM. The build needs around 2GB to complete well (later, during the linking of libxul) On my iBook with 1.25GB of RAM I need a lot of swap and linking completes after 20-30 minutes but completes. I have an x86 I would like to test a bit (because it doesn't have SSE3) but with only 1GB of RAM it fails essentially or swaps for hours, depending on compiler optimization. Also, big note: if you are limited in RAM don't issue a Make parallel build, it is useless and consumes more RAM. Thanks for trying, I hope your XServe will do better! Riccardo
Re: firefox, sndiod and pledge
firefox privilege seperation is very rough. The code was written as an afterthought, and it clearly has many cases where processes perform operations directly. I expect the response will be to add pledge "audio" to permit those ioctls, and in time the firefox processes will have essentially all pledges. It is a tremendously long line. The addition of each pledge admits the program isn't a privsep design, and the advertised isolation isn't that great. Reports of these pledge failures could be used by upstream to improve the seperation -- moving the operations to better processes. But I doubt that will happen. Adding privsep to programs after the fact is very difficult. > i'm not sure is this intended or not, but if sndiod isn't running and if > i want to open youtube video with firefox i got this log > firefox[54192]: pledge "tty", syscall 54 and firefox crashes > when sndiod is running everything seems fine .. > > > from kdump > 70068 firefox CALL ioctl(56,AUDIO_STOP,0x1) > 70068 firefox PLDG ioctl, "tty", errno 1 Operation not permitted > > > from gdb > (gdb) bt > #0 ioctl () at -:3 > #1 0x1ad9e350858e in sio_sun_fdopen (fd=31, mode=1, nbio=1) at > /usr/src/lib/libsndio/sio_sun.c:326 > #2 0x1ad9e3508626 in _sio_sun_open (str=Variable "str" is not > available. > ) at /usr/src/lib/libsndio/sio_sun.c:345 > #3 0x1ada4916e16b in WebPGetColorPalette () from > /usr/local/lib/firefox/libxul.so.84.0 > #4 0x1ada4916d47d in WebPGetColorPalette () from > /usr/local/lib/firefox/libxul.so.84.0 > #5 0x1ada47f0f415 in std::__1::__murmur2_or_cityhash 64ul>::__hash_len_0_to_16 () from /usr/local/lib/firefox/libxul.so.84.0 > #6 0x1ada47f0f2d2 in std::__1::__murmur2_or_cityhash 64ul>::__hash_len_0_to_16 () from /usr/local/lib/firefox/libxul.so.84.0 > #7 0x1ada480bdb0c in > cdm::ContentDecryptionModule_10::~ContentDecryptionModule_10 () from > /usr/local/lib/firefox/libxul.so.84.0 > #8 0x1ada480bca8a in > cdm::ContentDecryptionModule_10::~ContentDecryptionModule_10 () from > /usr/local/lib/firefox/libxul.so.84.0 > #9 0x1ada480bf915 in > cdm::ContentDecryptionModule_10::~ContentDecryptionModule_10 () from > /usr/local/lib/firefox/libxul.so.84.0 > #10 0x1ada480c60e9 in > cdm::ContentDecryptionModule_10::~ContentDecryptionModule_10 () from > /usr/local/lib/firefox/libxul.so.84.0 > #11 0x1ada47f63ada in std::__1::__split_buffer std::__1::allocator&>::push_front () from > /usr/local/lib/firefox/libxul.so.84.0 > #12 0x1ada47f5dc46 in std::__1::__split_buffer std::__1::allocator&>::push_front () from > /usr/local/lib/firefox/libxul.so.84.0 > #13 0x1ada47f5da7b in std::__1::__split_buffer std::__1::allocator&>::push_front () from > /usr/local/lib/firefox/libxul.so.84.0 > #14 0x1ada47f9047d in std::__1::__split_buffer std::__1::allocator&>::push_front () from > /usr/local/lib/firefox/libxul.so.84.0 > #15 0x1ada461232f8 in std::__1::function::swap > () from /usr/local/lib/firefox/libxul.so.84.0 > #16 0x1ada46120f51 in std::__1::function::swap > () from /usr/local/lib/firefox/libxul.so.84.0 > #17 0x1ada46134a3e in std::__1::function::swap > () from /usr/local/lib/firefox/libxul.so.84.0 > #18 0x1ada46134b9b in std::__1::function::swap > () from /usr/local/lib/firefox/libxul.so.84.0 > #19 0x1ada46130c32 in std::__1::function::swap > () from /usr/local/lib/firefox/libxul.so.84.0 > #20 0x1ada46133271 in std::__1::function::swap > () from /usr/local/lib/firefox/libxul.so.84.0 > #21 0x1ada4655eb47 in std::__1::vector > >::__append () from /usr/local/lib/firefox/libxul.so.84.0 > #22 0x1ada464dc85f in std::__1::vector std::__1::char_traits, std::__1::allocator >, > std::__1::allocator std::__1::char_traits, std::__1::allocator > > > >::insert std::__1::char_traits, std::__1::allocator >*> > () from > /usr/local/lib/firefox/libxul.so.84.0 > #23 0x1ada4612e92d in std::__1::function::swap > () from /usr/local/lib/firefox/libxul.so.84.0 > #24 0x1adaa590c0a9 in _pt_root (arg=0x1adab98c4100) at ptthread.c:201 > #25 0x1adac18e2771 in _rthread_start (v=Variable "v" is not available. > ) at /usr/src/lib/librthread/rthread.c:96 > #26 0x1ada973897c8 in __tfork_thread () at > /usr/src/lib/libc/arch/amd64/sys/tfork_thread.S:77 > #27 0x in ?? () > Current language: auto; currently asm >
Re: Prefered manpage idioms?
On Thu, May 30, 2019 at 10:16:12PM +1000, Stephen Gregoratto wrote: > When I'm writing new manpages, I like to draw inspiration from the > documentation of similar programs. The problem is that many manpages > have different ways of saying the same thing, probably due to their > authors and time period they were written in. > > So, I'd like to ask what your preferred choice is of the following > common idioms I keep finding: [cut] > 3. Program arguments > > Is it: > Argument > echo(1) > Operand > printf(1), also echo(1)? An argument to a command can be one of three things: 1. An option 2. An option-argument 3. An operand An option is an argument that starts with a dash. An option-argument is an argument to an option that takes an argument. An operand is an argument that is not an option or an option-argument. Example: man -M path ls * -M is an option * path is an option-argument to the -M option * ls is an operand since it's neither an option nor an option-argument. POSIX: Argument: "In the shell command language, a parameter passed to a utility as the equivalent of a single string in the argv array created by one of the exec functions. An argument is one of the options, option-arguments, or operands following the command name." Option: "An argument to a command that is generally used to specify changes in the utility's default behavior." Option-argument: "A parameter that follows certain options. In some cases an option-argument is included within the same argument string as the option-in most cases it is the next argument." Operand: "An argument to a command that is generally used as an object supplying information to a utility necessary to complete its processing. Operands generally follow the options in a command line." https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html -- Kusalananda Sweden
Prefered manpage idioms?
When I'm writing new manpages, I like to draw inspiration from the documentation of similar programs. The problem is that many manpages have different ways of saying the same thing, probably due to their authors and time period they were written in. So, I'd like to ask what your preferred choice is of the following common idioms I keep finding: 1. Manpage Is it: man page man-page manpage reference manual UNIX™ Programmers Manual ...on second thought, maybe not 2. Standard output Is it: Print to standard output/error tee(1) Print to the standard output/error cat(1), echo(1) Print to stdout/stderr bzcat(1) Bonus Round: Print to ... Write to ... Print on ... readlink(1) 3. Program arguments Is it: Argument echo(1) Operand printf(1), also echo(1)? -- Stephen Gregoratto PGP: 3FC6 3D0E 2801 C348 1C44 2D34 A80C 0F8E 8BAB EC8B
Re: firefox, sndiod and pledge
On 30.5.2019. 10:48, Solene Rapenne wrote: > On Thu, May 30, 2019 at 10:41:39AM +0200, Hrvoje Popovski wrote: >> Hi all, >> >> i'm not sure is this intended or not, but if sndiod isn't running and if >> i want to open youtube video with firefox i got this log >> firefox[54192]: pledge "tty", syscall 54 and firefox crashes >> when sndiod is running everything seems fine .. >> >> > > which firefox package and version on which openbsd version? i have installed gnome and desktop stuff few days ago just to see how it works :) i'm not much of a openbsd desktop user firefox-67.0Mozilla web browser OpenBSD 6.5-current (GENERIC.MP) #51: Wed May 29 19:46:38 MDT 2019 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8456089600 (8064MB) avail mem = 8189689856 (7810MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe87b1 (86 entries) bios0: vendor Hewlett-Packard version "J01 v02.29" date 04/04/2016 bios0: Hewlett-Packard HP Compaq 8200 Elite CMT PC acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC SSDT MCFG HPET SSDT SLIC TCPA acpi0: wakeup devices PS2K(S3) PS2M(S3) BR20(S4) EUSB(S3) USBE(S3) PEX0(S4) PEX1(S4) PEX2(S4) PEX3(S4) PEX4(S4) PEX5(S4) PEX6(S4) PEX7(S4) P0P1(S4) P0P2(S4) P0P3(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz, 3293.38 MHz, 06-2a-07 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,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz, 3292.53 MHz, 06-2a-07 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,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz, 3292.53 MHz, 06-2a-07 cpu2: 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,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz, 3292.53 MHz, 06-2a-07 cpu3: 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,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 0 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 acpimcfg0: addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 5 (BR20) acpiprt2 at acpi0: bus 1 (PEX0) acpiprt3 at acpi0: bus -1 (PEX1) acpiprt4 at acpi0: bus -1 (PEX2) acpiprt5 at acpi0: bus -1 (PEX3) acpiprt6 at acpi0: bus 2 (PEX4) acpiprt7 at acpi0: bus -1 (PEX5) acpiprt8 at acpi0: bus 3 (PEX6) acpiprt9 at acpi0: bus 4 (PEX7) acpiprt10 at acpi0: bus -1 (P0P1) acpiprt11 at acpi0: bus -1 (P0P2) acpiprt12 at acpi0: bus -1 (P0P3) acpiprt13 at acpi0: bus -1 (P0P4) acpicpu0 at acpi0: C1(1000@1 halt), PSS acpicpu1 at acpi0: C1(1000@1 halt), PSS acpicpu2 at acpi0: C1(1000@1 halt), PSS acpicpu3 at acpi0: C1(1000@1 halt), PSS acpipci0 at acpi0 PCI0: 0x0010 0x0011 0x acpicmos0 at acpi0 tpm0 at acpi0: TPM_ addr 0xfed4/0x5000, Infineon SLB9635 1.2 rev 0x10 acpibtn0 at acpi0: PWRB "PNP0C14" at acpi0 not configured ipmi at mainbus0 not configured cpu0: using VERW MDS workaround (except on vmm entry) cpu0: Enhanced SpeedStep 3293 MHz: speeds: 3301, 3300, 3100, 2900, 2700, 2500, 2300, 2100, 1900, 1700, 1600 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 2G Host" rev 0x09 inteldrm0 at pci0 dev 2 function 0 "
Re: firefox, sndiod and pledge
On Thu, May 30, 2019 at 10:41:39AM +0200, Hrvoje Popovski wrote: > Hi all, > > i'm not sure is this intended or not, but if sndiod isn't running and if > i want to open youtube video with firefox i got this log > firefox[54192]: pledge "tty", syscall 54 and firefox crashes > when sndiod is running everything seems fine .. > > which firefox package and version on which openbsd version?
firefox, sndiod and pledge
Hi all, i'm not sure is this intended or not, but if sndiod isn't running and if i want to open youtube video with firefox i got this log firefox[54192]: pledge "tty", syscall 54 and firefox crashes when sndiod is running everything seems fine .. from kdump 70068 firefox CALL ioctl(56,AUDIO_STOP,0x1) 70068 firefox PLDG ioctl, "tty", errno 1 Operation not permitted from gdb (gdb) bt #0 ioctl () at -:3 #1 0x1ad9e350858e in sio_sun_fdopen (fd=31, mode=1, nbio=1) at /usr/src/lib/libsndio/sio_sun.c:326 #2 0x1ad9e3508626 in _sio_sun_open (str=Variable "str" is not available. ) at /usr/src/lib/libsndio/sio_sun.c:345 #3 0x1ada4916e16b in WebPGetColorPalette () from /usr/local/lib/firefox/libxul.so.84.0 #4 0x1ada4916d47d in WebPGetColorPalette () from /usr/local/lib/firefox/libxul.so.84.0 #5 0x1ada47f0f415 in std::__1::__murmur2_or_cityhash::__hash_len_0_to_16 () from /usr/local/lib/firefox/libxul.so.84.0 #6 0x1ada47f0f2d2 in std::__1::__murmur2_or_cityhash::__hash_len_0_to_16 () from /usr/local/lib/firefox/libxul.so.84.0 #7 0x1ada480bdb0c in cdm::ContentDecryptionModule_10::~ContentDecryptionModule_10 () from /usr/local/lib/firefox/libxul.so.84.0 #8 0x1ada480bca8a in cdm::ContentDecryptionModule_10::~ContentDecryptionModule_10 () from /usr/local/lib/firefox/libxul.so.84.0 #9 0x1ada480bf915 in cdm::ContentDecryptionModule_10::~ContentDecryptionModule_10 () from /usr/local/lib/firefox/libxul.so.84.0 #10 0x1ada480c60e9 in cdm::ContentDecryptionModule_10::~ContentDecryptionModule_10 () from /usr/local/lib/firefox/libxul.so.84.0 #11 0x1ada47f63ada in std::__1::__split_buffer&>::push_front () from /usr/local/lib/firefox/libxul.so.84.0 #12 0x1ada47f5dc46 in std::__1::__split_buffer&>::push_front () from /usr/local/lib/firefox/libxul.so.84.0 #13 0x1ada47f5da7b in std::__1::__split_buffer&>::push_front () from /usr/local/lib/firefox/libxul.so.84.0 #14 0x1ada47f9047d in std::__1::__split_buffer&>::push_front () from /usr/local/lib/firefox/libxul.so.84.0 #15 0x1ada461232f8 in std::__1::function::swap () from /usr/local/lib/firefox/libxul.so.84.0 #16 0x1ada46120f51 in std::__1::function::swap () from /usr/local/lib/firefox/libxul.so.84.0 #17 0x1ada46134a3e in std::__1::function::swap () from /usr/local/lib/firefox/libxul.so.84.0 #18 0x1ada46134b9b in std::__1::function::swap () from /usr/local/lib/firefox/libxul.so.84.0 #19 0x1ada46130c32 in std::__1::function::swap () from /usr/local/lib/firefox/libxul.so.84.0 #20 0x1ada46133271 in std::__1::function::swap () from /usr/local/lib/firefox/libxul.so.84.0 #21 0x1ada4655eb47 in std::__1::vector >::__append () from /usr/local/lib/firefox/libxul.so.84.0 #22 0x1ada464dc85f in std::__1::vector, std::__1::allocator >, std::__1::allocator, std::__1::allocator > > >::insert, std::__1::allocator >*> > () from /usr/local/lib/firefox/libxul.so.84.0 #23 0x1ada4612e92d in std::__1::function::swap () from /usr/local/lib/firefox/libxul.so.84.0 #24 0x1adaa590c0a9 in _pt_root (arg=0x1adab98c4100) at ptthread.c:201 #25 0x1adac18e2771 in _rthread_start (v=Variable "v" is not available. ) at /usr/src/lib/librthread/rthread.c:96 #26 0x1ada973897c8 in __tfork_thread () at /usr/src/lib/libc/arch/amd64/sys/tfork_thread.S:77 #27 0x in ?? () Current language: auto; currently asm
