Re: [systemd-devel] Enable sandboxing options globally for all services
Am Mi., 9. Sept. 2020 um 21:40 Uhr schrieb Christopher Wong : > > Hi, > > > Is there a way to turn on a sandboxing option for all services? Recent versions of systemd allow to use global drop-in config snippets. See the changelog of v244 * Unit files now support top level dropin directories of the form .d/ (e.g. service.d/) that may be used to add configuration that affects all corresponding unit files. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Enable sandboxing options globally for all services
Hi, Is there a way to turn on a sandboxing option for all services? We would like to on an embedded system enable as much sandboxing options as default. Only whitelist options for services that need access to them. Best Regards, Christopher Wong ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] libsystemd/sd_bus: trouble understanding how to parse complex responses
On Di, 08.09.20 20:51, Sergey 'Jin' Bostandzhyan (j...@mediatomb.cc) wrote:
> >
> > https://dbus.freedesktop.org/doc/dbus-specification.html#introspection-format
>
> Oh, so you mean that when I use "busctl call" it would detect and fake a
> GetManagedObjects() method invocation and internally use XML
> introspection?
No. I meant that "busctl introspect" and "busctl tree" use the XML
data, and not GetManagedObjects(). If you invoke "busctl call" then
you get what you ask for, we do no magic redirect.
> Is it somehow possible to figure this out via command line tools if the
> problem is in the missing GetManagedObjects() implementation or not?
Well, the introspection data should advertise GetManagedObjects()
method if it's supported.
>
> > > while (sd_bus_message_enter_container(m, SD_BUS_TYPE_ARRAY,
> > > "{oa{sa{sv}}}") > 0)
> > > {
> >
> > Hmm, this is what you'd write when you have an array of arrays...
>
> Uhm, how do I correctly "enter" a container like this one:
> "a{oa{sa{sv}}}" ?
Using sd_bus_message_enter_container() as you do, but you#d not call
it in a loop like you do, as that only makes sense if the actual type
string is "aa{oa{sa{sv}}}", i.e. starts with an array of arrays.
> I guess this is correct, what GetManagedObjects() returns is an array of
> dictionaries "a{oa{sa{sv}}}" or am I misinterpreting it?
Well, the way dbus encodes dictionaries is as "array of dictionary
entries. That's what the "a{…}" means.
> sd_bus_message_enter_container(m, SD_BUS_TYPE_DICT_ENTRY, "oa{sa{sv}}")
> returns 1 on the first call, thats where I get the first path that
> equals to "/org/freedesktop/ModemManager1/Modem/0" and it returns 0 on the
> next invocation.
It returns 0 if you reached the end of the surrounding container, i.e. the
end of the structure or array.
> > Normally, you#d enter the array once and then iterate through the
> > dict entries contained therein. i.e. unless there's an "aa" object
> > somewhere (i.e. "array of array") you'd do the while loop around the
> > dict entries, not the array object.
>
> Could you please clarify how iteration works in sd_bus sense? Is my
> understanding correct that I need to use sd_bus_message_skip() before
> exiting the container in order to iterate to the next item, if I am not
> interested in parsing all of the nested items? Or can I just "exit" at any
> time and expect the next "enter" invocation to fast forward to the
> next entry?
You are supposed to be at the end of the structure/array when calling
sd_bus_message_exit_container(). Otherwise you'll get EBUSY. We should
probably document that in the man page.
> Based on what you are saying the inner while loop that I had right after
> entering the array should have returned all items. So I start by entering
> the array:
>
> // starting with a{oa{sa{sv}}}
> sd_bus_message_enter_container(m, SD_BUS_TYPE_ARRAY, "{oa{sa{sv}}}")
>
> And loop over dictionary key-value pairs:
>
> // brings me down into oa{sa{sv}}}, I am only interested in the object paths:
> while (sd_bus_message_enter_container(m, SD_BUS_TYPE_DICT_ENTRY,
> "oa{sa{sv}}") > 0) {
> sd_bus_message_read_basic(m, SD_BUS_TYPE_OBJECT_PATH, );
> sd_bus_message_skip(m, "a{sa{sv}}");
> sd_bus_message_exit_container(m);
> }
>
> Does the above look correct? As mentioned, I am not getting errors, return
> codes are fine, so it all looks normal, but I am only reading out
> the first path, on the second iteration
> sd_bus_message_enter_container(m, SD_BUS_TYPE_DICT_ENTRY,
> "oa{sa{sv}}") returns 0 which aborts the loop.
This does look correct to me.
> At this point I am not sure if sd_bus actually behaves correctly and
> GetManagedObjects() returns only one path or if I messed up the parsing of
> the reply somehow? And I am not sure how to check that...
>
> I would like to avoid parsing XML if I can, but of course that option is
> still there; nevertheless, I would first like to understand what is going on
> with the GetManagedObjects() call and if the problem is really there or
> somewhere else.
Consider using "busctl monitor" to see what the message your client
receives actually contains.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [EXT] Re: Using timedatectl on a readonly rootfile system using mender
Can we close this issue? I have a solution that works. I will provide it to mender and hopefully they will maintain it if not then I will be happy to maintain it. On Wed, Sep 9, 2020 at 11:30 AM Lennart Poettering wrote: > On Mi, 09.09.20 09:23, Colin Guthrie (gm...@colin.guthr.ie) wrote: > > > Alvin Šipraga wrote on 08/09/2020 22:54: > > > Hi, > > > > > > On 9/8/20 4:12 PM, Colin Guthrie wrote: > > > > > >> 2. Set your /etc/ master image to make /etc/localtime to be a symlink > to > > >> /run/localtime and then ensure /run/localtime is a symlink to the > > >> appropriate file in /usr during early boot (e.g. in initramfs). Then > > >> when you want to to change the timezone, just update the /run/ > symlink. > > > This might not work as expected - systemd sometimes assumes that > > > /etc/localtime is a symlink into /usr/share/zoneinfo and will not > > > understand double symlinks. See src/basic/time-util.c:get_timezone() > for > > > at least one example. > > > > But that really depends on what you define as "not work". Sure > > timedatectl may not report correctly, but that shouldn't matter too much > > if you're not using to query or update (the latter obviously won't work > > anyway), but for the purposes of software *using* the timezone, I don't > > tihnk anything will actually break. > > Actually, that's not quite true: > > > https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/message/TVVXVO5HJGH5JOAWJJDJNA3BPBPPRS37/ > > (This is a current thread on the fedora ML) > > glibc doesn't care what /etc/localtime is, but all code that wants to > know the timezone name, i.e. a string like "Europe/Berlin" generally > requires /etc/symlink to be a readable symlink. > > https://www.freedesktop.org/software/systemd/man/localtime.html > > Lennart > > -- > Lennart Poettering, Berlin > ___ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/systemd-devel > ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Cannot nspawn raspbian 10
On Mi, 09.09.20 14:20, chiasa.men (chiasa@web.de) wrote:
> (cf. https://github.com/systemd/systemd/issues/16975)
>
> Testscript:
> wget https://downloads.raspberrypi.org/raspios_lite_armhf_latest -o r.zip
> unzip r.zip
> LOOP=$(losetup --show -Pf *raspios-buster-armhf-lite.img)
> mount ${LOOP}p2 /mnt
> mount ${LOOP}p1 /mnt/boot
> systemd-nspawn --bind /usr/bin/qemu-arm-static --boot --directory=/mnt
My educated guess is that we call some syscall/ioctl qemu doesn't know
about, and cannot implement properly. You probably have to do some
manual tracing and then tell the qemu people about this so that they
can add the syscall/translation stubs to that.
i.e. I am pretty sure this will turn out to be something to fix in
qemu, not in systemd.
We had that before btw, and qemu addressed this quickly to my
knowledge.
Try booting up systemd.log_level=debug on the nspawn cmdline, to get
more verbose output. But output will generally suck if this is really
just a syscall/ioctl translation issue, you need to know what are you
doing if you want to track that down.
Lennart
--
Lennart Poettering, Berlin
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd-devel Digest, Vol 125, Issue 21
On Mi, 09.09.20 10:51, 海阔天空 (858293...@qq.com) wrote: > Hi All, > > > Could you help with the question below? > Does sd_dbus support non-blocking or multi-thread? sd-bus is threads-aware, but not thread-safe. The idea is to allocate a separate bus connection for each thread, and not share connections between threads though. if you want to receive asynchronous notifications via sd-bus, then you need to invoke sd_bus_wait() + sd_bus_process() in a loop (possibly interleaved with other calls), or use an event loop of some form, for example sd-event. If you invoke usleep() or similar long-blocking syscalls from a thread that also is supposed to run your bus connection then of course the processing of the bus connection cannot take place then. Lennart -- Lennart Poettering, Berlin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [EXT] Re: Using timedatectl on a readonly rootfile system using mender
On Mi, 09.09.20 09:23, Colin Guthrie (gm...@colin.guthr.ie) wrote: > Alvin Šipraga wrote on 08/09/2020 22:54: > > Hi, > > > > On 9/8/20 4:12 PM, Colin Guthrie wrote: > > > >> 2. Set your /etc/ master image to make /etc/localtime to be a symlink to > >> /run/localtime and then ensure /run/localtime is a symlink to the > >> appropriate file in /usr during early boot (e.g. in initramfs). Then > >> when you want to to change the timezone, just update the /run/ symlink. > > This might not work as expected - systemd sometimes assumes that > > /etc/localtime is a symlink into /usr/share/zoneinfo and will not > > understand double symlinks. See src/basic/time-util.c:get_timezone() for > > at least one example. > > But that really depends on what you define as "not work". Sure > timedatectl may not report correctly, but that shouldn't matter too much > if you're not using to query or update (the latter obviously won't work > anyway), but for the purposes of software *using* the timezone, I don't > tihnk anything will actually break. Actually, that's not quite true: https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/message/TVVXVO5HJGH5JOAWJJDJNA3BPBPPRS37/ (This is a current thread on the fedora ML) glibc doesn't care what /etc/localtime is, but all code that wants to know the timezone name, i.e. a string like "Europe/Berlin" generally requires /etc/symlink to be a readable symlink. https://www.freedesktop.org/software/systemd/man/localtime.html Lennart -- Lennart Poettering, Berlin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Cannot nspawn raspbian 10
(cf. https://github.com/systemd/systemd/issues/16975)
Testscript:
wget https://downloads.raspberrypi.org/raspios_lite_armhf_latest -o r.zip
unzip r.zip
LOOP=$(losetup --show -Pf *raspios-buster-armhf-lite.img)
mount ${LOOP}p2 /mnt
mount ${LOOP}p1 /mnt/boot
systemd-nspawn --bind /usr/bin/qemu-arm-static --boot --directory=/mnt
Output:
Press ^] three times within 1s to kill container.
systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR
+SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP
+BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
Detected virtualization systemd-nspawn.
Detected architecture arm.
Welcome to Raspbian GNU/Linux 10 (buster)!
Set hostname to .
Initializing machine ID from container UUID.
Failed to process netlink event: Message too long
File /lib/systemd/system/systemd-journald.service:12 configures an IP firewall
(IPAddressDeny=any), but the local system does not support BPF/cgroup based
firewalling.
Proceeding WITHOUT firewalling in effect! (This warning is only shown for the
first loaded unit using IP firewalling.)
[ OK ] Started Dispatch Password Requests to Console Directory Watch.
[UNSUPP] Starting of Arbitrary Executable File Formats File System Automount
Point not supported.
[ OK ] Listening on initctl Compatibility Named Pipe.
[ OK ] Started Forward Password Requests to Wall Directory Watch.
[ OK ] Reached target Local Encrypted Volumes.
[ OK ] Reached target Paths.
[ OK ] Listening on Journal Socket (/dev/log).
[ OK ] Reached target Swap.
[ OK ] Listening on Syslog Socket.
[UNSUPP] Starting of /dev/serial1 not supported.
[DEPEND] Dependency failed for Configure Bluetooth Modems connected by UART.
hciuart.service: Job hciuart.service/start failed with result 'dependency'.
[ OK ] Listening on Journal Socket.
Mounting Huge Pages File System...
Starting Journal Service...
Starting Set the console keyboard layout...
Starting Remount Root and Kernel File Systems...
Starting Helper to synchronize boot up for ifupdown...
[ OK ] Created slice system-getty.slice.
Starting Restore / save the current clock...
Mounting FUSE Control File System...
Mounting RPC Pipe File System...
[ OK ] Created slice User and Session Slice.
[ OK ] Reached target Slices.
[ OK ] Mounted Huge Pages File System.
[ OK ] Mounted RPC Pipe File System.
[ OK ] Mounted FUSE Control File System.
[ OK ] Started Helper to synchronize boot up for ifupdown.
Failed to receive notification message: Message too long
systemd-remount-fs.service: Main process exited, code=exited, status=1/FAILURE
systemd-remount-fs.service: Failed with result 'exit-code'.
[FAILED] Failed to start Remount Root and Kernel File Systems.
See 'systemctl status systemd-remount-fs.service' for details.
Starting Create Static Device Nodes in /dev...
[ OK ] Started Restore / save the current clock.
[ OK ] Started Create Static Device Nodes in /dev.
[ OK ] Started Set the console keyboard layout.
[ OK ] Reached target Local File Systems (Pre).
[ OK ] Reached target Local File Systems.
Starting Preprocess NFS configuration...
Starting Raise network interfaces...
Starting Set console font and keymap...
nfs-config.service: Succeeded.
[ OK ] Started Preprocess NFS configuration.
[ OK ] Reached target NFS client services.
[ OK ] Reached target Remote File Systems (Pre).
[ OK ] Reached target Remote File Systems.
[ OK ] Started Set console font and keymap.
[ OK ] Started Raise network interfaces.
[*** ] A start job is running for Journal Service (1min 29s / 1min 30s)
systemd-journald.service: Start operation timed out. Terminating.
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[DEPEND] Dependency failed for Flush Journal to Persistent Storage.
systemd-journal-flush.service: Job systemd-journal-flush.service/start failed
with result 'dependency'.
systemd-journald.service: Service has no hold-off time (RestartSec=0),
scheduling restart.
systemd-journald.service: Scheduled restart job, restart counter is at 1.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[* ] A start job is running for Journal Service (1min 29s / 1min 30s)
[**] A start job is running for Journal Service (1min 30s / 3min)
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
systemd-journald.service: Service has no hold-off time (RestartSec=0),
scheduling restart.
systemd-journald.service: Scheduled restart job, restart counter is at 2.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[ *** ] A start job is running for Journal Service (1min 29s / 1min 30s)
[ *** ] A start job is running for Journal Service (1min 30s / 3min)
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service'
Re: [systemd-devel] Why systemd keeps references on passed sockets ?
On Tue, Sep 8, 2020 at 5:41 PM Lennart Poettering wrote: > > On Di, 08.09.20 17:35, Francis Moreau (francis.m...@gmail.com) wrote: > > > On Mon, Sep 7, 2020 at 4:38 PM Lennart Poettering > > wrote: > > > > > > "React on the socket close?" — What do you mean by that? > > > > > > > I mean if my service explicitly calls close() then systemd could stop > > the socket on its side so its are freed until the service is > > restarted. I think it is what you described below. > > close() just drops a ref to the socket. Only when close() drops the > last ref something actually happens on the socket and it is > destroyed. This means: systemd doesn't get notified about your code > invoking close(), because all you did is drop one ref of many. > > > > Note that on Linux you can invoke shutdown() on a listening socket > > > (i.e. not just on the connection socket, but on a listening > > > socket). iirc in that case systemd actually notices and will put the > > > .socket unit in failure mode... > > > > > > > I looked at the code and there is: > > > > if (state != SOCKET_LISTENING) > > socket_unwatch_fds(s); > > > > So I'm not sure how systemd can react on shutdown(). And I tried to > > call shutdown() in my service but it has no effects. > > Hmm, that suggests we'd have to slightly update our logic then for > this to work: keep the listening fds in the poll, but turn off all > the EPOLLIN bit we listen on. > > > > Would that work for you? (Maybe we could even tweak this a bit in > > > systemd, so that when you invoke shutdown() on the socket systemd > > > holds for you we do not consider that a failure anymore, but a clean > > > way to tell systemd to stop the socket). > > > > That is a good idea especially if systemd doesn't consider an error > > when the service closes or shutdown the socket. > > > > But again in the code I can see: > > > > sd_event_add_io(UNIT(s)->manager->event, >event_source, p->fd, > > EPOLLIN, socket_dispatch_io, p); > > > > It seems that it only listens to "EPOLLIN" events. So it doesn't > > listen to "EPOLLUP". > > EPOLLHUP is always implied, you don't have to specify it. if you > specifiy zero as mask you will still get notified about EPOLLHUP + > EPOLLERR. > Thank you for the info > But you are right we currently remove the fd from polling while the > socket's service is running. We'd have to change that (as mentioned > above). happy to review a PR for that. I'm afraid I'm not skilled enough in systemd internals to work on this, sorry. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [EXT] Re: Using timedatectl on a readonly rootfile system using mender
Alvin Šipraga wrote on 08/09/2020 22:54: > Hi, > > On 9/8/20 4:12 PM, Colin Guthrie wrote: > >> 2. Set your /etc/ master image to make /etc/localtime to be a symlink to >> /run/localtime and then ensure /run/localtime is a symlink to the >> appropriate file in /usr during early boot (e.g. in initramfs). Then >> when you want to to change the timezone, just update the /run/ symlink. > This might not work as expected - systemd sometimes assumes that > /etc/localtime is a symlink into /usr/share/zoneinfo and will not > understand double symlinks. See src/basic/time-util.c:get_timezone() for > at least one example. But that really depends on what you define as "not work". Sure timedatectl may not report correctly, but that shouldn't matter too much if you're not using to query or update (the latter obviously won't work anyway), but for the purposes of software *using* the timezone, I don't tihnk anything will actually break. Just my take on it, and could indeed be wrong. Just seems like a lot of discussion over quite a minor point! :-) Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Antw: [EXT] Re: Q: Start a unit n minutes after a successful boot
>>> Lennart Poettering schrieb am 08.09.2020 um 16:19 in Nachricht <20200908141953.GB272516@gardel-login>: > On Di, 08.09.20 09:21, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) wrote: > >> Hi! >> >> Configuring a new system with non‑redundant system disk I'm >> wondering: How could I start an automatic backup job that is >> triggered n minutes after the system started successfully (to avoid >> backing up broken configurations)? > > What does "started successfully" mean to you? Definitely not "rescue shell" or "emergency mode" and most likely no failed services for some time. Something like that. > > Lennart > > ‑‑ > Lennart Poettering, Berlin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Antw: [EXT] Re: Alias use in socket file
>>> Lennart Poettering schrieb am 08.09.2020 um 16:04 in Nachricht <20200908140433.GC272410@gardel-login>: > On Di, 08.09.20 08:45, Belisko Marek (marek.beli...@gmail.com) wrote: > >> Hi, >> >> I'm using yocto build systemd and I'm using openssh server which >> create sshd.socket + sshd@.service files. With socket I can control if >> ssh is enabled / disabled. I have an application which expects to >> check statu of ssh.service. I tried to add Alias=ssh.service to >> sshd.socket file and tried systemd enable sshd.socket but systemd >> cannot see ssh.service. Is there some other way to create a link to an >> existing socket file? Thanks > > No, systemd refuses to recognize unit symlinks that change unit type > (i.e. the unit suffix after the dot) as aliases. It also doesn't > accept symlinks that change if a unit is templated or not. Objects > can't magically change their type, and they cannot suddenly > become/stop being templated or not. Never tried such, but I hope there is a good error message when such links are being ignored or denied ;-) > > Sorry, > > Lennart > > ‑‑ > Lennart Poettering, Berlin > ___ > systemd‑devel mailing list > systemd‑de...@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/systemd‑devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Antw: Re: [EXT] Re: Using timedatectl on a readonly rootfile system using mender
>>> Shravan Singh schrieb am 08.09.2020 um 15:31 in Nachricht : > No one is answering a simple question. Why we have to guard timezone so > much?. > Why can't I change it? What happens if I change it on a read-only rootfs? I > am breaking the whole systemd by doing this? > > In fact most of the people in this group are suggesting a work-around to me > > "I wonder: If you have a working pull request, why don't you use that code > and be happy with it? That's how free software works. > Still everybody interested can apply you patch." > > Yes, it works. My question is why is not getting included so that everyone > can benefit from it. That is how a free software community should work. I think the poroble is: You think your patch is great and everybody wants that. However you are not everybody, and so you have to let others decide whether they like the feature or not. Many times dome developers thing a feature is great, but it actually fails. Just think of the user interface of Windows 8... > > In this day and age of mobile computing it is really shocking to see. That > timezone is not regarded as something that can be dynamically changed. You are mixing things: With your android phone you can change timezones, but you have created a special setup where anothe rspecial patch is needed. A bit like first shooting your own foot and then calling for a doctor, wondering why not everybody is needing a doctor... This is just my opinion, not everybodys. ;-) Regards, Ulrich > > Anyway this issue is going no-further if people are adamant in not changing > it. > And I don't see any reason in going back and forth with everyone. > > > Regards, > Shravan Singh > (239) 243-0838 > > Blue Sparq, Inc. > 928 NE 24th Lane unit 4 and 5. > Cape Coral, FL 33993 > > IMPORTANT: The contents of this email and any attachments are confidential. > They are intended for the named recipient(s) only. If you have received > this email by mistake, please notify the sender immediately and do not > disclose the contents to anyone or make copies thereof. > > > On Mon, Sep 7, 2020 at 4:49 AM Ulrich Windl < > ulrich.wi...@rz.uni-regensburg.de> wrote: > >> >>> Shravan Singh schrieb am 05.09.2020 um 00:26 >> in >> Nachricht >> : >> > And this is a major problem for any one running raspberry pi, NXP or any >> > other embedded processor that uses mender and embedded linux. >> >> Maybe an embedded OS really should use UTC as timezone. >> >> > A machine with embedded linux running on it goes to San Francisco and >> then >> > transported to Chicago. >> > And you are saying that we shouldn't be allowed to change the timezone? >> >> The question is : Who will "see" the timezone? Does every process run with >> the same timezone? >> >> > Just because you are not "convinced" >> > Does this group have a poll system? Let's put this to poll and see? >> >> I wonder: If you have a working pull request, why don't you use that code >> and be happy with it? That's how free software works. >> Still everybody interested can apply you patch. >> > >> > I have tried having a rational explanation with you but your attitude is >> > just appalling >> > >> > I have tried this solution and it works >> > https://github.com/systemd/systemd/pull/8277. >> > I just don't understand why you are not willing to accept this. And >> provide >> > a solution to all the people using raspberry pi and or embedded >> processors? >> > >> > >> > >> > >> > Regards, >> > Shravan Singh >> > (239) 243-0838 >> > >> > Blue Sparq, Inc. >> > 928 NE 24th Lane unit 4 and 5. >> > Cape Coral, FL 33993 >> > >> > IMPORTANT: The contents of this email and any attachments are >> confidential. >> > They are intended for the named recipient(s) only. If you have received >> > this email by mistake, please notify the sender immediately and do not >> > disclose the contents to anyone or make copies thereof. >> > >> > >> > On Fri, Sep 4, 2020 at 6:16 PM Shravan Singh >> wrote: >> > >> >> What constitutes a configuration? >> >> And please read my email subject. I can't have writable /etc, mender >> >> dosen't allow that. >> >> >> >> In today's mobile computing age you really think users shouldn't change >> >> timezone? >> >> You keep saying " I for one am certainly not convinced that the >> timezones" >> >> but you don't explain why? >> >> Are you looking at this system as a static machine? That can never >> change >> >> timezone? >> >> >> >> And please don't use profanity. I have not and you shouldn't either. >> >> >> >> Regards, >> >> Shravan Singh >> >> (239) 243-0838 >> >> >> >> Blue Sparq, Inc. >> >> 928 NE 24th Lane unit 4 and 5. >> >> Cape Coral, FL 33993 >> >> >> >> IMPORTANT: The contents of this email and any attachments are >> >> confidential. They are intended for the named recipient(s) only. If you >> >> have received this email by mistake, please notify the sender >> immediately >> >> and do not disclose the contents to anyone or make copies thereof. >> >> >> >> >> >> On Fri,
