Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hi, I have a network attached server (zyxel NSA310) and it seems that when I change some files after restart they disappear. Now I would like to know how can I learn which are the folders where if I change files they won't survive on restart (on linux in general). As far as I understand the lines below containing tmpfs, sysdisk.img (this one I don't understand why) are mounts where changes won't survive. I also noticed that changes to /var/spool/cron/crontabs/root are lost on restart and I don't understand why; looking below it seems to me that /var/spool/cron/crontabs shouldn't be a volatile folder.
root@nsa310:~# mount -l
rootfs on / type rootfs (rw)
/proc on /proc type proc (rw,relatime)
/sys on /sys type sysfs (rw,relatime)
none on /proc/bus/usb type usbfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
/dev/mtdblock6 on /zyxel/mnt/nand type yaffs2 (ro,relatime)
/dev/sda1 on /zyxel/mnt/sysdisk type ext2 (ro,relatime,errors=continue)
/zyxel/mnt/sysdisk/sysdisk.img on /ram_bin type ext2 (ro,relatime,errors=continue)
/zyxel/mnt/sysdisk/sysdisk.img on /usr type ext2 (ro,relatime,errors=continue)
/zyxel/mnt/sysdisk/sysdisk.img on /lib/security type ext2 (ro,relatime,errors=continue)
/zyxel/mnt/sysdisk/sysdisk.img on /lib/modules type ext2 (ro,relatime,errors=continue)
/dev/ram0 on /tmp/tmpfs type tmpfs (rw,relatime,size=5120k)
/dev/ram0 on /usr/local/etc type tmpfs (rw,relatime,size=5120k)
/dev/ram0 on /usr/local/var type tmpfs (rw,relatime,size=5120k)
/dev/mtdblock4 on /etc/zyxel type yaffs2 (rw,relatime)
/dev/md0 on /i-data/949018fd type ext4 (rw,noatime,barrier=0,data=writeback,usrquota)
/dev/sdb1 on /e-data/806e0d7ac6c3709c857f0734b8572729 type tntfs (rw,relatime,uid=99,gid=0,umask=00,nls=utf8,case_sensitive,nocache,errors=continue,mft_zone_multipli er=1) [Expansion Drive]
/dev/md0 on /usr/local/zy-pkgs type ext4 (rw,noatime,barrier=0,data=writeback,usrquota)
/dev/md0 on /etc/zyxel/zy-pkgs type ext4 (rw,noatime,barrier=0,data=writeback,usrquota)
/dev/md0 on /usr/local/apache/htdocs/zyxel/pkg type ext4 (rw,noatime,barrier=0,data=writeback,usrquota)
/dev/md0 on /usr/local/apache/web_framework/data/cache type ext4 (rw,noatime,barrier=0,data=writeback,usrquota)
/dev/mtdblock4 on /usr/local/apache/web_framework/data/config type yaffs2 (rw,relatime)
Many embedded systems load the entire operating system into RAM so any changes must be specifically written to non volatile memory. In general with most desktop and servers all data is stored on a hard drive. I am unfamiliar with the zyxel NAS devices so I can not say exactly how it works.