Re: Bits from the Release Team - Kicking off Wheezy
- To: email@example.com
- Subject: Re: Bits from the Release Team - Kicking off Wheezy
- From: Goswin von Brederlow <firstname.lastname@example.org>
- Date: Sun, 03 Apr 2011 14:12:22 +0200
- Message-id: <[🔎] email@example.com>
- In-reply-to: <20110330234806.GA22088@khazad-dum.debian.net> (Henrique de Moraes Holschuh's message of "Wed, 30 Mar 2011 20:48:06 -0300")
- References: <20110329095102.GX37987@feta.halon.org.uk> <20110330190917.GG20813@codelibre.net> <20110330194521.GK12748@l04.local> <firstname.lastname@example.org> <20110330234806.GA22088@khazad-dum.debian.net>
Henrique de Moraes Holschuh <email@example.com> writes:
> On Thu, 31 Mar 2011, Goswin von Brederlow wrote:
>> > /etc/adjtime
> This needs to survive reboots, and it is also needed early in the boot.
> It is used to correct the RTC syndrome.
> I am at a loss about how it could be made compatible with RO /.
So my clock is sightly wrong during boot until the ntpd/chrony/ntpdate
fixes it. It doesn't give errors so i can live with that.
One could run a while with a read-write / to get an initial /etc/adjtime
for the RTC drift. After that the RTC hopefully doesn't change. So while
I agree that this can't completly be fixed I think it can be ignored.
>> > /etc/hosts.deny (written by denyhosts, hence that one is a bit hard to fix)
>> Don't have that. Fix denyhosts to link that to /var/ (or /run when we
>> have it).
> Has to be available before any tcp-wrapped network service is started.
I guess you could just have a /etc/defaults/hosts.deny that you copy to
/run and link /etc/hosts.deny -> /run/hosts.deny before starting
tcp-wrapped network services.