Hello Thomas,
Thomas Hood [EMAIL PROTECTED] wrote:
http://panopticon.csustan.edu/thood/readonly-root.html
I won't summarize the whole discussion here. I will just say that
I see good reasons for adopting /run as a standard location for the
storage of state information that needs to be
Joerg Sommer wrote:
But I've a question on it: How can I use it? How can I set up /run before
init runs the init script that is responsible for it?
I'd assume you'd make the mounting of /run be the first script init
runs. So, it'd be /etc/rcS.d/S00mountrun (under SysV-style init, of
course).
The issue of where to put state information that needs to be stored
prior to the initialization of networking (or independently of
networking) has been discussed before. The longest discussion I can
recall was in the spring of 2003 and had the subject headings:
* ifupdown writes to /etc... a
On Thu, Sep 01, 2005 at 09:11:31PM +, Joerg Sommer wrote:
It seems there is a misunderstanding. bootchart is a shell script that is
started as init (kernel prompt init=/sbin/bootchart), which then forks
the real init to start the real boot process. While init does its work
bootchart
* Steve Langasek [Thu, 01 Sep 2005 23:03:21 -0700]:
Hrm. If this information is all just being copied to the real
filesystem at the end of the boot process anyway, why does it need to
write it out to disk instead of just storing it in memory, anyway?
He claimed it's not possible:
On Fri, Sep 02, 2005 at 08:53:19AM +0200, Adeodato Simó wrote:
* Steve Langasek [Thu, 01 Sep 2005 23:03:21 -0700]:
Hrm. If this information is all just being copied to the real
filesystem at the end of the boot process anyway, why does it need to
write it out to disk instead of just
In article [EMAIL PROTECTED],
Adeodato Simó [EMAIL PROTECTED] wrote:
* Steve Langasek [Thu, 01 Sep 2005 23:03:21 -0700]:
Hrm. If this information is all just being copied to the real
filesystem at the end of the boot process anyway, why does it need to
write it out to disk instead of just
Hello Steve,
Steve Langasek [EMAIL PROTECTED] wrote:
On Thu, Sep 01, 2005 at 09:11:31PM +, Joerg Sommer wrote:
It seems there is a misunderstanding. bootchart is a shell script that is
started as init (kernel prompt init=/sbin/bootchart), which then forks
the real init to start the real
Hello Adeodato,
Adeodato Simó [EMAIL PROTECTED] wrote:
* Joerg Sommer [Mon, 29 Aug 2005 12:51:16 +]:
Do it and get enough things to use it. Then there is no stopping you.
Well, I add /run/ to the directories of my package and mount a tmpfs
there on startup. But I leave it mounted after
On Mon, Aug 29, 2005 at 09:25:22PM +0100, Roger Leigh wrote:
sean finney [EMAIL PROTECTED] writes:
On Sun, Aug 28, 2005 at 09:26:16PM +0100, Roger Leigh wrote:
sean finney [EMAIL PROTECTED] writes:
Some packages chose to place random junk in there (e.g. resolvconf).
This is wrong. This
* Joerg Sommer [Mon, 29 Aug 2005 12:51:16 +]:
Do it and get enough things to use it. Then there is no stopping you.
Well, I add /run/ to the directories of my package and mount a tmpfs
there on startup. But I leave it mounted after exit, because I don't know
if someone else use it.
On Sun, Aug 28, 2005 at 09:26:16PM +0100, Roger Leigh wrote:
sean finney [EMAIL PROTECTED] writes:
On Sat, Aug 27, 2005 at 12:53:09PM -0700, Steve Langasek wrote:
/run/bootchart, but there seems to be some resistance to actually trying to
standardize on /run :)
what about /dev/shm?
On Sat, Aug 27, 2005 at 06:32:26PM -0400, sean finney wrote:
On Sat, Aug 27, 2005 at 12:53:09PM -0700, Steve Langasek wrote:
/run/bootchart, but there seems to be some resistance to actually trying to
standardize on /run :)
what about /dev/shm?
Aside from the other objections voiced that
[Steve Langasek]
[use of /dev/shm] inappropriately ties the required feature (early
availability of read-write space for data that doesn't persist across
reboots) to a particular implementation, instead of leaving the admin
free to structure the mounts in a way that's most appropriate for the
Hello Goswin,
Goswin von Brederlow [EMAIL PROTECTED] wrote:
Joerg Sommer [EMAIL PROTECTED] writes:
Goswin von Brederlow [EMAIL PROTECTED] wrote:
Petter Reinholdtsen [EMAIL PROTECTED] writes:
What about /run/? Can a new package simply use/create /run? I would add
/run to the directories of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
sean finney [EMAIL PROTECTED] writes:
On Sun, Aug 28, 2005 at 09:26:16PM +0100, Roger Leigh wrote:
sean finney [EMAIL PROTECTED] writes:
Some packages chose to place random junk in there (e.g. resolvconf).
This is wrong. This location is for
On 08/29/05 03:32:55AM -0500, Peter Samuelson wrote:
[Steve Langasek]
[use of /dev/shm] inappropriately ties the required feature (early
availability of read-write space for data that doesn't persist across
reboots) to a particular implementation, instead of leaving the admin
free to
Hi Roger,
Roger Leigh [EMAIL PROTECTED] wrote:
In this case, it looks like we should standardise on something like
/run. Has this been brought up with the FHS/LSB folks? This sounds
like something other distributions will also need to tackle, so if it
gets standardised, so much the better.
Joerg Sommer [EMAIL PROTECTED] writes:
sean finney [EMAIL PROTECTED] wrote:
On Sat, Aug 27, 2005 at 12:53:09PM -0700, Steve Langasek wrote:
/run/bootchart, but there seems to be some resistance to actually trying to
standardize on /run :)
what about /dev/shm?
sean
Is it available
[Goswin von Brederlow]
Nothing is available before init is started, init is always the
first thing to start, even on initrd or initramfs (some archs call
init linuxrc though).
You suspect you miss the point. bootchartd is a init _replacement_.
We use it by passing init=/sbin/bootchartd to the
Petter Reinholdtsen [EMAIL PROTECTED] writes:
[Goswin von Brederlow]
Nothing is available before init is started, init is always the
first thing to start, even on initrd or initramfs (some archs call
init linuxrc though).
You suspect you miss the point. bootchartd is a init _replacement_.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
sean finney [EMAIL PROTECTED] writes:
On Sat, Aug 27, 2005 at 12:53:09PM -0700, Steve Langasek wrote:
/run/bootchart, but there seems to be some resistance to actually trying to
standardize on /run :)
what about /dev/shm?
/dev/shm is an
Hello Goswin,
Goswin von Brederlow [EMAIL PROTECTED] wrote:
Petter Reinholdtsen [EMAIL PROTECTED] writes:
[Goswin von Brederlow]
Nothing is available before init is started, init is always the
first thing to start, even on initrd or initramfs (some archs call
init linuxrc though).
You
Joerg Sommer [EMAIL PROTECTED] writes:
Hello Goswin,
Goswin von Brederlow [EMAIL PROTECTED] wrote:
Petter Reinholdtsen [EMAIL PROTECTED] writes:
[Goswin von Brederlow]
Nothing is available before init is started, init is always the
first thing to start, even on initrd or initramfs (some
Hi,
I will start maintaining the packages bootchart (#321784) and have a
question. Bootchart collects data while booting. It is started before
init, which means there is no place in the file tree to write to.
The upstream package creates a directory in /mnt/ where it mounts a
tmpfs. But using a
On Sat, Aug 27, 2005 at 06:31:20PM +, Joerg Sommer wrote:
I will start maintaining the packages bootchart (#321784) and have a
question. Bootchart collects data while booting. It is started before
init, which means there is no place in the file tree to write to.
The upstream package
I will start maintaining the packages bootchart (#321784) and have a
question. Bootchart collects data while booting. It is started before
init, which means there is no place in the file tree to write to.
can't you hack the package to use RAM until the init process is
complete, when it can
On Sat, Aug 27, 2005 at 12:53:09PM -0700, Steve Langasek wrote:
/run/bootchart, but there seems to be some resistance to actually trying to
standardize on /run :)
what about /dev/shm?
sean
--
signature.asc
Description: Digital signature
martin f krafft [EMAIL PROTECTED] wrote:
I will start maintaining the packages bootchart (#321784) and have a
question. Bootchart collects data while booting. It is started before
init, which means there is no place in the file tree to write to.
can't you hack the package to use RAM until
sean finney [EMAIL PROTECTED] wrote:
On Sat, Aug 27, 2005 at 12:53:09PM -0700, Steve Langasek wrote:
/run/bootchart, but there seems to be some resistance to actually trying to
standardize on /run :)
what about /dev/shm?
sean
Is it available _before_ init is started?
Jörg.
--
Steve Langasek [EMAIL PROTECTED] wrote:
On Sat, Aug 27, 2005 at 06:31:20PM +, Joerg Sommer wrote:
I will start maintaining the packages bootchart (#321784) and have a
question. Bootchart collects data while booting. It is started before
init, which means there is no place in the file tree
31 matches
Mail list logo
