From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from ar.aichi-u.ac.jp ([202.250.160.40]) by ur; Sat Sep 12 00:19:25 EDT 2015 Received: from [192.168.0.249] ([123.1.1.113]) by ar; Sat Sep 12 13:19:12 JST 2015 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: [9front] cwfs dump From: arisawa In-Reply-To: <1843000694f353e7801712e0f4348e81@felloff.net> Date: Sat, 12 Sep 2015 13:19:12 +0900 Content-Transfer-Encoding: quoted-printable Message-Id: <5987D4F9-71FF-4B26-851E-B35428C6AF73@ar.aichi-u.ac.jp> List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: lossless polling control References: <1843000694f353e7801712e0f4348e81@felloff.net> To: 9front@9front.org X-Mailer: Apple Mail (2.2104) Thanks > 2015/09/12 11:09=E3=80=81cinap_lenrek@felloff.net =E3=81=AE=E3=83=A1=E3=83= =BC=E3=83=AB=EF=BC=9A >=20 > correct. cwfs uses the systems time, which is initialized to from > rtc by /boot/boot (to get at least the date right), but is later > corrected by aux/timesync once the system is fully booted up. > the problem was that cwfs didnt use the local timezone because > /env/timezone is missing on boot. >=20 > i just pushed a change that makes cwfs read in /adm/timezone/local > when /env/timezone is missing so dump times will be in local time > now. >=20 > this was a classical bootstrap problem. normally, /env/timezone is > initialized by /bin/init, but cwfs is not run after init because > because init is on the very filesystem cwfs serves. >=20 > -- > cinap