| Author |
Message |
|
|
Post subject: config file question: /etc/skel/bashrc /etc/bash/bashrc +...
 Posted: Jun 05, 2008 - 11:11 PM
|
|
Joined: Nov 28, 2006
Posts: 4303
Status: Offline
|
|
While upgrading an old sidux install, I saw these two config file questions, after viewing the diffs, I opted for 'y', since it looks like they have some interesting new options, and it's also not my working box so it's fine if something goes a bit off.
The question is, was answering 'y' to use new configs for:
/etc/skel/bashrc /etc/bash/bashrc
correct, are there any technical problems with using the new ones?
Also, /etc/init.d/procps
I chose 'y' for that one too, is this correct? Any negative repercussions?
In general I've been trying to switch my older installs more and more to use default configs, which in most cases seems to work ok, but you never can tell. |
_________________
sidux Maintenance script: dist-upgrade, kernel install, general utilities: smxi
Backup script [using rdiff-backup]: rd-h2.sh
|
| |
|
|
|
 |
|
|
|
Post subject: Re: config file question: /etc/skel/bashrc /etc/bash/bashrc
Posted: Jun 06, 2008 - 12:14 AM
|
|
Joined: Dec 19, 2006
Posts: 1030
Status: Offline
|
|
|
h2 wrote:
While upgrading an old sidux install, I saw these two config file questions, after viewing the diffs, I opted for 'y', since it looks like they have some interesting new options, and it's also not my working box so it's fine if something goes a bit off.
The question is, was answering 'y' to use new configs for:
/etc/skel/bashrc /etc/bash/bashrc
correct, are there any technical problems with using the new ones?
Also, /etc/init.d/procps
I chose 'y' for that one too, is this correct? Any negative repercussions?
In general I've been trying to switch my older installs more and more to use default configs, which in most cases seems to work ok, but you never can tell.
No problems with either of the new configfiles in their default form, as far as i know. |
|
|
| |
|
|
|
|
|
|
|
Post subject: RE: Re: config file question: /etc/skel/bashrc /etc/bash/bas
Posted: Jun 06, 2008 - 02:09 AM
|
|
Joined: Nov 28, 2006
Posts: 4303
Status: Offline
|
|
ok, thanks, I'll add a note to people to say 'y' to:
/etc/skel/bashrc
/etc/bash/bashrc
/etc/init.d/procps
thanks |
_________________
sidux Maintenance script: dist-upgrade, kernel install, general utilities: smxi
Backup script [using rdiff-backup]: rd-h2.sh
|
| |
|
|
|
|
|
|
|
Post subject: Handy text file containing upgrade notes
Posted: Jun 06, 2008 - 05:16 PM
|
|
Joined: Nov 30, 2007
Posts: 35
Location: California
Status: Offline
|
|
| One thing that I've noticed during smxi updates: those notes that tell you whether to answer Y or N to various upgrade questions are usually not readable by the time the script actually gets to the point where you need to answer the questions -- they have scrolled up past the point where you can get back to them with Shift-PgUp. It would be nice if there were some way to view the notes at any point during the script. Even just something simple, like having smxi write all the current Y/N notes to a text file in the root directory, so I can open another console session and view them when I need to actually answer the Y/N questions. |
|
|
| |
|
|
|
|
|
|
|
Post subject: Re: Handy text file containing upgrade notes
Posted: Jun 06, 2008 - 10:57 PM
|
|
Joined: Dec 01, 2007
Posts: 203
Location: Enschede NL
Status: Offline
|
|
|
RuralRob wrote:
One thing that I've noticed during smxi updates: those notes that tell you whether to answer Y or N to various upgrade questions are usually not readable by the time the script actually gets to the point where you need to answer the questions -- they have scrolled up past the point where you can get back to them with Shift-PgUp.
I haven't bothered to search myself but if anybody knows a way to increase the amount of screens accessible with shift+pgup, I'd find that very handy.
How many questions are there currently and how many do require to answer 'no'?
RuralRob wrote:
It would be nice if there were some way to view the notes at any point during the script. Even just something simple, like having smxi write all the current Y/N notes to a text file in the root directory, so I can open another console session and view them when I need to actually answer the Y/N questions.
Oh no, not the root directory, it'll get lost between all the other stuff I keep there.
( /me remembers fondly the time when you actually could bang everything on C:\ and still manage it.  ) |
|
|
| |
|
|
|
|
|
|
|
Post subject: RE: Re: Handy text file containing upgrade notes
Posted: Jun 06, 2008 - 11:03 PM
|
|
Joined: Nov 28, 2006
Posts: 4303
Status: Offline
|
|
it's the 'y' ones that matter, not the 'n' ones, 'n' is default. y is to update your config to maintainer's version.
I looked for a way to increase the page ups too, and couldn't find one, it seems to be about 6 or so max.
This issue doesn't have a perfect resolution, but maybe if some heads bounce the idea around we can come up with better options for that. |
_________________
sidux Maintenance script: dist-upgrade, kernel install, general utilities: smxi
Backup script [using rdiff-backup]: rd-h2.sh
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jun 07, 2008 - 12:50 AM
|
|
Joined: Dec 11, 2006
Posts: 9
Status: Offline
|
|
| Usually I take a "Screenshot" of this messages with my mobile. It is alway available and the resolution is sufficient, but I don't remember that I ever had to use it later on |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jun 07, 2008 - 01:04 AM
|
|
Joined: Nov 28, 2006
Posts: 4303
Status: Offline
|
|
If I really need to remember something, I use a foolproof, albeit quite radical, technology: I write it down.
That's how I get these lists of config files to ask about, I have some scratch paper in front of my monitor, and I scribble down the file path, and that way I do not lose it. Sometimes tools like pen/pencil and paper are forgotten as we play with these electronic boxes, but trust me, they still work quite well, and are totally reliable. |
_________________
sidux Maintenance script: dist-upgrade, kernel install, general utilities: smxi
Backup script [using rdiff-backup]: rd-h2.sh
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jun 07, 2008 - 02:56 AM
|
|
Joined: Dec 11, 2006
Posts: 9
Status: Offline
|
|
You're right, quite often the most simple solution is the best, but I try to avoid using scratch paper, because I've got too much notes lying around here 
Excuse me for getting a bit off topic. |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jun 08, 2008 - 03:59 PM
|
|
Joined: Nov 30, 2007
Posts: 35
Location: California
Status: Offline
|
|
|
h2 wrote:
If I really need to remember something, I use a foolproof, albeit quite radical, technology: I write it down.
OMG!!! "Write it down"??? What century is this?? We don't "write things down" any more!!!
Tree-hater.
 |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jun 08, 2008 - 05:50 PM
|
|
Joined: Nov 28, 2006
Posts: 4303
Status: Offline
|
|
RuralRob, oh, no! I use actual scratch paper, junk mail envelopes, and so on. Not actual new, fresh paper, at least not usually, except when I am following some great programming advice I once got, which is:
to design a program, with pseudocode, do NOT do it sitting in front of your computer, use paper and pen/pencil, away from the computer. This creates a very important change in your brain and thinking, and can radically improve the overall design. The rare times I follow this excellent advice I tend to not have any real issues with the execution of the design elements.
Even for that I usually use actual scratch paper, the back side of paper already used.
Re the config file stuff: It's easier than it was to write this down, because I am now starting to try to be a bit smarter (difficult, for me I admit) and now I added first: last modified date to configs, and second, I add them to the bottom of the list.
Thus, you only need to update your list with the last items after making the first one.
I tried a quick idea that would have been nifty had it worked, export the config data to a variable, but that didn't last between terminals, probably because i misunderstand the way export and terminal sessions work. |
_________________
sidux Maintenance script: dist-upgrade, kernel install, general utilities: smxi
Backup script [using rdiff-backup]: rd-h2.sh
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jun 08, 2008 - 05:55 PM
|
|
Joined: Nov 28, 2006
Posts: 4303
Status: Offline
|
|
| This question however may one day get a really nice solution, like several other issues have gotten, when somebody comes up with a delightfully simple, elegant, yet effective, solution, and posts it in the smxi bug reports/feature requests thread. The simpler and more elegant, the more likely to be implemented. |
_________________
sidux Maintenance script: dist-upgrade, kernel install, general utilities: smxi
Backup script [using rdiff-backup]: rd-h2.sh
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jun 09, 2008 - 12:21 AM
|
|
Joined: Dec 01, 2007
Posts: 203
Location: Enschede NL
Status: Offline
|
|
What I understood was: the messages in smxi are long gone by the point when the information is needed. I don't upgrade that regularly anymore but so far the one that has a default advice of 'no' is kdmrc (or something like that). As a general rule I upgrade configs too unless I get a specific advice not to so I only remember the 'no' advice.
So that's easy. Now the whole point of config files is that they may not be like the original version anymore. If I'm correct, then it's always possible to do a diff before deciding to upgrade. When manually changing a file, I add a small comment with date, change and reason why and it'll show up in diff. Changes made by GUI apps perhaps don't have anything so obvious but frequently you're warned to make a backup anyway, and if it's something important I always see if a comment can be made too.
It does require a bit more discipline than I usually apply but I've learned this often pays off; it's another small price to pay to manage a complex system.
OT: I'm a scribbler too, I keep a bunch of notebooks ready next to my pc. Sometimes for useful info, often just for writing down passwords and usernames. Wouldn't want to use such an insecure plain textfile for that |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jun 09, 2008 - 11:01 PM
|
|
Joined: Dec 10, 2006
Posts: 139
Location: Cape Cod
Status: Online!
|
|
Just a thought
How about having the config file question answer info available as a getopts option (it looks like '-c' isn't taken) and have it be viewable in X. That way it could be printed out or pasted to a text file and be available easily when in init 3.
It's far from perfect, but it might help. |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Jun 10, 2008 - 12:44 AM
|
|
Joined: Nov 28, 2006
Posts: 4303
Status: Offline
|
|
| yes, something like that could work. |
_________________
sidux Maintenance script: dist-upgrade, kernel install, general utilities: smxi
Backup script [using rdiff-backup]: rd-h2.sh
|
| |
|
|
|
|
|
|
