Re: pf tagged rule not work/match
Hi, this one fixed my problem, thanks http://marc.info/?l=openbsd-cvs=149532101008885=2 On 2017年5月19日 GMT+08:00下午10時00分32秒, johnwwrote: >After upgrade to last day current, pf tagged rule not work/match any >more, >it work before. > >( below rules not match/work any more ) >pass in quick on $int_if from any flags any tag HOME >pass out quick on $ext_if from any nat-to ($ext_if:0) flags any tagged >HOME > >if change >pass out quick on $ext_if from any nat-to ($ext_if:0) flags any tagged >HOME >to >pass out quick on $ext_if from any nat-to ($ext_if:0) flags any > >NAT work again, thanks. > >-- >Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC
Re: Markus Uhlin
Stupid question but could you block his account? > On May 20, 2017, at 6:52 PM, Theo de Raadtwrote: > > I am being harrassed by a guy called Markus Uhlin. > > https://github.com/uhlin?tab=following > > By sending this mail, I'm hoping he comes to understand I am fed up. >
Re: faq5 and release.8 documentation adding wobj group
nevermind - sorry for the noise... Miscellaneous-section... oops... h. On Sun, May 21, 2017 at 7:47 AM, harold feltonwrote: > Hello, > > I am unsure whether this has already been addressed. > the documentation at faq5 and release.8 are slightly > outdated. For a non-root user, there should be another > step besides only adding them to the wsrc-group. > > Typically, this non-root user is already in group-wheel. > The instructions currently mention that they should be > in group-wsrc, but they should also be in group-wobj. > > The relevant command is simply: > > # *user mod -G wobj exampleuser* > > as seen at https://www.openbsd.org/faq/faq5.html#Bld > which then references release.8 step-2. > > I do not know where/how to check for documentation > that might be changing under -current. > > Sincerely, hfelton > > ps - I have followed the mailing-lists for awhile and > would reference the following researched items: > message to source-changes from 20170412 id: > aca921a291cf2...@openbsd.org > similar, but unrelated-bug from 20170116 at: > http://marc.info/?l=openbsd-bugs=148459605014161=2 > > -- harold at hfelton.com
Re: faq5 and release.8 documentation adding wobj group
On Sun, May 21, 2017 at 07:47:59AM +0800, harold felton wrote: > Hello, > > I am unsure whether this has already been addressed. > the documentation at faq5 and release.8 are slightly > outdated. For a non-root user, there should be another > step besides only adding them to the wsrc-group. This is one way that you can avoid running cvs as root. > Typically, this non-root user is already in group-wheel. > The instructions currently mention that they should be > in group-wsrc, but they should also be in group-wobj. This is not needed for 'make build' or 'make release', therefore I chose not to mention it in the "building from source" section of faq5. I did mention why that might be a useful thing to do here: https://www.openbsd.org/faq/faq5.html#Miscellanea and also on upgrade61.html. > The relevant command is simply: > > # *user mod -G wobj exampleuser* > > as seen at https://www.openbsd.org/faq/faq5.html#Bld > which then references release.8 step-2. > > I do not know where/how to check for documentation > that might be changing under -current. The faq is updated within about half an hour after a commit is made. For -current manuals, you can use http://man.openbsd.org > Sincerely, hfelton > > ps - I have followed the mailing-lists for awhile and > would reference the following researched items: > message to source-changes from 20170412 id: > aca921a291cf2...@openbsd.org This is when I added https://www.openbsd.org/faq/faq5.html#Miscellanea mentioned above. > similar, but unrelated-bug from 20170116 at: > http://marc.info/?l=openbsd-bugs=148459605014161=2 This was fixed a week or two after that conversation: https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/share/mk/bsd.obj.mk#rev1.17
Markus Uhlin
I am being harrassed by a guy called Markus Uhlin. https://github.com/uhlin?tab=following By sending this mail, I'm hoping he comes to understand I am fed up.
faq5 and release.8 documentation adding wobj group
Hello, I am unsure whether this has already been addressed. the documentation at faq5 and release.8 are slightly outdated. For a non-root user, there should be another step besides only adding them to the wsrc-group. Typically, this non-root user is already in group-wheel. The instructions currently mention that they should be in group-wsrc, but they should also be in group-wobj. The relevant command is simply: # *user mod -G wobj exampleuser* as seen at https://www.openbsd.org/faq/faq5.html#Bld which then references release.8 step-2. I do not know where/how to check for documentation that might be changing under -current. Sincerely, hfelton ps - I have followed the mailing-lists for awhile and would reference the following researched items: message to source-changes from 20170412 id: aca921a291cf2...@openbsd.org similar, but unrelated-bug from 20170116 at: http://marc.info/?l=openbsd-bugs=148459605014161=2
Re: Happy birthday Theo!
Likewise happy birthday from sweden On May 19, 2017 11:16:26 AM GMT+02:00, Craig Skinnerwrote: >Best wishes. -- Take Care Sincerely flipchan layerprox dev
Re: mips64el packages deprecated?
On Fri, May 19, 2017 at 03:28:33PM -, Christian Weisgerber wrote: > On 2017-05-19, Roland Kammererwrote: > > >> > Today I upgraded to OpenBSD 6.1 and saw that none of the mirrors seem to > >> > contain packages for mips64el anymore. > >> > > >> > Are they still building? > >> > >> Yes. > > > > Are we there yet? Are we there yet? ;-). > > Yes, the packages are finished. They should show up on the mirrors > real soon now. > > > I think for the last 5 or so releases I updated pretty soon after > > the official release, so this looks new... > > Previously, there was a long delay between when the release was > finalized and when it was published. This allowed for CD production > and for the slow archs to finish building packages. > > For 6.1, this delay was mostly eliminated, but this also means that > the packages for the non-x86 architectures arrive later, according > to the time it takes to build them. Thanks to you and Theo for the explanation, will keep that in mind. The update went smoothly as always. Regards, rck
Re: A mix: mounting ext3 usb, FF & js, audio
On 05/19/17 03:08, Stuart Henderson wrote: On 2017-05-19, system_haltedwrote: Hi, I am new to BSD world, yet enjoying very much OpenBSD 6.1 that I have installed recently. As a newcomer I have some questions, sorry for having a mix of everything. 1. I have a pendrive with ext3fs fdisk output on Debian: Disk /dev/sdc: 29.8 GiB, 32027705344 bytes, 62554112 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xbb378728 Device Boot Start End Sectors Size Id Type /dev/sdc12048 62554111 62552064 29.8G 83 Linux disklabel: # /dev/rsd2c: type: SCSI disk: Debian testing a label: md64 1 duid: flags: bytes/sector: 512 sectors/track: 32 tracks/cylinder: 64 sectors/cylinder: 2048 cylinders: 30544 total sectors: 62554112 boundstart: 0 boundend: 62554112 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] a: 625541120 ISO9660 c: 625541120 ISO9660 What is that I am missing? To my understanding OpenBSD does handle ext3, is this some kind of a problem with partition table on the drive? I did put ISO image of Debian testing on that drive with cp before, but than deleted all partitions created new and formatted the drive. After mounting sd2a I can see directory tree of ISO image that originally was on that drive, content of the files is obviously all messed up. sd2c cannot be mounted "Device not configured". It sounds like part of the special hybrid iso+HD image format from the Debian image remains on the disk. Generally it's best to dd zeros over the start of a drive before reusing it, especially with a special format like that. What I would do in this situation is copy the data off, "dd if=/dev/zero of=/dev/rsdXc bs=1m count=1" (replace X with the correct device number), repartition and reformat, then copy the data back. I wouldn't recommend ext2fs, it's not very widely used so you're more likely to run into a problem. Likewise I wouldn't use FFS support on Linux for the same reason. FAT32 is a safer choice if you need to share the filesystem. Thank you. Used both of your suggestions and this worked. 2. Firefox Seem to have problems with certain sites with js - cannot get through to log in into protonmail.com, Epiphany handles it without any problems. This is not associated with any addons that I have on FF, tried in on fresh vanilla FF and result is the same. Did anyone observe similar issue? Resolving suggestions? Try raising the datasize limit, either try "ulimit -d $((2048*1024))" before running firefox, or raise datasize-cur in the 'staff' class in /etc/login.conf and logout and back in. (adjust the actual value as necessary). Both datasize-max and datasize-cur already set to higher limits (2048M) in /etc/login.conf. I checked FF console, this is what it spits out. TypeError: asm.js link error: Unable to prepare ArrayBuffer for asm.js use openpgp.min.js:2:2189 uncaught exception: out of memory (unknown) Successfully compiled asm.js code (total compilation time 75ms; stored in cache) app.js Successfully compiled asm.js code (total compilation time 21ms; stored in cache) app.js TypeError: asm.js link error: Unable to prepare ArrayBuffer for asm.js use app.js:65:30730 uncaught exception: out of memory (unknown) Error: [$injector:modulerr] Failed to instantiate module proton due to: [$injector:modulerr] Failed to instantiate module proton.outside due to: [$injector:modulerr] Failed to instantiate module proton.routes due to: [$injector:nomod] Module 'proton.routes' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument. 3. Audio With headphones in there is a slight white noise that can be heard. I do not have that effect while on Debian. This effect does not go away when playing sound or reducing volume to 0 (xfce4-mixer). Any suggestions? No idea personally. But reply to the list with output of mixerctl, audioctl and dmesg (inline, not attached) and see if someone else has an idea. Thanks to Zé's comments I just went with mixerctl output.master.mute=on maybe not the cleanest solution, but worked. Thank you for all suggestion and guidance. ic1