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]
Message-Id: <200708301836.48707.rob@landley.net>
Date:	Thu, 30 Aug 2007 18:36:48 -0500
From:	Rob Landley <rob@...dley.net>
To:	"Robert P. J. Day" <rpjday@...dspring.com>
Cc:	Randy Dunlap <randy.dunlap@...cle.com>,
	lkml <linux-kernel@...r.kernel.org>,
	akpm <akpm@...ux-foundation.org>, bos@...pentine.com,
	werner@...esberger.net, hpa@...or.com
Subject: Re: [PATCH] docs: ramdisk/initrd/initramfs corrections

On Thursday 30 August 2007 1:28:17 pm Robert P. J. Day wrote:
> On Thu, 30 Aug 2007, Randy Dunlap wrote:
>
> ...
>
> > The old "ramdisk=<ram_size>" has been changed to
> > "ramdisk_size=<ram_size>" to make it clearer.  The original
> > "ramdisk=<ram_size>" has been kept around for compatibility reasons,
> > but it may be removed in the future.
>
> ...
>
> i just the other day submitted a patch to remove that backward
> compatibility, and the m68k portion of it has already been acked by
> geert uytterhoeven.

Could you mention it in feature-removal-schedule.txt?  (People check that for 
warning of upcoming changes that impact existing code.  They may not notice 
something elsewhere after they've got it working...)

(Also, sorting feature-removal-schedule.txt by date would be really nice.  The 
sucker's gotten huge...)

And while I'm looking at this, is there some other place that entries in this 
file go once they _have_ been removed, so people can see "oh yeah, that went 
away in 2.6.23) when they try to install 2.6.25?  If there is, I missed it.  
Maybe http://lwn.net/Articles/2.6-kernel-api/ is good enough, but this seems 
easy to do in Documentation...

Thanks,

Rob
-- 
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.
-
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