Re: File system is full after using dd
> If you had an appropriate sized root partition, perhaps 1G (default),I was >using the default partitioning before but I had to reinstall the system >because kf that: I couldn't install packages because /usr partition was full >after a week of usage. I'm new to OpenBSD and I'm still learning how to manage >it (even though I am loving how simpler is compared to other unix systems). I >know that I was doing something wrong but this seemed the most natural >solution to me.Lorenzo Torres (https://sagittarius-a.org)
Re: File system is full after using dd
On 2023-04-15, Nick Holland wrote: > Partition your system. And / should be as small as you can sanely > get away with. That isn't to say it should be super-tiny. But > if you have 1GB to spare, it is probably too big. I disagree on that, around 1GB to spare on / seems pretty comfortable unless you're on a small-for-modern-standards disk. A couple of standard kernels at ~25MB each, maybe a kernel with debug symbols (140M-odd), a couple of old ones while investigating problems, /etc/firmware, it adds up, and the files typically on / can't be split out into a second filesystem.
7.3: speetest doesn't work
Hi, after sysupgrade to 7.3 and pkg_add -u and reboot: > speedtest-cli --secure Could not find platform independent libraries Could not find platform dependent libraries Consider setting $PYTHONHOME to [:] Python path configuration: PYTHONHOME = (not set) PYTHONPATH = (not set) program name = '/usr/local/bin/python3.10' isolated = 0 environment = 1 user site = 1 import site = 1 sys._base_executable = '/usr/local/bin/python3.10' sys.base_prefix = '/usr/local' sys.base_exec_prefix = '/usr/local' sys.platlibdir = 'lib' sys.executable = '/usr/local/bin/python3.10' sys.prefix = '/usr/local' sys.exec_prefix = '/usr/local' sys.path = [ '/usr/local/lib/python310.zip', '/usr/local/lib/python3.10', '/usr/local/lib/lib-dynload', ] Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized ModuleNotFoundError: No module named 'encodings' Current thread 0x0beeef85d660 (most recent call first): dmesg is at https://www.oneiros.de/privat/openbsd/dmesg73.txt Thanks in advance Martin
Re: 7.3: speetest doesn't work
On Sun, 2023-04-16 at 14:41 +0200, Martin Schröder wrote: > > Fatal Python error: init_fs_encoding: failed to get the Python codec > of the filesystem encoding > Python runtime state: core initialized > ModuleNotFoundError: No module named 'encodings' > Is speedtest-cli installed via pkg_add? It looks like it was installed via pip or source package before the upgrade. I think you should reinstall speedtest-cli or re-build.
Re: 7.3: speetest doesn't work
Am So., 16. Apr. 2023 um 14:56 Uhr schrieb lux : > > On Sun, 2023-04-16 at 14:41 +0200, Martin Schröder wrote: > > > > Fatal Python error: init_fs_encoding: failed to get the Python codec > > of the filesystem encoding > > Python runtime state: core initialized > > ModuleNotFoundError: No module named 'encodings' > > > > Is speedtest-cli installed via pkg_add? pkg_add > It looks like it was installed via pip or source package before the > upgrade. > > I think you should reinstall speedtest-cli or re-build. > sudo pkg_delete speedtest-cli speedtest-cli-2.1.4beta1: ok Read shared items: ok [20230416T15:04:12+0200(106/15)] ms@wyvern 1032:~ > speedtest-cli --secure -bash: /usr/local/bin/speedtest-cli: No such file or directory [20230416T15:04:25+0200(106/15)] ms@wyvern 1033:~ > sudo pkg_add speedtest-cli quirks-6.121 signed on 2023-04-15T20:15:19Z speedtest-cli-2.1.4beta1: ok [20230416T15:04:36+0200(106/15)] ms@wyvern 1034:~ > speedtest-cli --secure Could not find platform independent libraries Could not find platform dependent libraries Consider setting $PYTHONHOME to [:] Python path configuration: PYTHONHOME = (not set) PYTHONPATH = (not set) program name = '/usr/local/bin/python3.10' isolated = 0 environment = 1 user site = 1 import site = 1 sys._base_executable = '/usr/local/bin/python3.10' sys.base_prefix = '/usr/local' sys.base_exec_prefix = '/usr/local' sys.platlibdir = 'lib' sys.executable = '/usr/local/bin/python3.10' sys.prefix = '/usr/local' sys.exec_prefix = '/usr/local' sys.path = [ '/usr/local/lib/python310.zip', '/usr/local/lib/python3.10', '/usr/local/lib/lib-dynload', ] Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized ModuleNotFoundError: No module named 'encodings' Current thread 0x0194a7b6c660 (most recent call first):
7.3: outdated mandoc.db lacks mutt(1) entry, run makewhatis /usr/local/man
Hi, after upgrading to 7.3 man is somehow confused: > man mutt man: /usr/local/man/mandoc.db: Permission denied man: outdated mandoc.db lacks mutt(1) entry, run makewhatis /usr/local/m Neither makewhatis /usr/local/man nor sudo makewhatis /usr/local/man helps. :-( How to fix? Thanks in advance Martin
Re: 7.3: outdated mandoc.db lacks mutt(1) entry, run makewhatis /usr/local/man
On 2023/04/16 15:10, Martin Schröder wrote: > Hi, > after upgrading to 7.3 man is somehow confused: > > > man mutt > man: /usr/local/man/mandoc.db: Permission denied > man: outdated mandoc.db lacks mutt(1) entry, run makewhatis /usr/local/m > > Neither >makewhatis /usr/local/man > nor >sudo makewhatis /usr/local/man > helps. :-( Ah yes, let's add to my previous mail: > You probably ran pkg_add with a restrictive umask set. > If you do that, permissions on @sample files and some others > (e.g. /var/db/pkg) follow what the umask is set to. ^^ and mandocdb files :)
Re: 7.3: speetest doesn't work
On 2023/04/16 15:05, Martin Schröder wrote: > Am So., 16. Apr. 2023 um 14:56 Uhr schrieb lux : > > > > On Sun, 2023-04-16 at 14:41 +0200, Martin Schröder wrote: > > > > > > Fatal Python error: init_fs_encoding: failed to get the Python codec > > > of the filesystem encoding > > > Python runtime state: core initialized > > > ModuleNotFoundError: No module named 'encodings' > > > > > > > Is speedtest-cli installed via pkg_add? > > pkg_add > > > It looks like it was installed via pip or source package before the > > upgrade. > > > > I think you should reinstall speedtest-cli or re-build. > > > sudo pkg_delete speedtest-cli > speedtest-cli-2.1.4beta1: ok > Read shared items: ok > [20230416T15:04:12+0200(106/15)] ms@wyvern 1032:~ > > speedtest-cli --secure > -bash: /usr/local/bin/speedtest-cli: No such file or directory > [20230416T15:04:25+0200(106/15)] ms@wyvern 1033:~ > > sudo pkg_add speedtest-cli > quirks-6.121 signed on 2023-04-15T20:15:19Z > speedtest-cli-2.1.4beta1: ok > [20230416T15:04:36+0200(106/15)] ms@wyvern 1034:~ > > speedtest-cli --secure > Could not find platform independent libraries > Could not find platform dependent libraries > Consider setting $PYTHONHOME to [:] > Python path configuration: > PYTHONHOME = (not set) > PYTHONPATH = (not set) > program name = '/usr/local/bin/python3.10' > isolated = 0 > environment = 1 > user site = 1 > import site = 1 > sys._base_executable = '/usr/local/bin/python3.10' > sys.base_prefix = '/usr/local' > sys.base_exec_prefix = '/usr/local' > sys.platlibdir = 'lib' > sys.executable = '/usr/local/bin/python3.10' > sys.prefix = '/usr/local' > sys.exec_prefix = '/usr/local' > sys.path = [ > '/usr/local/lib/python310.zip', > '/usr/local/lib/python3.10', > '/usr/local/lib/lib-dynload', > ] > Fatal Python error: init_fs_encoding: failed to get the Python codec > of the filesystem encoding > Python runtime state: core initialized > ModuleNotFoundError: No module named 'encodings' > > Current thread 0x0194a7b6c660 (most recent call first): > So let's also add "newly created directories" to the list of things where umask messes up pkg_add ;) In this case, it will be /usr/local/lib/python3.10/encodings/
Re: 7.3: speetest doesn't work
Am So., 16. Apr. 2023 um 15:38 Uhr schrieb Stuart Henderson : > So let's also add "newly created directories" to the list of things > where umask messes up pkg_add ;) In this case, it will be > /usr/local/lib/python3.10/encodings/ Probably more. In the end I did sudo chmod -R go+rX /usr/local/lib/python3.10/ as sudo chmod -R go+rX /usr/local/lib/python3.10/encodings/ wasn't enough. :-( Best Martin
Re: 7.3: speetest doesn't work
On 2023/04/16 15:42, Martin Schröder wrote: > Am So., 16. Apr. 2023 um 15:38 Uhr schrieb Stuart Henderson > : > > So let's also add "newly created directories" to the list of things > > where umask messes up pkg_add ;) In this case, it will be > > /usr/local/lib/python3.10/encodings/ > > Probably more. In the end I did > sudo chmod -R go+rX /usr/local/lib/python3.10/ > as >sudo chmod -R go+rX /usr/local/lib/python3.10/encodings/ > > wasn't enough. :-( > > Best > Martin > At this point I think you might be better served by dumping the package list, uninstalling them all, and reinstalling with 022 umask. Borrowing the old instructions from the 5.5 time_t flag day release notes, this also keeps the "auto installed" / "manually installed" markers (so that pkg_delete -a still behaves how you want): pkg_info -mq >/root/pkg_list_manual pkg_info -q >/root/pkg_list_full pkg_delete -X /var/db/pkg/*-firmware-[0-9]* pkg_add -z -l /root/pkg_list_manual pkg_add -za -l /root/pkg_list_full
Re: 7.3: speetest doesn't work
Am So., 16. Apr. 2023 um 15:49 Uhr schrieb Stuart Henderson : > At this point I think you might be better served by dumping the > package list, uninstalling them all, and reinstalling with 022 umask. > > Borrowing the old instructions from the 5.5 time_t flag day release > notes, this also keeps the "auto installed" / "manually installed" > markers (so that pkg_delete -a still behaves how you want): > > pkg_info -mq >/root/pkg_list_manual > pkg_info -q >/root/pkg_list_full > pkg_delete -X /var/db/pkg/*-firmware-[0-9]* > pkg_add -z -l /root/pkg_list_manual > pkg_add -za -l /root/pkg_list_full Thanks, that helped. Best Martin
Re: 7.3: speetest doesn't work
Martin Schröder wrote: > Am So., 16. Apr. 2023 um 15:49 Uhr schrieb Stuart Henderson > : > > At this point I think you might be better served by dumping the > > package list, uninstalling them all, and reinstalling with 022 umask. > > > > Borrowing the old instructions from the 5.5 time_t flag day release > > notes, this also keeps the "auto installed" / "manually installed" > > markers (so that pkg_delete -a still behaves how you want): > > > > pkg_info -mq >/root/pkg_list_manual > > pkg_info -q >/root/pkg_list_full > > pkg_delete -X /var/db/pkg/*-firmware-[0-9]* > > pkg_add -z -l /root/pkg_list_manual > > pkg_add -za -l /root/pkg_list_full OK, that's ridiculous. This got to be a bug. I cannot see any situation where you want packages to be installed in that way. What is the justification?
Re: File system is full after using dd
> Packages should be installing into /usr/local which should be a separate > partition from /usr. I know, in the last install I had something around 300 > packages installed and after trying to install qemu the partition ran out of > space. I could try to install the system again since I have no data to loose > but I have to change the default partition scheme for sure.Lorenzo Torres > (https://sagittarius-a.org)
