mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] fstab: don't explicitly mount debugfs
Date: Fri, 11 Jan 2019 14:51:21 +0100	[thread overview]
Message-ID: <20190111135121.feyfycoyhvclriix@pengutronix.de> (raw)
In-Reply-To: <20190108214102.24616-1-u.kleine-koenig@pengutronix.de>

On Tue, Jan 08, 2019 at 10:41:02PM +0100, Uwe Kleine-König wrote:
> If the kernel in use doesn't support it having an explicit entry results
> in a failure.

I don't mind either way, but this does not fail at boot, right? It has
'noauto' in the mount options.

Michael

> On systems with systemd it is mounted anyways by
> /lib/systemd/system/sys-kernel-debug.mount iff DEBUG_FS is enabled in
> the kernel.
> 
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
>  projectroot/etc/fstab | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/projectroot/etc/fstab b/projectroot/etc/fstab
> index 269e35f66859..88099aacc17e 100644
> --- a/projectroot/etc/fstab
> +++ b/projectroot/etc/fstab
> @@ -6,7 +6,6 @@
>  proc	/proc			proc	nosuid,nodev,noexec			0 0
>  devpts	/dev/pts		devpts	nosuid,noexec,mode=620,gid=112		0 0
>  sysfs	/sys			sysfs	nosuid,nodev,noexec			0 0
> -debugfs	/sys/kernel/debug	debugfs	noauto					0 0
>  
>  # ramdisks
>  tmpfs	/tmp			tmpfs	nosuid,nodev,mode=1777,size=20%		0 0
> -- 
> 2.19.1
> 
> 
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2019-01-11 13:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-08 21:41 Uwe Kleine-König
2019-01-11 13:51 ` Michael Olbrich [this message]

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=20190111135121.feyfycoyhvclriix@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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