June 2026
M	T	W	T	F	S	S
1	2	3	4	5	6	7
8	9	10	11	12	13	14
15	16	17	18	19	20	21
22	23	24	25	26	27	28
29	30

Archive for the ‘*nix’ Category

How to rename a VM through SSH on ESXi ? |VMware Communities

Posted by jpluimers on 2021/06/28

From [WayBack] How to rename a VM through SSH on ESXi ? |VMware Communities (numbering and code highlighting mine):

Kindly find the below:

Backup the virtual machine

Power down the virtual machine

Remove the virtual machine from the vSphere host inventory

Open an SSH console session to the vSphere host

Navigate to the storage directory containing the virtual machine: For example: cd /vmfs/volumes/<datastore_name>/<original_vmname>

Rename the primary .vmdk configuration files: vmkfstools -E "<original_vmname>.vmdk" "<new_vmname>.vmdk"

Rename the .vmx configuration file: mv "original_vmname.vmx" "new_vmname.vmx"

Edit the virtual machine .vmx configuration file (Be sure to properly update the directory and file name of the .vswp swap file reference): vi "new_vmname.vmx"

Rename any remaining files in the virtual machine’s folder as needed:

Rename the .vmxf configuration file: mv "original_vmname.vmxf" "new_vmname.vmxf"

Rename the .nvram configuration file: mv "original_vmname.nvram" "new_vmname.nvram"

Rename the .vsd configuration file: mv "original_vmname.vsd" "new_vmname.vmsd"

Rename the virtual machine folder: Move up one directory level to the parent folder ( cd .. ) then rename the virtual machine directory: mv "original_directory" "new_directory"

Add the newly-named virtual machine to the host’s inventory (the newly renamed .vmx configuration file)

Power on the newly renamed virtual machine

Answer “I moved it” to the virtual machine question prompt (not “I copied it”)

Review the virtual machine and all files/folders to make sure it is named as desired and functioning properly

Note: There are other methods to allow for renaming, but this method is fairly quick and easy. It should work on all editions of vSphere from free to Enterprise Plus.

The “Answer question” prompt where you should selected “I moved it”:

->

Prompt with symlink names in the path

On a site note, I need to figure uit how to set the ESXi shell prompt to show the current path like pwd does (with symlink names in it instead of the followed symlink targets):

[root@ESXi-X9SRI-3F:~] cd /vmfs/volumes/EVO860_250GB/
[root@ESXi-X9SRI-3F:/vmfs/volumes/5c9bd516-ef1f6d4c-f1b1-0025907d9d5c] pwd
/vmfs/volumes/EVO860_250GB

The ESXi shell is based on busybox, in fact it uses the ash variety:

[root@ESXi-X9SRI-3F:/vmfs/volumes/5c9bd516-ef1f6d4c-f1b1-0025907d9d5c] `readlink -f \`which readlink\`` | grep ^BusyBox
BusyBox v1.29.3 (2018-11-02 15:37:50 PDT) multi-call binary.
BusyBox is copyrighted by many authors between 1998-2015.
[root@ESXi-X9SRI-3F:/vmfs/volumes/5c9bd516-ef1f6d4c-f1b1-0025907d9d5c] type chdir
chdir is a shell builtin

This seemed to work fine:

[root@ESXi-X9SRI-3F:/vmfs/volumes/5c9bd516-ef1f6d4c-f1b1-0025907d9d5c] PS1="[\u@\h:`pwd`] "
[root@ESXi-X9SRI-3F:/vmfs/volumes/EVO860_250GB]

But in faxt fails, as it only takes a pwd value once, and not every time the prompt is evaluated:

[root@ESXi-X9SRI-3F:/vmfs/volumes/EVO860_250GB] cd ..
[root@ESXi-X9SRI-3F:/vmfs/volumes/EVO860_250GB] pwd
/vmfs/volumes
[root@ESXi-X9SRI-3F:/vmfs/volumes/EVO860_250GB]

So I need to re-visit these links:

Identifying disks when working with VMware ESXi/ESX (1014953)
Downloading files with wget on ESXi · random writes (explaining the BusyBox version trick)
busybox prompt – Google Search
- [WayBack] shell – What are special prompt symbols for busybox’s sh support? – Unix & Linux Stack Exchange
  BusyBox has two shells, ash and hush. To see which one you have, run type chdir: ash has it as a builtin (synonymous with cd), hush doesn’t. Both have an optional prompt expansion feature. Ash’s is enabled by activating the ASH_EXPAND_PRMT feature at compile time, while hush requires FEATURE_EDITING_FANCY_PROMPT.
  
  When that feature is present, in ash the value of PS1 is expanded like a double-quoted string: $foo, $(command) and `command` constructs are expanded.
  
  Some backslash escapes are processed (in ash, after substitutions). They are a subset of bash’s.
  - \!: line history count
  - \a: bell
  - \b: backspace
  - \e, \E: escape
  - \f: form feed
  - \h: host name
  - \n: newline
  - \r: carriage return
  - \t: tab
  - \u: user name (only with FEATURE_GETUSERNAME_AND_HOMEDIR)
  - \v: vertical tab
  - \w: current directory, with ~ for the home directory (only with FEATURE_GETUSERNAME_AND_HOMEDIR)
  - \W: current directory (unabbreviated)
  - \xHH or \XHH where HH are two hexadecimal digits: a character given by its hex code
  - \[…\]: the enclosed text doesn’t count for width calculation purposes
  (If you’re looking at the source code, this happens in parse_and_put_prompt in libbb/lineedit.c.)
- [WayBack] shell – busybox ash PS1 not expanding – Unix & Linux Stack Exchange
- [WayBack] Quick Tip – How to Change ESXi SSH Prompt
- [WayBack] shell – How to display current path in command prompt in linux’s sh (not bash)? – Super User

–jeroen

Posted in *nix, *nix-tools, BusyBox, ESXi6, ESXi6.5, ESXi6.7, Power User, Virtualization, VMware, VMware ESXi | Leave a Comment »

Hopefully datendomina (@sys_adm_ama) has followed up with some cool vi tips…

Posted by jpluimers on 2021/06/28

I hope that datendomina (@sys_adm_ama) has followed up with some cool vi/vim tips.

Though I can do basic editing (far more than quit-without-saving) and know about he various mode, I still feel not proficient.

[WayBack] Jeroen Pluimers on Twitter: “LOL! Boy was I glad that after finding my way in Ed and sed on SunOS in the 1980s, I discovered vi. Still not proficient in it (and I probably never will). However, knowing some of the basics allowed me to visually edit any file on any Unix like system. That’s still gold to me.…”

It also made me discover [WayBack] ed(1) Conference (@ed1conf) | Twitter.

One important tip:

[WayBack] Kristian Köhntopp on Twitter: “vi movement Kommandos haben System. Erkenne und lerne das System. hjkl + prefix+hjkl, Marken, prefix+jump to mark und so weiter. Und bleibe von den verblödeten Plugins weg. Die braucht kein Mensch und machen vim nur langsam im Start und kompliziert.”

The original thread, which I hoped would get longer: [WayBack] Thread by @sys_adm_ama: “Ich lerne jetzt vi(m). Klingt beknackt, oder?se […]”

Ich lerne jetzt vi(m).

Klingt beknackt, oder? Aber ich hab überlegt: ich möchte effizienter werden, meinen Kram stressfreier bewältigen. Und ich finde, es bietet sich an da an Baustellen anzusetzen, die täglich relevant sind. Und vi(m) nutze ich in der Tat täglich.

1/

Aber auch wenn ich ihn nutze und über den »Hilfe, wie komm ich aus dem Editor wieder raus?!«-Witz nur sehr müde die Augen rolle gehe ich davon aus, dass ich nicht mal einen Bruchteil der Möglichkeiten ausschöpfe, die er bietet (1. Release 1976, älter als ich!). Das ist spannend.

Das ist jetzt meine Mini-Challenge, auf die ich jeden Tag eine Viertelstunde verwenden will: wenn ich eine Funktion brauche mich nicht mehr drum herum zu hacken, sondern recherchieren wie es richtig geht und das dann gefälligst auch verinnerlichen. Mal sehen, ob das so klappt

3/

In dem Zuge will ich auch wieder verstärkt (neo)mutt in Verbindung mit vim nutzen – das wäre ein wunderbares tägliches Training 😎 Mails schreiben muss man irgendwie immer.

neomutt bietet leider auch einen Eimer voll Funktionen, die ich noch nicht ordentlich nutze. Gnah.

4/

An euren Replies erkenne ich, dass das mit dem »sich die Kürzel merken« echt heikel zu sein scheint 🤔 Wie handhabt ihr das im Alltag? Einfach ein paar Basics wie :u und CTRL+r und gut ist? Ich bin neugierig. Oder nutzt ihr alle nano? (Ich glaub, dann muss ich entfolgen) 😂

Nur als kleinen Zwischenstand: nach dem Lesen eurer Antworten schließe ich, dass ich mich mit meinem Kenntnisstand nicht verstecken muss 😂 Da hat mir der virtuelle Schulterblick schon weiter geholfen.

/5

vi(m), weil ich Admin bin und dieses Tool auf jedem System und ohne X-Geraffels üblicherweise vorfinde (wenn auch bei neueren Installationen dieser absurde „visual mode“ der Default ist 😳). Auch unter (Open)Solaris, IRIX, was weiß ich.

/6

Eben hab ich das Buch von @MasteringVim aus der Packstation gezogen (extrem vielversprechend!) – und klar, ich werde berichten 😎 Ich bin sehr gespannt.

/7ed

–jeroen

Read the rest of this entry »

Posted in *nix, *nix-tools, Development, ed, Power User, Scripting, sed, sed script, Software Development, vi/vim | Leave a Comment »

After the freenode to libera transition: openSUSE:IRC list – openSUSE Wiki

Posted by jpluimers on 2021/06/18

For my link archive: [Wayback] openSUSE:IRC list – openSUSE Wiki

–jeroen

Posted in *nix, Chat, IRC, Linux, openSuSE, Power User, SocialMedia, SuSE Linux | Leave a Comment »

CloudKey ESXi Appliance – Google Search

Posted by jpluimers on 2021/06/07

Via [Archive.is] CloudKey ESXi Appliance – Google Search:

–jeroen

Posted in *nix, Cloud Key, ESXi6, ESXi6.5, ESXi6.7, Internet, Network-and-equipment, Power User, Unifi-Ubiquiti, Virtualization, VMware, VMware ESXi | Leave a Comment »

Downloading files with wget on ESXi · random writes

Posted by jpluimers on 2021/05/31

Reminder to self to check if wget on ESXi now finally supports https downloading: [WayBack] Downloading files with wget on ESXi · random writes.

In the mean time, ESXi 6.7 Update 2 and up seems to support this; so the below workaround might only be needed for ESXi 6.7 update 1 and below.

[WayBack] VMware ESXi: help downloading large ISO – Server Fault

I will likely not do this, as by now all my ESXi boxes should have been recent enough.

I will keep the article because of the BusyBox commands section below.

If so, I might finally try and write a Python wrapper for this, as I know that Python 3 on ESXi supports https, but the ESXi BusyBox does not have a built-in cURL.

Some links and notes I might need by then:

BusyBox commands

Another cool thing in the above blog post is that it shows how to dump the BusyBox built in commands.

I ran it for ESXi 6.7 with a slight trick to get the full path (using back-ticks and escaped back-ticks) and content.

Since ESXi is BusyBox based, the commands that are in /bin are not actually binaries, but each command is a symlink to the BusyBox binary. BusyBox then knows the original name of the command, so it can deduct what part to execute. This makes for a very space efficient storage scheme.

The various bits of the tricks to get the location of the BusyBox binary, so the --list parameter can be passed to it:

The which wget gives the full path of wget.
The ls -l `which wget` shows the full path of wget and the symlink target (but there is no way for ls to only show the symlink target).
The readlink -f `which wget` shows the full path of where /bin/wget points to: the BusyBox binary.

The main trick consists of backtick evalution, and knowing that ls cannot get you just the symlink target, but readlink can:

Now the back-tick escapes, because you cannot nest back-ticks:

The `readlink -f \`which wget\`` executes the BusyBox binary without arguments.
The `readlink -f \`which wget\`` --list executes the BusyBox binary with the --list parameter.

Note I do not like the cat --help (see [WayBack] How do I check busybox version (from busybox)? – Unix & Linux Stack Exchange) way of getting the BusyBox version, as that gets echoed to stderr.

This is the output:

Read the rest of this entry »

Posted in *nix, *nix-tools, cURL, ESXi6, ESXi6.5, ESXi6.7, Power User, Virtualization, VMware ESXi, wget | Leave a Comment »

“FIPS mode initialized” when you ssh out of an ESXi box

Posted by jpluimers on 2021/05/28

The once per console/shell logon output of FIPS mode initialized to stderr when you ssh out of an ESXi box seems to be something new since ESXi 6.7.

Since I hardly do this, it took a while to reproduce and track back the version where it was introduced and to realise why it is on stderr.

stderr in retrospect is logical: if you need to parse stdout of a job running across an ssh channel, you do not want it to get interfered with “side channel” output, hence stderr.

For a longer explanation see, for instance [WayBack] ssh “FIPS mode initialized” message to stderr – Why? – Unix and Linux | DSLReports Forums:

Keep in mind that “ssh” is used to transport a stream, as with “rsync”. What you put on “stdout” becomes part of the stream. That’s why this sort of informational message needs to go to “stderr”.

Parsing is hard, so bugs like [WayBack] Git fetcher fails on machine with FIPS enabled machines · Issue #3664 · inspec/inspec · GitHub got [WayBack] fixed in [WayBack] pull request like [WayBack] not parsing stderr, but checking for exitstatus.

Stock OpenSSH portable does not contain FIPS support

Finding back when and how FIPS support for OpenSSH was introduced provide a bit harder than I hoped for.

It appears that stock [WayBack] OpenSSH: Portable Release does not support FIPS. But there are patches on top of these files:

Many (most?) Linux distributions include a patched version like [WayBack] ssh.c in openssh located at /openssh-5.9p1 (git://pkgs.fedoraproject.org/openssh).

They integrate the patches like [WayBack] File openssh.spec of Package openssh – openSUSE Build Service.

Patches for instance look like [WayBack] openssh/openssh-5.3p1-fips.patch at master · gooselinux/openssh · GitHub which is more than a decade old (see the 2009 message [WayBack] rpms/openssh/devel openssh-5.3p1-fips.patch, NONE, 1.1 openssh-5.3p1-mls.patch, NONE, 1.1 openssh-5.3p1-nss-keys.patch, NONE, 1.1 openssh-5.3p1-selabel.patch, NONE, 1.1 openssh-5.3p1-skip-initial.patch, NONE, 1.1 .cvsignore, 1.24, 1.25 openssh.spec, 1.170, 1.171 sources, 1.24, 1.25 openssh-3.8.1p1-krb5-config.patch, 1.1, NONE openssh-4.7p1-audit.patch, 1.2, NONE openssh-5.1p1-mls.patch, 1.1, NONE openssh-5.1p1-skip-initial.patch, 1.1, NONE openssh-5.2p1-fips.patch, 1.6, NONE openssh-5.2p1-nss-keys.patch, 1.3, NONE openssh-5.2p1-selabel.patch, 1.2, NONE).

The patches seem to originate at the (now defunct) WayBack Index of /export/openssh of http://openssl.com/export/openssh/ .

In the end I found [WayBack] Mailing List Archive: OpenSSH FIPS 140-2 support using OpenSSL FIPS modules? having these quotes:

vanilla OpenSSH doesn’t support running OpenSSL in FIPS-140 mode. Some
downstream providers patch OpenSSH they deliver with their distributions
with changes to enable FIPS-140 mode.

[WayBack] Secure Shell and FIPS 140-2 – Managing Secure Shell Access in Oracle® Solaris 11.4 explains a bit of background of them.

ESXi 6.7

Binary searching for the version where this was introduced could have been a lot shorter if I had done a “FIPS mode initialized” “ESXi” – Google Search, resulting in for instance:

[WayBack] Solved: SSH and SCP commands stucked in “FIPS initializing” when launched from ESXi 6.7 CLI |VMware Communities
[WayBack] New ESXCLI Commands in vSphere 6.7 | Virten.net
[WayBack] XSIBackup: Restoring from remote XSITools repo in ESXi 6.7 fails
[WayBack] XSIBackup: change log since version 4.2.4

Removal of annoying "FIPS mode initialized" message from --link-srv output in ESXi 6.7

The final two links made me discover XSIBackup

They see be one of the few (only one?!) free backup solutions for the bare ESXi:

[WayBack] Free VMWare ESXi backup solution: full featured: XSIBackup Free is a VMWare ESXi data protection solution. Differential backup and block deduplication. Works in the unlicensed version of ESXi 5.1 to 6.7
[WayBack] VMWare Differential Backup | XSIBackup, XSIDiff: differential backup copy software for ESXi

In addition, they have a binary for rsync version 3.1.0: [WayBack] 33HOPS | Rsync for VMWare Backup, so lees need to go to Source: ESXi 5.1 and rsync – damiendebin.net

––jeroen

Posted in *nix, *nix-tools, ESXi6.5, ESXi6.7, Power User, ssh/sshd, Virtualization, VMware, VMware ESXi | Leave a Comment »

Wondering about the flavours of Tumbleweed ISO images

Posted by jpluimers on 2021/05/28

The Tumbleweed ISO images have many flavours, none yet covered in a comprehensive list.

I found [WayBack] Get openSUSE , which only explains part of the puzzle:

Installation: x86_64, i586, aarch64, ppc64le (for DVD/NET)
Kubic x86_64 aarch64 (for DVD)
Live x86_64 i686 (for )

I do get the processor/architectures:

x86 is in [WayBack] Index of /tumbleweed/iso/ and can have
- i586 (32-bit Intel P5 Pentium Processor and up)
- i686 (32-bit Intel P6 Pentium Processor and up)
- x86_64 (64-bit AMD/Intel/Via for AMD Opteron and higher/Intel Prescott-2M and higher/VIA Nano and higher)
ARM is in [WayBack] Index of /ports/aarch64/tumbleweed/iso/ and can have
- aarch64 (64-bit ARM for ARMv8-A and more recent)
PowerPC is in [WayBack] Index of /ports/ppc/tumbleweed/iso/ and can have
- ppc64 (64-bit PowerPC big-endian)
- ppc64le (64-bit PowerPC little-endian for POWER8 and more recent)
Z Systems is in [WayBack] Index of /ports/zsystems/tumbleweed/iso/ and can have
- s390x (64-bit Linux on z Systems)

README files:

These all have the same content:

These ISO files are published automatically once a new snapshot finished.
They haven't seen any kind of testing before publishing, so download on your
own risk and cost.

Most of the time they work, but there are times when they are broken.

So visit (and edit if you reported a bug severe enough)
http://en.opensuse.org/Portal:Tumbleweed

But I could not find a single page explaining the difference between all these (and why some of them are not prefixed with Tumbleweed):

flavour	media name	architectures: x86	architectures: ARM	architectures: PowerPC	architectures: Z Systems
openSUSE-Kubic	DVD	x86_64	aarch64
openSUSE-MicroOS	DVD	x86_64
openSUSE-Tumbleweed	DVD	i586, x86_64	aarch64	ppc64, ppc64le	s390x
openSUSE-Tumbleweed-GNOME	Live	i686, x86_64
openSUSE-Tumbleweed-KDE	Live	i686, x86_64
openSUSE-Tumbleweed	NET	i586, x86_64	aarch64	ppc64, ppc64le	s390x
openSUSE-Tumbleweed-Rescue	CD	i686, x86_64
openSUSE-Tumbleweed-XFCE	Live	i686, x86_64

I do not get why:

some have a media name (especially not DVD: all of them are iso files, right?)
the architecture lists is so different for most of them
the rescue image is not i586

I know there are also non-ISO images for instance for Raspberry Pi or pure ARM at

[WayBack] Index of /ports/armv6hl/tumbleweed/images/:
- openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-Current.raw.xz
- openSUSE-Tumbleweed-ARM-JeOS.armv6-rootfs.armv6l-Current.tar.xz
[WayBack] Index of /ports/armv7hl/tumbleweed/images/
- Too long a list to fully categorise right now; limited categorisation:
- Flavours seem to be E20/GNOME/JeOS/KDE/LXQT/X11/XFCE
- Architectures seem to be a13olinuxino/a20olinuxinolime/a20olinuxinomicro/arndale/beagle/beaglebone/chromebook/cubieboard/cubietruck/cuboxi/efi/loco/midway/nanopineo/olinuxinolime/olinuxinolime2/panda/paz00/raspberry2/sabrelite/sinovoipbpimplus/socfpgade0nanosoc/udooneo/wga// all armv7zl flavoured

Then there is

RISC-V is in [WayBack] Index of /ports/riscv/tumbleweed/images/ has an extra infix “-RISC-V-” and can have
- riscv64
- Flavours seem to be GNOME/JeOS-devel/JeOS/KDE/LXQT/X11/XFCE

I have questions on these too (:

The JeOS question got answered

When originally writing this in 2019, I could not figure out what JeOS was.

Now I know it is supposed to be pronounced as juice and is meant to have “Just enough Operating System” to get a base system working:

[Wayback] How to setup OpenSuse Tumbleweed JeOS (Just Enough Operating System) to be a fully functional linux system? : openSUSE
[Wayback] Portal:JeOS – openSUSE Wiki

openSUSE Linux JeOS (pronounced /jo͞os/, just like “juice”) is a slimmed down form factor of openSUSE Leap and Tumbleweed that is ready to run in virtualization environment and cloud. With openSUSE Linux JeOS, you can choose the right sized option to fit your needs. JeOS provides ready to deploy server images for KVM/Xen Fully Virtualized, Xen Paravirtualized, Microsoft Hyper-V, VMware, and OpenStack Cloud.

For Raspberry Pi 2, this was the image to use mid 2020 via [Wayback] HCL:Raspberry Pi2 – openSUSE Wiki and [Wayback] http://download.opensuse.org/ports/armv7hl/tumbleweed/images/:

The OpenQA shows the global build state, but not specific to Raspberry Pi models: [Wayback] https://openqa.opensuse.org/group_overview/3

–jeroen

Read the rest of this entry »

Posted in *nix, *nix-tools, Linux, openSuSE, Power User, SuSE Linux, Tumbleweed | Leave a Comment »

Need to do some catch up on “Transactional Server” from Open Suse

Posted by jpluimers on 2021/05/28

Transactional Server to me smells like Microsoft data warehouse era, so seeing it in an OpenSuSE Tumbleweed install made me wonder: huh, DBMS?

So I likely need some catch up to do do on this:

Apparently “Transactional Server” is an installation type similar to “Server”, which can upgrade without touching a running system.

So how can the system then run with the updates applied?

The answer seems to be “reboot”.

This is contrary to a lot of update changes in the past (that seems to be towards “update the running system, even allow for live kernel patching” with optional before/after snapshots.

It immediately associates with “immutability”, and likely containers.

Hopefully I’m right, but I still have questions, like:

why “snapper rollback” does not suffice not any more?
how to change from “Server” to “Transactional Server” and back?
if only / is read-only, but others like /etc , /srv, and /var are not, how does that affect transactionality?
- (you can use [WayBack] findmnt(8): find filesystem – Linux man page to list all mounted file systems)

Until I have more time, these are on my reading list:

--jeroen

Read the rest of this entry »

Posted in *nix, Linux, openSuSE, Power User, SuSE Linux, Tumbleweed | Leave a Comment »

How to Copy files between ESXi hosts using SCP Command

Posted by jpluimers on 2021/05/21

Derived the bits below from [WayBack] How to Copy files between ESXi hosts using SCP Command.

Recursive copy from a remote machine to an existing local directory:

scp -rp root@192.168.71.97://vmfs/volumes/EVO860_500GB/VM1/ /vmfs/volumes/EVO860_250GB/VM2/

After this you need to edit the .vmxf files in the VM2 directory to ensure these are not duplicates.

One thing to remember is that you need the current host to allow the SSH client in the firewall, which is disabled by default:

After enabling:

Be really careful with the -3 option to scp; it allows you to transfer from one remote machine to another remote machine, but when using keyboard-interactive, you have a high change to lock-out your accounts: SSH will try to keyboard-interactive to both hosts at the same time.

If you lock-out root, then you have to go through the local DCUI console (use ALT-F2 to go there), then reset the root account failure count using pam_tally2 --user root --reset.

So this can be bad:

scp -3 -rp root@192.168.71.97://vmfs/volumes/EVO860_500GB/VM1/ root@192.168.71.91://vmfs/volumes/EVO860_250GB/VM2/

This works, but assumes the SSH client is enabled from the first host:

scp -rp root@192.168.71.97://vmfs/volumes/EVO860_500GB/VM1/ root@192.168.71.91://vmfs/volumes/EVO860_250GB/VM2/

See these links:

On scp -3:

[WayBack] scp(1) – Linux manual page

     -3      Copies between two remote hosts are transferred through the
             local host.  Without this option the data is copied directly
             between the two remote hosts.  Note that this option disables
             the progress meter.

[WayBack] linux – scp between two remote hosts from my (third) pc – Super User
The source and target can be specified as a URI in the form scp://[user@]host[:port][/path]

so you can run:
```
scp -3 scp://user@10.3.0.1:22/path/to/file scp://user@10.3.0.2:6969/pa
```
[WayBack] ssh – Rsync equivalent to scp -3 – Stack Overflow

On root lockout:
- [WayBack] Solved: Cannot Login to WebAccess but to ESXi c… |VMware Communities
- [WayBack] Unlock root account for VMware ESXi host
On enabling and accessing DCUI:
- [WayBack] How to access DCUI/Console of ESXi using ALT+F Keys (2148363)
  After you enable the ESXi Shell in the direct console, you can use these below combination of ALT + Function keys to access the Direct Console User Interface (DCUI) of an ESXi host:
  ALT+F1 = Switches to the console.
  
  ALT+F2 = Switches to the DCUI.
  
  ALT+F11 = Returns to the banner screen.
  
  ALT+F12 = Displays the VMkernel log on the console.
- [WayBack] How to access the VMware ESXi hidden console
Enabling/disabling SSH server and client in the firewall:
- [Archive.is] vSphere Documentation Center: Using esxcli network firewall for ESXi Firewall Management
- [WayBack] Troubleshooting the ESXi Firewall

[root@ESXi-X9SRI-F:~] esxcli network firewall get
   Default Action: DROP
   Enabled: true
   Loaded: true
[root@ESXi-X9SRI-F:~] esxcli network firewall ruleset list --ruleset-id sshClient
Name       Enabled
---------  -------
sshClient    false
[root@ESXi-X9SRI-F:~] esxcli network firewall ruleset set --ruleset-id sshClient --enabled true
[root@ESXi-X9SRI-F:~] esxcli network firewall ruleset list --ruleset-id sshClient
Name       Enabled
---------  -------
sshClient     true
[root@ESXi-X9SRI-F:~] esxcli network firewall ruleset set --ruleset-id sshClient --enabled false
[root@ESXi-X9SRI-F:~] esxcli network firewall ruleset list --ruleset-id sshClient
Name       Enabled
---------  -------
sshClient    false

–jeroen

Posted in *nix, *nix-tools, ESXi6, ESXi6.5, ESXi6.7, Power User, ssh/sshd, Virtualization, VMware, VMware ESXi | Leave a Comment »

NFS server on Windows

Posted by jpluimers on 2021/05/14

One way to access files from ESXi is over NFS shares.

Out of the box, Windows Server is the only edition that provides NFS server capability, but desktop editions only have an NFS client.

There are some commercial and open sources implementations though, of which [WayBack] GitHub – winnfsd/winnfsd seems the best maintained open source one.

In case I ever need NFS server support, I need to check out these links:

[WayBack] How to Mount Windows Folder into VMware ESXi – TheITBros
[WayBack] GitHub – winnfsd/winnfsd
[WayBack] GitHub – ZeWaren/WinNFSd_edited: Standalone, simple NFS Server for Windows (unmaintained since 2012)
[WayBack] WinNFSd download | SourceForge.net (unmaintained since 2005)
[WayBack] haneWIN NFS Server for Windows – Networking Software for Windows (shareware: EUR 20-30 per license)
[WayBack] Allegro NFS for Windows (commercial USD 75 per license)
[WayBack] [How To] Add NFS server capabilities to Windows (free)

1. Download WinNFSd.exe latest version from here (2.4.0 as of now)
2. Place it in a new folder. I’m gonna use C:\winnfsd for this guide.
3. Inside that folder create a text document, name it exports.txt, open it and paste inside the paths you’d like to share (eg F:\Videos). One path per line, and start from the second line – leave first line blank! (I don’t know why but in my case the path I put in the first line didn’t get shared).
4. Create another text document in the same folder, name it nfsservice.bat, and paste in it: winnfsd.exe -id 0 0 -log off -pathFile “C:\winnfsd\exports.txt” and save it.
5. Right-click on that file, Send to -> Desktop (create shortcut).
6. Move shortcut to windows’s startup folder (C:\Users\username\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup)

That’s it, run nfsservice.bat or restart (the service will start on every boot).
[WayBack/Archive.is]

NFS Server on Windows 10? Or alternatives?
byu/williamj2543 inhomelab

–jeroen

Posted in *nix, Power User, Virtualization, VMware, VMware ESXi, Windows | Leave a Comment »

« Previous Entries

Next Entries »

	xyzzy, Relay Confere… on Sad and Useless about Competit…
	jpluimers on Windows warned me of disk full…
	jpluimers on Started making people walk me…
	jpluimers on Stack Overflow’s forum is dead…
	jpluimers on Some links on getting the most…

The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

Subscribe

Archives

Recent Comments

Recent Posts

Blog Stats

Meta title

Tag Cloud Title

Top Clicks

Top Posts

My badges

Twitter Updates

My Flickr Stream

Pages

All categories

Email Subscription

Archive for the ‘*nix’ Category

How to rename a VM through SSH on ESXi ? |VMware Communities

Prompt with symlink names in the path

Hopefully datendomina (@sys_adm_ama) has followed up with some cool vi tips…

After the freenode to libera transition: openSUSE:IRC list – openSUSE Wiki

CloudKey ESXi Appliance – Google Search

Downloading files with wget on ESXi · random writes

BusyBox commands

“FIPS mode initialized” when you ssh out of an ESXi box

Stock OpenSSH portable does not contain FIPS support

ESXi 6.7

The final two links made me discover XSIBackup

Wondering about the flavours of Tumbleweed ISO images

The JeOS question got answered

Need to do some catch up on “Transactional Server” from Open Suse

How to Copy files between ESXi hosts using SCP Command

NFS server on Windows

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

Subscribe

Archives

Recent Comments

Recent Posts

Blog Stats

Meta title

Tag Cloud Title

Top Clicks

Top Posts

My badges

My Flickr Stream

Pages

All categories

Email Subscription

Archive for the ‘*nix’ Category

Prompt with symlink names in the path

Rate this:

Share this:

Rate this:

Share this:

Rate this:

Share this:

Rate this:

Share this:

BusyBox commands

Rate this:

Share this:

Stock OpenSSH portable does not contain FIPS support

ESXi 6.7

The final two links made me discover XSIBackup

Rate this:

Share this:

The JeOS question got answered

Rate this:

Share this:

Rate this:

Share this:

Rate this:

Share this:

Rate this:

Share this: