04-25-2017, 03:17 PM
(04-25-2017, 12:46 PM)Jerry link Wrote: Looking at the postinst file in Lite Software, do we need the following set?
Code:chown root:root /usr/share/applications/* -R
chown root:root /usr/share/icons/* -R
chown'ing is quick and not intensive.
[/quote]
Code:
find /usr/share/applications/ -type f -exec chmod 644 {} \;
find /usr/share/icons/ -type d -exec chmod 755 {} \;
find /usr/share/icons/ -type f -exec chmod 644 {} \;This is what really takes a lot of CPU time.
Quote:Given the number of applications and icons to set, would we be better off setting perms etc for only our files/dirs ? I mention this because when Lite Software receives an update, it is very slow to install.
The problem is that permissions are wrong right from a fresh install. The ISO images carry the wrong permissions out of the box or it happens right during the installation process.
We can somewhat improve it. For example, after installation the only folder and files with wrong permissions under /usr/share/icons is Faenza. So we could do:
Code:
chown root:root /usr/share/applications/* -R
chown root:root /usr/share/icons/* -R
find /usr/share/icons/Faenza* -type d -exec chmod 755 {} \;
find /usr/share/icons/Faenza* -type f -exec chmod 644 {} \;... and that would be saving already a huge search for files and folders that did carry the correct permissions out of the box.
We can do the same with other files and folders... Just need a fresh install and go over them so we can optimize lite-software postinst accordingly.
https://unlockforus.com
Sorry for seeming stupid and preferring Linux - I just don't know any better.




![[Image: X5qGkCg.png]](https://imgur.com/X5qGkCg.png)
![[Image: 0op1GNe.png]](https://i.imgur.com/0op1GNe.png)
![[Image: LgJ2mtP.png]](https://i.imgur.com/LgJ2mtP.png)
![[Image: vLZcFUE.png]](https://imgur.com/vLZcFUE.png)
![[Image: lrUHro3.jpg]](https://i.imgur.com/lrUHro3.jpg)