Skip to main content


Showing posts from December, 2023

Use POSTFIX with GMAIL and Mageia Linux

  In an earlier blog post, I described how to use mail with Mageia Linux to send system messages to your Google Mail account . At the time, sendmail was the default MTA (mail transfer agent) of choice and was overkill for what was needed for a simple messaging of security status ( from msec ). It still works. By Mageia 8, postfix became the default  MTA, so it seems it would be easier to configure postfix to use the Google Mail smtp relay server. Postfix and all necessary dependencies are installed by Mageia by default. Mageia builds their RPM of postfix with specific options, which are: Smtpd multiline greeting: --%{with_TXT multiline}  Virtual Delivery Agent: --%{with_TXT VDA}  Munge bare CR: --%{with_TXT barecr}  TLS support: --%{with_TXT tls}  IPV6 support: --%{with_TXT ipv6}  CDB support: --%{with_TXT cdb}  Chroot by default: --%{with_TXT chroot} If you need other options for some other purpose, you can rebuild the source RPM (which is beyond the scope of this post). It is necess

Win4Lin appwrapper for Windows 9x/2000/XP on the Linux OS

  Win4Lin is a discontinued non-free application for Linux which allowed users to run a copy of Windows 9x, Windows 2000 or Windows XP applications on their Linux desktop. It is based on MERGE, developed circa 1985 by  Locus Computing Corporation to run DOS applications on UNIX operating systems. Locus eventually gained licensing access to the MS Windows source code. A significant benefit for MERGE is that is runs on the native UNIX filesystem, considered more stable and faster than the Microsoft FAT and VFAT filesystems. The Merge technology was owned by several companies (including IBM and SCO), but was finally discontinued in 2010, likely due to improvements in VMWare and VirtualBox as well as incompatibilities with subsequent version of MS Windows. While MERGE/Win4lin ran the complete MS Windows 9x/2000/XP OS, many users in actuality only used it for one application, so  giving individual users access to the full Windows OS could be problematic. To this end, appwrapper.exe  was d

VritualBox to the Rescue for Dual-Booting Linux and MS Windows

 VirtualBox came in handy in the past when a larger hard drive was added to a Series2 TiVo . Once again, it came in handy when installing Windows 10 on a drive already installed in a computer tower alongside Mageia9 and a few additional drives. There used to be a Win7 installation on /dev/sdb , but it crashed. MS Windows is notoriously known for assuming it is the only OS belonging on a machine and not playing well with  others. When Win7 was originally installed on this machine, it was installed on the only drive in the machine, then moved to /dev/sdb and Linux installed on /dev/sda . Of course, all the other drives could have been disconnected and Windows10 installed, but what's the fun in that? The above referenced TiVo procedure provided the inspiration. In modern versions of VirtualBox, it is possible to install the guest OS to a physical drive. The physical drive in this case is /dev/sdb , so the process is as follows: $ cd ~/VirtualBox\ VMs Create the .vmdk file that refer