tag:blogger.com,1999:blog-628893440875228142024-03-14T07:00:14.611-07:00Esparciendo Conocimiento AcumuladoLas entradas en este blog están basadas en mis experiencias personales, por lo cual pueden contener errores y en algunos casos, seguramente hay maneras más simples de realizar los procesos.FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.comBlogger60125tag:blogger.com,1999:blog-62889344087522814.post-27443651099749314272023-09-09T17:54:00.001-07:002023-09-09T17:54:58.217-07:00Check Open Files By Process Name<p>I was tasked with finding how many files were open for a specific process name. The process name had many process IDs (PIDs) running, which could be listed using the following command:</p><p><span> </span>ps -eaf | grep -i<ProcessName></p><p>The PIDs were listed in the second column, which the required the addition of one more command:</p><p><span> </span>ps -eaf | grep -i $CheckProcessName | awk -F ' ' '{print $2}'</p><p>The output was a list of PIDs, in one column, and the amount of open files could be checked for each of them, by running the following command for the PIDs:</p><p><span> </span>lsof -p <PID1>,<PID2>,<PID3>,...,<PIDn> | wc -l<br /></p><p>This was cumbersome for processes that have multiple PIDs, thus adding one extra command to list all PIDs in one line:<br /></p><p><span> </span>ps -eaf | grep -i $CheckProcessName | awk -F ' ' '{print $2}' | tr '\n' ,</p><p> I decided to combine it all together and came up with this one-liner:</p><p><span> </span>lsof -p $(ps -eaf | grep -i <ProcessName> | awk -F ' ' '{print $2}' | tr '\n' ,) | wc -l</p><p>Last, but not least, I created a shell script that could be used to check on any process:</p><p><span> </span>#!/bin/bash<br /><span> </span>read -p "Enter process name: " CheckProcessName<br /><span> </span>lsof -p $(ps -eaf | grep -i $CheckProcessName | awk -F ' ' '{print $2}' | tr '\n' ,) | wc -l</p><p>Feel free to comment if you have a suggestion to make it simpler</p><p>Regards,</p><p>F. Bobbio C.<br /></p>FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.com0tag:blogger.com,1999:blog-62889344087522814.post-69409484139761798232022-10-31T17:04:00.001-07:002022-10-31T17:06:00.348-07:00Dynect Zones + Record_Id Export<p> I was tasked with exporting all records from Dynect to import into another portal. There was some information here: https://support.globaldots.com/hc/en-us/articles/115004002829-Dyn-How-to-get-all-records-from-a-zone-through-the-API which requires the creation of a file in json format with these parameters { "customer_name" : "ACME" , "user_name" : "user", "password" : "secretpassword" }</p><p></p><p>This would allow me to export only partial information and I needed to export over 750 zones, with over 100 records per zone in some cases. I created the following script, which exports each domain in the zones into its own json file<br /></p><p></p><p># Based on https://help.dyn.com/rest-resources/<br />#!/bin/bash<br />Token=$(curl -sX POST -d @Credentials.txt -H "Content-Type: application/json" https://api.dynect.net/REST/Session/ | awk -F '"' '{print $10}')<br />curl -sX GET -H "Content-Type: application/json" -H "Auth-Token: $Token" https://api.dynect.net/REST/Zone/ >> Zones.json<br />cat Zones.json | awk -F ']' '{print $1}' | awk -F '[' '{print $2}' > Zones.json.1<br />sed -i -e 's|/||g' -i -e 's|RESTZone||g' -i -e 's|,||g' -i -e 's|"||g' Zones.json.1<br />rm Zones.json && mv Zones.json.1 Zones.json<br />AllZones=$(cat Zones.json)<br />for val in ${AllZones[@]};do<br /> curl -sX GET -H "Content-Type: application/json" -H "Auth-Token: $Token" https://api.dynect.net/REST/AllRecord/$val/ >> $val.json<br /> echo -e Exporting data for zone $val<br /> cat $val.json | awk -F ']' '{print $1}' | awk -F '[' '{print $2}' > $val.json.1<br /> sed -i -e 's|,||g' -i -e 's|"||g' $val.json.1<br /> rm $val.json && mv $val.json.1 $val.json<br />done<br />for i in $(cat Zones.json);do<br /> EachZone=$(cat $i.json)<br /> for val in ${EachZone[@]};do<br /> EachZoneName=$(echo $val | awk -F '/' '{print $4}')<br /> ZoneNameAttribute=$(echo $val | awk -F '/' '{print $3}')<br /> curl -sX GET -H "Content-Type: application/json" -H "Auth-Token: $Token" https://api.dynect.net$val/ >> $EachZoneName-Detailed.json && echo >> $EachZoneName-Detailed.json && echo >> $EachZoneName-Detailed.json<br /> echo -e Exporting detailed data for $ZoneNameAttribute in zone $EachZoneName<br /> cat $i-Detailed.json | awk -F 'zone": ' '{print $2}' | awk -F ', "record_id":' '{print $1}' >> $i-Detailed-Cleaned.json<br /> sed -i -e 's|,|\n|g' -i -e 's|"||g' $i-Detailed-Cleaned.json<br /> done<br />done<br />#rm *-Detailed.json</p><p>Regards,</p><p>F. Bobbio C. </p><p></p>FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.com0tag:blogger.com,1999:blog-62889344087522814.post-75231127560395739602022-08-28T19:06:00.001-07:002022-08-28T19:19:06.381-07:001Password In Slackware64-current<p>There is currently no SlackBuild for 1password. It can be installed using the rpm file, via the following script: </p><p style="text-align: left;">#!/bin/bash<br />rm 1password-latest.rpm 1password-latest.txz<br />wget https://downloads.1password.com/linux/rpm/beta/x86_64/1password-latest.rpm<br />sudo rpm2txz 1password-latest.rpm<br />sudo killall 1password<br />sudo removepkg 1password-latest<br />sudo installpkg 1password-latest.txz<br />sudo cp custom_allowed_browsers /opt/1Password/resources/</p><p>Copy custom_allowed_browsers from /opt/1Password/resources/ and modify it by adding a line with the default browser in use, such as firefox<br /></p><p></p><p>Regards,<br /><br />F. Bobbio C. <br /></p>FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.com0tag:blogger.com,1999:blog-62889344087522814.post-42389561497861305722021-04-05T19:09:00.001-07:002022-08-28T19:19:39.020-07:00Slackware64-current Query Installed Packages Versions<p>Update 08-28-2022: I added more packages to be queried. The script is now hosted in <a href="https://gitlab.com/FBobbioC/scripting/-/blob/main/Releases.sh" target="_blank">GitLab</a> and has one extra line comparing the versions of the packages.</p><p>Original:<br /></p><p>I needed a script to check on the current versions of specific packages, as well as the latest versions from the vendors or manufacturer websites. I used the github and gitlab repositories for the packages, along with awk to query the versions and tr to remove the v in front of the version numbers. I even added a line for Microsoft Teams.</p><p><span style="color: red;"><b>First attempt</b>:</span> <br /></p><p>#!/usr/bin/bash<br />echo DKMS && echo Current: && ls /var/log/packages | grep dkms | awk -F "-" '{print $2}' && echo Latest: && git ls-remote --tags --refs --sort="version:refname" git://github.com/dell/dkms | awk -F/ 'END{print$NF}' | tr -d \v<br />echo<br />echo EVDI: && echo Current: && ls /var/log/packages | grep evdi-1 | awk -F "-" '{print $2}' && echo Latest: && git ls-remote --tags --refs --sort="version:refname" git://github.com/DisplayLink/evdi | awk -F/ 'END{print$NF}' | tr -d \v<br />echo<br />echo FreeRDP && echo Current: && xfreerdp /version | awk '{print $5}' && echo "Latest:" && git ls-remote --tags --refs --sort="version:refname" git://github.com/FreeRDP/FreeRDP | awk -F/ 'END{print$NF}' | tr -d \v<br />echo<br />echo NVIDIA: && echo Current: && grep "X Driver" /var/log/Xorg.0.log | awk '{print $8}' && echo Latest: && git ls-remote --tags --refs --sort="version:refname" git://github.com/NVIDIA/nvidia-xconfig | awk -F/ 'END{print$NF}' | tr -d \v<br />echo<br />echo Remmina: && echo Current: && ls /var/log/packages | grep Remmina | awk -F "-" '{print $2}' | tr -d \v && echo Latest: && git ls-remote --tags --refs --sort="version:refname" https://gitlab.com/Remmina/Remmina.git | awk -F/ 'END{print$NF}' | tr -d \v<br />echo<br />echo Teams: && echo Current: && ls /var/log/packages | grep teams-insiders | awk -F "-" '{print $3}' | tr -d \v && echo Latest: && curl -s https://packages.microsoft.com/repos/ms-teams/pool/main/t/teams-insiders/ | awk -F "teams" 'NF > 1 {print $NF}' | tail -1 | awk -F "_" '{print $2}' </p><p><span style="color: red;"><b>Second attempt</b>:</span></p><p>#!/usr/bin/bash<br />CurrentDKMS=$(ls /var/log/packages | grep dkms | awk -F "-" '{print $2}' 2>&1)<br />LatestDKMS=$(git ls-remote --tags --refs --sort="version:refname" git://github.com/dell/dkms | awk -F/ 'END{print$NF}' | tr -d \v 2>&1)<br />echo DKMS Current: $CurrentDKMS Latest: $LatestDKMS<br />CurrentEVDI=$(ls /var/log/packages | grep evdi-1 | awk -F "-" '{print $2}' 2>&1)<br />LatestEVDI=$(git ls-remote --tags --refs --sort="version:refname" git://github.com/DisplayLink/evdi | awk -F/ 'END{print$NF}' | tr -d \v 2>&1)<br />echo EVDI Current: $CurrentEVDI Latest: $LatestEVDI<br />CurrentFreeRDP=$(xfreerdp /version | awk '{print $5}' 2>&1)<br />LatestFreeRDP=$(git ls-remote --tags --refs --sort="version:refname" git://github.com/FreeRDP/FreeRDP | awk -F/ 'END{print$NF}' | tr -d \v 2>&1)<br />echo FreeRDP Current: $CurrentFreeRDP Latest: $LatestFreeRDP<br />CurrentNVIDIA=$(grep "X Driver" /var/log/Xorg.0.log | awk '{print $8}' 2>&1)<br />LatestNVIDIA=$(git ls-remote --tags --refs --sort="version:refname" git://github.com/NVIDIA/nvidia-xconfig | awk -F/ 'END{print$NF}' | tr -d \v 2>&1)<br />echo NVIDIA Current: $CurrentNVIDIA Latest: $LatestNVIDIA<br />CurrentRemmina=$(ls /var/log/packages | grep Remmina | awk -F "-" '{print $2}' | tr -d \v 2>&1)<br />LatestRemmina=$(git ls-remote --tags --refs --sort="version:refname" https://gitlab.com/Remmina/Remmina.git | awk -F/ 'END{print$NF}' | tr -d \v 2>&1)<br />echo Remmina Current: $CurrentRemmina Latest: $LatestRemmina<br />CurrentTeams=$(ls /var/log/packages | grep teams-insiders | awk -F "-" '{print $3}' | tr -d \v 2>&1)<br />LatestTeams=$(curl -s https://packages.microsoft.com/repos/ms-teams/pool/main/t/teams-insiders/ | awk -F "_" 'NF >1 {print $2}' | tail -1 2>&1)<br />echo Teams Current: $CurrentTeams Latest: $LatestTeams<br /></p><p>Regards,</p><p>F. Bobbio C. </p>FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.com0tag:blogger.com,1999:blog-62889344087522814.post-42417218537213669492021-02-08T06:00:00.001-08:002021-02-08T06:00:55.488-08:00Slackware64-current In MacBook Pro<p>I am just another regular Slackware user, who likes tinkering around
with machines and installing Slackware64-current on them to check on
their performance and if Slackware64-current can work on them.<br /></p><p>I received a MacBook Pro from one of my customers and wanted to see if I could install Slackware64-current natively on it, since it had an issue that would cost $300 to $500 to fix with the built-in or integrated (soldered to the motherboard) video card, which all laptops have anyway. These are the steps I took and the URLs I gathered in this process.</p><p><span style="color: red;"><u><b>Note</b></u>: Do this at your own risk. I assume no responsibility if something goes wrong. This procedure will format the whole drive and you will lose macOS on it.</span><br /></p><p>01) Download Slackware64-current iso (https://slackware.nl/slackware/slackware64-current-iso/) and create a USB bootable stick with it<br /></p><p>02) Hold "alt" or "option" before pressing the power button on the MacBook Pro. Release it when you see "EFI Boot"</p><p>03) Double click on "EFI Boot" to start the Slackware64-current installation<br /></p><p>04) Use cfdisk or cgdisk to create partitions. The first partition should be a 100M EFI partition. Other partitions can include a swap partition, a root ("/") partition and a home ("/home") partitions or any other partition that you need. The EFI partition is required for this procedure to work</p><p>05) Run setup as with any other installation and follow the prompts. After it finishes installing the system, it will encounter the EFI partition and ask you if you want to format it</p><p>06) Click on "install" on the "<span>ELILO (EFI Linux Loader) installation" screen</span></p><p><span><u><b>Note</b></u>: The text mentions "Apple computers use a different type of EFI firmware and efibotmgr has been know to damage them. On all other computers, it is recommended to add a boot menu entry." and give the options to "install" or "skip". This is the step that creates the boot entry and makes the MacBook Pro recognize the partition and allow you to boot from the installation</span></p><p><span>07) Remove elilo and configure grub. I could not get elilo to work once I updated the kernel, plus I "pimped" my Slackware64-current installation a bit, by creating a png file to display while grub loads with 5 a seconds countdown. I also downloaded a font to use in this splash screen in grub. You can still use "e" while grub is displayed on the screen to login into a different runlevel</span></p><p><span><u><b>Files</b></u>:</span></p><p><span style="color: red;"># grub (place it in <span>/etc/default/</span><span></span> or run the script)</span></p><p><span># If you change this file, run grub-mkconfig -o /boot/grub/grub.cfg<br /># afterwards to update /boot/grub/grub.cfg.<br /><br />GRUB_DEFAULT=0<br />GRUB_HIDDEN_TIMEOUT_QUIET=true<br />GRUB_TIMEOUT=5<br />GRUB_DISTRIBUTOR="Slackware"<br />GRUB_CMDLINE_LINUX_DEFAULT="quiet splash vga=current"<br />GRUB_FONT="/boot/grub/fonts/unicode.pf2"<br />GRUB_DISABLE_OS_PROBER=true<br />GRUB_BACKGROUND="/boot/grub/SlackGrub.png"<br /><br /># Uncomment to enable BadRAM filtering, modify to suit your needs<br /># This works with Linux (no patch required) and with any kernel that obtains<br /># the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)<br />#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"<br /><br /># Uncomment to disable graphical terminal (grub-pc only)<br />#GRUB_TERMINAL=console<br /><br /># The resolution used on graphical terminal<br /># note that you can use only modes which your graphic card supports via VBE<br /># you can see them in real GRUB with the command `vbeinfo'<br />GRUB_GFXMODE=1280x1024<br /><br /># Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux<br />#GRUB_DISABLE_LINUX_UUID=true<br /><br /># Uncomment to disable generation of recovery mode menu entries<br />GRUB_DISABLE_RECOVERY="true"<br /><br /># Uncomment to get a beep at grub start<br />#GRUB_INIT_TUNE="480 440 1"</span></p><p><span style="color: red;"># Save this image as SlackGrub.png and place it in <span><span>/boot/grub/</span></span></span></p><p></p><p><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjWyTXn4ehEsMVNbLsfxBtcZbPxfkK8h3eoOJjkDFdJFUbnp19H5ikKS2zfKnn8RJa_7d5SLKVLQNi2W0ZXSI3hMAO7qNI3uewjVk1VRv8VdSsWpCAers2PW_NMwlInj8JqwjaVZKAtCIk/s1280/SlackGrub.png" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="960" data-original-width="1280" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjWyTXn4ehEsMVNbLsfxBtcZbPxfkK8h3eoOJjkDFdJFUbnp19H5ikKS2zfKnn8RJa_7d5SLKVLQNi2W0ZXSI3hMAO7qNI3uewjVk1VRv8VdSsWpCAers2PW_NMwlInj8JqwjaVZKAtCIk/s320/SlackGrub.png" width="320" /></a><br /><span></span></p><p><span><u><b>Script</b></u>:</span></p><p></p><p></p><p></p><p></p><p><span></span></p><p><span style="color: red;"><span># I saved it as grubconf.sh and chmod +x for it to run<br /></span></span></p><p><span>#!/bin/bash<br />echo "Removing elilo"<br />removepkg elilo<br />cd /boot/efi/EFI/Slackware<br />mv elilo.conf elilo.conf.orig<br />mv elilo.efi elilo.efi.orig<br /><br />echo "Configuring grub"<br />grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=grub --recheck --debug<br />mkdir -p /boot/grub/locale<br />cp /usr/share/locale/en\@quot/LC_MESSAGES/grub.mo /boot/grub/locale/en.mo<br /><br />echo "Copying grub files"<br />cp grub /etc/default/grub<br />cp SlackGrub.png /boot/grub/SlackGrub.png<br />mkdir /boot/grub/fonts<br />cp unicode.pf2 /boot/grub/fonts/unicode.pf2<br /><br />echo "Reconfiguring grub"<br />grub-mkconfig -o /boot/grub/grub.cfg<br /></span></p><p><span><u><b>URLs</b></u>:</span></p><p><span>https://docs.slackware.com/howtos:slackware_admin:set_up_grub_as_boot_loader_on_uefi_based_hardware</span></p><p><span>https://github.com/anak10thn/ign-bootloader/blob/master/ign-grub2/config/boot/grub/ <span style="color: red;">-- Download unicode.pf2 from it</span><br /></span></p><p><span></span><span></span></p><p>Regards,</p><p>F. Bobbio C. </p>FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.com0tag:blogger.com,1999:blog-62889344087522814.post-82504251552338227322021-01-18T12:11:00.008-08:002021-01-18T12:11:59.138-08:00Citrix WorkSpace In Slackware64-current<p>Some time ago I wrote about <a href="http://conoacum.blogspot.com/2018/04/citrix-receiver-in-mozilla-firefox-in.html">Citrix Receiver In Mozilla Firefox (64-bit) In Slackware64-current</a>. Citrix Receiver has been replaced by Citrix WorkSpace. These are the steps to install it in Slackware64-current. </p><p>1) Repackage and install libmanette (SlackBuild: https://github.com/conraid/SlackBuilds/tree/master/libmanette and package: https://ftp.acc.umu.se/pub/GNOME/sources/libmanette/) and webkit2gtk (SlackBuild: http://cgit.ponce.cc/slackbuilds/tree/libraries/webkit2gtk and package: https://www.webkitgtk.org/releases/)</p><p>2) Download the "Tarball Packages" Citrix WorkSpace app for Linux (x86_64) from https://www.citrix.com/downloads/workspace-app/linux/workspace-app-for-linux-latest.html</p><p>3) Untar the package</p><p>4) Open a terminal, su, enter root password</p><p>5) Run ./setupwfc and accept all defaults for installation</p><p>6) cd /opt/Citrix/ICAClient</p><p>7) Run ./selfservice or open Citrix WorkSpace app from KDE menu</p><p>8) Check https://www.citrix.com/content/dam/citrix/en_us/documents/downloads/citrix-receiver/linux-oem-guide-13-1.pdf for information on mapping drives (Hint: Search for "DrivePathA...Z" on page 72 of 104 and read on ~/.ICAClient/wfclient.ini file)</p><p>Regards,</p><p>F. Bobbio C. </p>FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.com0tag:blogger.com,1999:blog-62889344087522814.post-81842760113572356132019-12-23T17:37:00.001-08:002019-12-23T17:37:22.147-08:00Grub In Slackware64-currentAfter upgrading to kernel 5.4.1 in Slackware64-current, elilo did not work at all, even after running eliloconfig. I realized that the latest Slackware64-current ISO (http://slackware.uk/people/alien-current-iso/slackware64-current-iso/) was running grub as the bootloader. I decided to give grub a try. These are the steps I followed:<br />
<br />
1) Uninstall elilo (removepkg elilo)<br />
2) Removed all files under /boot/efi/EFI/elilo (create a backup before removing the folder, in case you need the files afterwards)<br />
3) Run "grub-mkconfig -o /boot/grub/grub.cfg" to create the required boot entries<br />
4) Reboot and test<br />
<br />
Regards,<br />
<br />
F. Bobbio C.FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.com0tag:blogger.com,1999:blog-62889344087522814.post-28946272858313771432019-12-23T17:29:00.004-08:002020-01-07T19:17:23.125-08:00NVIDIA GeForce GTX 1050 In Slackware64-currentUpdate 12-30-2019: My DisplayLink based USB 3.0 docking station is working nicely with the NVIDIA driver now. I had to modify the /etc/rc.d/rc.local file and add the following lines:<br />
<br />
# Load evdi after reboot<br />
modprobe evdi<br />
cd /usr/lib64/displaylink<br />
./DisplayLinkManager &<br />
# Create missing nvidia device nodes after reboot<br />
/usr/bin/nvidia-modprobe -c 0 -u<br />
<br />
I am also using the latest versions of xorg-server, x-org-server-xephyr, xorg-server-xnest and xorg-server-xvfb. I documented all the changes here: http://docs.slackware.com/talk:howtos:hardware:displaylink<br />
<br />
Update 12-26-2019: My DisplayLink based USB 3.0 docking station did not play nicely with the NVIDIA driver. I am using it without the xorg.conf file and the Intel chip. I will use the xorg.conf file and NVIDIA driver in situations when I have to use the HDMI port and the Intel driver without the xorg.conf file when using the USB 3.0 docking station<br />
<br />
My old and trusty Toshiba laptop "died" and I needed to replace it. I purchased an Acer Nitro 5 AN515-53-52FA laptop with an Intel Core i5-8300H Processor 2.3GHz and an NVIDIA GeForce GTX 1050 4GB GDDR5 video card. The Intel built-in video driver worked out of the box on Slackware64-current (kernel 5.4.6), but the NVidia driver could not install and work properly. At the time of this writing, the latest version was 440.44 (https://www.nvidia.com/Download/driverResults.aspx/156086/en-us). The Intel driver did not display the HDMI port at all when running xrandr, only eDP-1-1. I read various pages of tutorials and gathered enough information to fix the issue<br />
<br />
I repackaged nvidia-kernel (http://www.slackbuilds.org/repository/14.2/system/nvidia-kernel/) and nvidia-driver (http://www.slackbuilds.org/repository/14.2/system/nvidia-driver/) using the latest .run file. Once the driver and kernel packages were ready, I installed them and rebooted, with some issues. I rebooted again, and pressed "e" at the grub screen and added "3" at the line starting with "linux" and pressed F10 to boot into runlevel 3 (multiuser, no GUI, just cli, with networking)<br />
<br />
I edited the following files:<br />
<br />
/etc/X11/xorg.conf<br />
Section "ServerLayout"<br />
Identifier "layout"<br />
Screen 0 "nvidia"<br />
Inactive "intel"<br />
EndSection<br />
<br />
Section "Files"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Keyboard0"<br />
Driver "kbd"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Mouse0"<br />
Driver "mouse"<br />
Option "Protocol" "auto"<br />
Option "Device" "/dev/psaux"<br />
Option "Emulate3Buttons" "no"<br />
Option "ZAxisMapping" "4 5"<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "nvidia"<br />
Driver "nvidia"<br />
BusID "PCI:1:0:0"<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "intel"<br />
Driver "modesetting"<br />
BusID "PCI:0:2:0"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "nvidia"<br />
Device "nvidia"<br />
Option "AllowEmptyInitialConfiguration" "Yes"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "intel"<br />
Device "intel"<br />
EndSection<br />
<br />
/usr/share/sddm/scripts/Xsetup<br />
xrandr --setprovideroutputsource modesetting NVIDIA-0<br />
xrandr --auto<br />
<br />
I also removed all files under /var/lib/sddm<br />
rm -R /var/lib/sddm/*<br />
<br />
Upon reboot in runlevel 4, I was able to view port HDMI-0 and plugged in a TV with an HDMI cable. The resolution was 1920 x 1080. The audio also worked in the TV and the laptop was able to use the HDMI port for audio<br />
<br />
I hope this helps someone<br />
<br />
Regards,<br />
<br />
F. Bobbio C.FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.com0tag:blogger.com,1999:blog-62889344087522814.post-30653056039459842272019-07-22T21:10:00.001-07:002019-07-22T21:10:11.131-07:00Meraki L2TP VPN Connection In Slackware64-current Plasma 5 - KDE 5I needed a Meraki VPN connection for Slackware64-current as listed here: https://documentation.meraki.com/MX/Client_VPN/Client_VPN_OS_Configuration#Linux<br />
<br />
I took the idea from http://stuffjasondoes.com/2018/08/16/configuring-meraki-client-vpn-on-linux-mint-19-network-manager/<br />
<br />
You can find more information here: https://wiki.gnome.org/Projects/NetworkManager/VPN<br />
<br />
1) Download NetworkManager-l2tp 1.2.12 from https://github.com/nm-l2tp/NetworkManager-l2tp/releases<br />
<br />
2) Repackage NetworkManager-l2tp using the following, modified SlackBuild:<br />
<br />
#!/bin/sh<br />
<br />
# Slackware build script for NetworkManager-l2tp<br />
<br />
# Copyright 2010-2017 Robby Workman, Tuscaloosa, Alabama, USA<br />
# All rights reserved.<br />
#<br />
# Redistribution and use of this script, with or without modification, is<br />
# permitted provided that the following conditions are met:<br />
#<br />
# 1. Redistributions of this script must retain the above copyright<br />
# notice, this list of conditions and the following disclaimer.<br />
#<br />
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS" AND ANY EXPRESS OR IMPLIED<br />
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF<br />
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO<br />
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,<br />
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,<br />
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;<br />
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,<br />
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR<br />
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF<br />
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.<br />
<br />
PRGNAM=NetworkManager-l2tp<br />
VERSION=${VERSION:-1.2.12}<br />
BUILD=${BUILD:-1}<br />
TAG=${TAG:-_SBo}<br />
<br />
if [ -z "$ARCH" ]; then<br />
case "$( uname -m )" in<br />
i?86) ARCH=i586 ;;<br />
arm*) ARCH=arm ;;<br />
*) ARCH=$( uname -m ) ;;<br />
esac<br />
fi<br />
<br />
CWD=$(pwd)<br />
TMP=${TMP:-/tmp/SBo}<br />
PKG=$TMP/package-$PRGNAM<br />
OUTPUT=${OUTPUT:-/tmp}<br />
<br />
if [ "$ARCH" = "i586" ]; then<br />
SLKCFLAGS="-O2 -march=i586 -mtune=i686"<br />
LIBDIRSUFFIX=""<br />
elif [ "$ARCH" = "x86_64" ]; then<br />
SLKCFLAGS="-O2 -fPIC"<br />
LIBDIRSUFFIX="64"<br />
else<br />
SLKCFLAGS="-O2"<br />
LIBDIRSUFFIX=""<br />
fi<br />
<br />
set -e<br />
<br />
rm -rf $PKG<br />
mkdir -p $TMP $PKG $OUTPUT<br />
cd $TMP<br />
rm -rf $PRGNAM-$VERSION<br />
tar xvf $CWD/$PRGNAM-$VERSION.tar.xz<br />
cd $PRGNAM-$VERSION<br />
chown -R root:root .<br />
find -L . \<br />
\( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 -o -perm 511 \) \<br />
-exec chmod 755 {} \; -o \<br />
\( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \<br />
-exec chmod 644 {} \;<br />
<br />
CFLAGS="$SLKCFLAGS" \<br />
CXXFLAGS="$SLKCFLAGS" \<br />
./configure \<br />
--prefix=/usr \<br />
--libdir=/usr/lib${LIBDIRSUFFIX} \<br />
--sysconfdir=/etc \<br />
--localstatedir=/var \<br />
--mandir=/usr/man \<br />
--docdir=/usr/doc/$PRGNAM-$VERSION \<br />
--without-libnm-glib \<br />
--build=$ARCH-slackware-linux<br />
<br />
make<br />
make install DESTDIR=$PKG<br />
<br />
# Create the chroot directory<br />
mkdir -p $PKG/var/lib/l2tp/chroot<br />
<br />
find $PKG | xargs file | grep -e "executable" -e "shared object" | grep ELF \<br />
| cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true<br />
<br />
mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION<br />
<br />
mkdir -p $PKG/install<br />
cat $CWD/slack-desc > $PKG/install/slack-desc<br />
<br />
cd $PKG<br />
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz}<br />
<br />
3) Download, repackage and install xl2tpd 1.3.14 using the SlackBuild from ponce's repository: http://cgit.ponce.cc/slackbuilds/tree/network/xl2tpd<br />
<br />
4) Download, repackage and install strongswan 5.8.0 using the SlackBuild from ponce's repository: http://cgit.ponce.cc/slackbuilds/tree/network/strongswan<br />
<br />
5) Create the VPN connection using NetworkManager, as a "Layer 2 Tunneling Protocol (L2TP)" connection:<br />
<br />
Give the connection a name under "Connection name:" on the top section<br />
Under the "VPN (l2tp)" tab, enter the "Gateway:", "User name:", "Password:" and "NT Domain:"<br />
Under the "VPN (l2tp)" tab, click on "IPsec Settings...", check "Enable IPsec tunnel to L2TP host", enter your secret under "Pre-shared Key:", enter 3des-sha1-modp1024 under "Phase1 algorithms:" and 3des-sha1 under "Phase2 algorithms:", click on "OK"<br />
Under the "VPN (l2tp)" tab, click on "PPP Settings...", check only "PAP" under "Allow following authentication methods" and uncheck all other methods, uncheck "Use MPPE Encryption", check "Allow BSD compression", "Allow Deflate compression", "Allow TCP header compression", "Use protocol field compression negotiation", and "Use Address/Control compression". Leave "Send PPP echo packets" unchecked. Under "Other Settings", change "MRU:" and "MTU:" to 1400, click on "OK"<br />
Under the "IPv4" tab, enter your Active Directory domain or domains under "Search Domains:". Click on "Routes...". Click on "+ Add" and enter the proper "Address", "Netmask", "Gateway" and "Metric". Click on "+ Add" and follow the same instructions until you add all proper routes (Hint: Routes can be found by running route in a terminal session). Click on "OK"<br />
Click on "Apply" and then on "OK"<br />
<br />
6) Test your newly created L2TP connection<br />
<br />
Regards,<br />
<br />
F. Bobbio C.FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.com0tag:blogger.com,1999:blog-62889344087522814.post-36094943475378245632018-09-28T04:51:00.005-07:002022-08-28T19:18:28.531-07:00Microsoft Exchange Mozilla Thunderbird Integration<p>Update 08-28-2022: TbSync does not work with Thunderbird 102.2.0. I am now using <a href="https://outlook.office365.com" target="_blank">OWA</a><br /></p><p>Update 09-21-2019: ExchangeCalendar does not work with Thunderbird 68.1.0. I am now using IMAP + TbSync successfully<br />
<br />
Update 08-18-2019: Since ExQuilla has slowed down the opening of Thunderbird (2 to 3 minutes to open Thunderbird, with constant "freezing" during the day) I am now using the Exchange accounts via IMAP + TbSync + ExchangeCalendar<br />
<br />
Update 12-30-2018: I now use ExchangeCalendar (https://github.com/ExchangeCalendar/exchangecalendar/releases) instead of TbSync. ExchangeCalendar integrates seamlessly with Thunderbird to display meetings and times slotted in Exchange<br />
<br />
Most of the users I encounter work in a Microsoft Windows environment or use a Microsoft Windows based machine (desktop or laptop). Some others use a macOS based machine (iMac, MacBook Air or MacBook Pro). The rest of us, though, prefer to work in a Linux based machine, some with access to cli and others with a GUI<br />
<br />
In a Microsoft Windows business environment, the business "de facto" E-Mail client is Microsoft Outlook, since it communicates with Exchange servers to synchronize E-Mails, calendars, tasks and contacts. Microsoft Outlook can also be installed in macOS based devices, with similar capabilities. In Linux, some of us use Mozilla Thunderbird<br />
<br />
One big issue that most Mozilla Thunderbird users encounter is the inability to tie directly to Exchange. The workaround is either using the web portal for Microsoft (https://outlook.office365.com), but in some cases (nowadays less and less) the Exchange server is on premises. Meet ExQuilla for Microsoft Exchange by R Kent James and TbSync by John Bieling. Both, ExQuilla and TbSync, are add-ons for Mozilla Thunderbird<br />
<br />
ExQuilla can be downloaded from https://addons.thunderbird.net/en-US/thunderbird/addon/exquilla-exchange-web-services/ as an xpi file and installed in Mozilla Thunderbird by clicking on "Tools", "Add-ons", the gear on the top section, towards the left, "Install Add-on From File...". Once it is installed, either use the "Autodiscover" feature or the "Manual" one. In my case, I had to use the "Manual" one, enter the "Microsoft Exchange EWS URL" (https://outlook.office365.com/EWS/Exchange.asmx) and "Test EWS URL". The proper EWS URL can be found following step 2. in https://support.neuxpower.com/hc/en-us/articles/202482832-Determining-the-Exchange-Web-Services-EWS-URL<br />
<br />
TbSync can be downloaded from https://github.com/jobisoft/TbSync/releases as an xpi file as well using the same procedure for installing ExQuilla. Once installed, double click the icon on the lower right corner of Mozilla Thunderbird labeled "TbSync: Idle", click on "Account actions", "+ Add new account", "Exchange ActiveSync (EAS)", enter proper information and either use the "Automatic configuration via ActiveSync Autodiscover" or "Custom configuration". In my case, I had to use the "Custom configuration", with "Server address" https://outlook.office365.com and "ActiveSync version" v2.5. Click on "Enable account & try to connect to server"<br />
<br />
The E-Mails will show as a new account with an "X" preceding it on the left pane in Mozilla Thunderbird. The contacts will show in the "Address Book". The address book with "/GAL" will allow for contact queries/searches, as if you were using Microsoft Outlook. The same procedure can be used in Mozilla Thunderbird in Microsoft Windows and macOS based machines <br />
<br />
Regards,<br />
<br />
F. Bobbio C.</p>FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.com0tag:blogger.com,1999:blog-62889344087522814.post-6436315230195149812018-08-03T05:27:00.001-07:002018-08-03T05:29:06.691-07:00Automated Data Transfer - Linux To Windows + Vice VersaRecently one of the developers where I work had an interesting task to accomplish: Transfer data from a Windows server to a Linux server and vice versa automatically every 5 minutes for a production environment. The data originated at the Windows server, was processed in the Linux server, copied to a different path and the result needed to be copied back to the Windows server, to a different folder. The accounting users were saving the original data to a Windows shared folder. The process needed to originate at the Windows server, since my team mates were not proficient in Linux, in case the files needed to be modified later on<br />
<br />
Thanks to WinSCP, the solution was simple:<br />
<br />
1) Create a batch file (WinSCP2Linux.bat) with permissions for service account to read and execute. The content should be something similar to this:<br />
<br />
winscp.com /ini=nul /synchronize /script=C:\Users\LocalAdmin\ScriptCopyToOracle.txt<br />
<br />
2) Create a text file (C:\Users\LocalAdmin\ScriptCopyToOracle.txt), with permissions for service account to read and execute. The content should be something similar to this:<br />
<br />
open sftp://LinuxServerUsername:LinuxServerUserPassword@LinuxServerName/ -hostkey="ssh-rsa 2048 xx:yy:zz:aa:bb:cc..."<br />
put C:\Path\To\Windows\Original\Files\* /path/to/Linux/server/firstfolder/<br />
get /path/to/Linux/server/secondfolder/* C:\Path\To\Windows\Processed\Files\<br />
exit<br />
<br />
Note: LinuxServerUsername requires read and write permissions to both Linux folders for this procedure to work. Both Windows folders have read and write permissions<br />
<br />
3) Create a task via "Task Scheduler" which runs the batch file every 5 minutes and runs under the service account specified in step 1)<br />
<br />
The task will only synchronize files that are not in the folders every 5 minutes. I would recommend testing if the task works by opening an elevated command prompt ("Start", cmd, right click, "Run as administrator"), pasting winscp.com /ini=nul /synchronize /script=C:\Users\LocalAdmin\ScriptCopyToOracle.txt into it and hitting the "Enter" key. If there are no errors, you should see the processed files in the firstfolder in Linux and in the processed files folder in Windows<br />
<br />
The Linux server was running Red Hat Linux and the Windows server was on Windows Server 2012<br />
<br />
Regards,<br />
<br />
F. Bobbio C.FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.com0tag:blogger.com,1999:blog-62889344087522814.post-45963206927836575442018-08-03T05:11:00.003-07:002019-11-26T10:20:53.798-08:00Corrupted Profile - In A MacAny IT professional that deals with users needs to know a bit of other Operating Systems. The three main ones currently are Windows, macOS and Linux.<br />
<br />
I recently had a case where a customer using a Mac could not open any application. When the application icon was clicked, there were errors pointing to the Library folder and cache. All applications had the same issue. I thought about it for some minutes and logged out and back in, but under a different profile. The other profile did not display those issues, thus the issue being with the original profile<br />
<br />
I created a new profile with Administrator privileges (that was the access level for the original profile) and copied all documents over, thinking that all permissions would transfer, but, how wrong was I! The permissions for the iPhoto and Photo libraries did not transfer. They were under OriginalUser:OriginalGroup and the new user was NewUser:staff and when the customer tried to open iPhoto or Photos, there was an error about permissions<br />
<br />
I had to use a bit of "command line" (or console/terminal) "magic" and change the permissions for the whole folder/application. I logged out and back in with another Administrator account, since the new user account did not allow me for the change. The other account did not have any password, which did not allow for sudo access. I changed the password and ran the commands, each in a different terminal session. Click on the upper right corner on "Spotlight" and type terminal. Open the application. Right click on the application icon on the lower bar and "New window" for the second terminal session<br />
<br />
First terminal session:<br />
sudo chown -R NewUser:staff /Users/NewUser/Pictures/iPhoto Library.photolibrary<br />
<br />
Second terminal session:<br />
sudo chown -R NewUser:staff /Users/NewUser/Pictures/Photos Library.photoslibrary/<br />
<br />
Let both commands run until they finish. In this case, the customer had well over 250 GB of pictures in each application. The process took all night long. Once the terminal session showed the MacDeviceName:~ AdminUser$ prompt in each terminal session, the customer closed everything (Command + Q in each window) and logged out and back in. The customer reported all the pictures were accessible and viewable. No more permissions errors<br />
<br />
I hope this helps someone<br />
<br />
Regards,<br />
<br />
F. Bobbio C.FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.com0tag:blogger.com,1999:blog-62889344087522814.post-20719984681900304482018-06-20T04:33:00.000-07:002018-06-23T11:02:18.439-07:00Barco ClickShare In Slackware64-currentUpdate 06-23-2018: According to https://www.barco.com/en/support/clickshare%20csc-1/knowledge-base/KB1191 users can use MirrorOp or the Google Cast extension to share screen<br />
<br />
ClickShare is a neat way of presenting the content of your machine (and 3 others) without having to plug and unplug an HDMI cable. ClickShare, by Barco (https://www.barco.com/en/clickshare), requires a USB port to work. Simply plug in the USB adapter and run the .exe (MS Windows) or .dmg (macOS) file.<br />
Unfortunately, back in December 2017, Barco stopped support for Linux clients (https://www.barco.com/en/support/clickshare%20csc-1/knowledge-base/KB1191).<br />
Since a Slacker does not give up easily, I setup to install and run ClickShare on Slackware-current. Here are the steps I needed to follow to accomplish this task.<br />
<br />
1) Download and install ffmpeg 2.1.5 (http://slackware.uk/slacky/slackware64-14.1/multimedia/ffmpeg/2.1.3/ may also do it) (ffmpeg 3.X does not work with ClickShare). This version of ffmpeg will allow the use of libswresample.so.2<br />
Note: Even ffmpeg 2.8.6 will use libswresample.so.3 which will not work with ClickShare<br />
<br />
2) Download the SlackBuild script for libresample from PhantomX (https://github.com/PhantomX/slackbuilds/tree/master/libresample). This will repackage libresample in 64-bit for your system. There are some libresample packages for Slackware, but for x86, not x86_64<br />
Repackage libresample and install it<br />
<br />
3) Download clickshare_01.07.01-79_amd64.deb (https://drive.google.com/drive/folders/0B9IKZqXvLKM_Yno1UmpGLVRXNDg)<br />
This package was a bit harder to find, since Barco does not offer it anymore on its website<br />
<br />
4) Decompress the contents and cp -a the content into the appropriate folders<br />
<br />
5) Start ClickShare by typing clickshare in a terminal session or from your launcher <br />
<br />
Regards,<br />
<br />
F. Bobbio C.FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.com0tag:blogger.com,1999:blog-62889344087522814.post-85622978619544719542018-04-21T07:06:00.003-07:002020-03-13T16:23:05.649-07:00Citrix Receiver In Mozilla Firefox (64-bit) In Slackware64-currentUpdate 03-02-2020: In case you run into SSL error 61, download "GoDaddy Secure Server Certificate (Intermediate Certificate) - G2" in "crt (DER)" format from the GoDaddy Repository (https://ssl-ccp.godaddy.com/repository?origin=CALLISTO) and follow steps in Error: "SSL Error 61: You have not chosen to trust 'Certificate Authority'..." on Receiver for Linux (https://support.citrix.com/article/CTX203362). In my case ICAROOT is located under /opt/Citrix/ICAClient<br />
1) cd to the location of the downloaded crt certificate<br />
2) cp gdig2.crt /opt/Citrix/ICAClient/keystore/cacerts/<br />
3) cd /opt/Citrix/ICAClient/util/<br />
4) su and enter root password<br />
5) ./ctx_rehash<br />
6) Try the icon on the Citrix page again<br />
<br />
Update 01-02-2019: Citrix Receiver has not updated for a while and has been replaced by Citrix Workspace: https://www.citrix.com/downloads/workspace-app/linux/workspace-app-for-linux-latest.html but I still received error messages regarding "0.0.0.2 - Application No such file or directory. Verify your connection settings and try again." even after installing certificates and creating symbolic links for libidn. The internal storefront works without any issues, while the external one has some issues if using Mozilla Firefox or Google Chrome in Slackware64-current. This issue does not happen in Microsoft Windows 10.<br />
After a bit of research and reading, I found this forum https://www.linuxquestions.org/questions/slackware-14/citrix-receiver-problems-due-to-missing-libidn-so-11-in-current-of-2018-06-21-a-4175632430/ where they listed this URL for Chrome: https://chrome.google.com/webstore/detail/citrix-workspace/haiffjcadagjlijoggckpgfnoeiflnem?hl=en as an "app" for Google Chrome. The "app" is working great so far. No need to install Citrix Receiver anymore, just point the "app" to the proper URL for your storefront and enjoy<br />
<br />
Update 12-23-2018: In cases where there is a black square around the mouse pointer, follow the instructions in this page: https://support.citrix.com/article/CTX212013<br />
<br />
Citrix Receiver is a virtualization client which allows to run applications and programs running on a Citrix server from within a browser connection<br />
<br />
In the Microsoft Windows world, you can simply download and install an application that would start when you login to your computer and even allows to use single sign on (https://www.citrix.com/downloads/citrix-receiver/windows/receiver-for-windows-latest.html), but my laptop is Linux based and I prefer to use Citrix Receiver natively in Linux<br />
<br />
In the past, you needed to run a multilib system to run Citrix Receiver (https://docs.slackware.com/howtos:network_services:citrix_client or https://alien.slackbook.org/blog/new-multilib-versions-of-glibc-and-gcc-for-slackware-current/), but luckily for all of us, now the 64-bit version of Citrix Receiver can be run on Firefox without an issue<br />
<br />
1) Download Citrix Receiver from https://www.citrix.com/downloads/citrix-receiver/linux/receiver-for-linux-latest.html by choosing "Tarball Packages" and "Receiver for Linux (x86_64). Accept the license agreement and save the tar.gz file<br />
<br />
2) Navigate to the location where you saved the the tar.gz file and extract it (tar vxf linuxx64-13.9.1.6.tar.gz in this case)<br />
<br />
3) Run setupwfc as root and choose "1. Install Citrix Receiver for Linux 13.9.1"<br />
<br />
4) Follow the prompts, making sure to select "n" for "Do you want to install USB support? [default n]:"<br />
<br />
5) Follow steps "5. Add more SSL certificates" and "7. (64-bit only) Fix Firefox plugin installation" from https://help.ubuntu.com/community/CitrixICAClientHowTo<br />
<br />
Note: If steps 5 and 7 from https://help.ubuntu.com/community/CitrixICAClientHowTo are not followed, error message "Cannot connect to "0.0.0.2 - Application No such file or directory. Verify your connection settings and try again." may display on the screen when trying to launch an application<br />
<br />
6) Alternatively follow step "6. Configure Citrix Receiver" from https://help.ubuntu.com/community/CitrixICAClientHowTo if you want to map drives to allow access to files in the remote Citrix session<br />
<br />
7) Create symbolic links, if needed, for libidn:<br />
ln -s libidn.so.12.6.0 libidn.so.11<br />
ln -s libidn.so.12.6.0 libidn.so<br />
<br />
Regards,<br />
<br />
F. Bobbio C.FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.com0tag:blogger.com,1999:blog-62889344087522814.post-3943848810228038132018-04-21T06:44:00.003-07:002018-06-18T18:38:43.526-07:00VPN Connections In Slackware64-current Plasma 5 - KDE 5I use three different VPN connections in my laptop: OpenConnect, OpenVPN and PPTP. I like these connections to be managed by NetworkManager and not by third parties<br />
<br />
The first one (OpenConnect) is compatible with Cisco AnyConnect: http://www.infradead.org/openconnect/<br />
<br />
The second one (OpenVPN) is compatible with pfSense: https://openvpn.net/<br />
<br />
The third one is used to connect to a Point-to-Point Windows server: http://pptpclient.sourceforge.net/<br />
<br />
After some updates in Slackware-current and KDE5, the connections stopped working. These are the steps I followed to have the connections up and running<br />
<br />
OpenConnect:<br />
I repackaged openconnect from https://www.slackbuilds.org/repository/14.2/network/openconnect/ and used the same NetworkManager-openconnect package for 14.2 from https://www.slackbuilds.org/repository/14.2/network/NetworkManager-openconnect/<br />
I also found a Plasma 5 NetworkManager package at https://github.com/philipvdh/slackbuilds/tree/master/plasma5-nm-openconnect (from rworkman) by searching on Google for plasma5-nm-openconnect and followed the .info file in there to download the latest version of the package from https://github.com/KDE/plasma-nm/releases which matched with the Plasma packages (5.12.4). This last step did the trick for OpenConnect<br />
The alternative would be to download and run the Cisco AnyConnect native client for Linux<br />
<br />
OpenVPN:<br />
I repackaged openvpn from https://ftp.osuosl.org/pub/slackware/slackware64-current/source/n/openvpn/ and used the NetworkManager-openvpn SlackBuilds script from https://www.slackbuilds.org/repository/14.2/network/NetworkManager-openvpn/ which worked fine, but I changed the tar.xz file to be the latest (1.8.2) and used the package from https://download.gnome.org/sources/NetworkManager-openvpn/1.8/NetworkManager-openvpn-1.8.2.tar.xz<br />
The plasma5-nm-5.12.4 package from alienBOB worked perfectly for this connection<br />
I imported the ovpn file that I have saved and used before<br />
<br />
PPTP:<br />
I repackaged pptp from https://www.slackbuilds.org/repository/14.2/network/pptp/using the latest version (1.10.0) from https://sourceforge.net/projects/pptpclient/files/ and used the NetworkManager-pptp SlackBuilds script from https://www.slackbuilds.org/repository/14.2/network/NetworkManager-pptp/ which worked fine, but I changed the tar.xz file to be the latest (1.2.6) and used the package from http://ftp.gnome.org/pub/GNOME/sources/NetworkManager-pptp/1.2/NetworkManager-pptp-1.2.6.tar.xz<br />
The main part is to click on "Advanced..." and select only "MSCHAP" and "MSCHAPv2" under "Allow following authentication methods:" and "Use MPPE Encryption" with "Crypto: Any"<br />
<br />
Regards,<br />
<br />
F. Bobbio C.FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.com0tag:blogger.com,1999:blog-62889344087522814.post-1017566372128247202018-03-18T09:01:00.003-07:002018-03-18T09:02:46.772-07:00Remmina RDP IssueRemmina allows to connect to computers via different protocols (NX, RDP, SFTP, SSH, VNC and even XDMCP). Microsoft Windows allows remote control of a computer via RDP (Remote Desktop Protocol). Some Windows Updates in March, 2018 may break connectivity via Remmina, which uses FreeRDP to connect to Microsoft Windows machines. This is not an issue with FreeRDP, but with some implementation or modification on Microsoft's side, which tries to only allow machines within the domain to use RDP to communicate with each other.<br />
<br />
There is a simple fix for this. Follow these steps:<br />
<br />
Microsoft Windows:<br />
1) Connect to the Microsoft Windows machine via RDP from another Microsoft Windows machine using "Remote Desktop Connection" by typing mstsc in the "Start" menu and typing either the computer name or its IP address. Use proper credentials<br />
2) Right click on "Computer", "My PC" or "This PC" and click on "Properties"<br />
3) Click on "Change settings"<br />
4) Click on the "Remote" tab<br />
5) Uncheck the "Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)"<br />
6) Open "Services" by typing services.msc in the "Start" menu<br />
7) Restart "Remote Desktop Services" by right clicking on it and clicking on "Restart"<br />
Note: This last step will disconnect the RDP session<br />
8) Attempt connection to machine again after 15 to 30 seconds<br />
<br />
Remmina<br />
1) Right click on the machine name from step 1) in the Microsoft Windows section<br />
2) Click on "Edit"<br />
3) Click on the "Advanced" tab<br />
4) Change "Security" to "RDP"<br />
Note: Option "NLA" for "Network Level Authentication" may not work, neither does option "Negotiate" (default)<br />
5) Click on "Save"<br />
6) Double click on machine name to attempt connection, which should be successful<br />
<br />
Regards,<br />
<br />
F. Bobbio C.FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.com1tag:blogger.com,1999:blog-62889344087522814.post-55339630178567807852018-02-14T13:53:00.000-08:002018-06-18T18:38:24.493-07:00KUser In Slackware64-current Plasma 5 - KDE 5One part of systems administration is adding, removing and modifying groups and users. These tasks can be accomplished via a terminal session using the following commands:<br />
<br />
Adding a group: groupadd groupname<br />
Adding a user: useradd username<br />
Adding a user to a group: usermod -aG groupname username<br />
<br />
More information on how to add, remove and modify groups and users can be found here: https://www.tecmint.com/delete-remove-a-user-account-with-home-directory-in-linux/<br />
<br />
In Slackware, I used KUser until KDE 4. KUser allowed me to manage groups and users graphically. KDE 5 does not have KUser installed. I downloaded KUser from Slackware-current, copied three libraries needed by KUser to run (libkabc.so.4.14.38, libkldap.so.4.14.38 and libkresources.so.4.14.38) and created symbolic links. All libraries have to be in /usr/lib64<br />
<br />
The dynamic links I created were:<br />
<br />
libkabc.so.4 as a symbolic link to libkabc.so.4.14.38<br />
libkabc.so as a symbolic link to libkabc.so.4<br />
libkldap.so.4 as a symbolic link to libkldap.so.4.14.38<br />
libkldap.so as a symbolic link to libkldap.so.4<br />
libkresources.so.4 as a symbolic link to libkresources.so.4.14.38<br />
libkresources.so as a symbolic link to libkresources.so.4<br />
<br />
Regards,<br />
<br />
F. Bobbio C.FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.com0tag:blogger.com,1999:blog-62889344087522814.post-25101664528724087182018-02-02T08:28:00.001-08:002018-06-18T18:38:54.765-07:00Plasma 5 - KDE5 In Slackware64-currentTechnology changes constantly, and as such, we need to adapt. One of those changes, in my field of work, is the Graphical User Interface (GUI). In Linux, my OS of choice, I use KDE. Slackware-current comes with KDE 4.14.3 installed. KDE 5 has been around for a while, though, so I decided to "bite the bullet" and installed on my Slackware-current system, using the instructions on https://slackware.nl/alien-kde/current/latest/README<br />
<br />
I took a different approach, since I still consider myself a "novice" in the Linux world, even though I have been using it for quite a while, due to the fact that I am constantly learning something new. The steps I took were:<br />
<br />
00) Take a screenshot of your whole screen, especially if you are using specific icons on the "Panel", since you will need to dock those icons after this whole procedure<br />
01) rsync -Hav --exclude=x86 rsync://slackware.nl/mirrors/alien-kde/current/5/ 5/<br />
02) telinit 3 would not work for me, since /etc/inittab was set to id:4:initdefault:<br />
03) Modified /etc/inittab to id:3:initdefault:<br />
04) Rebooted<br />
05) slackpkg remove kde<br />
06) cd to the location of the folder where you "rsynced" 5 in step 01)<br />
07) upgradepkg --reinstall --install-new x86_64/deps/*.t?z<br />
08) upgradepkg --reinstall --install-new x86_64/deps/telepathy/*.t?z<br />
09) upgradepkg --reinstall --install-new x86_64/kde/*/*.t?z<br />
10) find /etc/ -name "*.new"<br />
11) slackpkg new-config<br />
12) Reboot<br />
13) xwmconfig 'xinitrc.plasma' as your desktop session<br />
14) Modify /etc/inittab to id:4:initdefault:<br />
15) startx<br />
16) Dock any icons you may need (see step 00)<br />
17) Change settings for keyboard layout, etc.<br />
18) Enabled multiple monitors (http://conoacum.blogspot.com/2018/02/multiple-monitors-in-slackware-current.html)<br />
<br />
Regards,<br />
<br />
F. Bobbio C.FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.com0tag:blogger.com,1999:blog-62889344087522814.post-52820116079682674722018-02-02T08:22:00.002-08:002019-12-29T15:15:40.508-08:00Multiple Monitors In Slackware64-currentUpdate 12-26-2019: I am using a USB 3.0 Dell D3100 docking station with 3 monitors. These are the new files I use with the Intel driver and with the NVIDIA driver:<br />
<br />
Intel:<br />
xrandr --listproviders --setprovideroutputsource 1 0 --setprovideroutputsource 2 0 --setprovideroutputsource 3 0<br />
xrandr --output DVI-I-3-3 --auto --output DVI-I-2-2 --auto --output DVI-I-1-1 --auto<br />
xrandr --output DVI-I-3-3 --pos 0x0 --output DVI-I-2-2 --pos 1920x0 --primary --output DVI-I-1-1 --pos 3840x0 --output eDP-1 --pos 5760x0<br />
<br />
NVIDIA:<br />
xrandr --listproviders --setprovideroutputsource 1 0 --setprovideroutputsource 2 0 --setprovideroutputsource 3 0<br />
xrandr --output DVI-I-4-3 --auto --output DVI-I-3-2 --auto --output DVI-I-2-1 --auto<br />
xrandr --output DVI-I-4-3 --pos 0x0 --output DVI-I-3-2 --pos 1920x0 --primary --output DVI-I-2-1 --pos 3840x0 --output eDP-1-1 --pos 5760x0<br />
<br />
I use a Toshiba Satellite S55 laptop for personal and sometimes work related tasks. The laptop has an HDMI port which works fine when I plug in an external monitor/LCD TV. At work I sometimes need the extra space and do not have a big TV that I can plug into it at all. I purchased a USB 3.0 Lenovo ThinkPad docking station, which features two DVI ports, which I use with a DVI to VGA converter and a DVI to HDMI converter to two HP w2338h LCDs. Since this docking station is based on the DisplayLink chipset, I downloaded and installed the DisplayLink drivers using alienBOB's excellent wiki for it: <br />
https://docs.slackware.com/howtos:hardware:displaylink<br />
I will not repeat what he already mentions on the wiki, since the instructions are self explanatory and spot-on<br />
<br />
I also created a shell script that I use to setup the monitors properly that I run when I am at work, since I do not use the same docking station at home. The proper --output will be displayed when running xrandr with the docking station plugged in. The script is as follows:<br />
<br />
xrandr --listproviders<br />
xrandr --setprovideroutputsource 1 0<br />
xrandr --setprovideroutputsource 2 0<br />
xrandr --output DVI-I-1-1 --auto *** Change DVI-I-1-1 to proper output<br />
xrandr --output DVI-I-2-2 --auto *** Change DVI-I-2-2 to proper output<br />
xrandr --output DVI-I-1-1 --pos 1920x0 *** Change DVI-I-1-1 to proper output. This is the center monitor (1920x1080)<br />
xrandr --output DVI-I-2-2 --pos 0x0 *** Change DVI-I-2-2 to proper output. This is the monitor on the left (1920x1080)<br />
xrandr --output eDP1 --pos 3840x312 *** Change eDP1 to proper output. This is the built-in laptop monitor, on the right (1366x768)<br />
<br />
Save it to a proper location (monitors.sh), make it executable (chmod +x monitors.sh) and run it whenever you plug in the USB 3.0 docking station (sh monitors.sh)<br />
<br />
I have tested this setup on Slackware 14.0, 14,1, 14.2 and Slackware-current, even with KDE5, without any issues<br />
<br />
Regards,<br />
<br />
F. Bobbio C.FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.com0tag:blogger.com,1999:blog-62889344087522814.post-82286931198261108912018-01-18T07:24:00.004-08:002018-06-18T18:39:17.981-07:00TightVNC En Slackware64-currentPara algunos usuarios es difícil la transición de Microsoft Windows a Linux debido a la interface gráfica ("Graphical User Interface", o "GUI"). El protocolo VNC permite acceder a máquinas de Linux en interface gráfica, en casos donde los paquetes de la interface gráfica hayan sido instalados. Uno de los paquetes para VNC es TightVNC, el cual usé para este propósito:<br />
<br />
1) Descargué y desempaqueté tightvnc desde SlackBuilds: https://slackbuilds.org/repository/14.2/network/tightvnc/?search=tightvnc<br />
<br />
2) Creé el archivo /etc/rc.d/rc.vncserver de acuerdo a https://www.linuxquestions.org/questions/slackware-14/start-vncserver-at-boot-as-non-root-user-403757/ cambiando las líneas 7, 8, 9 y 10<br />
VNCSERVERS="1:NombreUsuario1 2:NombreUsuario2 3:NombreUsuario3" ### Usar los nombres de usuarios ya creados y que necesiten entrar via VNC ###<br />
VNCSERVERARGS[1]="-geometry 1366x768"<br />
VNCSERVERARGS[2]="-geometry 1920x1080"<br />
VNCSERVERARGS[3]="-geometry 1920x1080"<br />
<br />
3) Cambié los permisos de ejecución (chmod +x /etc/rc.d/rc.vncserver) e ingresé dos entradas en /etc/rc.d/rc.local para iniciarlo:<br />
cd /etc/rc.d<br />
./rc.vncserver start<br />
<br />
4) Ingresé como cada usuario y se creó el archivo xstartup en el directorio oculto vnc en el "hogar" de cada usuario, el cual tuve que modificar:<br />
#!/bin/sh<br />
xrdb $HOME/.Xresources<br />
xsetroot -solid grey<br />
startkde & ### Esta fue la línea que cambié ###<br />
<br />
5) Modifiqué el archivo /usr/bin/vncserver, línea 37 <br />
De $fontPath = 'unix/:7100'; a $fontPath = "/usr/share/fonts/misc/";<br />
<br />
6) Ejecuté rc.vncserver start<br />
<br />
¡Listo! Ahora los usuarios pueden conectarse usando VNC<br />
<br />
Saludos,<br />
<br />
F. Bobbio C.FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.com0tag:blogger.com,1999:blog-62889344087522814.post-45032090095274109502018-01-03T22:17:00.000-08:002018-06-23T11:01:04.722-07:00TeamViewer 13 En Slackware64-currentActualización 06-23-2018: Ya existe un SlackBuild para instalar TeamViewer en Slackware64-current<br />
<br />
TeamViewer es un programa de control remoto que se puede instalar en Windows, macOS y hasta en Linux. Hasta hace poco, la instalación en Slackware requería usar wine (winehq.com), que no es un emulador, pero permite ejecutar ciertas aplicaciones de Windows en Linux. El usar wine es un proceso a veces tedioso, puesto que no todas las aplicaciones pueden ejecutarse en la misma versión de wine<br />
<br />
Hace unos días vi que existía TeamViewer 13, pero que no había instalador para Slackware. Según la página de descarga de TeamViewer 13 (https://www.teamviewer.com/en/download/linux/), los requerimientos básicos son al menos Qt 5.2, Kernel 2.6.27 y GLIBC 2.17<br />
La versión de Slackware-current del 03 de enero del 2018 tiene kernel 4.9.67 y glibc 2.26, pero solamente qt4, por lo cual primero intenté instalar qt5 desde https://download.qt.io/archive/qt/ usando el archivo .run dentro de 5.10, pero luego de instalarlo en /opt, TeamViewer aún no cargaba. Se me ocurrió entonces descargar e instalar los paquetes de qt5 y qt5-webkit desde la página de Eric Hameleers (también conocido como alienBOB), el cual tiene los instaladores reempaquetados: http://www.slackware.com/~alien/slackbuilds/<br />
<br />
Luego de instalar ambos paquetes, instalé teamviewer usando el paquete x86 64bits (tar.xz) de https://www.teamviewer.com/en/download/linux/ y aún así no cargaba TeamViewer. El paso final fue agregar dos líneas a /etc/rc.d/rc.local que es el archivo que ejecuta scripts que uno desea cargar al iniciar Slackware. Las dos líneas fueron:<br />
cd /etc/init.d<br />
./teamviewerd start<br />
<br />
Luego de reiniciar mi portátil, TeamViewer pudo iniciar sin problema alguno. Espero les sirva<br />
<br />
Saludos,<br />
<br />
F. Bobbio C.FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.com0tag:blogger.com,1999:blog-62889344087522814.post-80214344983740680902017-12-22T14:58:00.001-08:002018-06-18T18:39:38.059-07:00DokuWiki En Slackware64-currentHoy instalé DokuWiki en una máquina en Slackware-current<br />
La instalación por defecto de Slackware incluye el servidor web de Apache (httpd), php y otros paquetes que son necesarios para esta instalación<br />
La máquina en la que instalé DokuWiki no tiene monitor, teclado, ni ratón, pero sí una conexión de red y un cable de poder, por lo cual ingresé por medio de una conexión ssh<br />
La máquina es una Intel Core 2 Duo con 4 GB de RAM y dos discos sólidos de 128 GB cada uno <br />
Usé la página de SlackBuild para re-empaquetar DokuWiki:<br />
https://slackbuilds.org/repository/14.2/network/dokuwiki/?search=dokuwiki<br />
<br />
Descarqué el script usando wget https://slackbuilds.org/slackbuilds/14.2/network/dokuwiki.tar.gz<br />
Desempaqueté el archivo: tar -vxf dokuwiki.tar.gz y luego cd dokuwiki<br />
Cambié lo siguiente:<br />
* Descargué la versión más reciente desde https://download.dokuwiki.org/ bajo "Stable (Recommended) (direct link)" usando wget https://download.dokuwiki.org/src/dokuwiki/dokuwiki-stable.tgz<br />
* Copié la versión del paquete de la línea debajo de "Stable (Recommended)"<br />
* Renombré el paquete: mv dokuwiki-stable.tgz dokuwiki-2017-02-19e.tgz<br />
* Modifiqué dos líneas del archivo dokuwiki.SlackBuild:&nbsp; vi dokuwiki.Slackbuild<br />
Línea 25: De VERSION=${VERSION:-20160626a} a VERSION=${VERSION:-2017-02-19e}<br />
Línea 26: De SRCVERSION=${SRCVERSION:-2016-06-26a} a SRCVERSION=${SRCVERSION:-2017-02-19e}<br />
* Elevé mis permisos: su (e ingresé la contraseña de "root")<br />
* Ejecuté el script: sh dokuwiki.SlackBuild<br />
* Instalé el paquete: installpkg /tmp/dokuwiki-2017-02-19e-noarch-1_SBo.tgz<br />
* Agregué estas dos líneas al final de /etc/httpd/httpd.conf de acuerdo a SlackBuilds:<br />
# Dokuwiki<br />
Include /etc/httpd/extra/httpd-dokuwiki.conf<br />
<br />
Reinicié el servidor web de Apache (killall httpd seguido de httpd), pero hubo errores, por lo cual tuve que modificar /etc/httpd/mod_php.conf:<br />
Línea 6: De LoadModule php5_module lib64/httpd/modules/libphp5.so a LoadModule php7_module lib64/httpd/modules/libphp7.so<br />
<br />
Reinicié el servidor web de Apache<br />
* Abrí http://MiServidor/dokuwiki/start.php y seguí los pasos<br />
<br />
Finalmente, pude ver mi Wiki y crear mi primera entrada. Espero les sirva<br />
<br />
Saludos,<br />
<br />
F. Bobbio C.FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.com0tag:blogger.com,1999:blog-62889344087522814.post-75905411205930421852017-10-31T22:10:00.002-07:002017-11-01T08:08:21.381-07:00Sabrás Que Eres Madre/Padre Cuando...Este texto no incluye todas las razones, mas sí algunas en las que pude pensar rápidamente. Espero les gusten y se identifiquen con algunas de ellas, o tal vez todas.<br><br>
Sabrás Que Eres Madre/Padre Cuando...<br><br>
* Tu vehículo de dos puertas lo cambies por uno de cuatro (o por una camioneta)<br>
* Tu cuarto de estudios/juegos se convierta en el dormitorio de tus hijas<br>
* Los juegos de balompié más importantes sean los de tus hijas<br>
* Te pelees con los padres del equipo contrario de tus hijas<br>
* Alientes a tus hijas cuando jueguen un partido de baloncesto<br>
* Seas voluntario para entrenar al equipo de tus hijas<br>
* No sepas el nombre de los jugadores de tu equipo favorito<br>
* Sepas el nombre de todos los juguetes de tus hijas<br>
* Te sientes a ver "Dora La Exploradora" en vez de la novela<br>
* Tu calendario esté lleno de citas... de tus hijas<br>
* No puedas dormir, porque tu hija está con fiebre y al día siguiente tengas que trabajar<br>
* Comas cereal para el desayuno, sobre todo si es el cereal Cheerios u otro para niños<br>
* Juegues a tomar el té, en vez de un partido de baloncesto<br>
* Estés pendiente del celular cuando sabes que tu hija tenía una fiebre leve antes de ir a la escuela<br>
* Recuerdes el nombre de al menos cinco amigas de cada una de tus hijas<br>
* Aprendas a, y te guste, tomar sopa, porque eso le gusta a tus hijas<br>
* Sepas reconocer colores como "melón", "fucsia", "melocotón" y sus diferentes tonalidades<br>
* Te sientes a leer un libro, pero de cuentos, a tus hijas y lo disfrutes<br>
* Tu programa favorito de televisión sea "Bob Esponja" y te sepas la canción de entrada<br>
* Recuerdes, y les enseñes a tus hijas, cómo jugar trompo, bolero y hasta "canicas"<br>
* Tu vehículo tenga en algún monento al menos una silla especial para niños y sepas cómo usarla<br>
* Aprendas a cambiar pañales en menos de un minuto y lo hagas con gusto y orgullo<br>
* Tus conversaciones comiencen con "este fin de semana llevé a mis hijas a..."<br>
* Las películas que veas en el cine tengan que ser aptas para menores de 13 años<br>
* Con un dedo te controlen y no puedas decir "no" a lo que te pidan tus hijas<br><br>
Saludos,<br><br>
F. Bobbio C.FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.com0tag:blogger.com,1999:blog-62889344087522814.post-16134118452071444202017-10-02T10:46:00.002-07:002017-10-02T10:54:23.455-07:00FirmaEn un puesto de trabajo donde estuve, nos pidieron crear una firma personalizada. Muchas personas usaron textos conocidos, lo cual no me pareció original, por lo cual creé mi propia firma:<br><br>
"Es ist nicht, daß ich zu viel weiß, es ist nur, daß ich die meisten Problemen getroffen habe und von anderen gelernt habe, wie sie zu lösen. Ich bin nur ein Lösungssammler mit mittlerem Gedächtnis."
<br><br>
"It is not that I know the most, it is just that I have encountered the most problems and learned from others how to solve them. I am only a compiler of solutions with decent memory."
<br><br>
"No es que yo sepa mucho, sino que he encontrado la mayor cantidad de problemas y aprendido de otros cómo resolverlos. Soy tan sólo un compilador de soluciones con memoria decente."
<br><br>
Luego de usar mi firma por menos de un mes, me pidieron que dejara de usarla, porque, según algunas personas, no era un texto conocido y alguna otra persona se sintió ofendida por no usar lo que las demás personas estaban usando. La palabra "personalizada" significa adecuada a la persona, pero al final borré la firma y simplemente usé "Saludos, Fernando" sin nada más.<br><br>
Penosamente vivimos en un planeta donde la mediocridad es premiada y hasta exigida. Desde la niñez esperan que nos "acoplemos" y seamos seguidores, en vez de líderes. Espero nunca tener que ser mediocre y ser parte del grupo de "ovejas seguidoras".
<br><br>
Saludos,<br><br>
F. Bobbio C. FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.com0tag:blogger.com,1999:blog-62889344087522814.post-66714636127640503352017-08-25T20:46:00.001-07:002018-06-18T18:39:59.754-07:00Remmina En Slackware64-currentLlevo usando Remmina en Slackware 3 años. Remmina es un cliente de conexión remota a escritorio multiprotocolo. Su página oficial es http://www.remmina.org/wp/ y su página de descarga es https://github.com/FreeRDP/Remmina/releases bajo la sección "Downloads" --> "Source code (tar.gz)". <br />
<br />
Actualmente están en la versión 1.2.0-rcgit-19, la cual permite cambiar contraseñas a varias conexiones a la vez. Para poder compilar esta versión en Slackware-current, necesité instalar ffmpeg 3.2.4 y no ffmpeg 3.3.3, puesto que esta última versión no funcionaba con Remmina. <br />
<br />
Re-empaqueté FreeRDP 2.0.0 y usé el script de Remmina de SlackBuilds para Slackware 14.2 (https://slackbuilds.org/repository/14.2/network/remmina/?search=remmina). Tuve que renombrar el archivo .SlackBuild a Remmina.SlackBuild (cambiar la R a mayúscula) y modificar tres líneas: <br />
<br />
Línea 27: PRGNAM=remmina --> PRGNAM=Remmina <br />
Línea 28: VERSION=${VERSION:-next20160509} --> VERSION=${VERSION:-1.2.0-rcgit.19} <br />
Línea 33: TARVERSION=next --> TARVERSION=1.2.0-rcgit.19 <br />
<br />
Luego de re-empaquetar e instalar la nueva versión, al abrir Remmina se puede cambiar las contraseñas de varias conexiones primero seleccionando una conexión dentro del grupo, dando clic en las tres líneas horizontales en la esquina superior derecha y luego en "Multi password changer" <br />
<br />
Saludos, <br />
<br />
F. Bobbio C.FBobbioChttp://www.blogger.com/profile/07980018462406442543noreply@blogger.com0