From: Keith M. <kei...@us...> - 2012-11-30 22:18:21
|
On 30/11/12 21:02, Renato Silva wrote: > Anyway, point taken. However, how about /etc/fstab? My customizations > weren't overwritten for this file. In MSYS, /etc/fstab is a historical anomaly; it isn't used as its namesake on traditional unix systems, isn't distributed, and should really have been called /etc/mtab or /etc/mnttab, (for these are its closest analogues in such traditional unix systems). In MSYS usage today, /etc/fstab is created dynamically when you mount its virtual file systems; (historically, the mount command didn't fulfil this function; you "mounted" file systems by editing /etc/fstab directly). > 4) If user-specific customisations aren't sufficient, add a custom > hook script, (or more than one, if you prefer), in /etc/profile.d; > (anything you place here is your's to maintain, in perpetuity, > and will be sourced by /etc/profile at login shell invocation). > > I have moved the timezone script to that directory, and it worked fine > except that we need to add the .sh extension. Which is how it is on my Debian system too. I guess the idea is to discriminate between initialisation scripts for Bourne class shells, and those for other shells; of course, we don't offer alternative (non-Bourne) shells with MSYS. > That was also for having MSYS utilities available outside bash in general, We neither endorse, nor support such usage. It may work, sometimes; it may also go horribly wrong. YMMV, but if it blows up in your face, you are on your own. > for example not just cmd.exe (if I'm forced to use it for any reason, > e.g. for applying the announced update) But, you aren't running an MSYS application when you do this; (in fact you must not be running any MSYS application in any process on the box). Eventually, you won't use cmd.exe to launch mingw-get when you perform such upgrades; you will use the GUI, (as I did last night, as a test of my current development prototype). -- Regards, Keith. |