<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3" -->
<rss version="0.92">
<channel>
	<title>SystemRescueCd news</title>
	<link>http://www.sysresccd.org/news</link>
	<description>latest news about the sysresccd livecd</description>
	<lastBuildDate>Sun, 13 Apr 2008 20:43:40 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>New boot options for advanced ethernet IP configuration</title>
		<description>SystemRescueCd provides several network configuration boot options so that the network interfaces are already configured when the SystemRescueCd boot process is complete. These options allows both dynamic IP configuration (using dodhcp) and static IP configuration (using ethx=ipaddr/cidr, gateway=ipaddr, dns=ipaddr).

With the ethx=ipaddr/cidr option, all the ethernet interfaces of the computer are ...</description>
		<link>http://www.sysresccd.org/news/2008/04/13/new-boot-options-for-advanced-ethernet-ip-configuration/</link>
			</item>
	<item>
		<title>Use SystemRescueCd remotely with Vnc server</title>
		<description>SystemRescueCd-1.0.2-beta7 introduces the Vnc server. Now the tightvnc package is compiled with the server support. It means a Vnc server can be started on SystemRescueCd so that you can graphical applications (such as GParted) from another computer (the vnc client).

It means you have the ability use the graphical environment remotely. ...</description>
		<link>http://www.sysresccd.org/news/2008/04/12/use-systemrescuecd-remotely-with-vnc-server/</link>
			</item>
	<item>
		<title>SystemRescueCd ported to unicode (utf8)</title>
		<description>SystemRescueCd was ported to unicode (thanks to Melkor for his help). Since SystemRescueCd-1.0.2-beta4, all programs are compiled with the USE="unicode" that is used by gentoo portage to compile the software. The new default locale is en_US.utf8. It must not be a problem to use special characters in the console under ...</description>
		<link>http://www.sysresccd.org/news/2008/04/06/systemrescuecd-ported-to-unicode-utf8/</link>
			</item>
	<item>
		<title>SystemRescueCd is now based on unionfs</title>
		<description>The recent 1.0.1-beta versions are now based on unionfs. The root filesystem of the livecd is the union of two filesystems: first it shows the contents of the read-only squash filesystem stored in sysrcd.dat that contains all the programs.  The second filesystem is a writeable tmpfs filesystem that allows ...</description>
		<link>http://www.sysresccd.org/news/2008/03/16/systemrescuecd-is-now-based-on-unionfs/</link>
			</item>
	<item>
		<title>Use Xvesa when Xorg does not work</title>
		<description>The Xvesa X server has been added to SystemRescueCd-1.0.0. This tiny X server aims to provide a graphical environment when Xorg does not work on a machine because the driver does not work or for any other reason.

In older versions (until SystemRescueCd-0.4.4-beta12), the only thing you could do when startx ...</description>
		<link>http://www.sysresccd.org/news/2008/02/17/use-xvesa-when-xorg-does-not-work/</link>
			</item>
	<item>
		<title>Manage remote servers using SystemRescueCd</title>
		<description>The most popular way of using SystemRescueCd is from a CDRom drive on a desktop in interactive mode. Recent SystemRescueCd versions also come with the support for network boot via PXE. The network configuration  boot options (such as ethx=ip, gateway=ip, dns=ip, dochdp) allow you to automatically configure the network ...</description>
		<link>http://www.sysresccd.org/news/2008/02/10/manage-remote-servers-using-systemrescuecd/</link>
			</item>
	<item>
		<title>SystemRescueCd supports i486 processors again</title>
		<description>Since SystemRescueCd-0.3.0, it was required to have at least an i686 CPU (Pentium-Pro processor or newer) to be able to run SystemRescueCd. This was because the glibc on gentoo required i686 to compile. So SystemRescueCd-0.2.19 was the last version that supports old processors (between i386 and i686).

The support for old ...</description>
		<link>http://www.sysresccd.org/news/2008/02/08/systemrescuecd-supports-i486-processors-again/</link>
			</item>
	<item>
		<title>PXE can download the sysrcd.dat filesystem through TFTP as well as HTTP</title>
		<description>PXE network booting was a major feature added to SystemRescueCd-0.4.0. To get it to work, you need three network services:

	dhcp server that sends a dynamic IP address and some parameters
	tftp server that sends the bootloader and the kernel + ramdisk
	http server that sends the compressed root filesystem (sysrcd.dat)

Some users complained ...</description>
		<link>http://www.sysresccd.org/news/2008/01/27/pxe-can-download-the-sysrcddat-filesystem-through-tftp-as-well-as-http/</link>
			</item>
	<item>
		<title>Autorun rewritten in SystemRescueCd-1.0.0</title>
		<description>Autorun has been rewritten in SystemRescueCd-1.0.0 (0.4.4-beta4 and newer). Autorun is the feature that allow you to execute your own scripts when sysresccd starts. The scripts can be copied in sysresccd by doing an customized version. They can also be copied from a partition on your harddisk / usb-key or ...</description>
		<link>http://www.sysresccd.org/news/2008/01/27/autorun-rewritten-in-systemrescuecd-044/</link>
			</item>
	<item>
		<title>GPT disklabel support (Guid Partition Table)</title>
		<description>SystemRescueCd-1.0.0 comes with the support of the GPT disklabels (Guid Partition Table). The GPT disklabel is the new generation disklabel that aims to replace the very old msdos disklabel created with the first PCs. The GPT table is the default system on computer with EFI bios such as macintel and ...</description>
		<link>http://www.sysresccd.org/news/2008/01/26/gpt-disklabel-support-guid-partition-table/</link>
			</item>
</channel>
</rss>
