From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: where is tftp mounting documented in the source code?
Date: Tue, 20 Nov 2012 07:03:58 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.02.1211200702001.26129@oneiric> (raw)
In-Reply-To: <20121120080831.GE10369@pengutronix.de>
On Tue, 20 Nov 2012, Sascha Hauer wrote:
> On Mon, Nov 19, 2012 at 09:48:41AM -0500, Robert P. J. Day wrote:
> >
> > perusing the wiki and ran across page on TFTP support:
> > http://wiki.barebox.org/doku.php?id=filesystems:tftp which suggests:
> >
> > mount 192.168.1.1 tftp /mnt/tftp
>
> This was the original mount behaviour. This was recently changed to
> mount -t fstype <ip> /dir, mainly to allow making the fstype option
> optional for autodetecting the type. The wiki page is out of date
> here. As a sidenote I brought back the old behaviour as a
> compatibility option to not break old environments.
so ... the wiki page should be updated to show both the old and new
behaviour? and the "help mount" content should be extended as well?
what's the proper fix here?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-11-20 12:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 14:48 Robert P. J. Day
2012-11-20 8:08 ` Sascha Hauer
2012-11-20 12:03 ` Robert P. J. Day [this message]
2012-11-21 9:11 ` Sascha Hauer
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=alpine.DEB.2.02.1211200702001.26129@oneiric \
--to=rpjday@crashcourse.ca \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@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