Re: Clarification about mfs/tmpfs on /tmp

2018-10-10 Thread Otto Moerbeek
On Wed, Oct 10, 2018 at 12:59:27PM +0200, Eivind Eide wrote: > I was not able to get correct permissions on my mfs /tmp until I put > the following in /etc/rc.securelevel, which solved the problem. > /bin/chmod 1777 /tmp That is not the right solution. The right one is to unmount /tmp (boot to si

Re: Clarification about mfs/tmpfs on /tmp

2018-10-10 Thread Eivind Eide
I was not able to get correct permissions on my mfs /tmp until I put the following in /etc/rc.securelevel, which solved the problem. /bin/chmod 1777 /tmp -- Eivind Eide "ONLY THOSE WHO ATTEMPT THE IMPOSSIBLE WILL ACHIEVE THE ABSURD" - Oceania Association of Autonomous Astronauts

Re: Clarification about mfs/tmpfs on /tmp

2018-10-10 Thread Paul de Weerd
On Wed, Oct 10, 2018 at 10:20:32AM +0200, Felix Maschek wrote: | | On 10/9/18 11:46 PM, Alexander Hall wrote: | > On a sidenote, 777 is not the proper permissions for /tmp. | | | What is the proper permission for /tmp? 1777 (you need to enable the sticky bit on the directory, see sticky(8) for

Re: Clarification about mfs/tmpfs on /tmp

2018-10-10 Thread Felix Maschek
On 10/9/18 11:46 PM, Alexander Hall wrote: On a sidenote, 777 is not the proper permissions for /tmp. What is the proper permission for /tmp? ~Felix

Re: Clarification about mfs/tmpfs on /tmp

2018-10-10 Thread r.gr
Alexander wrote: > When you create and mount an mfs, its root node will "inherit" (or copy) the > permissions of the mount point. > When you mount an ffs filesystem, it already has an existing root node from > the time it was newfs'd, which will not be modified based on the underlying > mount p

Re: Clarification about mfs/tmpfs on /tmp

2018-10-09 Thread Alexander Hall
On October 9, 2018 6:17:05 PM GMT+02:00, r...@tutanota.com wrote: >I recall having to do this as well (in fact, as mentioned earlier >in this thread): > >> doas chmod 777 /tmp > >If I understood Stuart Henderson correctly, then > >> This one is easy, simply set the appropriate permissions >> on

Re: Clarification about mfs/tmpfs on /tmp

2018-10-09 Thread r.gr
I recall having to do this as well (in fact, as mentioned earlier in this thread): > doas chmod 777 /tmp If I understood Stuart Henderson correctly, then > This one is easy, simply set the appropriate permissions > on the directory where you mount the mfs. implies that irrespective of what is m

Re: Clarification about mfs/tmpfs on /tmp

2018-10-09 Thread Felix Maschek
On 10/8/18 11:27 PM, r...@tutanota.com wrote: chrome --disk-cache/dir=/tmp/chrome? This works fine for me. BTW, I've set up a RAM based /tmp directory using the following /etc/fstab entry:     #/dev/sd0f /tmp ffs rw,nodev,nosuid 1 2     swap /tmp mfs rw,noexec,nodev,nosuid,-s=512m 0 0 But

Re: Clarification about mfs/tmpfs on /tmp

2018-10-09 Thread r.gr
This is a reply to both Stuart Henderson and Gregor Best. > This one is easy, simply set the appropriate permissions on the > directory where you mount the mfs. Will do. > [...] it's assumed that the relevant support is compiled into the > kernel [...] I understand. Than it would be a matter of

Re: Clarification about mfs/tmpfs on /tmp

2018-10-09 Thread Martijn van Duren
On 10/9/18 2:03 PM, Stuart Henderson wrote: > On 2018-10-09, wrote: >> Solene Rapenne wrote: >>> hello, >> >>> if you don't put any /tmp in fstab, /tmp comes from the / partition, which >>> doesn't have nodev and nosuid mount options, and which is very tiny. >> >>> tmpfs has been disabled: see >>

Re: Clarification about mfs/tmpfs on /tmp

2018-10-09 Thread Stuart Henderson
On 2018-10-09, wrote: > Solene Rapenne wrote: >> hello, > >> if you don't put any /tmp in fstab, /tmp comes from the / partition, which >> doesn't have nodev and nosuid mount options, and which is very tiny. > >> tmpfs has been disabled: see >> https://marc.info/?l=openbsd-tech&m=148173068424515&

Re: Clarification about mfs/tmpfs on /tmp

2018-10-09 Thread Gregor Best
Hi, >> [...] >> The last part of my question concerns caching chromium data in /tmp. >> I have read that the OpenBSD chromium port has been "pledged" and >> "unveiled". Does this have any influence over whether I can run >> chrome --disk-cache/dir=/tmp/chrome? >> [...] I don't know about the sp

Re: Clarification about mfs/tmpfs on /tmp

2018-10-09 Thread r.gr
Solene Rapenne wrote: > hello, > if you don't put any /tmp in fstab, /tmp comes from the / partition, which > doesn't have nodev and nosuid mount options, and which is very tiny. > tmpfs has been disabled: see > https://marc.info/?l=openbsd-tech&m=148173068424515&w=2 >

Re: Clarification about mfs/tmpfs on /tmp

2018-10-08 Thread Solene Rapenne
wrote: > Dear OpenBSD Community, > > I have been playing around with OpenBSD for ~2 weeks now, and I find > myself very much at home in a system that puts correctness and careful > development first. Needless to say that I have already made my first > donation; I sincerely thank the developers fo

Clarification about mfs/tmpfs on /tmp

2018-10-08 Thread r.gr
Dear OpenBSD Community, I have been playing around with OpenBSD for ~2 weeks now, and I find myself very much at home in a system that puts correctness and careful development first. Needless to say that I have already made my first donation; I sincerely thank the developers for their time and eff