Coders Edge

dual card

It's fun to finally have a system that will render quicker. I haven't leveraged it yet to produce animation. I'm still too much of a newbie to Blender, even after 18 months of deciding that I would 'get into it'.

I configured another new system, this time totally from scratch. The grub configuration has changed yet again. One uses the grub.d directory in /etc, in the usual way as all of the other configuration directories of that type with a numbered file system of loading configuration options. Prudent backup requires the backup of those, too. But thta would require a sudo user privledge (if you don't know . . . then you aren't a sys-admin, so you can gloss over this part). These configuration options contain important information. Especially in the case of older processors that need a specifically configured kernel to overcome various aspects of hardware limitation. (said in a verbose way). Basic point: special setups of various kernel aspects require special configurations, and often times, unique options and features enabled. All of the conf directories, if they are to be backed up, also need to be tagged as for a specific configuration. In other words some of it is very system specific and possibly damaging to other configureations, other actual systems, if used there. Other things are for any system and, in essence, ought not be included in a system area but instead in some kind of alternative storage, or just left as a link to a URL elsewhere.

And so, shoudl such options be saved? IN the case of grub one can gather information from the linux command line, and that information now resides in a diretory. If one wants to back it up, then one ought to. But in the case of most systems, if the system fails . . . that's just the way it goes. A new system also will have unique aspects. Cataloging these is often useful. MOre often than not a system is abandoned and not repaired, and so storing the idiosyncratic aspects will often give no benefit.

The verbosity of a journaling log system means that often it isn't prudent to store everything, or to even have all of the logging functionality enabled. It just eats storage and slows the system.

But when issues arise a boot that has copious logging will allow one to investigate the causes of failures. Linux has exceptional stability. And it always squacks if you let it: copiusly. Investigate the logs and you shall find much that will give you insight into how to improve your configuration.

May 4, 2017

Please visit DEMOS