Blackburn's Wiki

UploadLog

Thu, 07 May 2009 23:13:53 GMT

date	user	location	storeUrl	uploadDir	toFilename	backupdir	origin
03/07/2008 12:52:28	ChrisBlackburn	/	store.cgi	.	index.html	.	failed
03/07/2008 12:53:04	ChrisBlackburn	/	store.cgi	.	index.html	.
07/07/2008 19:44:57	YourName	cbci.html	store.cgi	.	index.html	.	ok
07/05/2009 18:13:53	ChrisBlackburn	cbci.html	store.cgi	.	index.html	.

Asterisk

Mon, 27 Oct 2008 21:10:00 GMT

When having trouble with receiving incoming calls from standard POTS lines through ZAP channel, but able to make outgoing calls just fine on same channel:

Possible solutions:

rebuild_zaptel
/usr/src/rebuildastsrc.sh
tail /var/log/asterisk/full # and watch for "Alarm cleared on channel x"

ColorPalette

Mon, 27 Oct 2008 19:16:00 GMT

Name: MptwBlue
Background: #fff
Foreground: #000
PrimaryPale: #cdf
PrimaryLight: #57c
PrimaryMid: #114
PrimaryDark: #012
SecondaryPale: #ffc
SecondaryLight: #fe8
SecondaryMid: #db4
SecondaryDark: #841
TertiaryPale: #eee
TertiaryLight: #ccc
TertiaryMid: #999
TertiaryDark: #666
Error: #f88

Next Gen Boards - View Single Post - Invisible/Invincible Tank/Warhawk + Effects

Thu, 24 Jul 2008 04:34:00 GMT

The tank glitch works flawlessly. It works perfectly if you get the hang of it.

Problem is... the tank glitch works easier on player (unranked) servers. On official ranked (or dedicated ranked servers), the tank glitch gets difficult to work. Thus, it takes more than five to ten minutes in ranked servers as opposed to a few seconds on a player or unranked server.

Anyway, for those having a difficult time doing the tank glitch, try it on a unranked server. Refer to Outsider's steps of how to do the tank glitch. You can actually execute the glitch within a few seconds instead of fifteen to twenty seconds.

Oh, by the way... this glitch is useless for Warhawks. You may be invincible/invisible but you cannot kill anyone. :(

TANK GLITCH

- Find any tank on the map (Eucadian or Chernovan). The condition of the tank does not matter.

- Before you do the glitch, make sure you find a spot that no player (enemy or teammate) can find you.
^ Why? Because if you perform the glitch, your tank or soldier will be exposed on the location you did it on. Hence, you're basically separating yourself from your "physical state tank" to a "mental state tank"... However, players can still kill (or teamkill you) if they find your "physical state tank." Sometimes if they destroy your "physical state tank," you can end up at the location of your "mental state tank." (Physical State: Original Mode/Mental State: Glitch Mode) :)

- Rapidly press the SQUARE button a few times (or more) and make sure you end up inside the tank after each session.
^ Some posters here say it depends on your ping. I'm not sure of this or determined it if it's true. If your trying it for the first time, I suggest you do it on a unranked server. For me it takes: one to three tries (or less than 10 seconds) to get the tank glitch to work on unranked servers; ten to a lot tries (one minute to beyond 10 minutes) to get the tank glitch working on a ranked server.

- Now, look at your tank's health bar. It should begin to rapidly change from full health to zero and vice versa. It means... TANK GLITCH! :p
^ It is easier to have a tank at its full health condition before you do the glitch. So you can tell if you did it right since (at most times) your perfectly undamaged tank is now on fire which means that the glitch worked. ;)

Tank glitch effect will go away if:

~ You exit the tank during the glitch mode (why in the hell would you do that?).
~ Your physical state was found and players destroyed your tank or killed you. But again, you might end up at your mental state's location if this happens.
~ Risk of being kicked or banned (only unranked servers)... :D

ADVANTAGES

- Invincibility: Infinite health.
- Invisibility: No one can see you.
- Teleporting: You can teleport back to your original physical state.
^ Useful if your tank gets stuck. Simply hold the SQUARE button and press down on the D-Pad. You will be on the passenger's seat of the tank. It will teleport you back to the location of your physical state. However, you will have to exit the tank and perform the glitch again.

DISADVANTAGES

- Foot soldiers animations are extremely laggy as hell.
- Effect goes away if physical state is destroyed.
- Cannot run over players.
- Cannot capture zones.
- Another play may control your physical state while you are in your mental state. As a result, if this player dies in your physical state, you may either die or spawn at the location of your mental state.
- During mental state (or glitch), you are extremely light. Meaning, you are pushable.
- High risk of being kicked or banned.
- Risk of being banned from PlayStation Network if reported.

Source: Next Gen Boards - View Single Post - Invisible/Invincible Tank/Warhawk + Effects

Simple AFP Forensics using Access Logs « Pattern Buffer:

Thu, 24 Jul 2008 03:37:00 GMT

Simple AFP Forensics using Access Logs
July 15, 2008 — Kyle Crawford

Mac OS X Server’s AFP server access logs aren’t the greatest (no full paths is a glaring omission), but if you have them enabled, they can be useful for finding who deleted a file or folder for example.

If the item’s name starts with “Important File”, this command gives us the ip address of the client that deleted the item :
file_server:~ root# grep -i "Delete Important File*" /Library/Logs/AppleFileService/AppleFileServiceAccess.log
IP 10.1.21.6 - - [08/Jul/2008:14:26:14 -0500] “Delete Important File 2009.xls” 0 0 0

Then we pass the ip address into this command to give us the login of the user:
file_server:~ root# grep 10.1.21.6 /Library/Logs/AppleFileService/AppleFileServiceAccess.log | grep Login
IP 10.1.21.6 - - [08/Jul/2008:09:05:43 -0500] “Login mpickens” 0 0 0

Finally we can use dscl to lookup the full name the user:
file_server:~ root# dscl localhost read /Search/Users/mpickens RealName
RealName: Pickens, Mary Ellen

Older logs are available too in zipped form. Use gunzip -c to read the contents.
file_server:~ root# gunzip -c '/Library/Logs/AppleFileService/AppleFileServiceAccess.log 12.11.07.gz' | grep Login | grep mpickens
IP 10.1.21.143 - - [14/Dec/2007:19:12:38 -0500] “Login mpickens” 0 0 0
IP 10.1.21.143 - - [14/Dec/2007:19:24:32 -0500] “Login mpickens” 0 0 0
IP 10.1.21.143 - - [17/Dec/2007:09:21:38 -0500] “Login mpickens” 0 0 0
IP 10.1.21.143 - - [17/Dec/2007:10:37:49 -0500] “Login mpickens” 0 0 0

Source: Simple AFP Forensics using Access Logs « Pattern Buffer:

Having fun with netcat. - Linux Forums

Tue, 15 Jul 2008 23:21:00 GMT

Interestingly netcat is going to help us in future as the best way to debug future network protocols. Peer to peer networking is often touted as the wave of the future Internet and I shall talk about an interesting anecdote of how invaluable netcat proved to me whilst testing my peer topeer NAT traversal library.

It is not very likely you have used it. So let us start with few simple exams before we get on to nontrivial ones.

$nc -l -p 1234

will set up a TCP server on your machine. You can fire up

$nc localhost 1234

on another terminal which will set up a TCP client. You can now start talking between the two. Whatever you type here appears there and vice versa. Simple, isn't it?

on another terminal which will set up a TCP client. You can now start. Moreover it has power. The sort of power that only deceptively simple tools can possess. Let me demonstrate.

$nc -l -u -p 1234

will setup a UDP server. And you can talk to it with

$nc -u localhost 1234

Source: Having fun with netcat. - Linux Forums

Netcat - tcp proxy

Tue, 15 Jul 2008 23:13:00 GMT

mknod backpipe p nc -l -p 80 0<backpipe | tee -a inflow | nc localhost 81 | tee -a outflow 1>backpipe

Source: Netcat - network connections made easy

Caller id problems - BlackBerry Forums at CrackBerry.com

Tue, 08 Jul 2008 01:57:00 GMT

Click on the phone icon.

Click the menu button

Click options / general options / restrict my identity - is it on, or off?

Source: Caller id problems - BlackBerry Forums at CrackBerry.com

www.centos.org - Forums - CentOS 4 - General Support - Second Harddrive Installation fstab & fstab-sync Problems

Tue, 08 Jul 2008 01:46:00 GMT

DISABLING FSTAB-SYNC
Automatic updates of the /etc/fstab file by the fstab-sync program from the HAL dae-
mon can be disabled by changing the 50-fstab-sync.hal symlink in /etc/hal/device.d
directory to point to /bin/false

Source: www.centos.org - Forums - CentOS 4 - General Support - Second Harddrive Installation fstab & fstab-sync Problems

UploadPlugin

Tue, 08 Jul 2008 00:46:00 GMT

Name:	PasswordOptionPlugin
Description:	Extends TiddlyWiki options with non encrypted password option.
Version:	1.0.2
Date:	Apr 19, 2007
Source:	http://tiddlywiki.bidix.info/#PasswordOptionPlugin
Author:	BidiX (BidiX (at) bidix (dot) info)
License:	BSD open source license
CoreVersion:	2.2.0 (Beta 5)

version.extensions.PasswordOptionPlugin = {
	major: 1, minor: 0, revision: 2, 
	date: new Date("Apr 19, 2007"),
	source: 'http://tiddlywiki.bidix.info/#PasswordOptionPlugin',
	author: 'BidiX (BidiX (at) bidix (dot) info',
	license: '[[BSD open source license|http://tiddlywiki.bidix.info/#%5B%5BBSD%20open%20source%20license%5D%5D]]',
	coreVersion: '2.2.0 (Beta 5)'
};

config.macros.option.passwordCheckboxLabel = "Save this password on this computer";
config.macros.option.passwordInputType = "password"; // password | text
setStylesheet(".pasOptionInput {width: 11em;}\n","passwordInputTypeStyle");

merge(config.macros.option.types, {
	'pas': {
		elementType: "input",
		valueField: "value",
		eventName: "onkeyup",
		className: "pasOptionInput",
		typeValue: config.macros.option.passwordInputType,
		create: function(place,type,opt,className,desc) {
			// password field
			config.macros.option.genericCreate(place,'pas',opt,className,desc);
			// checkbox linked with this password "save this password on this computer"
			config.macros.option.genericCreate(place,'chk','chk'+opt,className,desc);			
			// text savePasswordCheckboxLabel
			place.appendChild(document.createTextNode(config.macros.option.passwordCheckboxLabel));
		},
		onChange: config.macros.option.genericOnChange
	}
});

merge(config.optionHandlers['chk'], {
	get: function(name) {
		// is there an option linked with this chk ?
		var opt = name.substr(3);
		if (config.options[opt]) 
			saveOptionCookie(opt);
		return config.options[name] ? "true" : "false";
	}
});

merge(config.optionHandlers, {
	'pas': {
 		get: function(name) {
			if (config.options["chk"+name]) {
				return encodeCookie(config.options[name].toString());
			} else {
				return "";
			}
		},
		set: function(name,value) {config.options[name] = decodeCookie(value);}
	}
});

// need to reload options to load passwordOptions
loadOptionsCookie();

/*
if (!config.options['pasPassword'])
	config.options['pasPassword'] = '';

merge(config.optionsDesc,{
		pasPassword: "Test password"
	});
*/

Name:	UploadPlugin
Description:	Save to web a TiddlyWiki
Version:	4.1.0
Date:	May 5, 2007
Source:	http://tiddlywiki.bidix.info/#UploadPlugin
Documentation:	http://tiddlywiki.bidix.info/#UploadPluginDoc
Author:	BidiX (BidiX (at) bidix (dot) info)
License:	BSD open source license
CoreVersion:	2.2.0 (#3125)
Requires:	PasswordOptionPlugin

version.extensions.UploadPlugin = {
	major: 4, minor: 1, revision: 0,
	date: new Date("May 5, 2007"),
	source: 'http://tiddlywiki.bidix.info/#UploadPlugin',
	author: 'BidiX (BidiX (at) bidix (dot) info',
	coreVersion: '2.2.0 (#3125)'
};

//
// Environment
//

if (!window.bidix) window.bidix = {}; // bidix namespace
bidix.debugMode = false;	// true to activate both in Plugin and UploadService
	
//
// Upload Macro
//

config.macros.upload = {
// default values
	defaultBackupDir: '',	//no backup
	defaultStoreScript: "store.php",
	defaultToFilename: "index.html",
	defaultUploadDir: ".",
	authenticateUser: true	// UploadService Authenticate User
};
	
config.macros.upload.label = {
	promptOption: "Save and Upload this TiddlyWiki with UploadOptions",
	promptParamMacro: "Save and Upload this TiddlyWiki in %0",
	saveLabel: "save to web", 
	saveToDisk: "save to disk",
	uploadLabel: "upload"	
};

config.macros.upload.messages = {
	noStoreUrl: "No store URL in parmeters or options",
	usernameOrPasswordMissing: "Username or password missing"
};

config.macros.upload.handler = function(place,macroName,params) {
	if (readOnly)
		return;
	var label;
	if (document.location.toString().substr(0,4) == "http") 
		label = this.label.saveLabel;
	else
		label = this.label.uploadLabel;
	var prompt;
	if (params[0]) {
		prompt = this.label.promptParamMacro.toString().format([this.destFile(params[0], 
			(params[1] ? params[1]:bidix.basename(window.location.toString())), params[3])]);
	} else {
		prompt = this.label.promptOption;
	}
	createTiddlyButton(place, label, prompt, function() {config.macros.upload.action(params);}, null, null, this.accessKey);
};

config.macros.upload.action = function(params)
{
		// for missing macro parameter set value from options
		var storeUrl = params[0] ? params[0] : config.options.txtUploadStoreUrl;
		var toFilename = params[1] ? params[1] : config.options.txtUploadFilename;
		var backupDir = params[2] ? params[2] : config.options.txtUploadBackupDir;
		var uploadDir = params[3] ? params[3] : config.options.txtUploadDir;
		var username = params[4] ? params[4] : config.options.txtUploadUserName;
		var password = config.options.pasUploadPassword; // for security reason no password as macro parameter	
		// for still missing parameter set default value
		if ((!storeUrl) && (document.location.toString().substr(0,4) == "http")) 
			storeUrl = bidix.dirname(document.location.toString())+'/'+config.macros.upload.defaultStoreScript;
		if (storeUrl.substr(0,4) != "http")
			storeUrl = bidix.dirname(document.location.toString()) +'/'+ storeUrl;
		if (!toFilename)
			toFilename = bidix.basename(window.location.toString());
		if (!toFilename)
			toFilename = config.macros.upload.defaultToFilename;
		if (!uploadDir)
			uploadDir = config.macros.upload.defaultUploadDir;
		if (!backupDir)
			backupDir = config.macros.upload.defaultBackupDir;
		// report error if still missing
		if (!storeUrl) {
			alert(config.macros.upload.messages.noStoreUrl);
			clearMessage();
			return false;
		}
		if (config.macros.upload.authenticateUser && (!username || !password)) {
			alert(config.macros.upload.messages.usernameOrPasswordMissing);
			clearMessage();
			return false;
		}
		bidix.upload.uploadChanges(false,null,storeUrl, toFilename, uploadDir, backupDir, username, password); 
		return false; 
};

config.macros.upload.destFile = function(storeUrl, toFilename, uploadDir) 
{
	if (!storeUrl)
		return null;
		var dest = bidix.dirname(storeUrl);
		if (uploadDir && uploadDir != '.')
			dest = dest + '/' + uploadDir;
		dest = dest + '/' + toFilename;
	return dest;
};

//
// uploadOptions Macro
//

config.macros.uploadOptions = {
	handler: function(place,macroName,params) {
		var wizard = new Wizard();
		wizard.createWizard(place,this.wizardTitle);
		wizard.addStep(this.step1Title,this.step1Html);
		var markList = wizard.getElement("markList");
		var listWrapper = document.createElement("div");
		markList.parentNode.insertBefore(listWrapper,markList);
		wizard.setValue("listWrapper",listWrapper);
		this.refreshOptions(listWrapper,false);
		var uploadCaption;
		if (document.location.toString().substr(0,4) == "http") 
			uploadCaption = config.macros.upload.label.saveLabel;
		else
			uploadCaption = config.macros.upload.label.uploadLabel;
		
		wizard.setButtons([
				{caption: uploadCaption, tooltip: config.macros.upload.label.promptOption, 
					onClick: config.macros.upload.action},
				{caption: this.cancelButton, tooltip: this.cancelButtonPrompt, onClick: this.onCancel}
				
			]);
	},
	refreshOptions: function(listWrapper) {
		var uploadOpts = [
			"txtUploadUserName",
			"pasUploadPassword",
			"txtUploadStoreUrl",
			"txtUploadDir",
			"txtUploadFilename",
			"txtUploadBackupDir",
			"chkUploadLog",
			"txtUploadLogMaxLine",
			]
		var opts = [];
		for(i=0; i<uploadOpts.length; i++) {
			var opt = {};
			opts.push()
			opt.option = "";
			n = uploadOpts[i];
			opt.name = n;
			opt.lowlight = !config.optionsDesc[n];
			opt.description = opt.lowlight ? this.unknownDescription : config.optionsDesc[n];
			opts.push(opt);
		}
		var listview = ListView.create(listWrapper,opts,this.listViewTemplate);
		for(n=0; n<opts.length; n++) {
			var type = opts[n].name.substr(0,3);
			var h = config.macros.option.types[type];
			if (h && h.create) {
				h.create(opts[n].colElements['option'],type,opts[n].name,opts[n].name,"no");
			}
		}
		
	},
	onCancel: function(e)
	{
		backstage.switchTab(null);
		return false;
	},
	
	wizardTitle: "Upload with options",
	step1Title: "These options are saved in cookies in your browser",
	step1Html: "<input type='hidden' name='markList'></input><br>",
	cancelButton: "Cancel",
	cancelButtonPrompt: "Cancel prompt",
	listViewTemplate: {
		columns: [
			{name: 'Description', field: 'description', title: "Description", type: 'WikiText'},
			{name: 'Option', field: 'option', title: "Option", type: 'String'},
			{name: 'Name', field: 'name', title: "Name", type: 'String'}
			],
		rowClasses: [
			{className: 'lowlight', field: 'lowlight'} 
			]}
}

//
// upload functions
//

if (!bidix.upload) bidix.upload = {};

if (!bidix.upload.messages) bidix.upload.messages = {
	//from saving
	invalidFileError: "The original file '%0' does not appear to be a valid TiddlyWiki",
	backupSaved: "Backup saved",
	backupFailed: "Failed to upload backup file",
	rssSaved: "RSS feed uploaded",
	rssFailed: "Failed to upload RSS feed file",
	emptySaved: "Empty template uploaded",
	emptyFailed: "Failed to upload empty template file",
	mainSaved: "Main TiddlyWiki file uploaded",
	mainFailed: "Failed to upload main TiddlyWiki file. Your changes have not been saved",
	//specific upload
	loadOriginalHttpPostError: "Can't get original file",
	aboutToSaveOnHttpPost: 'About to upload on %0 ...',
	storePhpNotFound: "The store script '%0' was not found."
};

bidix.upload.uploadChanges = function(onlyIfDirty,tiddlers,storeUrl,toFilename,uploadDir,backupDir,username,password)
{
	var callback = function(status,uploadParams,original,url,xhr) {
		if (!status) {
			displayMessage(bidix.upload.messages.loadOriginalHttpPostError);
			return;
		}
		if (bidix.debugMode) 
			alert(original.substr(0,500)+"\n...");
		// Locate the storeArea div's 
		var posDiv = locateStoreArea(original);
		if((posDiv[0] == -1) || (posDiv[1] == -1)) {
			alert(config.messages.invalidFileError.format([localPath]));
			return;
		}
		bidix.upload.uploadRss(uploadParams,original,posDiv);
	};
	
	if(onlyIfDirty && !store.isDirty())
		return;
	clearMessage();
	// save on localdisk ?
	if (document.location.toString().substr(0,4) == "file") {
		var path = document.location.toString();
		var localPath = getLocalPath(path);
		saveChanges();
	}
	// get original
	var uploadParams = Array(storeUrl,toFilename,uploadDir,backupDir,username,password);
	var originalPath = document.location.toString();
	// If url is a directory : add index.html
	if (originalPath.charAt(originalPath.length-1) == "/")
		originalPath = originalPath + "index.html";
	var dest = config.macros.upload.destFile(storeUrl,toFilename,uploadDir);
	var log = new bidix.UploadLog();
	log.startUpload(storeUrl, dest, uploadDir,  backupDir);
	displayMessage(bidix.upload.messages.aboutToSaveOnHttpPost.format([dest]));
	if (bidix.debugMode) 
		alert("about to execute Http - GET on "+originalPath);
	var r = doHttp("GET",originalPath,null,null,null,null,callback,uploadParams,null);
	if (typeof r == "string")
		displayMessage(r);
	return r;
};

bidix.upload.uploadRss = function(uploadParams,original,posDiv) 
{
	var callback = function(status,params,responseText,url,xhr) {
		if(status) {
			var destfile = responseText.substring(responseText.indexOf("destfile:")+9,responseText.indexOf("\n", responseText.indexOf("destfile:")));
			displayMessage(bidix.upload.messages.rssSaved,bidix.dirname(url)+'/'+destfile);
			bidix.upload.uploadMain(params[0],params[1],params[2]);
		} else {
			displayMessage(bidix.upload.messages.rssFailed);			
		}
	};
	// do uploadRss
	if(config.options.chkGenerateAnRssFeed) {
		var rssPath = uploadParams[1].substr(0,uploadParams[1].lastIndexOf(".")) + ".xml";
		var rssUploadParams = Array(uploadParams[0],rssPath,uploadParams[2],'',uploadParams[4],uploadParams[5]);
		bidix.upload.httpUpload(rssUploadParams,convertUnicodeToUTF8(generateRss()),callback,Array(uploadParams,original,posDiv));
	} else {
		bidix.upload.uploadMain(uploadParams,original,posDiv);
	}
};

bidix.upload.uploadMain = function(uploadParams,original,posDiv) 
{
	var callback = function(status,params,responseText,url,xhr) {
		var log = new bidix.UploadLog();
		if(status) {
			// if backupDir specified
			if ((params[3]) && (responseText.indexOf("backupfile:") > -1))  {
				var backupfile = responseText.substring(responseText.indexOf("backupfile:")+11,responseText.indexOf("\n", responseText.indexOf("backupfile:")));
				displayMessage(bidix.upload.messages.backupSaved,bidix.dirname(url)+'/'+backupfile);
			}
			var destfile = responseText.substring(responseText.indexOf("destfile:")+9,responseText.indexOf("\n", responseText.indexOf("destfile:")));
			displayMessage(bidix.upload.messages.mainSaved,bidix.dirname(url)+'/'+destfile);
			store.setDirty(false);
			log.endUpload("ok");
		} else {
			alert(bidix.upload.messages.mainFailed);
			displayMessage(bidix.upload.messages.mainFailed);
			log.endUpload("failed");			
		}
	};
	// do uploadMain
	var revised = bidix.upload.updateOriginal(original,posDiv);
	bidix.upload.httpUpload(uploadParams,revised,callback,uploadParams);
};

bidix.upload.httpUpload = function(uploadParams,data,callback,params)
{
	var localCallback = function(status,params,responseText,url,xhr) {
		url = (url.indexOf("nocache=") < 0 ? url : url.substring(0,url.indexOf("nocache=")-1));
		if (xhr.status == httpStatus.NotFound)
			alert(bidix.upload.messages.storePhpNotFound.format([url]));
		if ((bidix.debugMode) || (responseText.indexOf("Debug mode") >= 0 )) {
			alert(responseText);
			if (responseText.indexOf("Debug mode") >= 0 )
				responseText = responseText.substring(responseText.indexOf("\n\n")+2);
		} else if (responseText.charAt(0) != '0') 
			alert(responseText);
		if (responseText.charAt(0) != '0')
			status = null;
		callback(status,params,responseText,url,xhr);
	};
	// do httpUpload
	var boundary = "---------------------------"+"AaB03x";	
	var uploadFormName = "UploadPlugin";
	// compose headers data
	var sheader = "";
	sheader += "--" + boundary + "\r\nContent-disposition: form-data; name=\"";
	sheader += uploadFormName +"\"\r\n\r\n";
	sheader += "backupDir="+uploadParams[3] +
				";user=" + uploadParams[4] +
				";password=" + uploadParams[5] +
				";uploaddir=" + uploadParams[2];
	if (bidix.debugMode)
		sheader += ";debug=1";
	sheader += ";;\r\n"; 
	sheader += "\r\n" + "--" + boundary + "\r\n";
	sheader += "Content-disposition: form-data; name=\"userfile\"; filename=\""+uploadParams[1]+"\"\r\n";
	sheader += "Content-Type: text/html;charset=UTF-8" + "\r\n";
	sheader += "Content-Length: " + data.length + "\r\n\r\n";
	// compose trailer data
	var strailer = new String();
	strailer = "\r\n--" + boundary + "--\r\n";
	data = sheader + data + strailer;
	if (bidix.debugMode) alert("about to execute Http - POST on "+uploadParams[0]+"\n with \n"+data.substr(0,500)+ " ... ");
	var r = doHttp("POST",uploadParams[0],data,"multipart/form-data; boundary="+boundary,uploadParams[4],uploadParams[5],localCallback,params,null);
	if (typeof r == "string")
		displayMessage(r);
	return r;
};

// same as Saving's updateOriginal but without convertUnicodeToUTF8 calls
bidix.upload.updateOriginal = function(original, posDiv)
{
	if (!posDiv)
		posDiv = locateStoreArea(original);
	if((posDiv[0] == -1) || (posDiv[1] == -1)) {
		alert(config.messages.invalidFileError.format([localPath]));
		return;
	}
	var revised = original.substr(0,posDiv[0] + startSaveArea.length) + "\n" +
				store.allTiddlersAsHtml() + "\n" +
				original.substr(posDiv[1]);
	var newSiteTitle = getPageTitle().htmlEncode();
	revised = revised.replaceChunk("<title"+">","</title"+">"," " + newSiteTitle + " ");
	revised = updateMarkupBlock(revised,"PRE-HEAD","MarkupPreHead");
	revised = updateMarkupBlock(revised,"POST-HEAD","MarkupPostHead");
	revised = updateMarkupBlock(revised,"PRE-BODY","MarkupPreBody");
	revised = updateMarkupBlock(revised,"POST-SCRIPT","MarkupPostBody");
	return revised;
};

//
// UploadLog
// 
// config.options.chkUploadLog :
//		false : no logging
//		true : logging
// config.options.txtUploadLogMaxLine :
//		-1 : no limit
//      0 :  no Log lines but UploadLog is still in place
//		n :  the last n lines are only kept
//		NaN : no limit (-1)

bidix.UploadLog = function() {
	if (!config.options.chkUploadLog) 
		return; // this.tiddler = null
	this.tiddler = store.getTiddler("UploadLog");
	if (!this.tiddler) {
		this.tiddler = new Tiddler();
		this.tiddler.title = "UploadLog";
		this.tiddler.text = "| !date | !user | !location | !storeUrl | !uploadDir | !toFilename | !backupdir | !origin |";
		this.tiddler.created = new Date();
		this.tiddler.modifier = config.options.txtUserName;
		this.tiddler.modified = new Date();
		store.addTiddler(this.tiddler);
	}
	return this;
};

bidix.UploadLog.prototype.addText = function(text) {
	if (!this.tiddler)
		return;
	// retrieve maxLine when we need it
	var maxLine = parseInt(config.options.txtUploadLogMaxLine,10);
	if (isNaN(maxLine))
		maxLine = -1;
	// add text
	if (maxLine != 0) 
		this.tiddler.text = this.tiddler.text + text;
	// Trunck to maxLine
	if (maxLine >= 0) {
		var textArray = this.tiddler.text.split('\n');
		if (textArray.length > maxLine + 1)
			textArray.splice(1,textArray.length-1-maxLine);
			this.tiddler.text = textArray.join('\n');		
	}
	// update tiddler fields
	this.tiddler.modifier = config.options.txtUserName;
	this.tiddler.modified = new Date();
	store.addTiddler(this.tiddler);
	// refresh and notifiy for immediate update
	story.refreshTiddler(this.tiddler.title);
	store.notify(this.tiddler.title, true);
};

bidix.UploadLog.prototype.startUpload = function(storeUrl, toFilename, uploadDir,  backupDir) {
	if (!this.tiddler)
		return;
	var now = new Date();
	var text = "\n| ";
	var filename = bidix.basename(document.location.toString());
	if (!filename) filename = '/';
	text += now.formatString("0DD/0MM/YYYY 0hh:0mm:0ss") +" | ";
	text += config.options.txtUserName + " | ";
	text += "[["+filename+"|"+location + "]] |";
	text += " [[" + bidix.basename(storeUrl) + "|" + storeUrl + "]] | ";
	text += uploadDir + " | ";
	text += "[[" + bidix.basename(toFilename) + " | " +toFilename + "]] | ";
	text += backupDir + " |";
	this.addText(text);
};

bidix.UploadLog.prototype.endUpload = function(status) {
	if (!this.tiddler)
		return;
	this.addText(" "+status+" |");
};

//
// Utilities
// 

bidix.checkPlugin = function(plugin, major, minor, revision) {
	var ext = version.extensions[plugin];
	if (!
		(ext  && 
			((ext.major > major) || 
			((ext.major == major) && (ext.minor > minor))  ||
			((ext.major == major) && (ext.minor == minor) && (ext.revision >= revision))))) {
			// write error in PluginManager
			if (pluginInfo)
				pluginInfo.log.push("Requires " + plugin + " " + major + "." + minor + "." + revision);
			eval(plugin); // generate an error : "Error: ReferenceError: xxxx is not defined"
	}
};

bidix.dirname = function(filePath) {
	if (!filePath) 
		return;
	var lastpos;
	if ((lastpos = filePath.lastIndexOf("/")) != -1) {
		return filePath.substring(0, lastpos);
	} else {
		return filePath.substring(0, filePath.lastIndexOf("\\"));
	}
};

bidix.basename = function(filePath) {
	if (!filePath) 
		return;
	var lastpos;
	if ((lastpos = filePath.lastIndexOf("#")) != -1) 
		filePath = filePath.substring(0, lastpos);
	if ((lastpos = filePath.lastIndexOf("/")) != -1) {
		return filePath.substring(lastpos + 1);
	} else
		return filePath.substring(filePath.lastIndexOf("\\")+1);
};

bidix.initOption = function(name,value) {
	if (!config.options[name])
		config.options[name] = value;
};

//
// Initializations
//

// require PasswordOptionPlugin 1.0.1 or better
bidix.checkPlugin("PasswordOptionPlugin", 1, 0, 1);

// styleSheet
setStylesheet('.txtUploadStoreUrl, .txtUploadBackupDir, .txtUploadDir {width: 22em;}',"uploadPluginStyles");

//optionsDesc
merge(config.optionsDesc,{
	txtUploadStoreUrl: "Url of the UploadService script (default: store.php)",
	txtUploadFilename: "Filename of the uploaded file (default: in index.html)",
	txtUploadDir: "Relative Directory where to store the file (default: . (downloadService directory))",
	txtUploadBackupDir: "Relative Directory where to backup the file. If empty no backup. (default: ''(empty))",
	txtUploadUserName: "Upload Username",
	pasUploadPassword: "Upload Password",
	chkUploadLog: "do Logging in UploadLog (default: true)",
	txtUploadLogMaxLine: "Maximum of lines in UploadLog (default: 10)"
});

// Options Initializations
bidix.initOption('txtUploadStoreUrl','');
bidix.initOption('txtUploadFilename','');
bidix.initOption('txtUploadDir','');
bidix.initOption('txtUploadBackupDir','');
bidix.initOption('txtUploadUserName','');
bidix.initOption('pasUploadPassword','');
bidix.initOption('chkUploadLog',true);
bidix.initOption('txtUploadLogMaxLine','10');


/* don't want this for tiddlyspot sites

// Backstage
merge(config.tasks,{
	uploadOptions: {text: "upload", tooltip: "Change UploadOptions and Upload", content: '<<uploadOptions>>'}
});
config.backstageTasks.push("uploadOptions");

*/

WelcomeToTiddlyspot

Tue, 08 Jul 2008 00:44:00 GMT

This document is a TiddlyWiki from tiddlyspot.com. A TiddlyWiki is an electronic notebook that is great for managing todo lists, personal information, and all sorts of things.

What now? Before you can save any changes, you need to enter your password in the form below. Then configure privacy and other site settings at your control panel (your control panel username is cbci).

tiddlyspot password:	Save this password on this computer
site management:	upload(requires tiddlyspot password) control panel, download (go offline)
links:	tiddlyspot.com, FAQs, blog, email support & feedback, donate

See also GettingStarted.

Working online    You can edit this TiddlyWiki right now, and save your changes using the "save to web" button in the column on the right.

Working offline    A fully functioning copy of this TiddlyWiki can be saved onto your hard drive or USB stick. You can make changes and save them locally without being connected to the Internet. When you're ready to sync up again, just click "upload" and your TiddlyWiki will be saved back to tiddlyspot.com.

Help!    Find out more about TiddlyWiki at TiddlyWiki.com. Also visit TiddlyWiki.org for documentation on learning and using TiddlyWiki. New users are especially welcome on the TiddlyWiki mailing list, which is an excellent place to ask questions and get help. If you have a tiddlyspot related problem email tiddlyspot support.

Enjoy :)    We hope you like using your tiddlyspot.com site. Please email feedback@tiddlyspot.com with any comments or suggestions.

GettingStarted

Tue, 08 Jul 2008 00:44:00 GMT

To get started with this blank TiddlyWiki, you'll need to modify the following tiddlers:

SiteTitle & SiteSubtitle: The title and subtitle of the site, as shown above (after saving, they will also appear in the browser title bar)
MainMenu: The menu (usually on the left)
DefaultTiddlers: Contains the names of the tiddlers that you want to appear when the TiddlyWiki is opened

You'll also need to enter your username for signing your edits:

tiddlyspot password:	Save this password on this computer
site management:	upload(requires tiddlyspot password) control panel, download (go offline)
links:	tiddlyspot.com, FAQs, blog, email support & feedback, donate

LinuxCommands

Tue, 08 Jul 2008 00:42:00 GMT

Administration Two

Copy a disk partition to a different sized partition.

cp -ax /mnt/source /mnt/destination

LinuxAdministrationCommands

Tue, 08 Jul 2008 00:41:00 GMT

Copy a disk partition to a different sized partition.

cp -ax /mnt/source /mnt/destination

DefaultTiddlers

Tue, 08 Jul 2008 00:30:00 GMT

GettingStarted LinuxCommands

Hard Disk Upgrade Mini How-To

Tue, 08 Jul 2008 00:28:00 GMT

Hard Disk Upgrade Mini How-To
Yves Bellefeuille

yan@storm.ca
Konrad Hinsen

hinsen@cnrs-orleans.fr

v2.11, 13 April 2000

How to copy a Linux system from one disk to another.

Table of Contents
1. Introduction
2. Install both disks on your system
3. Unmount non-Linux partitions and network drives
4. Partition the new disk
5. Format the new disk
6. Mount the new disk
7. Copy the files from the old disk to the new disk
8. Modify /new-disk/etc/fstab as appropriate
9. Prepare LILO to boot the new disk
10. Make a boot diskette (optional)
11. Remove the old disk
12. Reboot the system, modify LILO configuration file
13. Acknowledgements

1. Introduction

This document explains how to transfer, or migrate, an entire Linux system, including LILO, from one hard disk to another.

In the following explanation, /dev/hda (first IDE hard disk) means the old disk, and /dev/hdb (second IDE hard disk) means the new disk.

Specific partitions on the old disk are referred to as /dev/hda1, /dev/hda2, and so on. Specific partitions on the new disk are referred to as /dev/hdb1, /dev/hdb2, and so on.

The explanations in this document are based on Red Hat 6.0. They have also been tested with Debian 2.1, Slackware 3.5 and SuSE 6.2; we indicate a few differences to note if you're using those distributions.

If the commands don't work properly on your system, please let us know, mentioning what distribution you're using.
2. Install both disks on your system

Modern systems can accept four EIDE devices on the hard disk controller, so there shouldn't be any problem installing both disks on your system at the same time, even if you also have other EIDE devices. Hard disks and CD-ROM drives are typical EIDE devices. Floppy drives and tape drives are usually connected to the floppy drive controller rather than to the hard disk controller.

SCSI adapters are even more flexible and can accept seven devices. If you're lucky (and rich) enough to have a SCSI adapter, you probably already know this, and you probably know which of your devices are SCSI devices! For more information, see the SCSI How-To.

Even the oldest systems can accept two devices on the hard disk controller, so you can still install both hard disks at the same time. However, if you already have another device installed in addition to your hard disk (for example, if you have both a hard disk and a CD-ROM drive), you'll have to remove the other device to be able to install the old hard disk and the new hard disk at the same time.

You must configure the disks as master or slave by installing the disks' jumpers as appropriate. You'll often find configuration information on the disks themselves; if not, consult the manuals or the disks' manufacturers.

You must also inform the BIOS of the disks' presence and of their geometry. Usually, you enter the BIOS setup program by pressing a key during the system boot-up. Here's what to do for some common BIOSes:

Acer notebooks

F2 key during Power-On Self-Test (POST)
American Megatrends (AMI)

Del key during Power-On Self-Test
Award

Del, or Ctrl-Alt-Esc
Compaq

F10 key after the square appears in the top right corner of the screen during boot-up
Dell

Ctrl-Alt-Enter
DTK

Esc key during Power-On Self-Test
Hewlett-Packard Pavilion

F1 key during HP blue splash screen
IBM Aptiva 535

F1 while the square with the wavy lines is displayed in the upper right corner during power-on [1]
IBM PS/2

Ctrl-Alt-Del, then Ctrl-Alt-Ins when the cursor is in the top right corner
Mr. BIOS

Ctrl-Alt-S during Power-On Self-Test
Packard Bell

For some models, F1 or F2 key during Power-On Self-Test
Phoenix

Ctrl-Alt-Esc, Ctrl-Alt-S, or Ctrl-Alt-Enter

Many older systems require an Installation or Reference Disk.

We're interested in receiving information on other BIOSes to add them to this list.

Reboot the system and login as root. If you use the su command to become the user root, use su -, with the hyphen option.
3. Unmount non-Linux partitions and network drives

Some people like to mount partitions from other operating systems (DOS, Windows, OS/2, etc.) so they can use them under Linux. These partitions must be created and copied under their own operating system, and you should unmount them before copying your Linux partition. For example, if you have a DOS partition mounted at /dos, you must unmount it with this command:

umount /dos

Note that the command is umount, without the first letter n in the word unmount.

You should also unmount network drives.
4. Partition the new disk

Use this command to partition the new disk:

fdisk /dev/hdb

EIDE devices are identified as hda, hdb, hdc, and hdd in the /dev directory. Partitions on these disks can range from 1 to 16 and are also in the /dev directory. For example, /dev/hda4 refers to partition 4 on hard disk a (first EIDE hard disk).

SCSI devices are listed as devices sda, sdb, sdc, sdd, sde, sdf, and sdg in the /dev directory. Similarly, partitions on these disks can range from 1 to 16 and are also in the /dev directory. For example, /dev/sda3 refers to partition 3 on SCSI disk a (first SCSI hard disk).

For Linux partitions with the ext2 file system, use system ID 83. For swap partitions, use system ID 82.

For more information on partitioning, see the Installation How-To and the Partition Mini How-To.

If your new disk has over 1024 cylinders, see the Large Disk Mini How-To. In brief, you should install all files required to boot Linux within the first 1024 cylinders. One way to do this is to create a small partition (5 Mb or so) just for the /boot directory at the beginning of the disk. (Slackware only: The kernel is at /vmlinuz rather than /boot/vmlinuz, so you should put both the / directory and the /boot directory in this partition.)

Partitions for systems other than Linux should be created using their own fdisk or equivalent command rather than with Linux's fdisk.
5. Format the new disk

Use the following command to format Linux partitions using ext2fs on the new disk:

mkfs.ext2 /dev/hdb1

To check the disk for bad blocks (physical defects), add the -c option just before /dev/hdb1.

If the new disk will have more than one Linux partition, format the other partitions with mkfs.ext2 /dev/hdb2, mkfs.ext2 /dev/hdb3, and so on. Add the -c option if desired.

Note: With older distributions, the command mkfs -t ext2 -c /dev/hdb1 didn't check for bad blocks under any of Red Hat, Debian or Slackware, contrary to what the man page stated. This has now been fixed.

To format a swap partition, use this command:

mkswap /dev/hdb1

Again, you can add the -c option before /dev/hdb1 to check for bad blocks.
6. Mount the new disk

Create a directory where you'll mount the new disk, for example /new-disk, and mount it there:

mkdir /new-disk
mount -t ext2 /dev/hdb1 /new-disk

If the new disk will have more than one Linux partition, mount them all under /new-disk with the same organization they'll have later.

Example. The new disk will have four Linux partitions, as follows:

/dev/hdb1: /
/dev/hdb2: /home
/dev/hdb3: /var
/dev/hdb4: /var/spool

Mount the four partitions under /new-disk as follows:

/dev/hdb1: /new-disk
/dev/hdb2: /new-disk/home
/dev/hdb3: /new-disk/var
/dev/hdb4: /new-disk/var/spool

You must create the mount points for each level before you mount the partitions at that level.

Example.

mkdir /new-disk [1st level]
mount -t ext2 /dev/hdb1 /new-disk

mkdir /new-disk/home [2nd level]
mount -t ext2 /dev/hdb2 /new-disk/home

mkdir /new-disk/var [2nd level also]
mount -t ext2 /dev/hdb3 /new-disk/var

mkdir /new-disk/var/spool [3rd level]
mount -t ext2 /dev/hdb4 /new-disk/var/spool

If you've created a mount point at /new-disk/tmp, you'll need to correct the directory's permissions to let all users access it:

chmod 1777 /new-disk/tmp

7. Copy the files from the old disk to the new disk

You might want to go to single-user mode before starting to copy the disk, in order to shut down the system daemons and preserve the state of the logs, and to prevent users from logging in:

/sbin/telinit 1

When copying the hard disk, you want to copy all directories and files, including links.

However, you don't want to copy the directory /new-disk, since this would copy the new disk to itself!

Furthermore, you want to create the /proc directory on the new disk, but you don't want to copy its contents: /proc is a virtual file system and doesn't have any actual files, but rather contains information on the processes running on the system.

Here are three different ways to copy the old disk to the new one. This may take quite a while, especially if you have a large disk or little memory. You can expect to be able to copy 10 Mb per minute, and possibly much more.

You can follow the copy's progress by using the command df from another terminal. Try watch df or watch ls -l /new-disk to see a report updated every two seconds; press Ctrl-C to end the display. Be aware that running the watch program itself will slow down the copying.

cp -ax / /new-disk

This is the simplest method, but will only work if your original Linux system is on a single disk partition.

The -a option preserves the original system as much as possible. The -x option limits cp to a single file system; this is necessary to avoid copying the /new-disk and /proc directories.

SuSE only. With this method only, you must also create the directory /dev/pts on the new disk. Use the command mkdir /new-disk/dev/pts".

Note: When using the -x option, recent versions of cp will create the directories /new-disk/new-disk and /new-disk/proc, although the directories will be empty. If these directories are created, you should delete /new-disk/new-disk, and keep /new-disk/proc.

cd / && echo cp -a `/bin/ls -1Ab | egrep -v "^new-disk$|^proc$"` /new-disk | sh

(write this all on one line)

This goes to the root directory and then copies all files and directories except /new-disk and /proc to /new-disk. Note that the first option after ls is the number 1, not the letter L!

This command should work in all circumstances.
cp -a /bin /boot /dev /etc /home /lib /lost+found /mnt /root /sbin /tmp /usr /var /new-disk

(write this all on one line)

The last directory, /new-disk, is the destination for the cp command. All the other directories are the sources. Therefore, we're copying all the directories we're listing to /new-disk.

With this method, you simply list yourself the directories you want to copy. Here we listed all the directories except /new-disk and /proc. If you can't use the other methods for any reason, you can always use this command to manually specify the directories you want to copy.

With this method only, if there are any files in the root directory itself, you need another command to copy them. In particular, this is required with Debian and Slackware, since these distributions put files in the root directory:

cp -dp /* /.* /new-disk

Previous versions of the Mini How-To stated that you could also use tar to copy the disk, but this method was found to have a bug. There are of course many other ways to copy the disks, but these three are the simplest, quickest, and most reliable.

After using any of these three methods, you must also create the /proc directory on the new disk, if it doesn't already exist:

mkdir /new-disk/proc

At this point, you may verify the file structure on the new disk, if you wish:

umount /new-disk
fsck.ext2 -f /dev/hdb1
mount -t ext2 /dev/hdb1 /new-disk

If the new disk has more than one partition, you must unmount them from the bottom up before running fsck.ext2: in the example mentioned above, you'd first unmount the 3rd level partitions, then the 2nd level partitions, and then the 1st level partition.

You may also compare the two disks, to ensure that the files were copied properly:

find / -path /proc -prune -o -path /new-disk -prune -o -xtype f -exec cmp {} /new-disk{} \;

(write this all on one line)

Slackware only. A basic Slackware installation ("A" series only) doesn't include the cmp command, so you won't be able to run this command if you have only installed the basic files. The cmp command is in the "AP1" series.)

This will only compare regular files, not character or block special files (in the /dev directory), sockets, etc., since the cmp command doesn't work properly with these. We would welcome suggestions on how to verify these "special" files.
8. Modify /new-disk/etc/fstab as appropriate

If your new disk doesn't have the same partitions or organization as the old disk, modify the file /new-disk/etc/fstab on the new disk as appropriate.

Make sure that the disk partitions (first column) correspond to the organization you'll have with the new disk, once the old disk has been removed, and that you're only mounting one partition at / as shown in the second column.

For more information on the format of the file /etc/fstab, see the Linux System Administrator's Guide, section 4, under Mounting and unmounting.

For swap partitions, use a line similar to this one:

/dev/hda1 swap swap defaults 0 0

9. Prepare LILO to boot the new disk

(Thanks to Rick Masters for helping with this.)

We're assuming that LILO is installed on the hard disk's Master Boot Record (MBR); this seems to be the most common configuration. You want to install LILO on what's presently the second hard disk but will become the first hard disk.

Edit the file /new-disk/etc/lilo.conf as follows:

disk=/dev/hdb bios=0x80 # Tell LILO to treat the second
# disk as if it were the first
# disk (BIOS ID 0x80).
boot=/dev/hdb # Install LILO on second hard
# disk.
map=/new-disk/boot/map # Location of "map file".
install=/new-disk/boot/boot.b # File to copy to hard disk's
# boot sector.
prompt # Have LILO show "LILO boot:"
# prompt.
timeout=50 # Boot default system after 5
# seconds. (Value is in tenths of
# seconds.)
image=/new-disk/boot/vmlinuz # Location of Linux kernel. The
# actual name may include a version
# number, for example
# "vmlinuz-2.0.35".
label=linux # Label for Linux system.
root=/dev/hda1 # Location of root partition on
# new hard disk. Modify this as
# appropriate for your system.
# Note that you must use the name
# of the future location, once the
# old disk has been removed.
read-only # Mount partition read-only at
# first, to run fsck.

Slackware only. Use image=/new-disk/vmlinuz.

If you're using a SCSI hard disk, you may have to add a line with initrd. See your existing file /etc/lilo.conf.

Install LILO on the new disk:

/sbin/lilo -C /new-disk/etc/lilo.conf

The -C option tells LILO what configuration file to use.
10. Make a boot diskette (optional)

If you wish, you can make a boot diskette, in case you run into problems when trying to boot the new disk.

Insert an empty diskette, format it, create a file system on it and mount it:

fdformat /dev/fd0H1440
mkfs.ext2 /dev/fd0
mount -t ext2 /dev/fd0 /mnt

Debian only. With Debian 2.x, use /dev/fd0u1440 instead of /dev/fd0H1440. With Debian 1.x, use /dev/fd0h1440, with a lower case h.

Debian only. With Debian 2.x, use superformat instead of fdformat. You can ignore the error mformat: command not found. With Debian 1.x, if you don't have the command fdformat, you can omit it if the floppy is already formatted. In this case, you should check the diskette for bad blocks by adding -c after the mkfs.ext2 command.

Slackware only. Use /dev/fd0u1440 instead of /dev/fd0H1440. With older versions, try /dev/fd0h1440, with a lower case h.

SuSE only. Use /dev/fd0u1440 instead of /dev/fd0H1440.

Copy all files in /boot to the diskette:

cp -dp /boot/* /mnt

Red Hat only. If the /boot directory contains both vmlinux and vmlinuz files (note the difference in the last letter), you only need to copy the vmlinuz files to the boot diskette. They are the same as the vmlinux files, except that they're compressed to save space.

Slackware only. Copy the file /vmlinuz to the boot diskette; use the command cp /vmlinuz /mnt.

Create a new file /mnt/lilo.conf as follows:

boot=/dev/fd0 # Install LILO on floppy disk.
map=/mnt/map # Location of "map file".
install=/mnt/boot.b # File to copy to floppy's
# boot sector.
prompt # Have LILO show "LILO boot:"
# prompt.
timeout=50 # Boot default system after 5
# seconds. (Value is in tenths of
# seconds.)
image=/mnt/vmlinuz # Location of Linux kernel on
# floppy. The actual name may
# include a version number, for
# example "vmlinuz-2.0.35".
label=linux # Label for Linux system.
root=/dev/hda1 # Location of root partition on
# new hard disk. Modify this as
# appropriate for your system.
# Note that you must use the name
# of the future location, once the
# old disk has been removed.
read-only # Mount partition read-only at
# first, to run fsck.

Install LILO on the boot diskette:

/sbin/lilo -C /mnt/lilo.conf

The -C option tells LILO what configuration file to use.

Unmount the diskette:

umount /mnt

11. Remove the old disk

Shut down the system and remove the old disk. Remember to modify the disk jumpers and the BIOS information to reflect the changes.
12. Reboot the system, modify LILO configuration file

Reboot the system. If you have problems, you can use the boot diskette you just make. To do so, you may have to modify your BIOS's boot-up sequence to A:, C:.

You should modify the file /etc/lilo.conf in case you later want to run LILO again. Here's an example of how the file can look:

boot=/dev/hda # Install LILO on first hard
# disk.
map=/boot/map # Location of "map file".
install=/boot/boot.b # File to copy to floppy's
# boot sector.
prompt # Have LILO show "LILO boot:"
# prompt.
timeout=50 # Boot default system after 5
# seconds. (Value is in tenths of
# seconds.)
image=/boot/vmlinuz # Location of Linux kernel. The
# actual name may include a version
# number, for example
# "vmlinuz-2.0.35".
label=linux # Label for Linux system.
root=/dev/hda1 # Location of root partition on
# new hard disk. Modify this as
# appropriate for your system.
read-only # Mount partition read-only at
# first, to run fsck.

Slackware only. Use image=/vmlinuz.
13. Acknowledgements

Thanks to Scott Christensen, Frank Damgaard, Alexandre Fornieles, David Fullerton, Igor Furlan, Jerry Gaines, Chris Gillespie, Nicola Girardi, Per Gunnar Hansoe, Richard Hawes, Ralph Heimueller, Gerald Hermant, Andy Heynderickx, Paul Koning, Hannu Liljemark, Claes Maansson, Rick Masters, Jason Priebe, Josh Rabinowitz, Douglas Rhodes, Valentijn Sessink, Kragen Sitaker, Stephen Thomas, and Gerald Willman.

This document may be translated into any language. If you do so, please send a copy of the translation to Konrad Hinsen <hinsen@cnrs-orleans.fr>.
Notes
[1]

Does this also apply to other Aptiva models?

MainMenu

Tue, 08 Jul 2008 00:19:00 GMT

WelcomeToTiddlyspot GettingStarted

SiteSubtitle

Tue, 08 Jul 2008 00:18:00 GMT

my reusable non-linear personal web notebook

SiteTitle

Tue, 08 Jul 2008 00:17:00 GMT

Blackburn's Wiki

Refreshingly Blue » Blog Archives » How To Remove External Repositories From Subversion

Thu, 03 Jul 2008 18:02:00 GMT

svn propedit svn:externals vendor/plugins

Source: Refreshingly Blue » Blog Archives » How To Remove External Repositories From Subversion