From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: Roman Mamedov <rm@romanrm.net>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Is there a "nossd" option ?
Date: Sun, 21 Jun 2015 20:11:25 +0200 [thread overview]
Message-ID: <4527646.9Fsd4pK4E8@zafu> (raw)
In-Reply-To: <20150621223121.617b8894@natsu>
Le dimanche 21 juin 2015 22:31:21 Roman Mamedov a écrit :
>
> Yes the "nossd" option (written literally like that) does in fact exist.
> It would have taken you less time to try if it works, than to write this
> long-winded message. :)
Possibly. Unless trying a non-existing mount option causes the mount to fail,
thus causing the system boot to fail, thus needing me to boot from a live
rescue CD... that would take much longer than writing an half-page
email ;-)
Best regards.
--
Swâmi Petaramesh <swami@petaramesh.org> http://petaramesh.org PGP 9076E32E
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
next prev parent reply other threads:[~2015-06-21 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-21 17:13 Is there a "nossd" option ? Swâmi Petaramesh
2015-06-21 17:31 ` Roman Mamedov
2015-06-21 18:11 ` Swâmi Petaramesh [this message]
2015-06-21 18:18 ` Eric Sandeen
2015-06-21 18:22 ` Roman Mamedov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4527646.9Fsd4pK4E8@zafu \
--to=swami@petaramesh.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=rm@romanrm.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox