Canuks are good at this stuff too!
What was that kid thinking?!
Using such blatant hacking tools like that new fangled curl!!!!
Curl is only a little bit older than the kid is.
Maybe they should drop the damned charges and hire him to go over the documents that are posted on that site to make sure they are in the prescribed condition to be publicly available. He might be clever enough to figure out the search function for pdfs even! I am pretty sure there is probably a similar tool that would look at batches of pdfs at the same time. Might even be older than curl.
People don't read the fine print. Well most don't. When we bought our Win98 box I actually read the damned eula. Should have done that before getting the box built. Would have gotten the same thing built but would have gone with the Red Hat distro probably (unless the guy that built it suggested something else - we had only considered RH because it was the only one we had discovered).
Wife has a FB account. I read that crap and there is really no way I would have an account.
Read this a while back
This is from today
This sounds like fun
This is entertaining. Didn't realize this was such an important aniversary.
We need to plan for this
I suggested to my favorite bartender (wife) that she should plan something for the bar. This was a joke. I was pretty confident that the 2 of us may well be the only people in town to actually have even heard of that book let alone read it. She thinks their could possibly be 1 other person. So I guess that is out for the big town of Broadus.
At least I don't have to pick out a towel. The others would get jealous.
Just stuff I read on The Reg and found of interest.
What I would like to know is what kind of rat is about that size but actually very brown with a fairly bushy haired tail. We got infested by that sort "up on top" at the ranch. Haven't seen them anywhere else so they are not real common. Eat dry cat food very happily.
Was feeding at the other end of the ranch and went into the barn there to check the cat food supply and one of the buggers was eating. Wasn't very nervous about me coming in. Looked more irritated at having dinner interrupted. Didn't run off until I was about 10 feet away.
At first glance I thought it was a squirrel with a really bad case of lice or something due to the condition of the tail. Fairly fluffy furred critter. Fur is about 1/4 to 5/8 inch long with some under fur in the winter.
Had the cat pan (old skillet) up on the deck of the hay swather where you stand to get into the cab. Wasn't an easy place for something that size to get onto except by being pretty good at leaping.
Asked the boss about them and they are apparently the only kind of rat she was familiar with. Told me to use small animal leg traps to catch them. Sounded weird to me but there were some in the shop in pretty bad condition so I cleaned up about 3 of the buggers and got them back into working order.
Took them over to the other place and put one in the bottom of a 5 gallon bucket with a tire rim on top of it. Figured that would keep the cats out of the the trap and secure the trap as the boss claimed they would drag the things off. Those traps are pretty deadly and not all that easy to drag around really. Inside a bucket with a wheel rim should easily hold them was my thinking.
Caught one in that setup. Thing somehow could leap from the bottom of that bucket to the hole in the center of the wheel and actually managed to get out with the trap. Damned tough rats. Changed to wiring the traps to the wheel.
Killed 6 or 8 of them in about 18 months and never saw any again. Would take "cake" (field pea/alfalfa mix pellets for cattle) as bait some managed to get out of the bucket and drag the wheel a little ways (inches).
The ranch cats, particularly over there where no one lived, were kind of tame. Some you could pet even. They didn't eat much cat food in good weather and preferred to go kill something. Would kill things up to jack rabbits which are at least 6 times the size of those rats. Were hell on mice.
Pretty much moved out of the barn until I started setting traps. The were not in there when I saw that first rat. Came in when I was there to eat and apparently stayed somewhere else until those rats were gone.
I think it much be a colony type rat that lives in small (family?) groups and don't breed themselves out of food. Actually kind of a good looking animal. Put me more in mind of a muskrat than anything else.
I am more familiar with black rats which sound more like what that article is talking about than norway rats which are generally not quite that big. But even black rats can be pretty easily controlled with the sort of rat traps you find in hardware stores.
That sort of trap may have been used as food by the ones in the barn. Certainly would not have killed them and probably not even upset them much. Only permanent damage I could see that sort of trap doing would be to damage a tail enough to have some of it die off and leave the rat with a stubbier tail.
What a whiny bunch of wimps.
Out and Abouter (of course pronounced Abooter) has it about right
This is a great looking cannon. Fires a 40 pound projectile at 984.25 feet/sec. Probably not good to be anywhere near the interior wall though. Like within 15 feet.
Might be best to have one in every class room to use to get out with. May be slightly costly to repair the building after use though.
I would be a bit concerned if talking to a "defense consultant" that really has no clue as to the physics of projectiles.
You could blow a hole without a lot of structural damage or need more than a 4 foot "safety" zone inside the wall and not have any major rebuilding of the wall after you were finished using the hole.
People on the outside would be pretty safe within a very few feet of the impact though so it would be good for storming a room/building.
Have been having a lot of FUN lately with hdd fs problems.
Keep in mind that none of these drives can be described as anything but old. Box may be new(ish) but the drives are all ones that were used with the old Dell for years. At least one is probably 9 years older and the rest are over 5.
Have 4 internally. 2 of those are data storage only and the other 2 are system and data.
Sda has one /home partition for my stable install and all the / partitions for the other 5 installs and a data partition.
Sdb has the home partitions for the extra 5 installs and a data partition.
Sdc has a data partition on it.
Had a couple heat related crashes involving Thunderbird with enigmail and large attachments. That is a separate mystery but the crashes corrupted some blocks on both sdb and sdc to the point where I needed to run e2fsck on them to get them to work at all.
Sdc seemed to be the worst case. Cleared out some room on my experimental installs external and on my Loaner drive and on another external and got that data recovered and moved to those places. Then did a dd security type wipe of the drive and the mbr for that drive and reformatted and it seems to be working fine now and has the data back on it.
Then I cleaned up enough room to deal with the sdb contents on to the externals and did the same sort of backup to them. Most of the data was backed up anyway but I did loose some from both drives. Obviously nothing important. You can tell because it wasn't backed up.
But while doing that transfer of info, while very successfull really, the problem with sdb got worse. Can't do much with it now. So I figure this is a good time to have a learning experience.
Usually if I shut down and make sure to power unit and then reboot the sdb drive is read. I am not mounting it at all from any fstab files. I am using a pair of new partitions on the loaner drive (external) for the /home partition for my pet Lizards (Stoned and Lounge) and for VictimH which is the /home for 3 other installs. Currently I have just fired things up and logged into Stoned Lizard (Debian testing) and could see during bootup (not quite) that sdb was not reading correctly.
Opening a # terminal I take a look at
This is pretty standard on booting just to see what is happening. This time I have listed sda, sdc, sdd and sde. Sde is the external and there is no sdb listed. This is not always the case when sdb is not cooperating at all. There are time with a boot to any install where I will get an sdb listed which and no sde for the external or just sda, sdb and sdc if booting to my stable install with both partitions on the sda drive and the external turned off. Basically in both those cases real sdb is not detected at all and so sdc becomes sdb and so forth.
On the other hand I just was on Lounge Lizard (Debian Sid) and blkid gave a full read on the 4 partitions on sdb. Stoned-home, VictimH, Info-Spring and swap.
When that happens, which is the usual case, I can mount a partition from there and open it in Thunar and see the files and read them fine, open in the appropriate applications and even save a file to it. This is true for all 3 of the data type partitions. But you can't mount a second one. Drive is now no longer readable.
Open up gparted when sdb is shown by blkid and it will show all the partitions and all the data provided there looks pretty good. Usually will have the triangle warning emblem up for one, two or all three data partitions because it can't figure out which FS is used on the partition. But the content sizes are right (used/unused). Do anything on some other drive like relabel a partition on sdd and then gparted will no longer read sdb either. Will show it with everything in the graphic display just gray and nothin in the lower pane.
I sdb partitions are shown in blkid and I open another tab and run e2fsck I will sometimes be surprised by the plain command telling me the file system is clean. Run
# e2fsck -f /dev/sdb
and it immediately finds a few errors and I just keep hitting enter until they clear. This usually will be about 4 to 6 blocks with errors. It then exits with the comment that there are more errors. Repeat and it can't find the superblock. This is all ext4 by the way.
Using their suggested alternatives comes up blank.
And, of course, if you then run blkid there is no entries for sdb at all again. Reboot with a complete shutdown and you can do it all again.
Here is out put before doing some procedure the other day
root@stoned:/home/tom# blkid /dev/sda5: UUID="80cba5b3-07c6-49eb-b975-9fde47ede7e2" TYPE="ext4" PARTUUID="0003b632-05" /dev/sda6: LABEL="Main-home" UUID="48fbbed6-ce39-459a-8f60-68c760350156" TYPE="ext4" PARTUUID="0003b632-06" /dev/sda7: UUID="47b93b44-ca76-441d-a921-11547ad2e39d" TYPE="swap" PARTUUID="0003b632-07" /dev/sda8: LABEL="Stoned-root" UUID="79d2035f-7b77-4627-b5fa-fd546ed52d48" TYPE="ext4" PARTUUID="0003b632-08" /dev/sda9: LABEL="Lounge-root" UUID="8d58c5f3-4814-4687-84a3-dd1b346768ad" TYPE="ext4" PARTUUID="0003b632-09" /dev/sda10: LABEL="Linux-Info" UUID="d9fa27f0-4985-4b44-93e7-843df728f377" TYPE="ext4" PTTYPE="dos" PARTUUID="0003b632-0a" /dev/sda11: LABEL="Mageia5" UUID="d250598f-c14d-4df0-86f9-27daa3bd8bea" TYPE="ext4" PARTUUID="0003b632-0b" /dev/sda12: LABEL="VictimOS" UUID="d6ec9624-d51d-4be9-a250-3d1732594483" TYPE="ext4" PTTYPE="dos" PARTUUID="0003b632-0c" /dev/sda13: UUID="467c050b-3c55-4c04-9bc6-22aca41a3f07" TYPE="ext4" PARTUUID="0003b632-0d" /dev/sda14: UUID="f1f9b2b7-a2ed-45a3-aa1a-003660088a8f" TYPE="ext4" PARTUUID="0003b632-0e" /dev/sdb5: UUID="2120dded-2ab8-40a7-8bfc-1e9bbce849c7" TYPE="swap" PARTUUID="0008742d-05" /dev/sdb6: LABEL="Stoner-home" UUID="cf81c8aa-9f62-47ec-9eb3-ec760c8d00cf" TYPE="ext4" PTTYPE="dos" PARTUUID="0008742d-06" /dev/sdb7: LABEL="InfoSpring" UUID="4e351ba0-bd83-44b7-aa73-52e0550e1a77" TYPE="ext4" PARTUUID="0008742d-07" /dev/sdb8: LABEL="VictimH" UUID="aa15d094-5703-474b-b6cd-d7975194cece" TYPE="ext4" PARTUUID="0008742d-08" /dev/sdc5: LABEL="Store" UUID="8dcb08ea-eb26-49be-a119-96767d406a89" TYPE="ext4" PARTUUID="d12beac5-05"
And after covering the same range from sda to sdc
root@stoned:/home/tom# blkid /dev/sda5: UUID="80cba5b3-07c6-49eb-b975-9fde47ede7e2" TYPE="ext4" PARTUUID="0003b632-05" /dev/sda6: LABEL="Main-home" UUID="48fbbed6-ce39-459a-8f60-68c760350156" TYPE="ext4" PARTUUID="0003b632-06" /dev/sda7: UUID="47b93b44-ca76-441d-a921-11547ad2e39d" TYPE="swap" PARTUUID="0003b632-07" /dev/sda8: LABEL="Stoned-root" UUID="79d2035f-7b77-4627-b5fa-fd546ed52d48" TYPE="ext4" PARTUUID="0003b632-08" /dev/sda9: LABEL="Lounge-root" UUID="8d58c5f3-4814-4687-84a3-dd1b346768ad" TYPE="ext4" PARTUUID="0003b632-09" /dev/sda10: LABEL="Linux-Info" UUID="d9fa27f0-4985-4b44-93e7-843df728f377" TYPE="ext4" PTTYPE="dos" PARTUUID="0003b632-0a" /dev/sda11: LABEL="Mageia5" UUID="d250598f-c14d-4df0-86f9-27daa3bd8bea" TYPE="ext4" PARTUUID="0003b632-0b" /dev/sda12: LABEL="VictimOS" UUID="d6ec9624-d51d-4be9-a250-3d1732594483" TYPE="ext4" PTTYPE="dos" PARTUUID="0003b632-0c" /dev/sda13: UUID="467c050b-3c55-4c04-9bc6-22aca41a3f07" TYPE="ext4" PARTUUID="0003b632-0d" /dev/sda14: LABEL="VictimO" UUID="f1f9b2b7-a2ed-45a3-aa1a-003660088a8f" TYPE="ext4" PARTUUID="0003b632-0e" /dev/sdc5: LABEL="Store" UUID="8dcb08ea-eb26-49be-a119-96767d406a89" TYPE="ext4" PARTUUID="d12beac5-05"
I find this really fascinating. Can't say I understand it a bit but still really interesting.
I tried to use dd to just wipe the drive. Had no effect what so ever.
I also, early on, tried testdisk on the drive but it couldn't find any partitions at all.
So, I hear you say, "what is the problem? The drive is bricked."
This is probably true. But I can, on occasion at least, read the drive. I have found on some drives that really seem pretty bad that doing some sort of radical wipe on them makes them capable of further use. This drive obviously is useless as it is. There fore I would really like to try to recover it back into usable condition if at all possible. This is just for educational bennefit. Drive is obviously not something even some nut case like me would ever trust. So I see no problem experimenting on it.
This is a Seagate drive of the ST3 variety and 500GB.
Another place, come to think of it, where I can see if the drive is responcive at all is in the boot menu (F8 on this AMD MB) where if it shows up in correct order with the other drives you can be sure that it is cooperating.
Which brings us to other things you may want to know such as this is a new box for me. It is a uefi type MB but I am booting legacy mode mbr because I just slapped the sda and sdb drives out of the dead Dell into this box.
One tool I have never used and am not sure about at all is hdparm which has a way to do a security wipe and works with sata drives fine apparently if you simply use sdx instead of hdx. Looking into that I discovered sdparm which is newer, designed for sata drives but doesn't seem to be nearly as capable as hdparm.
I figure my time is limited as far as having any slim chance of success with this drive so I would love to here any suggestion as to how to attempt to rescue the thing. Data recovery is NOT at all an interest. I have all I need off of it. I just want to try and put it back into service if I can.
My externals are all USB2, not sure this would work even on USB3. I have both USB2 and 3 ports along with a couple Sata ports but basically this will have to be done internally so I have not removed the drive at this point.
When I can afford it I am getting 2 new 500 GB drives and putting them in and setting them up for uefi boot and then use the best drives for data storage untill I can get another pair of new drives. I know it works because I have used uefi on here in some installs on an external. Debian installer, last time I tried it is crap for setting up the efi partition so that it actually works. But the Mageia installer works fine so you can do that and then install anything you want and ditch Mageia.
For some reason I can't seem to get the contents of that partition in manually and get them to work. Not sure what the problem is. Has to be with me as I can't even copy working contents from an efi partition and then create one - put that content back into it and have it work. But that is not a concern for me at all at this point because I know how to work around it. Once set up it works fine as long as you don't mess with it no matter what you do install wise.
I edited this to fix the code boxes. BBCode tags don't work on this forum software. To set a code tag, you need to put a backwards apostrophe before and after the text. I'll write a post about it to explain it better.
Edit: Some more code-tags, and some typos. Leppie
Pretty serious stuff.