thunk wrote:And Baltistan begins his blitz. Present me informs he isn't done yet...
Isnt' done yet. Yes.
And I haven't done any blitzing in the last weeks.
And this is why:
I mustarded my computer for 3 weeks. And did not blitz then.
For not so recent anymore decree, this is one of my last disacchievments.
What did I do?
On my computer's HDD I had:
- sda1 (C:) - A primary fat32 partition with Windows XP[/spoiler]
- sda5 (D:) - A logical fat32 partition with lots of my files and also some programs
- sda6 - A logical ext4 partition with Debian 7.
- sda7 - A a logical swap partition
Some months ago I was playing a Windows hotdog with my cousin. Windows crashed when shuttinG down. It corrupted both C: and D: partitions.
Using some tools on the Debian OS I managed to recover sda5 (D) but not completely. One directory ("D:\Programy", where I had programs installed) was not recoverable. But all my files were ok. C: was so much corrupted that almost nothing could be recovered.
What to do next?
Reformatting C and D and reinstalling Windows would be an obvious option. I could not do it. I got Windows for free. Students of electronics at PWr could get some software (including Windows) for free. I was no longer a student. The license allowed me to still use the softwares after finishing the studies. But I was no longer allowed to install it. And I was not interested in buying it either. I don't need Windows, actually. I already got used to GNU/Linux which I like much more now. I installed XP only because it was available for free. Before that (until 2012, I think) I used Windows 98 as the primary OS. And I still have Windows 98, and Windows 3.11 on my redundant computers.
So I didn't change anything. I used the Debian OS and I could access all the files on sda5 from it. sda1 was not mountable.
But recently (about 6 weeks ago) I decided to change this. there where errors while accessing some directories on sda5 (but all the files were ok) and I was running out of free space on sda6 while sda5 occupied most of the hdd and had much free space which was unusable to me because it was a fat32 partition (no access control) mounted in read-only mode (to not increase the damage accidentally).
I copied all the data from sda5 to the botcastle. I copied all the data form sda6 to the botcastle. Then I used a partition manager software which booted from a liveCD. I removed sda5. I resized sda6 to take all the space that previously belonged to sda5 and sda6 except the first 7MB. I restarted the computer.
The OS didn't start. GRUB started but crashed. I could only use GRUB's command line with most commands unavailable. What I had to do was to boot the OS somehow and from it to restore GRUB (maybe it didn't survive the resizing). I couldn't. Trying to load the kernel resulted with a memory error.
I recorded a CD with GRUB on it. Using it it was possible to load the kernel but the OS still didn't start. It complained that it couldn't mount "/" and entered the kernel panic. I started another GNU/Linux from a liveCD and found out that that sda6 was no longer mountable. However GRUB could access the filesystem without any problems but for some reasons Linux couldn't (???). I also noticed that the CD GRUB saw the Debian partition as sda,5 and the swap as sda,6 while the original GRUB still saw them as sda,6 and sda,7. Maybe that's because the real sda5 was removed. So I inserted a placeholder partition to replace the old sda5. But I couldn't do it. The bootmanager couldn't create a partition smaller than 8 MB and there was only 7MB free space. So I used GParted from a Linux liveCD. After this, both GRUBs saw the partitions as: placeholder: sda7, Debian: sda5, swap: sda6. 7,5,6 instead of 5,6,7. Not what I wanted. I couldn't change the partition numbers from any of the partition managers. But I discovered what was wrong. The partitioning software I used doesn't support ext4 (there was no ext4 when they made it, I think). It interpreted the filesystem as ext3 instead and resized it as if it was ext3. But it was ext4, actually. (I could have resized it with GParted instead and avoid all the problems). That's why the filesystem was broken (but the files seemed ok because GRUB could access them). I tried to fix it using fsck and such but it wasn't successful.
Why not restore the system from the backup I made on the botcastle? Because I only saved the files but not the file ownership and access control information.
When (after 3 weeks) I went again to the place where my botcastle is. I reformatted everything, installed the OS again and copied all the importand data from the botcastle. I had to spend some time to recreate my configurations of things using files from previous installation.
During these 3 weeks I was using a GNU/Linux OS from a liveCD.
And I made another mustard. This time I used almost all the space for the Debian GNU/Linux OS but left a 4 GB partition at the beginning because I wanted to install FreeDOS on it. But last Thursday, when I wanted to do it I found out that I made a mistake and the partition has 4 MB instead of GB.
Well, 4 MB is still more than enough to have a perfectly working DOS but that's not what I wanted :/
And then, I noticed in a post by mrob27 a mention of Homestuck.
I already heard the name before but didn't know much more about it. I think I saw the first page of it once.
I went to see what it is...
and spent 3 weeks reading it. I finished yesterday.
I liked it.
Wow, they have object generators! (but with a different name)
And sending messages through time! And things!
make these things these days?
(First Kieryn, then this)
Well, I have been warned
the possibility of this happening.
s:Just 5 pages later
b thiks about having more than one world to see what happens if you do something and what if you don't. EE EE EE
In late 2010 / early 2011 I was drawing some comic. I needed a "random" 3-digit number. What was it?
I later reused it because why waste such a good random number?
And now I read this and find this number there as well??? : :
. . .