Deprecated options suggestion
As rc.conf is a major wiki article and I don't want to waste everyone's time making changes that are not desirable, I'd like to open a discussion about listing deprecated options. Mentioning UDEV_TIMEOUT on forums initiated a developer response, stating that the option is no longer usable. There was no reference on rc.conf wiki anymore, and such information can be easily missed while updating. This brought me to an idea that deprecated options could be listed on wiki, to make people aware that their functionality has been dropped, and perhaps linking to a way to replace it if one is known. Provided that such information would be properly labeled not to cause any confusion, I can't see any real downsides to it, though I'm not entirely sure that listing obsolete information in this way is desirable. Please share your thoughts. - Meph 20:40, 23 January 2012 (EST)
- My opinion: only if necessary (in situations like yours). --AlexanderR 21:58, 23 January 2012 (EST)
- I can't see any real downsides either, I'd just create a separate section for deprecated options, and make sure to write the last version of initscripts where the option was present, so that in the future it will be possible to remove the options which have been deprecated for too long. Also a brief description of the purpose of the section may prevent somebody from deleting it in case they think it's useless. -- Kynikos 06:43, 24 January 2012 (EST)
HARDWARECLOCK random string
Four options are given for HARDWARECLOCK. UTC, localtime, an empty string, and any other value. From experience, any other value behaves the same as an empty string. hwclock's source code seems to confirm this.--Stijn 18:04, 17 April 2012 (EDT)
if (utc) ret = TRUE; /* --utc explicitly given on command line */ else if (local_opt) ret = FALSE; /* --localtime explicitly given */ else /* get info from adjtime file - default is UTC */ ret = (adjtime.local_utc != LOCAL);
I can't find any documentation on this file. All the other "new" configuration files are conveniently documented in man pages, but the best I can get on this file, is man page for a function. Where did I not look? Is this file a simple new-line/EOF ended file, like hostname, or does it go VARIABLE=value like other files? --Freso (talk) 08:15, 18 August 2012 (UTC)
What is the structure of this file? Reading the rc.conf section leaves it unclear if the network settings should stay there a or move to network. Also the network_persist should it go in network or in rc.conf.
I suggest to display templates for all the new configuration files to assist configuration. This files a pretty key. Not having a network is not fun.