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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Wed, 15 Aug 2007 11:19:33 -0400
From:	Dave Jones <davej@...hat.com>
To:	Dave Young <hidave.darkstar@...il.com>
Cc:	Randy Dunlap <rdunlap@...otime.net>,
	Dave Jones <davej@...emonkey.org.uk>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: two questions about the boot_delay

On Wed, Aug 15, 2007 at 03:45:08PM +0800, Dave Young wrote:
 > >On 8/12/07, Randy Dunlap <rdunlap@...otime.net> wrote:
 > > On Wed, 8 Aug 2007 07:39:33 +0000 Dave Young wrote:
 > >
 > > > Hi,
 > > > I have tried the "slow down printk" , and I have two questions.
 > > >
 > > > 1. why it depends the DEBUG_KERNEL? Sometimes we only need boot_delay
 > > > to see the printk infomations.  How about set it as a standalone
 > > > config option?
 > >
 > > Is depending on DEBUG_KERNEL a problem?  If so, why?
 > 
 > IMHO, the DEBUG_KERNEL will build a big kernel and the building time
 > is long, so if the we only want to look at the boot messages at panic
 > point, the DEBUG_KERNEL is not needed.
 
Only if you enable other debug options too. (Yes, some default to on,
perhaps they shouldn't).

DEBUG_KERNEL itself shouldn't make any difference to the generated
code at all.

	Dave

-- 
http://www.codemonkey.org.uk
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ