<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://old.andunix.net/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://old.andunix.net/feed.php">
        <title>andunix.net</title>
        <description></description>
        <link>https://old.andunix.net/</link>
        <image rdf:resource="https://old.andunix.net/_media/favicon.ico" />
       <dc:date>2026-06-03T19:33:52+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://old.andunix.net/info/linux/debian/cleanup_packages"/>
                <rdf:li rdf:resource="https://old.andunix.net/blog/2010/memory_usage_solaris_container_zone"/>
                <rdf:li rdf:resource="https://old.andunix.net/info/solaris/localeadm"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://old.andunix.net/_media/favicon.ico">
        <title>andunix.net</title>
        <link>https://old.andunix.net/</link>
        <url>https://old.andunix.net/_media/favicon.ico</url>
    </image>
    <item rdf:about="https://old.andunix.net/info/linux/debian/cleanup_packages">
        <dc:format>text/html</dc:format>
        <dc:date>2014-04-28T09:01:22+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Cleanup Packages</title>
        <link>https://old.andunix.net/info/linux/debian/cleanup_packages</link>
        <description>Cleanup Packages

Purge uninstalled Packages

If a package is removed, it is only uninstalled, but the configuration remains on the system.
This is a good thing, as you are able to reinstall the package and have it configured with the old configuration.
But if you want to cleanup this old stuff, you can ge a list of uninstalled (but not purged) packages with this command:</description>
    </item>
    <item rdf:about="https://old.andunix.net/blog/2010/memory_usage_solaris_container_zone">
        <dc:format>text/html</dc:format>
        <dc:date>2010-04-21T08:17:00+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>Memory Usage of a Solaris Container (Zone)</title>
        <link>https://old.andunix.net/blog/2010/memory_usage_solaris_container_zone</link>
        <description>Memory Usage of a Solaris Container (Zone)

Last week one of my servers ran out of RAM and Swap. Shame on me for not monitoring that, but it's now.

As the server is running several zones, my first question was: Which zone is eating up my RAM? So, here are the commands I used.</description>
    </item>
    <item rdf:about="https://old.andunix.net/info/solaris/localeadm">
        <dc:format>text/html</dc:format>
        <dc:date>2013-03-01T20:58:12+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>localeadm</title>
        <link>https://old.andunix.net/info/solaris/localeadm</link>
        <description>localeadm

The localeadm utility queries and configures Solaris locales through a command line interface.

	*  man page: localeadm(1M)

Preparation

Check your Solaris Release with cat /etc/release and get a matching DVD or ISO image.

If you're using an ISO image, you have to mount it (insert your path in the first line.</description>
    </item>
</rdf:RDF>
