Difference between pages "UEFI Install Guide" and "Package:Clamav"

(Difference between pages)
 
m (finish up ebuild)
 
Line 1: Line 1:
{{Note|This material has been integrated into the main [[Funtoo Linux Installation]] guide, so please look at that guide if you are installing Funtoo Linux. Editors: this page still contains some good content that we might want to move over there.}}
+
{{Ebuild
 
+
|Summary=Clam Anti-Virus Scanner
This tutorial will show you how to install Funtoo on a UEFI system. UEFI, also known as the [[Wikipedia:Unified Extensible Firmware Interface|Unified Extensible Firmware Interface]], is a new firmware interface that is used on some newer computers as a replacement for the traditional PC BIOS. It has an integrated boot loader, so setting up booting is different.
+
|CatPkg=app-antivirus/clamav
 
+
|Homepage=http://www.clamav.net/
This tutorial is meant to be an "overlay" over the Regular Funtoo Installation. Follow the normal installation and only follow steps in this tutorial when dealing with partitioning and configuring the boot loader (GRUB). All steps are otherwise identical to the regular installation process.
+
 
+
== What Are We Doing? ==
+
 
+
This guide will show you how to set up your UEFI system to load the GRUB boot loader, which will then load your Funtoo Linux kernel and initramfs. This is the "UEFI + GRUB" method as described on the [[Boot Methods]] page.
+
 
+
== First Steps ==
+
 
+
To install Funtoo Linux on a UEFI system, first you need to boot SysRescueCD in UEFI mode. To do this, enable UEFI in your BIOS, and if necessary disable legacy booting. After some fiddling, you should be able to boot SysRescueCD and get a black and white text menu instead of the traditional aqua/cyan-colored menu. The black and white menu indicates that you booted SysRescueCD in UEFI mode. Once you've accomplished this, you're ready to continue with your Funtoo Linux installation and partition your drive. See below for details.
+
 
+
{{fancynote|If the <tt>/sys/firmware/efi</tt> directory exists, then you have successfully booted in EFI mode and will be able to configure your Funtoo system to boot in EFI mode. If the directory doesn't exist, fix this first. It is a requirement for setting up EFI booting.}}
+
 
+
== Partitioning ==
+
 
+
To set up your partitions for UEFI booting, you will create a ~500MB FAT32 partition on <tt>/dev/sda1</tt>, and set it to type <tt>EF00</tt> using <tt>gdisk</tt>.
+
 
+
<console>
+
Command: ##i##n ↵
+
Partition Number: ##i##1 ↵
+
First sector: ##i##↵
+
Last sector: ##i##+500M ↵
+
Hex Code: ##i##EF00
+
</console>
+
 
+
This partition will serve as your Funtoo <tt>/boot</tt> filesystem as well as the partition that the UEFI firmware can read to load GRUB. Then you will set up swap on <tt>/dev/sda2</tt> and your root filesystem on <tt>/dev/sda3</tt>. To create the FAT32 filesystem, type:
+
 
+
<console>
+
# ##i##mkfs.vfat -F 32 /dev/sda1
+
</console>
+
 
+
Your <tt>/etc/fstab</tt> entry for this filesystem will also differ, and will look like this:
+
 
+
<pre>
+
/dev/sda1 /boot vfat noatime 1 2
+
</pre>
+
 
+
== Kernel ==
+
 
+
=== VFAT ===
+
 
+
Make sure you add VFAT support to your kernel if you are building it manually.
+
 
+
=== EFI Framebuffer ===
+
 
+
If you have the following option enabled in your kernel, then uvesafb and efifb will not be able to detect the framebuffer:
+
 
+
{{kernelop|title=Bus options (PCI etc.)|desc=
+
    [*] Mark VGA/VBE/EFI FB as generic system framebuffer (NEW)
+
 
}}
 
}}
 +
Clamav is an open source antivirus solution.
  
If you have that option enabled, ''you must also enable'':
+
=== Installation ===
 +
{{console|body=###i## emerge app-antivirus/clamav}}
  
{{kernelop|title=Device Drivers,Graphics support,Frame buffer Devices|desc=
+
Virus definitions need to be installed before starting the clamd service
    [*]  Simple framebuffer support
+
{{console|body=###i## freshclam}}
}}
+
  
This is the preferred method of using the EFI framebuffer, the efifb and uvesafb drivers will be used as a fallback if the above is not compatible.
+
=== Configuration ===
=== Grub method ===
+
Configuration files are located at {{c|/etc/conf.d/clamd}}, {{c|/etc/clamd.conf}}, and {{c|/etc/freshclam.conf}}
  
==== Unmask Grub 2.02_beta2 ====
+
=== Runtime ===
 +
{{console|body=###i## rc-update add clamd default
 +
###i## rc}}
  
Unmask the latest version of GRUB by placing this in your <code>/etc/portage/package.unmask</code>:
+
==== Testing ====
 +
To make sure things are installed correctly, test this harmless file:
 +
{{console|body=###i## wget -O- http://www.eicar.org/download/eicar.com.txt | clamscan -
 +
###i##rm eicar.com.txt}}
  
<pre>
+
==== Usage ====
sys-boot/grub
+
To scan single files:
</pre>
+
{{console|body=###i## clamscan /usr/bin/portageq}}
  
The 2.00 version of GRUB has known issues with UEFI booting. Using 2.02 is essential for having this boot method work reliably.
+
To scan a directory:
 
+
{{console|body=###i## clamscan -ir /var/www/localhost/htdocs/
==== Emerging GRUB ====
+
----------- SCAN SUMMARY -----------
 
+
Known viruses: 3736482
You will still use GRUB as a boot loader, but before emerging grub, you will need to enable EFI booting. To do this,
+
Engine version: 0.98.6
add the following line to <tt>/etc/portage/make.conf</tt>:
+
Scanned directories: 663
 
+
Scanned files: 6067
<pre>
+
Infected files: 0
GRUB_PLATFORMS="efi-64"
+
Total errors: 8
</pre>
+
Data scanned: 58.61 MB
 
+
Data read: 36.59 MB (ratio 1.60:1)
Then, <tt>emerge grub</tt>. You will notice <tt>efibootmgr</tt> getting pulled in as a dependency. This is expected and good.
+
Time: 42.691 sec (0 m 42 s)
 
+
==== Installing GRUB ====
+
 
+
Now, for the magic of getting everything in place for booting. You should copy your kernel and initramfs (if you have one -- you will if you are following the default install) to <tt>/boot</tt>. GRUB will boot those. But how do we get UEFI to boot GRUB? Well, we need to run the following command:
+
 
+
<console>
+
# ##i##grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sda
+
</console>
+
This command will simply install all the stuff to <tt>/boot/EFI</tt> and <tt>/boot/grub</tt> that your system needs to boot. In particular, the <tt>/boot/EFI/grub/grubx64.efi</tt> file will be created. This is the GRUB boot image that UEFI will load and start.
+
 
+
A more detailed explanation of the flags used in the above command:
+
* <code>--target=x86_64-efi</code>: Tells GRUB that we want to install it in a way that allows it to boot in UEFI
+
* <code>--efi-directory=/boot</code>: All GRUB UEFI files will be installed in ''/boot''
+
* <code>--bootloader-id="Funtoo Linux [GRUB]"</code>: This flag is not necessary for GRUB to boot. However, it allows you to change the text of the boot option in the UEFI BIOS. The stuff in the quotes can be set to anything that you would like.  
+
* <code>--recheck</code>: If a device map already exists on the disk or partition that GRUB is being installed on, it will be removed.
+
* <code>/dev/sda</code>:The device that we are installing GRUB on.
+
 
+
==== Configuring GRUB ====
+
 
+
OK, now UEFI has the GRUB image it needs to boot. But we still need to configure GRUB itself so it finds and boots your kernel and initramfs. This is done by performing the following steps. Since boot-update doesn't yet support UEFI, we will use boot-update, but then edit our <code>/boot/grub/grub.cfg</code> to support UEFI booting.  
+
 
+
First, you will need to edit <code>/etc/boot.conf</code>. Format this as you would if you were booting without UEFI. If you are not sure how this should look, below is an example of what it could look like if you are booting from an unencrypted ext4 partition:
+
 
+
{{file|name=/etc/boot.conf|desc=|body=
+
boot {
+
        generate grub
+
        default "Funtoo Linux"
+
        timeout 3
+
}
+
 
+
"Funtoo Linux" {
+
        kernel vmlinuz[-v]
+
        params += rootfstype=ext4 root=/dev/sda2
+
}
+
 
}}
 
}}
  
After you have edited your <code>/etc/boot.conf</code> file, run <code>boot-update</code>. If you check your <code>/boot/grub/grub.cfg</code> now, you should see something like this:
+
=== External Resources ===
 
+
http://www.clamav.net/doc/install.html
{{file|name=/boot/grub/grub.cfg|desc=|body=
+
{{EbuildFooter}}
set timeout=3
+
 
+
  insmod part_gpt
+
  insmod fat
+
  set root=(hostdisk//dev/sda,gpt1)
+
  search --no-floppy --fs-uuid --set 3CFD-6884
+
if loadfont /grub/unifont.pf2; then
+
  set gfxmode=text
+
  insmod gfxterm
+
  insmod vbe
+
  terminal_output gfxterm
+
fi
+
 
+
set menu_color_normal=cyan/blue
+
set menu_color_highlight=blue/cyan
+
 
+
menuentry "Funtoo Linux - vmlinuz-3.16.3" {
+
  insmod part_gpt
+
  insmod fat
+
  set root=(hostdisk//dev/sda,gpt1)
+
  search --no-floppy --fs-uuid --set 3CFD-6884
+
  linux /vmlinuz-3.16.3 video=uvesafb:1920x1080-32,mtrr:3,ywrap rootfstype=ext4 root=/dev/sda2
+
  set gfxpayload=text
+
}
+
set default=0
+
}}
+
 
+
To get your <code>/boot/grub/grub.cfg</code> to support booting with UEFI, make your <code>/boot/grub/grub.cfg</code> look like this:
+
{{file|name=/boot/grub/grub.cfg|desc=|body=
+
set timeout=3
+
 
+
  insmod part_gpt
+
  insmod fat
+
  insmod efi_gop
+
  insmod efi_uga
+
  set root=(hostdisk//dev/sda,gpt1)
+
  search --no-floppy --fs-uuid --set 3CFD-6884
+
if loadfont /grub/unifont.pf2; then
+
  set gfxmode=auto
+
  insmod gfxterm
+
  insmod vbe
+
  terminal_output gfxterm
+
fi
+
 
+
set menu_color_normal=cyan/blue
+
set menu_color_highlight=blue/cyan
+
 
+
menuentry "Funtoo Linux - vmlinuz-3.16.3" {
+
  insmod part_gpt
+
  insmod fat
+
  set root=(hostdisk//dev/sda,gpt1)
+
  search --no-floppy --fs-uuid --set 3CFD-6884
+
  linux /vmlinuz-3.16.3 video=uvesafb:1920x1080-32,mtrr:3,ywrap rootfstype=ext4 root=/dev/sda2
+
  set gfxpayload=keep
+
}
+
set default=0
+
}}
+
 
+
The lines that we have added and altered do the following:
+
* <code>insmod efi_gop</code> and <code>insmod efi_uga</code>: Both of these involve adding support for the UEFI framebuffer to GRUB.
+
* <code>set gfxmode=auto</code>: Instead of having the GRUB boot option screen being displayed at the smallest resolution possible, changing this to auto will make it fit the resolution of your display.
+
 
+
== Known Issues ==
+
*With pure UEFI boot mode, with legacy mode disabled, following error expected:
+
** video driver not supported, boot hangs, hard reboot required.
+
*Choose UEFI first, next legacy driver. It depends on motherboard vendor and efi bios version.
+
**In UEFI bios choose grub option, if your succeeded with above guide, additional menu should appear in Boot Menu, otherwise it boots into EFI shell: <code>grub:NAME of you hard drive</code>
+
* On some systems, installing the packages that are required for UEFI booting with any gcc later than a 4.x.x release may lead to a black screen after the GRUB screen. To fix this, before you begin installing any packages on your system, emerge =gcc-4.6.4-r2 and proceed with the installation as usual. Remember to switch your compiler back to the version of gcc that came with your system after you have finished installing. To do this, use <code>gcc-config 2</code>.
+
 
+
=== Done! ===
+
 
+
Remember to follow all other steps in the regular Funtoo Install Guide. Assuming you did everything correctly, your system should now boot via UEFI! We will be adding UEFI support to boot-update soon to make this process easier.
+
 
+
[[Category:HOWTO]]
+

Revision as of 10:36, February 3, 2015

app-antivirus/clamav


Source Repository:Repository:Gentoo Portage Tree

http://www.clamav.net/

Summary: Clam Anti-Virus Scanner

Use Flags

clamdtop
A Top like tool which shows what clamd is currently scanning amongst other things
metadata-analysis-api
Enables collection of file property metadata using ClamAV API for analysis by ClamAV bytecode programs.

News

Drobbins

IP Space Migration Continues

All Funtoo user containers in the 8.28 IP space will be moving into our new IP space (172.97) over the next few days. If you have DNS set up -- be sure to watch your container and update to the new IP! container.host.funtoo.org DNS will be updated after the move.
2015-08-27 by Drobbins
Drobbins

Funtoo Hosting IP Move

Funtoo user containers with IPs in the 72.18.x.x range will be gradually migrating to new IP addresses this week. If you have DNS entries for your containers, please be aware that your DNS will need to be updated.
2015-08-11 by Drobbins
Drobbins

New ARM Stages

New ARM Stages, built with a new toolchain, are now hitting mirrors. Existing ARM users should re-install using these stages (dated Aug 3, 2015 or later,) rather than upgrade using emerge.
2015-08-06 by Drobbins
More...

Clamav

Tip

We welcome improvements to this page. To edit this page, Create a Funtoo account. Then log in and then click here to edit this page. See our editing guidelines to becoming a wiki-editing pro.

Clamav is an open source antivirus solution.

Installation

# emerge app-antivirus/clamav


Virus definitions need to be installed before starting the clamd service

# freshclam


Configuration

Configuration files are located at /etc/conf.d/clamd, /etc/clamd.conf, and /etc/freshclam.conf

Runtime

# rc-update add clamd default
# rc


Testing

To make sure things are installed correctly, test this harmless file:

# wget -O- http://www.eicar.org/download/eicar.com.txt


Usage

To scan single files:

# clamscan /usr/bin/portageq


To scan a directory:

# clamscan -ir /var/www/localhost/htdocs/
----------- SCAN SUMMARY -----------
Known viruses: 3736482
Engine version: 0.98.6
Scanned directories: 663
Scanned files: 6067
Infected files: 0
Total errors: 8
Data scanned: 58.61 MB
Data read: 36.59 MB (ratio 1.60:1)
Time: 42.691 sec (0 m 42 s)


External Resources

http://www.clamav.net/doc/install.html