Manage fstab #9

Closed
opened 2019-02-20 18:25:15 +01:00 by jdubois · 4 comments
Member

Including the option "wxallowed" needed to use python since OpenBSD 6.0, and wether "softdep" is required or not, given that it speedups file create/delete operations but can be undesirable for SD cards used on APU.

Including the option "wxallowed" needed to use python since OpenBSD 6.0, and wether "softdep" is required or not, given that it speedups file create/delete operations but can be undesirable for SD cards used on APU.

I only use softdeps on partitions that do not contain data, so /tmp, most /usr/ partitions and / are okay in my mind.

For stuff like /var, /home and /boot, kernel panics could render them unrecoverable, and your backups aren't necessarily synced yet. The rest can be recovered with bsd.rd or backups and don't need to be backup up as often.

The default OpenBSD partition setup works for python use though. /usr/local is mounted wxallowed and all scripts are run by the python interpreter, which is located in /usr/local/bin.

I only use softdeps on partitions that do not contain data, so /tmp, most /usr/ partitions and / are okay in my mind. For stuff like /var, /home and /boot, kernel panics could render them unrecoverable, and your backups aren't necessarily synced yet. The rest can be recovered with bsd.rd or backups and don't need to be backup up as often. The default OpenBSD partition setup works for python use though. /usr/local is mounted wxallowed and all scripts are run by the python interpreter, which is located in /usr/local/bin.

Yes it works in the case of an installation but not an upgrade.

Anyway it's not possible to include the management of the "wxallowed" option in a task since it would need Python to be executable in the first place…

Yes it works in the case of an installation but not an upgrade. Anyway it's not possible to include the management of the "wxallowed" option in a task since it would need Python to be executable in the first place…

Yes it works in the case of an installation but not an upgrade.

Yeah, if you're upgrading from a version before the flag became a thing, then you'll have to add it manually, though OpenBSD tends to be pretty precise when it comes to manual operations after an upgrade: https://www.openbsd.org/faq/upgrade64.html

> Yes it works in the case of an installation but not an upgrade. Yeah, if you're upgrading from a version before the flag became a thing, then you'll have to add it manually, though OpenBSD tends to be pretty precise when it comes to manual operations after an upgrade: https://www.openbsd.org/faq/upgrade64.html

Since this is inherent to the upgrade of an OpenBSD system prior to 6.0 and not related to EvoBSD itself, I suggest to close this issue.

Since this is inherent to the upgrade of an OpenBSD system prior to 6.0 and not related to EvoBSD itself, I suggest to close this issue.
Ghost closed this issue 2019-09-05 12:05:49 +02:00
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: evolix/EvoBSD#9
No description provided.