Tasksel For Simple Installation

Tasksel is an installation system that is an integral part of the Debian installer (it is also included in Ubuntu). Tasksel groups software packages by tasks and offers an easy way to install all the packages needed for that task. It provides the same functionality as using conventional meta-packages.

Tasks List

Tasks are defined in .desc files found in /usr/share/tasksel. Debian derivatives can easily add tasks.

The default list available in Ubuntu can be viewed with this command-line:

gedit /usr/share/tasksel/ubuntu-tasks.desc

Installation

tasksel has been included as part of the base installation since Ubuntu 6.10 (Edgy). Tasksel is present on all versions of Ubuntu's installer (but previously was not installed as part of the base system).

Usage

To run tasksel from the command line, type:

sudo tasksel

the tasksel menu will be shown:

Already-installed tasks will have an asterisk beside their name. Select a task by scrolling down and pressing space. This will put an asterisk beside the selected task and mark it for installation. Removing an asterisk marks the task for removal. Once "ok" is selected the task installations and/or removals will take place using apt-get.

Command line arguments

You can also directly specify which task to install.

For instance, to add the Apache-MySQL-PHP stack to an existing system:

sudo tasksel install lamp-server

For complete options, see the tasksel manpage:

man tasksel

Usage (alternative)

NOTE - Calling tasks from apt-get is not documented anywhere. If you find a page that documents this, please update this page with a link.

One can alternatively install tasks with apt-get. This is the syntax:

sudo apt-get install the_name_of_the_task_you_want^

And yes, you forgot the caret (^), and yes, it is magical.

Examples:

sudo apt-get install ubuntu-desktop^ sudo apt-get install kubuntu-desktop^ sudo apt-get install lamp-server^

Task descriptions

Here are the long descriptions of a few common tasks:

• dns-server

Selects the BIND DNS server and its documentation.

• edubuntu-server

This task provides the Edubuntu classroom server.

• lamp-server

Selects a ready-made Linux/Apache/MySQL/PHP server.

• ubuntu-desktop

This task installs the Ubuntu desktop environment.

• ubuntu-live

This task provides the extra packages installed on the Ubuntu LiveCD. It is neither useful nor recommended to install this task in other environments.

source : https://help.ubuntu.com/community/Tasksel

Debian Packages Cycle : Package maintenance

Each Debian software package has a maintainer who keeps track of releases by the "upstream" authors of the software and ensures that the package is compliant with Debian Policy, coheres with the rest of the distribution, and meets the standards of quality of Debian. In relations with users and other developers, the maintainer uses the bug tracking system to follow up on bug reports and fix bugs. Typically, there is only one maintainer for a single package, but increasingly small teams of developers "co-maintain" larger and more complex packages and groups of packages.^[41]

Periodically, a package maintainer makes a release of a package by uploading it to the "incoming" directory of the Debian package archive (or an "upload queue" which periodically batch-transmits packages to the incoming directory). Package uploads are automatically processed to ensure that they are well-formed (all the requisite files are in place) and that the package is digitally signed by a Debian developer usingOpenPGP-compatible software. All Debian developers have public keys.^[42] Packages are signed to be able to reject uploads from hostile outsiders to the project, and to permit accountability in the event that a package contains a serious bug, a violation of policy, or malicious code.

If the package in incoming is found to be validly signed and well-formed, it is installed into the archive into an area called the "pool" and distributed every day to hundreds of mirrors worldwide. Initially, all package uploads accepted into the archive are only available in the "unstable" suite of packages, which contains the most up-to-date version of each package.

However, new code is also untried code, and those packages are only distributed with clear disclaimers. For packages to become candidates for the next "stable" release of the Debian distribution, they first need to be included in the "testing" suite. The requirements for a package to be included in "testing" is that it:^[43][44]

• Must have been in unstable for the appropriate length of time (the exact duration depends on the "urgency" of the upload)
• Must not have a greater number of "release-critical" bugs filed against it than the current version in testing. Release-critical bugs are those bugs which are considered serious enough that they make the package unsuitable for release.
• Must be compiled for all release architectures the package claims to support (eg: the i386-specific package gmod can be included in "testing")
• All of its dependencies must either be satisfiable by packages already in testing, or be satisfiable by the group of packages which are going to be installed at the same time.
• The operation of installing the package into testing must not break any packages currently in testing.

Thus, a release-critical bug in a package on which many packages depend, such as a shared library, may prevent many packages from entering the "testing" area, because that library is considered deficient.

Periodically, the Release Manager publishes guidelines to the developers in order to ready the release, and in accordance with them eventually decides to make a release. This occurs when all important software is reasonably up-to-date in the release-candidate suite for all architectures for which a release is planned, and when any other goals set by the Release Manager have been met. At that time, all packages in the release-candidate suite ("testing") become part of the released suite ("stable").

It is possible for a package – particularly an old, stable, and seldom-updated one – to belong to more than one suite at the same time. The suites are simply collections of pointers into the package "pool" mentioned above.

[edit]Security information and policy

The Debian Project, being free software, handles security policy through public disclosure rather than through security through obscurity. Many advisories are coordinated with other free software vendors and are published the same day a vulnerability is made public. Debian has a security audit team that reviews the archive looking for new or unfixed security bugs. Debian also participates in security standardization efforts: the Debian security advisories are compatible with the Common Vulnerabilities and Exposures (CVE) dictionary, and Debian is represented in the Board of the Open Vulnerability and Assessment Language (OVAL) project.^[45]

The Debian Project offers extensive documentation and tools to harden a Debian installation both manually and automatically.^[46] SELinux(Security-Enhanced Linux) packages are installed by default though not enabled.^[47]

Source : wikipedia.org

Bootloader Karmic Koala with Grub2

Today I have finished installing karmic koala, at menu loader many option to log in, and than I thing to remove some loader.

First I go to : /boot/grub/menu.lst , but viola... i cant that at my karmic koala. after googling I can find the problem, the last version of ubuntu use Grub v1 and for ubuntu karmic koala user Grub v2.

what is basicly different between Grub v1 and Grub v2?

• menu.lst no longer controls the menu.

• 'grub.cfg` is now in control of the menu.

• grub.cfg is automatically generated by one of the GRUB 2 scripts.

• The partition numbering is different.

• Stanzas are phrased slightly differently and can't be copied directly from a GRUB 1 menu.lst to grub.cfg. They are pretty close and easy to change, though.

So according to manual from grub v2, i can edit my loader Ubuntu Karmic with : /boot/grub/grub.cfg

### BEGIN /etc/grub.d/10_linux ###
menuentry "Ubuntu, Linux 2.6.31-19-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd0,10)
search --no-floppy --fs-uuid --set fa5dfed6-faa4-43b5-b0a9-6b3f623706f9
linux /boot/vmlinuz-2.6.31-19-generic root=UUID=fa5dfed6-faa4-43b5-b0a9-6b3f623706f9 ro quiet splash
initrd /boot/initrd.img-2.6.31-19-generic
}
menuentry "Ubuntu, Linux 2.6.31-19-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd0,10)
search --no-floppy --fs-uuid --set fa5dfed6-faa4-43b5-b0a9-6b3f623706f9
linux /boot/vmlinuz-2.6.31-19-generic root=UUID=fa5dfed6-faa4-43b5-b0a9-6b3f623706f9 ro single
initrd /boot/initrd.img-2.6.31-19-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd0,10)
search --no-floppy --fs-uuid --set fa5dfed6-faa4-43b5-b0a9-6b3f623706f9
linux /boot/vmlinuz-2.6.31-14-generic root=UUID=fa5dfed6-faa4-43b5-b0a9-6b3f623706f9 ro quiet splash
initrd /boot/initrd.img-2.6.31-14-generic
}
menuentry "Ubuntu, Linux 2.6.31-14-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd0,10)
search --no-floppy --fs-uuid --set fa5dfed6-faa4-43b5-b0a9-6b3f623706f9
linux /boot/vmlinuz-2.6.31-14-generic root=UUID=fa5dfed6-faa4-43b5-b0a9-6b3f623706f9 ro single
initrd /boot/initrd.img-2.6.31-14-generic
}
## END /etc/grub.d/10_linux ###

and change to :

### BEGIN /etc/grub.d/10_linux ###
menuentry "Ubuntu, Linux 2.6.31-19-generic" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
set quiet=1
insmod ext2
set root=(hd0,10)
search --no-floppy --fs-uuid --set fa5dfed6-faa4-43b5-b0a9-6b3f623706f9
linux /boot/vmlinuz-2.6.31-19-generic root=UUID=fa5dfed6-faa4-43b5-b0a9-6b3f623706f9 ro quiet splash
initrd /boot/initrd.img-2.6.31-19-generic
}
menuentry "Ubuntu, Linux 2.6.31-19-generic (recovery mode)" {
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
insmod ext2
set root=(hd0,10)
search --no-floppy --fs-uuid --set fa5dfed6-faa4-43b5-b0a9-6b3f623706f9
linux /boot/vmlinuz-2.6.31-19-generic root=UUID=fa5dfed6-faa4-43b5-b0a9-6b3f623706f9 ro single
initrd /boot/initrd.img-2.6.31-19-generic
}
## END /etc/grub.d/10_linux ###

After do that we can reboot our Ubuntu and just look different view while boot loader menu shown.

Squid 3.0 On Debian Lenny

There is sample configuration for Squid 3.0

http_port 192.168.1.1:3128 transparent

icp_port 3130

acl youtube dstdomain .youtube.com

no_cache allow youtube

hierarchy_stoplist cgi-bin ? localhost .js .jsp .friendster.com

acl QUERY urlpath_regex cgi-bin \? localhost .friendster.com

no_cache deny QUERY

cache_replacement_policy heap LFUDA

memory_replacement_policy heap GDSF

cache_mem 6 MB

cache_dir diskd cache0 12000 28 256

cache_dir diskd cache1 12000 28 256

cache_swap_low 98

cache_swap_high 99

cache_access_log /var/log/squid/access.log

cache_log /var/log/squid/cache.log

cache_store_log /var/log/squid/store.log

mime_table /usr/share/squid/mime.conf

pid_filename /var/run/squid.pid

client_netmask 255.255.255.0

refresh_pattern ^ftp: 10080 95% 241920 reload-into-ims override-lastmod

refresh_pattern . 180 95% 120960 reload-into-ims override-lastmod

redirect_rewrites_host_header off

acl all src 0.0.0.0/0.0.0.0

acl manager proto cache_object

acl localnet src 192.168.1.0/255.255.255.0

acl localhost src 127.0.0.1/255.255.255.255

acl SSL_ports port 443 8443 563 777

acl Safe_ports port 25 80 81 110 443 563 6667 7000 777 210 119 70 21 1025-65535

acl Safe_ports port 280 6668 6669

acl Safe_ports port 488

acl Safe_ports port 591

acl Safe_ports port 777

always_direct deny all

acl CONNECT method CONNECT

http_access allow manager localhost

http_access deny manager

http_access allow localnet

http_access allow localhost

http_access deny !Safe_ports

http_access deny CONNECT !SSL_ports

http_access deny CONNECT

#httpd_accel_host virtual

#httpd_accel_port 80

#httpd_accel_with_proxy on

#httpd_accel_uses_host_header on

http_access deny all

maximum_object_size 128 MB

maximum_object_size_in_memory 8 KB

ipcache_size 4096

ipcache_low 98

ipcache_high 99

quick_abort_min 0

quick_abort_max 0

quick_abort_pct 75

fqdncache_size 4096

shutdown_lifetime 10 seconds

cache_mgr squidku@yahoo.com

cache_effective_user proxy

cache_effective_group proxy

memory_pools off

buffered_logs off

log_icp_queries off

logfile_rotate 1

log_fqdn off

forwarded_for off

icp_hit_stale on

query_icmp on

reload_into_ims on

emulate_httpd_log off

negative_ttl 2 minutes

pipeline_prefetch on

vary_ignore_expire on

half_closed_clients off

high_page_fault_warning 2

nonhierarchical_direct on

prefer_direct off

visible_hostname squidku.net.id

unique_hostname squidku.net.id

For more configuration we can modificate the configuration above, beside implemented to Debian this configuration can apply to Ubuntu, Linuxmint and other linux distro.

For more information, just visit squid official site.