From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] owfs: add sysv init scripts
Date: Fri, 25 Mar 2016 23:20:56 +0100 [thread overview]
Message-ID: <87fuvedws7.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <56F5B617.4080605@mind.be> (Arnout Vandecappelle's message of "Fri, 25 Mar 2016 23:05:11 +0100")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Hi,
>> I've never used owfs, but /dev/1wire sounds like an odd mount point to
>> me. I would have expected something under /mnt?
> /dev/1wire is what is used by the bundled debian init scripts. I
> didn't use the bundled init scripts because they are slightly more
> complicated than what we need and I wanted to add some features, like
> loading the fuse module.
> /mnt is annoying, because some scripts will (temporarily) mount
> something on /mnt (without subdir), thus hiding anything else mounted
> there. For example, many of our board readme's say to mount
> /dev/mmcblk0p1 /mnt as part of creating the SD card.
Ok, /dev/1wire is ok with me.
>> Googling around, I see the manual page suggests /mnt/1wire:
>>
>> http://owfs.org/index.php?page=owfs
>>
>> You will need to create the mount point during build time though, as
>> /mnt might not be writable.
> Oh yeah, another reason to put it on /dev or /sys.
Do keep in mind that we still support BR2_ROOTFS_DEVICE_CREATION_STATIC,
so you need to create it at build time AND mkdir -p it in the init
script.
>> The point of sourcing /etc/default/owfs is so the user can override the
>> defaults. How about sticking the MOUNTPOINT / SERVER into a OWFS_ARGS or
>> at least prefixing the variables with OWFS?
> Yes, that's a good idea. I'm on it.
Great, thanks!
--
Venlig hilsen,
Peter Korsgaard
prev parent reply other threads:[~2016-03-25 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 20:00 [Buildroot] [PATCH] owfs: add sysv init scripts Arnout Vandecappelle
2016-03-25 20:41 ` Peter Korsgaard
2016-03-25 22:05 ` Arnout Vandecappelle
2016-03-25 22:20 ` Peter Korsgaard [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=87fuvedws7.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.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