Date: Thu, 04 Jun 2020 18:56:17 +0000 From: Nazim Can Bedir <nzmjx@protonmail.com> To: freebsd-fs@freebsd.org Subject: Re: newfs(1) on a file Message-ID: <475e7bb7-399f-4c32-ae67-b31a62e70455@protonmail.com> In-Reply-To: <CAGBxaXmhBKOgB1iprR909KxVtMQXGOpVFeFcHz5OtC9LHgCtJg@mail.gmail.com> References: <1d05302e-db7f-2538-16ee-dcd73c229e37@national.shitposting.agency> <CAGBxaXmhBKOgB1iprR909KxVtMQXGOpVFeFcHz5OtC9LHgCtJg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
No my friend, he is not trolling but shit-posting. Please let pay attention to details, because devil lies in details. On 04/06/2020 21:51, Aryeh Friedman wrote: > Top posting since the comment has very little to do with the actual conte= nt > of the message. I am amazed people call me a troll but someone who is > purposely being one is not called out?!?!!? How many of the posting > guidelines has this guy broken already? > > On Thu, Jun 4, 2020 at 12:49 PM <goatshit54108@national.shitposting.agenc= y> > wrote: > >> Running newfs(1) on a regular file bumps into some GAY issues: >> >> $ dd status=3Dnone if=3D/dev/zero bs=3D1m count=3D4 of=3Dshit >> $ newfs ./shit >> newfs: ./shit: not a character-special device: No error: 0 >> newfs: no valid label found >> >> The message is not clear, but it happens to be a cry for a BSD label. OK= , >> first creating a BSD label does allow newfs to succeed: >> $ bsdlabel -wf ./shit >> $ newfs ./shit >> newfs: ./shit: not a character-special device: No error: 0 >> ... (creation OK) >> >> The bump is inside getdisklabel(). Patching out the one and only call to >> getdisklabel() seems to avoid the issue without negative consequences: >> ... >> lp =3D NULL; //lp =3D getdisklabel(); // GAY >> ... >> >> $ dd status=3Dnone if=3D/dev/zero bs=3D1m count=3D4 of=3Dshit >> $ non-gay_newfs ./shit >> newfs: ./shit: not a character-special device: No error: 0 >> preposterous size 0 >> $ non-gay_newfs -s $(((4 << 20) / 512)) ./shit >> newfs: ./shit: not a character-special device: No error: 0 >> ... (creation OK) >> >> The inconvenient alternative, to get newfs to format the file though a >> memory disk, appears to create an identical file: >> $ dd status=3Dnone if=3D/dev/zero bs=3D1m count=3D4 of=3Dshit >> $ su root >> ... (GAY) ... >> # mdconfig -a -t vnode -f ./shit -u 9 >> # newfs /dev/md9 >> ... (creation OK) ... >> >> Identical, that is, if we use `newfs -R` and discount a couple of >> reproducibility bugs/issues (< >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246983>, < >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246985>). >> >> Also, at a glance, using the BSD label method yields nothing other than = a >> UFS filesystem along with a BSD label. >> >> So this code appears to be old garbage. >> >> Furthermore, the "not a character-special device" warning is just GAY >> without any benefit. >> >> Or?... >> _______________________________________________ >> 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" >> > > -- > Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org > _______________________________________________ > 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?475e7bb7-399f-4c32-ae67-b31a62e70455>