From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] actual system time and timezone info-bar to ipfire theme
Date: Wed, 09 Sep 2015 15:27:19 +0100 [thread overview]
Message-ID: <1441808839.5798.40.camel@ipfire.org> (raw)
In-Reply-To: <55E6E53C.5040903@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 2511 bytes --]
Hi,
On Wed, 2015-09-02 at 21:02 +0900, Xaver4all wrote:
> I'm sorry that this information is not useful for your workflow,
> but I don't want to waste your and my time, to explain you my working
> scenario.
you must accept a certain discourse about these things. If we would
accept every patch without considering it carefully, we might have
really messed up distribution after a while. Everything that is added
must make sense, must not harm the system and must be maintained by
someone.
> But I will give two examples:
> I guess form your mail that you don't use the GUI to check the logs,
> because if you do so how do you tell how old is a given log entry.
> Or if you add a firewall rule which should only apply on workdays
> form 8-16 o'clock.
> So when you do something like this you have to connect via SSH and
> check the time
> and for the rest you use the GUI? IHO this is not very handy.
> Or do you just trust a system that is running 24/7 and you set the
> clock one's and believe that the time doesn't get messed up (even
> with an daily NTP update). There are Country's with daylight saving
> period so timezone offset could also get changed (at least on your
> workstation).
So this a point for showing the system clock I can agree to. I would
like to suggest to add it to the already existing bar at the top,
because I think that it will fit wonderfully to the right of the speed
-o-meter which can be made a bit more narrow to make the needed space.
The time should definitely include the timezone. I am not sure if secon
ds must be included. A piece of JS that automatically updates the time
is nice, but must be optional for browsers that do not support JS.
Best,
-Michael
>
> Kim
> > Hi,
> >
> > On Wed, 02 Sep 2015 04:03:26 +0200, Xaver4all <xaver4all(a)gmx.de>
> > wrote:
> >
> > > But time and timezone (you do not always administrate a machine
> > > that is
> > > in the local timezone, or maybe use the UTC time for your
> > > network)
> > > should really be displayed in GUI.
> > > The Uptime should also be displayed, maybe only on the home site.
> > > I don't want to check the logs when was last reboot, or if I see
> > > uptime
> > > is short I can check the logs for the reason.
> > I don't understand why you need that information. When I want to
> > add a firewall rule or a VPN user, I couldn't care less for any of
> > that information. So, perhaps you want to explain how exactly this
> > is useful for your working scenario.
> >
> >
> > Lars
> >
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next parent reply other threads:[~2015-09-09 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <55E6E53C.5040903@gmx.de>
2015-09-09 14:27 ` Michael Tremer [this message]
2015-09-09 15:13 ` Xaver4all
2015-09-11 15:08 ` Michael Tremer
[not found] <55CC92AC.3000504@gmx.de>
2015-08-13 13:00 ` Larsen
2015-08-13 16:33 ` Michael Tremer
2015-08-13 17:33 ` Matthias Fischer
2015-08-13 21:25 ` Michael Tremer
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=1441808839.5798.40.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/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