I'm getting tired of booting into Windows for work. I figured out how to
connect to the VPN from Debian, but it would be very helpful to RDP into
the workstation in my office.
I know the URL for my workstation, the domain, the username, and the
password, but I'm failing to get it to work. What should I try?
Remmina says "Connecting to <server>..." for a minute, then fails with
"Connection to RDP server <server> failed."
--
Rich
I am trying for figure out what, if anything, of FEDORA RED HAT LINUX is
still available. I have downloaded a DVD that I plan to install on my DELL
XPS desktop PC running WINDOWS 10. Will it find for me my old LINUX
atmosphere?
Ken Jones
Hey Gang,
I hope everybody is staying safe and healthy. While Linux doesn't need
virus protection, we do. Wash your hands you filthy animals.
As the subject reads, we're going to be doing the WLUG meeting online.
I've been active in the wlug-ma irc channel as have others.
What do people think about Jitsi for doing a video meetup?
Refreshments will not be provided and we won't be going out for dinner!!
Stay home, stay safe and I hope we'll all get to see each other soon.
Later,
Tim.
--
I am leery of the allegiances of any politician who refers to their
constituents as "consumers".
Hey everyone,
Apparently Lenovo is planning on shipping Fedora on their Thinkpad lines,
and will use only packages from the official repos instead of custom
packages.
I think this is great news as somebody who shopped for Thinkpads before and
had to contact support about refunding a Windows license (turns out that
wasn't possible at the time). Having a distro pre-installed should mean
improved hardware compatibility, and maybe even be able contact support for
Linux-specific issues.
More info here:
https://fedoramagazine.org/coming-soon-fedora-on-lenovo-laptops/
-Josh
What is the best way to provide proof to an audit person who needs to know
all the root/sudo users for a RHEL 6 server?
(I am new at this company, and don't have access to all their resources)
We can provide the /etc/passwd & /etc/sudoers file (the auditor may
not know how to read these files)
We also have the RedHat Identity Management running here, but I am not
familiar with this tool.
Any suggestions would be appreciated.
Thanks!
John Malloy
jomalloy(a)gmail.com
Hey Everybody,
I just wanted to give a shout out to everybody who showed up to the virtual
meeting last night. It was cool to see Maddog show up, I'm glad he's
staying safe and healthy.
Yeah, there were a couple of audio/video hiccups, but I thought overall it
went great.
I shared my screen a couple of times and that worked just fine as well.
One cool thing that was brought up doing the meeting and I thought was
worth talking about is "vscodium" which is a 100% open source recompile of
the visual studio code editor. The big difference is that the vscode as
shipped from microsoft contains telemetry tracking data that gets sent back
to the mothership... https://vscodium.com/ solves that problem.
We obviously jibber jabbed about COVID19 and folding@home and Logan showed
off the facemasks he's been printing as well as the antennae he's building
to contact a long lost satellite in geostationary orbit.
While it wasn't the same as a physical meeting, when we do manage to get
ourselves all back in the same room, I think it's something we'll
definitely incorporate into the physical meetings.
Stay safe, stay healthy and wash your hands!
We'll see what May brings us and decide from there...
Tim.
WLUG President
--
I am leery of the allegiances of any politician who refers to their
constituents as "consumers".
Guys,
I'm starting to work on deplying ansible at $WORK to start managing a
bunch of existing servers. The goal is to A) get them consistent, B)
learn ansible, and C) automate deployments so if I get hit by a bus,
they can have a hope of keeping things going.
So my first thoughts are about organization. Ansible is a
file/directory heavy setup. And I understand how a task has one or
more roles. And then a playbook can have one or more tasks. But it's
how to manage the overall site or bundles of playbooks that I want to
understand.
I've looked at:
https://docs.ansible.com/ansible/latest/user_guide/playbooks_best_practices…
and I think I can deal with the first layout suggestion, but I'd
porbably put playbooks into a playbooks/ directory. But... how to
keep them organized as my collection grows.
Do I want a new directory structure for each group of playbooks? For
example I want to do:
- add ssh-keys for logins
- make sure right repo(s) are configured
- ntp client config
- postfix config
- NIS config
- fstab config
- nsswitch.conf config
So ideally all of the above would be a playbook each, since for
example ntp config, would/could include:
- install ntp
- install default client config
- restart ntpd once configured
- etc...
Where it all comes down to is keeping all this organized nicely,
especially as it grows ever more complicated. All the silly examples
of setting up a LAMP stack completely gloss over the actual pushing of
content, which is really what we want to do.
So, thoughts? Real life experience? Suggestions for good training
classes? Unfortunately it would have to be online now, not my
preferred in-person training....
John
Hey Gang,
We've got a virtual meeting today!
We're all going to meet on Jitsi! Here's the location:
https://meet.jit.si/WlugMA
The big blue button stuff looks really awesome, but I haven't had a chance
to dig into it, however for presenting it looks pretty awesome.
I hope everybody is staying sane and staying safe.
Later,
Tim Keller
WLUG President
--
I am leery of the allegiances of any politician who refers to their
constituents as "consumers".
