Compression – mintCast https://mintcast.org The podcast by the Linux Mint community for all users of Linux Wed, 17 Mar 2021 03:53:36 +0000 en-US hourly 1 https://wordpress.org/?v=7.1 https://mintcast.org/wp-content/uploads/2020/03/cropped-small-logo-32x32.png Compression – mintCast https://mintcast.org 32 32 mintCast false episodic CC-BY-SA 4.0 CC-BY-SA 4.0 podcast Compression – mintCast https://mintcast.org/wp-content/uploads/2020/03/big-logo-1600.png https://mintcast.org TV-G 164426984 mintCast 356.5 – Itty Bitty Living Space (mp3) https://mintcast.org/mintcast-356-5-itty-bitty-living-space-mp3/ Wed, 17 Mar 2021 03:52:54 +0000 http://mintcast.org/?p=4970 And finally, the feedback and a couple suggestions
Download
]]> Download

1:57 Linux Innards
30:28 Vibrations from the Ether
55:19 Check This Out
59:22 Announcements & Outro

In our Innards section, we talk Compression

And finally, the feedback and a couple suggestions

LINUX INNARDS:

Compression

  • Joe
    • I tried to use the built in tool to compress my home drive but kept running into permissions problems even as root. 
    • So I used tar.gz in order to test the compression on my Downloads folder which started out as 58.8 gb and ended up at like 55 gb so not much savings in space
  • TonyH  
    • I ran .tar.gz on my desktop folder which was 40.3Gb I backed this folder up to one of my external 4Tb drives I use for backup and storage and after completion the new folder was 33.3Gb so a saving of 7Gb just on this one folder, so if space was an issue this would be a good way to backup folders and save some space. Just for comparison, 7Gb is larger than the 6Gb HDD I had in my first Windows PC back in late 1998 and that was a decent amount of storage for the time, lol.  
  • Moss
    • I keep most of my files most people keep in Home on an external drive, so there wasn’t much in my Home folder to compress. In fact, my Home folder was only 1.5 Gb; running compression, the resulting files were each 1.7 Gb. I ran both .tar.gz and .tar.7z for comparison with no difference. Maybe I should check compression on my external, but I’m not sure I have room anywhere for a file which would hold all that. /dev/sdb is a 512 Gb drive with only 145 Gb free…
  • Josh
    • I mainly tested my compression on my .img backups of my internal nvme drive with about 506 GB of data on it using dd and partclone to image the disk and pigz to compress. I tried both 7z and gzip but for this task both of them take way too long at over 5 hours estimated time. 
    • Rescuezilla won the speed of compression coming in at 55 minutes. The compressed size was tied with Partclone+pigz at 383GB. I am unsure of the exact command it uses.
    • Partclone + pigz came in second at 57 minutes. The compressed size as I have stated earlier is exactly the same as Rescuzilla at 383GB. The command I used to achieve this was.
      • partclone.ntfs -c -s /dev/nvme0n1p3 | pigz -9 > /mnt/backup/backup.img.gz
    • dd + pigz came in 3rd at 1H 38M. The compressed size was a little larger than the other two at 387GB and the command I used to achieve all this was.
      • dd if=/dev/nvme0n1p3 | pv | pigz -9 > /mnt/backup/backup.img.gz
    • As I said before 7z took too long. I am not sure why this is but it is supposed to be multithreaded but when looking at htop only one thread was in use. In a later test of compressing a folder I had it actually did use all my cores to compress and the time it took was not that long. I cannot use that to compare against my other findings because it was not the same file I was compressing but I think it would perform close to the others.
  • Leo
    • For long compressions, install and use progress to monitor that state of tar.
      • sudo apt install progress
      • progress -m
      • It won’t tell you the status of the whole compression process, but will tell you the status of each file, at least letting you know that it’s working and will exit automatically when done.
    • I currently have a 1.2GB home folder on this machine. Mostly downloaded files like a Lineage image, nyquist plugins for audacity, and a little more than half of the size is pictures.
      • xz
        • tar -cJf /media/leo/Ventoy/Backup/home.tar.xz ~/*
        • Done in about 5 minutes
        • 2nd Best compression: 1,128,815,932 bytes
      • gz
        • tar -czf /media/leo/Ventoy/Backup/home.tar.gz ~/*
        • Done in 1 minute
        • Worst compression: 1,143,787,050 bytes
      • bz2
        • tar -cjf /media/leo/Ventoy/Backup/home.tar.bz2 ~/*
        • Done in 2.5 minutes
        • Middling compression: 1,140,996,181 bytes
      • 7z
        • 7z a /media/leo/Ventoy/Backup/home.7z ~/*
        • Done in 45 seconds
        • Best compression: 1,127,056,501 bytes
    • All the algorithms seemed to have saved me about 10% on the backup.
    • Josh and I have been playing around with pigz, which is a rewrite of gzip to include multi-core CPU support. To do the same backup as above:
      • sudo apt install pigz
      • tar –use-compress-program=”pigz –best –recursive” -cf /media/leo/Ventoy/Backup/home.tar.gz ~/*
      • Done in about 30 seconds
      • Ever so slightly worse compression than gz? Approximately 1MB diff.
        • 1,144,479,482 bytes

VIBRATIONS FROM THE ETHER: 

Leo

    • accounts-daemon.service
      • It can safely be disabled, because dbus will start it when needed.
      • It’s used mostly for graphical apps that handle users.
      • Masking will break these apps.
    • acct.service
      • It can safely be disabled if you don’t care about account and session usage stats.
      • acct tracks things like how long you’ve been logged in, which commands you’ve run, etc.
      • Masking won’t likely break anything visible.
    • acpid.service
      • Understand before disabling
      • This one handles hardware actions. Plugging in headphones, brightness buttons on the laptop, etc.
      • Masking may break these.
    • alsa-state.service
      • Understand before disabling
      • This DIEMON will monitor the state and settings of your sound card. The volume settings, mute, sound card selection, etc.
      • Masking may force ALSA to forget these things.
    • anacron.service
      • Disabling will prevent anacron from running timed scripts.
      • Anacron is like lazy cron. If you have scripts run by anacron, they will fail to execute.
  • Mike F

CHECK THIS OUT!

  • Leo
    • Can you beat 1024 bytes of code in chess? Kilobyte’s Gambit
    • Noti notifies you of completed commands in Telegram
  • Bo – NoiseTorch is a real-time microphone noise suppression application for Linux
  • Moss
    • JingOS, a phone/tablet Linux OS which aims to replicate iOS, announced they will not release version 0.7 and will instead release version 0.8 on March 31, claiming it will be a full-featured Linux, and in the future will be releasing as OTA. It looks great, hope they can pull it off.
    • For all you Mandrakers out there, Rosa Fresh R11 is also out.This fork is by the Russians who were co-developers of the last official version of Mandriva, and is the base for OpenMandriva Lx. I do not myself recommend Rosa. If you’re more of an Enterprise user, Rosa Enterprise Server is a fork of RHEL.
    • Listener Dylan Burger asked the Distrohoppers’ team, “What one feature would you ask to be added to your daily driver distro?” We’re saving that topic for a future show.

ANNOUNCEMENTS: 

Our next episode will be at 2 pm Central US time on March 21, 2021.

Get the show time converted to your time zone!

Wrap-up:

Before we leave, we want to make sure to acknowledge some of the people who make mintCast possible …

  • Owen Peery for our audio editing, Josh Lowe for all his work on the website, Hobstar for our logo, and Londoner for our time sync
  • Bytemark Hosting for hosting mintcast.org and our Mumble server
  • Archive.org for hosting our audio files
  • HPR for our backup Mumble room
  • The Linux Mint development team for the fine distro we love to talk about <Thanks, Clem!>
]]> full 4970 mintCast 356.5 – Itty Bitty Living Space https://mintcast.org/mintcast-356-5-itty-bitty-living-space/ Wed, 17 Mar 2021 03:40:08 +0000 http://mintcast.org/?p=4966 And finally, the feedback and a couple suggestions
Download
]]> Download

1:57 Linux Innards
30:28 Vibrations from the Ether
55:19 Check This Out
59:22 Announcements & Outro

In our Innards section, we talk Compression

And finally, the feedback and a couple suggestions

LINUX INNARDS:

Compression

  • Joe
    • I tried to use the built in tool to compress my home drive but kept running into permissions problems even as root. 
    • So I used tar.gz in order to test the compression on my Downloads folder which started out as 58.8 gb and ended up at like 55 gb so not much savings in space
  • TonyH  
    • I ran .tar.gz on my desktop folder which was 40.3Gb I backed this folder up to one of my external 4Tb drives I use for backup and storage and after completion the new folder was 33.3Gb so a saving of 7Gb just on this one folder, so if space was an issue this would be a good way to backup folders and save some space. Just for comparison, 7Gb is larger than the 6Gb HDD I had in my first Windows PC back in late 1998 and that was a decent amount of storage for the time, lol.  
  • Moss
    • I keep most of my files most people keep in Home on an external drive, so there wasn’t much in my Home folder to compress. In fact, my Home folder was only 1.5 Gb; running compression, the resulting files were each 1.7 Gb. I ran both .tar.gz and .tar.7z for comparison with no difference. Maybe I should check compression on my external, but I’m not sure I have room anywhere for a file which would hold all that. /dev/sdb is a 512 Gb drive with only 145 Gb free…
  • Josh
    • I mainly tested my compression on my .img backups of my internal nvme drive with about 506 GB of data on it using dd and partclone to image the disk and pigz to compress. I tried both 7z and gzip but for this task both of them take way too long at over 5 hours estimated time. 
    • Rescuezilla won the speed of compression coming in at 55 minutes. The compressed size was tied with Partclone+pigz at 383GB. I am unsure of the exact command it uses.
    • Partclone + pigz came in second at 57 minutes. The compressed size as I have stated earlier is exactly the same as Rescuzilla at 383GB. The command I used to achieve this was.
      • partclone.ntfs -c -s /dev/nvme0n1p3 | pigz -9 > /mnt/backup/backup.img.gz
    • dd + pigz came in 3rd at 1H 38M. The compressed size was a little larger than the other two at 387GB and the command I used to achieve all this was.
      • dd if=/dev/nvme0n1p3 | pv | pigz -9 > /mnt/backup/backup.img.gz
    • As I said before 7z took too long. I am not sure why this is but it is supposed to be multithreaded but when looking at htop only one thread was in use. In a later test of compressing a folder I had it actually did use all my cores to compress and the time it took was not that long. I cannot use that to compare against my other findings because it was not the same file I was compressing but I think it would perform close to the others.
  • Leo
    • For long compressions, install and use progress to monitor that state of tar.
      • sudo apt install progress
      • progress -m
      • It won’t tell you the status of the whole compression process, but will tell you the status of each file, at least letting you know that it’s working and will exit automatically when done.
    • I currently have a 1.2GB home folder on this machine. Mostly downloaded files like a Lineage image, nyquist plugins for audacity, and a little more than half of the size is pictures.
      • xz
        • tar -cJf /media/leo/Ventoy/Backup/home.tar.xz ~/*
        • Done in about 5 minutes
        • 2nd Best compression: 1,128,815,932 bytes
      • gz
        • tar -czf /media/leo/Ventoy/Backup/home.tar.gz ~/*
        • Done in 1 minute
        • Worst compression: 1,143,787,050 bytes
      • bz2
        • tar -cjf /media/leo/Ventoy/Backup/home.tar.bz2 ~/*
        • Done in 2.5 minutes
        • Middling compression: 1,140,996,181 bytes
      • 7z
        • 7z a /media/leo/Ventoy/Backup/home.7z ~/*
        • Done in 45 seconds
        • Best compression: 1,127,056,501 bytes
    • All the algorithms seemed to have saved me about 10% on the backup.
    • Josh and I have been playing around with pigz, which is a rewrite of gzip to include multi-core CPU support. To do the same backup as above:
      • sudo apt install pigz
      • tar –use-compress-program=”pigz –best –recursive” -cf /media/leo/Ventoy/Backup/home.tar.gz ~/*
      • Done in about 30 seconds
      • Ever so slightly worse compression than gz? Approximately 1MB diff.
        • 1,144,479,482 bytes

VIBRATIONS FROM THE ETHER: 

Leo

    • accounts-daemon.service
      • It can safely be disabled, because dbus will start it when needed.
      • It’s used mostly for graphical apps that handle users.
      • Masking will break these apps.
    • acct.service
      • It can safely be disabled if you don’t care about account and session usage stats.
      • acct tracks things like how long you’ve been logged in, which commands you’ve run, etc.
      • Masking won’t likely break anything visible.
    • acpid.service
      • Understand before disabling
      • This one handles hardware actions. Plugging in headphones, brightness buttons on the laptop, etc.
      • Masking may break these.
    • alsa-state.service
      • Understand before disabling
      • This DIEMON will monitor the state and settings of your sound card. The volume settings, mute, sound card selection, etc.
      • Masking may force ALSA to forget these things.
    • anacron.service
      • Disabling will prevent anacron from running timed scripts.
      • Anacron is like lazy cron. If you have scripts run by anacron, they will fail to execute.
  • Mike F

CHECK THIS OUT!

  • Leo
    • Can you beat 1024 bytes of code in chess? Kilobyte’s Gambit
    • Noti notifies you of completed commands in Telegram
  • Bo – NoiseTorch is a real-time microphone noise suppression application for Linux
  • Moss
    • JingOS, a phone/tablet Linux OS which aims to replicate iOS, announced they will not release version 0.7 and will instead release version 0.8 on March 31, claiming it will be a full-featured Linux, and in the future will be releasing as OTA. It looks great, hope they can pull it off.
    • For all you Mandrakers out there, Rosa Fresh R11 is also out.This fork is by the Russians who were co-developers of the last official version of Mandriva, and is the base for OpenMandriva Lx. I do not myself recommend Rosa. If you’re more of an Enterprise user, Rosa Enterprise Server is a fork of RHEL.
    • Listener Dylan Burger asked the Distrohoppers’ team, “What one feature would you ask to be added to your daily driver distro?” We’re saving that topic for a future show.

ANNOUNCEMENTS: 

Our next episode will be at 2 pm Central US time on March 21, 2021.

Get the show time converted to your time zone!

Wrap-up:

Before we leave, we want to make sure to acknowledge some of the people who make mintCast possible …

  • Owen Peery for our audio editing, Josh Lowe for all his work on the website, Hobstar for our logo, and Londoner for our time sync
  • Bytemark Hosting for hosting mintcast.org and our Mumble server
  • Archive.org for hosting our audio files
  • HPR for our backup Mumble room
  • The Linux Mint development team for the fine distro we love to talk about <Thanks, Clem!>

]]> full 4966 mintCast 339.5 – ZFS Butter Recognize (mp3) https://mintcast.org/mintcast-339-5-zfs-butter-recognize-mp3/ Wed, 22 Jul 2020 04:46:11 +0000 http://mintcast.org/?p=4540 And finally, some feedback and a few suggestions
Download
]]>

Download

1:58 Innards
44:04 Feedback
1:16:41 Check This Out
1:20:58 Outro

In our Innards section, community member Joshua Hawk tries to convert us to unsalted BTRFS.

And finally, some feedback and a few suggestions

LINUX INNARDS: 

Joshua Hawk

When did you first learn about Linux?

When did you start using it as much as you do?

Btrfs – No Partitions Needed, with Joshua Hawk 

  • Features
    1. Copy on Write (CoW)
      1. Creates new files when storing data instead of overwriting current data.
      2. Necessary for snapshots
    2. Subvolumes
      1. Like a partition but has access to the entire space of the btrfs formatted disk.
      2. Also necessary for snapshots
      3. Can be interacted with either like a directory on a filesystem or like a separately mounted filesystem.
      4. Some subvolume commands
        1.  subvolume create [destination] <name of subvolume>
        2. subvolume delete [option] <subvolume name> [<subvolume inside subvolume>] 
        3. subvolume list [options] [–sort=rootid,gen,ogen,path] <path>
    3. Snapshots
      1. NOT BACKUPS! They are akin to Windows system restore points but far far superior. 
      2. Can be automated using snapper or timeshift.
      3. Is a subvolume itself that points to data and metadata in its parent subvolume.
      4. NOT BACKUPS! 
    4. File System Compression (ZLIB, LZO, ZSTD)
      1. Saves space sometimes up to 20%-30%
      2. Increases life of SSD’s due to significantly less writes
      3. ZSTD is flexible and configurable to your needs.
      4. Mounting a subvolume with the compression option won’t compress files currently on subvolume.
      5. To compress files already contained in a subvolume you must use the Defrag command with the -r option
    5. Checksumming
      1. Not Enabled on SSD’s by default due to the fact that ssd’s tend to just fail rather than die slowly. If you want this feature with ssd’s it is recommended to use 2 ssd’s in a RAID 1 Configuration.
      2. Enabled by default on HDD’s and when used with RAID 1 will checksum and self heal files that are corrupt. 
    6. SSD Awareness
      1. Disables file duplication to reduce writes
      2. TRIM/Discard to report free blocks for reuse
      3. Sends writes in clusters resulting in larger write operations and faster throughput. 
    7. Send/Receive of subvolume changes
      1. Can send and receive subvolumes and changes to those subvolumes over the network for backup operations.
    8. RAID Support
      1. RAID 0, 1, 5, 6, 10 support
      2. RAID 5 and 6 are experimental and are NOT recommended!
      3. RAID 0, 1, and 10 are production ready
      4. Can add and remove storage to RAID on the fly
  1. When to use btrfs
    1. Root Filesystem
    2. Redundant data storage (NAS)
    3. Laptops with SSDs
    4. Btrfs works for MOST filesystem cases
  1. When not to use btrfs
    1. Anything that does not need redundant data storage (video game data storage for example excluding game save data)
    2. Databases due to the slow nature of CoW.
  1. Issues with btrfs
    1. Will not mount a filesystem if errors are detected on disk. This can be corrected by using the scrub command 99% of the time.
    2. If connection is lost or computer/server loses power during some btrfs operations, may result in data corruption or file system issues.
    3. If snapshots are not being controlled by a script or a limit is not set the disk drive may fill up and cause issues. Can be corrected by deleting some snapshots.
    4. As stated before RAID 5/6  is experimental and has major issues. 
  1. Main Contributors to btrfs
    1. Facebook – Where Chris Mason the lead dev on btrfs is employed
    2. SUSE Linux Enterprise (SLE)
    3. Fujitsu
    4. Oracle
  1. Links to Good btrfs Content
    1. https://btrfs.wiki.kernel.org/index.php/Main_Page
    2. https://en.wikipedia.org/wiki/Btrfs
    3. btrfs: The Best Filesystem You’ve Never Heard Of – YouTube
    4. openSUSE Conference 2018 – btrfs is awesome, except when it isn’t – YouTube
    5. btrfs Tutorial | btrfs Filesystem | btrfs Subvolume and btrfs Snapshots – YouTube
    6. BTRFS Guide – Basic Commands, Snapshots, and RAID – Chris Titus Tech

VIBRATIONS FROM THE ETHER

  • Brad Alexander 
  • Brad’s addendum
  • Joe’s response
  • Henrik
  • Benjamin Moser
  • Jim Daldry
  • Bill Dietrich
  • John Wallis Saga Episode x+1

CHECK THIS OUT! 

Not Linux related at all, just a great poem about the current situation and how it may just be a positive thing. It is released under a Creative commons licence and called ‘What Happened when we all stopped’ by Tom & Bee Rivett-Carnac, very thought provoking.

Announcements:

The next show will be Sunday, the 26th of July at 7PM UTC, 2PM US Central Time, 8PM British Summer Time

Wrap-up:

Before we leave, we want to make sure to acknowledge some of the people who make mintCast possible … 

  • Hobstar for his work on the new logo
  • Josh for all his work on the website
  • Hacker Public Radio for the Mumble server we are using to record
  • Bytemark Hosting for hosting mintcast.org and our Mumble server
  • Archive.org for hosting our audio files
  • The Linux Mint development team for the fine distro we love to talk about.
]]> full 4540 mintCast 339.5 – ZFS Butter Recognize https://mintcast.org/mintcast-339-5-zfs-butter-recognize/ Wed, 22 Jul 2020 04:20:44 +0000 http://mintcast.org/?p=4534 And finally, some feedback and a few suggestions
Download
]]>

Download

1:58 Innards
44:04 Feedback
1:16:41 Check This Out
1:20:58 Outro

In our Innards section, community member Joshua Hawk tries to convert us to unsalted BTRFS.

And finally, some feedback and a few suggestions

LINUX INNARDS: 

Joshua Hawk

When did you first learn about Linux?

When did you start using it as much as you do?

Btrfs – No Partitions Needed, with Joshua Hawk 

  • Features
    1. Copy on Write (CoW)
      1. Creates new files when storing data instead of overwriting current data.
      2. Necessary for snapshots
    2. Subvolumes
      1. Like a partition but has access to the entire space of the btrfs formatted disk.
      2. Also necessary for snapshots
      3. Can be interacted with either like a directory on a filesystem or like a separately mounted filesystem.
      4. Some subvolume commands
        1.  subvolume create [destination] <name of subvolume>
        2. subvolume delete [option] <subvolume name> [<subvolume inside subvolume>] 
        3. subvolume list [options] [–sort=rootid,gen,ogen,path] <path>
    3. Snapshots
      1. NOT BACKUPS! They are akin to Windows system restore points but far far superior. 
      2. Can be automated using snapper or timeshift.
      3. Is a subvolume itself that points to data and metadata in its parent subvolume.
      4. NOT BACKUPS! 
    4. File System Compression (ZLIB, LZO, ZSTD)
      1. Saves space sometimes up to 20%-30%
      2. Increases life of SSD’s due to significantly less writes
      3. ZSTD is flexible and configurable to your needs.
      4. Mounting a subvolume with the compression option won’t compress files currently on subvolume.
      5. To compress files already contained in a subvolume you must use the Defrag command with the -r option
    5. Checksumming
      1. Not Enabled on SSD’s by default due to the fact that ssd’s tend to just fail rather than die slowly. If you want this feature with ssd’s it is recommended to use 2 ssd’s in a RAID 1 Configuration.
      2. Enabled by default on HDD’s and when used with RAID 1 will checksum and self heal files that are corrupt. 
    6. SSD Awareness
      1. Disables file duplication to reduce writes
      2. TRIM/Discard to report free blocks for reuse
      3. Sends writes in clusters resulting in larger write operations and faster throughput. 
    7. Send/Receive of subvolume changes
      1. Can send and receive subvolumes and changes to those subvolumes over the network for backup operations.
    8. RAID Support
      1. RAID 0, 1, 5, 6, 10 support
      2. RAID 5 and 6 are experimental and are NOT recommended!
      3. RAID 0, 1, and 10 are production ready
      4. Can add and remove storage to RAID on the fly
  1. When to use btrfs
    1. Root Filesystem
    2. Redundant data storage (NAS)
    3. Laptops with SSDs
    4. Btrfs works for MOST filesystem cases
  1. When not to use btrfs
    1. Anything that does not need redundant data storage (video game data storage for example excluding game save data)
    2. Databases due to the slow nature of CoW.
  1. Issues with btrfs
    1. Will not mount a filesystem if errors are detected on disk. This can be corrected by using the scrub command 99% of the time.
    2. If connection is lost or computer/server loses power during some btrfs operations, may result in data corruption or file system issues.
    3. If snapshots are not being controlled by a script or a limit is not set the disk drive may fill up and cause issues. Can be corrected by deleting some snapshots.
    4. As stated before RAID 5/6  is experimental and has major issues. 
  1. Main Contributors to btrfs
    1. Facebook – Where Chris Mason the lead dev on btrfs is employed
    2. SUSE Linux Enterprise (SLE)
    3. Fujitsu
    4. Oracle
  1. Links to Good btrfs Content
    1. https://btrfs.wiki.kernel.org/index.php/Main_Page
    2. https://en.wikipedia.org/wiki/Btrfs
    3. btrfs: The Best Filesystem You’ve Never Heard Of – YouTube
    4. openSUSE Conference 2018 – btrfs is awesome, except when it isn’t – YouTube
    5. btrfs Tutorial | btrfs Filesystem | btrfs Subvolume and btrfs Snapshots – YouTube
    6. BTRFS Guide – Basic Commands, Snapshots, and RAID – Chris Titus Tech

VIBRATIONS FROM THE ETHER

  • Brad Alexander 
  • Brad’s addendum
  • Joe’s response
  • Henrik
  • Benjamin Moser
  • Jim Daldry
  • Bill Dietrich
  • John Wallis Saga Episode x+1

CHECK THIS OUT! 

Not Linux related at all, just a great poem about the current situation and how it may just be a positive thing. It is released under a Creative commons licence and called ‘What Happened when we all stopped’ by Tom & Bee Rivett-Carnac, very thought provoking.

Announcements:

The next show will be Sunday, the 26th of July at 7PM UTC, 2PM US Central Time, 8PM British Summer Time

Wrap-up:

Before we leave, we want to make sure to acknowledge some of the people who make mintCast possible … 

  • Hobstar for his work on the new logo
  • Josh for all his work on the website
  • Hacker Public Radio for the Mumble server we are using to record
  • Bytemark Hosting for hosting mintcast.org and our Mumble server
  • Archive.org for hosting our audio files
  • The Linux Mint development team for the fine distro we love to talk about.
]]> full 4534