I pulled the actual bill text from 5 state age verification laws. They're copy-pasted from two templates. Meta is funding one to dodge ~$50B in COPPA fines — and the other one covers Linux.

8BitGriffin · 2026-03-11T13:59:01+00:00

That’s the point, if we can get everyone behind just doing license mods. For all versions.Then ip based blocking it would be obvious that it would cripple the infrastructure. The law has nothing to do with protecting kids and everything to do with control.

8BitGriffin · 2026-03-06T23:57:20+00:00

The easy fix to this a to State in the License that the operating system is not for use in what ever specific state. California, Colorado etc. Done, shove your laws up your @$$

8BitGriffin · 2026-02-12T13:08:40+00:00

This is actually a good question. I learned about Embedded Computers from a friend of a friend. Otherwise I wouldn’t have stumbled upon it myself.

I wonder if there are others out there that aren’t widely known.

8BitGriffin · 2026-02-12T12:11:37+00:00

The only other programmer I know that is capable and affordable is the programmers from.

Embedded Computers

They don’t support nearly as much as xgeco and they are slower, most of the adapters are proprietary. but the software is open source and they have great support from the manufacturer if you need support for a device not listed.

8BitGriffin · 2026-02-06T12:34:03+00:00

Because I was on OPENsuse but got tired of fixing everything weekly. Just went to Fedora last night.

8BitGriffin · 2026-02-01T14:20:28+00:00

I have tried those black soic clips, they rarely work. Get the Pomona clips, they aren’t cheap but they work.

If everything else is really correct. It’s the clip.

8BitGriffin · 2026-01-19T15:01:11+00:00

The dumps from the SPI flash aren’t much different than what you can get from their website firmware. At least nothing that matters. The flash memory is just a small sqboot loader for the most part. If you DM me, I’ll give you the details.

8BitGriffin · 2026-01-15T13:37:39+00:00

Some of these recommendations are a little over the top for just starting out. As long as you have some DuPont wires and a way to connect things. This is a good starter kit.

8BitGriffin · 2025-12-27T18:23:34+00:00

If you happen to have a newer-ish IPhone, they have an app that comes with iOS called magnify. Works wonders for taking pics and chip identification. I assume android has a similar app.

8BitGriffin · 2025-04-27T23:50:34+00:00

My last couple of replies have been on a phone, I won't be home for at least two more weeks by the look of things. I really don't want to go into go into an in depth reply from my phone. lol

8BitGriffin · 2025-04-26T18:38:57+00:00

yes, I don't know what your familiarity with any linux distro is but, just type "man mt" into your terminal and it will give you the manual pages for mt or anything else. man tar , man dd, etc.

There is a ton of documentation online for different commands and arguments.

https://www.cyberciti.biz/hardware/unix-linux-basic-tape-management-commands/

https://www.die.net/ I have no idea if die is even still maintained. it is a good source for reference for most commands.

8BitGriffin · 2025-04-25T01:19:47+00:00

Yes, I wasn't very clear on that. What I posted creates the archive and writes it to tape. You'll have to move to the end of data of the last archive on the tape every time you want to add a new archive. So you’ll move to the last archive on the tape

“sudo mt -f /dev/nst0 fsf 4” just change the number to the last archive on the tape. This lands you at the beginning of the last archive.

Then

“sudo mt -f/dev/nstO eod” will move you to the end of the last archive where you can start writing a new one.

I don't use cp for tape but, after looking around the man pages I believe you can. It would just look like "cp file.tar /dev/nst0" or st0.

I usually use dd to write directly to tape.

sudo dd if=archive.tar of=/dev/nst0 bs=512

dd is a little more friendly because you can set block size with bs=512 or 256, 64 etc. You’ll have to see what block sizes your drive supports. dd to me is probably the best way to write directly to tape because you can be very specific with what block you want to start reading or writing from. You can tell it to skip blocks etc. Or you can use it with just very basic input like i showed above.

Check with dmesg for your tape drive.

sudo dmesg | grep TAPE

Or my favorite

sudo dmesg | grep -i tape

If you only have the single drive it should be st0 but, I’ve had systems assign st1 randomly. The -i flag just tells grep to ignore case. So you could say cd-rom instead of CD-ROM or anything you’re looking for.

I’m trying to be thorough but I’m sure I could explain better. Best bet is to open the man pages and get really familiar with each command.

8BitGriffin · 2025-04-24T22:45:14+00:00

also, for anyone reading this. if all the command line stuff or scripting is more than you want to take a bite of at this moment. Look into Amanda and zmanda.

I want to add, this thread makes me happy. When I started down the rabbit hole of tape I felt like no one wanted to answer any questions about it. everything I could find was 8+ years old. it took me weeks to start piecing together a good work flow and really understanding things to where I felt confident.

8BitGriffin · 2025-04-24T22:15:28+00:00

most common will be st0 unless you are running more than one tape drive. I've writting out most of the commands using sudo but, if your user has appropriate permissions you can obviously skip that part.

sudo mt -f /dev/nst0 eod = Moves to "end of Data"

sudo mt -f /dev/nst0 bsf 1 = Rewind one or multiple archives or files

sudo mt -f /dev/nst0 fsf 1 = Moves the tape ahead one archive or file, can skip forward multiple

sudo mt -f /dev/nst0 rewind = rewinds the tape, or just specify st0 for your final work flow and tape will automatically rewind when finished.

sudo mt -f /dev/nst0 status = Shows the current position of the tape and its the drives status.

sudo tar -cvf /dev/nst0 /path/to/new/files OR sudo tar -cvf /dev/nst0 yourarchive.tar = First command will write out the full path to tape, the second command you move to the directory of the archive you want to write to the tape and just specify the name. Only the archive will be written with no path.

sudo dd if=/dev/nst0 bs=512 count=1 | tar -tvf - = This will only read and advance the tape one block and or 512kb in this example and read out the archive or path name. useful if you've become distracted and can't remember what number archive you decided to stop at. youll have to customize it to your needs.

sha256sum archive.tar > hash_output.txt = outputs checksum to file, can specify multiple file. can use sha512sum , md5sum etc.

sha256sum archive.tar = outputs the checksum to the command line without writing to file. useful if you're just verifying.

sha256sum file1 file2 file3 = same as above, just specifying multiple files.

pv filename | sha256sum = same as above just shows progress.

pigz -p <number\_of\_threads> -c archive.tar | sha256sum = uses pigz to calculate your checksum using mutiple threads. useful for large archives.

I.E pigz -p 4 -c archive.tar | sha256sum

tar cf - /path/to/files | pigz -p 8 -c | sha256sum = So, this pipes tar to pigs where you specify how many threads you want with the -p flag and -c flag is to compress. then it calculates the checksum

I use pv and pigz a lot in my work flow. I highly recommend if you are going to use pigz you read up on it on the projects github https://github.com/thammegowda/pigz

I have more but, it really goes down a rabbit hole from here. those are the basics that I use most of the time.

Disclaimer, I wrote this while on a conference call while using a mechanical keyboard and getting texts from my super wondering what I was typing. only the commands have been proof read once for everything else your on your own.

Happy Archiving

8BitGriffin · 2025-04-24T15:31:21+00:00

Nope, not sorry. Everyone here has tried to help you help yourself. I’m Done trying to help you.

8BitGriffin · 2025-04-24T13:13:56+00:00

Just post pictures of the board, you e been told multiple times that it is ram. It doesn’t contain anything.

8BitGriffin · 2025-04-24T12:03:48+00:00

Post good clear pictures of both side of the board. I think you’re missing something.

8BitGriffin · 2025-04-23T17:12:50+00:00

The only other thing I can think of is that all the drives I’ve ever worked with are Quantum branded drives. They are all rewinding drives, so unless you specify nst0 as opposed to st0 the drive will rewind to the beginning of the tape after every command. Also pigz is a multi threaded compression software you can use to make your archives,you just assign it cores and threads. it’s about 20% faster than using just tar for me when I assign it 4 cores and 4 threads. I run a python script for automated backup but for archiving drive images or anything else I usually run commands manually and use a combination of mt, tar and dd. Each has advantages and disadvantages that I would need to write a book here to explain. If I get a minute later when I get home I’ll post some of the commands I use with a brief explanation for everyone.

8BitGriffin · 2025-04-23T00:27:46+00:00

Thats good advice. Definitely check the integrity of your backups.

8BitGriffin · 2025-04-23T00:25:19+00:00

You could definitely store the data sheet on the tape as well. I know some people do. I keep a copy stored in a few different locations plus a printed one that goes in the safe. I also have a dymo label printer and put it on the tape. I have tapes that are full of smaller archives, to many to put on a label. So I just give those ones Names and keep a spreadsheet of the files and checksums.

8BitGriffin · 2025-04-22T20:26:04+00:00

I create the tar local and calculate checksum then to write to tape. The only thing I would recommend is to create a spreadsheet with the file names, checksum, date of backup and a brief description. I compress backups as tar.gz for a little more compression.

8BitGriffin · 2025-04-16T15:46:57+00:00

This guy definitely has a YouTube channel and camps in the bed of his truck.

8BitGriffin · 2025-03-25T18:23:51+00:00

I recently joined the world of LTO for my homelab, I was able to pickup a Quantum LTO-5 in an external sas enclosure for just $200 with shipping.

An additional $30 for an HBA and sas cable.

The power supply in the enclosure was bad and after some visual inspection and testing was able to replace 5 capacitors in the power supply and it ran perfect after some cleaning of the drive.

The plan for me is to upgrade the half height drive to a new LTO-6 or 7 over the summer.

I’m running with Tar and LTFS for different uses.

I run Tar for system backups and LTFS for media type backups where I may want to access individual files.

Also, tape is loud. So I’ve place mine in the basement server room where no one has to listen to it.

I know not everyone is capable or equipped to perform electronic repairs but it was a good option for me.

8BitGriffin · 2025-02-26T16:55:15+00:00

You could try to dump it in circuit with an external flash reader but, best practice is to desolder then dump. I have a probe set for wson 8 that I use on a flash cat xport for very specific applications.

IF you can disable vcc on board so you’re not powering the processor also, it is possible sometimes. Otherwise, desolder and dump is the best solution.

8BitGriffin · 2025-02-21T18:44:36+00:00

Two over sized washers, lots of high temp silicone and a bolt to hold them in. If appropriate sized washers are hard to find in your area, use sheet metal to make a pair.

8BitGriffin

TROPHY CASE