Difference between revisions of "Talk:Initscripts/rc.conf"

From ArchWiki
Jump to: navigation, search
(HARDWARECLOCK random string: new section)
m (Thestinger moved page Talk:Rc.conf to Talk:Initscripts/rc.conf: turn into a sub-page for clarity)
(9 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== <s>Blacklisting deprecated?</s> ==
 
 
I thought that just the MOD_BLACKLIST array was deprecated, not the bang preponing into MODULES array. How can someone avoid module loading now? Through some udev rule? --[[User:4javier|4javier]] 12:08, 1 June 2011 (EDT)
 
:Ok, I've seen alsa page edit...then, conf files into /etc/modprobe.d are the preferred blacklisting method? --[[User:4javier|4javier]] 12:12, 1 June 2011 (EDT)
 
::initscripts 2011.06.1-1 (in [testing] at the moment) has dropped support for blacklisting in rc.conf's MODULES array, since upstream provides a way to do it, and using that method lets the devs get rid of load-modules.sh and use a more vanilla (and faster) udev package. [[User:Thestinger|thestinger]] 12:17, 1 June 2011 (EDT)
 
:::Perfect, thanks. I'll fix my configuration in advance. :) --[[User:4javier|4javier]] 12:20, 1 June 2011 (EDT)
 
 
 
 
== Deprecated options suggestion ==
 
== Deprecated options suggestion ==
  
Line 18: Line 10:
  
 
Four options are given for HARDWARECLOCK. UTC, localtime, an empty string, and any other value.
 
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.
+
From experience, any other value behaves the same as an empty string. hwclock's source code seems to confirm this.--[[User:Stijn|Stijn]] 18:04, 17 April 2012 (EDT)
  
 
{{hc
 
{{hc
Line 31: Line 23:
 
ret = (adjtime.local_utc != LOCAL);
 
ret = (adjtime.local_utc != LOCAL);
 
</nowiki>}}
 
</nowiki>}}
 +
 +
== /etc/adjtime ==
 +
 +
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 [http://linux.die.net/man/3/adjtime|a 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? --[[User:Freso|Freso]] ([[User talk:Freso|talk]]) 08:15, 18 August 2012 (UTC)
 +
 +
Documented in hwclock(8). A better option is to use "timedatectl". Will update relevant pages once that (as part of systemd-195) hits [core]. [[User:Tomegun|Tomegun]] ([[User talk:Tomegun|talk]]) 11:21, 25 October 2012 (UTC)

Revision as of 05:51, 26 October 2012

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)

hwclock.c 230-236
	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);

/etc/adjtime

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)

Documented in hwclock(8). A better option is to use "timedatectl". Will update relevant pages once that (as part of systemd-195) hits [core]. Tomegun (talk) 11:21, 25 October 2012 (UTC)