| 34 | | '''EDIT''': maybe bash attempts to open itself (??) à la B_READ_WRITE, which fails in packagefs (regardless of whether or not the 'w' bit it set or not, of course, being a read-only fs), but succeeds in bfs, allowing the bfs variant to get past that error and hit another one downstream ? |
| | 34 | '''EDIT''': maybe bash attempts to open itself (wow!?) à la B_READ_WRITE, which fails in packagefs (regardless of whether or not the 'w' bit it set or not, of course, being a read-only fs), but succeeds in bfs, allowing the bfs variant to get past that error and hit another one downstream ? |
| | 35 | |
| | 36 | EDIT2: yea also tried changing rights to config/settings/bash_history, allocating its own homedir instead of /boot/home, makes no difference; strange as that is, it seems the bash file itself is the issue. |
| | 37 | Running `ll /system` is a bit scary by the way: most of its contents is 600 (instead of 644) ! Including '''runtime_loader'''... I wonder if VFS/BFS will allow non-superuser access to runtime_loader if it's '''rw-------" ? |
| | 38 | |
| | 39 | |
