- Talk - lists.gtalug.org

warning: Mint website served malware-infected .iso files (and more)
by D. Hugh Redelmeier 22 Feb '16

22 Feb '16

<http://arstechnica.com/security/2016/02/linux-mint-hit-by-malware-infection…>

1 0

VPN Recommendations?
by phiscock＠ee.ryerson.ca 21 Feb '16

21 Feb '16

I've been using Hola to create a VPN, and then a friend pointed out this: http://lifehacker.com/hola-better-internet-sells-your-bandwidth-turning-its… so maybe Hola isn't such a good idea. Any recommendations from this group? Maybe OpenVPN? Thanks - Peter -- Peter Hiscocks Syscomp Electronic Design Limited, Toronto http://www.syscompdesign.com USB Oscilloscope and Waveform Generator 647-839-0325

6 5

Getting debian "dwww" to work on Ubuntu Studio
by sciguy 21 Feb '16

21 Feb '16

I have Ubuntu Studio on which Debian "dwww" is installed. I needed to fix some directories by adding symbolic links to get everything to work. But for now, if I click on a command to see its manpage or documentation, I am asked to download the gzipped file. It is not uncompressing and converting to html. I imagine it should do something if it is appending ?type=man to all of the links. But I don't see a script to run the CGI query. There are none in the dwww directory, nor under dwww/cgi-bin (to non-Debian users, that's http://hostname/dwww) There was never a cgi-bin directory at any rate. I actually had to create one so the links to the manpages wouldn't break, but there are no scripts in there unless I wrote it, and I didn't write any. What is this script supposed to be called? There are no clues in the HTML. Can I download it from somewhere? pkingman

2 3

Fedora Partitioning
by Howard Gibson 21 Feb '16

21 Feb '16

Updating my desktop to Fedora_23 continues to be a challenge. I figured out how to connect to the network. Now, it insists on a /boot partition separate from /home. This appears to be a new feature. I am trying to upgrade, rather than re-install everything. I don't recall how I managed to do this, but my root partition is /dev/sda1. My other partitions are contained in the extended partition /dev/sda2. Does anybody know how I can use the Fedora installer to split /dev/sda1 into two partitions /dev/sda1 and /dev/sda6?. I tried deleting /, and creating the two new partitions, and it did not work. Alternately, is there a way to use my root partition for booting? I have looked at my partition table using fdisk. It looks like I can delete /dev/sda1 and create the two new partitions sda1 and sda6. Definitely, this destroys my current setup, and my new install had damn well better work. Partitions sda1 and sda6 will be next to each other, followed by sda2. Has anybody done this safely? I have a Ubuntu DVD here. When I "Try Ubuntu", I was able to make it claim that my network was connected, but I was unable to ping the machine, or connect the browser to http://www.google.com. Is this how Ubuntu behaves in demo mode? The Ubuntu installer seems to over-write boot. If I play with it, I am forced to re-install something. Fedora_20 was a dead cinch to install. How did everything get so complicated? -- Howard Gibson hgibson(a)eol.ca howard.gibson(a)teledyneoptech.com jhowardgibson(a)gmail.com http://home.eol.ca/~hgibson

8 12

Ubuntu Studio: Sound not working in all applications
by Paul King 20 Feb '16

20 Feb '16

I have what I must describe as a strange sound problem under Linux Ubuntu Studio 14.x. The operating system sound is dead, so is sound which ought to come out of media players like VLC. Sound also fails to work in the browser. BUT, it DOES work perfectly under Audacity. I have tried to change the system settings to the same settings as Audacity, but I haven't been successful. THere was touted to be a window called "Sound Preferences", but when I clicked on the speaker icon to select "sound preferences" from the dropdown, the window that came up was "System settings", which only had icons for the printer, desktop and one other thing that had nothing to do with sound that I can't recall. Any ideas?

3 5

(Fwd) Re: Ubuntu Studio: Sound not working in all applications
by Paul King 20 Feb '16

20 Feb '16

Some other oddments of the sound on my system: The Ubuntu online docs suggested I run aplay /usr/share/sounds/alsa/Front_Center.wav as a "fail-safe" audio file that is touted to work in all configs. It worked when: a) I was logged on as root on a console (ie, one of the ALT+# screens); b) when I logged onto a console with my joeuser account (as myself) and ran the command with sudo. It did not work when logged in as myself, as myself on X-windows, or sudoed in X-Windows under my account, nor did it work if I logged on to X-windows as root. In summary, logging in as root in a TTY has the best sound right now. On 20 Feb 2016 at 8:30, Paul King wrote: No need to apologize. If it is the PCM channel, then I don't know how to access its information to know if it is muted or not. I noticed that alsa was installed but not running (I did a ps | grep as root). Pulseaudio was actually running. I didn't know it was a wrapper for Alsa. It appears to be standalone going by the docs (I don't see alsa or OSS listed as a pre-requisite or a system requirement). Paul On 20 Feb 2016 at 5:43, Russell Reiter wrote: Sorry to top post. I meant to say PCM channel. Still haven't had morning coffee. > Are you using Alsa, OSS or the Pulseaudio wrapper. I've seen this problem where the Alsa mixer mutes the dsp channel on reboot. > If you are using Alsa you can try using the alsamixer to unmute the channel and alsactl store to make the settings persistent. > > Hope this helps. > Russell > > Sent from mobile. > > On Feb 19, 2016 9:17 PM, "Paul King" <sciguy(a)vex.net> wrote: > > > > I have what I must describe as a strange sound problem under Linux Ubuntu > > Studio 14.x. The operating system sound is dead, so is sound which ought to > > come out of media players like VLC. Sound also fails to work in the browser. > > > > BUT, it DOES work perfectly under Audacity. I have tried to change the system > > settings to the same settings as Audacity, but I haven't been successful. > > > > THere was touted to be a window called "Sound Preferences", but when I clicked > > on the speaker icon to select "sound preferences" from the dropdown, the window > > that came up was "System settings", which only had icons for the printer, > > desktop and one other thing that had nothing to do with sound that I can't > > recall. > > > > Any ideas? > > > > > > --- > > Talk Mailing List > > talk(a)gtalug.org > > https://gtalug.org/mailman/listinfo/talk --Message-Boundary-8768-- --- Talk Mailing List talk(a)gtalug.org https://gtalug.org/mailman/listinfo/talk ------- End of forwarded message -------

2 2

OpenWrt vs TP-Link Archer C7 v2
by D. Hugh Redelmeier 19 Feb '16

19 Feb '16

For a while it has looked as if the C7 v2 was a very good choice if one wanted to run open firmware. In particular, it uses an Atheros radio that has open drivers. Based on my criteria, OpenWrt is the firmware to run (or something based on it). DD-WRT and others have problems that make them not open by my standards. I haven't actually run OpenWrt on a C7. But I learned a few things last night that dismayed me. You can find these in "Note:" entries on the wiki page but they don't stick out. <https://wiki.openwrt.org/toh/tp-link/archer-c5-c7-wdr7500> 0) It is "OpenWrt", not "OpenWRT". 1) Recent stock firmware from TP-Link locks out flashing third-party firmware. <http://ml.ninux.org/pipermail/battlemesh/2016-February/004379.html> If you have a C7 with older stock firmware, don't upgrade it to the current stock firmware if you ever hope to use OpenWrt. There are apparently work-arounds but they seem a bit intricate. 2) The C7 (and a number of other routers) have a hardware fast-path to do NAT. This hardware is undocumented and hacky so OpenWrt will never use it. Without using it it is impossible to get gigabit wire-speed NATting. But the stock firmware does use it. <https://dev.openwrt.org/ticket/11779> 3) For mysterious reasons OpenWrt is significantly less efficient handling 5GHz 802.11ac. You won't notice this unless you are using a 3-antenna client (or, I speculate, multiple 2-antenna clients) <https://forum.openwrt.org/viewtopic.php?id=53703> This thread is pretty frustrating because the first message very carefully posts observations and yet most of the following 168 messages ask questions already answered or veer off-topic. There appears to be no resolution. All this reinforces my decision to build gateways out of small PCs rather than consumer routers. I do use an off-the-shelf wireless router as an access point.

3 2

A few notes on SystemD
by Christopher Browne 18 Feb '16

18 Feb '16

I had prepped a few notes at the last meeting with a view to saying a wee bit about SystemD; apparently my name never got picked by the 1D20. I have been collecting notes for a couple of months, particularly with a view to the "Stupid SystemD tricks" part. There's a lot there; perhaps this "memory dump" will help others recognize things too. The other pointed interesting bit is in recognizing the differences between "political parties" on the merits/demerits. There seem to be sizable sets of people that have stopped thinking/listening, which is pretty unfortunate, and in sad keeping with shapes of political movements elsewhere. * SystemD debates [[http://uselessd.darknedgy.net/ProSystemdAntiSystemd/][Why Pro SystemD and Anti SystemD people cannot get along]] - It's actually mostly politics, just not of one of the parties that they recognize - Proponents tend to have afiliation with "modern desktop" - Want more interoperability - Sure, somewhat more "Windows like" - Seek reducing interface complexity but not implementation complexity - Computers as appliances rather than tools - Detractors often come from niche distributions - Less interested in desktop advances - Care about malleability more than user friendliness - Computers as tools - The fight is more about desktop vs minimalism - A moderate annoyance: systemd includes *journald*, which does logging - Why not use *syslog*??? - Because you /cannot/ use *syslog* to log things until *syslog* is running - And *syslog* is not running until a whole bunch of /other/ services get started, by *systemd* - Ergo, *systemd* needs a logging system /that is not syslog/ - It may be desirable to /forward/ responsibility for logging to *syslog*, /once it is running/, and *systemd* supports that * SystemD concepts :systemd: ** Units - objects that systemd can manage - standardized representation of system resources - like services, jobs in init systems - can use units to abstract services, network resources, filesystem mounts, resource pools - Various activation methods - socket based :: start unit upon accessing a socket, like xinetd - bus based :: start unit when DBus request is submitted - path based :: start unit when inotify indicates a path is available - device based :: start unit when hardware is available based on udev events - With dependency mapping/ordering - Various types - ~.service~ :: indicates how to manage a service/application, including - how to start/stop the service - when service should be automatically started - dependency and ordering information for related software - ~.socket~ :: indicates network/IPC socket or FIFO that is to be used for socket-based activation - points to ~.service~ file - ~.device~ :: indicates a device needs systemd management - often needed for ordering, mounting, accessing the device - ~.mount~ :: defines a mountpoint to be managed by systemd - named after mount path with slashes transformed to dashes - ~/etc/fstab~ entries automatically get such units (how???) - ~.automount~ :: indicates mount points to be automatically mounted - refers to a ~.mount~ file - ~.swap~ :: indicates swap space - ~.target~ :: target unit provides synchronization points for other units when changing state - seems to be a way of indicating dependencies a bit abstractly - ~.path~ :: indicates cases where, when a path reaches desired state, the service will be started - uses inotify to watch for changes - e.g. - do not start up /postgresql-database/ until the filesystem with data has been mounted - ~.timer~ :: indicates a timer for systemd to manage indicating when the service unit will be started - can be used to do things like cron jobs - ~.snapshot~ :: - ~.slice~ :: associates with Linux Control Group nodes to restrict access to resources to processes in the slice - so, security-ish??? - samples on Debian say NOTHING about this, so perhaps they're no-ops? - ~.scope~ :: help (how?) to manage system processes created externally (from systemd?) - Default unit files in ~/lib/systemd/system~ - Customize into ~/etc/systemd/system~ *** Directives - unit section :: defines metadata - Description :: what is this? - Documentation :: reference - Requires :: units required before this one (failure to have them indicate this unit fails) - Wants :: units wanted (less strict) - BindsTo :: this unit should terminate when another one terminates - Before :: units specified must not start until after the present one is started, but this is not indicating dependency - After :: this unit must not start until the specified units are started - Conflicts :: mutual exclusions of units - Condition :: things to test prior to starting the unit - failure leads to graceful skipping of the unit - PathExists - Capability - PathIsReadWrite - DirectoryNotEmpty - FileIsExecutible - KernelCommandLine - NeedsUpdate - PathIsDirectory - PathIsMountPoint - PathIsSymbolicLink - Virtualization - Assert :: failure of conditions lead to reporting failure of the unit - Various other sections specialized to various sorts of units - Transaction manager - Jobs - Job queueing - Tasks - What is journald? ** Translating former understandings to SystemD - Configuration that you mess with tends to be in ~/etc/systemd/system~ - Finding all services #+BEGIN_EXAMPLE # systemctl list-units #+END_EXAMPLE - This lists loaded units, and does so if you omit ~list-units~ - ~systemctl list-units --all~ :: list non-loaded units - ~systemctl list-unit-files~ :: list unit files - ~systemctl list-dependencies~ :: list the hierarchy of dependencies - and other things can be listed - The common start/stop/restart targets work - ~systemctl start boa~ - ~systemctl stop boa~ - ~systemctl reload boa~ - ~systemctl force-reload boa~ - More operations that should be obvious-ish - ~systemctl cat boa~ :: list the unit files - ~systemctl disable boa~ :: disable boa - ~systemctl reenable boa~ :: reenable boa - ~systemctl enable boa~ :: enable boa - ~systemctl edit boa~ :: edit boa units (copying to ~/etc/systemd/system~ if needed) - ~systemctl show boa~ :: show environment values and such * SystemD Bibliography :systemd: - [[https://n0where.net/understanding-systemd/][Understanding SystemD]] * Stupid SystemD Tricks ** Emacs as a service - Set up a unit file #+BEGIN_EXAMPLE [Unit] Description=Emacs: the extensible, self-documenting text editor [Service] Type=forking ExecStart=/usr/bin/emacs --daemon ExecStop=/usr/bin/emacsclient --eval "(kill-emacs)" Environment=SSH_AUTH_SOCK=%t/keyring/ssh Restart=always [Install] WantedBy=default.target #+END_EXAMPLE ** Use SystemD rather than crontab? It seems as though the job information needs to be integrated into the "central" systemD configuration, so this is more or less a contraindicated thing to do. There are examples in documentation of running system cleanup tasks as SystemD-controlled jobs, so that is fairly reasonable to do. But I'd kind of like it if I could use SystemD to do things like... - starting up my favorite file downloader daemon - start up user space daemons running /at user level/ - run user-oriented scheduled tasks And this seems totally unnatural to do via SystemD. -- When confronted by a difficult problem, solve it by reducing it to the question, "How would the Lone Ranger handle this?"

1 0

A few notes on SystemD
by Christopher Browne 18 Feb '16

18 Feb '16

I had prepped a few notes at the last meeting with a view to saying a wee bit about SystemD; apparently my name never got picked by the 1D20. I have been collecting notes for a couple of months, particularly with a view to the "Stupid SystemD tricks" part. There's a lot there; perhaps this "memory dump" will help others recognize things too. The other pointed interesting bit is in recognizing the differences between "political parties" on the merits/demerits. There seem to be sizable sets of people that have stopped thinking/listening, which is pretty unfortunate, and in sad keeping with shapes of political movements elsewhere. * SystemD debates [[http://uselessd.darknedgy.net/ProSystemdAntiSystemd/][Why Pro SystemD and Anti SystemD people cannot get along]] - It's actually mostly politics, just not of one of the parties that they recognize - Proponents tend to have afiliation with "modern desktop" - Want more interoperability - Sure, somewhat more "Windows like" - Seek reducing interface complexity but not implementation complexity - Computers as appliances rather than tools - Detractors often come from niche distributions - Less interested in desktop advances - Care about malleability more than user friendliness - Computers as tools - The fight is more about desktop vs minimalism - A moderate annoyance: systemd includes *journald*, which does logging - Why not use *syslog*??? - Because you /cannot/ use *syslog* to log things until *syslog* is running - And *syslog* is not running until a whole bunch of /other/ services get started, by *systemd* - Ergo, *systemd* needs a logging system /that is not syslog/ - It may be desirable to /forward/ responsibility for logging to *syslog*, /once it is running/, and *systemd* supports that * SystemD concepts :systemd: ** Units - objects that systemd can manage - standardized representation of system resources - like services, jobs in init systems - can use units to abstract services, network resources, filesystem mounts, resource pools - Various activation methods - socket based :: start unit upon accessing a socket, like xinetd - bus based :: start unit when DBus request is submitted - path based :: start unit when inotify indicates a path is available - device based :: start unit when hardware is available based on udev events - With dependency mapping/ordering - Various types - ~.service~ :: indicates how to manage a service/application, including - how to start/stop the service - when service should be automatically started - dependency and ordering information for related software - ~.socket~ :: indicates network/IPC socket or FIFO that is to be used for socket-based activation - points to ~.service~ file - ~.device~ :: indicates a device needs systemd management - often needed for ordering, mounting, accessing the device - ~.mount~ :: defines a mountpoint to be managed by systemd - named after mount path with slashes transformed to dashes - ~/etc/fstab~ entries automatically get such units (how???) - ~.automount~ :: indicates mount points to be automatically mounted - refers to a ~.mount~ file - ~.swap~ :: indicates swap space - ~.target~ :: target unit provides synchronization points for other units when changing state - seems to be a way of indicating dependencies a bit abstractly - ~.path~ :: indicates cases where, when a path reaches desired state, the service will be started - uses inotify to watch for changes - e.g. - do not start up /postgresql-database/ until the filesystem with data has been mounted - ~.timer~ :: indicates a timer for systemd to manage indicating when the service unit will be started - can be used to do things like cron jobs - ~.snapshot~ :: - ~.slice~ :: associates with Linux Control Group nodes to restrict access to resources to processes in the slice - so, security-ish??? - samples on Debian say NOTHING about this, so perhaps they're no-ops? - ~.scope~ :: help (how?) to manage system processes created externally (from systemd?) - Default unit files in ~/lib/systemd/system~ - Customize into ~/etc/systemd/system~ *** Directives - unit section :: defines metadata - Description :: what is this? - Documentation :: reference - Requires :: units required before this one (failure to have them indicate this unit fails) - Wants :: units wanted (less strict) - BindsTo :: this unit should terminate when another one terminates - Before :: units specified must not start until after the present one is started, but this is not indicating dependency - After :: this unit must not start until the specified units are started - Conflicts :: mutual exclusions of units - Condition :: things to test prior to starting the unit - failure leads to graceful skipping of the unit - PathExists - Capability - PathIsReadWrite - DirectoryNotEmpty - FileIsExecutible - KernelCommandLine - NeedsUpdate - PathIsDirectory - PathIsMountPoint - PathIsSymbolicLink - Virtualization - Assert :: failure of conditions lead to reporting failure of the unit - Various other sections specialized to various sorts of units - Transaction manager - Jobs - Job queueing - Tasks - What is journald? ** Translating former understandings to SystemD - Configuration that you mess with tends to be in ~/etc/systemd/system~ - Finding all services #+BEGIN_EXAMPLE # systemctl list-units #+END_EXAMPLE - This lists loaded units, and does so if you omit ~list-units~ - ~systemctl list-units --all~ :: list non-loaded units - ~systemctl list-unit-files~ :: list unit files - ~systemctl list-dependencies~ :: list the hierarchy of dependencies - and other things can be listed - The common start/stop/restart targets work - ~systemctl start boa~ - ~systemctl stop boa~ - ~systemctl reload boa~ - ~systemctl force-reload boa~ - More operations that should be obvious-ish - ~systemctl cat boa~ :: list the unit files - ~systemctl disable boa~ :: disable boa - ~systemctl reenable boa~ :: reenable boa - ~systemctl enable boa~ :: enable boa - ~systemctl edit boa~ :: edit boa units (copying to ~/etc/systemd/system~ if needed) - ~systemctl show boa~ :: show environment values and such * SystemD Bibliography :systemd: - [[https://n0where.net/understanding-systemd/][Understanding SystemD]] * Stupid SystemD Tricks ** Emacs as a service - Set up a unit file #+BEGIN_EXAMPLE [Unit] Description=Emacs: the extensible, self-documenting text editor [Service] Type=forking ExecStart=/usr/bin/emacs --daemon ExecStop=/usr/bin/emacsclient --eval "(kill-emacs)" Environment=SSH_AUTH_SOCK=%t/keyring/ssh Restart=always [Install] WantedBy=default.target #+END_EXAMPLE ** Use SystemD rather than crontab? It seems as though the job information needs to be integrated into the "central" systemD configuration, so this is more or less a contraindicated thing to do. There are examples in documentation of running system cleanup tasks as SystemD-controlled jobs, so that is fairly reasonable to do. But I'd kind of like it if I could use SystemD to do things like... - starting up my favorite file downloader daemon - start up user space daemons running /at user level/ - run user-oriented scheduled tasks And this seems totally unnatural to do via SystemD. -- When confronted by a difficult problem, solve it by reducing it to the question, "How would the Lone Ranger handle this?"

1 0

Windows support
by Alex Volkov 18 Feb '16

18 Feb '16

Hello everyone, Do you know any students/hobbyists doing desktop support and/or making house calls as a side business. I know a few people who need help, but I just don't have time. If anyone could give me referral that would be awesome. This is all for Windows, unfortunately. Thanks, Alex.

1 0