<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://blogmarks.net/api/user/linuxmint/marks">
<title>Public marks from user linuxmint</title>
<description>Public marks from user linuxmint</description>
<link>http://blogmarks.net/user/linuxmint/marks</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/linuxmint/mark/751955"/>
<rdf:li resource="http://blogmarks.net/api/user/linuxmint/mark/751777"/>
<rdf:li resource="http://blogmarks.net/api/user/linuxmint/mark/751775"/>
<rdf:li resource="http://blogmarks.net/api/user/linuxmint/mark/751773"/>
<rdf:li resource="http://blogmarks.net/api/user/linuxmint/mark/650504"/>
<rdf:li resource="http://blogmarks.net/api/user/linuxmint/mark/650502"/>
<rdf:li resource="http://blogmarks.net/api/user/linuxmint/mark/650501"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/linuxmint/mark/751955">
<title>Network configuration files in Linux</title>
<link>http://linuxmint.com/content/view/714/29/</link>
<description>Commands like route and ifconfig can set up a computer on the network. However, upon reboot, the configuration is lost. Although route and ifconfig properly configure the computer to connect to the network, they didn't change its permanent network configuration, which was restored at boot time.</description>
<dc:date>2006-08-04T13:34:18Z</dc:date>
<dc:author>linuxmint</dc:author>
<dc:subject>networking, linux</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://linuxmint.com/content/view/714/29/"><img border="0" src="http://blogmarks.net/screenshots/2006/08/04/acda4e6b6cf0bbdaa889329f6d546f56.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://linuxmint.com/content/view/714/29/">Network configuration files in Linux</a></h4>
 
by <a href="http://blogmarks.net/user/linuxmint">linuxmint</a> 
<p class="description">Commands like route and ifconfig can set up a computer on the network. However, upon reboot, the configuration is lost. Although route and ifconfig properly configure the computer to connect to the network, they didn't change its permanent network configuration, which was restored at boot time.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/networking">networking</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/linux">linux</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=751955">Copy</a> | 
<a href="http://blogmarks.net/link/1009206">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/linuxmint/mark/751777">
<title>Using both static addresses and DHCP</title>
<link>http://linuxmint.com/content/view/692/53/</link>
<description>When you set up your home network an important choice has to be made. Are you going to use dynamic or static addressing? In other words, are you going to assign IP addresses to your computers manually, or will you ask your router to assign them for you dynamically through the use of DHCP? Sometimes, the best is to use both. In this article we'll see what advantages DHCP and static addressing can give us compared to each other and we'll learn how to use both in our home network.
</description>
<dc:date>2006-08-04T10:26:44Z</dc:date>
<dc:author>linuxmint</dc:author>
<dc:subject>networking, linux</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://linuxmint.com/content/view/692/53/"><img border="0" src="http://blogmarks.net/screenshots/2006/08/04/04def44625fea43c090632298a4db7ad.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://linuxmint.com/content/view/692/53/">Using both static addresses and DHCP</a></h4>
 
by <a href="http://blogmarks.net/user/linuxmint">linuxmint</a> 
<p class="description">When you set up your home network an important choice has to be made. Are you going to use dynamic or static addressing? In other words, are you going to assign IP addresses to your computers manually, or will you ask your router to assign them for you dynamically through the use of DHCP? Sometimes, the best is to use both. In this article we'll see what advantages DHCP and static addressing can give us compared to each other and we'll learn how to use both in our home network.
</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/networking">networking</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/linux">linux</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=751777">Copy</a> | 
<a href="http://blogmarks.net/link/1009063">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/linuxmint/mark/751775">
<title>Securing your network by filtering MAC Addresses</title>
<link>http://linuxmint.com/content/view/691/53/</link>
<description>If you live in the middle of nowhere you probably wonder why you should secure the access to your network. If you're setting up a company network however, this probably seems obvious to you: you don't want unwanted access to the network. Even at home, with wireless networks becoming more and more popular, you could very well be concerned by this problem. For instance,  if you have a Wifi router at home which connects you to the Internet, chances are that people around you (your neighbours?) are connecting through it to access the Internet via your Internet account.

There are many ways to secure a network, and even more ways to secure a wireless network. In this article we will see how to secure the access to a router by filtering the MAC addresses.
</description>
<dc:date>2006-08-04T10:25:42Z</dc:date>
<dc:author>linuxmint</dc:author>
<dc:subject>networking, linux</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://linuxmint.com/content/view/691/53/"><img border="0" src="http://blogmarks.net/screenshots/2006/08/04/7b37834d189838c3b5addb3848de42f9.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://linuxmint.com/content/view/691/53/">Securing your network by filtering MAC Addresses</a></h4>
 
by <a href="http://blogmarks.net/user/linuxmint">linuxmint</a> 
<p class="description">If you live in the middle of nowhere you probably wonder why you should secure the access to your network. If you're setting up a company network however, this probably seems obvious to you: you don't want unwanted access to the network. Even at home, with wireless networks becoming more and more popular, you could very well be concerned by this problem. For instance,  if you have a Wifi router at home which connects you to the Internet, chances are that people around you (your neighbours?) are connecting through it to access the Internet via your Internet account.

There are many ways to secure a network, and even more ways to secure a wireless network. In this article we will see how to secure the access to a router by filtering the MAC addresses.
</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/networking">networking</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/linux">linux</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=751775">Copy</a> | 
<a href="http://blogmarks.net/link/1009060">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/linuxmint/mark/751773">
<title>How to setup a home network using static addresses?</title>
<link>http://linuxmint.com/content/view/690/29/</link>
<description>If you have more than one computer at home, you'll probably want to set up a network so that they can communicate. This way you'll be able to share your Internet connection and to transfer files and services between your different computers. Most home networks have two functions: They connect the computers together on the same network and they connect that network to the Internet. The most popular technology to set up home network is called Ethernet and it uses a communication protocol called IP (which stands for &quot;Internet Protocol&quot;). All modern computers now have ethernet or wifi cards and it has become very easy to connect them to the network.
</description>
<dc:date>2006-08-04T10:24:19Z</dc:date>
<dc:author>linuxmint</dc:author>
<dc:subject>networking, linux</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://linuxmint.com/content/view/690/29/"><img border="0" src="http://blogmarks.net/screenshots/2006/08/04/7a8f858058fa2ecf474c08b0a94c879d.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://linuxmint.com/content/view/690/29/">How to setup a home network using static addresses?</a></h4>
 
by <a href="http://blogmarks.net/user/linuxmint">linuxmint</a> 
<p class="description">If you have more than one computer at home, you'll probably want to set up a network so that they can communicate. This way you'll be able to share your Internet connection and to transfer files and services between your different computers. Most home networks have two functions: They connect the computers together on the same network and they connect that network to the Internet. The most popular technology to set up home network is called Ethernet and it uses a communication protocol called IP (which stands for "Internet Protocol"). All modern computers now have ethernet or wifi cards and it has become very easy to connect them to the network.
</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/networking">networking</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/linux">linux</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=751773">Copy</a> | 
<a href="http://blogmarks.net/link/1009058">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/linuxmint/mark/650504">
<title>Mandriva One Review</title>
<link>http://linuxmint.com/content/view/149/32/</link>
<description>After Ubuntu 6.06, Fedora Core 5 and SUSE 10.1 were released in the first two quarters of this year, I started to wonder about Mandriva. Was there still any reason for people to use Mandriva? Had the distribution become outdated?</description>
<dc:date>2006-06-23T13:57:50Z</dc:date>
<dc:author>linuxmint</dc:author>
<dc:subject>linux, mandriva, review, 2006, one</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://linuxmint.com/content/view/149/32/"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://linuxmint.com/content/view/149/32/">Mandriva One Review</a></h4>
 
by <a href="http://blogmarks.net/user/linuxmint">linuxmint</a> 
<p class="description">After Ubuntu 6.06, Fedora Core 5 and SUSE 10.1 were released in the first two quarters of this year, I started to wonder about Mandriva. Was there still any reason for people to use Mandriva? Had the distribution become outdated?</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/linux">linux</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mandriva">mandriva</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/review">review</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/2006">2006</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/one">one</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=650504">Copy</a> | 
<a href="http://blogmarks.net/link/937567">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/linuxmint/mark/650502">
<title>How to add MP3 support to your Linux Distribution?</title>
<link>http://linuxmint.com/content/view/200/51/</link>
<description>You've just installed a new Linux distribution on your computer and it won't play your MP3 files? All your songs are encoded in that format and you don't know what to do? Well, don't worry. This is a common problem in Linux and it has a simple solution. </description>
<dc:date>2006-06-23T13:54:21Z</dc:date>
<dc:author>linuxmint</dc:author>
<dc:subject>linux, mp3</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://linuxmint.com/content/view/200/51/"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://linuxmint.com/content/view/200/51/">How to add MP3 support to your Linux Distribution?</a></h4>
 
by <a href="http://blogmarks.net/user/linuxmint">linuxmint</a> 
<p class="description">You've just installed a new Linux distribution on your computer and it won't play your MP3 files? All your songs are encoded in that format and you don't know what to do? Well, don't worry. This is a common problem in Linux and it has a simple solution. </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/linux">linux</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mp3">mp3</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=650502">Copy</a> | 
<a href="http://blogmarks.net/link/937566">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/linuxmint/mark/650501">
<title>How to get widescreen resolution in Linux?</title>
<link>http://linuxmint.com/content/view/212/29/</link>
<description>If you own a laptop with widescreen resolution such as 1280x768, 1280x800 or 1400x1050, you might have encountered that problem. XWindow shows up in 1024x768, and it doesn't fill the entire width of the screen. If your laptop's graphic card is an Intel 800 or 900 series (Intel 845G, 855G, 865G, 915G, 915GM, and 945G), there is a very easy solution to fix this. </description>
<dc:date>2006-06-23T13:51:44Z</dc:date>
<dc:author>linuxmint</dc:author>
<dc:subject>linux, resolution, xwindow, kde, gnome</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://linuxmint.com/content/view/212/29/"><img border="0" src="http://www.blogmarks.net/screenshots/2006/06/23/d3de5a16b7c024c94b728470a65357a3.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://linuxmint.com/content/view/212/29/">How to get widescreen resolution in Linux?</a></h4>
 
by <a href="http://blogmarks.net/user/linuxmint">linuxmint</a> 
<p class="description">If you own a laptop with widescreen resolution such as 1280x768, 1280x800 or 1400x1050, you might have encountered that problem. XWindow shows up in 1024x768, and it doesn't fill the entire width of the screen. If your laptop's graphic card is an Intel 800 or 900 series (Intel 845G, 855G, 865G, 915G, 915GM, and 945G), there is a very easy solution to fix this. </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/linux">linux</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/resolution">resolution</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/xwindow">xwindow</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/kde">kde</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/gnome">gnome</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=650501">Copy</a> | 
<a href="http://blogmarks.net/link/937563">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>