Unable to make changes to /etc












0















I am using embedded linux (built using LTIB).



I am unable to make changes to /etc directory. Basically I want to add a start-up script to /etc/rc.d/init.d



/etc/ seems to be mounted as rwfs



output of df -h:



Filesystem                Size      Used Available Use% Mounted on
/dev/root 3.0G 376.9M 2.4G 13% /
tmpfs 424.2M 36.0K 424.1M 0% /dev
shm 424.2M 0 424.2M 0% /dev/shm
rwfs 376.0M 5.1M 370.9M 1% /mnt/rwfs
rwfs 376.0M 5.1M 370.9M 1% /tmp
rwfs 376.0M 5.1M 370.9M 1% /var
rwfs 376.0M 5.1M 370.9M 1% /etc


I have tried :



umount /etc/ 
touch /etc/dummy --> just for the sake of checking
reboot
(after boot-up)
ls -lth /etc/dummy ---> file is missing


This is an image which I boot from an SD card. On one of the SD cards, after I did the above umount /etc, and then placed a dummy file as mentioned above, on the next boot as expected /etc goes back to be mounted as tmpfs but the dummy file was available. But on another SD card when I try the same, dummy file is not available.



Any suggestions?



Output of mount (before using umount /etc/):



root@freescale /etc$ mount
rootfs on / type rootfs (rw)
/dev/root on / type ext2 (rw,relatime,errors=continue)
proc on /proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
shm on /dev/shm type tmpfs (rw,relatime)
rwfs on /mnt/rwfs type tmpfs (rw,relatime,size=385024k)
rwfs on /tmp type tmpfs (rw,relatime,size=385024k)
rwfs on /var type tmpfs (rw,relatime,size=385024k)
rwfs on /etc type tmpfs (rw,relatime,size=385024k)


Output of mount (after umount /etc):



rootfs on / type rootfs (rw)
/dev/root on / type ext2 (rw,relatime,errors=continue)
proc on /proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
shm on /dev/shm type tmpfs (rw,relatime)
rwfs on /mnt/rwfs type tmpfs (rw,relatime,size=385024k)
rwfs on /tmp type tmpfs (rw,relatime,size=385024k)
rwfs on /var type tmpfs (rw,relatime,size=385024k)









share|improve this question




















  • 1





    have you tried mount -o remount,rw /etc?

    – Eugen Rieck
    Jan 11 at 13:16











  • @EugenRieck: Yes I have tried, it comes back saying "mount: can't find /etc in /proc/mounts"

    – kman
    Jan 11 at 13:39













  • Please ask a specific question. "Any suggestions?" is not specific. My answer assumes the real question is "why?" See How to Ask.

    – Kamil Maciorowski
    Jan 11 at 14:04
















0















I am using embedded linux (built using LTIB).



I am unable to make changes to /etc directory. Basically I want to add a start-up script to /etc/rc.d/init.d



/etc/ seems to be mounted as rwfs



output of df -h:



Filesystem                Size      Used Available Use% Mounted on
/dev/root 3.0G 376.9M 2.4G 13% /
tmpfs 424.2M 36.0K 424.1M 0% /dev
shm 424.2M 0 424.2M 0% /dev/shm
rwfs 376.0M 5.1M 370.9M 1% /mnt/rwfs
rwfs 376.0M 5.1M 370.9M 1% /tmp
rwfs 376.0M 5.1M 370.9M 1% /var
rwfs 376.0M 5.1M 370.9M 1% /etc


I have tried :



umount /etc/ 
touch /etc/dummy --> just for the sake of checking
reboot
(after boot-up)
ls -lth /etc/dummy ---> file is missing


This is an image which I boot from an SD card. On one of the SD cards, after I did the above umount /etc, and then placed a dummy file as mentioned above, on the next boot as expected /etc goes back to be mounted as tmpfs but the dummy file was available. But on another SD card when I try the same, dummy file is not available.



Any suggestions?



Output of mount (before using umount /etc/):



root@freescale /etc$ mount
rootfs on / type rootfs (rw)
/dev/root on / type ext2 (rw,relatime,errors=continue)
proc on /proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
shm on /dev/shm type tmpfs (rw,relatime)
rwfs on /mnt/rwfs type tmpfs (rw,relatime,size=385024k)
rwfs on /tmp type tmpfs (rw,relatime,size=385024k)
rwfs on /var type tmpfs (rw,relatime,size=385024k)
rwfs on /etc type tmpfs (rw,relatime,size=385024k)


Output of mount (after umount /etc):



rootfs on / type rootfs (rw)
/dev/root on / type ext2 (rw,relatime,errors=continue)
proc on /proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
shm on /dev/shm type tmpfs (rw,relatime)
rwfs on /mnt/rwfs type tmpfs (rw,relatime,size=385024k)
rwfs on /tmp type tmpfs (rw,relatime,size=385024k)
rwfs on /var type tmpfs (rw,relatime,size=385024k)









share|improve this question




















  • 1





    have you tried mount -o remount,rw /etc?

    – Eugen Rieck
    Jan 11 at 13:16











  • @EugenRieck: Yes I have tried, it comes back saying "mount: can't find /etc in /proc/mounts"

    – kman
    Jan 11 at 13:39













  • Please ask a specific question. "Any suggestions?" is not specific. My answer assumes the real question is "why?" See How to Ask.

    – Kamil Maciorowski
    Jan 11 at 14:04














0












0








0








I am using embedded linux (built using LTIB).



I am unable to make changes to /etc directory. Basically I want to add a start-up script to /etc/rc.d/init.d



/etc/ seems to be mounted as rwfs



output of df -h:



Filesystem                Size      Used Available Use% Mounted on
/dev/root 3.0G 376.9M 2.4G 13% /
tmpfs 424.2M 36.0K 424.1M 0% /dev
shm 424.2M 0 424.2M 0% /dev/shm
rwfs 376.0M 5.1M 370.9M 1% /mnt/rwfs
rwfs 376.0M 5.1M 370.9M 1% /tmp
rwfs 376.0M 5.1M 370.9M 1% /var
rwfs 376.0M 5.1M 370.9M 1% /etc


I have tried :



umount /etc/ 
touch /etc/dummy --> just for the sake of checking
reboot
(after boot-up)
ls -lth /etc/dummy ---> file is missing


This is an image which I boot from an SD card. On one of the SD cards, after I did the above umount /etc, and then placed a dummy file as mentioned above, on the next boot as expected /etc goes back to be mounted as tmpfs but the dummy file was available. But on another SD card when I try the same, dummy file is not available.



Any suggestions?



Output of mount (before using umount /etc/):



root@freescale /etc$ mount
rootfs on / type rootfs (rw)
/dev/root on / type ext2 (rw,relatime,errors=continue)
proc on /proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
shm on /dev/shm type tmpfs (rw,relatime)
rwfs on /mnt/rwfs type tmpfs (rw,relatime,size=385024k)
rwfs on /tmp type tmpfs (rw,relatime,size=385024k)
rwfs on /var type tmpfs (rw,relatime,size=385024k)
rwfs on /etc type tmpfs (rw,relatime,size=385024k)


Output of mount (after umount /etc):



rootfs on / type rootfs (rw)
/dev/root on / type ext2 (rw,relatime,errors=continue)
proc on /proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
shm on /dev/shm type tmpfs (rw,relatime)
rwfs on /mnt/rwfs type tmpfs (rw,relatime,size=385024k)
rwfs on /tmp type tmpfs (rw,relatime,size=385024k)
rwfs on /var type tmpfs (rw,relatime,size=385024k)









share|improve this question
















I am using embedded linux (built using LTIB).



I am unable to make changes to /etc directory. Basically I want to add a start-up script to /etc/rc.d/init.d



/etc/ seems to be mounted as rwfs



output of df -h:



Filesystem                Size      Used Available Use% Mounted on
/dev/root 3.0G 376.9M 2.4G 13% /
tmpfs 424.2M 36.0K 424.1M 0% /dev
shm 424.2M 0 424.2M 0% /dev/shm
rwfs 376.0M 5.1M 370.9M 1% /mnt/rwfs
rwfs 376.0M 5.1M 370.9M 1% /tmp
rwfs 376.0M 5.1M 370.9M 1% /var
rwfs 376.0M 5.1M 370.9M 1% /etc


I have tried :



umount /etc/ 
touch /etc/dummy --> just for the sake of checking
reboot
(after boot-up)
ls -lth /etc/dummy ---> file is missing


This is an image which I boot from an SD card. On one of the SD cards, after I did the above umount /etc, and then placed a dummy file as mentioned above, on the next boot as expected /etc goes back to be mounted as tmpfs but the dummy file was available. But on another SD card when I try the same, dummy file is not available.



Any suggestions?



Output of mount (before using umount /etc/):



root@freescale /etc$ mount
rootfs on / type rootfs (rw)
/dev/root on / type ext2 (rw,relatime,errors=continue)
proc on /proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
shm on /dev/shm type tmpfs (rw,relatime)
rwfs on /mnt/rwfs type tmpfs (rw,relatime,size=385024k)
rwfs on /tmp type tmpfs (rw,relatime,size=385024k)
rwfs on /var type tmpfs (rw,relatime,size=385024k)
rwfs on /etc type tmpfs (rw,relatime,size=385024k)


Output of mount (after umount /etc):



rootfs on / type rootfs (rw)
/dev/root on / type ext2 (rw,relatime,errors=continue)
proc on /proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
shm on /dev/shm type tmpfs (rw,relatime)
rwfs on /mnt/rwfs type tmpfs (rw,relatime,size=385024k)
rwfs on /tmp type tmpfs (rw,relatime,size=385024k)
rwfs on /var type tmpfs (rw,relatime,size=385024k)






linux filesystems mount






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 11 at 15:26









Mr Shunz

1,80711917




1,80711917










asked Jan 11 at 13:10









kman kman

12




12








  • 1





    have you tried mount -o remount,rw /etc?

    – Eugen Rieck
    Jan 11 at 13:16











  • @EugenRieck: Yes I have tried, it comes back saying "mount: can't find /etc in /proc/mounts"

    – kman
    Jan 11 at 13:39













  • Please ask a specific question. "Any suggestions?" is not specific. My answer assumes the real question is "why?" See How to Ask.

    – Kamil Maciorowski
    Jan 11 at 14:04














  • 1





    have you tried mount -o remount,rw /etc?

    – Eugen Rieck
    Jan 11 at 13:16











  • @EugenRieck: Yes I have tried, it comes back saying "mount: can't find /etc in /proc/mounts"

    – kman
    Jan 11 at 13:39













  • Please ask a specific question. "Any suggestions?" is not specific. My answer assumes the real question is "why?" See How to Ask.

    – Kamil Maciorowski
    Jan 11 at 14:04








1




1





have you tried mount -o remount,rw /etc?

– Eugen Rieck
Jan 11 at 13:16





have you tried mount -o remount,rw /etc?

– Eugen Rieck
Jan 11 at 13:16













@EugenRieck: Yes I have tried, it comes back saying "mount: can't find /etc in /proc/mounts"

– kman
Jan 11 at 13:39







@EugenRieck: Yes I have tried, it comes back saying "mount: can't find /etc in /proc/mounts"

– kman
Jan 11 at 13:39















Please ask a specific question. "Any suggestions?" is not specific. My answer assumes the real question is "why?" See How to Ask.

– Kamil Maciorowski
Jan 11 at 14:04





Please ask a specific question. "Any suggestions?" is not specific. My answer assumes the real question is "why?" See How to Ask.

– Kamil Maciorowski
Jan 11 at 14:04










1 Answer
1






active

oldest

votes


















2














This line from the output of mount



rwfs on /etc type tmpfs (rw,relatime,size=385024k)


says /etc is in fact tmpfs. Now from Wikipedia:




tmpfs is a common name for a temporary file storage facility on many Unix-like operating systems. It is intended to appear as a mounted file system, but stored in volatile memory instead of a persistent storage device.




And




Everything stored in tmpfs is temporary in the sense that no files will be created on the hard drive; however, swap space is used as backing store in case of low memory situations. On reboot, everything in tmpfs will be lost.




This is exactly what happens in your case.



Embedded systems use tmpfs for /etc and few other directories to make them writable for any program that needs it, but in the same time




  • to avoid filesystem corruption when any writing is in progress and the device is powered off by pulling the plug;

  • to avoid OS corruption when you do something wrong by playing in the console.


"Big" systems may be rescued by booting from USB, running fsck etc. Here it's highly desirable to just restart with verified configuration.



In general the OS may provide a way to commit changes, write them to a non-volatile memory from where they will be restored at the next reboot. Or it may neither provide a way nor such restoration process at all.






share|improve this answer


























  • this is an image which I boot from an sd card. On one of the sd card, after I did 'umount /etc', and then placed a dummy file inside it. On the next boot 'etc' goes back to be mounted as tmpfs but the dummy file was available. But on another sd card when I try the same, it doesn't work.

    – kman
    Jan 11 at 13:54











  • @kman What is your point? Note I don't know details of your embedded system, e.g. how it populates /etc after mounting tmpfs there.

    – Kamil Maciorowski
    Jan 11 at 14:00











  • Just added my above comment to the description above - just to ensure I have described the problem fully. What is not clear at this point is - as you say "In general the OS may provide a way to commit changes, write them to a non-volatile memory from where they will be restored at the next reboot. Or it may neither provide a way nor such restoration process at all." --- how is this working on one sd card but not on the other.

    – kman
    Jan 11 at 14:00











  • @kman My bet is you did something in a different way.

    – Kamil Maciorowski
    Jan 11 at 14:05











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1393161%2funable-to-make-changes-to-etc%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









2














This line from the output of mount



rwfs on /etc type tmpfs (rw,relatime,size=385024k)


says /etc is in fact tmpfs. Now from Wikipedia:




tmpfs is a common name for a temporary file storage facility on many Unix-like operating systems. It is intended to appear as a mounted file system, but stored in volatile memory instead of a persistent storage device.




And




Everything stored in tmpfs is temporary in the sense that no files will be created on the hard drive; however, swap space is used as backing store in case of low memory situations. On reboot, everything in tmpfs will be lost.




This is exactly what happens in your case.



Embedded systems use tmpfs for /etc and few other directories to make them writable for any program that needs it, but in the same time




  • to avoid filesystem corruption when any writing is in progress and the device is powered off by pulling the plug;

  • to avoid OS corruption when you do something wrong by playing in the console.


"Big" systems may be rescued by booting from USB, running fsck etc. Here it's highly desirable to just restart with verified configuration.



In general the OS may provide a way to commit changes, write them to a non-volatile memory from where they will be restored at the next reboot. Or it may neither provide a way nor such restoration process at all.






share|improve this answer


























  • this is an image which I boot from an sd card. On one of the sd card, after I did 'umount /etc', and then placed a dummy file inside it. On the next boot 'etc' goes back to be mounted as tmpfs but the dummy file was available. But on another sd card when I try the same, it doesn't work.

    – kman
    Jan 11 at 13:54











  • @kman What is your point? Note I don't know details of your embedded system, e.g. how it populates /etc after mounting tmpfs there.

    – Kamil Maciorowski
    Jan 11 at 14:00











  • Just added my above comment to the description above - just to ensure I have described the problem fully. What is not clear at this point is - as you say "In general the OS may provide a way to commit changes, write them to a non-volatile memory from where they will be restored at the next reboot. Or it may neither provide a way nor such restoration process at all." --- how is this working on one sd card but not on the other.

    – kman
    Jan 11 at 14:00











  • @kman My bet is you did something in a different way.

    – Kamil Maciorowski
    Jan 11 at 14:05
















2














This line from the output of mount



rwfs on /etc type tmpfs (rw,relatime,size=385024k)


says /etc is in fact tmpfs. Now from Wikipedia:




tmpfs is a common name for a temporary file storage facility on many Unix-like operating systems. It is intended to appear as a mounted file system, but stored in volatile memory instead of a persistent storage device.




And




Everything stored in tmpfs is temporary in the sense that no files will be created on the hard drive; however, swap space is used as backing store in case of low memory situations. On reboot, everything in tmpfs will be lost.




This is exactly what happens in your case.



Embedded systems use tmpfs for /etc and few other directories to make them writable for any program that needs it, but in the same time




  • to avoid filesystem corruption when any writing is in progress and the device is powered off by pulling the plug;

  • to avoid OS corruption when you do something wrong by playing in the console.


"Big" systems may be rescued by booting from USB, running fsck etc. Here it's highly desirable to just restart with verified configuration.



In general the OS may provide a way to commit changes, write them to a non-volatile memory from where they will be restored at the next reboot. Or it may neither provide a way nor such restoration process at all.






share|improve this answer


























  • this is an image which I boot from an sd card. On one of the sd card, after I did 'umount /etc', and then placed a dummy file inside it. On the next boot 'etc' goes back to be mounted as tmpfs but the dummy file was available. But on another sd card when I try the same, it doesn't work.

    – kman
    Jan 11 at 13:54











  • @kman What is your point? Note I don't know details of your embedded system, e.g. how it populates /etc after mounting tmpfs there.

    – Kamil Maciorowski
    Jan 11 at 14:00











  • Just added my above comment to the description above - just to ensure I have described the problem fully. What is not clear at this point is - as you say "In general the OS may provide a way to commit changes, write them to a non-volatile memory from where they will be restored at the next reboot. Or it may neither provide a way nor such restoration process at all." --- how is this working on one sd card but not on the other.

    – kman
    Jan 11 at 14:00











  • @kman My bet is you did something in a different way.

    – Kamil Maciorowski
    Jan 11 at 14:05














2












2








2







This line from the output of mount



rwfs on /etc type tmpfs (rw,relatime,size=385024k)


says /etc is in fact tmpfs. Now from Wikipedia:




tmpfs is a common name for a temporary file storage facility on many Unix-like operating systems. It is intended to appear as a mounted file system, but stored in volatile memory instead of a persistent storage device.




And




Everything stored in tmpfs is temporary in the sense that no files will be created on the hard drive; however, swap space is used as backing store in case of low memory situations. On reboot, everything in tmpfs will be lost.




This is exactly what happens in your case.



Embedded systems use tmpfs for /etc and few other directories to make them writable for any program that needs it, but in the same time




  • to avoid filesystem corruption when any writing is in progress and the device is powered off by pulling the plug;

  • to avoid OS corruption when you do something wrong by playing in the console.


"Big" systems may be rescued by booting from USB, running fsck etc. Here it's highly desirable to just restart with verified configuration.



In general the OS may provide a way to commit changes, write them to a non-volatile memory from where they will be restored at the next reboot. Or it may neither provide a way nor such restoration process at all.






share|improve this answer















This line from the output of mount



rwfs on /etc type tmpfs (rw,relatime,size=385024k)


says /etc is in fact tmpfs. Now from Wikipedia:




tmpfs is a common name for a temporary file storage facility on many Unix-like operating systems. It is intended to appear as a mounted file system, but stored in volatile memory instead of a persistent storage device.




And




Everything stored in tmpfs is temporary in the sense that no files will be created on the hard drive; however, swap space is used as backing store in case of low memory situations. On reboot, everything in tmpfs will be lost.




This is exactly what happens in your case.



Embedded systems use tmpfs for /etc and few other directories to make them writable for any program that needs it, but in the same time




  • to avoid filesystem corruption when any writing is in progress and the device is powered off by pulling the plug;

  • to avoid OS corruption when you do something wrong by playing in the console.


"Big" systems may be rescued by booting from USB, running fsck etc. Here it's highly desirable to just restart with verified configuration.



In general the OS may provide a way to commit changes, write them to a non-volatile memory from where they will be restored at the next reboot. Or it may neither provide a way nor such restoration process at all.







share|improve this answer














share|improve this answer



share|improve this answer








edited Jan 11 at 13:55

























answered Jan 11 at 13:40









Kamil MaciorowskiKamil Maciorowski

27.2k155982




27.2k155982













  • this is an image which I boot from an sd card. On one of the sd card, after I did 'umount /etc', and then placed a dummy file inside it. On the next boot 'etc' goes back to be mounted as tmpfs but the dummy file was available. But on another sd card when I try the same, it doesn't work.

    – kman
    Jan 11 at 13:54











  • @kman What is your point? Note I don't know details of your embedded system, e.g. how it populates /etc after mounting tmpfs there.

    – Kamil Maciorowski
    Jan 11 at 14:00











  • Just added my above comment to the description above - just to ensure I have described the problem fully. What is not clear at this point is - as you say "In general the OS may provide a way to commit changes, write them to a non-volatile memory from where they will be restored at the next reboot. Or it may neither provide a way nor such restoration process at all." --- how is this working on one sd card but not on the other.

    – kman
    Jan 11 at 14:00











  • @kman My bet is you did something in a different way.

    – Kamil Maciorowski
    Jan 11 at 14:05



















  • this is an image which I boot from an sd card. On one of the sd card, after I did 'umount /etc', and then placed a dummy file inside it. On the next boot 'etc' goes back to be mounted as tmpfs but the dummy file was available. But on another sd card when I try the same, it doesn't work.

    – kman
    Jan 11 at 13:54











  • @kman What is your point? Note I don't know details of your embedded system, e.g. how it populates /etc after mounting tmpfs there.

    – Kamil Maciorowski
    Jan 11 at 14:00











  • Just added my above comment to the description above - just to ensure I have described the problem fully. What is not clear at this point is - as you say "In general the OS may provide a way to commit changes, write them to a non-volatile memory from where they will be restored at the next reboot. Or it may neither provide a way nor such restoration process at all." --- how is this working on one sd card but not on the other.

    – kman
    Jan 11 at 14:00











  • @kman My bet is you did something in a different way.

    – Kamil Maciorowski
    Jan 11 at 14:05

















this is an image which I boot from an sd card. On one of the sd card, after I did 'umount /etc', and then placed a dummy file inside it. On the next boot 'etc' goes back to be mounted as tmpfs but the dummy file was available. But on another sd card when I try the same, it doesn't work.

– kman
Jan 11 at 13:54





this is an image which I boot from an sd card. On one of the sd card, after I did 'umount /etc', and then placed a dummy file inside it. On the next boot 'etc' goes back to be mounted as tmpfs but the dummy file was available. But on another sd card when I try the same, it doesn't work.

– kman
Jan 11 at 13:54













@kman What is your point? Note I don't know details of your embedded system, e.g. how it populates /etc after mounting tmpfs there.

– Kamil Maciorowski
Jan 11 at 14:00





@kman What is your point? Note I don't know details of your embedded system, e.g. how it populates /etc after mounting tmpfs there.

– Kamil Maciorowski
Jan 11 at 14:00













Just added my above comment to the description above - just to ensure I have described the problem fully. What is not clear at this point is - as you say "In general the OS may provide a way to commit changes, write them to a non-volatile memory from where they will be restored at the next reboot. Or it may neither provide a way nor such restoration process at all." --- how is this working on one sd card but not on the other.

– kman
Jan 11 at 14:00





Just added my above comment to the description above - just to ensure I have described the problem fully. What is not clear at this point is - as you say "In general the OS may provide a way to commit changes, write them to a non-volatile memory from where they will be restored at the next reboot. Or it may neither provide a way nor such restoration process at all." --- how is this working on one sd card but not on the other.

– kman
Jan 11 at 14:00













@kman My bet is you did something in a different way.

– Kamil Maciorowski
Jan 11 at 14:05





@kman My bet is you did something in a different way.

– Kamil Maciorowski
Jan 11 at 14:05


















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1393161%2funable-to-make-changes-to-etc%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Plaza Victoria

Brian Clough

Cáceres