Installed Debian Linux to Dualboot with Windows 10, but can't boot to Debian

How to fix: After Installing Debian for dualbooting with Windows 10, just boots straight to WIN10 without a choice

Let's say you have installed Debian with Windows 10, in your UEFI system, you have all the right kernel parameters set and UEFI configs and all the partitions are all set and mounted right, windows 10 was installed before you installed Linux and you got /boot/efi at fat32/vfat FS, but your comp just boots straight to Windows 10 without a choice to boot to Debian, the reason is Windows will usually try and make its bootloader default again which means Debian isn't an option, well the easy fix as long as you got everything right on the basic install would be:


1.) Boot up Windows 10

2.) Then start a terminal console (command prompt), but run as administrator

3.) Issue this command at the console:

bcdedit /set {bootmgr} path \EFI\debian\grubx64.efi

4.) Reboot, and it should give you a choice to boot to Debian Linux or Windows 10 now, if not look to changing the boot order of operating systems installed in your computer in your computer firmware, and change it to Debian as mentioned in NOTES below.


*NOTES:
- You can reuse the EFI partition that windows 10 uses, just mount that as /boot/efi with Linux, its recommended that there be only one EFI partition per disk, so if you have 2 disks and you install windows and linux in each disk you can either reuse the efi partition that windows 10 has but make sure its atleast 300MB or bigger, you can resize the partition before installing, but dont delete and format the existing EFI windows 10 is using as it already contains necessary files Windows 10 needs or you can and this is recommended just make another efi partition on the disk linux will be installed in.
- There's also the option to change the boot order of OS'es in the BIOS/UEFI firmware of your computer/laptop, however there are many versions and kinds of firmware and each firmware can look somewhat different, so its kinda tough to give a step by step one size fixes all procedure here about that but the option to choose the order should be located in the BOOT category, all you have to do then is make sure you set Debian as the primary OS at boot, save then exit and restart.
- You could also try GrubEFIReinstall
- For Ubuntu you can use:

bcdedit /set {bootmgr} path \EFI\ubuntu\grubx64.efi 

in place of the debian command above.

/var/cache/debconf/config.dat Is Locked by Another Process: Resource Temporarily Unavailable

a Debian apt-get error lock: 

/var/cache/debconf/config.dat Is Locked by Another Process: Resource Temporarily Unavailable

 

When issuing apt-get install commands you get this error output -

/var/cache/debconf/config.dat Is Locked by Another Process: Resource Temporarily Unavailable

(for example trying to install an app like debconf with apt-get install debconf), and thus unable to use apt-get nor dpkg, to fix this problem is to kill the associated process holding a lock on that file.

Issue command in terminal:

# fuser -v /var/cache/debconf/config.dat

then grab the PID number of that output (for an example PID number 9999),
and issue the command in terminal to kill the problematic process:

# kill -9 9999

it should now work and so you can now run apt-get and dpkg.

Installed OpenSUSE Linux to Dualboot with Windows 10, but can't boot to OpenSUSE

How to fix: After Installing OpenSUSE for dualbooting with Windows 10, just boots straight to WIN10 without a choice

Let's say you have installed OpenSUSE with Windows 10, in your UEFI system, you have all the right kernel parameters set and UEFI configs and all the partitions are all set and mounted right, windows 10 was installed before you installed Linux and you got /boot/efi at fat32/vfat FS, but your comp just boots straight to Windows 10 without a choice to boot to OpenSUSE, the reason is Windows will usually try and make its bootloader default again which means openSUSE isn't an option, well the easy fix as long as you got everything right on the basic install would be:


1.) Boot up Windows 10

2.) Then start a terminal console (command prompt), but run as administrator

3.) Issue this command at the console:

bcdedit /set {bootmgr} path \EFI\opensuse\shim.efi

4.) Reboot, and it should give you a choice to boot to OpenSUSE Linux or Windows 10 now, if not look to changing the boot order of operating systems installed in your compter in your computer firmware, and change it to OpenSUSE as mentioned in NOTES below.


*NOTES:
- You can reuse the EFI partition that windows 10 uses, just mount that as /boot/efi with Linux, its recommended that there be only one EFI partition per disk, so if you have 2 disks and you install windows and linux in each disk you can either reuse the efi partition that windows 10 has but make sure its atleast 300MB or bigger, you can resize the partition before installing, but dont delete and format the existing EFI windows 10 is using as it already contains necessary files Windows 10 needs or you can and this is recommended just make another efi partition on the disk linux will be installed in.
- There's an option to use secureboot with OpenSUSE in the install, so you can use UEFI secureboot or not with it.
- There's also the option to change the boot order of OS'es in the BIOS/UEFI firmware of your computer/laptop, however there are many versions and kinds of firmware and each firmware can look somewhat different, so its kinda tough to give a step by step one size fixes all procedure here about that but the option to choose the order should be located in the BOOT category, all you have to do then is make sure you set OpenSUSE as the primary OS at boot, save then exit and restart.

Restart KDE5 plasma without logging out or rebooting

Restart KDE5 plasma without logging out or restarting the desktop environment (because of KDE5 Bugs? as great as KDE5 has been improved recently to KDE5 it still has a lot of bugs like if Krunner crashed and wont restart, want to restart KDE5 without logging out? or if you just need to restart for whatever reasons without logging or rebooting)


    Either Runs these commands in console:

    $ killall plasmashell & kstart plasmashell &

or a better way is to make a script (for example plasma_script) and make it executable and run it when you need to, with the content below:


#!/bin/bash

killall plasmashell
kstart plasmashell &

Install Asian CJK Langauge Font Character Support in OpenSUSE (in this case Japanese, Chinese, Korean)

Install Asian Langauge (CJK) Font Character Support in OpenSUSE (in this case Japanese, Chinese, Korean)

1.) The easy and heavy way to do this is to go use YAST (via GUI or ncurses):

YAST then -> System then -> Language 

In the language list you can pick whichever language you want to install character font support but in this example we focus on CJK /or Chinese, Japanese, Korean Languages.

Once you click Chinese, Japanese, Korean Languages, press ok and it will start downloading and installing the packages, this can take awhile as opensuse will download a lot of packages and still depends on your machine and net connection too

The Problem or rather issue with this is it will install everything with the including the kitchen sink approach, it will install so much packages than needed or rather what i call an overkill to support so many fonts and packages for the chosen languages, in the second option i will explain a more leaner way to install CJK language character support and break it down to each of the CJK languages

2.) This second option will be using the Command Line only no GUI, issue command in terminal:

# zypper install arphic-ukai-fonts arphic-uming-fonts ipa-ex-mincho-fonts ipa-mincho-fonts ipa-pmincho-fonts xano-mincho-fonts baekmuk-bitmap-fonts baekmuk-ttf-fonts

or with sans noto google fonts for CJK

# zypper install arphic-ukai-fonts arphic-uming-fonts ipa-ex-mincho-fonts ipa-mincho-fonts ipa-pmincho-fonts xano-mincho-fonts baekmuk-bitmap-fonts baekmuk-ttf-fonts noto-sans-cjk-fonts

In this one command it will install Chinese, Japanese, Korean Font support, below you can choose what to install for CJK support, lets you wanted to install just a leaner version for Japanese or Korean you can just install:

Japnese packages:

ipa-ex-mincho-fonts ipa-mincho-fonts ipa-pmincho-fonts xano-mincho-fonts

so issue command in terminal:

# zypper install ipa-ex-mincho-fonts ipa-mincho-fonts ipa-pmincho-fonts xano-mincho-fonts

Korean packages:

baekmuk-bitmap-fonts baekmuk-ttf-fonts

so issue command in terminal:

# zypper install baekmuk-bitmap-fonts baekmuk-ttf-fonts

Chinese: Actually the chinese packages include several language support including japanese and korean but only partial support in arphic-ukai-fonts arphic-uming-fonts, to show what I meant on what languages are exactly supported in the chinese package details:

arphic-ukai-fonts: contain both Big5 and GB2312 charsets plus some european characters.
    Currently it fully supports the following charsets:
    ISO8859-1,2,3,4,7,9,10,13,14,15 Big5 GB2312-80 Bopomofo Extensions for
    Hakka, Minnan (Unicode 4.0) and MBE variants using the Stylistic
    Alternatives (salt) feature from the OTF spec.
    Partly support is implemented for: HKSCS CNS 11643 GB18030 Japanese
    Korean
                                                                                                  
arphic-uming-fonts: contain both Big5 and GB2312 charsets plus some european characters.                                                                                                   
    Currently it fully supports the following charsets:                                                                                                                    
    ISO8859-1,2,3,4,9,10,13,14,15 Big5 GB2312-80 HKSCS 2004 Bopomofo
    Extensions for Hakka, Minnan (Unicode 4.0) and MBE variants using the
    Alternatives (aalt) feature from the OTF spec.
    Partly support is implemented for: CNS 11643 GB18030 Japanese Korean

Anyways to install issue command in terminal:

# zypper install arphic-ukai-fonts arphic-uming-fonts

Alternatively there is the Google SANS NOTO Fonts you can just install the noto-sans-cjk-fonts: which contains Chinese, Japanese, Korean Font Support from google sans noto CJK fonts, issue command in terminal:

# zypper install noto-sans-cjk-fonts

However this font package though is about 70+MB Download but it will install for support on all 3 CJK languages, you can choose to just install this or install it with the other packages mentioned above, but this by itself can support all 3 langauges, though with a bigger download size, however even if you install all the packages mentioned in this article, it still wont be as much as the gargantuan amount of packages opensuse will install with option 1 mentioned earlier with GUI and ncurses YAST way.

NOTES:

- All fonts packages mentioned here are available from openSUSE-Tumbleweed-Oss REPO or your respective opensuse version OSS REPO, so just make sure you have the OSS repository enabled in your zypper repo list

- List fonts with this command:

$ fc-list

- Rebuilds cached list of fonts (after installing fonts and it doesnt work, run this command):

$ fc-cache -fv

- You could just install everything mentioned here and rebuild the cache font list in one go with this command:

# zypper install arphic-ukai-fonts arphic-uming-fonts ipa-ex-mincho-fonts ipa-mincho-fonts ipa-pmincho-fonts xano-mincho-fonts baekmuk-bitmap-fonts baekmuk-ttf-fonts noto-sans-cjk-fonts && fc-cache -fv

Clamav Linux Anti-virus

Clamav Linux Anti-virus

First Install Clamav:

Install clamav in Archlinux:

$ sudo pacman -Sy clamav

Install clamav in Slackware from a slackbuild script from slackbuilds.org

Install clamav in Debian:

$ sudo apt-get install clamav 

Install clamav in OpenSUSE:

$ zypper install clamav 

Check the clamav version:

$ clamdscan -V




Terminal Usage:

At first you have to update the virus definitions with:

# freshclam

Then you can scan for viruses.

# clamscan OPTIONS File/Folder 

If necessary start with root permissions: sudo clamscan.

Examples:

• To check all files on the computer, displaying the name of each file:

  # clamscan -r /
  

• To check all files on the computer, but only display infected files and ring a bell when found:

  # clamscan -r --bell -i /
  

• To scan all files on the computer but only display infected files when found and have this run in the background:

  # clamscan -r -i / &
  

  Note - Display background process's status by running the jobs command.
• To check files in the all users home directories:

  # clamscan -r /home
  

• To check files in the USER home directory and move infected files to another folder:

  # clamscan -r --move=/home/USER/VIRUS /home/USER
  

• To check files in the USER home directory and remove infected files (WARNING: Files will be removed):

  # clamscan -r --remove /home/USER

• Another possibility is to move the infected files to another folder with the option --move=FOLDER, so you can later check which files of them maybe not infected or a virus.  example:  
  

  # mkdir -p home/USER/QUARANTINED && clamscan -r --move=/home/USER/QUARANTINED /home/USE

• To see more options:  
  

   # clamscan --help 

   

To put all the infected files list on a particular file: 

# clamscan -r /path-to-folder-to-scan/ | grep FOUND >> /path-to-file/clamav-log.txt

Updating Clamav:

Update clamav in command line:

# freshclam 

Clamav Common Update Problems and Troubleshooting:

1.) If you get an error saying something like:

ERROR: Can't open /var/log/clamav/freshclam.log in append mode (check permissions!).
ERROR: Problem with internal logger (UpdateLogFile = /var/log/clamav/freshclam.log).

The Fix is - Check file permissions and make clamav runnable with your user or better run it with sudo or as root

2.) If you get an error like this despite running as root or with sudo with freshclam update command:

ERROR: /var/log/clamav/freshclam.log is locked by another process
ERROR: Problem with internal logger (UpdateLogFile = /var/log/clamav/freshclam.log).

The Fix is - Delete the file ( /var/log/clamav/freshclam.log) with this command:

# rm -rf /var/log/clamav/freshclam.log

for a GUI for clamav, install clamtk (debian)

# apt-get install clamtk


Clamav Config Files: 

The Config file of clamav updater is in etc/clamav/freshclam.conf 
The Config file of the main clamav scanner is in /etc/clamav/clamd.conf