Re: [DNG] Identifying or rsetting a microsd card
On Tue, Dec 10, 2019 at 05:01:24AM +0100, k...@aspodata.se wrote: > Hendrik: > ... > > Device Start End Sectors Size Type > > /dev/sdb1 20483481532768 16M unknown > > /dev/sdb2 34816 31116254 31081439 14.8G unknown > > # file -s /dev/sdb1 > # file -s /dev/sdb2 > > Regards, > /Karl Hammar root@midwinter:~# file -s /dev/sdb1 /dev/sdb1: data root@midwinter:~# file -s /dev/sdb2 /dev/sdb2: data root@midwinter:~# file -s /dev/sdb /dev/sdb: DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 31116287 sectors, extended partition table (last) root@midwinter:~# All the attempts to figure out what's on it have resulted in more or less the same conclision, so I'll take that as definitive; This is an MBR-formatted disk, with the entire partitions encrypted, so it's unlikely I can find any useful data on it. Time to give up and reformat it empty. Thanks for all the forensic tricks. -- hendrik > > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Please don't introduce yet more 'crayon licences' (was: fifth freedom)
Quoting onefang (onefang_dev...@sledjhamr.org): > I had recently added what I call freedom -1 to the licence of > apt-panopticon. The price of using peculiar, and in particular one-off, licensing is that many people will forego even looking a second further at your work, as it's easier to do so than to do licensing review. FYI (and separately from that), your addition to what would have otherwise been 2-clause BSD serves only to protect against a noonday-midnight, i.e., the action you claim to forbid is inherently impossible by basic operation of copyright law. I.e., the granting of access to reserved rights under copyright law is itself a reserved right (available only to the copyright owner, in this case you) under copyright law. It's neither necessary nor useful to do the legal equivalent of swinging a dead chicken to ward off theft of that legal monopoly. On OSI's license-discuss and license-review mailing lists, we call these sorts of things 'crayon licences', and as illustration of why most programmers really shouldn't try to draft licences, any more than most lawyers should try to code major software projects. > I even mention the alteratives that I know of in the docs, so that's your > fifth freedom catered for. Which reminds me: If coders feel they really cannot help themselves and must include manifestos, _please_ put them in the docs and not as disfigurings of otherwise useful and standard software licences. Why? Isn't avoiding hapless obscurity for your codebase reason enough? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] fifth freedom
On Thu, 12 Dec 2019 01:29:27 +1000, onefang wrote in message <20191211152927.7dnv67o7b554jf5f@true>: > On 2019-12-11 05:29:21, freemedia via Dng wrote: > > free software force and golinux have expressed interest in a > > revised version of the four freedoms, which i was initially very > > shy about the idea of. for some time ive proposed as an alternative > > a list of companion qualities or "pillars" which i havent > > completely abandoned yet. > > > > still, while seeking what these pillars would be, someone stepped > > up with a really ideal fifth freedom, which im now taking on a tour > > of sorts, consider this a request for comments: > > > > The freedom to NOT run the software, to be free to avoid vendor > > lock-in through appropriate modularization/encapsulation and > > minimized dependencies; meaning any free software can be replaced > > with a user’s preferred alternatives (freedom 4). > > > > for comparison, the existing four freedoms are: > > > > The freedom to run the program as you wish, for any purpose > > (freedom 0). The freedom to study how the program works, and change > > it so it does your computing as you wish (freedom 1). Access to the > > source code is a precondition for this. The freedom to redistribute > > copies so you can help others (freedom 2). The freedom to > > distribute copies of your modified versions to others (freedom 3). > > By doing this you can give the whole community a chance to benefit > > from your changes. Access to the source code is a precondition for > > this. > > I had recently added what I call freedom -1 to the licence of > apt-panopticon. 'the author specifically grants themselves the > freedom to not be infected by the viral licence clauses of any code > this source code "links" to. It's my code, I choose my licence > terms, no one else does.' ..the freedom from having your power grid utility force a new power meter with pirated software on it, on you? ..I requested said software license(s) documents and any GPL etc source where relevant to secure my own GPL compliance, and now the power grid utility refuses to document their alleged lawful "not-pirated" software in their old and new power meters, and they refuse to swap out my power meter, aaand, in so doing, they deny me my lawful right to sell my 24kW of power onto the free EEA/EU power market. Court proceding due next week, Wed Dec 18 11:30:00 CET 2019. > Yes there is a GPL bit included, yes I do distribute that bit with my > modifications in source code form in the same places I distribute > apt-panopticon. I also point out in the README of that bit, where to > get the original, and where to get my modified forms. No > apt-panopticon isn't gonna be GPL, just coz someone else thought that > I should not have the freedom to choose my own licence. > > I even mention the alteratives that I know of in the docs, so that's > your fifth freedom catered for. I carefully chose the dependencies > to be stuff and versions that are available in the standard Devuan > ASCII package repo. Except for the modified GPL bit of code, that > isn't in Devuan ASCII. > -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Identifying or rsetting a microsd card
Anno domini 2019 Wed, 11 Dec 13:24:46 -0700 Gregory Nowak scripsit: > On Wed, Dec 11, 2019 at 05:32:46PM +, Simon Hobson wrote: > > I would imagine there's a command you can send to the card which tells it > > to bulk-erase itself. Function in one of the disk utils ? > > Yup, hdparm. It works for SSD, I don't know if it would work for SD > cards too. > > Greg > > Does not "blkdiscard /dev/..." do the same job? Nik -- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ... ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Identifying or rsetting a microsd card
On Wed, Dec 11, 2019 at 05:32:46PM +, Simon Hobson wrote: > I would imagine there's a command you can send to the card which tells it to > bulk-erase itself. Function in one of the disk utils ? Yup, hdparm. It works for SSD, I don't know if it would work for SD cards too. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Identifying or rsetting a microsd card
marc wrote: > > I wonder if writing 0xff instead of 0x00 is kinder to flash > media. In particular, if the controller is dumb/smart enough > to only erase, not write... I would imagine there's a command you can send to the card which tells it to bulk-erase itself. Function in one of the disk utils ? Simon ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] fifth freedom
On 2019-12-11 05:29:21, freemedia via Dng wrote: > free software force and golinux have expressed interest in a revised version > of the four freedoms, which i was initially very shy about the idea of. for > some time ive proposed as an alternative a list of companion qualities or > "pillars" which i havent completely abandoned yet. > > still, while seeking what these pillars would be, someone stepped up with a > really ideal fifth freedom, which im now taking on a tour of sorts, consider > this a request for comments: > > The freedom to NOT run the software, to be free to avoid vendor lock-in > through appropriate modularization/encapsulation and minimized dependencies; > meaning any free software can be replaced with a user’s preferred > alternatives (freedom 4). > > for comparison, the existing four freedoms are: > > The freedom to run the program as you wish, for any purpose (freedom 0). > The freedom to study how the program works, and change it so it does your > computing as you wish (freedom 1). Access to the source code is a > precondition for this. > The freedom to redistribute copies so you can help others (freedom 2). > The freedom to distribute copies of your modified versions to others (freedom > 3). By doing this you can give the whole community a chance to benefit from > your changes. Access to the source code is a precondition for this. I had recently added what I call freedom -1 to the licence of apt-panopticon. 'the author specifically grants themselves the freedom to not be infected by the viral licence clauses of any code this source code "links" to. It's my code, I choose my licence terms, no one else does.' Yes there is a GPL bit included, yes I do distribute that bit with my modifications in source code form in the same places I distribute apt-panopticon. I also point out in the README of that bit, where to get the original, and where to get my modified forms. No apt-panopticon isn't gonna be GPL, just coz someone else thought that I should not have the freedom to choose my own licence. I even mention the alteratives that I know of in the docs, so that's your fifth freedom catered for. I carefully chose the dependencies to be stuff and versions that are available in the standard Devuan ASCII package repo. Except for the modified GPL bit of code, that isn't in Devuan ASCII. -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] fifth freedom
free software force and golinux have expressed interest in a revised version of the four freedoms, which i was initially very shy about the idea of. for some time ive proposed as an alternative a list of companion qualities or "pillars" which i havent completely abandoned yet. still, while seeking what these pillars would be, someone stepped up with a really ideal fifth freedom, which im now taking on a tour of sorts, consider this a request for comments: The freedom to NOT run the software, to be free to avoid vendor lock-in through appropriate modularization/encapsulation and minimized dependencies; meaning any free software can be replaced with a user’s preferred alternatives (freedom 4). for comparison, the existing four freedoms are: The freedom to run the program as you wish, for any purpose (freedom 0). The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1). Access to the source code is a precondition for this. The freedom to redistribute copies so you can help others (freedom 2). The freedom to distribute copies of your modified versions to others (freedom 3). By doing this you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
