Tiny Core Base > Release Candidate Testing
Core v7.0beta2
gerald_clark:
Why not set them in bootsync.sh until the issue is resolved.
andyj:
I could. But I think the ideal extension is one that you can load and it will work without a whole lot of having to fix stuff afterwards if you know it needs to be fixed and can take care of it when it loads. The previous version of open-vm-tools used a kernel driver so the permissions on /dev/fuse weren't an issue. Now, since it's in userspace the permissions matter, and because they matter, why not make sure that they are what they need to be and not hope they are. I think doing as part of the extension initialization is preferable to having to document "to use this extension add 'chmod 1666 /dev/fuse' to /opt/bootsync.sh' until further notice". I know it's a kludge and I don't like it either, but I like not taking care of it when I know it needs to be done and leaving it for someone else even less.
andyj:
I think the double window manager extension being loaded fix is simple, if I'm reading tc-install.sh right. On line 38 the current $DESKTOP is added to onboot.lst, so that part should stay. On line 768 flwm_topside.tcz is hard coded in the list of extensions to load and I think that should be deleted. If flwm_topside is the desktop it will get added in 38. This also explains why I was seeing it twice in onboot.lst.
Juanito:
tc-install updated - thanks :)
Juanito:
--- Quote from: andyj on January 21, 2016, 11:17:32 AM ---Further testing reveals that loading libXdamage or libXxf86vm will also change the permissions on /dev/fuse to 1600, and that loading i2c-KERNEL or libX11-dev will reset them to 1666.
--- End quote ---
Did you try "udevadm monitor" to try to see why the changes happen?
I tried with libX11-dev (and i2c-KERNEL), but the permissions were not reset to 1666.
terminal 1:
--- Code: ---$ sudo chmod 1600 /dev/fuse
$ ls -l /dev/fuse
crw------T 1 root root 10, 229 Jan 22 08:50 /dev/fuse
$ tce-load -i libX11-dev
libXdmcp-dev.tcz: OK
libxcb-dev.tcz: OK
libX11-dev.tcz: OK
$ ls -l /dev/fuse
crw------T 1 root root 10, 229 Jan 22 08:50 /dev/fuse
--- End code ---
terminal 2:
--- Code: ---$ udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[1115.966588] add /devices/virtual/bdi/7:73 (bdi)
KERNEL[1115.966627] add /devices/virtual/block/loop73 (block)
UDEV [1115.966822] add /devices/virtual/bdi/7:73 (bdi)
KERNEL[1115.966868] change /devices/virtual/block/loop73 (block)
UDEV [1115.967011] add /devices/virtual/block/loop73 (block)
UDEV [1115.967329] change /devices/virtual/block/loop73 (block)
KERNEL[1116.017148] add /devices/virtual/bdi/7:74 (bdi)
KERNEL[1116.017185] add /devices/virtual/block/loop74 (block)
UDEV [1116.017326] add /devices/virtual/bdi/7:74 (bdi)
KERNEL[1116.017382] change /devices/virtual/block/loop74 (block)
UDEV [1116.017490] add /devices/virtual/block/loop74 (block)
UDEV [1116.017702] change /devices/virtual/block/loop74 (block)
KERNEL[1116.063067] add /devices/virtual/bdi/7:75 (bdi)
KERNEL[1116.063092] add /devices/virtual/block/loop75 (block)
KERNEL[1116.063166] change /devices/virtual/block/loop75 (block)
UDEV [1116.063247] add /devices/virtual/bdi/7:75 (bdi)
UDEV [1116.063386] add /devices/virtual/block/loop75 (block)
UDEV [1116.063600] change /devices/virtual/block/loop75 (block)
--- End code ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version