Date: Tue, 05 Aug 2014 09:03:10 -0400 From: "John D. Hendrickson and Sara Darnell" <johnandsara2@cox.net> Cc: freebsd-bugs@FreeBSD.org Subject: Re: [Bug 133286] dd can fill system memory Message-ID: <53E0D60E.4030206@cox.net> In-Reply-To: <arf11o02G2X408g01rf2io> References: <bug-133286-8@https.bugs.freebsd.org/bugzilla/> <arf11o02G2X408g01rf2io>
next in thread | previous in thread | raw e-mail | index | archive | help
bugzilla-noreply@freebsd.org wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=133286 > > yaneurabeya@gmail.com changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |yaneurabeya@gmail.com > > --- Comment #5 from yaneurabeya@gmail.com --- > (Just a "drive-by" comment) > It might be a good idea to do add iflags/oflags for Linux compatibility; they > have an iflags=direct/oflags=direct option, as well as other interesting > options for tweaking O_APPEND, O_NONBLOCK, and other O_* flags: > https://www.gnu.org/software/coreutils/manual/html_node/dd-invocation.html > so will break software and scripts (or printed books) using dd(1) ? if such a binary is on a rescue disk that may float around, what will the hangups be of not being able to use dd(1) due to versional tweeks ?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53E0D60E.4030206>