Re: sha256sum --text generating blank spaces and hyphens?
On 27/04/2023 11:02, David Christensen wrote: Things get more interesting when you approach the problem as a database. Save the content wherever and put the metadata into a table -- content hash (primary key), URL, download timestamp, author, subject, title, keywords, etc.. Create fully inverted indexes. Create a search engine. Create a spider. Implementation could range from a CSV/TSV flat-file and shell/P* scripts, to a desktop database/UI, to a LAMP stack, and beyond (NoSQL, N-tier). There are distributed file sharing systems based on such ideas. I have never tried: "Open-source self-hosted web archiving" https://github.com/ArchiveBox/ArchiveBox This one allows to save selected part of a page: https://github.com/danny0838/webscrapbook/
Re: Debian support for AMD GPU applications
jeremy ardley writes: > Is there any reliable source of information to install computational > back-ends using AMD GPUs on Debian 11? I followed the below repo and it worked perfectly on Debian 12 (Bookworm). No need to install anything else on your system (no need for rocm-device-* etc. packages). You can cleanly uninstall also, if you want. https://gitlab.com/BCMM/amdgpu-opencl-on-debian
Re: AMD ryzen 5 2400G VGA drivers required for Debian 10 based linux OS
We have Debian 10 based linux system And we are unable to boot into desktop VGA -AMD RAVEN RIDGE RADEON VEGA SERIES Subsystem - Elitegroup Computer Systems raven ridge Radeo Vega series Is there any suitable drivers for it On April 26, 2023 at 10:20 PM Dan Ritter wrote: > Timothy M Butterworth wrote: > > On Wed, Apr 26, 2023 at 10:12 AM karans wrote: > > > > > Dear Debian Team > > > > > > We have Debian 10 buster based linux OS but we are facing issue after > > > install linux > > > > > > > I forwarded this to the Debian User mailing list, which is the end user > > support list. Debian developers list is strictly just for developer topics. > > > > Tim > > > > > > > *Processor - AMD RYZEN 5 2400G* > > > *VGA - Advanced Micro Devices Inc AMD/ATI Raven Ridge > > > Radeon Vega Series* > > > *Kernel - 5.7.0-0.bpo.2-amd64* > > > > > > We are unable to find compatible drivers for the amdgpu > > > xserver-xorg-video-amdgpu > firmware-amd-graphics > libdrm-amdgpu1 > > These are all usable in bullseye (11, currently stable). You > should not be installing a new buster at this calendar date; > 12 is likely to be stable in just a few months. > > What specific issues are you seeing? > > -dsr- Thanks & Regards, Karan Sharma / श्री कर्ण शर्मा Project Engineer /श्री कर्ण शर्मा Centre for Development of Advanced Computing(C-DAC) / प्रगत संगणन विकास केन्द्र(सी-डैक) Tidel Park”, 8th Floor, “D” Block, (North &South) / “टाइडल पार्क”,8वीं मंजिल, “डी” ब्लॉक, (उत्तर और दक्षिण) No.4, Rajiv Gandhi Salai / नं.4, राजीव गांधी सलाई Taramani / तारामणि Chennai / चेन्नई – 600113 Ph.No.:044-22542226/27 Fax No.: 044-22542294 [ C-DAC is on Social-Media too. Kindly follow us at: Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ] This e-mail is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email is strictly prohibited and appropriate legal action will be taken.
Re: sha256sum --text generating blank spaces and hyphens?
On 4/26/23 16:21, Albretch Mueller wrote: On 4/26/23, David Christensen wrote: I suggest hashing the document content rather than the URL. This would work nicely for static documents. What do you mean by "hashing the document content"? 2023-04-26 21:03:08 dpchrist@taz ~ $ touch foo 2023-04-26 21:03:12 dpchrist@taz ~ $ sha256sum foo e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 foo In this case, the content is an empty string and the hexadecimal encoding of the the SHA256 hash is "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855". How would that help when what you are trying to do is cleanse and canonize texts as best as you could to find relationships among their text segments? lbrtchx * Each unique text would be stored once regardless of how many URL's link to it. * If the content at a URL changes, the new content will have a new hash. So, the new content will be saved and the old content will be preserved (instead of the new content overwriting the old content). * With regard to my response to the post by Nicolas George, a database of metadata could benefit analysis regardless of the scheme used to name content files. David
Re: sha256sum --text generating blank spaces and hyphens?
On 4/26/23 15:48, Nicolas George wrote: David Christensen (12023-04-26): I suggest hashing the document content rather than the URL. This would work nicely for static documents. That will be very convenient to retrieve the document content from the URL. My suggestion assumes that the URL => hash => content mapping is saved somehow. For example, save the content in a file named after the hash and save the URL in a file whose name is the hash plus a suffix. Finding a document by URL then becomes a grep(1) invocation. Things get more interesting when you approach the problem as a database. Save the content wherever and put the metadata into a table -- content hash (primary key), URL, download timestamp, author, subject, title, keywords, etc.. Create fully inverted indexes. Create a search engine. Create a spider. Implementation could range from a CSV/TSV flat-file and shell/P* scripts, to a desktop database/UI, to a LAMP stack, and beyond (NoSQL, N-tier). There are distributed file sharing systems based on such ideas. David
Re: (Thread restarted!) Debian installation using debootstrap and grub-install - no entry in ESC boot menu
On 26/04/2023 22:57, Valentin Caracalla wrote: the issue with the BIOS boot interface (see my original posting) is still unsolved I had impression that there was no issue with booting in BIOS (legacy, compatibility, CSM) mode, of course when it is chosen in firmware/BIOS setup (requires disabling of secure boot). Perhaps I confused it with qemu instead of bare metal. I tried using the EFI removable media path (which should bypass any issues with EFI variables) without success. This statement might be too strong. Internal drive is not a removable media. My impression is that you can boot from removable media (live CD), but not from internal drive. - Is booting from that internal drive enabled in firmware setup? - Is shim-signed package installed? Just shim is not enough when secure boot is enabled in firmware. I want to install Debian on my Asus UX31A UEFI implementation may have some peculiarities, likely you will find more pages: https://wiki.osdev.org/Broken_UEFI_implementations https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface#Troubleshooting I want to install it to the internal drive /dev/sda, and I want to do so by executing commands on an installer system, which is a system already installed on the external drive /dev/sdb. Does it mean that you have another linux installed and there is no issue with its booting? Is it debian? For now, I only want to get a GRUB command line, because that appears to be the difficult part. Then you do not need debian installer at all. To debug such issues it is enough to copy files to EFI/debian and to run a couple of efibootmgr commands. By the way, you have not posted "efibootmgr -v" or at least "efibootmgr" output. Running it from an existing install or a live media is OK. For the BIOS boot interface: sudo parted /dev/sda mklabel gpt sudo parted /dev/sda mkpart root 512MiB 100% sudo parted /dev/sda set 1 bios_grub on Perhaps you may create both BIOS Boot and EFI System partitions on the same disk to support both modes. For the EFI boot interface: sudo parted /dev/sda mklabel gpt sudo parted /dev/sda mkpart init 0% 512MiB sudo parted /dev/sda set 1 boot on sudo mkfs.vfat /dev/sda1 I do not remember if the "boot" flag sets proper GUID for ESP. I have heard that there may be issues if fat16 is used instead of fat32 https://www.rodsbooks.com/gdisk/booting.html file --special /dev/sda1 parted /dev/sda print sgdisk -p /dev/sda (Some people may be more familiar with output of sgdisk than parted) sudo mount --bind /sys /mnt/sys sudo mount --bind /proc /mnt/proc sudo mount --bind /dev /mnt/dev sudo mount --bind /dev/pts /mnt/dev/pts sudo mount --bind /run /mnt/run I still do not see /sys/firmware/efi/efivars here. Check /mnt/sys/firmware/efi/efivars Frankly speaking, I am confused by your description. I suspect it is a mix of - What you are going to do in future (having working install, prepare a disk for another machine or install a fresh system for the same computer) - What you are really doing - Recipe which way others may try reproduce (boot from a live media and install to an internal drive) Let's concentrate on UEFI. Unless you faced an Asus-specific issue, it should be possible to use qemu+OVMF.
Re: Evolution email (problem?)
On 26/04/2023 22:05, Default User wrote: it absolutely refuses to delete email messages directly from the [Gmail]/All Mail folder of any email account. Disclaimer: I do not use evolution. Do you use IMAP for your gmail account? Notice that IMAP assumes tree-like structure of folders and messages. Gmail uses concept of labels, so the same message may have multiple labels. When mapped to IMAP it means the same message (not a copy) may be accessed from different folders. Moreover All Mail is a meta label/folder that includes every message (besides trash?). I am unsure if it can be reasonably handled using conventional IMAP. So gmail IMAP accounts may be special to some degree for mail clients. Perhaps some kind of cooperation between a mailer and the server is necessary. I am unsure at which moment a message should completely disappear from the server in response to removing it from particular folders (actually labels).
OT: flatcam, pcb2gcode
Hello, Has anyone successfully installed a working version of either flatcam or pcb2gcode? How? Best regards, Fred
Re: sha256sum --text generating blank spaces and hyphens?
On 4/26/23, David Christensen wrote: > I suggest hashing the document content rather than the URL. This would > work nicely for static documents. What do you mean by "hashing the document content"? How would that help when what you are trying to do is cleanse and canonize texts as best as you could to find relationships among their text segments? lbrtchx
Re: sha256sum --text generating blank spaces and hyphens?
David Christensen (12023-04-26): > I suggest hashing the document content rather than the URL. This would work > nicely for static documents. That will be very convenient to retrieve the document content from the URL. -- Nicolas George
Re: sha256sum --text generating blank spaces and hyphens?
On 4/26/23 00:41, Albretch Mueller wrote:
This is not a debian question per se (more like a Linux bash one),
but I wasn't able to find an answer on the Internet.
Here is first the problem I am having before you start reading a
conspiracy theory into it ;-)
I need to somehow map URL on the web to a local file, but you can't
do that for two main reasons:
1) URLs are free text
2) which people take to their heart's content.
Take for example:
https://dokumen.pub/qdownload/nietzsche-und-der-deutsche-geist-band-4-ausbreitung-und-wirkung-des-nietzscheschen-werkes-im-deutschen-sprachraum-bis-zum-ende-des-zweiten-weltkrieges-ein-schrifttumsverzeichnis-der-jahre-1867-1945-ergnzungen-berichtigungen-und-gesamtverzeichnisse-zu-den-bnden-i-iii-9783110202861-9783110189865-3110189860.html
that file and the pdf you would download I need to map to a local
directory looking like: ... /pub/dokumen/qdownload/ ...
but the file name (excluding the extension) is 306 characters long,
which Windows NTFS would not swallow. There may be also funky rules
regarding character sets and where in a string certain chars may be
used; so, as a way to work around those kinds of problems I:
a) encode the string name as base64
b) calculate the sha256sum of §a
c) use §b as file name (of course, leaving the original extension as it is)
d) include a "§b_file_name.txt" plain text file decriptor which only
content is the actual prehash name of that file.
https://dokumen.pub/qdownload/nietzsche-und-der-deutsche-geist-band-4-ausbreitung-und-wirkung-des-nietzscheschen-werkes-im-deutschen-sprachraum-bis-zum-ende-des-zweiten-weltkrieges-ein-schrifttumsverzeichnis-der-jahre-1867-1945-ergnzungen-berichtigungen-und-gesamtverzeichnisse-zu-den-bnden-i-iii-9783110202861-9783110189865-3110189860.html
_TXT="nietzsche-und-der-deutsche-geist-band-4-ausbreitung-und-wirkung-des-nietzscheschen-werkes-im-deutschen-sprachraum-bis-zum-ende-des-zweiten-weltkrieges-ein-schrifttumsverzeichnis-der-jahre-1867-1945-ergnzungen-berichtigungen-und-gesamtverzeichnisse-zu-den-bnden-i-iii-9783110202861-9783110189865-3110189860"
_B64TXTENC=$(printf '%s' "${_TXT}" | base64 )
echo "// __ \$_B64TXTENC: |${_B64TXTENC}|"
_B64TXTDEC=$(printf '%s' "${_B64TXTENC}" | base64 --decode)
echo "// __ \$_B64TXTDEC: |${_B64TXTDEC}|"
if [[ "${_TXT}" == "${_B64TXTDEC}" ]]; then
echo "// __ [[ \${_TXT} == \${_B64TXTDEC} ]]: |${_TXT}|"
_SHA256=$(printf '%s' "${_TXT}" | sha256sum --text )
echo "// __ \$_SHA256: |${_SHA256}|"
fi
// __ $_SHA256:
|7d5895cb24ab49692a8ad495e036074fec8e61b22040544f02a9b69c926dbdeb -|
I am trying to avoid funky characters and sha256sum --text still
generates them!?!
I work like this because I need replicate the original URL as a local
path in a way that would be compatible any file system.
Do you know of a better way to deal with such issues?
lbrtchx
I will assume you have solved the sha256sum output issue. (I would use
Perl and Digest::SHA.)
I suggest hashing the document content rather than the URL. This would
work nicely for static documents.
David
Re: sha256sum --text generating blank spaces and hyphens?
Hello, On Wed, Apr 26, 2023 at 08:30:01PM +, Albretch Mueller wrote: > On 4/26/23, Dan Ritter wrote: > > The only characters used in the sha256 hash itself are [a-f] and > > [0-9] > > Yes, I knew that; that is why I could not understand why sha256sum > was being "courteous" to me. The man page is very clear on what the output will be, and just running it on a few files should also make it obvious to you, also, all the other sha*sum and md5sum utilities work pretty much the same way. So I don't know why this comes as a surprise, but OK. > OK, now I see why cutting off the string on the first space that > appears is safe. I never saw such cases because I always used sha*sums > on files. But it does the same thing with files… Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: Evolution email (problem?)
On Wed, 2023-04-26 at 11:11 -0400, Patrick Wiseman wrote: > Can't explain it, but it strikes me it's almost certainly a > permissions problem. > > Patrick > > > > > On Wed, Apr 26, 2023 at 11:06 AM Default User > wrote: > > Strange . . . > > > > I run Debian 11 (Bullseye) Stable, up to date, Gnome 3 desktop > > environment. > > > > I recently set up Evolution email. Works okay. > > > > Two days ago, I realized that it absolutely refuses to delete email > > messages directly from the [Gmail]/All Mail folder of any email > > account. To delete a message in the All Mail folder, that is not > > also > > in another folder, the message must be moved into another folder > > and > > then deleted from there. > > > > I sure think I remember being able to delete directly from the All > > Mail > > folder when I first set up Evolution. > > > > I re-started Evolution. No change. > > I re-booted. No change. > > I did sudo aptitude reinstall evolution. No Change. > > I moved ~/.local/share/evolution/mail/local/folders.db to Trash, > > then > > re-started Evolution to construct a new folders.db file. No > > change. > > I did sudo aptitude purge evolution, then sudo aptitude install > > Evolution. No change. > > I moved ~/.local/share/evolution, ~/.cache/evolution, and > > ~/.config/evolution to Trash, then did sudo aptitude purge > > evolution, > > then sudo aptitude install Evolution. No change. > > I did some research online, seeking a solution, or at least a > > "good" > > explanation. No solution or "good" answer was found. > > > > But . . . then I booted into a Debian 11.6 Live/Install usb thumb > > drive, and then installed Evolution into the Live session, upon > > which > > Evolution DID allow message deletion directly from the [Gmail]/All > > Mail > > folder! > > > > Back to my regular Debian 11 Stable install. No change. > > > > It makes no sense to me that it would work from a Debian 11 > > Live/Install session, but not (currently) from a regular Debian > > session. > > > > Even if it did not work from a Live Debian session, it makes no > > sense > > to me that Evolution could be designed this way. I see no good > > reason > > that messages can be directly deleted from any other folder, but > > not > > [Gmail]/All Mail. > > > > Does anyone have a solution, so that messages must be moved to > > another > > folder (if they are not also there already), just to be deleted? > > Or at > > least a "good" explanation as to why Evolution appears to be > > designed > > this way? > > > > > > Hi, Patrick. I don't see anything obviously wrong about the permissions on my computer. Not surprising, since I rarely change any permissions, and can't recall doing so where it might cause the condition in question. But I don't know what exactly to look for. Perhaps a directory that has extra or inappropriate read-only permission(s)? And I don't think that any permissions on my computer are involved, since the email folders in question are not on my local computer, they are on one or more Google server(s) elsewhere. I am just accessing them remotely, they are not downloaded to my computer. Possibly interesting note: The [Gmail]/Important and [Gmail]/All Mail folders both have listed in "folder properties"/"Labels" the Server Tag "$Phishing". No other folders do. But again, messages can be directly deleted from [Gmail]/Important folders, but not from [Gmail]/All Mail folders. So it probably doesn't mean anything in the current context. Well, anyway, do other Debian Stable Evolution users experience this problem? Or is it really "just me"?
Re: sha256sum --text generating blank spaces and hyphens?
On 4/26/23, David Wright wrote:
> I guess you need the expense of sha256 rather than md5 as you're
> downloading the entire web?
I am not downloading the entire web. I have no way of knowing how
they entertained those ideations but I think we could use their
estimate when google said that approximately 1 million and a half
books have been ever published. Think of it! It is not that much data.
It would all fit nicely in one hard drive; include some searching
capability and "bye bye google" will be the name of your movie. At
times you need to gain a sense of things before going into exposed
mode to search for something (which these days means making sure you
are not being baited into something else)
On 4/26/23, Dan Ritter wrote:
> The only characters used in the sha256 hash itself are [a-f] and
> [0-9]
Yes, I knew that; that is why I could not understand why sha256sum
was being "courteous" to me.
On 4/26/23, Nicolas George wrote:
> shaXsum always writes X/4 hexadecimal nibbles then two spaces then the
> file name. If the input is from stdin, then the convention is the file
> name is ‘-’.
>
> (Well, not always always: if the file name contains very special
> characters, it will use an escaped output format. And there is the -z
> option.)
On 4/26/23, Thomas Schmitt wrote:
> "FILE" is the minus-sign for standard input. The second blank is there
> to indicate the text mode of sha256sum.
> Only the first blank is somewhat puzzling. But it's always there.
>
>
> https://www.gnu.org/software/coreutils/manual/html_node/sha2-utilities#sha2-utilities
> points to
>
> https://www.gnu.org/software/coreutils/manual/html_node/md5sum-invocation.html
> which says
> For each file, ‘md5sum’ outputs by default, the MD5 checksum, a space,
> a flag indicating binary or text input mode, and the file name. Binary
> mode is indicated with ‘*’, text mode with ‘ ’ (space). Binary mode is
> the default on systems where it’s significant, otherwise text mode is
> the default. The cksum command always uses binary mode and a ‘ ’
> (space) flag.
>
> So the first blank can be relied on and thus the proposal by Andy Smith
> to use "awk '{print $1}'" is valid.
OK, now I see why cutting off the string on the first space that
appears is safe. I never saw such cases because I always used sha*sums
on files. I would expect if a user enters a string via printf that was
all there was to it. Of course, sha*sums can tell apart a file from a
text string.
On 4/26/23, Jeffrey Walton wrote:
> There's no guarantee a URL will map onto a filesystem.
> I seem to
> recall Stunnel tried to do that in a caching mode, but it had weird
> corner cases. (In addition to problems with filesystems that had
> character set and path limitations).
Well, no; and I am fine with:
a) trying to best match both; the URL path as best as possible
b) the extra malabarism base64-ing and hashsing the name of the file ...
Something I have learned as a corpora research kind of guy is not to
ever try to "educate" people. I would just take their sh!t as they
dump it and cleanse, deal with it!
You would not hear the end of it if I start telling stories of the
kind of cr@p you find out there when you look at the web from that
point of view.
> I think your best bet is to digest the URL into a representation. I
> suggest using SipHash+Base64 or Base64URL. SipHash provides collision
> resistance, a uniform distribution, and its fast. SipHash has a very
> good pedigree since it was designed by Jean-Philippe Aumasson and
> Daniel J. Bernstein. The final Base64 or Base64URL encoding ensures
> you stay within printable character range without reserved file system
> characters.
Thank you I will look into what they did when I get a chance,
lbrtchx
On 4/26/23, Albretch Mueller wrote:
> On 4/26/23, David Wright wrote:
>> I guess you need the expense of sha256 rather than md5 as you're
>> downloading the entire web?
>
> I am not downloading the entire web. I have no way of knowing how
> they entertained those ideations but I think we could use their
> estimate when they said that approximately 1 million and a half books
> have been ever published. Think of it! It is not that much data. It
> would all fit nicely in one hard drive include some searching
> capability and "bye bye google" will be the name of your movie.
>
> On 4/26/23, Dan Ritter wrote:
>> The only characters used in the sha256 hash itself are [a-f] and
>> [0-9]
>
> Yes, I knew that; that is why I could not understand why sha256sum
> was being "courteous" to me.
>
> On 4/26/23, Nicolas George wrote:
>> shaXsum always writes X/4 hexadecimal nibbles then two spaces then the
>> file name. If the input is from stdin, then the convention is the file
>> name is ‘-’.
>>
>> (Well, not always always: if the file name contains very special
>> characters, it will use an escaped output format. And there is the -z
>> option.)
>
> On 4/26/23, Thomas Schmitt wrote:
>> "FILE" is the minus-sign for standard
Re: sha256sum --text generating blank spaces and hyphens?
On 4/26/23, David Wright wrote:
> I guess you need the expense of sha256 rather than md5 as you're
> downloading the entire web?
I am not downloading the entire web. I have no way of knowing how
they entertained those ideations but I think we could use their
estimate when they said that approximately 1 million and a half books
have been ever published. Think of it! It is not that much data. It
would all fit nicely in one hard drive include some searching
capability and "bye bye google" will be the name of your movie.
On 4/26/23, Dan Ritter wrote:
> The only characters used in the sha256 hash itself are [a-f] and
> [0-9]
Yes, I knew that; that is why I could not understand why sha256sum
was being "courteous" to me.
On 4/26/23, Nicolas George wrote:
> shaXsum always writes X/4 hexadecimal nibbles then two spaces then the
> file name. If the input is from stdin, then the convention is the file
> name is ‘-’.
>
> (Well, not always always: if the file name contains very special
> characters, it will use an escaped output format. And there is the -z
> option.)
On 4/26/23, Thomas Schmitt wrote:
> "FILE" is the minus-sign for standard input. The second blank is there
> to indicate the text mode of sha256sum.
> Only the first blank is somewhat puzzling. But it's always there.
>
>
> https://www.gnu.org/software/coreutils/manual/html_node/sha2-utilities#sha2-utilities
> points to
>
> https://www.gnu.org/software/coreutils/manual/html_node/md5sum-invocation.html
> which says
> For each file, ‘md5sum’ outputs by default, the MD5 checksum, a space,
> a flag indicating binary or text input mode, and the file name. Binary
> mode is indicated with ‘*’, text mode with ‘ ’ (space). Binary mode is
> the default on systems where it’s significant, otherwise text mode is
> the default. The cksum command always uses binary mode and a ‘ ’
> (space) flag.
>
> So the first blank can be relied on and thus the proposal by Andy Smith
> to use "awk '{print $1}'" is valid.
OK, now I see why cutting off the string on the first space that
appears is safe. I never saw such cases because I always used sha*sums
on files. I would expect if a user enters a string via printf that was
all there was to it. Of course, sha*sums can tell apart a file from a
string a plain text.
On 4/26/23, Jeffrey Walton wrote:
> There's no guarantee a URL will map onto a filesystem.
> I seem to
> recall Stunnel tried to do that in a caching mode, but it had weird
> corner cases. (In addition to problems with filesystems that had
> character set and path limitations).
Well, no; and I am fine with:
a) trying to best match both; the URL path as best as possible
b) the extra malabarism base64-ing and hashsing the name of the file ...
Something I have learned as a corpora research kind of guy is not to
ever try to "educate" people. I would just take their sh!t as they
dump it and cleanse, deal with it!
You would not hear the end of it if I start telling stories of the
kind of cr@p you find out there when you look at the web from that
point of view: from folks at archive.org who would list: "Henry
Valentine Miller", "Henry V. Miller", "Henry Miller", "henry miller",
"Miller, Henry", "Miller, Henry 12-1891 06-1980" apparently as
different authors/"creators", to the gutenberb.org large text bank
including some protagonistic bs in the actual texts, to developers of
libreoffice watermarking text with some cr@p which of course is being
used for "monitoring" purposes by the kinds of folks who put
"intelligence" in the names of the organizations they work for and to
make sure they are making sense they put flags around them when they
fart through their mouths whatever nonsense they think of.
I had had rehearsing day dreams about becoming a dictator of the
world ;-) and making people do "the right thing" (tm) ... until I had
once an epiphany while watching Trump talk to a media prestitude who
caracteristically wasn't making much sense. After asking a few
questions trying to make sense of what she was saying, prestitude said
"let me formulate it better". Trump quietly sat back saying: "OK, take
your time"!!!
I was amazed! There you have someone the U.S. media, who as a mouth
piece of the status quo, were being viscerally offensive towards
anything relating to him, including posting on the front page of
mainstream US news papers naked pictures of his wife and mother of his
child one month before she became "the first lady" and he took it
easy, respectfully on her! That was the best case I have noticed so
far of "separating the message from the messenger". I mean people who
erect all those pay walls and somehow see themselves as authoring,
guarding content are not even the messengers and we all have to put up
with their bs.
> I think your best bet is to digest the URL into a representation. I
> suggest using SipHash+Base64 or Base64URL. SipHash provides collision
> resistance, a uniform distribution, and its fast. SipHash has a very
> good pe
RE: Sales at INFOCOMM 2023
Hi Good Day, Would you like to have a look at the cost and counts for a better review? Do you want me to share the sample list, if required? Thanks, Evelyn From: Evelyn Davis Sent: Tuesday, April 25, 2023 1:32 PM To: debian-user@lists.debian.org Subject: Sales at INFOCOMM 2023 Importance: High Hi, Would you be interested in INFOCOMM 2023 Attendees Database with Email Address, Phone Number etc.. Attendees:- Systems Integrator/Dealer/Contractor, Manufacturer, Distributor, Manufacturer/Independent Representative, Design/Business Consultant/Architect, Rental/Staging Firm, Independent Programmer.. Please let me know if you are Interested , so that I can share the Pricing and Available Counts.. Regards, Evelyn Davis
Re: AMD ryzen 5 2400G VGA drivers required for Debian 10 based linux OS
Timothy M Butterworth wrote: > On Wed, Apr 26, 2023 at 10:12 AM karans wrote: > > > Dear Debian Team > > > > We have Debian 10 buster based linux OS but we are facing issue after > > install linux > > > > I forwarded this to the Debian User mailing list, which is the end user > support list. Debian developers list is strictly just for developer topics. > > Tim > > > > *Processor - AMD RYZEN 5 2400G* > > *VGA - Advanced Micro Devices Inc AMD/ATI Raven Ridge > > Radeon Vega Series* > > *Kernel - 5.7.0-0.bpo.2-amd64* > > > > We are unable to find compatible drivers for the amdgpu xserver-xorg-video-amdgpu firmware-amd-graphics libdrm-amdgpu1 These are all usable in bullseye (11, currently stable). You should not be installing a new buster at this calendar date; 12 is likely to be stable in just a few months. What specific issues are you seeing? -dsr-
Re: sha256sum --text generating blank spaces and hyphens?
On Wed, Apr 26, 2023 at 02:33:03PM +, Albretch Mueller wrote: [...] > because I would like to include the three strings in the file descriptor: > a) the crazy long name > b) its base64 representation > c) §b's sha256sum representation which is the one used for the file > name and the log of the download. [...] It's your work, of course. > >> // __ $_SHA256: > >> |7d5895cb24ab49692a8ad495e036074fec8e61b22040544f02a9b69c926dbdeb -| > > > > > > I only see harmless hexadecimal chars there. > > > >> I am trying to avoid funky characters and sha256sum --text still > >> generates them!?! > > > > Where are there "funky chars"? > > This is the first time I have seen blank spaces and hyphens in a text > segment's sum. Those characters might be confusing. Ah -- I thing someone else (I think it was Dan, sorry if my memory fails me) pointed that out already. The dash is the "file name" (which in this case was stdin, this follows a widespread convention). All those sums output the sum (never ever spaces in there), a whitespace, then the file name. Background: you can give them multiple args, then they generate a list of sums and names, which you then can conveniently use with the -c option to see whether any of the files has changed. > > Besides, I don't think --text does what you think it does. Quoting > > the manpage: > > > > "Note: There is no difference between binary mode and text > >mode on GNU systems." > > Thank you. I was playing with different options to see if that was > the reason I was getting those white spaces and hyphens at the end. > > Why is that happening? How could it be avoided? COuld you set the > characters used in the representation of a sum? You just cut it out with, e.g. 'cut' like so: sha256sum | cut -d' ' -f1 Cheers -- t signature.asc Description: PGP signature
Re: OpenCL with Radeon GPU
Which leaves me with one question for this mail thread: Can anybody recommend a test program for OpenCL functionality? There are tests from Khronos: https://github.com/KhronosGroup/OpenCL-CTS It's seems to be over 50 tests and then subtests. There are presets to run different test suites from a Python script. I ran only some random ones with ROCm and Mesa OpenCL, using Vega64 or RX 5700 XT. All tested fine with ROCm OpenCL. Mesa OpenCL failed some with Vega64 and then most tests with the RX 5700 XT... This is Debian 12. -- Sarunas Burdulis Dartmouth Mathematics math.dartmouth.edu/~sarunas · https://useplaintext.email · OpenPGP_signature Description: OpenPGP digital signature
(Thread restarted!) Debian installation using debootstrap and grub-install - no entry in ESC boot menu
Hello Max, thanks a lot for your input! I do, however, believe that the problem has a different cause. I came to that conclusion, mainly because the issue with the BIOS boot interface (see my original posting) is still unsolved, but also because I tried using the EFI removable media path (which should bypass any issues with EFI variables) without success. Therefore, and to make it easier for new people entering this thread, I restart the thread now by asking my original question again, in a single and well arranged posting. You can forget everything you read in the thread before if you just read this one post: Hello everyone, I want to install Debian on my Asus UX31A using command line utilities like debootstrap and grub-install. I want to install it to the internal drive /dev/sda, and I want to do so by executing commands on an installer system, which is a system already installed on the external drive /dev/sdb. To reproduce the issue, you should use a current stable Debian Live-CD as the installer system. Just write the Live-CD image to the external drive /dev/sdb using dd. For now, I only want to get a GRUB command line, because that appears to be the difficult part. Here are the step-by-step instructions to reproduce the problem: 1.: On the installer system, type "sudo apt install ..." to install any dependencies required by the recipe (see below). 2.: On the installer system, exercise one of the following two recipes: For the BIOS boot interface: sudo parted /dev/sda mklabel gpt sudo parted /dev/sda mkpart init 0% 512MiB sudo parted /dev/sda mkpart root 512MiB 100% sudo parted /dev/sda set 1 bios_grub on sudo mkfs.ext4 /dev/sda2 sudo mount /dev/sda2 /mnt sudo debootstrap stable /mnt sudo mount --bind /sys /mnt/sys sudo mount --bind /proc /mnt/proc sudo mount --bind /dev /mnt/dev sudo mount --bind /dev/pts /mnt/dev/pts sudo mount --bind /run /mnt/run sudo chroot /mnt apt install grub-pc sudo chroot /mnt grub-install /dev/sda sudo umount /mnt/run sudo umount /mnt/dev/pts sudo umount /mnt/dev sudo umount /mnt/proc sudo umount /mnt/sys sudo umount /mnt For the EFI boot interface: sudo parted /dev/sda mklabel gpt sudo parted /dev/sda mkpart init 0% 512MiB sudo parted /dev/sda mkpart root 512MiB 100% sudo parted /dev/sda set 1 boot on sudo mkfs.vfat /dev/sda1 sudo mkfs.ext4 /dev/sda2 sudo mount /dev/sda2 /mnt sudo mkdir /mnt/boot sudo mkdir /mnt/boot/efi sudo mount /dev/sda1 /mnt/boot/efi sudo debootstrap stable /mnt sudo mount --bind /sys /mnt/sys sudo mount --bind /proc /mnt/proc sudo mount --bind /dev /mnt/dev sudo mount --bind /dev/pts /mnt/dev/pts sudo mount --bind /run /mnt/run sudo chroot /mnt apt install grub-efi sudo chroot /mnt grub-install --target=x86_64-efi /dev/sda sudo chroot /mnt grub-install --target=x86_64-efi --removable /dev/sda sudo umount /mnt/runsudo umount /mnt/dev/pts sudo umount /mnt/dev sudo umount /mnt/proc sudo umount /mnt/sys sudo umount /mnt/boot/efi sudo umount /mnt Please check every command's output before entering the next one. 3.: Shut down the installer system and disconnect the external drive /dev/sdb. 4.: Start the computer with the ESC key pressed. This will show a list of boot options (the ESC boot menu). The expected behavior is that the list contains an entry for the installed system. Selecting that entry will give you a GRUB command line. The actual behavior is that there is only the "Enter Setup" entry in the list, which is always there and does not do what we want (boot to GRUB command line). That much for the step-by-step instructions. Notice that the EFI variant of the recipe does set the "boot" and "esp" flags and the partition has the recommended size. Also notice that the EFI recipe will create the following directory structure on /dev/sda1: drwxr-xr-x 3 root root 16384 Jan 1 1970 /mnt/boot/efi drwxr-xr-x 4 root root 8192 Apr 26 09:33 /mnt/boot/efi/EFI drwxr-xr-x 2 root root 8192 Apr 26 09:33 /mnt/boot/efi/EFI/BOOT -rwxr-xr-x 1 root root 108 Apr 26 09:33 /mnt/boot/efi/EFI/BOOT/BOOTX64.CSV -rwxr-xr-x 1 root root 934240 Apr 26 09:33 /mnt/boot/efi/EFI/BOOT/BOOTX64.EFI -rwxr-xr-x 1 root root 84648 Apr 26 09:33 /mnt/boot/efi/EFI/BOOT/fbx64.efi -rwxr-xr-x 1 root root 126 Apr 26 09:33 /mnt/boot/efi/EFI/BOOT/grub.cfg -rwxr-xr-x 1 root root 3827136 Apr 26 09:33 /mnt/boot/efi/EFI/BOOT/grubx64.efi -rwxr-xr-x 1 root root 845480 Apr 26 09:33 /mnt/boot/efi/EFI/BOOT/mmx64.efi drwxr-xr-x 2 root root 8192 Apr 26 09:33 /mnt/boot/efi/EFI/debian -rwxr-xr-x 1 root root 108 Apr 26 09:33 /mnt/boot/efi/EFI/debian/BOOTX64.CSV -rwxr-xr-x 1 root root 84648 Apr 26 09:33 /mnt/boot/efi/EFI/debian/fbx64.efi -rwxr-xr-x 1 root root 126 Apr 26 09:33 /mnt/boot/efi/EFI/debian/grub.cfg -rwxr-xr-x 1 root root 4150720 Apr 26 09:33 /mnt/boot/efi/EFI/debian/grubx64.efi -rwxr-xr-x 1 root root 845480 Apr 26 09:33 /mnt/boot/efi/EFI/debian/mmx64.efi -rwxr-xr-x 1 root root 934240 Apr 26 09:33 /mnt/boot/efi/EFI/
Re: sha256sum --text generating blank spaces and hyphens?
On Wed, Apr 26, 2023 at 3:42 AM Albretch Mueller wrote:
>
> This is not a debian question per se (more like a Linux bash one),
> but I wasn't able to find an answer on the Internet.
>
> Here is first the problem I am having before you start reading a
> conspiracy theory into it ;-)
>
> I need to somehow map URL on the web to a local file, but you can't
> do that for two main reasons:
>
> 1) URLs are free text
> 2) which people take to their heart's content.
>
> Take for example:
>
>
> https://dokumen.pub/qdownload/nietzsche-und-der-deutsche-geist-band-4-ausbreitung-und-wirkung-des-nietzscheschen-werkes-im-deutschen-sprachraum-bis-zum-ende-des-zweiten-weltkrieges-ein-schrifttumsverzeichnis-der-jahre-1867-1945-ergnzungen-berichtigungen-und-gesamtverzeichnisse-zu-den-bnden-i-iii-9783110202861-9783110189865-3110189860.html
>
> that file and the pdf you would download I need to map to a local
> directory looking like: ... /pub/dokumen/qdownload/ ...
>
> but the file name (excluding the extension) is 306 characters long,
> which Windows NTFS would not swallow. There may be also funky rules
> regarding character sets and where in a string certain chars may be
> used; so, as a way to work around those kinds of problems I:
>
> a) encode the string name as base64
> b) calculate the sha256sum of §a
> c) use §b as file name (of course, leaving the original extension as it is)
> d) include a "§b_file_name.txt" plain text file decriptor which only
> content is the actual prehash name of that file.
>
>
>
> https://dokumen.pub/qdownload/nietzsche-und-der-deutsche-geist-band-4-ausbreitung-und-wirkung-des-nietzscheschen-werkes-im-deutschen-sprachraum-bis-zum-ende-des-zweiten-weltkrieges-ein-schrifttumsverzeichnis-der-jahre-1867-1945-ergnzungen-berichtigungen-und-gesamtverzeichnisse-zu-den-bnden-i-iii-9783110202861-9783110189865-3110189860.html
>
> _TXT="nietzsche-und-der-deutsche-geist-band-4-ausbreitung-und-wirkung-des-nietzscheschen-werkes-im-deutschen-sprachraum-bis-zum-ende-des-zweiten-weltkrieges-ein-schrifttumsverzeichnis-der-jahre-1867-1945-ergnzungen-berichtigungen-und-gesamtverzeichnisse-zu-den-bnden-i-iii-9783110202861-9783110189865-3110189860"
> _B64TXTENC=$(printf '%s' "${_TXT}" | base64 )
> echo "// __ \$_B64TXTENC: |${_B64TXTENC}|"
> _B64TXTDEC=$(printf '%s' "${_B64TXTENC}" | base64 --decode)
> echo "// __ \$_B64TXTDEC: |${_B64TXTDEC}|"
> if [[ "${_TXT}" == "${_B64TXTDEC}" ]]; then
> echo "// __ [[ \${_TXT} == \${_B64TXTDEC} ]]: |${_TXT}|"
> _SHA256=$(printf '%s' "${_TXT}" | sha256sum --text )
> echo "// __ \$_SHA256: |${_SHA256}|"
> fi
>
> // __ $_SHA256:
> |7d5895cb24ab49692a8ad495e036074fec8e61b22040544f02a9b69c926dbdeb -|
>
> I am trying to avoid funky characters and sha256sum --text still
> generates them!?!
>
> I work like this because I need replicate the original URL as a local
> path in a way that would be compatible any file system.
>
> Do you know of a better way to deal with such issues?
There's no guarantee a URL will map onto a filesystem. I seem to
recall Stunnel tried to do that in a caching mode, but it had weird
corner cases. (In addition to problems with filesystems that had
character set and path limitations).
I think your best bet is to digest the URL into a representation. I
suggest using SipHash+Base64 or Base64URL. SipHash provides collision
resistance, a uniform distribution, and its fast. SipHash has a very
good pedigree since it was designed by Jean-Philippe Aumasson and
Daniel J. Bernstein. The final Base64 or Base64URL encoding ensures
you stay within printable character range without reserved file system
characters.
Jeff
Re: Evolution email (problem?)
Can't explain it, but it strikes me it's almost certainly a permissions problem. Patrick On Wed, Apr 26, 2023 at 11:06 AM Default User wrote: > Strange . . . > > I run Debian 11 (Bullseye) Stable, up to date, Gnome 3 desktop > environment. > > I recently set up Evolution email. Works okay. > > Two days ago, I realized that it absolutely refuses to delete email > messages directly from the [Gmail]/All Mail folder of any email > account. To delete a message in the All Mail folder, that is not also > in another folder, the message must be moved into another folder and > then deleted from there. > > I sure think I remember being able to delete directly from the All Mail > folder when I first set up Evolution. > > I re-started Evolution. No change. > I re-booted. No change. > I did sudo aptitude reinstall evolution. No Change. > I moved ~/.local/share/evolution/mail/local/folders.db to Trash, then > re-started Evolution to construct a new folders.db file. No change. > I did sudo aptitude purge evolution, then sudo aptitude install > Evolution. No change. > I moved ~/.local/share/evolution, ~/.cache/evolution, and > ~/.config/evolution to Trash, then did sudo aptitude purge evolution, > then sudo aptitude install Evolution. No change. > I did some research online, seeking a solution, or at least a "good" > explanation. No solution or "good" answer was found. > > But . . . then I booted into a Debian 11.6 Live/Install usb thumb > drive, and then installed Evolution into the Live session, upon which > Evolution DID allow message deletion directly from the [Gmail]/All Mail > folder! > > Back to my regular Debian 11 Stable install. No change. > > It makes no sense to me that it would work from a Debian 11 > Live/Install session, but not (currently) from a regular Debian > session. > > Even if it did not work from a Live Debian session, it makes no sense > to me that Evolution could be designed this way. I see no good reason > that messages can be directly deleted from any other folder, but not > [Gmail]/All Mail. > > Does anyone have a solution, so that messages must be moved to another > folder (if they are not also there already), just to be deleted? Or at > least a "good" explanation as to why Evolution appears to be designed > this way? > > > >
Re: AMD ryzen 5 2400G VGA drivers required for Debian 10 based linux OS
On Wed, Apr 26, 2023 at 10:12 AM karans wrote: > Dear Debian Team > > We have Debian 10 buster based linux OS but we are facing issue after > install linux > I forwarded this to the Debian User mailing list, which is the end user support list. Debian developers list is strictly just for developer topics. Tim > *Processor - AMD RYZEN 5 2400G* > *VGA - Advanced Micro Devices Inc AMD/ATI Raven Ridge > Radeon Vega Series* > *Kernel - 5.7.0-0.bpo.2-amd64* > > We are unable to find compatible drivers for the amdgpu > > > > > > Thanks & Regards, > Karan Sharma / श्री कर्ण शर्मा > Project Engineer /श्री कर्ण शर्मा > Centre for Development of Advanced Computing(C-DAC) / प्रगत संगणन विकास > केन्द्र(सी-डैक) > Tidel Park”, 8th Floor, “D” Block, (North &South) / “टाइडल पार्क”,8वीं > मंजिल, “डी” ब्लॉक, (उत्तर और दक्षिण) > No.4, Rajiv Gandhi Salai / नं.4, राजीव गांधी सलाई > Taramani / तारामणि > Chennai / चेन्नई – 600113 > Ph.No.:044-22542226/27 > Fax No.: 044-22542294 > > > > [ C-DAC is on Social-Media too. Kindly follow us at: > Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ] > > This e-mail is for the sole use of the intended recipient(s) and may > contain confidential and privileged information. If you are not the > intended recipient, please contact the sender by reply e-mail and destroy > all copies and the original message. Any unauthorized review, use, > disclosure, dissemination, forwarding, printing or copying of this email > is strictly prohibited and appropriate legal action will be taken. > > > -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄⠀⠀
Evolution email (problem?)
Strange . . . I run Debian 11 (Bullseye) Stable, up to date, Gnome 3 desktop environment. I recently set up Evolution email. Works okay. Two days ago, I realized that it absolutely refuses to delete email messages directly from the [Gmail]/All Mail folder of any email account. To delete a message in the All Mail folder, that is not also in another folder, the message must be moved into another folder and then deleted from there. I sure think I remember being able to delete directly from the All Mail folder when I first set up Evolution. I re-started Evolution. No change. I re-booted. No change. I did sudo aptitude reinstall evolution. No Change. I moved ~/.local/share/evolution/mail/local/folders.db to Trash, then re-started Evolution to construct a new folders.db file. No change. I did sudo aptitude purge evolution, then sudo aptitude install Evolution. No change. I moved ~/.local/share/evolution, ~/.cache/evolution, and ~/.config/evolution to Trash, then did sudo aptitude purge evolution, then sudo aptitude install Evolution. No change. I did some research online, seeking a solution, or at least a "good" explanation. No solution or "good" answer was found. But . . . then I booted into a Debian 11.6 Live/Install usb thumb drive, and then installed Evolution into the Live session, upon which Evolution DID allow message deletion directly from the [Gmail]/All Mail folder! Back to my regular Debian 11 Stable install. No change. It makes no sense to me that it would work from a Debian 11 Live/Install session, but not (currently) from a regular Debian session. Even if it did not work from a Live Debian session, it makes no sense to me that Evolution could be designed this way. I see no good reason that messages can be directly deleted from any other folder, but not [Gmail]/All Mail. Does anyone have a solution, so that messages must be moved to another folder (if they are not also there already), just to be deleted? Or at least a "good" explanation as to why Evolution appears to be designed this way?
Re: sha256sum --text generating blank spaces and hyphens?
Albretch Mueller wrote:
> On 4/26/23, Andy Smith wrote:
> > If you're referring to the space and then the file name ("-" in case
> > of stdin) on the end, you can just select only the first output up
> > to whitespace with e.g. awk:
> >
> > _SHA256=$(printf '%s' "${_TXT}" | sha256sum | awk '{print $1}')
>
> Yes, you could but I am trying to find out why this is happening
> instead of truncating the string when a space appears because I don't
> think what would be safe.
The white space and the - are not part of the sha256, they are
emitted by sha256sum as a courtesy. You can safely remove
everything starting with the first whitespace.
> >> // __ $_SHA256:
> >> |7d5895cb24ab49692a8ad495e036074fec8e61b22040544f02a9b69c926dbdeb -|
> >
> > I only see harmless hexadecimal chars there.
> >
> >> I am trying to avoid funky characters and sha256sum --text still
> >> generates them!?!
> >
> > Where are there "funky chars"?
>
> This is the first time I have seen blank spaces and hyphens in a text
> segment's sum. Those characters might be confusing.
The white space and the - are not part of the sha256, they are
emitted by sha256sum as a courtesy. You can safely remove
everything starting with the first whitespace.
> Why is that happening? How could it be avoided? COuld you set the
> characters used in the representation of a sum?
The white space and the - are not part of the sha256, they are
emitted by sha256sum as a courtesy. You can safely remove
everything starting with the first whitespace.
The only characters used in the sha256 hash itself are [a-f] and
[0-9]
-dsr-
Re: sha256sum --text generating blank spaces and hyphens?
Hi,
Albretch Mueller wrote:
> > > I am trying to avoid funky characters and sha256sum --text still
> > > generates them!?!
Andy Smith wrote:
> > If you're referring to the space and then the file name ("-" in case
> > of stdin) on the end, you can just select only the first output up
> > to whitespace with e.g. awk:
> Yes, you could but I am trying to find out why this is happening
> instead of truncating the string when a space appears because I don't
> think what would be safe.
One of the blanks and the hyphen-or-minus are announced by the man page:
The default mode is
to print a line with checksum, a character indicating input mode ('*'
for binary, space for text), and name for each FILE.
"FILE" is the minus-sign for standard input. The second blank is there
to indicate the text mode of sha256sum.
Only the first blank is somewhat puzzling. But it's always there.
https://www.gnu.org/software/coreutils/manual/html_node/sha2-utilities#sha2-utilities
points to
https://www.gnu.org/software/coreutils/manual/html_node/md5sum-invocation.html
which says
For each file, ‘md5sum’ outputs by default, the MD5 checksum, a space,
a flag indicating binary or text input mode, and the file name. Binary
mode is indicated with ‘*’, text mode with ‘ ’ (space). Binary mode is
the default on systems where it’s significant, otherwise text mode is
the default. The cksum command always uses binary mode and a ‘ ’
(space) flag.
So the first blank can be relied on and thus the proposal by Andy Smith
to use "awk '{print $1}'" is valid.
Have a nice day :)
Thomas
Re: sha256sum --text generating blank spaces and hyphens?
On Wed 26 Apr 2023 at 14:33:03 (+), Albretch Mueller wrote: > On 4/26/23, to...@tuxteam.de wrote: > >> a) encode the string name as base64 > >> b) calculate the sha256sum of §a > > > > Why the detour over base64? > > because I would like to include the three strings in the file descriptor: > a) the crazy long name > b) its base64 representation The base64 command wraps the output, in case you didn't notice. > c) §b's sha256sum representation which is the one used for the file > name and the log of the download. I guess you need the expense of sha256 rather than md5 as you're downloading the entire web? > I would like to make this scheme "fool (and fail) proof" as they say. > There is no way in earth that a file system messes with all three > aspects of it. > > >> c) use §b as file name (of course, leaving the original extension as it > >> is) > > > > Why the extension? DOS nostalgia? > > The local copies should represent the web URLs as close as possible > in order to minimize "what came from where" kinds of confusions. Also > from the same URL you would then download the corresponding pdf file > with exactly the same name, the only difference being the extension. The extension is part of the name. If you preserve it as is, what happens when it contains a "funky" character. > >> // __ $_SHA256: > >> |7d5895cb24ab49692a8ad495e036074fec8e61b22040544f02a9b69c926dbdeb -| > > > > > > I only see harmless hexadecimal chars there. > > > >> I am trying to avoid funky characters and sha256sum --text still > >> generates them!?! > > > > Where are there "funky chars"? > > This is the first time I have seen blank spaces and hyphens in a text > segment's sum. Those characters might be confusing. You calculated the sha256sum of stdin. - is the name of the input file you encoded. Duh. Cheers, David.
Re: OpenCL with Radeon GPU
Le 26/04/2023 à 15:47, Arno Lehmann a écrit : Hi Jörg-Volker, On 26.04.23 at 11:34, Jörg-Volker Peetz wrote: Hi Arno, Arno Lehmann wrote on 25/04/2023 12:54: Hi Jörg-Volker, Am 25.04.2023 um 11:19 schrieb Jörg-Volker Peetz: ... In Debian testing I see the package `mesa-opencl-icd`. I have no experience with opencl and AMD graphic cards but are very interested how it works in Debian. That's more or less where I am myself... seems a bit too complex for me, at this time ;-) I'm wondering if package mesa-opencl-icd would do the trick (version 22.3.6-1+deb12u1 like the other installed mesa packages). From the description it seems to be the right package: That's the package I tried initially which failed all my (limited) testing due to the hardware not being supported. Mesa 23 is available as experimental, but I did not manage to install that due to dependencies. In the end, you'll have to test with your particular hardware, I think -- I've not been able to find a reliable and realistic list of working hard- and software combinations. Current state, by the way, is that I'm fighting with boinc and systemd in this environment. OpenCL reminds me of the (good|bad) days of building my own kernel based upon incomplete information ;-) As I previously said, I know nothing about the subject so I might be out of topic, but: - in February 2022 someone wrote an interesting article, in French, of the current (bad) state of OpenCL Linux software with AMD hardware - this article points to some English documentation and scripts this person maintain [2] 1. https://linuxfr.org/news/opencl-sous-linux-l-etat-des-pilotes-amd-est-desormais-pire-que-ce-qu-il-etait-a-l-epoque-de-fglrx 2. https://gitlab.com/illwieckz/i-love-compute Hope this helps. Would be fun if I could sink a few days in it. Cheers, Arno OpenPGP_signature Description: OpenPGP digital signature
Re: sha256sum --text generating blank spaces and hyphens?
Albretch Mueller (12023-04-26): > Yes, you could but I am trying to find out why this is happening > instead of truncating the string when a space appears because I don't > think what would be safe. shaXsum always writes X/4 hexadecimal nibbles then two spaces then the file name. If the input is from stdin, then the convention is the file name is ‘-’. (Well, not always always: if the file name contains very special characters, it will use an escaped output format. And there is the -z option.) For your case, just use “cut -c 1-64”. > > Why the detour over base64? > because I would like to include the three strings in the file descriptor: > a) the crazy long name > b) its base64 representation > c) §b's sha256sum representation which is the one used for the file > name and the log of the download. Then do so, but in c, store the SHA-256 of the URL, not the SHA-256 of the base64 encoding of the URL. > The local copies should represent the web URLs as close as possible > in order to minimize "what came from where" kinds of confusions. You are right to do so. Many utilities rely on the extension to decide what to do with a file. Lacking a standardized place to store the file type, it is the most robust options. Applications that rely on probing and heuristics, like libfile and co., are in fact much less reliable and a lot more annoying. (Also, if we were to want a standardized place to store the file type, a lot of user interface would have to be revamped.) OTOH, HTTP does have a place to state the type of the file, and the extension in URLs is not reliable: if you want to do it properly, you must set your local file extension based on the Content-Type response header. > Also > from the same URL you would then download the corresponding pdf file > with exactly the same name, the only difference being the extension. Then you need to exclude the extension from the URL, but a lot of URLs do not have extensions and you should be using the Content-Type instead. This feature is a pipe dream. > This is the first time I have seen blank spaces and hyphens in a text > segment's sum. Those characters might be confusing. See above. Regards, -- Nicolas George signature.asc Description: PGP signature
Re: sha256sum --text generating blank spaces and hyphens?
On 4/26/23, Andy Smith wrote:
> If you're referring to the space and then the file name ("-" in case
> of stdin) on the end, you can just select only the first output up
> to whitespace with e.g. awk:
>
> _SHA256=$(printf '%s' "${_TXT}" | sha256sum | awk '{print $1}')
Yes, you could but I am trying to find out why this is happening
instead of truncating the string when a space appears because I don't
think what would be safe.
> These web sites can change their URLs at any time you know, so it
> may not be worth trying to replicate their structure locally.
yes, I know and my way to deal with such issues is:
a) by including in the name of the web log of the download the date
and time ...
b) once the data file is downloaded, say a pdf file of an old book or
some publication, all the metadata in the front and back pages of the
book are OCRed, the actual title, ISBN, publishing date ...
On 4/26/23, to...@tuxteam.de wrote:
>> a) encode the string name as base64
>> b) calculate the sha256sum of §a
>
> Why the detour over base64?
because I would like to include the three strings in the file descriptor:
a) the crazy long name
b) its base64 representation
c) §b's sha256sum representation which is the one used for the file
name and the log of the download.
I would like to make this scheme "fool (and fail) proof" as they say.
There is no way in earth that a file system messes with all three
aspects of it.
>> c) use §b as file name (of course, leaving the original extension as it
>> is)
>
> Why the extension? DOS nostalgia?
The local copies should represent the web URLs as close as possible
in order to minimize "what came from where" kinds of confusions. Also
from the same URL you would then download the corresponding pdf file
with exactly the same name, the only difference being the extension.
>> // __ $_SHA256:
>> |7d5895cb24ab49692a8ad495e036074fec8e61b22040544f02a9b69c926dbdeb -|
>
>
> I only see harmless hexadecimal chars there.
>
>> I am trying to avoid funky characters and sha256sum --text still
>> generates them!?!
>
> Where are there "funky chars"?
This is the first time I have seen blank spaces and hyphens in a text
segment's sum. Those characters might be confusing.
> Besides, I don't think --text does what you think it does. Quoting
> the manpage:
>
> "Note: There is no difference between binary mode and text
>mode on GNU systems."
Thank you. I was playing with different options to see if that was
the reason I was getting those white spaces and hyphens at the end.
Why is that happening? How could it be avoided? COuld you set the
characters used in the representation of a sum?
lbrtchx
Re: OpenCL with Radeon GPU
Hi Jörg-Volker, On 26.04.23 at 11:34, Jörg-Volker Peetz wrote: Hi Arno, Arno Lehmann wrote on 25/04/2023 12:54: Hi Jörg-Volker, Am 25.04.2023 um 11:19 schrieb Jörg-Volker Peetz: ... In Debian testing I see the package `mesa-opencl-icd`. I have no experience with opencl and AMD graphic cards but are very interested how it works in Debian. That's more or less where I am myself... seems a bit too complex for me, at this time ;-) I'm wondering if package mesa-opencl-icd would do the trick (version 22.3.6-1+deb12u1 like the other installed mesa packages). From the description it seems to be the right package: That's the package I tried initially which failed all my (limited) testing due to the hardware not being supported. Mesa 23 is available as experimental, but I did not manage to install that due to dependencies. In the end, you'll have to test with your particular hardware, I think -- I've not been able to find a reliable and realistic list of working hard- and software combinations. Current state, by the way, is that I'm fighting with boinc and systemd in this environment. OpenCL reminds me of the (good|bad) days of building my own kernel based upon incomplete information ;-) Would be fun if I could sink a few days in it. Cheers, Arno -- Arno Lehmann IT-Service Lehmann Sandstr. 6, 49080 Osnabrück
Re: Email clients and IMAP search support
Lionel Élie Mamane writes: > On Sun, Apr 16, 2023 at 05:01:53PM +0100, Andre Rodier wrote: > >> Is there any desktop email client on Debian, that supports server >> side IMAP search, please ? > > mutt makes a server-side search when the search operator starts with > "=" instead of "~"; this also means that it is a string search rather > than a regexp search, if I understand correctly this is due to the > IMAP protocol search not supporting regexps. > > So e.g. "=s f.o" makes a server-side search for the exact string "f.o" > in the subject, but "~s f.o" makes a client-side search in subject for > f, then any character, then o. With Gnus on Emacs you can run general IMAP queries: Example: C-u G G ON "17-Aug-2011" RET imap RET Other keywords: SUBJECT TO FROM BEFORE SINCE See: http://tools.ietf.org/html/rfc1730#section-6.4.4 Cheers, Loris -- This signature is currently under constuction.
AW: EPSON ET M 1120 new printer: If You can read this, you are using the wrong driver
Good afternoon How can I do more structure? Thank You Regards Sophie Von: Brian Gesendet: Samstag, 15. April 2023 11:33 An: debian-user@lists.debian.org Betreff: Re: EPSON ET M 1120 new printer: If You can read this, you are using the wrong driver On Fri 14 Apr 2023 at 19:28:19 -0400, The Wanderer wrote: > On 2023-04-14 at 19:17, Brian wrote: [...] > > That's an issue for the OP, not me. > > Certainly. I was meaning that bullet-point item as an addendum to the > list you provided (which I understand to have been aimed at the OP), not > as something directed at you. Apologies. I should have taken more notice of the structure of your mail. -- Brian.
Re: sha256sum --text generating blank spaces and hyphens?
Hello,
On Wed, Apr 26, 2023 at 07:41:56AM +, Albretch Mueller wrote:
> _SHA256=$(printf '%s' "${_TXT}" | sha256sum --text )
> echo "// __ \$_SHA256: |${_SHA256}|"
[…]
> // __ $_SHA256:
> |7d5895cb24ab49692a8ad495e036074fec8e61b22040544f02a9b69c926dbdeb -|
>
> I am trying to avoid funky characters and sha256sum --text still
> generates them!?!
If you're referring to the space and then the file name ("-" in case
of stdin) on the end, you can just select only the first output up
to whitespace with e.g. awk:
_SHA256=$(printf '%s' "${_TXT}" | sha256sum | awk '{print $1}')
Your use of "--text" does nothing by the way.
> I work like this because I need replicate the original URL as a local
> path in a way that would be compatible any file system.
These web sites can change their URLs at any time you know, so it
may not be worth trying to replicate their structure locally.
Also maybe you want some sort of web site mirroring solution.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
Re: Debian installation using debootstrap and grub-install - no entry in ESC boot menu
David Wright (12023-04-25): > Don't knock it! The Human Era is much easier for us to parse than ;-) > the French Republican calendar (pre 2018). I had not realized I had fans devoted to the point of tracking the eras of my mail attribution. ;-)² Regards, -- Nicolas George signature.asc Description: PGP signature
Re: OpenCL with Radeon GPU
Hi Arno, Arno Lehmann wrote on 25/04/2023 12:54: Hi Jörg-Volker, Am 25.04.2023 um 11:19 schrieb Jörg-Volker Peetz: Hi, which mesa packages do you have installed? None providing OpenCL capabilities at that time, but if you followed this thread, you are aware of this already: # LANG=C dpkg -l '*mesa*' | cut -c 1-72 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Tri |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Archite +++-===--=== ii libegl-mesa0:amd64 22.3.6-1+deb12u1 amd64 un libegl1-mesa-dev un libgl1-mesa-dev ii libgl1-mesa-dri:amd64 22.3.6-1+deb12u1 amd64 un libgl1-mesa-glx ii libglapi-mesa:amd64 22.3.6-1+deb12u1 amd64 un libgles2-mesa-dev ii libglu1-mesa:amd64 9.0.2-1.1 amd64 ii libglx-mesa0:amd64 22.3.6-1+deb12u1 amd64 un libwayland-egl1-mesa ii mesa-amdgpu-common-dev 1:22.3.0.50403-1538762.20.04 amd64 ii mesa-amdgpu-omx-drivers:amd64 1:22.3.0.50403-1538762.20.04 amd64 ii mesa-amdgpu-va-drivers:amd64 1:22.3.0.50403-1538762.20.04 amd64 ii mesa-amdgpu-vdpau-drivers:amd64 1:22.3.0.50403-1538762.20.04 amd64 ii mesa-common-dev:amd64 22.3.6-1+deb12u1 amd64 un mesa-opencl-icd ii mesa-utils 8.5.0-1 amd64 ii mesa-utils-bin:amd64 8.5.0-1 amd64 un mesa-utils-extra ii mesa-va-drivers:amd64 22.3.6-1+deb12u1 amd64 ii mesa-vdpau-drivers:amd64 22.3.6-1+deb12u1 amd64 ii mesa-vulkan-drivers:amd64 22.3.6-1+deb12u1 amd64 un mesag3 un xlibmesa3 In Debian testing I see the package `mesa-opencl-icd`. I have no experience with opencl and AMD graphic cards but are very interested how it works in Debian. That's more or less where I am myself... seems a bit too complex for me, at this time ;-) I'm wondering if package mesa-opencl-icd would do the trick (version 22.3.6-1+deb12u1 like the other installed mesa packages). From the description it seems to be the right package: free implementation of the OpenCL API -- ICD runtime This package contains the mesa implementation of the OpenCL (Open Compute Language) library, which is intended for use with an ICD loader. OpenCL provides a standardized interface for computational analysis on graphical processing units. Regards, Jörg.
Re: Debian installation using debootstrap and grub-install - no entry in ESC boot menu
Greg Wooledge (12023-04-25):
> find /mnt/boot/efi -exec ls -dl {} +
zsh
ls -dl /mnt/boot/efi/**/*
Regards,
--
Nicolas George
signature.asc
Description: PGP signature
Re: sha256sum --text generating blank spaces and hyphens?
On Wed, Apr 26, 2023 at 07:41:56AM +, Albretch Mueller wrote: > This is not a debian question per se (more like a Linux bash one), > but I wasn't able to find an answer on the Internet. > > Here is first the problem I am having before you start reading a > conspiracy theory into it ;-) > > I need to somehow map URL on the web to a local file, but you can't > do that for two main reasons: OK. [...] > but the file name (excluding the extension) is 306 characters long, > which Windows NTFS [...] There's the first problem. > a) encode the string name as base64 > b) calculate the sha256sum of §a Why the detour over base64? > c) use §b as file name (of course, leaving the original extension as it is) Why the extension? DOS nostalgia? > d) include a "§b_file_name.txt" plain text file decriptor which only > content is the actual prehash name of that file. OK. [...] > // __ $_SHA256: > |7d5895cb24ab49692a8ad495e036074fec8e61b22040544f02a9b69c926dbdeb -| I only see harmless hexadecimal chars there. > I am trying to avoid funky characters and sha256sum --text still > generates them!?! Where are there "funky chars"? > I work like this because I need replicate the original URL as a local > path in a way that would be compatible any file system. > > Do you know of a better way to deal with such issues? Besides, I don't think --text does what you think it does. Quoting the manpage: "Note: There is no difference between binary mode and text mode on GNU systems." This is about *reading* the input in text or binary mode, which are equivalent in most civilised operating systems. Cheers -- t signature.asc Description: PGP signature
Re: Email clients and IMAP search support
On Sun, Apr 16, 2023 at 05:01:53PM +0100, Andre Rodier wrote: > Is there any desktop email client on Debian, that supports server > side IMAP search, please ? mutt makes a server-side search when the search operator starts with "=" instead of "~"; this also means that it is a string search rather than a regexp search, if I understand correctly this is due to the IMAP protocol search not supporting regexps. So e.g. "=s f.o" makes a server-side search for the exact string "f.o" in the subject, but "~s f.o" makes a client-side search in subject for f, then any character, then o.
sha256sum --text generating blank spaces and hyphens?
This is not a debian question per se (more like a Linux bash one),
but I wasn't able to find an answer on the Internet.
Here is first the problem I am having before you start reading a
conspiracy theory into it ;-)
I need to somehow map URL on the web to a local file, but you can't
do that for two main reasons:
1) URLs are free text
2) which people take to their heart's content.
Take for example:
https://dokumen.pub/qdownload/nietzsche-und-der-deutsche-geist-band-4-ausbreitung-und-wirkung-des-nietzscheschen-werkes-im-deutschen-sprachraum-bis-zum-ende-des-zweiten-weltkrieges-ein-schrifttumsverzeichnis-der-jahre-1867-1945-ergnzungen-berichtigungen-und-gesamtverzeichnisse-zu-den-bnden-i-iii-9783110202861-9783110189865-3110189860.html
that file and the pdf you would download I need to map to a local
directory looking like: ... /pub/dokumen/qdownload/ ...
but the file name (excluding the extension) is 306 characters long,
which Windows NTFS would not swallow. There may be also funky rules
regarding character sets and where in a string certain chars may be
used; so, as a way to work around those kinds of problems I:
a) encode the string name as base64
b) calculate the sha256sum of §a
c) use §b as file name (of course, leaving the original extension as it is)
d) include a "§b_file_name.txt" plain text file decriptor which only
content is the actual prehash name of that file.
https://dokumen.pub/qdownload/nietzsche-und-der-deutsche-geist-band-4-ausbreitung-und-wirkung-des-nietzscheschen-werkes-im-deutschen-sprachraum-bis-zum-ende-des-zweiten-weltkrieges-ein-schrifttumsverzeichnis-der-jahre-1867-1945-ergnzungen-berichtigungen-und-gesamtverzeichnisse-zu-den-bnden-i-iii-9783110202861-9783110189865-3110189860.html
_TXT="nietzsche-und-der-deutsche-geist-band-4-ausbreitung-und-wirkung-des-nietzscheschen-werkes-im-deutschen-sprachraum-bis-zum-ende-des-zweiten-weltkrieges-ein-schrifttumsverzeichnis-der-jahre-1867-1945-ergnzungen-berichtigungen-und-gesamtverzeichnisse-zu-den-bnden-i-iii-9783110202861-9783110189865-3110189860"
_B64TXTENC=$(printf '%s' "${_TXT}" | base64 )
echo "// __ \$_B64TXTENC: |${_B64TXTENC}|"
_B64TXTDEC=$(printf '%s' "${_B64TXTENC}" | base64 --decode)
echo "// __ \$_B64TXTDEC: |${_B64TXTDEC}|"
if [[ "${_TXT}" == "${_B64TXTDEC}" ]]; then
echo "// __ [[ \${_TXT} == \${_B64TXTDEC} ]]: |${_TXT}|"
_SHA256=$(printf '%s' "${_TXT}" | sha256sum --text )
echo "// __ \$_SHA256: |${_SHA256}|"
fi
// __ $_SHA256:
|7d5895cb24ab49692a8ad495e036074fec8e61b22040544f02a9b69c926dbdeb -|
I am trying to avoid funky characters and sha256sum --text still
generates them!?!
I work like this because I need replicate the original URL as a local
path in a way that would be compatible any file system.
Do you know of a better way to deal with such issues?
lbrtchx
