Tiny Core Base > Release Candidate Testing

tinycore_v2.11rc2

<< < (3/6) > >>

curaga:

--- Quote from: sci_fi on April 24, 2010, 07:23:33 AM ---Good Morning:

Two questions/comments re rc2

1. I load all my extensions into RAM. While loading extensions with rc2 I get an error message for each extension:

 Error: Could not umount /mnt/test Permission denied.

I then find many (apparently one per extension) "/mnt/test" mounted.

I did not change anything from rc1 so something is different here.

--- End quote ---

Good find. This is from the busybox update, now it behaves more properly like the GNU versions, and we had depended on the old behavior.

The point being that random loop mounts cannot be unmounted by users. Adding sudo there should fix it.


--- Quote ------ tce-load   2010-04-24 14:49:42.000000000 +0300
+++ tce-load.new   2010-04-24 14:53:45.000000000 +0300
@@ -55,7 +55,7 @@
          yes n | sudo cp -ai /mnt/test/. / 2>/dev/null
          [ -d /mnt/test/usr/local/lib/modules ] && MODULES=TRUE
       fi
-      busybox umount -d /mnt/test
+      sudo busybox umount -d /mnt/test
    fi
 }
 
--- End quote ---


--- Quote ---2. I also do not understand .X.d/
The directory is there containing wbar file with one line relating to wbar. My .xsession file is there and everything seems to work as before. To test,  I renamed .xsession and restarted x. I then got a new .xsession fine which was fine except my own customizations (starting xscreensaver) are not present (as expected).

Should I copy my working .xsession into .X.d/wbar and delete .xsession  going forward. Is something else required?

Thanks and best regards,

sci_fi

--- End quote ---

You can put new files there for autostarting with X. For example you could create a new file there to start xscreensaver, and so not need to change anything in .xsession between core updates.

jur:
Any idea why the /.X.d is not present in my persistent /home? wbar does load despite its absence.

curaga:
If you already had persistent home, it is not touched during updates. You'll need to manually check against /etc/skel if you wish to change something.

jur:

--- Quote from: curaga on April 24, 2010, 08:18:04 AM ---If you already had persistent home, it is not touched during updates. You'll need to manually check against /etc/skel if you wish to change something.

--- End quote ---
But when I renamed .xsession, a fresh one WAS copied across to my persistent /home. So why not /.X.d?

curaga:
That would be a special case, if .xsession does not exist, it's restored by xsetup (which is run by startx if .xsession is not there). More bullet-proof X that way ;)

Navigation

[0] Message Index

[#] Next page

[*] Previous page