I just made a fresh iso off this site and put it on a bootable usb and have begun configuring it like I've done a dozen times before (16 modules total, no gui just cli). Wierdest thing, but some directories show empty when I do an "ls" on them but the files are still there. For example when I do "ls /var/log" shows nothing, it just goes to the next line on the command prompt. Same when I do an "ls -a /var/log", but when I do "cat /var/log/messages" the file is there and I get the log output, it just doesn't show in an "ls". There are a couple other directories like this, but other than that "ls" would appear to work everywhere else. The system is working, and if I know the name of the file I am looking for I can work on it, but this is the weirdest thing I've seen. I've spent a whole day configuring this setup and would rather not start over from scratch. Does anybody have an idea why "ls" isn't working?
This happens when, for instance you try to 'ls' a directory that you don't own
(and that have no write or read permission for other users).
For example, in a distro with 2 users (root, and an ordinary user) if you do ls /root
as the ordinary user, you get this message
ls: cannot open directory /root: Permission denied
Do you get a similar message?
What does the command whoami
return? And what does ls -ld /var/log shows?
Check if the user returned by whoami is the same as the one that appears in the second command,
and check the permissions, is it drwx--x--?
I'm logged in as root on a fresh install. There shouldn't be permissions issues. As for changing the permissions to rw I've been creating files on it all day/rebooting and then creating more without issues.
What fixed this was deleting the "/mnt/sda/slax/changes/var/log" and the "/mnt/sda/slax/changes/etc/samba" directories. The posixovl files had been corrupted.
What fixed this was deleting the "/mnt/sda/slax/changes/var/log" and the "/mnt/sda/slax/changes/etc/samba" directories. The posixovl files had been corrupted. >gt46l
+++++++++++++
There ya go. The permanent solution to this is to save changes in a slaxsave.dat file.
How would I migrate to that, or is that assuming you are starting with a new install from scratch (no changes yet)? Probably seems like a stupid question, but I don't want to blow up my install after 2 weeks setting it up and scripting the way I want it. I want to make sure that making a change like changes=slaxsave.dat will A. save all my pre-dat file changes and B. not lose all my current changes.
Anybody done this before? Is there a process to follow to migrate to this or does it just pick up all the changes and shuv them into the dat file on the first reboot? Does it leave changes diretories that you can delete afterwards?
No, changing to slaxsave.dat will not forward any previous changes, it will be as if you started fresh. The advantage is that there will not be any future corruption from saving changes on a vfat filesystem.
But do you really want to do that? It might be possible, but you'd also be forwarding any corruption, like the problem you had at the head of this thread.
If your current cheatcodes use 'changes=/slax' then look under /slax on your usbstick, may be a subdir named /changes. If so, then boot to always fresh, and then cd to /slax, and run #dir2lzm /changes /zchanges.lzm ... and then when that finishes, and you get a prompt back, copy /zchanges.lzm to /slax/modules, and then rename /changes to /ex-changes, and finally reboot to always fresh again. If your previous changes appear to still be in place, then you can edit your slax.cfg to 'changes=slaxsave.dat' and start with an empty slaxsave.dat with no loss. But be aware, doing this you may be propagating corruption that you simply haven't seen yet. Far safer to start over.
Thx for both the suggestions. I found a usb stick ripper called imageusb and I backed up my install. Got another usb stick and cloned it so I can work on that w/o affecting my working version. Going to work on the slaxsave.dat migration this week.
