#jumpdrive — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #jumpdrive, aggregated by home.social.
-
Lexar’s D70E Compact SSD Packs 2TB into a Tiny Thumb Drive https://petapixel.com/2026/05/07/lexars-d70e-compact-ssd-packs-2tb-into-a-tiny-thumb-drive/ #flashdrive #thumbdrive #Equipment #jumpdrive #storage #lexar #News #ssd
-
Lexar’s D70E Compact SSD Packs 2TB into a Tiny Thumb Drive https://petapixel.com/2026/05/07/lexars-d70e-compact-ssd-packs-2tb-into-a-tiny-thumb-drive/ #flashdrive #thumbdrive #Equipment #jumpdrive #storage #lexar #News #ssd
-
Lexar’s D70E Compact SSD Packs 2TB into a Tiny Thumb Drive https://petapixel.com/2026/05/07/lexars-d70e-compact-ssd-packs-2tb-into-a-tiny-thumb-drive/ #flashdrive #thumbdrive #Equipment #jumpdrive #storage #lexar #News #ssd
-
Lexar’s D70E Compact SSD Packs 2TB into a Tiny Thumb Drive https://petapixel.com/2026/05/07/lexars-d70e-compact-ssd-packs-2tb-into-a-tiny-thumb-drive/ #flashdrive #thumbdrive #Equipment #jumpdrive #storage #lexar #News #ssd
-
Lexar’s D70E Compact SSD Packs 2TB into a Tiny Thumb Drive https://petapixel.com/2026/05/07/lexars-d70e-compact-ssd-packs-2tb-into-a-tiny-thumb-drive/ #flashdrive #thumbdrive #Equipment #jumpdrive #storage #lexar #News #ssd
-
I wanted to try #Mobian #Trixie on my #Librem5 again as I got a way to go back to #pulseaudio to as a work around to missing echo cancellation support in #pipewire (Thanks to @dos ). So I went ahead and ran the usual apt dis-upgrade way (in hindsight, may be gnome software was a better option). But I got locked out of the session as upgrade was progressing. So I had to force shut down and then use #JumpDrive to repair it from my laptop.
I documented it in #debian wiki
https://wiki.debian.org/InstallingDebianOn/Purism/Librem5Phone#Using_JumpDrive_and_qemu_to_get_emergency_access_to_your_system -
I wanted to try #Mobian #Trixie on my #Librem5 again as I got a way to go back to #pulseaudio to as a work around to missing echo cancellation support in #pipewire (Thanks to @dos ). So I went ahead and ran the usual apt dis-upgrade way (in hindsight, may be gnome software was a better option). But I got locked out of the session as upgrade was progressing. So I had to force shut down and then use #JumpDrive to repair it from my laptop.
I documented it in #debian wiki
https://wiki.debian.org/InstallingDebianOn/Purism/Librem5Phone#Using_JumpDrive_and_qemu_to_get_emergency_access_to_your_system -
@ralfchr @BGStatsApp Ich denke den direkt einzuprogrammieren wird zu aufwändig, weil es sich nicht auf andere Spiele übertragen lässt.
Ich habe manchmal den Tiebreaker bei Spielen als Nachkommastelle eingetragen. Du hast 50 Punkte und 14 Handkarten bei #JumpDrive und ich 50 Punkte und 7 Handkarten: es steht 50.14 zu 50.07
Aber wahrscheinlich nicht das was du gesucht hast, oder?
-
#JumpDrive Erweiterung #TerminalVelocity
In der Hand sind neue und alte Karten gemischt. Die Rückseite passt also!
Die Startwelten haben auch andere Rückseiten. Sehr gut für den Ab- und Aufbau!
( @NomenEstNemo )
-
#JumpDrive Erweiterung #TerminalVelocity
In der Hand sind neue und alte Karten gemischt. Die Rückseite passt also!
Die Startwelten haben auch andere Rückseiten. Sehr gut für den Ab- und Aufbau!
( @NomenEstNemo )
-
On to Jump Drive simplified version of Race For The Galaxy. #boardgamesnight #boardgames #boardgamegeek #jumpdrive
-
On to Jump Drive simplified version of Race For The Galaxy. #boardgamesnight #boardgames #boardgamegeek #jumpdrive
-
#Highlights im #Monat Januar 2023
#WundervolleWelt Rauf und runter auf #BGA - viel gelernt
#AstroKnights sehr gelungener #AeonsEnd Nachfolger - schnell Partien zusammen bekommen
#JumpDrive große Vorfreude auf die Erweiterung (zeitweise Platz 5 auf BGA)
#StarRealms 17 Partien gegen meinen Bruder
#TooManyBones zum 1. Mal Multiplayer - zu lang, aber gut
#Kniffel gute Zeit mit meinem Vater
#ElBurro bestes neues Spiel (von 8 Neuen), gelungener Nachfolger
#AirLandAndSea auch mit meinem Bruder
-
#Highlights im #Monat Januar 2023
#WundervolleWelt Rauf und runter auf #BGA - viel gelernt
#AstroKnights sehr gelungener #AeonsEnd Nachfolger - schnell Partien zusammen bekommen
#JumpDrive große Vorfreude auf die Erweiterung (zeitweise Platz 5 auf BGA)
#StarRealms 17 Partien gegen meinen Bruder
#TooManyBones zum 1. Mal Multiplayer - zu lang, aber gut
#Kniffel gute Zeit mit meinem Vater
#ElBurro bestes neues Spiel (von 8 Neuen), gelungener Nachfolger
#AirLandAndSea auch mit meinem Bruder
-
-
-
Next up on #boardgame night is Jump Drive. Lovely Lite version of Race For The Galaxy/Roll For The Galaxy. #JumpDrive #RollForTheGalaxy #RaceForTheGalaxy
-
Next up on #boardgame night is Jump Drive. Lovely Lite version of Race For The Galaxy/Roll For The Galaxy. #JumpDrive #RollForTheGalaxy #RaceForTheGalaxy
-
Heute mal wieder viele gute Titel in der #BGGPeoplesChoiceSoloTop200-2022
Kann mich nicht entscheiden zwischen #Grove (#Zitrushain) und #JumpDrive.
Verrückt, dass #Carnegie direkt so hoch einsteigt.
-
Wow. Stunned that my #PinePhonePro is here already! :annoyingdog: Way quicker than my OG #PinePhone arrived. Loving how silky smooth many of the animations are and how much quicker the apps load!
Looking forward to when the camera is testable!
After initial setup, my EMMC #Manjaro install doesn't seem to work, though. Just black screen+cursor.
Does anyone know if #Jumpdrive by @danctnix and @martijnbraam works on the pro model, too? If not, I'll just install #PmOS on it from the SDcard. 👍
-
Wow. Stunned that my #PinePhonePro is here already! :annoyingdog: Way quicker than my OG #PinePhone arrived. Loving how silky smooth many of the animations are and how much quicker the apps load!
Looking forward to when the camera is testable!
After initial setup, my EMMC #Manjaro install doesn't seem to work, though. Just black screen+cursor.
Does anyone know if #Jumpdrive by @danctnix and @martijnbraam works on the pro model, too? If not, I'll just install #PmOS on it from the SDcard. 👍
-
Linux Class: Howto dd Command:
Includes: copying img/iso files, backing up sdcard's to an img file (Pinephone ex), backup your emmc, and use a pipe to backup to a compressed image file (.img.gz).
#Linux #FOSS #FLOSS #Pinephone #OpenSource #HowTo #Tutorial #Pinetab #jumpdrive
https://odysee.com/@RTP:9/linux-intro-create-backup-image-files-%2B:4
-
Linux Class: Howto dd Command:
Includes: copying img/iso files, backing up sdcard's to an img file (Pinephone ex), backup your emmc, and use a pipe to backup to a compressed image file (.img.gz).
#Linux #FOSS #FLOSS #Pinephone #OpenSource #HowTo #Tutorial #Pinetab #jumpdrive
https://odysee.com/@RTP:9/linux-intro-create-backup-image-files-%2B:4
-
The forty-eighth edition of my weekly collection of news about #LinuxPhones (@PINE64 #PinePhone, @purism #Librem5 and such), #LinBits, is out!
https://linmob.net/linbits-47-weekly-linux-phone-news-week21-22/
New #Crust, #Phosh and #Jumpdrive releases, #Volla Community days and more!
#LinuxPhones -
The forty-eighth edition of my weekly collection of news about #LinuxPhones (@PINE64 #PinePhone, @purism #Librem5 and such), #LinBits, is out!
https://linmob.net/linbits-47-weekly-linux-phone-news-week21-22/
New #Crust, #Phosh and #Jumpdrive releases, #Volla Community days and more!
#LinuxPhones -
I've refined my method for saving the image of a working #pinephone and preserving the image so that it can be reproduced, whenever, the need arises. The concept is, one's pinephone is working just like one configured it to and for whatever reason, one has to re-flash, the image or, flash it to a new phone. With a ready made image on hand, one does not have to start from scratch, one may pick up where one has left off. Now, to create the image from the eMMC, one uses #jumpdrive and, if, for instance, the eMMC is listed as /dev/sdb, with partitions /dev/sdb1 and /dev/sdb2, just dd=if=/dev/sdb conv=sync,noerror bs=512 status=progress of=mypinephone.img. Now that image is going to be 30GB, the size of the eMMC, in this case, which is going to be too big. The image will need to be resized. I've written an article on my #Gemini capsule on the steps, that I took, to resize the image, and I'll soon post one on my Web blog too, later this week, or sooner. However, in the meantime, any of you who are interested in the process, my capsule is at gemini://mstdn.design and the article is at gemini://mstdn.design/logs/2021-03-18-dd-reflections.gmi. Let me know what you think. For those without Gemini browsers I'll post a write up on my blog as soon as I can. #dd #pinephone #gemini -
I've refined my method for saving the image of a working #pinephone and preserving the image so that it can be reproduced, whenever, the need arises. The concept is, one's pinephone is working just like one configured it to and for whatever reason, one has to re-flash, the image or, flash it to a new phone. With a ready made image on hand, one does not have to start from scratch, one may pick up where one has left off. Now, to create the image from the eMMC, one uses #jumpdrive and, if, for instance, the eMMC is listed as /dev/sdb, with partitions /dev/sdb1 and /dev/sdb2, just dd=if=/dev/sdb conv=sync,noerror bs=512 status=progress of=mypinephone.img. Now that image is going to be 30GB, the size of the eMMC, in this case, which is going to be too big. The image will need to be resized. I've written an article on my #Gemini capsule on the steps, that I took, to resize the image, and I'll soon post one on my Web blog too, later this week, or sooner. However, in the meantime, any of you who are interested in the process, my capsule is at gemini://mstdn.design and the article is at gemini://mstdn.design/logs/2021-03-18-dd-reflections.gmi. Let me know what you think. For those without Gemini browsers I'll post a write up on my blog as soon as I can. #dd #pinephone #gemini -
I think I may have figured out, remembered, how to control the size of the #dd command's output file. If you remember, I had installed #mobian on a SD card, the SD card itself, is 32GB, the data used on the drive is only 5.4GB. My wish was to preserve the data on the card and use it as the image that I would flash to the eMMC, using #jumpdrive. However, on my first attempt, I issued the command,sudo dd if=/dev/sdb of=mymobian.img status=progress. What that command did, was make an image, the size, of the entirety of the card, roughly 30GB. That image, was just too large to flash, according to the tool I was using to write the image, to the eMMC. I now think, that if I had issued this new command, sudo dd if=/dev/sdb of=mymobian.img bs=1G count=6 status=progress, that, I would have an image file that is 6GB and would be of an acceptable size to flash to a 29-32GB eMMC. One could say that it's a little late now for the light bulb to start shining, since I've already flashed a fresh mobian image and have already reconfigured my newly imaged phone to where it once was, but any good scientist would love to prove that his theory works, wouldn't he? I think I'll try flashing another SD card with this new image first and go from there, instead of tempting fate. I just wish I could have gotten a chance to prove the concept the first time. #pinephone
-
I think I may have figured out, remembered, how to control the size of the #dd command's output file. If you remember, I had installed #mobian on a SD card, the SD card itself, is 32GB, the data used on the drive is only 5.4GB. My wish was to preserve the data on the card and use it as the image that I would flash to the eMMC, using #jumpdrive. However, on my first attempt, I issued the command,sudo dd if=/dev/sdb of=mymobian.img status=progress. What that command did, was make an image, the size, of the entirety of the card, roughly 30GB. That image, was just too large to flash, according to the tool I was using to write the image, to the eMMC. I now think, that if I had issued this new command, sudo dd if=/dev/sdb of=mymobian.img bs=1G count=6 status=progress, that, I would have an image file that is 6GB and would be of an acceptable size to flash to a 29-32GB eMMC. One could say that it's a little late now for the light bulb to start shining, since I've already flashed a fresh mobian image and have already reconfigured my newly imaged phone to where it once was, but any good scientist would love to prove that his theory works, wouldn't he? I think I'll try flashing another SD card with this new image first and go from there, instead of tempting fate. I just wish I could have gotten a chance to prove the concept the first time. #pinephone
-
Well I didn't get to do it my way. I forgot the tricks, I once knew about #dd, so the image I made, of my SD card, was 30GB, the size of the card, while, I only had 5GB of data on it. I think I once knew a way to fix that. So when I tried to write the image to the eMMC the program I used, #rpi-imager, told me, before I could start, that there wouldn't be enough room to write the image. Since I couldn't remember my magic spells and didn't word my intentions well in the search engines, I conceded to use my initial #mobian image, that I used to make the SD card. Then I just used dpkg -i to install my custom kernel and everything went swimmingly. Honestly, I'm going to have to read everything I can about dd, because there are some tricks to force the program to write the image the size of the disk usage. At least, I think so. I swear, I did something like that a few years back. Anyway I've gotten most of my modifications reimplemented so it's a mute point now. #pinephone #jumpdrive
-
Well I didn't get to do it my way. I forgot the tricks, I once knew about #dd, so the image I made, of my SD card, was 30GB, the size of the card, while, I only had 5GB of data on it. I think I once knew a way to fix that. So when I tried to write the image to the eMMC the program I used, #rpi-imager, told me, before I could start, that there wouldn't be enough room to write the image. Since I couldn't remember my magic spells and didn't word my intentions well in the search engines, I conceded to use my initial #mobian image, that I used to make the SD card. Then I just used dpkg -i to install my custom kernel and everything went swimmingly. Honestly, I'm going to have to read everything I can about dd, because there are some tricks to force the program to write the image the size of the disk usage. At least, I think so. I swear, I did something like that a few years back. Anyway I've gotten most of my modifications reimplemented so it's a mute point now. #pinephone #jumpdrive
-
So when I bought my #pinephone it came with the #Manjaro #KDE Plasma Desktop, if you will. Now I'm not a fan of Manjaro or, by the way, #arch, for that matter. Their software applications, offerings, are extremely limited, in comparison to, say #Debian, for instance. Programs that I commonly use, were just not in their repositories, plus I'm more accustomed to using apt as my package manager. Anyway, I tested out #Mobian on a SD card and I love it. So now, the system on the SD card, is just the one I'd like on my phone, including all my modifications, especially the newly, customized kernel and I don't want, to have to start all over again, from scratch. What I'm proposing to do, in a few days or weeks, since, I want to make sure I wont make mistakes, is, eventually, using #jumpdrive to replace the Manjaro/KDE Plasma and commit to Mobian. I'm going to use #dd to create, from my SD card, the image that will be flashed to the eMMC. I don't see why that wouldn't work. I'll be essentially just cloning the SD card with the eMMC. I haven't heard any of those video making people speaking specifically on using this method. they just seem to expect one to start from scratch. However, I'm going to do it my way and see what's what. Yes, dd if=/dev/MYSDCAARD of=mymobian.img [Options], then flash that image to the eMMC with the aid of jumpdrive and the trusty dd, with mymobian.img on my host computer, I think, dd if=mymobian.img of=eMMC to some degree, should do the trick. Wish me luck.
-
So when I bought my #pinephone it came with the #Manjaro #KDE Plasma Desktop, if you will. Now I'm not a fan of Manjaro or, by the way, #arch, for that matter. Their software applications, offerings, are extremely limited, in comparison to, say #Debian, for instance. Programs that I commonly use, were just not in their repositories, plus I'm more accustomed to using apt as my package manager. Anyway, I tested out #Mobian on a SD card and I love it. So now, the system on the SD card, is just the one I'd like on my phone, including all my modifications, especially the newly, customized kernel and I don't want, to have to start all over again, from scratch. What I'm proposing to do, in a few days or weeks, since, I want to make sure I wont make mistakes, is, eventually, using #jumpdrive to replace the Manjaro/KDE Plasma and commit to Mobian. I'm going to use #dd to create, from my SD card, the image that will be flashed to the eMMC. I don't see why that wouldn't work. I'll be essentially just cloning the SD card with the eMMC. I haven't heard any of those video making people speaking specifically on using this method. they just seem to expect one to start from scratch. However, I'm going to do it my way and see what's what. Yes, dd if=/dev/MYSDCAARD of=mymobian.img [Options], then flash that image to the eMMC with the aid of jumpdrive and the trusty dd, with mymobian.img on my host computer, I think, dd if=mymobian.img of=eMMC to some degree, should do the trick. Wish me luck.
-
So when I bought my #pinephone it came with the #Manjaro #KDE Plasma Desktop, if you will. Now I'm not a fan of Manjaro or, by the way, #arch, for that matter. Their software applications, offerings, are extremely limited, in comparison to, say #Debian, for instance. Programs that I commonly use, were just not in their repositories, plus I'm more accustomed to using apt as my package manager. Anyway, I tested out #Mobian on a SD card and I love it. So now, the system on the SD card, is just the one I'd like on my phone, including all my modifications, especially the newly, customized kernel and I don't want, to have to start all over again, from scratch. What I'm proposing to do, in a few days or weeks, since, I want to make sure I wont make mistakes, is, eventually, using #jumpdrive to replace the Manjaro/KDE Plasma and commit to Mobian. I'm going to use dd to create, from my SD card, the image that will be flashed to the eMMC. I don't see why that wouldn't work. I'll be essentially just cloning the SD card with the eMMC. I haven't heard any of those video making people speaking specifically on using this method. they just seem to expect one to start from scratch. However, I'm going to do it my way and see what's what. Yes, dd if=/dev/MYSDCAARD of=mymobian.img [Options], then flash that image to the eMMC with the aid of jumpdrive and the trusty dd, with mymobian.img on my host computer, I think, dd if=mymobian.img of=eMMC to some degree, should do the trick. Wish me luck.
-
So when I bought my #pinephone it came with the #Manjaro #KDE Plasma Desktop, if you will. Now I'm not a fan of Manjaro or, by the way, #arch, for that matter. Their software applications, offerings, are extremely limited, in comparison to, say #Debian, for instance. Programs that I commonly use, were just not in their repositories, plus I'm more accustomed to using apt as my package manager. Anyway, I tested out #Mobian on a SD card and I love it. So now, the system on the SD card, is just the one I'd like on my phone, including all my modifications, especially the newly, customized kernel and I don't want, to have to start all over again, from scratch. What I'm proposing to do, in a few days or weeks, since, I want to make sure I wont make mistakes, is, eventually, using #jumpdrive to replace the Manjaro/KDE Plasma and commit to Mobian. I'm going to use dd to create, from my SD card, the image that will be flashed to the eMMC. I don't see why that wouldn't work. I'll be essentially just cloning the SD card with the eMMC. I haven't heard any of those video making people speaking specifically on using this method. they just seem to expect one to start from scratch. However, I'm going to do it my way and see what's what. Yes, dd if=/dev/MYSDCAARD of=mymobian.img [Options], then flash that image to the eMMC with the aid of jumpdrive and the trusty dd, with mymobian.img on my host computer, I think, dd if=mymobian.img of=eMMC to some degree, should do the trick. Wish me luck.
-
The twentieth edition of my weekly collection of Linux phone news (@PINE64#PinePhone, @purism #Librem5 and such), #LinBits, is out!
https://linmob.net/2020/11/15/linbits19-weekly-linux-phone-news-week46.html
New distribution releases, #JumpDrive 0.6, a bigger battery for the #Librem5, #LAS2020 talks, #PlasmaMobile’s October Update and more!
-
The twentieth edition of my weekly collection of Linux phone news (@PINE64#PinePhone, @purism #Librem5 and such), #LinBits, is out!
https://linmob.net/2020/11/15/linbits19-weekly-linux-phone-news-week46.html
New distribution releases, #JumpDrive 0.6, a bigger battery for the #Librem5, #LAS2020 talks, #PlasmaMobile’s October Update and more!
-
Yes, #sxmo is installed on the eMMC of my #pinephone.
I've first installed #postmarketos (without a ui) on the eMMC of my pinephone using #pmbootstrap and #jumpdrive. Then, I've followed the instructions at https://git.sr.ht/~mil/sxmo-docs/tree/master/INSTALLGUIDE.md to install #sxmo on top of it.
I've also altered /etc/fstab, so my /home is on a SD card.