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] [EXT] Re: Using timedatectl on a readonly rootfile system using mender
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. 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. 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, Sep 4, 2020 at 6:05 PM Lennart Poettering < > lenn...@poettering.net> > >> wrote: > >> > >>> On Fr, 04.09.20 15:54, Shravan Singh (shra...@bluesparq.com) wrote: > >>> > >>> > Yes, But help me understand. > >>> >
Re: [systemd-devel] Using timedatectl on a readonly rootfile system using mender
"is automatically acquire and automatically released and automatically manage" And this is just what a timezone. "I think this discussion kinda lost its usefulness, I am just repeating myself" Ohh I knew that you narcissist 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:30 PM Lennart Poettering wrote: > On Fr, 04.09.20 18:16, Shravan Singh (shra...@bluesparq.com) wrote: > > > What constitutes a configuration? > > And please read my email subject. I can't have writable /etc, mender > > dosen't allow that. > > Well, then that's sad, and something to bring up with mender? if they > do not allow local config, then obviously your goals and their > offerings apparently do not match given you want to cnfigure timezones > locally, as I understand. > > > In today's mobile computing age you really think users shouldn't change > > timezone? > > I don't think that. Do you? > > I am just saying: config is config, if you want writable config then > make /etc writable. /etc is for local config. timezones are config, > hence if you want changable timezones then make /etc writable. pretty > logic, pretty easy. > > > You keep saying " I for one am certainly not convinced that the > timezones" > > but you don't explain why? > > transient state is when something only has validity during the > current boot in the current context, is automatically acquire and > automatically released and automatically managed. > > Config otoh is generally persistent, ultimately configured by some > human or so and has is more of static nature. > > Timezone settings are usually man made, and assumed to be > persistent. They aren't part of network params acquired via DHCP > (well, DHCP actually has a field for that, but it's typically not > used, at least I didn't find a single network in the wild that uses > that) or a similar dynamic protocol. > > > Are you looking at this system as a static machine? That can never change > > timezone? > > It's you who insists that /etc (and thus configuration) should be > read-only, not me. It's you who's then upset that you cannot change > configuration if /etc (and thus configuration) is read-only. > > I think this discussion kinda lost its usefulness, I am just repeating > myself, and will thus refrain from further input on this thread. If my > explanations aren't enough, aren't acceptable I think we both have to > live with that. > > Lennart > > -- > Lennart Poettering, Berlin > ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Using timedatectl on a readonly rootfile system using mender
And this is a major problem for any one running raspberry pi, NXP or any other embedded processor that uses mender and embedded linux. 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? Just because you are not "convinced" Does this group have a poll system? Let's put this to poll and see? 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, Sep 4, 2020 at 6:05 PM Lennart Poettering > wrote: > >> On Fr, 04.09.20 15:54, Shravan Singh (shra...@bluesparq.com) wrote: >> >> > Yes, But help me understand. >> > I think you said that you are not convinced as to why that has to done. >> > >> > My argument is very simple shouldn't a Linux environment allow change in >> > timezone easily? >> >> Oh we do. But if your want configuration to be changable, then mount >> /etc writable. >> >> You have two contradicting goals: you want immutable config, but then >> you want to change config. So how's that gonna work? >> >> If you want your persistent config changable then make it changable, >> i.e. mount /etc/ writable. >> >> > Now I am not an expert in Linux kernel development. But I see that some >> of >> > the files, even though they reside in /etc are linked to file in /run >> > Like *resolv.conf. *Which allows dynamic changes. >> >> I explained this already. DNS server data today is much less config >> than state, acquired dynamically via DHCP, hence most distros don#t >> configure it in /etc so much anymore, but manage it in /run (where >> transient state is generally kept), and only keep a compat symlink in >> /etc. If you try to convince people though that the local timezone >> should just be transient state and not persistent config you'll have a >> hard time. I for one am certainly not convinced that the timezones are >> state... >> >> I mean, the line between persistent configuration and transient state >> is blurry, but in the case of DNS settings and timezone settings I >> certainly can draw a line easily. >> >> > timezone activity change is a very basic change one that needs to be >> > supported by the system. Why guard it with so much. >> >> We don't do that. Just make /etc/ writable ffs, if you want stuff in >> /etc to be changable. >> >> Lennart >> >> -- >> Lennart Poettering, Berlin >> > ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Using timedatectl on a readonly rootfile system using mender
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, Sep 4, 2020 at 6:05 PM Lennart Poettering wrote: > On Fr, 04.09.20 15:54, Shravan Singh (shra...@bluesparq.com) wrote: > > > Yes, But help me understand. > > I think you said that you are not convinced as to why that has to done. > > > > My argument is very simple shouldn't a Linux environment allow change in > > timezone easily? > > Oh we do. But if your want configuration to be changable, then mount > /etc writable. > > You have two contradicting goals: you want immutable config, but then > you want to change config. So how's that gonna work? > > If you want your persistent config changable then make it changable, > i.e. mount /etc/ writable. > > > Now I am not an expert in Linux kernel development. But I see that some > of > > the files, even though they reside in /etc are linked to file in /run > > Like *resolv.conf. *Which allows dynamic changes. > > I explained this already. DNS server data today is much less config > than state, acquired dynamically via DHCP, hence most distros don#t > configure it in /etc so much anymore, but manage it in /run (where > transient state is generally kept), and only keep a compat symlink in > /etc. If you try to convince people though that the local timezone > should just be transient state and not persistent config you'll have a > hard time. I for one am certainly not convinced that the timezones are > state... > > I mean, the line between persistent configuration and transient state > is blurry, but in the case of DNS settings and timezone settings I > certainly can draw a line easily. > > > timezone activity change is a very basic change one that needs to be > > supported by the system. Why guard it with so much. > > We don't do that. Just make /etc/ writable ffs, if you want stuff in > /etc to be changable. > > Lennart > > -- > Lennart Poettering, Berlin > ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Using timedatectl on a readonly rootfile system using mender
This is the link: https://github.com/systemd/systemd/pull/8277 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:00 PM Dave Howorth wrote: > On Fri, 4 Sep 2020 21:32:19 +0200 > Lennart Poettering wrote: > > On Fr, 04.09.20 14:10, Shravan Singh (shra...@bluesparq.com) wrote: > > > > > Hello Lennart, > > > > > > Can you help me in understanding why this push was rejected? > > > *Make timedatectl nicely work with read-only filesystems #8277 * > > > > The explanation is in the PR comments. > > Would either of you care to provide a link to the actual text you're > referring to, for people reading who are not intimately associated with > the code? > > I can see why read-only rootfs might be desirable, and in an age of > mobile computing I can see why mutable timezones might also be > desirable. > > > Lennart > ___ > 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] Using timedatectl on a readonly rootfile system using mender
Yes, But help me understand. I think you said that you are not convinced as to why that has to done. My argument is very simple shouldn't a Linux environment allow change in timezone easily? Now I am not an expert in Linux kernel development. But I see that some of the files, even though they reside in /etc are linked to file in /run Like *resolv.conf. *Which allows dynamic changes. timezone activity change is a very basic change one that needs to be supported by the system. Why guard it with so much. Again I am asking if there is something else that you would want instead of the method suggested in the ticket. I guess, your main concern is that this might open the flood gates where now everyone is changing /etc files according to their own whim and now read-only fs is not really a read-only fs But then again I would argue that timezone changes has little effect and it should be customizable according to the user. I am happy to spend my time doing that and submitting it again for review. Like I said I just want to know the root issue with that approach . Because there are plenty other people who might be facing the same issue. I am happy to invest my time in doing this 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 3:32 PM Lennart Poettering wrote: > On Fr, 04.09.20 14:10, Shravan Singh (shra...@bluesparq.com) wrote: > > > Hello Lennart, > > > > Can you help me in understanding why this push was rejected? > > *Make timedatectl nicely work with read-only filesystems #8277 * > > The explanation is in the PR comments. > > Lennart > > -- > Lennart Poettering, Berlin > ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Using timedatectl on a readonly rootfile system using mender
Hello Lennart, Can you help me in understanding why this push was rejected? *Make timedatectl nicely work with read-only filesystems #8277 * If there is some major issue. I would like to take this opportunity to make it right and submit it again 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 11:27 AM Lennart Poettering wrote: > On Do, 20.08.20 14:22, Shravan Singh (shra...@bluesparq.com) wrote: > > > But no one is telling how to resolve my issue with a read-only > > rootfs. > > There's no concept for having some files in /etc writable and others > not. And you cannot use symlinking for this, nor bind mounts, since > config files in /etc are usually updated atomically, i.e. new versions > written in full into temporary files and then moved into place > atomically so that you either see the old or the new but never > anything half-written. This means that the dir of the file to update > needs to be writable and that the old inode goes away entirely on > update instead of being updated. > > I must say I see little point in having "etc mostly read-only" > though. I mean, either your config is entirely read-only or it > isn't. If it is read-only /etc being read-only is not a problem. If it > can be modified then make /etc the source of truth for it and > writable, and drop everything else from it, so that it only contains > the writable data you care about. A lot of software these days falls > back to fallback settings below /usr somewhere if their config files > in /etc don#t exist, and for the stuff that doesn't work like this, > move it over and symlink it from /etc (you can create those symlinks > with tmpfiles.d factory options). > > > There are other files which can be overwritten in /etc that are linked > to a > > file in /run directory for eg /etc/resolv.conf file. > > Well, that file is quite different, resolve.conf is historically was > configuraiton but today is more state than configuraiton, i.e. it is > usually configured dynamically via DHCP or so. Hence people started to > manage it in /run and leave /etc/resolv.conf only as a compat symlink > in place, if you so will. > > > Then why not /etc/localtime. Why is localtime guarded so much > > I refuse to believe that I am the only person facing this problem. But I > > did find some leads now. Will keep you posted > > /etc/localtime is generally considered to be configuration and not > state, hence people are typically fine with leaving it in /etc, since > that's where persistant configuration is supposed to be. > > I am sorry, but /etc on Linux is a single directory, and you can only > cleanly choose between all configuration read only or none, there's no > nice way for a middle ground. Sorry. > > 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
Hello Ulrich, Ohh believe me when I say this. I do not want to make it a read-only file system. I was a happy guy with a swing in my steps. But mender-delta updates won't work without making it read-only rootfs . So this is just a big loop that I have involved myself in. And from that day on, this has been a constant reason of despair in my life. I raised an issue with mender. According to them, They haven't come across this issue. Which again is a difficult pill to swallow. And On top of that there was a merge request sent to systemd which tries to address the same issue that I am talking about and it was rejected. Can someone explain to me why it was rejected? this is the heading --> *Make timedatectl nicely work with read-only filesystems #8277 * But I can now see what was done in that merge request and try to imitate that. 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, Aug 21, 2020 at 2:34 AM Ulrich Windl < ulrich.wi...@rz.uni-regensburg.de> wrote: > >>> Shravan Singh schrieb am 20.08.2020 um 20:22 > in > Nachricht > : > > Hello Andrei, > > > > Thank you for your email. Yes, People have been telling me this: > > > > *Changing timezone globally requires changing /etc/localtime link which > > requires writable /etc. * > > > > But no one is telling how to resolve my issue with a read-only rootfs. > > There are other files which can be overwritten in /etc that are linked > to a > > file in /run directory for eg /etc/resolv.conf file. > > Then why not /etc/localtime. Why is localtime guarded so much > > I guess this is due to the fact that a PDP 11 really wasn't a mobile > computer; > thus the system timezone was not expected to change every boot. ;-) > > > I refuse to believe that I am the only person facing this problem. But I > > did find some leads now. Will keep you posted > > Traditionally /etc (thus rootfs) is writable. No problems. Making it > read-only, you create a problem. > > > > > But thank you so much for your response > > > > 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 Thu, Aug 20, 2020 at 2:00 PM Andrei Borzenkov > > wrote: > > > >> 20.08.2020 18:55, Shravan Singh пишет: > >> > Hello, > >> > I have raspberry-pi cm3 which is running an embedded yocto poky linux > >> > warrior branch with mender. > >> > > >> > I have made my rootfs as read-only because of which I am not able to > use > >> > timedatectl to change the system time zone. > >> > > >> > I was looking through the c code which makes me think that even if I > did > >> > create and change symlink to point to a file in a read and write > location > >> > of the memory. It won't make any difference. > >> > > >> > >> Changing timezone globally requires changing /etc/localtime link which > >> requires writable /etc. > >> > >> > I looked into the file timedated.c and here is where I wanted some > help. > >> I > >> > see the line > >> > * r= get_timzeone()* in the function *context_read_data* all I want to > >> know > >> > is where is *get_timezone* defined and how is it calling > */etc/localtime* > >> > > >> > >> src/basic/time-util.c > >> > >> grep is wonderful tool. > >> > >> > Any help will be appreciated. I have raised questions everywhere and I > am > >> > not getting any help at all. > >> > > >> > And I am not an embedded developer. This place is my last cry for help > >> > Regards, > >> > Shravan Singh > >> > (239) 243-0838 > >> > > >> > Blue Sparq, Inc. > >> > 928 NE 24th Lane unit 4 and 5. > >> > Cape Coral, FL 33993 > >> > >
Re: [systemd-devel] Using timedatectl on a readonly rootfile system using mender
Hello Andrei, Thank you for your email. Yes, People have been telling me this: *Changing timezone globally requires changing /etc/localtime link which requires writable /etc. * But no one is telling how to resolve my issue with a read-only rootfs. There are other files which can be overwritten in /etc that are linked to a file in /run directory for eg /etc/resolv.conf file. Then why not /etc/localtime. Why is localtime guarded so much I refuse to believe that I am the only person facing this problem. But I did find some leads now. Will keep you posted But thank you so much for your response 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 Thu, Aug 20, 2020 at 2:00 PM Andrei Borzenkov wrote: > 20.08.2020 18:55, Shravan Singh пишет: > > Hello, > > I have raspberry-pi cm3 which is running an embedded yocto poky linux > > warrior branch with mender. > > > > I have made my rootfs as read-only because of which I am not able to use > > timedatectl to change the system time zone. > > > > I was looking through the c code which makes me think that even if I did > > create and change symlink to point to a file in a read and write location > > of the memory. It won't make any difference. > > > > Changing timezone globally requires changing /etc/localtime link which > requires writable /etc. > > > I looked into the file timedated.c and here is where I wanted some help. > I > > see the line > > * r= get_timzeone()* in the function *context_read_data* all I want to > know > > is where is *get_timezone* defined and how is it calling */etc/localtime* > > > > src/basic/time-util.c > > grep is wonderful tool. > > > Any help will be appreciated. I have raised questions everywhere and I am > > not getting any help at all. > > > > And I am not an embedded developer. This place is my last cry for help > > 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. > > > > > > ___ > > 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 > ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Using timedatectl on a readonly rootfile system using mender
Hello, I have raspberry-pi cm3 which is running an embedded yocto poky linux warrior branch with mender. I have made my rootfs as read-only because of which I am not able to use timedatectl to change the system time zone. I was looking through the c code which makes me think that even if I did create and change symlink to point to a file in a read and write location of the memory. It won't make any difference. I looked into the file timedated.c and here is where I wanted some help. I see the line * r= get_timzeone()* in the function *context_read_data* all I want to know is where is *get_timezone* defined and how is it calling */etc/localtime* Any help will be appreciated. I have raised questions everywhere and I am not getting any help at all. And I am not an embedded developer. This place is my last cry for help 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. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
