Re: [DNG] mutt attachment problem
From: "dng" ; Sent: Monday, August 22, 2022 4:56:08 PM Antony Stone wrote: > Haines Brown wrote: > > The size of the zip file is 164 Mb [...] > Perhaps some kind souls on the list might suggest possible ways to > send large binary files? That's the real problem and it needs a real > solution. > > Bob A site that can transfer very large files, allegedly securely, is: https://wormhole.app/ For files up to 5Gb in size, the files are stored on a server for a maximum of 24 hours. HTH, Xenguy ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] mutt attachment problem
Hi Haines, On Mon, 2022-08-22 at 14:56 -0600, Bob Proulx via Dng wrote: > Antony Stone wrote: > > Haines Brown wrote: > > > The size of the zip file is 164 Mb > > > > 164MB! OMG! Repeat after me. "SMTP is not a file transport > protocol." The likelihood of being able to send a 164MB email > message from one random system on the net to another random system on > the net today is vanishingly small. The default for most popular > mail transport agents even today is 10MB max in size. Though most > sites have increased that to at least 50MB and some to 100MB due to > people trying to send photos through email. But 164MB? I don't know > of any site that allows such a large single email. Gmail limits > message size to 25MB > https://support.google.com/a/answer/1366776?hl=en. > > Since email is not a file transport protocol I suggest using a > different method to transfer those files. I am worthless for > suggesting a large binary file drop method since I have my own web > site and so I always use it for these things. I just copy it there > and pass along a URL. But I know that not everyone maintains their > own servers and associated web sites. > > Perhaps some kind souls on the list might suggest possible ways to > send large binary files? That's the real problem and it needs > a real solution. > If you have a Google account then you /could/ just use Google Drive: https://drive.google.com/drive/my-drive Google Drive has a 15GB capacity free tier, plenty for what you need, if you haven't filled it already. Create a shared folder on your Google Drive. Copy and paste the zip file to it. Allow the recipient viewer access to the shared folder (you can allow anyone or be specific to the recipient(s)). Then just send then a link to the file, they can then just click on the link and the file will download. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] mutt attachment problem
On Mon, Aug 22, 2022 at 02:56:08PM -0600, Bob Proulx via Dng wrote: > 164MB! OMG! Repeat after me. "SMTP is not a file transport > protocol." The likelihood of being able to send a 164MB email message > from one random system on the net to another random system on the net > today is vanishingly small. The default for most popular mail > transport agents even today is 10MB max in size. Though most sites > have increased that to at least 50MB and some to 100MB due to people > trying to send photos through email. But 164MB? I don't know of any > site that allows such a large single email. Gmail limits message size > to 25MB https://support.google.com/a/answer/1366776?hl=en. > > Since email is not a file transport protocol I suggest using a > different method to transfer those files. I am worthless for > suggesting a large binary file drop method since I have my own web > site and so I always use it for these things. I just copy it there > and pass along a URL. But I know that not everyone maintains their > own servers and associated web sites. > > Perhaps some kind souls on the list might suggest possible ways to > send large binary files? That's the real problem and it needs a real > solution. There are various services for sending large files. Dropbox and Wetransfer are the big ones, but increasingly complicated to use. I use the following web service. https://send.vis.ee/ The author also provides a CLI utility. I can't comment on the security of these methods. -- Joel Roth ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Wifi dropping ramdomly
Jim Murphy via Dng wrote: > My wifi connection drops randomly. It can sometimes run for days. > Other times it may drop within hours of a reboot. There seems to be > no pattern to when. Initially rebooting seemed to be the only way to > get the network back. Under xfce4 disabling the wifi and/or network, > then re-enabling them had no effect. After many google searches > I finally found at: > > https://askubuntu.com/questions/26054/how-to-restart-wifi-interface-without-rebooting-it-drops-connection > > I now have the alias(zsh): > > alias reload_network_module='sudo modprobe -r iwldvm && sudo modprobe > iwldvm' > > to re-enable the wifi. So far this has restored the network connection > without having to reboot. Strange as it may seem, the wifi connection > has stopped dropping as frequently since reloading the iwldvm module > this way.?? FWIW Is this problematic WiFi Access Point encrypted using WPA/WPA2? Or is it an open not encrypted Access Point? I find that WPA/WPA2 APs are perfectly reliable using wpasupplicant which will handle glitches and reconnecting without problem. But I find that open APs are problematic. They will often glitch and drop the connection. And since those are connected to directly from the Linux kernel the connection simply drops. The WiFi manager utility monitoring the connection must notice this and retry the connection. Being a glitch the retry always succeeds. But how well this is handled depends upon the connection manager. Up until now I have been using WICD. But of course as all of us know that is a python 2 program and as we upgrade from Beowulf to Chimaera we wicd users are forced to find alternatives. The connman network connection manager is often recommended for those like me who have been frustrated by network-manager. > Computer: ThinkPad X230 > configuration: broadcast=yes driver=iwlwifi I normally use an X220 with the same driver. I am using the firmware-iwlwifi package from non-free. I have no problems with WPA/WPA2 sites. And some open APs are perfectly reliable. While other open APs glitch and drop the connection very often. The wicd manager handles these seemlessly. > % ls /lib/modules/**/iwldvm.ko > /lib/modules/5.10.0-10-amd64/kernel/drivers/net/wireless/intel/iwlwifi/dvm/iwldvm.ko > /lib/modules/5.10.0-9-amd64/kernel/drivers/net/wireless/intel/iwlwifi/dvm/iwldvm.ko That's the free software portion that is in Linux kernel main. However to install the iwlwifi driver you will need the files from the firmware-iwlwifi package. Do you have it installed? dpkg -l | grep firmware-iwlwifi If not then enable the non-free suite and install it. apt-get install firmware-iwlwifi > If anyone has any advice it would be appreciated. Since I have a > workaround it is just an annoyance. For some debugging one can run ip monitor and see the status changes of network devices as they happen. ip monitor And then for example I might associate with an open AP. sudo iw dev wlan0 connect "Starbucks WiFi" And then I might see this from "ip monitor". Also similar data is logged to the /var/log/syslog file. 10.0.0.1 dev wlan0 lladdr 74:83:c2:78:b0:8b STALE 10.0.0.1 dev wlan0 lladdr 74:83:c2:78:b0:8b PROBE 10.0.0.1 dev wlan0 lladdr 74:83:c2:78:b0:8b REACHABLE 10.0.0.1 dev wlan0 lladdr 74:83:c2:78:b0:8b STALE 10.0.0.1 dev wlan0 lladdr 74:83:c2:78:b0:8b PROBE 10.0.0.1 dev wlan0 lladdr 74:83:c2:78:b0:8b REACHABLE Everything is all good. And then see this. Deleted 10.0.0.1 dev wlan0 lladdr 74:83:c2:78:b0:8b REACHABLE Deleted ff02::2 dev wlan0 lladdr 33:33:00:00:00:02 NOARP Deleted ff02::16 dev wlan0 lladdr 33:33:00:00:00:16 NOARP 2: wlan0: mtu 1500 qdisc noqueue state DOWN group default link/ether 20:1e:88:78:61:94 brd ff:ff:ff:ff:ff:ff 2: wlan0: link/ether 10.0.0.1 dev wlan0 FAILED 10.0.0.1 dev wlan0 FAILED 10.0.0.1 dev wlan0 FAILED 10.0.0.1 dev wlan0 FAILED 10.0.0.1 dev wlan0 FAILED Deleted 2: wlan0inet 10.0.8.118/20 brd 10.0.15.255 scope global dynamic wlan0 valid_lft 3826sec preferred_lft 3826sec Deleted 10.0.0.0/20 dev wlan0 proto kernel scope link src 10.0.8.118 linkdown Deleted broadcast 10.0.15.255 dev wlan0 table local proto kernel scope link src 10.0.8.118 linkdown Deleted local 10.0.8.118 dev wlan0 table local proto kernel scope host src 10.0.8.118 Deleted 10.0.0.1 dev wlan0 INCOMPLETE A glitch has caused the connection to the open access point to fail and the connection was dropped. I find that the local Starbucks WiFi does this very often. Another local coffee shop with an open AP however is absolutely reliable and never drops the connection. A network connection manager would retry the connection and that would immediately succeed. Here I am working the task manually so I am the connection manager. sudo iw dev wlan0 connect "Starbucks WiFi" That's normally handled automatically by
Re: [DNG] Installing build-essential on Chimaera PPC
On Mon, Aug 22, 2022 at 08:37:52PM +0200, Luciano Mannucci wrote: > > I installed a Chimaera guest on my KVM/quemu PPC (well, not exactly; > I had to install a Debian bullseye and then migrate using rrq script). > Now I'm trying to install some usefull software via apt-get and it says > I have broken packages. This is what I typed (with anwers :): > > root@bob:~# apt-get install build-essential > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > libtirpc-dev : Depends: libtirpc3 (= 1.3.1-1) but 1.3.1-1+deb11u1 is to be > installed > E: Unable to correct problems, you have held broken packages. > > Do I have any chance to correct that issue? I think your sources.list lines have soe impurity, because the expected installation version for libtirpc-dev is 1.3.1-1+deb11u1 and that package depends on "libtirpc3 (= 1.3.1-1+deb11u1)". If/when your sources.list lines are correct, then the first step would be # apt-get update so as to ensure that your local Packages files are up to date, and then this particular problems should no longer come up. Ralph. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] mutt attachment problem
Antony Stone wrote: > Haines Brown wrote: > > The size of the zip file is 164 Mb > > Just in case it's actually your mail service provider responding to your mail > client trying to send such a large message, try the same thing but with a > small zip file (such as 2Mb) to see whether that nakes the difference. 164MB! OMG! Repeat after me. "SMTP is not a file transport protocol." The likelihood of being able to send a 164MB email message from one random system on the net to another random system on the net today is vanishingly small. The default for most popular mail transport agents even today is 10MB max in size. Though most sites have increased that to at least 50MB and some to 100MB due to people trying to send photos through email. But 164MB? I don't know of any site that allows such a large single email. Gmail limits message size to 25MB https://support.google.com/a/answer/1366776?hl=en. Since email is not a file transport protocol I suggest using a different method to transfer those files. I am worthless for suggesting a large binary file drop method since I have my own web site and so I always use it for these things. I just copy it there and pass along a URL. But I know that not everyone maintains their own servers and associated web sites. Perhaps some kind souls on the list might suggest possible ways to send large binary files? That's the real problem and it needs a real solution. Bob signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Installing build-essential on Chimaera PPC
On 22-08-2022 20:37, Luciano Mannucci wrote: I installed a Chimaera guest on my KVM/quemu PPC (well, not exactly; I had to install a Debian bullseye and then migrate using rrq script). Now I'm trying to install some usefull software via apt-get and it says I have broken packages. This is what I typed (with anwers :): root@bob:~# apt-get install build-essential Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libtirpc-dev : Depends: libtirpc3 (= 1.3.1-1) but 1.3.1-1+deb11u1 is to be installed E: Unable to correct problems, you have held broken packages. Do I have any chance to correct that issue? Many thanks to everybody, Luciano. You already tried the old: apt-get -f install to resolve the dependency? Grtz. Nick ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Installing build-essential on Chimaera PPC
I installed a Chimaera guest on my KVM/quemu PPC (well, not exactly; I had to install a Debian bullseye and then migrate using rrq script). Now I'm trying to install some usefull software via apt-get and it says I have broken packages. This is what I typed (with anwers :): root@bob:~# apt-get install build-essential Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libtirpc-dev : Depends: libtirpc3 (= 1.3.1-1) but 1.3.1-1+deb11u1 is to be installed E: Unable to correct problems, you have held broken packages. Do I have any chance to correct that issue? Many thanks to everybody, Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 02485781 FAX: +39 0248028247 X AGAINST HTML MAIL/ E-MAIL: posthams...@sublink.sublink.org / \ AND POSTINGS/ WWW: http://www.lesassaie.IT/ ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] mutt attachment problem
On Monday 22 August 2022 at 18:10:53, Haines Brown wrote: > I usually have no problem sending attachments with mutt. But now I > want to send a directory that holds files: > > ./patthToDirectory/directory > > This does not work because I gather attachements must be > single files. Is not a directory a single file?. Highly technically, yes, a directory is a single file, however it is a file containing filenames and links to inodes, which are the locations on disk of the data in those files. So, although you might find some way of sending the file "." to someone, they would nto receive the content of the files - at best, they would receive a list of the names, and pointers to where they reside on the file system in your computer. > So I zipped the directory. But when I try to attach it I get the error Please show us exactly how you attached it. > "Error sending message, child exited 1 ()" Is that really it - "Error sending message"? No further information about what the error is? > My fishing on line did not find a solution. What is this "child"? Is > it the attachment process? I do not know mutt well enough to speculate on an answer to that. > The size of the zip file is 164 Mb Just in case it's actually your mail service provider responding to your mail client trying to send such a large message, try the same thing but with a small zip file (such as 2Mb) to see whether that nakes the difference. Antony. -- "Tannenbaumschmuck" is a perfectly reasonable German word meaning Christmas tree decorations, and is not a quote from Linus Torvalds. Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] mutt attachment problem
I usually have no problem sending attachments with mutt. But now I want to send a directory that holds files: ./patthToDirectory/directory This does not work because I gather attachements must be single files. Is not a directory a single file?. So I zipped the directory. But when I try to attach it I get the error "Error sending message, child exited 1 ()" My fishing on line did not find a solution. What is this "child"? Is it the attachment process? My version of mutt is 2.2.6-1 The size of the zip file is 164 Mb The file has a .zip extension. The path is no longer than usual Haines Brown ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Another problem you won't have without Systemd (or separate oomd)
On 22-08-2022 17:31, Didier Kryn wrote: Le 20/08/2022 à 10:20, Martin Steigerwald a écrit : oomd may make sense in certain cloud based workloads, maybe, just maybe. However… on a desktop? You are frigging kidding me, aren't you? Well, it can happen to anybody to write an application which leaks memory. The oom killer is automatically launched by the kernel when memory pressure is too high, and it is a necessity. The problem here is with systemd's oom killer, and/or with Gnome. -- Didier Depends on what you call a problem.I do not have a problem with systemd and Gnome killing each other. The sooner the better. Grtz Nick ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Another problem you won't have without Systemd (or separate oomd)
Le 20/08/2022 à 10:20, Martin Steigerwald a écrit : oomd may make sense in certain cloud based workloads, maybe, just maybe. However… on a desktop? You are frigging kidding me, aren't you? Well, it can happen to anybody to write an application which leaks memory. The oom killer is automatically launched by the kernel when memory pressure is too high, and it is a necessity. The problem here is with systemd's oom killer, and/or with Gnome. -- Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
