Write to Eric Troan <[EMAIL PROTECTED]>. He's on vacation this week.
Caldera simply follows Red Hat's lead on this issue. Red Hat has
shown a willingness to deal with us.
Thanks
Bruce
--
Bruce Perens <[EMAIL PROTECTED]> Pixar Animation Studios
What are the appropriate contact address at Red Hat and Caldera? I'd
like to write to both companies and discuss this issue.
--- Start of forwarded message ---
Date: Sun, 17 Dec 1995 17:37:36 -0500 (EST)
From: Ian Murdock <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re:
> Isn't it just as likely that /var/log will be on a mounted filesystem?
> (In fact /var is a separate filesystem on mine.)
Ditto here ( and /var/spool is separate too). To be sane/safe, assume
that /sbin, /lib, and /etc are all that / has at boot time. Anything
else can be mounted on some mut's
Ian Jackson:
> I agree. Bruce, would it be too much to ask you to hold off making
> this change until we've got the issue settled ?
I'm waiting for Miquel van Smoorenberg, the author of sysvinit, to get
back to me regarding whether he will take over the sysvinit package. If
he leads, the users of
Bruce Perens writes ("Re: coming soon"):
> I was talking about moving initrunlvl to /etc, not /var/log .
Ah, sorry, I misunderstood you too.
Ian.
Ian Murdock writes ("Re: coming soon "):
> I also agree that compatibility between distributions is paramount, but
> I'd rather convince Caldera, Red Hat, etc. to be compatible with System V
> than change Debian to be incompatible with it. We should make talking to
Bruce Perens writes ("Re: coming soon"):
> From: Ian Jackson <[EMAIL PROTECTED]>
> >[Bruce wrote:]
> >>4. The /etc/init.d/functions file will no longer be used.
> > Please make it exist and be empty so that existing programs don't
> > break.
&
On Sat, 16 Dec 1995, Ian Jackson wrote:
> > 4. The /etc/init.d/functions file will no longer be used.
>
> Please make it exist and be empty so that existing programs don't
> break. It should contain a comment saying that programs shouldn't use
> it.
Also, don't forget to remove the ". /etc/
I agree with Ian J.
I also agree that compatibility between distributions is paramount, but
I'd rather convince Caldera, Red Hat, etc. to be compatible with System V
than change Debian to be incompatible with it. We should make talking to
them the first step in resolving this incompatibility prob
On Sat, 16 Dec 1995, Michael K. Johnson wrote:
> All the other Linux distributions are going to /etc/rc.d/* because
> that's what comes with the svinit package. It works very well; in
> practice I've found that it's one of the things that I like better
> about my Red Hat system than my Debian syst
From: Jeff Noxon <[EMAIL PROTECTED]>
> In fact, isn't /etc guaranteed to be on the root filesystem? I don't see
> how a system can boot without it. Why move initrunlevel at all? I think
> other distributions will leave it in /etc.
Debian does not currently have it in /etc . I am going to move i
I was talking about moving initrunlvl to /etc, not /var/log .
Regarding the location of the rc[0-6].d directories, slackware, redhat,
caldera, etc. all put them in /etc/rc.d/rc[0-6].d . I don't have to change
their locations, but it seems to make more sense for us to be Linux-compatible
than SysV-
> Bruce Perens writes:
> >From: Ian Jackson <[EMAIL PROTECTED]>
>
> >>>1. The "initrunlevel" file is moving to /etc from /var/log.
> >>/var/run, surely ?
> >
> >/var/run is possibly in a mounted filesystem. Init breaks if it can't
> >find this file. I've been thinking about using a named pipe so t
>>I can make symbolic links in /etc/rc.d that point back out to where
>>the directories are instead of moving the directories. I was of the
>>impression that real SysV worked the other way, but I can satisfy
>>everyone.
>
>I agree with Ian. Pleas don't do this. Adding alternative paths to
>the s
Bruce Perens writes:
>From: Ian Jackson <[EMAIL PROTECTED]>
>>>1. The "initrunlevel" file is moving to /etc from /var/log.
>>/var/run, surely ?
>
>/var/run is possibly in a mounted filesystem. Init breaks if it can't
>find this file. I've been thinking about using a named pipe so that
>it will wor
On Sat, 16 Dec 1995, Michael K. Johnson wrote:
>
> David Engel writes:
> >> >> 3. /etc/rc[0-6].d will move to /etc/rc.d/rc[0-6].d to match the
> >> >>practice on other Linux systems. Symbolic links will provide
> >> >>compatibility with the old locations.
> >> > Is
David Engel writes:
>> >> 3. /etc/rc[0-6].d will move to /etc/rc.d/rc[0-6].d to match the
>> >> practice on other Linux systems. Symbolic links will provide
>> >> compatibility with the old locations.
>> > Is this really necessary ? Real SysV's do things the way we have
>> > done.
>>
> >>3. /etc/rc[0-6].d will move to /etc/rc.d/rc[0-6].d to match the
> >> practice on other Linux systems. Symbolic links will provide
> >> compatibility with the old locations.
> > Is this really necessary ? Real SysV's do things the way we have
> > done.
>
> I can make symbolic l
From: Ian Jackson <[EMAIL PROTECTED]>
>> 1. The "initrunlevel" file is moving to /etc from /var/log.
> /var/run, surely ?
/var/run is possibly in a mounted filesystem. Init breaks if it can't
find this file. I've been thinking about using a named pipe so that
it will work with a read-only roo
Bruce Perens writes ("coming soon"):
> I am changing "init" in a few ways:
>
> 1. The "initrunlevel" file is moving to /etc from /var/log.
> Currently, init gets sick if /usr is unmounted. I may look
> at an alternative to using this file, so that it can better
> t
20 matches
Mail list logo