lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 14 Jun 2008 11:35:35 +0200
From:	Alessandro Zummo <alessandro.zummo@...ertech.it>
To:	rtc-linux@...glegroups.com
Cc:	david-b@...bell.net, Ingo Molnar <mingo@...e.hu>,
	Lior Dotan <liodot@...il.com>, Adrian Bunk <bunk@...nel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	bugme-daemon@...zilla.kernel.org
Subject: Re: [rtc-linux] Re: [Bug 10866] /dev/rtc was missing until I
 disabled CONFIG_RTC_CLASS

On Fri, 13 Jun 2008 15:38:54 -0700
David Brownell <david-b@...bell.net> wrote:

> 
> They can continue working just fine with *only* the legacy RTC.
> If they stuck with defaults, no problems appear.  (Modulo the
> fact that bitrot is setting in.)
> 
> The only thing that causes the least hiccup is someone who was
> for a while using a bogus (and non-default) configuration.
> 
> Given a bogus configuration, how should it be fixed?  There
> can be several solutions, and the right answer for one system
> will always be the right one for another.  So any approach
> that doesn't expect a human to select options sometimes will
> be inherently wrong in various cases.

 I agree with david. oldconfig cannot be made to fix every possible
 manual misconfiguration that has been introduced by the user, even
 those that, by chance, just worked.

 The actual Kconfig will handle pretty well the transition from
 a good config. where good is different from working-by-chance.

 There are far too many people that just keep pressing Y
 when a new kernel option appears without even considering what would
 happen or reading the help.


-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Torino, Italy

  http://www.towertech.it

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists