From owner-freebsd-fs@freebsd.org Thu Jun 4 21:20:21 2020 Return-Path: Delivered-To: freebsd-fs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 16728332A02 for ; Thu, 4 Jun 2020 21:20:21 +0000 (UTC) (envelope-from nzmjx@protonmail.com) Received: from mail2.protonmail.ch (mail2.protonmail.ch [185.70.40.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49dJb76pDnz3yhn for ; Thu, 4 Jun 2020 21:20:19 +0000 (UTC) (envelope-from nzmjx@protonmail.com) Date: Thu, 04 Jun 2020 21:20:11 +0000 To: freebsd-fs@freebsd.org From: Nazim Can Bedir Reply-To: Nazim Can Bedir Subject: Re: newfs(1) on a file Message-ID: <1e6f811b-768b-0382-ff7e-54f0128cb876@protonmail.com> In-Reply-To: References: <1d05302e-db7f-2538-16ee-dcd73c229e37@national.shitposting.agency> <8e221643-965c-3cbb-a043-4eed786c01e3@protonmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-0.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HK_RANDOM_REPLYTO shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Rspamd-Queue-Id: 49dJb76pDnz3yhn X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.24 / 15.00]; HAS_REPLYTO(0.00)[nzmjx@protonmail.com]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[protonmail.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[protonmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[protonmail.com]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.89)[-0.890]; RWL_MAILSPIKE_POSSIBLE(0.00)[185.70.40.22:from]; NEURAL_HAM_MEDIUM(-0.09)[-0.091]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; DKIM_TRACE(0.00)[protonmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[protonmail.com,quarantine]; NEURAL_HAM_SHORT(-0.15)[-0.154]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[protonmail.com]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[185.70.40.22:from] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2020 21:20:21 -0000 Linux is able to perform `swapon ./file`, FreeBSD isn't. Then, go fuck and use Linux. No body gives a shit about you and your=20 fucking preferred system. And, stay with Linux: asshole! Again, I don't like this way of thinking. First, it goes again the Unix phi= losophy. Second, there is a clear separation between (a) creating, attempti= ng to repair or debugging an instance of a filesystem, and (b) mounting a f= ilesystem, thus connecting it to the kernel's filesystem-system -- a highly= flammable area --, which practically assumes that the instance is well-for= matted, and demands exclusive write access. Then, your problem is you are trying to live in a world where you don't=20 understand. It doesn't work in real life, and it doesn't work in Unix=20 either. So, go fuck yourself. Did I say "Go fuck yourself, and never come back!"? Sorry, I am not=20 smart enough. If my country there is a saying: "If you know better, then prove it. At=20 least, we can use the better one." Otherwise, shut the fuck up and find=20 another list to shit-post! In this list, there is only one dick who can=20 shit-post and guess who he is? So, seriously my friend, FUCK OFF! Regards, Nazim Can. On 05/06/2020 00:14, goatshit54108@national.shitposting.agency wrote: > On 6/4/20 5:04 PM, Nazim Can Bedir via freebsd-fs wrote: >> in order to include efficient and proper caching of disk >> blocks into the equation, damn filesystem backing stores need to be >> exist as devices. > I find that hard to believe, at least with that exact wording. An alterna= tive "Sorry, but all current FreeBSD-kernel filesystem-code is designed onl= y with underlying block devices in mind, so some work is needed to handle o= ther cases." sounds acceptable. > > The caching strategy mainly depends on the filesystem type, its implement= ation, and the settings. For some "filesystems", such as swap spaces, cachi= ng is specifically to be avoided. > > Linux is able to perform `swapon ./file`, FreeBSD isn't. > >> if mount command couldn't mount a GAY filesystem from the file >> as-is, then newfs(8) command shouldn't allow to create filesystem on >> file as-is (otherwise, idiot FreeBSD users like me could think that >> "aah, if newfs initialises filesystem on file without md, then it must >> be able to mount without md). > But newfs *is* able to create a filesystem on a regular file. > >> I really don't understand what is the damn problem here? Filesystem >> operations are performed on special files (a.k.a disks); and md kernel >> driver does exist for that purpose. > Again, I don't like this way of thinking. First, it goes again the Unix p= hilosophy. Second, there is a clear separation between (a) creating, attemp= ting to repair or debugging an instance of a filesystem, and (b) mounting a= filesystem, thus connecting it to the kernel's filesystem-system -- a high= ly flammable area --, which practically assumes that the instance is well-f= ormatted, and demands exclusive write access. > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"