Kicou

Tech

#Tech #3dPrinting

With the prospect of being stuck at home during the Winter, and probably longer if the Covid-19 pandemic keeps progressing the way it does, this may be the opportunity to become more than just a button pusher, and maybe learn to make new things. Actual things.

I am envious of Mrs. Kicou who can operate a metal lathe or mill, and is transforming the garage into her woodworking shop, but I only use power tools when doing work around the house: I can build a kitchen, lay ceramic tile, create an opening in a wall, install hardwood floor, build a deck, a garden shed, and more. I learned it all out of necessity, because this is what home ownership does to you. But I have no particular interest in the construction trades (next year our house projects include building a thermosyphon heating system for the garage, a pergola for the deck, and a greenhouse — not sure how much of it will become reality but they are all very doable).

But if I make something I'd rather enjoy it, so I'm looking for something that would be more fun.

Read more...

#Tech #Internet

A list of software products and services I use both for personal and professional use. I self-host whenever I can, but not always.

When I host, I do so on remote Linux VMs. I don't run anything from home anymore, except for the home automation system (duh!) which runs on a Raspberry Pi.

My database engine of choice is PostgreSQL. My go-to web server/reverse proxy is Nginx. I also host my own DNS servers running ISC BIND9. I backup all my systems and data with Restic, to remote Object Storage with a local replica on a NAS device.

I am naturally drawn toward free and open-source software first, but I recognise the fact that sometimes proprietary/paid software can be more efficient. I'd rather use the software than waste all my time maintaining it.

So here is a list of the main tools and services I use on a daily basis.

Read more...

#Linux #Tech #RemoteAssistance

I have tried various remote assistance solutions and so far none had completely met our expecations.

We purchased Zoho Assist because its web-based control centre is ideal for a small team of independent Linux consultants like us, all the while having the features you'd expect from an enterprise-grade product. We were happy to purchase endpoint licence packages for paying customers, and fall back to DWS for less critical systems as well as personal machines.

While I have nothing against Zoho and am supportive of DWS, both solutions have a huge drawback in my opinion: we are relying on a third party to manage traffic to our customers, and we have no control over the data we put on their servers. Not that I believe that they are ill-intentioned, but we have to admit that we are also at the mercy of their technical and business choices: they may decide to suddenly change their pricing structure (this has happened with competing products like Logmein or Teamviewer), or they could change the product, remove features, move them to different tier, etc. and we wouldn't have much of choice, would we?

Read more...

#P2V #SCO #Unix #VMware #Tech

The client from the previous post had a successful migration of his RHEL5 and Windows 2000 physical servers to ESXi so that they could last forever. He is happy with the results.

Now he wants to do the same for a SCO Unix server.

His infrastructure is starting to look like a Computer History Museum.

#Linux #VMware #P2V #V2V #Windows2000 #Tech

A client of mine has a customer of his who runs a Windows 2000 Terminal Server because their antique ERP client will only run on Windows XP-level machines.

I already converted the ERP server last week: a Red Hat Enterprise Linux 5 server running Oracle 10g that I had to turn into CentOS because its RHN subscription had run out and I needed a newer kernel + headers for vmware-guest tools. The RHEL P2V worked well, and now it is the W2K TS's turn.

The Hypervisor I am moving this to is ESXi 6.5 and it turns out VMware Converter 6 will not migrate a Windows 2000 system: for this you need Vmware Converter 4. But Converter 4 will not migrate to ESXi higher than V4.

So how do we do?

Well, here is what I am in the middle of doing:

  • install ESXi 4 in ESXi 6 (yes, you can nest ESX installations)
  • convert the Win2k system to ESXi 4 (you can do this on the live system) with VMware Converter 4
  • DO NOT start the newly converted VM in ESXi 4!
  • fire up a Windows system that has access to both the ESXi 4 virtual OS and the ESXi 6 infrastructure
  • install VMware converter 6 onto the Windows machine, and perform a V2V offline conversion of the intermediate W2K VM to ESXi 6

I have not finished migration yet (I have to upload Win10 ISO to have my Windows system) but as crazy as it sounds, I think it should work.

Update: it actually did work. I had to install an old version of the VMware Tools that is compatible with Windows 2000 to have proper display drivers and in order for networking to work. Everything is working now.