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!
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It appears that ls -l shows me the last modification date.
Is there a way to see the creation date of a file or directory?
Is this info stored in the file system?
If so, how does one access it?
Ive read 'man ls' and 'info ls' but they don't seem to tell
Umm, I hate to break it to you, but as far as I know, you can't it does'nt seem to be stored anywhere. There is a last-modified time (shown by "ls -l"), a last-accessed time (shown by "ls -lu") and an inode change time (shown by "ls -lc")....sorry...
The ext2/ext3 filesystems don't store the creation time of a file, but the last time at which the inode of the file has been updated. This is called "change time" usually named ctime. It reflects the time of creation until the access permissions or the ownership are not changed. For this reason you cannot trust this timestamp to reveal the creation date of a file. On the contrary the ext4 filesystem adds support for the storage of the true creation date, but as far as I know the libraries and utilities in Linux have not been updated in order to use it.
Regarding your question, you can visualize the "change time" using the stat command or the option -c of ls, e.g.
Colucix and Thor - thanks guys - in my case I took the defaults when I got onto Fedora f12 and have the logical volume file system (which I would not have picked if I had known) but anyway it is ext4 - thus presumably if I look up the file formats I could write a little utility to see the cration date?
Since you guys obviously know your stuff - maybe you can answer this one
Fedora f16 takes 1 minute longer to boot than my f14 - I see that in the process it created or modifies files and folders as follows:
tmpfs results in creating or updating 13 items with 671.1 MB
sysfs results in creating or updating 20,047 items with 192.5 Mb
proc results in creating or updating 39294 items
I gotta believe this is overkill for a single user desktop system - but dont know where to modify the startup
are there command files that control what happens in startup?
are there command files that control what happens in startup?
on Arch, these are located in /etc/rc.d/ the script /etc/rc.conf coverns most stuff...
By the way, careful what you wish for if you sc**w up startup scripts, you can basically end up with a dead system make backups of any and evertything you touch...
Maybe some info of the wiki can help...
One minute? That's still okay...do realise fedora keeps getting more complex. It's philosophy is different of, say, Arch, where the user controls the show...
Thor
Edit - it may do a fsck on bootup...that takes time too...
Last edited by ButterflyMelissa; 09-27-2012 at 04:07 PM.
on Arch, these are located in /etc/rc.d/ the script /etc/rc.conf coverns most stuff...
By the way, careful what you wish for if you sc**w up startup scripts, you can basically end up with a dead system make backups of any and evertything you touch...
Maybe some info of the wiki can help...
One minute? That's still okay...do realise fedora keeps getting more complex. It's philosophy is different of, say, Arch, where the user controls the show...
Thor
Edit - it may do a fsck on bootup...that takes time too...
Super - needless to say I have a backup and a backup of the backup!
Thanks - will look into it
Super - needless to say I have a backup and a backup of the backup!
Wow, we dont need to tell you this! You're an example of how it has to be done, it seems. Most disasters can be avoided this way. I'll follow this thread, maybe I can learn something here
Wow, we dont need to tell you this! You're an example of how it has to be done, it seems. Most disasters can be avoided this way. I'll follow this thread, maybe I can learn something here
Thor
Hi THor
I occurred to me to search the web and I found this - out of date but pretty detailed - looks like a good starting point
Umm, please tap me on the head ...this is the very first page (a long while ago) I found and learned about bootup...I should have given you this URL instead...I need to re-organise my bookmarks. Dated, perhaps, educational, yes.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.