15-CURRENT

R

rshad muhammad

Hi. I know This version is not covered. sTill i would like to share the issues i've had with it. same error.

+ vi .config/hypr/hyprland.conf
ex/vi: Error: Log file: Permission denied. midnight commander starts with
+ mc -u
Cannot create temporary directory /tmp/mc-S5Q962: Permission denied (13).
Temporary files will not be created
Press any key to continue...
fyi, it was ok initially. This morning i woke up. and then i got this issue.
+ uname -aKU
FreeBSD mrpju 15.0-CURRENT FreeBSD 15.0-CURRENT main-n277432-bada3811884c GENERIC amd64 1500043 1500043
Btw, i am using a custom kernel, but it show a different one.
 
i tried to boot to a different kernel, but still the same issue n error message. since i am using bectl, i rebooted back to the default. Still the same.

BE Active Mountpoint Space Created
15C - - 8.41G 2025-05-22 14:38
default NR / 5.87G 2025-05-22 09:16

+ vi .config/hypr/hyprland.conf
ex/vi: Error: Log file: Permission denied

This issue on 15-CURRENT has happened to me too many times.
 
First... keep in mind that CURRENT is an unsupported version and thus more or less offtopic on this forum. Second... you're not giving us much to go on. Considering the error I'm tempted to blame userland settings instead of contributing this to a problem with the OS itself. How did you set up /tmp in the first place? So many possibilities.. could be a dedicated directory, could be something you set up with tmpfs or a mixture thereof.

I've been using CURRENT for a while now and even though I have had some hiccups every once in a while I never had permission issues. In fact... I updated my system just yesterday (world + kernel, up to commit 9c20010361854a6034595fdb13cd3583ea13f289) and things are running smoothly with MC. /tmp is behaving just like it always has, so does vi and vim.

Start by identifying what you're using exactly, check permissions and optionally run a trace (strace / ktrace) and see what that tells you.

No offense intended (!) but this should be very easy to solve, if this is giving you issues then maybe CURRENT isn't the best choice to use.
 
FYI: My configuration for /tmp in /etc/fstab is as follows.
Code: 
tmpfs    /tmp    tmpfs    rw,mode=1777    0    0
It's oldish (considered not enough secure recently) in mode (maybe rw,mode=1666 recently?), but I'm the only user of my computer and I'm basically building everything executable locally.
 
In those cases, remount to rw would be needed.
mount -uw /
And if you're on ZFS,
zfs mount -a
would be needed additionally.
And any more non-ZFS filesystems, too,
mount -a
is needed, too.
 
Thank you for the reply.
are you logged in as root in a desktop env and then operating as a regular user in a terminal?
i login as normal user:1001. i use doas n very seldom su. This is my fstab.
+ cat /etc/fstab
# Device Mountpoint FStype Options Dump Pass#
/dev/gpt/efiboot0 /boot/efi msdosfs rw 2 2
/dev/nda0p3 none swap sw 0 0
proc /proc procfs rw 0 0
fdesc /dev/fd fdescfs rw,auto,late 0 0
tmpfs /tmp tmpfs rw,mode=0177 0 0

Are you in single user mode with a READ-ONLY filesystem ?
no. i only do so if i am unable to boot.

How did you set up /tmp in the first place?
i just put it in fstab.
 
rshad muhammad said:
tmpfs /tmp tmpfs rw,mode=0177 0 0
Click to expand...
There you go. A better mode would be 1777, this allows everyone to access the directory.

It's a bit odd to see this, because when I check /etc/rc.d/tmp then it specifically issues chmod 01777 /tmp to cover this. So instead of using /etc/fstab it's probably easier to specifically enable tmpfs using /etc/rc.conf.

By default it's set to "AUTO", but you can also specifically enable it by using "YES".
 
ShelLuser said:
There you go. A better mode would be 1777, this allows everyone to access the directory.

It's a bit odd to see this, because when I check /etc/rc.d/tmp then it specifically issues chmod 01777 /tmp to cover this. So instead of using /etc/fstab it's probably easier to specifically enable tmpfs using /etc/rc.conf.

By default it's set to "AUTO", but you can also specifically enable it by using "YES".
Click to expand...
i got it from one of the post i read.
So instead of using /etc/fstab it's probably easier to specifically enable tmpfs using /etc/rc.conf.
how do you do that?
is this ok?
tmpmfs="YES"
tmpsize="1024m"
tmpmfs_flags="-m 0 -o async,noatime -S -p 1777"

all my settings n configurations are taken from post i have read.
 
rshad muhammad said:
i got it from one of the post i read.
So instead of using /etc/fstab it's probably easier to specifically enable tmpfs using /etc/rc.conf.
how do you do that?
is this ok?
tmpmfs="YES"
tmpsize="1024m"
tmpmfs_flags="-m 0 -o async,noatime -S -p 1777"

all my settings n configurations are taken from post i have read.
Click to expand...

That enables an md device with ufs on it, not tmpfs.

tmpfs devices have a built-in filesystem, so they are aware of file deletion , and can free up memory.
 
bob2112 said:
That enables an md device with ufs on it, not tmpfs.

tmpfs devices have a built-in filesystem, so they are aware of file deletion , and can free up memory.
Click to expand...
That enables an md device with ufs on it, not tmpfs.

oohhh. Thank u. could u show me how to enable tmpfs in /etc/rc.conf?
 
Actually you can use the RC system... as I mentioned above: check /etc/rc.d/tmp, but when in doubt also check /etc/defaults/rc.conf. In this case you're looking for:
Code: 
mfs_type="auto"         # "md", "tmpfs", "auto" to prefer tmpfs with md as fallback
So no, it's not an MD device per definition, but when in doubt.. just enforce tmpfs only.
 
T-Aoki said:
FYI: My configuration for /tmp in /etc/fstab is as follows.
Code: 
tmpfs    /tmp    tmpfs    rw,mode=1777    0    0
It's oldish (considered not enough secure recently) in mode (maybe rw,mode=1666 recently?), but I'm the only user of my computer and I'm basically building everything executable locally.
Click to expand...
i never knew it changed to 1777, furthermore to 1666.
Thankx all for telling me this.
 
Basically, making any directory / file that "everyone can write" to be executalbe is considered insecure recently. But it's on admins.
 
T-Aoki said:
Basically, making any directory / file that "everyone can write" to be executalbe is considered insecure recently.
Click to expand...
That doesn't make much sense to me, +x on directory only means that you can enumerate files in it. Even with files having +x set on them, what are the possible security concerns? Note that /tmp is mounted with nosuid by default.
 
Well, if any malicious program (including scripts in any web sites) generates scripts and/or binaries under /tmp, it can invoke it if +x is set.
Yes, if the bitten user is really a regular user without system-wide priviledges, system-wide problems wouldn't happen "directly by the generated codes".
But sensitive info of the user can be stolen, or configurations of the specific user could be destroyed (as kinda sandboxes usually, AFAIK, applied inside the user's home directory).

I think this is the reason /tmp, /var/tmp and any other temporary directories are recommended to be "non-executable" recently.
 
you can mount them with noexec and this will prevent binaries from being run (directory still stays a+x)
a noexec /tmp will break make installworld and tmpfs does not support mount -u :( /tmp as tempdir can be overriden for make installworld if you don't forget about it
 
You must log in or register to reply here.
Back
Top