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
| ||
|
Date: Tue, 16 Oct 2007 10:17:09 +0200 (CEST) From: Jan Engelhardt <jengelh@...putergmbh.de> To: Nick Piggin <nickpiggin@...oo.com.au> cc: "Eric W. Biederman" <ebiederm@...ssion.com>, Andrew Morton <akpm@...ux-foundation.org>, Christian Borntraeger <borntraeger@...ibm.com>, linux-mm@...ck.org, linux-kernel@...r.kernel.org, Martin Schwidefsky <schwidefsky@...ibm.com>, Theodore Ts'o <tytso@....edu> Subject: Re: [patch][rfc] rewrite ramdisk On Oct 16 2007 18:07, Nick Piggin wrote: >Changed. But it will hopefully just completely replace rd.c, >so I will probably just rename it to rd.c at some point (and >change .config options to stay compatible). Unless someone >sees a problem with that? I do not see a problem with keeping brd either. >> It also does not seem needed, since it did not exist before. >> It should go, you can set the variable with brd.rd_nr=XXX (same >> goes for ramdisk_size). > >But only if it's a module? Attributes always work. Try vt.default_red=0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 and you will see. - 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