Re: xterm not showing Norwegian alphabet
Hi Xianwen Chen, Xianwen Chen wrote on Sat, Feb 10, 2018 at 10:41:19PM +: > I use C shell, csh. When I change the shell to Bourne shell, sh, On OpenBSD, sh(1) is not a Bourne shell, but the same binary as ksh(1), a Korn shell, which is reasonably POSIX-compatible with various extensions. You can see that with ls -i. > I am able to type [non-ASCII characters]. > > Could you check whether you can reproduce my problem by > entering csh and typing [non-ASCII characters]. Some time ago, i hacked into ksh(1) and added minimal UTF-8 support to both emacs and vi input mode, with very little disruption to the existing code base. I didn't bother to do anything similar for csh(1); whatever Theo may say, it is not a very modern shell IMHO... ;) I did not test, but i would be very surprised if csh(1) were able to work sensibly with UTF-8 input. Of course, i wouldn't object to similar work being done in csh(1). > I think I would like to file a bug report. Please don't, it is already well-known that no UTF-8 support was added to OpenBSD csh(1). Yours, Ingo
Re: which NIC to use on Ubiquiti Networks UniFi Security Gateway PRO-4
On Fri, Feb 09, 2018 at 02:10:00PM -0700, Diana Eichert wrote: > systemname$ ifconfig |grep flags > lo0: flags=8049mtu 32768 > cnmac0: flags=8843 mtu 1500 > cnmac1: flags=8843 mtu 1500 > cnmac2: flags=8843 mtu 1500 > cnmac3: flags=8843 mtu 1500 > enc0: flags=0<> > pflog0: flags=141 mtu 33136 > > > systemname$ dmesg |grep phy > ukphy0 at cnmac0 phy 4: Generic IEEE 802.3u media interface, rev. 3: OUI > 0x180361, model 0x0004 > ukphy1 at cnmac1 phy 5: Generic IEEE 802.3u media interface, rev. 3: OUI > 0x180361, model 0x0004 > brgphy0 at cnmac2 phy 0: BCM5482 10/100/1000baseT PHY, rev. 2 > brgphy1 at cnmac3 phy 1: BCM5482 10/100/1000baseT PHY, rev. 2 > > I'm currently using cnmac0 on ukphy0 and I'm wondering if I should be > using cnmac2/3 on brgphy0/1 . > > Any thoughts? I know cnmac0/1 are Cu only, whereas cnmac2/3 could be > SFP if the switch they were connected on could be manipulated. I have > contacts at Cavium, but last time I asked about the internal switch on > an ARM64 box we use they would only release info under NDA. :-( This is probably the same situation as the cu/sfp ports on the ERPro-8, where the phy driver needs some extra logic that controls whether cu or sfp is active, and which set of LEDs blinks when things happen. Without that, they're just regular copper ports, and I don't think there's any reason to prefer one set of interfaces over the other. >From memory there's code for this in linux. I had it half working at one point (packets in one direction through the sfp, but not the other, maybe) but I haven't looked at it in a while.
Re: Support for AMD/ATI Firepro M7820
On Sat, Feb 10, 2018 at 03:18:22PM -0800, Raymond Lillard wrote: > I have a Dell M6500 Precision workstation with an Nvidia FX 3800M. > > I would like to wipe it and install OBSD. I can get a Firepro M7820 > for it.?? If I do, will any of the OBSD drivers work or will I > be stuck with fb performance. It looks like that has a product id of 0x68a0 which is a JUNIPER radeon comparable to a Mobility Radeon HD 5870. JUNIPER is part of the evergreen generation which has modesetting and 2d/3d acceleration with the in tree radeondrm(4) and Mesa 13.0.6. > > I see no mention of Firepro on the OBSD web site and google is > no help either. Each radeon part can have many different marketing names for each variant that change each time they change the marketing names and rebadge the old parts. The kernel and userland code generally refers to codenames and there isn't any one place that has an exhaustive mapping. https://www.x.org/wiki/RadeonFeature/ https://en.wikipedia.org/wiki/List_of_AMD_graphics_processing_units https://en.wikipedia.org/wiki/List_of_AMD_accelerated_processing_unit_microprocessors src/sys/dev/pci/drm/drm_pciids.h https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/drm/drm_pciids.h?h=v4.15 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c?h=v4.15#n469
Re: Support for AMD/ATI Firepro M7820
Sat, 10 Feb 2018 18:50:04 -0800 Mike Larkin> On Sun, Feb 11, 2018 at 02:51:50AM +0200, li...@wrant.com wrote: > > Sat, 10 Feb 2018 15:18:22 -0800 Raymond Lillard > > > I have a Dell M6500 Precision workstation with an Nvidia FX 3800M. > > > > > > I would like to wipe it and install OBSD. I can get a Firepro M7820 > > > for it. If I do, will any of the OBSD drivers work or will I > > > be stuck with fb performance. > > > > > > I see no mention of Firepro on the OBSD web site and google is > > > no help either. > > > > > > Thanks > > > > Hi Raymond, > > > > This is known to work very well and supported including HW acceleration: > > > > Sapphiretech Radeon HD 6450 1G D3 > > http://www.sapphiretech.com/searchSKU.asp?kw=11190-02-10G > > > > ww Radeon HD 6000 Series > > https://en.wikipedia.org/wiki/Radeon_HD_6000_Series#Northern_Islands_(HD_6xxx)_Series > > > > You can get it new very inexpensive and passive cooled ~20W half height. > > I have this and the previous model Radeon HD 5450 both work outstanding. > > > > Kind regards, > > Anton Lazarov > > > > I would like to see how he's going to fit a half-height PCIe card in > his M6500, which is a notebook. > > -ml Marketing, ain't it wonder full of.. work, stations and precision terms.
Re: Support for AMD/ATI Firepro M7820
On Sun, Feb 11, 2018 at 02:51:50AM +0200, li...@wrant.com wrote: > Sat, 10 Feb 2018 15:18:22 -0800 Raymond Lillard> > I have a Dell M6500 Precision workstation with an Nvidia FX 3800M. > > > > I would like to wipe it and install OBSD. I can get a Firepro M7820 > > for it. If I do, will any of the OBSD drivers work or will I > > be stuck with fb performance. > > > > I see no mention of Firepro on the OBSD web site and google is > > no help either. > > > > Thanks > > Hi Raymond, > > This is known to work very well and supported including HW acceleration: > > Sapphiretech Radeon HD 6450 1G D3 > http://www.sapphiretech.com/searchSKU.asp?kw=11190-02-10G > > ww Radeon HD 6000 Series > https://en.wikipedia.org/wiki/Radeon_HD_6000_Series#Northern_Islands_(HD_6xxx)_Series > > You can get it new very inexpensive and passive cooled ~20W half height. > I have this and the previous model Radeon HD 5450 both work outstanding. > > Kind regards, > Anton Lazarov > I would like to see how he's going to fit a half-height PCIe card in his M6500, which is a notebook. -ml
Re: Support for AMD/ATI Firepro M7820
Great news, thank you On 02/10/2018 04:51 PM, li...@wrant.com wrote: Sat, 10 Feb 2018 15:18:22 -0800 Raymond LillardI have a Dell M6500 Precision workstation with an Nvidia FX 3800M. I would like to wipe it and install OBSD. I can get a Firepro M7820 for it. If I do, will any of the OBSD drivers work or will I be stuck with fb performance. I see no mention of Firepro on the OBSD web site and google is no help either. Thanks Hi Raymond, This is known to work very well and supported including HW acceleration: Sapphiretech Radeon HD 6450 1G D3 http://www.sapphiretech.com/searchSKU.asp?kw=11190-02-10G ww Radeon HD 6000 Series https://en.wikipedia.org/wiki/Radeon_HD_6000_Series#Northern_Islands_(HD_6xxx)_Series You can get it new very inexpensive and passive cooled ~20W half height. I have this and the previous model Radeon HD 5450 both work outstanding. Kind regards, Anton Lazarov
Re: xterm not showing Norwegian alphabet
On Sat, Feb 10, 2018 at 10:41:19PM +, Xianwen Chen wrote: > Could you check whether you can reproduce my problem by entering csh > and typing æ, ø, and å? If it is confirmed, I think I would like to > file a bug report. I'm way out of my league here but I can confirm the behaviour. (Also: when entering sh(1) from csh(1), I can type æ, ø and å again.) Good luck! Sincerely, Erling > Sincerely, > Xianwen > > On 2/10/18, Erling Westenvikwrote: > > On Sat, Feb 10, 2018 at 07:33:20PM +, Xianwen Chen wrote: > >> I am however not able to show or type Norwegian alphabet of ø, å, and > >> æ. ø is shown as C8. å is shown as C%. And æ is shown is C&. > > > > See https://www.openbsd.org/faq/faq8.html#locales. Take note of the > > following: > > > > If logging in via xenodm(1), add export LC_CTYPE="en_US.UTF-8" > > to your ~/.xsession before starting the window manager. > > > > Add the export command to the startup file (before invoking any window > > manager) and restart X. This at least solved my problems with Norwegian > > characters. > > > > Regards, > > Erling > > > >> I tried to copi ø, å, and æ from SeaMonkey to xterm. The same thing > >> happens. > >> > >> I tried to copy C8, C%, and C& from xterm back to SeaMonkey. They > >> remained two characters as C8, C%, and C&. > >> > >> Please help. > >> > >> Sincerely, > >> Xianwen
Re: Support for AMD/ATI Firepro M7820
Sat, 10 Feb 2018 15:18:22 -0800 Raymond Lillard> I have a Dell M6500 Precision workstation with an Nvidia FX 3800M. > > I would like to wipe it and install OBSD. I can get a Firepro M7820 > for it. If I do, will any of the OBSD drivers work or will I > be stuck with fb performance. > > I see no mention of Firepro on the OBSD web site and google is > no help either. > > Thanks Hi Raymond, This is known to work very well and supported including HW acceleration: Sapphiretech Radeon HD 6450 1G D3 http://www.sapphiretech.com/searchSKU.asp?kw=11190-02-10G ww Radeon HD 6000 Series https://en.wikipedia.org/wiki/Radeon_HD_6000_Series#Northern_Islands_(HD_6xxx)_Series You can get it new very inexpensive and passive cooled ~20W half height. I have this and the previous model Radeon HD 5450 both work outstanding. Kind regards, Anton Lazarov
Support for AMD/ATI Firepro M7820
I have a Dell M6500 Precision workstation with an Nvidia FX 3800M. I would like to wipe it and install OBSD. I can get a Firepro M7820 for it. If I do, will any of the OBSD drivers work or will I be stuck with fb performance. I see no mention of Firepro on the OBSD web site and google is no help either. Thanks
Re: For a FFS on an SSD, which of "-o" nil, "sync" &/ "softdep" is more data-safe and fast?
2018-02-10 7:28 GMT+01:00 Rupert Gallagher: > The only problem I've encountered is rsync unable to preserve the original > time of files: copied files have the time of the copy. man rsync -t, --times preserve modification times You want -a, --archive archive mode; equals -rlptgoD (no -H,-A,-X) Best Martin
Re: dhclient not renewing
On Feb 10, 2018 5:07 PM, Christer Solskogenwrote: > > On Sat, Feb 10, 2018 at 11:16 PM, Edgar Pettijohn > wrote: > > > try: > > supersede host-name "my.hugs"; > > > > > Still same warning. But I think this comes from the dhcp server of my ISP. > Even without the options it says so. What is the output of: $ hostname
Re: For a FFS on an SSD, which of "-o" nil, "sync" &/ "softdep" is more data-safe and fast?
The only problem I've encountered is rsync unable to preserve the original time of files: copied files have the time of the copy. Sent from ProtonMail Mobile On Sat, Feb 10, 2018 at 01:50,wrote: >> From tom.sm...@wirelessconnect.eu Thu Feb 8 23:37:59 2018 > From: Tom Smyth >> > Date: Thu, 8 Feb 2018 19:40:23 + > Subject: Re: For a FFS on an SSD, >> which of "-o" nil, "sync" &/ "softdep" is > more data-safe and fast? > To: >> Tinker > > Also use noatime mount option so whe reading files you are not >> updating > access time But then don't complain when your favorite software >> package either doesn't work or does unexpected things. Martin >> @protonmail.ch> @wirelessconnect.eu>
Re: dhclient not renewing
On Sat, Feb 10, 2018 at 11:16 PM, Edgar Pettijohnwrote: > try: > supersede host-name "my.hugs"; > > Still same warning. But I think this comes from the dhcp server of my ISP. Even without the options it says so.
Re: xterm not showing Norwegian alphabet
Dear Erling, Thank you. I did that. I actually set both LC_ALL and LC_CTYPE. It was helpful that you stated it worked for you. I used your information and investigated more. It turned out that the problem was in the shell that I use. I use C shell, csh. When I change the shell to Bourne shell, sh, I am able to type æ, ø, and å. Could you check whether you can reproduce my problem by entering csh and typing æ, ø, and å? If it is confirmed, I think I would like to file a bug report. Sincerely, Xianwen On 2/10/18, Erling Westenvikwrote: > On Sat, Feb 10, 2018 at 07:33:20PM +, Xianwen Chen wrote: >> I am however not able to show or type Norwegian alphabet of ø, å, and >> æ. ø is shown as C8. å is shown as C%. And æ is shown is C&. > > See https://www.openbsd.org/faq/faq8.html#locales. Take note of the > following: > > If logging in via xenodm(1), add export LC_CTYPE="en_US.UTF-8" > to your ~/.xsession before starting the window manager. > > Add the export command to the startup file (before invoking any window > manager) and restart X. This at least solved my problems with Norwegian > characters. > > Regards, > Erling > >> I tried to copi ø, å, and æ from SeaMonkey to xterm. The same thing >> happens. >> >> I tried to copy C8, C%, and C& from xterm back to SeaMonkey. They >> remained two characters as C8, C%, and C&. >> >> Please help. >> >> Sincerely, >> Xianwen
Re: dhclient not renewing
On 02/10/18 15:43, Christer Solskogen wrote: On Sat, Feb 10, 2018 at 8:44 PM, Mihai Popescuwrote: Upgraded to latest current snapshot, and it looks like dhclient doesn't renew the ip anymore. I'm > running it in debug mode now, to see if there is anything in the log. Thank you for letting people know. It will take forever if it is not correctly setup. http://www.openbsd.org/faq/faq1.html#MailLists http://www.openbsd.org/faq/faq1.html#Bugs http://www.openbsd.org/report.html em2: DHCPREQUEST to 255.255.255.255 em2: DHCPACK from 51.174.112.1 (00:02:00:01:00:01) em2: invalid host name in host-name ^ em2: bound to 51.174.196.170 from 51.174.112.1 (00:02:00:01:00:01) em2: DHCPREQUEST to 51.174.112.1 em2: DHCPNAK from 51.174.112.1 (00:02:00:01:00:01) em2: DHCPDISCOVER - interval 1 em2: DHCPDISCOVER - interval 1 em2: DHCPOFFER from 51.174.112.1 (00:02:00:01:00:01) em2: invalid host name in host-name em2: DHCPREQUEST to 255.255.255.255 em2: DHCPACK from 51.174.112.1 (00:02:00:01:00:01) em2: invalid host name in host-name em2 [priv]: writev(RTM_GET) - no default route em2 [priv]: writev(RTM_GET) - no default route em2 [priv]: writev(RTM_GET) - no default route OpenBSD 6.2-current (GENERIC.MP) #0: Sat Feb 10 00:05:49 MST 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP my dhclient.conf looks like this: interface "em2" { supersede host-name "hugs"; try: supersede host-name "my.hugs"; supersede domain-name "antarctica.no"; supersede domain-name-servers 192.168.0.1, 192.168.0.4; }
Re: dhclient not renewing
On Sat, Feb 10, 2018 at 8:44 PM, Mihai Popescuwrote: > > Upgraded to latest current snapshot, and it looks like dhclient doesn't > renew the ip anymore. I'm > running it in debug mode now, to see if there > is anything in the log. > > Thank you for letting people know. > It will take forever if it is not correctly setup. > > http://www.openbsd.org/faq/faq1.html#MailLists > http://www.openbsd.org/faq/faq1.html#Bugs > http://www.openbsd.org/report.html > > em2: DHCPREQUEST to 255.255.255.255 em2: DHCPACK from 51.174.112.1 (00:02:00:01:00:01) em2: invalid host name in host-name em2: bound to 51.174.196.170 from 51.174.112.1 (00:02:00:01:00:01) em2: DHCPREQUEST to 51.174.112.1 em2: DHCPNAK from 51.174.112.1 (00:02:00:01:00:01) em2: DHCPDISCOVER - interval 1 em2: DHCPDISCOVER - interval 1 em2: DHCPOFFER from 51.174.112.1 (00:02:00:01:00:01) em2: invalid host name in host-name em2: DHCPREQUEST to 255.255.255.255 em2: DHCPACK from 51.174.112.1 (00:02:00:01:00:01) em2: invalid host name in host-name em2 [priv]: writev(RTM_GET) - no default route em2 [priv]: writev(RTM_GET) - no default route em2 [priv]: writev(RTM_GET) - no default route OpenBSD 6.2-current (GENERIC.MP) #0: Sat Feb 10 00:05:49 MST 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP my dhclient.conf looks like this: interface "em2" { supersede host-name "hugs"; supersede domain-name "antarctica.no"; supersede domain-name-servers 192.168.0.1, 192.168.0.4; }
Re: xterm not showing Norwegian alphabet
On Sat, Feb 10, 2018 at 07:33:20PM +, Xianwen Chen wrote: > I am however not able to show or type Norwegian alphabet of ø, å, and > æ. ø is shown as C8. å is shown as C%. And æ is shown is C&. See https://www.openbsd.org/faq/faq8.html#locales. Take note of the following: If logging in via xenodm(1), add export LC_CTYPE="en_US.UTF-8" to your ~/.xsession before starting the window manager. Add the export command to the startup file (before invoking any window manager) and restart X. This at least solved my problems with Norwegian characters. Regards, Erling > I tried to copi ø, å, and æ from SeaMonkey to xterm. The same thing happens. > > I tried to copy C8, C%, and C& from xterm back to SeaMonkey. They > remained two characters as C8, C%, and C&. > > Please help. > > Sincerely, > Xianwen
Re: dhclient not renewing
> Upgraded to latest current snapshot, and it looks like dhclient doesn't renew > the ip anymore. I'm > running it in debug mode now, to see if there is > anything in the log. Thank you for letting people know. It will take forever if it is not correctly setup. http://www.openbsd.org/faq/faq1.html#MailLists http://www.openbsd.org/faq/faq1.html#Bugs http://www.openbsd.org/report.html
xterm not showing Norwegian alphabet
Dear list, I have a freshly installed OpenBSD 6.2 i386, with the following environmental setting: $env LOGNAME=oe WINDOWPATH=ttyC4 HOME=/home/oe DISPLAY=:0 LC_ALL=en_US.UTF-8 PATH=/home/xc/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin:/usr/local/bin:/usr/local/sbin:/usr/games:. SHELL=/bin/csh USER=oe TERM=xterm WINDOWID=8388621 XTERM_VERSION=XTerm/OpenBSD(330) XTERM_LOCALE=en_US.UTF-8 XTERM_SHELL=/bin/csh PWD=/home/oe LC_CTYPE=en_US.UTF-8 EXINIT=set ai sm noeb I am however not able to show or type Norwegian alphabet of ø, å, and æ. ø is shown as C8. å is shown as C%. And æ is shown is C&. I tried to copi ø, å, and æ from SeaMonkey to xterm. The same thing happens. I tried to copy C8, C%, and C& from xterm back to SeaMonkey. They remained two characters as C8, C%, and C&. Please help. Sincerely, Xianwen
dhclient not renewing?
Upgraded to latest current snapshot, and it looks like dhclient doesn't renew the ip anymore. I'm running it in debug mode now, to see if there is anything in the log.
Re: Wondering if any of my hardware is working on -current
On Fri, Feb 09, 2018 at 04:33:35PM -0800, Chris Bennett wrote: > Wifi is still a no go. OpenBSD has no driver for ath10k wifi devices. This is unlikely to change any time soon.
Re: supermicro x8sil-f - only one fan detected after replug on the board
On Sat, Feb 10, 2018 at 04:23:41AM +0200, li...@wrant.com wrote: > > I have supermicro x8sil-f (latest bios/ipmi fw) with 2 fans and it has > > started > > to beep after a while when OS is up while it detected non-existing fans > > either > > run at 0 RPM or in -2560 RPM. > > Does a manual restart of the BMC card (via IPMI) make a difference, how? Nope, it's related to https://marc.info/?l=openbsd-misc=144473090118095=2 Jiri
Re: supermicro x8sil-f - only one fan detected after replug on the board
On Fri, Feb 09, 2018 at 05:12:11PM +0200, Atanas Vladimirov wrote: > On 2018-02-09 14:45, Jiri B wrote: > >Hi, > > > >I have supermicro x8sil-f (latest bios/ipmi fw) with 2 fans and it has > >started > >to beep after a while when OS is up while it detected non-existing fans > >either > >run at 0 RPM or in -2560 RPM. > > > >OpenBSD itself used to detect both fans (though lm1.fanX numbers were > >different > >to numbering from motherboard vendor). > > > >I replugged both fans on the board and OpenBSD has detected only one fan > >now. > >Why only one now, if it used to previously detected both? > > Hi, > This is a known issue [0] with this particular motherboard > and you have to disable lm driver. > > [0] https://marc.info/?l=openbsd-misc=144473090118095=2 Thank you. I should have to search archives, it would solve my crazy headaches :) Anyway, it's surprise that after fans replug to different connectors on the board - which has caused OpenBSD not detecting one fan - the board doesn't beep anymore. So yes, it must be related to the issue you pointed to. Jiri
Re: samba client
On 02/10/2018 10:50 AM, Stuart Henderson wrote: I can get this to work for root, but not for a regular user. (I get "fuse mount: permission denied" for a non-root user, with the exact same usmb setup that works for root...) https://undeadly.org/cgi?action=article=20160715125022 Thank you. I wish I knew about this before this excursion, there was unfortunately nothing indicating this peculiarity in any man pages I consulted along the way.
Re: For a FFS on an SSD, which of "-o" nil, "sync" &/ "softdep" is more data-safe and fast?
I use ls -lu and find -atime quite frequently. I've also been using OpenBSD as a desktop (with all the insane disk activity of a browser cache, temp files, git, etc) while doing absolutely nothing special using SATA SSD drives. I'm running Softraid crypto on one, running without softraid on the other. No snazzy mount options outside the defaults. It's been as reliable as any spinning rust I've used. You're keeping good backups regardless, right? Because that protects you from many more likely failure modes than wear-level-exhaustion on SSD. On Sat, Feb 10, 2018 at 10:38 AM,wrote: > > From tom.sm...@wirelessconnect.eu Sat Feb 10 11:28:46 2018 > > From: Tom Smyth > > Date: Sat, 10 Feb 2018 09:10:30 + > > Subject: Re: For a FFS on an SSD, which of "-o" nil, "sync" &/ "softdep" > is > > more data-safe and fast? > > To: mar...@martinbrandenburg.com > > > > Hi Martin... can you give a specific case where you have experienced > > negative impacts from thevmount options i suggested... > > It would be good to know... > > Well I don't run noatime, so I can't give specific examples. > > The point I was making is that noatime is a tradeoff. You give up > adherence to POSIX and historical Unix behavior in exchange for > performance and less disk wear. > > Now I will admit that programs that rely on atime updates are few and > far between. It was always a bit niche. Nowadays, most software is > written on Linux, and most Linux systems use relatime. > > It might be an acceptable tradeoff. To use the examples from the > manpage, if you know you're not going run any programs that need it and > that you'll never leave your laptop up for seven days or if you know > your news server doesn't need it, go ahead and disable it. > > Just don't forget to consider it as a potential problem if you run into > trouble. > > Here are some lines from /etc/daily. Without atime updates, it could > delete files. (Some of these might get more frequent mtime or ctime > updates which would bump the atime under noatime.) > > The second set might be uncommented on a big multiuser system to clear > out /tmp since users don't. They might be a little irritated when the > file they've been reading for the last day gets deleted. > > next_part "Removing scratch and junk files:" > if [ -d /tmp -a ! -L /tmp ]; then > cd /tmp && { > find -x . \ > \( -path './ssh-*' -o -path ./.X11-unix -o -path ./.ICE-unix \ > -o -path './tmux-*' \) \ > -prune -o -type f -atime +7 -execdir rm -f -- {} \; 2>/dev/null > find -x . -type d -mtime +1 ! -path ./vi.recover ! -path > ./.X11-unix \ > ! -path ./.ICE-unix ! -name . \ > -execdir rmdir -- {} \; >/dev/null 2>&1; } > fi > > # Additional junk directory cleanup would go like this: > #if [ -d /scratch -a ! -L /scratch ]; then > # cd /scratch && { > # find . ! -name . -atime +1 -execdir rm -f -- {} \; > # find . ! -name . -type d -mtime +1 -execdir rmdir -- {} \; \ > # >/dev/null 2>&1; } > #fi > > Martin > >
Re: For a FFS on an SSD, which of "-o" nil, "sync" &/ "softdep" is more data-safe and fast?
> From tom.sm...@wirelessconnect.eu Sat Feb 10 11:28:46 2018 > From: Tom Smyth> Date: Sat, 10 Feb 2018 09:10:30 + > Subject: Re: For a FFS on an SSD, which of "-o" nil, "sync" &/ "softdep" is > more data-safe and fast? > To: mar...@martinbrandenburg.com > > Hi Martin... can you give a specific case where you have experienced > negative impacts from thevmount options i suggested... > It would be good to know... Well I don't run noatime, so I can't give specific examples. The point I was making is that noatime is a tradeoff. You give up adherence to POSIX and historical Unix behavior in exchange for performance and less disk wear. Now I will admit that programs that rely on atime updates are few and far between. It was always a bit niche. Nowadays, most software is written on Linux, and most Linux systems use relatime. It might be an acceptable tradeoff. To use the examples from the manpage, if you know you're not going run any programs that need it and that you'll never leave your laptop up for seven days or if you know your news server doesn't need it, go ahead and disable it. Just don't forget to consider it as a potential problem if you run into trouble. Here are some lines from /etc/daily. Without atime updates, it could delete files. (Some of these might get more frequent mtime or ctime updates which would bump the atime under noatime.) The second set might be uncommented on a big multiuser system to clear out /tmp since users don't. They might be a little irritated when the file they've been reading for the last day gets deleted. next_part "Removing scratch and junk files:" if [ -d /tmp -a ! -L /tmp ]; then cd /tmp && { find -x . \ \( -path './ssh-*' -o -path ./.X11-unix -o -path ./.ICE-unix \ -o -path './tmux-*' \) \ -prune -o -type f -atime +7 -execdir rm -f -- {} \; 2>/dev/null find -x . -type d -mtime +1 ! -path ./vi.recover ! -path ./.X11-unix \ ! -path ./.ICE-unix ! -name . \ -execdir rmdir -- {} \; >/dev/null 2>&1; } fi # Additional junk directory cleanup would go like this: #if [ -d /scratch -a ! -L /scratch ]; then # cd /scratch && { # find . ! -name . -atime +1 -execdir rm -f -- {} \; # find . ! -name . -type d -mtime +1 -execdir rmdir -- {} \; \ # >/dev/null 2>&1; } #fi Martin
Feb 10 snapshot - nd6_dad_timer kernel message
Hello, I upgraded my Feb 8 snapshot to Feb 10. After bsd.rd was booted, I saw this kernel message I have not seen before: nd6_dad_timer: called with non-tentative address 2601:2c2:600:2c5d:898e:c06d:294c:16c8(re0) After completing the install, I couldn't connect using IPv6: b1$ ping6 google.com PING google.com (2607:f8b0:4000:814::200e): 56 data bytes ping6: sendmsg: No route to host ping: wrote google.com 64 chars, ret=-1 I removed IPv6 from the interface and re-added it. After that IPv6 connectivity started working. Anyway, not sure if it's related to the snapshot or not but thought to report it. David b1$ ndp -an Neighbor Linklayer Address Netif ExpireS Flags 2601:2c2:600:2c5d:2035:2c9b:7059:f6eb 78:f2:9e:90:96:4ere0 permanent R l 2601:2c2:600:2c5d:2cd7:ed0e:97a7:e7c3 78:f2:9e:90:96:4ere0 permanent R l 2601:2c2:600:2c5d:898e:c06d:294c:16c8 78:f2:9e:90:96:4ere0 permanent R l 2601:2c2:600:2c5d:bb6e:eaba:bb9:6370 78:f2:9e:90:96:4e re0 permanent R l fe80::64bf:1138:2c46:d796%re078:f2:9e:90:96:4e re0 permanent R l fe80::724c:a5ff:fe23:28e2%re070:4c:a5:23:28:e2 re0 expired D R fe80::9c8b:3a74:b860:fd78%re0(incomplete) re0 expired N b1$ ifconfig re0 re0: flags=208843mtu 1500 lladdr 78:f2:9e:90:96:4e index 1 priority 0 llprio 3 groups: egress media: Ethernet autoselect (1000baseT full-duplex,rxpause,txpause) status: active inet 192.168.0.9 netmask 0xff00 broadcast 192.168.0.255 inet6 2601:2c2:600:2c5d:898e:c06d:294c:16c8 prefixlen 64 autoconf pltime 281571 vltime 281571 inet6 2601:2c2:600:2c5d:2035:2c9b:7059:f6eb prefixlen 64 autoconf autoconfprivacy pltime 84964 vltime 281571 inet6 fe80::64bf:1138:2c46:d796%re0 prefixlen 64 scopeid 0x1 inet6 2601:2c2:600:2c5d:bb6e:eaba:bb9:6370 prefixlen 64 autoconf pltime 282507 vltime 282507 inet6 2601:2c2:600:2c5d:2cd7:ed0e:97a7:e7c3 prefixlen 64 autoconf autoconfprivacy pltime 85224 vltime 281574 b1$ doas ifconfig re0 -inet6 b1$ ifconfig re0 re0: flags=8843 mtu 1500 lladdr 78:f2:9e:90:96:4e index 1 priority 0 llprio 3 groups: egress media: Ethernet autoselect (1000baseT full-duplex,rxpause,txpause) status: active inet 192.168.0.9 netmask 0xff00 broadcast 192.168.0.255 b1$ doas ifconfig re0 inet6 autoconf b1$ ifconfig re0 re0: flags=208843 mtu 1500 lladdr 78:f2:9e:90:96:4e index 1 priority 0 llprio 3 groups: egress media: Ethernet autoselect (1000baseT full-duplex,rxpause,txpause) status: active inet 192.168.0.9 netmask 0xff00 broadcast 192.168.0.255 inet6 fe80::64bf:1138:2c46:d796%re0 prefixlen 64 scopeid 0x1 inet6 2601:2c2:600:2c5d:bb6e:eaba:bb9:6370 prefixlen 64 tentative autoconf pltime 282520 vltime 282520 inet6 2601:2c2:600:2c5d:647f:dab8:35f7:7f97 prefixlen 64 tentative autoconf autoconfprivacy pltime 86399 vltime 282520 b1$ ping6 google.com PING google.com (2607:f8b0:4000:814::200e): 56 data bytes 64 bytes from 2607:f8b0:4000:814::200e: icmp_seq=0 hlim=54 time=16.893 ms 64 bytes from 2607:f8b0:4000:814::200e: icmp_seq=1 hlim=54 time=15.956 ms 64 bytes from 2607:f8b0:4000:814::200e: icmp_seq=2 hlim=54 time=18.775 ms 64 bytes from 2607:f8b0:4000:814::200e: icmp_seq=3 hlim=54 time=16.277 ms 64 bytes from 2607:f8b0:4000:814::200e: icmp_seq=4 hlim=54 time=15.811 ms ^C --- google.com ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 15.811/16.742/18.775/1.082 ms b1$ ndp -an Neighbor Linklayer Address Netif ExpireS Flags 2601:2c2:600:2c5d:647f:dab8:35f7:7f97 78:f2:9e:90:96:4ere0 permanent R l 2601:2c2:600:2c5d:bb6e:eaba:bb9:6370 78:f2:9e:90:96:4e re0 permanent R l fe80::64bf:1138:2c46:d796%re078:f2:9e:90:96:4e re0 permanent R l fe80::724c:a5ff:fe23:28e2%re070:4c:a5:23:28:e2 re0 expired D R OpenBSD 6.2-current (RAMDISK_CD) #0: Sat Feb 10 00:10:18 MST 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 16813948928 (16035MB) avail mem = 16300613632 (15545MB) enter_shared_special_pages: entered idt page va 0x8001 pa 0x1a32000 enter_shared_special_pages: entered kutext page va 0x8133f000 pa 0x133f000 enter_shared_special_pages: entered kutext page va 0x8134 pa 0x134 enter_shared_special_pages: entered kutext page va 0x81341000 pa 0x1341000 cpu_enter_pages: entered tss+gdt page at va 0x81852000 pa 0x1852000 cpu_enter_pages: entered t.stack page at va 0x81853000 pa 0x1853000 cpu_enter_pages: cif_tss.tss_rsp0 = 0x818533e0 mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xed9d0 (17
Re: LibreSSL Linux portability and OpenBSD security
On Saturday 10 February 2018 11:09:04 Kevin Chadwick wrote: > On Sat, 10 Feb 2018 16:24:38 +1100 > > > > Just in case some libressl dev doesn't want read the full thread in > > > the Alpine list, they want also a workaround for the lack of time_t > > > for 32bits platforms on Linux. > > > > We've already addressed this - a notafter that exceeds 2038 is > > clamped to 2038 on system that only has 32-bit time_t - see r1.65 of > > src/lib/libcrypto/x509/x509_vfy.c: > > > > http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/lib/libcrypto/x509/x509_vfy.c > > .diff?r1=1.64=1.65 > > Natanael had already found that but William says TAI64n is required to > be conformant. Perhaps you will understand where he is coming > from or whether he has an unspoken agenda? His original email did not > seem to be a fair representation of facts though. Conformant with what exactly? I do not recall seeing anything regarding TAI64N in TLS/X509 RFCs, where everything is handled in ASN.1 GENERALIZEDTIME or UTCTIME. > I can't see how this (assuming this is the TAI64N in question) helps but > I assume I am missing something. > > https://cr.yp.to/daemontools/tai64n.html > > "Beware that most gettimeofday implementations are not Y2038-compliant."
Re: LibreSSL Linux portability and OpenBSD security
On Sat, 10 Feb 2018 16:24:38 +1100 > > Just in case some libressl dev doesn't want read the full thread in > > the Alpine list, they want also a workaround for the lack of time_t > > for 32bits platforms on Linux. > > We've already addressed this - a notafter that exceeds 2038 is > clamped to 2038 on system that only has 32-bit time_t - see r1.65 of > src/lib/libcrypto/x509/x509_vfy.c: > > http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/lib/libcrypto/x509/x509_vfy.c.diff?r1=1.64=1.65 Natanael had already found that but William says TAI64n is required to be conformant. Perhaps you will understand where he is coming from or whether he has an unspoken agenda? His original email did not seem to be a fair representation of facts though. I can't see how this (assuming this is the TAI64N in question) helps but I assume I am missing something. https://cr.yp.to/daemontools/tai64n.html "Beware that most gettimeofday implementations are not Y2038-compliant."
Re: samba client
On 2018-02-10, Edgar Pettijohnwrote: > > > On 02/09/18 18:20, listo factor wrote: >> On 02/08/2018 11:44 AM, Peter N. M. Hansteen wrote: >> ...> cd /usr/ports; make search key=smb >>> yields among other things >>> Port: usmb-20130204p4 >> ... >>> which might fit the scenario. >> >> Thank you, it appears it does. However...: >> >> I can get this to work for root, but not for a regular user. >> (I get "fuse mount: permission denied" for a non-root user, >> with the exact same usmb setup that works for root...) > > https://marc.info/?l=openbsd-misc=149805347118472=2 And lots of discussion about this at https://undeadly.org/cgi?action=article=20160715125022
Re: For a FFS on an SSD, which of "-o" nil, "sync" &/ "softdep" is more data-safe and fast?
Hi Martin... can you give a specific case where you have experienced negative impacts from thevmount options i suggested... It would be good to know... Thanks Martin Tom Smyth On 10 Feb 2018 12:50 AM,wrote: > > From tom.sm...@wirelessconnect.eu Thu Feb 8 23:37:59 2018 > > From: Tom Smyth > > Date: Thu, 8 Feb 2018 19:40:23 + > > Subject: Re: For a FFS on an SSD, which of "-o" nil, "sync" &/ "softdep" > is > > more data-safe and fast? > > To: Tinker > > > > Also use noatime mount option so whe reading files you are not updating > > access time > > But then don't complain when your favorite software package either > doesn't work or does unexpected things. > > Martin >