Entries

The following is a list of entries by command/concept:

9 Responses to Entries

  1. Tina says:

    Is there a RSS feed for the videos?
    Great site.

  2. Javafant says:

    First of all I want to thank you for your useful posts. I would really love to see an episode on tar. In my opinion it’s an important command, but it’s difficult to learn.

  3. Toby says:

    Just wanted to say cheers for these Dann. I’ve been slowly but surely getting to grips with Linux over the last year or so, and have found these tutorials, as well as the podcasts you contribute to, to be totally invaluable in expanding my knowledge.
    Your an extremely kind and thoughtful man to give away your time and knowledge so freely. Very inspiring – please keep up the good work. Hopefully one day I will be accomplished enough to pay the favour forward, and thus perpetuate the wonderful spirit and philosophy of FLOSS that you so humbly embody 🙂
    P.S. Although not strictly LITS related, an extension to your HPR series on the linux boot process covering systemd would be gratefully appreciated!

    • dannSWashko says:

      Thanks for the feedback. I’ve been thinking about continuing on with the HPR boot series, but the time….

  4. I’ve really enjoyed listening to all these episodes. I’ve been using Linux/Unix for nearly 30 years (yikes!) and am still learning new tricks from you. factor and seq, who knew? My bash scripts can be simplified now.

    My one dangling question from an earlier episode is, what is the use case for a hard link? I see hard-links sometimes, but can’t think of an example they would be preferable to a sym link.

    • dannSWashko says:

      Here is a decent explanation to your question:

      http://serverfault.com/questions/122364/linux-best-practices-for-hard-linking

      Off the cuff – backups, content versioning software. Recall that unlike a symlink, a hard link shares the same innode and link to the data as the master but has a different file name or entry in the file table. Thus, if you delete the original file, the innode and data will still exist because the hard link still exists. That information is not removed until all link counter for the innode reaches zero. That is very different from a symbolic link where it is just a pointer to the file, it does not share the same innode. Deleting the original file does not preserve the innode or data if there is a symlink to the original file.

Leave a Reply

Your email address will not be published. Required fields are marked *

Social Widgets powered by AB-WebLog.com.