prehistoric wrote:@belham2
Have you ever zeroed a 32 GB or larger flash drive? Believe me this takes a while. If you find that acceptable, what about my 128 GB drive?
Yes, and Yes, and even larger.......it's what beer and a night's sleep are for
You do realize that the vast majority of people will not accept this don't you? If this is required I'm afraid puppy will become even more a minority choice than it is now. Unnecessary writes also shorten the useful life of a drive.belham2 wrote:prehistoric wrote:@belham2
Have you ever zeroed a 32 GB or larger flash drive? Believe me this takes a while. If you find that acceptable, what about my 128 GB drive?
Yes, and Yes, and even larger.......it's what beer and a night's sleep are for
No. No. No. The problem is NOT what was on the disk before.belham2 wrote:It is flatout crazy that anyone who does a compressed image install using the dd command does not first do a complete dd wipe of that install device, whether they had GPT-related partitions previousy or not.
Listen, Prehistoric, Let's stop here. I am sorry I brought it up, and in fact, it was intended as an option for Barry, but of course others..well.... . Also, I try to stay reserved on the internet, but I work in the data security industry, 3+ decades now...we are NOT talking here about "securely" erasing drives and data on them. Don't mix and mash the discussion , trying to pull an apples to oranges comparison. I am not even sure if you know you are doing it. One thing I've learned over the decades of working securing databases & securing networks, is people, sometimes myself included, have trouble staying on point with "what" is being discussed and/or sorted out. Data recovery? Versus removing sectors on device sufficiently for home installs so partitioning schemes don't conflict? Two entirely diff subjects. Our objective with dd (for Barry's install's sakes) is not to securely, in totality, to wipe every bit off a drive. Also, we are NOT talking about attracting users to puppy or not, so please stop. Without Barry and the other creators, you and I and everyone else do not have anything to fuss over, period. I am not creating pups and their varities. Are you? Stop the childish insinuations. You, me and all the regulars here want the same thing; what is best for puppy. In essence, don't stand out in the sun and make the profound statement that it is warm out.prehistoric wrote:You do realize that the vast majority of people will not accept this don't you? If this is required I'm afraid puppy will become even more a minority choice than it is now. Unnecessary writes also shorten the useful life of a drive.belham2 wrote:prehistoric wrote:@belham2
Have you ever zeroed a 32 GB or larger flash drive? Believe me this takes a while. If you find that acceptable, what about my 128 GB drive?
Yes, and Yes, and even larger.......it's what beer and a night's sleep are for
What's more, I don't think this is necessary. Fix the GPT and expand the filesystem, and none of the previous use will matter.
Also, if you are trying to eliminate the possibility that earlier data can be recovered from the drive it is not adequate. I've had friends who have had flash memory used in industrial applications who found companies who specialize in recovering data from such media after they have been overwritten. Also happened with a photographer I know. He carries insurance against losing data on flash drives that pays for recovery.
So, what do you think you are actually accomplishing with this proposed procedure?
linuxcbon wrote:No. No. No. The problem is NOT what was on the disk before.belham2 wrote:It is flatout crazy that anyone who does a compressed image install using the dd command does not first do a complete dd wipe of that install device, whether they had GPT-related partitions previousy or not.
The problem is sfdisk not calculating "empty space" correctly.
You should never need to "dd dev zero", except to erase the whole disk and it takes many many many minutes. That's never needed for installing iso to the disk.
Agreed!linuxcbon wrote:Hi belham,belham2 wrote:linuxcbon,
Did I ever tell you the story of GPT Ghosting?? Me no like
sounds complicated...let's try not to complicate things and to find the bugs in puppy.
Cheers
I am sure he will keep his promise but he said he's very busy and he needs to rest (he is not as "young" as us)... So let's not pressure him too much. He needs to stay fit (like we do).belham2 wrote:Agreed!
Hey, you think Barry might ever give your request consideration? I posted a few times about it, even stuck my necks out with a separate thread, but I know he is probably near his wits end with everything going on right now. Still, a barebones quirky?? Ooooh lala....
All joking aside, I repeat, what do you think this waste of time will accomplish?belham2 wrote:prehistoric wrote:@belham2
Have you ever zeroed a 32 GB or larger flash drive? Believe me this takes a while. If you find that acceptable, what about my 128 GB drive?
Yes, and Yes, and even larger.......it's what beer and a night's sleep are for
f2fs, yes... unfortunately, the latest version requires selinux to be installed.@barry
Thanks and kudos for Slaq. This might actually trigger my final move to x64.
Besides the already reported "filesystem growing issue" that is the major issue I have with it...
Now to go after chromium and netflix! Anyone has the latest slack based pets for the latest chromium?
Thanks,
gcav
PS: Why drop F2FS? I did notice a slow-down at boot-time, compared to April 7.2.1 on T2.
BarryK wrote:Hmmmm.........
Solution to the problem:linuxcbon wrote:Quirky SlaQ 8.1.6 x86_64
- jwmrc not correct. That's why startup programs (network tray, retrovol) don't appear in tray.
Code: Select all
Generating /root/.icewm/menu... mv: cannot move '/root/.icewm/menu' to a subdirectory of itself, '/root/.icewm/menu-previous' Generating /root/.jwmrc... mv: cannot move '/root/.jwmrc' to a subdirectory of itself, '/root/.jwmrc-previous'
Code: Select all
# jwm -p JWM: warning: /root/.jwmrc[423]: close tag "Program" does not match open tag "?xml"
I know this already, but that's not a solution, it's a manual workaround. You need to find where the bug exactly comes from in the scripts and give a real solution.FeodorF wrote:Solution to the problem: