Close without confirm
Yes, you can just write a plugin to set the view as scratch and close it. Then create a keybinding for that command. Select Tools > Developer > New Plugin... and paste:
import sublime_plugin
class CloseWithoutSavingCommand(sublime_plugin.WindowCommand):
def run(self):
view = self.window.active_view()
view.set_scratch(True)
view.close()
Sift + ctrl + p to find menu
The create a keybinding to overwrite ctrl+w
{
"keys": ["ctrl+w"],
"command": "close_without_saving",
},
https://learn.microsoft.com/en-us/troubleshoot/windows-client/networking/cannot-access-shared-folder-file-explorer
1. install smb 1.0 client.
2. enable insecure guest logins
Go to Start.
Go to Search, enter the word gpedit.msc, and then press Enter.
Go to Computer Configuration > Administrative templates > Network > Lanman Workstation.
From the right-side pane, double-click Enable insecure guest logons.
Select Enabled, and then press Enter.
1 . download update
2. put a update file to localdata store directory
3 use command below
esxcli software vib update -d "PATH TO A PATCH"
*** BELOW WORK AROUND SOLUTION STILL NOT WORKING
1. Passthrough setting not persist.
https://tinkertry.com/vmware-vsphere-esxi-7-gpu-passthrough-ui-bug-workaround
https://williamlam.com/2020/06/passthrough-of-integrated-gpu-igpu-for-standard-intel-nuc.html
Work around solution is releasing video card usage of ESXi host
by doing this work around ESXi won't display anything to monitor or local display device.
It can be turn on later.
add setting in advanced option in vm
hypervisor.cpuid.v0 = FALSE
pciPassthru0.msiEnabled = FALSE
pciPassthru.use64bitMMIO = TRUE
SSH to ESXi host, use below command to release graphic card from ESXi host.esxcli system settings kernel set -s vga -v FALSE
below command to get pci info:
lspci -p
add pci info to /etc/vmware/passthru.map # NVIDIA
#10de ffff bridge false <= commented out
# GRAPHIC Cards AMD
1002 6818 d3d0 default
1002 aab0 d3d0 default
# GRAPHIC Cards NVIDIA
10de 128b d3d0 default
10de 0e0f d3d0 default
https://www.xmodulo.com/change-default-boot-kernel-centos.html
Often times you may want to switch to a different kernel just temporarily, not permanently. Even if you do want to change the default kernel permanently, it is a good idea to try a temporary boot to a new kernel before making a permanent transition from the old kernel to a new one. That way, in case there is any kernel crash with the new kernel, you can easily fall back to the old kernel simply by rebooting.
Of course you can choose a kernel to boot interactively via GRUB menu. However, such interactive control is not always available, for example, when you are booting over SSH remotely.
Here is how to change the default boot kernel temporarily from the command line. I assume that 2
is the numeric GRUB menu entry value of a kernel that you want to boot
into during the next boot session. Replace the number with your own.
[root~]# grub2-reboot 2 [root~]# reboot
[root~]# echo "savedefault --default=2 --once" | grub --batch [root~]# reboot
Once you reboot, you will boot into a specified kernel just once. Next time you reboot, you will revert to the default kernel.
======= Change boot order permanently
https://studysection.com/blog/how-to-change-boot-order-in-ubuntu-18-04-from-grub2-to-set-windows-as-default-launch/
# sudo gedit /etc/default/grub
# sudo nano /etc/default/grub# sudo update-grub# sudo grub-set-default NUMBER
ssh -L localport:host:remoteport username@serverhost
example)
connecting remote host from local desktop
ssh -L 7777:localhost:5900 USER@REMOTE_HOST
in VNC
localhost:7777 reaches out to REMOTE_HOST:5900
| Tutorial details | |
|---|---|
| Difficulty level | Easy |
| Root privileges | No |
| Requirements | Samba server on Linux or Unix |
| Est. reading time | 2 minutes |
For example, allow access to smbd service inside LAN only via /etc/hosts.allow:
smbd : 192.168.2.
However, samba may or may not be built to support tcp wrappers.
Open your smb.conf file and add the following line to [share] to configuring Host-based share access:
[share] hosts allow = 192.168.2. 127.0.0.1
The hosts deny parameter has a higher priority than the hosts allow parameter. For instance:
[share] hosts allow = 192.168.2. 127.0.0.1 hosts deny = router.sweet.home
Open your smb.conf file and add the following line to [share]
[share] valid users = user1 user2 @group1 @group2
So we can use share-based access control enables you to grant or deny access to a share for certain users and groups:
[share] valid users = +SAMDOM\"Domain Users" # block tom invalid users = SAMDOM\tom
You can also set read and write access to set of users with the read list and write list directives.
[share]
read only = yes
write list = user1 user2 @group1 @group2
Make [sales] share read only but allow user tom and jerry to write it:
[sales]
comment = All Printers
path = /nas/fs/sales
read only = yes
write list = tom jerry
You can also configure iptables to allow or deny access to the Samba server. See the following pages:
https://serverfault.com/questions/683518/check-if-samba-only-works-locally
It is probably secure, but there is no guarantee for that.
The samba service runs as a process listening at least on the TCP ports 139 and 445. By default it accepts connections from everywhere.
Your host allow/deny parameters make only the authentication impossible on these ports, but they don't forbid the connections to your samba service, which will be so attackable by different methods (for example, DoS attack or for any possible sechole in your system).
On my opinion, the best and most simple thing which you can do, if you set up samba to listen only on your internal network. It can be done with the interfaces setting in your smb.conf. For example, set an interfaces = 192.168.1.1/24, if your internal IP is 192.168.1.1 on a /24 subnet.
As an alternative, you can change your firewall settings as well. It depends on your firewall. In case of iptables, an iptables -A INPUT -j DROP ! -s 192.168.1.0/24 -m multiport -p tcp --dports 139,445 would deny every incoming connections to your samba service which originates out of your internal network.
