csh
/
y.st.
forked from y.st./y.st.


			
				
					
						
						
							123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190
							<?xml version="1.0" encoding="utf-8"?>
<!--
                                                                                     
 h       t     t                ::       /     /                     t             / 
 h       t     t                ::      //    //                     t            // 
 h     ttttt ttttt ppppp sssss         //    //  y   y       sssss ttttt         //  
 hhhh    t     t   p   p s            //    //   y   y       s       t          //   
 h  hh   t     t   ppppp sssss       //    //    yyyyy       sssss   t         //    
 h   h   t     t   p         s  ::   /     /         y  ..       s   t    ..   /     
 h   h   t     t   p     sssss  ::   /     /     yyyyy  ..   sssss   t    ..   /     
                                                                                     
	<https://y.st./>
	Copyright © 2015 Alex Yst <mailto:copyright@y.st>

	This program is free software: you can redistribute it and/or modify
	it under the terms of the GNU General Public License as published by
	the Free Software Foundation, either version 3 of the License, or
	(at your option) any later version.

	This program is distributed in the hope that it will be useful,
	but WITHOUT ANY WARRANTY; without even the implied warranty of
	MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
	GNU General Public License for more details.

	You should have received a copy of the GNU General Public License
	along with this program. If not, see <https://www.gnu.org./licenses/>.
-->
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
		<base href="https://y.st./en/weblog/2015/05-May/11.xhtml" />
		<title>My laptop takes it&apos;s last breath &lt;https://y.st./en/weblog/2015/05-May/11.xhtml&gt;</title>
		<link rel="icon" type="image/png" href="/link/CC_BY-SA_4.0/y.st./icon.png" />
		<link rel="stylesheet" type="text/css" href="/link/basic.css" />
		<link rel="stylesheet" type="text/css" href="/link/site-specific.css" />
		<script type="text/javascript" src="/script/javascript.js" />
		<meta name="viewport" content="width=device-width" />
	</head>
	<body>
		<nav>
			<p>
				<a href="/en/">Home</a> |
				<a href="/en/a/about.xhtml">About</a> |
				<a href="/en/a/contact.xhtml">Contact</a> |
				<a href="/a/canary.txt">Canary</a> |
				<a href="/en/URI_research/"><abbr title="Uniform Resource Identifier">URI</abbr> research</a> |
				<a href="/en/opinion/">Opinions</a> |
				<a href="/en/coursework/">Coursework</a> |
				<a href="/en/law/">Law</a> |
				<a href="/en/a/links.xhtml">Links</a> |
				<a href="/en/weblog/2015/05-May/11.xhtml.asc">{this page}.asc</a>
			</p>
			<hr/>
			<p>
				Weblog index:
				<a href="/en/weblog/"><abbr title="American Standard Code for Information Interchange">ASCII</abbr> calendars</a> |
				<a href="/en/weblog/index_ol_ascending.xhtml">Ascending list</a> |
				<a href="/en/weblog/index_ol_descending.xhtml">Descending list</a>
			</p>
			<hr/>
			<p>
				Jump to entry:
				<a href="/en/weblog/2015/03-March/07.xhtml">&lt;&lt;First</a>
				<a rel="prev" href="/en/weblog/2015/05-May/10.xhtml">&lt;Previous</a>
				<a rel="next" href="/en/weblog/2015/05-May/12.xhtml">Next&gt;</a>
				<a href="/en/weblog/latest.xhtml">Latest&gt;&gt;</a>
			</p>
			<hr/>
		</nav>
		<header>
			<h1>My laptop takes it&apos;s last breath</h1>
			<p>Day 00065: Monday, 2015 May 11</p>
		</header>
<p>
	Evolution is being a pain about encryption.
	It refuses to encrypt letters to people unless I have either signed their key to verify that I trust it or I tell Evolution to trust all keys.
	The fact that I want to encrypt a letter to someone does not necessarily mean that I truly trust that the key belongs to someone in particular.
	I send letters to people I don&apos;t know and do not trust.
	I still want the <abbr title="National Security Agency">NSA</abbr> to keep out, so I still need these letters encrypted.
	I&apos;ve told Evolution to trust all keys for now, but that means I cannot distinguish between keys that I honestly trust and keys that I do not trust.
	This is suboptimal.
	I much prefer the way Claws Mail handles it.
	It warns you that the key is untrusted when you try to send the letter, but allows you to use the key anyway if you like.
</p>
<p>
	I decided to plug in an external mouse to deal with my built-in one locking up continually on me.
	This solution, while far from ideal, has either comejustin time orhasmadethings worse.
	The built-in mouse no longer functions at all, even right after waking the machine.
</p>
<p>
	It seems that Cricket finished cutting off my service a full month ahead of when I thought they would.
	I&apos;m not really prepaired for this.
	It will be about a month before the <abbr title="subscriber identity module">SIM</abbr> cutter arives, and the <abbr title="subscriber identity module">SIM</abbr> card for the new plan is too large.
	This is what I get for counting on a plan that I wasn&apos;t paying for any more.
	It was a gamble from the start, and it did not pay off.
	Then again though, it did buy me time to find the cheap MetroPCS plan, so in the end, I think it will have worked out for the better.
</p>
<p>
	Maybe tomorrow I will start a three-month experiment, and actually use the MetroPCS tablet.
	Last time I tried such an experiment, it made me appreciate my Replicant device all the more.
	While Replicant lacks certain useful features such as wifi connectivity, it more than makes up for it in simple features that Android has no excuse not to have.
	Android really should have basic ext4 support on <abbr title="Secure Digital">SD</abbr> cards,for one.
	The internal storage used by the system is formatted as ext4, so the ext4-handling code is all in there, yet for some idiotic reason, Android can&apos;t mount an ext4 <abbr title="Secure Digital">SD</abbr> card, claiming the <abbr title="Secure Digital">SD</abbr> card is corrupted or blank.
	To transfer my music files to the <abbr title="Secure Digital">SD</abbr> card, I need the character set support ext4 has.
	<abbr title="File Allocation Table">FAT</abbr> simply won&apos;t cut it.
	Not to mention that <abbr title="File Allocation Table">FAT</abbr> file systems are so easy to break ...
</p>
<p>
	The other option is to go running to T-Mobile proper.
	I could cancel my plans to attempt to get the MetroPCS $15 <abbr title="United States Dollars">USD</abbr> per month on my Replicant device and just get the T-Mobile $20 <abbr title="United States Dollars">USD</abbr> per month plan.
	The T-Mobile plan is better in a couple ways anyway.
	First of all, it doesn&apos;t require buying a specific device to get the plan.
	Second, they plan is entirely <abbr title="Short Message Service">SMS</abbr>-free!
</p>
<p>
	On second though, both of those options are bad ideas.
	I should at least try to get the MetroPCS plan working, as the <abbr title="Short Message Service">SMS</abbr> feature would keep my mother happy.
	But at the same time, I can&apos;t function well on Android, I&apos;ve already proven that.
	The proper choices would be to ether wait the month or so until my <abbr title="subscriber identity module">SIM</abbr> cutter arrives or to attempt to cut the <abbr title="subscriber identity module">SIM</abbr> card by hand.
	Either way, the <abbr title="subscriber identity module">SIM</abbr> card <strong>*must*</strong> be cut soon after getting the device.
	I have seven days from the time that I get the MetroPCS tablet to say &quot;This device does not satisfy me.&quot; and get my money back.
	If the <abbr title="subscriber identity module">SIM</abbr> card cannot be cut, fitted into my Replicant device, and the bring working service to it, there is no point in me buying this $150 <abbr title="United States Dollars">USD</abbr> device that I won&apos;t even use anyway.
</p>
<p>
	The first of Yst Dawson&apos;s two packages arrived today, ahead of schedule.
</p>
<p>
	<strong>*(At this point in my writing, my laptop gave out on me and I began writing my weblog entries on my mobile.)*</strong>
</p>
<blockquote>
	<p>
		Day 0:
	</p>
	<p>
		My computer has just given up the ghost.
		With both my computer out of commission and my mobile out of service, I now have no connection to the network.
		I will attempt to keep a personal record of what is going on while I&apos;m disconnected, but without an actual keyboard I may not be as verbose as usual.
	</p>
	<p>
		As I had been saying before my computer died, my new mobile protective case came in today, ahead of schedule.
		Unlike my old case the new one seems to be built to be opened and closed repeatedly.
		For that reason I decided to try it out early because the only reason I have been wanting to wait was to avoid extra damage to the case from opening the case more times than necessary.
		The new case does seem more durable, but at the same time, it is harder to push the hardware buttons and the main on-screen buttons.
	</p>
	<p>
		I&apos;m not sure what to do with this.
		I feel trapped.
		I need to get ahold of another laptop as soon as possible.
		Luckily, my most recent backup is from yesterday, so even if I can&apos;t recover my hard drive, I shouldn&apos;t lose much.
		I do hope to recover the data from my laptop hard drive though, as it contains the rest of today&apos;s web blog entry, which I had been writing when the computer started messing up.
		At first, the control keys on the laptop quit working.
		It is when I went to restart the machine in an effort to get the keys to function again, that the computer quit working altogether.
		It won&apos;t even show signs of even starting to boot.
		The power button simply does nothing.
		I hope to be back online before my canary expires, but I have no guarantee that this is going to happen.
		I will probably try to get down to the second-hand computer store on Wednesday, as I have the day off.
		I would not be able to buy one right away, but I will be able to explain what I need from them and see if they are willing to help.
	</p>
	<p>
		I tried putting the battery pack in my laptop, and for some reason, the laptop booted once more.
		I took the opportunity to backup the one file that I did not have backed up from yesterday, which was a partial weblog entry from today.
		I also updated the copy of my KeePassX database on my mobile as well as copied my <abbr title="Pretty Good Privacy">PGP</abbr> key over.
		It&apos;s not like the files will do me any good on mobile though, as I have no network connection.
		I should have taken the opportunity to update my canary to state that a could be away for an extended period of time and let a few certain people know via email that I&apos;m fine.
		However, I got cocky and decided to experiment.
		I shut down my laptop and tried to boot it back up.
		It would not boot.
		I had one opportunity to get some last minute things done, and that was all.
	</p>
</blockquote>
<p>
	I couldn&apos;t update my <a href="/a/canary.txt">canary</a> today, as I was cut off from my Web/ssh server.
</p>
		<hr/>
		<p>
			Copyright © 2015 Alex Yst;
			You may modify and/or redistribute this document under the terms of the <a rel="license" href="/license/gpl-3.0-standalone.xhtml"><abbr title="GNU&apos;s Not Unix">GNU</abbr> <abbr title="General Public License version Three or later">GPLv3+</abbr></a>.
			If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
			My address is in the source comments near the top of this document.
			This license also applies to embedded content such as images.
			For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
		</p>
		<p>
			<abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
			This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2015%2F05-May%2F11.xhtml"><abbr title="Extensible Hypertext Markup Language">XHTML</abbr> 5.1</a> specification and uses style sheets that conform to the <a href="http://jigsaw.w3.org./css-validator/validator?uri=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2015%2F05-May%2F11.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
		</p>
	</body>
</html>