brolin_empey | Joerg-Neo900: SFTP has at least two possible meanings: Secure File Transfer Protocol or Secure Shell File Transfer Protocol. | 08:14 |
---|---|---|
Joerg-Neo900 | brolin_empey: my mimetypes interprete SFTP:// in unambiguous way | 13:54 |
Joerg-Neo900 | https://www.startpage.com/do/search?q=SFTP | 13:55 |
Joerg-Neo900 | I guess nobody nowadays thinks "simple file transfer" when SFTP | 13:57 |
Joerg-Neo900 | though indeed SSH FTP aka SFTP is simpler than classical FTP | 13:59 |
Joerg-Neo900 | see "FTP passive mode" and "NAT" | 14:01 |
Joerg-Neo900 | >>Simple File Transfer Protocol (the first protocol abbreviated SFTP), as defined by RFC 913, was proposed as an (unsecured) file transfer protocol with a level of complexity intermediate between TFTP and FTP. It was never widely accepted on the Internet, and is now assigned Historic status by the IETF. << (wikipedia) I don't know what you meant by "Secure File Transfer Protocol", assuming you refer to "Simple" instead "Secure" | 14:10 |
Joerg-Neo900 | there's FTPS which is differnet to SFTP | 14:10 |
brolin_empey | Joerg-Neo900: I thought that SFTP = Secure File Transfer Protocol is File Transfer Protocol using SSL/TLS. I do not remember the details because I have not studied this stuff for years. | 21:10 |
enyc | brolin_empey: Sftp is more like sort-of-ftp over ** SSH ** | 22:17 |
Joerg-Neo900 | my workstation is pretty much messed up completely, after system upgrade :-/ this will take quite a while to fix | 22:27 |
Joerg-Neo900 | particularly KDE is fubar now | 22:27 |
houkime | Joerg, what is the reason behind U1101 exp connecting to a different ground from all other ground pins of this component? | 22:30 |
Joerg-Neo900 | sorry I'm totally out of business, can't even switch windows ATM | 22:31 |
houkime | it is because there won't be a split in a groundplane to accomodate agnd and we're using star instead? | 22:31 |
houkime | ok | 22:31 |
Joerg-Neo900 | yes, sounds like a reasonable explanation as far as I can follow | 22:33 |
Joerg-Neo900 | we have some chips with both AGND and normal GND | 22:33 |
Joerg-Neo900 | however pad should connect to one of them | 22:33 |
Joerg-Neo900 | there shouldn't be a component that has all GND pins on one GND and only thermal pad on a different GND | 22:34 |
Joerg-Neo900 | the data sheet needs to advice which GND to connect exp to | 22:35 |
Joerg-Neo900 | or leave it completely unconnected | 22:35 |
enyc | 'AGND = audio ground? | 22:35 |
Joerg-Neo900 | yes | 22:35 |
houkime | I will also try out Arch with KDE once they figure out Wayland. Should be quite resource saving since xorgless (ancient clunky monster xorg). | 22:35 |
houkime | datasheet says to connect it to the same gnd as other pins - agnd | 22:36 |
houkime | Just thought you invented some optimisation or have other reasons to go usual gnd for exp | 22:37 |
Joerg-Neo900 | no, not afaik | 22:38 |
houkime | thing is that you won't be able to do thermal vias if you don't have aunderlying agnd then | 22:38 |
Joerg-Neo900 | what is this chip? | 22:39 |
houkime | headphone ampli | 22:39 |
Joerg-Neo900 | hmmm | 22:39 |
houkime | my thought for audio was to have a whole region for agnd on the gndplane | 22:40 |
Joerg-Neo900 | doesn't it have both AGND and digital/common GND? ut has I2C, no? | 22:40 |
houkime | and concentrate stuff together | 22:40 |
houkime | it has i2c | 22:41 |
houkime | however recommended layout in datasheet uses only one gnd | 22:42 |
houkime | which given this is an ampli should be agnd | 22:42 |
Joerg-Neo900 | we use a different layout if we have a I2C GND on this chip | 22:44 |
Joerg-Neo900 | sory this makes no sense. This KDE is total shit and I can't do anything to really help right now. I need to fix my workstation so I can work again (also for PIA) | 22:45 |
houkime | ok | 22:45 |
Joerg-Neo900 | I hope this won'T take the anticipated 2 weeks | 22:46 |
Joerg-Neo900 | but as it looks right now, it might | 22:46 |
houkime | btw what os you are trying out? | 22:46 |
Joerg-Neo900 | I just upgraded | 22:46 |
Joerg-Neo900 | which included KDE4 -> KDE5 | 22:47 |
Joerg-Neo900 | which in turn nuked *everything* I got configured on my desktop during almost 20 years | 22:47 |
houkime | my first reaction when shit like that happens - recompile problematic stuff from sources. | 22:48 |
houkime | usually saves the day | 22:48 |
Joerg-Neo900 | this is a config issue, recompiling stuff won't help | 22:49 |
Joerg-Neo900 | also I couldn't even open a terminal right now | 22:49 |
houkime | can you open a file manager? | 22:50 |
houkime | or the terminal is broken itself? | 22:52 |
Joerg-Neo900 | the desktop is broken | 22:52 |
Joerg-Neo900 | I can't even reach the menu bar of my IRC client | 22:53 |
houkime | on occasions like this (which I had), i have an emergency usb stick with a live medium | 22:53 |
houkime | live medium for arch allows you to chroot into system. | 22:54 |
houkime | probably other also have sth like that | 22:54 |
Joerg-Neo900 | I jave ctrl+alt+F1 | 22:55 |
Joerg-Neo900 | but... what then? | 22:55 |
houkime | last time I did it I cleaned up problematic stuff from shell. You can purge your config files and reinstall kde probably | 22:58 |
houkime | so that you can have a default kde again. | 22:59 |
houkime | it is also possible that kde has a special CLI command to restore defaults. | 23:18 |
Joerg-Neo900 | ok removed the top-of-screen panel and added task manager to bottom panel, now (after session restart) I see window title bars again and also buttons in taskswitcher | 23:28 |
Joerg-Neo900 | what the hell??? is this new systemd "session" concept that every app loses connection to internet when you switch to a new X11 session? | 23:54 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!