#nfs4 — Public Fediverse posts

@photocyte ah yes, hashtags, forgot about those.

so, `mount` is setuid and mounting a filesystem as not-root is a totally acceptable and normal thing to be able to do, and the code is nominally set up to do it but it looks a heck of a lot like /[gs]ete?uid/ is being called in lieu of its counterpart, because the net effect is root needs a copy of the non-root user's kerberos ticket as well for it to work, which is SUPER annoying for e.g. ticket renewal

#nfs #nfs4 #nfsv4 #kerberos #krb5

@photocyte ah yes, hashtags, forgot about those.

so, `mount` is setuid and mounting a filesystem as not-root is a totally acceptable and normal thing to be able to do, and the code is nominally set up to do it but it looks a heck of a lot like /[gs]ete?uid/ is being called in lieu of its counterpart, because the net effect is root needs a copy of the non-root user's kerberos ticket as well for it to work, which is SUPER annoying for e.g. ticket renewal

#nfs #nfs4 #nfsv4 #kerberos #krb5

@photocyte ah yes, hashtags, forgot about those.

so, `mount` is setuid and mounting a filesystem as not-root is a totally acceptable and normal thing to be able to do, and the code is nominally set up to do it but it looks a heck of a lot like /[gs]ete?uid/ is being called in lieu of its counterpart, because the net effect is root needs a copy of the non-root user's kerberos ticket as well for it to work, which is SUPER annoying for e.g. ticket renewal

#nfs #nfs4 #nfsv4 #kerberos #krb5

@photocyte ah yes, hashtags, forgot about those.

so, `mount` is setuid and mounting a filesystem as not-root is a totally acceptable and normal thing to be able to do, and the code is nominally set up to do it but it looks a heck of a lot like /[gs]ete?uid/ is being called in lieu of its counterpart, because the net effect is root needs a copy of the non-root user's kerberos ticket as well for it to work, which is SUPER annoying for e.g. ticket renewal

#nfs #nfs4 #nfsv4 #kerberos #krb5

@photocyte ah yes, hashtags, forgot about those.

so, `mount` is setuid and mounting a filesystem as not-root is a totally acceptable and normal thing to be able to do, and the code is nominally set up to do it but it looks a heck of a lot like /[gs]ete?uid/ is being called in lieu of its counterpart, because the net effect is root needs a copy of the non-root user's kerberos ticket as well for it to work, which is SUPER annoying for e.g. ticket renewal

#nfs #nfs4 #nfsv4 #kerberos #krb5

@doriantaylor #nfs #nfs4 #nfsv4

@doriantaylor #nfs #nfs4 #nfsv4

@doriantaylor #nfs #nfs4 #nfsv4

@doriantaylor #nfs #nfs4 #nfsv4

@doriantaylor #nfs #nfs4 #nfsv4

Когда я играл в #NFS4 я перепробовал все #PS1 ядра в #RetroArch , но в игре всё равно проседала частота кадров. Особенно на французской трассе с воздушным шаром.

Сейчас попробовал DuckStation, проехал по этой трассе дважды и не заметил проседаний. Стабильные 59.82 кадра в секунду.

И да это на смартфоне.

Когда я играл в #NFS4 я перепробовал все #PS1 ядра в #RetroArch , но в игре всё равно проседала частота кадров. Особенно на французской трассе с воздушным шаром.

Сейчас попробовал DuckStation, проехал по этой трассе дважды и не заметил проседаний. Стабильные 59.82 кадра в секунду.

И да это на смартфоне.

Когда я играл в #NFS4 я перепробовал все #PS1 ядра в #RetroArch , но в игре всё равно проседала частота кадров. Особенно на французской трассе с воздушным шаром.

Сейчас попробовал DuckStation, проехал по этой трассе дважды и не заметил проседаний. Стабильные 59.82 кадра в секунду.

И да это на смартфоне.

Когда я играл в #NFS4 я перепробовал все #PS1 ядра в #RetroArch , но в игре всё равно проседала частота кадров. Особенно на французской трассе с воздушным шаром.

Сейчас попробовал DuckStation, проехал по этой трассе дважды и не заметил проседаний. Стабильные 59.82 кадра в секунду.

И да это на смартфоне.

Когда я играл в #NFS4 я перепробовал все #PS1 ядра в #RetroArch , но в игре всё равно проседала частота кадров. Особенно на французской трассе с воздушным шаром.

Сейчас попробовал DuckStation, проехал по этой трассе дважды и не заметил проседаний. Стабильные 59.82 кадра в секунду.

И да это на смартфоне.

i was just thinking about how hard it is to fix third-party open-source software

for instance, i use #nfs4 with #kerberos and there is a bug that requires me to maintain two tickets (one owned by root but as my principal, one normal one as me) and i am dead certain i could fix it but i have no idea where it is and i can't even get anybody on the linux nfs mailing list to even acknowledge it or me

i am dead certain it's a one-line fix, the question is WHERE

Ok, tech mastodon, anyone here have some serious kung-fu around #nfsv4 on #macos?

I've got a file server running #debian, it's exporting a directory via #nfs4 and I have a mac that can mount that directory. A user on the mac has the same username as a user on the server, and the /etc/nfs.conf settings map that successfully.

Doing shell commands like cp and echo foo > file and such works fine. But copying files in finder or trying to open or save word docs etc borks.

i was just thinking about how hard it is to fix third-party open-source software

for instance, i use #nfs4 with #kerberos and there is a bug that requires me to maintain two tickets (one owned by root but as my principal, one normal one as me) and i am dead certain i could fix it but i have no idea where it is and i can't even get anybody on the linux nfs mailing list to even acknowledge it or me

i am dead certain it's a one-line fix, the question is WHERE

i was just thinking about how hard it is to fix third-party open-source software

for instance, i use #nfs4 with #kerberos and there is a bug that requires me to maintain two tickets (one owned by root but as my principal, one normal one as me) and i am dead certain i could fix it but i have no idea where it is and i can't even get anybody on the linux nfs mailing list to even acknowledge it or me

i am dead certain it's a one-line fix, the question is WHERE

i was just thinking about how hard it is to fix third-party open-source software

for instance, i use #nfs4 with #kerberos and there is a bug that requires me to maintain two tickets (one owned by root but as my principal, one normal one as me) and i am dead certain i could fix it but i have no idea where it is and i can't even get anybody on the linux nfs mailing list to even acknowledge it or me

i am dead certain it's a one-line fix, the question is WHERE

i was just thinking about how hard it is to fix third-party open-source software

for instance, i use #nfs4 with #kerberos and there is a bug that requires me to maintain two tickets (one owned by root but as my principal, one normal one as me) and i am dead certain i could fix it but i have no idea where it is and i can't even get anybody on the linux nfs mailing list to even acknowledge it or me

i am dead certain it's a one-line fix, the question is WHERE

Ok, tech mastodon, anyone here have some serious kung-fu around #nfsv4 on #macos?

I've got a file server running #debian, it's exporting a directory via #nfs4 and I have a mac that can mount that directory. A user on the mac has the same username as a user on the server, and the /etc/nfs.conf settings map that successfully.

Doing shell commands like cp and echo foo > file and such works fine. But copying files in finder or trying to open or save word docs etc borks.

Ok, tech mastodon, anyone here have some serious kung-fu around #nfsv4 on #macos?

I've got a file server running #debian, it's exporting a directory via #nfs4 and I have a mac that can mount that directory. A user on the mac has the same username as a user on the server, and the /etc/nfs.conf settings map that successfully.

Doing shell commands like cp and echo foo > file and such works fine. But copying files in finder or trying to open or save word docs etc borks.

Ok, tech mastodon, anyone here have some serious kung-fu around #nfsv4 on #macos?

I've got a file server running #debian, it's exporting a directory via #nfs4 and I have a mac that can mount that directory. A user on the mac has the same username as a user on the server, and the /etc/nfs.conf settings map that successfully.

Doing shell commands like cp and echo foo > file and such works fine. But copying files in finder or trying to open or save word docs etc borks.

Ok, tech mastodon, anyone here have some serious kung-fu around #nfsv4 on #macos?

I've got a file server running #debian, it's exporting a directory via #nfs4 and I have a mac that can mount that directory. A user on the mac has the same username as a user on the server, and the /etc/nfs.conf settings map that successfully.

Doing shell commands like cp and echo foo > file and such works fine. But copying files in finder or trying to open or save word docs etc borks.