Softpanorama

Home Switchboard Unix Administration Red Hat TCP/IP Networks Neoliberalism Toxic Managers
May the source be with you, but remember the KISS principle ;-)

Ubuntu Notes

News Recommended Links Installing software via apt    
Swap file Managing Services in Ubuntu      

Ubuntu is dumped down derivative of Debian, which looks to me like an oversimplified distribution. Nothing interesting. I am surprised at the amount of lemming-like praising of Ubuntu. In reality Ubuntu desktop is much weaker then OpenSuse.

The strongest part of Ubuntu is packages repositories, the advantage that it shares with Debian.  But that's about it as for strong points.  

Ubuntu designers just try to hide the complexity and default installation "kind of work" for complete novice. But if you try to change something or install new software you need to know as much if not more then on regular distributions like OpenSuse.  BTW, by default, sshd is not installed.  That means that is is weak even as client.

GUI is actually pretty weak, especially in configuration area. Much weaker then in OpenSuse (might be even weaker then in Fedora, although I am not sure).  There is nothing comparable with YaST on Ubuntu and that fact alone makes it a weaker distribution even by any Linux distribution comparison standards.

BTW Oracle ported YaST to Red Hat and I do not understand why Ubuntu can't do the same.

Also installed applications usually are not added to GUI menu.  And Linux is about using open source applications not just browsing the Web.

Patches sometimes break the system. For example I experienced a patch that prevents system from reaching runlevel 2. Machine was a toast after the patch and this is just one example.

Cleaning Ubuntu

Runlevels in Ubuntu is a mess (that's the trait it shares with Debian)

NEWS CONTENTS

Old News

[Aug 06, 2017] uefi - CentOS Kickstart Installation - Error populating transaction

Aug 06, 2017 | superuser.com

I am trying to perform a network unattended installation for my servers. They are all UEFI systems and I have gotten them to successfully boot over the network, load grub2, and start the kickstart script for installation.

It seems to reach the point where it runs yum update , although I am not entirely sure. It downloads the CentOS image from the mirror fine and then continually tells me error populating transaction 10 times and then quits.

I've run through this multiple times with different mirrors, so I don't think this is a bad image problem.

Here is an image of the error.

Here is the compiled code for my kickstart script.

install
url --url http://mirror.umd.edu/centos/7/os/x86_64/
lang en_US.UTF-8
selinux --enforcing
keyboard us
skipx

network --bootproto dhcp --hostname r2s2.REDACTED.com --device=REDACTED
rootpw --iscrypted REDACTED
firewall --service=ssh
authconfig --useshadow --passalgo=SHA256 --kickstart
timezone --utc UTC
services --disabled gpm,sendmail,cups,pcmcia,isdn,rawdevices,hpoj,bluetooth,openibd,avahi-daemon,avahi-dnsconfd,hidd,hplip,pcscd




bootloader --location=mbr --append="nofb quiet splash=quiet" 


zerombr
clearpart --all --initlabel
autopart



text
reboot

%packages
yum
dhclient
ntp
wget
@Core
redhat-lsb-core
%end

%post --nochroot
exec < /dev/tty3 > /dev/tty3
#changing to VT 3 so that we can see whats going on....
/usr/bin/chvt 3
(
cp -va /etc/resolv.conf /mnt/sysimage/etc/resolv.conf
/usr/bin/chvt 1
) 2>&1 | tee /mnt/sysimage/root/install.postnochroot.log
%end
%post
logger "Starting anaconda r2s2.REDACTED.com postinstall"
exec < /dev/tty3 > /dev/tty3
#changing to VT 3 so that we can see whats going on....
/usr/bin/chvt 3
(



# eno1 interface
real=`ip -o link | awk '/REDACTED/ {print $2;}' | sed s/:$//`
sanitized_real=`echo $real | sed s/:/_/`


cat << EOF > /etc/sysconfig/network-scripts/ifcfg-$sanitized_real
BOOTPROTO="dhcp"
DEVICE=$real
HWADDR="REDACTED"
ONBOOT=yes
PEERDNS=yes
PEERROUTES=yes
DEFROUTE=yes
EOF



#update local time
echo "updating system time"
/usr/sbin/ntpdate -sub 0.fedora.pool.ntp.org
/usr/sbin/hwclock --systohc


rpm -Uvh https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm


# update all the base packages from the updates repository
if [ -f /usr/bin/dnf ]; then
  dnf -y update
else
  yum -t -y update
fi


# SSH keys setup snippet for Remote Execution plugin
#
# Parameters:
#
# remote_execution_ssh_keys: public keys to be put in ~/.ssh/authorized_keys
#
# remote_execution_ssh_user: user for which remote_execution_ssh_keys will be
#                            authorized
#
# remote_execution_create_user: create user if it not already existing
#
# remote_execution_effective_user_method: method to switch from ssh user to
#                                         effective user
#
# This template sets up SSH keys in any host so that as long as your public
# SSH key is in remote_execution_ssh_keys, you can SSH into a host. This only
# works in combination with Remote Execution plugin.

# The Remote Execution plugin queries smart proxies to build the
# remote_execution_ssh_keys array which is then made available to this template
# via the host's parameters. There is currently no way of supplying this
# parameter manually.
# See http://projects.theforeman.org/issues/16107 for details.









if [ -f /usr/bin/dnf ]; then
  dnf -y install puppet
else
  yum -t -y install puppet
fi

cat > /etc/puppet/puppet.conf << EOF


[main]
vardir = /var/lib/puppet
logdir = /var/log/puppet
rundir = /var/run/puppet
ssldir = \$vardir/ssl

[agent]
pluginsync      = true
report          = true
ignoreschedules = true
ca_server       = foreman.REDACTED.com
certname        = r2s2.lab.REDACTED.com
environment     = production
server          = foreman.REDACTED.com

EOF

puppet_unit=puppet
/usr/bin/systemctl list-unit-files | grep -q puppetagent && puppet_unit=puppetagent
/usr/bin/systemctl enable ${puppet_unit}
/sbin/chkconfig --level 345 puppet on

# export a custom fact called 'is_installer' to allow detection of the installer environment in Puppet modules
export FACTER_is_installer=true
# passing a non-existent tag like "no_such_tag" to the puppet agent only initializes the node
/usr/bin/puppet agent --config /etc/puppet/puppet.conf --onetime --tags no_such_tag --server foreman.REDACTED.com --no-daemonize




sync

# Inform the build system that we are done.
echo "Informing Foreman that we are built"
wget -q -O /dev/null --no-check-certificate http://foreman.REDACTED.com/unattended/built?token=REDACTED
) 2>&1 | tee /root/install.post.log
exit 0

%end

[Aug 06, 2017] Some basics of MBR vs GPT and BIOS vs UEFI - Manjaro Linux

Aug 06, 2017 | wiki.manjaro.org
Some basics of MBR v/s GPT and BIOS v/s UEFI From Manjaro Linux Jump to: navigation , search Contents [ hide ]

MBR

A master boot record (MBR) is a special type of boot sector at the very beginning of partitioned computer mass storage devices like fixed disks or removable drives intended for use with IBM PC-compatible systems and beyond. The concept of MBRs was publicly introduced in 1983 with PC DOS 2.0.

The MBR holds the information on how the logical partitions, containing file systems, are organized on that medium. Besides that, the MBR also contains executable code to function as a loader for the installed operating system!usually by passing control over to the loader's second stage, or in conjunction with each partition's volume boot record (VBR). This MBR code is usually referred to as a boot loader.

The organization of the partition table in the MBR limits the maximum addressable storage space of a disk to 2 TB (232 ◊ 512 bytes). Therefore, the MBR-based partitioning scheme is in the process of being superseded by the GUID Partition Table (GPT) scheme in new computers. A GPT can coexist with an MBR in order to provide some limited form of a backwards compatibility for older systems. [1]

GPT

GUID Partition Table (GPT) is a standard for the layout of the partition table on a physical hard disk, using globally unique identifiers (GUID). Although it forms a part of the Unified Extensible Firmware Interface (UEFI) standard (Unified EFI Forum proposed replacement for the PC BIOS), it is also used on some BIOS systems because of the limitations of master boot record (MBR) partition tables, which use 32 bits for storing logical block addresses (LBA) and size information.

MBR-based partition table schemes insert the partitioning information for (usually) four "primary" partitions in the master boot record (MBR) (which on a BIOS system is also the container for code that begins the process of booting the system). In a GPT, the first sector of the disk is reserved for a "protective MBR" such that booting a BIOS-based computer from a GPT disk is supported, but the boot loader and O/S must both be GPT-aware. Regardless of the sector size, the GPT header begins on the second logical block of the device. [2]


GPT uses modern logical block addressing (LBA) in place of the cylinder-head-sector (CHS) addressing used with MBR. Legacy MBR information is contained in LBA 0, the GPT header is in LBA 1, and the partition table itself follows. In 64-bit Windows operating systems, 16,384 bytes, or 32 sectors, are reserved for the GPT, leaving LBA 34 as the first usable sector on the disk. [3]

MBR vs. GPT

Compared with MBR disk, A GPT disk can support larger than 2 TB volumes where MBR cannot. A GPT disk can be basic or dynamic, just like an MBR disk can be basic or dynamic. GPT disks also support up to 128 partitions rather than the 4 primary partitions limited to MBR. Also, GPT keeps a backup of the partition table at the end of the disk. Furthermore, GPT disk provides greater reliability due to replication and cyclical redundancy check (CRC) protection of the partition table. [4]

The GUID partition table (GPT) disk partitioning style supports volumes up to 18 exabytes in size and up to 128 partitions per disk, compared to the master boot record (MBR) disk partitioning style, which supports volumes up to 2 terabytes in size and up to 4 primary partitions per disk (or three primary partitions, one extended partition, and unlimited logical drives). Unlike MBR partitioned disks, data critical to platform operation is located in partitions instead of unpartitioned or hidden sectors. In addition, GPT partitioned disks have redundant primary and backup partition tables for improved partition data structure integrity. [5]

BIOS

In IBM PC compatible computers, the Basic Input/Output System (BIOS), also known as System BIOS, ROM BIOS or PC BIOS, is a de facto standard defining a firmware interface. The name originated from the Basic Input/Output System used in the CP/M operating system in 1975. The BIOS software is built into the PC, and is the first software run by a PC when powered on.

The fundamental purposes of the BIOS are to initialize and test the system hardware components, and to load a bootloader or an operating system from a mass memory device. The BIOS additionally provides abstraction layer for the hardware, i.e. a consistent way for application programs and operating systems to interact with the keyboard, display, and other input/output devices. Variations in the system hardware are hidden by the BIOS from programs that use BIOS services instead of directly accessing the hardware. Modern operating systems ignore the abstraction layer provided by the BIOS and access the hardware components directly. [6]

UEFI

The Unified Extensible Firmware Interface (UEFI) (pronounced as an initialism U-E-F-I or like "unify" without the n) is a specification that defines a software interface between an operating system and platform firmware. UEFI is meant to replace the Basic Input/Output System (BIOS) firmware interface, present in all IBM PC-compatible personal computers. In practice, most UEFI images provide legacy support for BIOS services. UEFI can support remote diagnostics and repair of computers, even without another operating system.

The original EFI (Extensible Firmware Interface) specification was developed by Intel. Some of its practices and data formats mirror ones from Windows.] In 2005, UEFI deprecated EFI 1.10 (final release of EFI). The UEFI specification is managed by the Unified EFI Forum.


BIOS vs. UEFI

UEFI enables better use of bigger hard drives. Though UEFI supports the traditional master boot record (MBR) method of hard drive partitioning, it doesn't stop there. It's also capable of working with the GUID Partition Table (GPT), which is free of the limitations the MBR places on the number and size of partitions. GPT ups the maximum partition size from 2.19TB to 9.4 zettabytes.

UEFI may be faster than the BIOS. Various tweaks and optimizations in the UEFI may help your system boot more quickly it could before. For example: With UEFI you may not have to endure messages asking you to set up hardware functions (such as a RAID controller) unless your immediate input is required; and UEFI can choose to initialize only certain components. The degree to which a boot is sped up will depend on your system configuration and hardware, so you may see a significant or a minor speed increase.

Technical changes abound in UEFI. UEFI has room for more useful and usable features than could ever be crammed into the BIOS. Among these are cryptography, network authentication, support for extensions stored on non-volatile media, an integrated boot manager, and even a shell environment for running other EFI applications such as diagnostic utilities or flash updates. In addition, both the architecture and the drivers are CPU-independent, which opens the door to a wider variety of processors (including those using the ARM architecture, for example).

However, UEFI is still not widespread. Though major hardware companies have switched over almost exclusively to UEFI use, you still won't find the new firmware in use on all motherboards!or in quite the same way across the spectrum. Many older and less expensive motherboards also still use the BIOS system. [7]

MBR vs. GPT and BIOS vs. UEFI

Usually, MBR and BIOS (MBR + BIOS), and GPT and UEFI (GPT + UEFI) go hand in hand. This is compulsory for some systems (eg Windows), while optional for others (eg Linux).

http://en.wikipedia.org/wiki/GUID_Partition_Table#Operating_systems_support

http://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#DISKDEVCOMPAT

Converting from MBR to GPT

From http://www.rodsbooks.com/gdisk/mbr2gpt.html

One of the more unusual features of gdisk is its ability to read an MBR partition table or BSD disklabel and convert it to GPT format without damaging the contents of the partitions on the disk. This feature exists to enable upgrading to GPT in case the limitations of MBRs or BSD disklabels become too onerous!for instance, if you want to add more OSes to a multi-boot configuration, but the OSes you want to add require too many primary partitions to fit on an MBR disk.

Conversions from MBR to GPT works because of inefficiencies in the MBR partitioning scheme. On an MBR disk, the bulk of the first cylinder of the disk goes unused!only the first sector (which holds the MBR itself) is used. Depending on the disk's CHS geometry, this first cylinder is likely to be sufficient space to store the GPT header and partition table. Likewise, space is likely to go unused at the end of the disk because the cylinder (as seen by the BIOS and whatever tool originally partitioned the disk) will be incomplete, so the last few sectors will go unused. This leaves space for the backup GPT header and partition table. (Disks partitioned with 1 MiB alignment sometimes leave no gaps at the end of the disk, which can prevent conversion to GPT format!at least, unless you delete or resize the final partition.)

The task of converting MBR to GPT therefore becomes one of extracting the MBR data and stuffing the data into the appropriate GPT locations. Partition start and end points are straightforward to manage, with one important caveat: GPT fdisk ignores the CHS values and uses the LBA values exclusively. This means that the conversion will fail on disks that were partitioned with very old software. If the disk is over 8 GiB in size, though, GPT fdisk should find the data it needs.

Once the conversion is complete, there will be a series of gaps between partitions. Gaps at the start and end of the partition set will be related to the inefficiencies mentioned earlier that permit the conversion to work. Additional gaps before each partition that used to be a logical partition exist because of inefficiencies in the way logical partitions are allocated. These gaps are likely to be quite small (a few kilobytes), so you're unlikely to be able to put useful partitions in those spaces. You could resize your partitions with GNU Parted to remove the gaps, but the risks of such an operation outweigh the very small benefits of recovering a few kilobytes of disk space.

Switching from BIOS to UEFI

See: UEFI_-_Install_Guide#Switching_from_BIOS_to_UEFI

Note

Switching from [MBR + BIOS] to [GPT + UEFI]

Switching from BIOS to UEFI consists of 2 parts-

i. Conversion of disk from MBR to GPT. Side effects- Possible Data Loss, other OS installed on same disk may or may not boot (eg Windows)..

ii. Changing from BIOS to UEFI (and installing GRUB in UEFI mode). Side Effects- Other OS (can be both Linux and Windows) may or may not boot, with systemd you need to comment out the swap partition in /etc/fstab on a GPT partition table (if you use a swap partition).

After converting from MBR to GPT, probably your installed Manjaro wont work, so you would need to prepare beforehand what to do in such a case. (eg, chroot using a live disk and installing GRUB in UEFI way)

And Windows 8 if installed in MBR way, would need to be repaired/reinstalled in accordance to UEFI way.

Feedback

Questions, suggestions, critics? Please post here: [8]

[Jun 28, 2017] AptGet-Howto - Community Help Wiki

Notable quotes:
"... /etc/apt/sources.list ..."
"... /etc/apt/preferences ..."
"... /etc/apt/preferences ..."
"... /var/cache/apt/archives ..."
"... /var/cache/apt/archives ..."
"... not ..."
"... /etc/apt/apt.conf ..."
Jun 28, 2017 | help.ubuntu.com

The apt tool on Ubuntu 14.04 and above makes this very easy to list installed packages apt list --installed

All these commands except the search commands must be run as root or with superuser privileges, see sudo for more information.

Installation commands auto-apt

Maintenance commands

Removal commands

Search commands

For more information on apt-get, apt-cache and dpkg consult their manual pages by using the man command. These manuals will provide a wider scope of information in addition to all of the options that you can use with each program.

Typical usage example

I want to feel the wind in my hair, I want the adrenaline of speed. So let's install a racing game. But what racing games are available?

apt-cache search racing game

It gives me a lot of answers. I see a game named "torcs". Let's get some more information on this game.

apt-cache show torcs

Hmmm... it seems interesting. But is this game not already installed on my computer? And what is the available version? Which repository is it from (Universe or Main)?

apt-cache policy torcs

Ok, so now, let's install it!

apt-get install torcs

What is the command I must type in the console to launch this game? In this example, it's straightforward ("torcs"), but that's not always the case. One way of finding the name of the binary is to look at what files the package has installed in "/usr/bin". For games, the binary will be in "/usr/games". For administrative programs, it's in "/usr/sbin".

dpkg -L torcs | grep /usr/games/

The first part of the command display all files installed by the package "torcs" (try it). With the second part, we ask to only display lines containing "/usr/games/".

Hmmm, that game is cool. Maybe there are some extra tracks?

apt-cache search torcs

But I'm running out of space. I will delete the apt cache!

apt-get clean

Oh no, my mother asked me to remove all games from this computer. But I want to keep the configuration files so I can simply re-install it later.

apt-get remove torcs

If I want to also remove config files :

apt-get purge torcs

Setting up apt-get to use a http-proxy

These are three methods of using apt-get with a http-proxy.

Temporary proxy session

This is a temporary method that you can manually use each time you want to use apt-get through a http-proxy. This method is useful if you only want to temporarily use a http-proxy.

Enter this line in the terminal prior to using apt-get (substitute your details for yourproxyaddress and proxyport).

export http_proxy=http://yourproxyaddress:proxyport

If you normally use sudo to run apt-get you will need to login as root first for this to work unless you also add some explicit environment settings to /etc/sudoers, e.g.

Defaults env_keep = "http_proxy https_proxy ftp_proxy"

APT configuration file method

This method uses the apt.conf file which is found in your /etc/apt/ directory. This method is useful if you only want apt-get (and not other applications) to use a http-proxy permanently.

IconsPage/info.png On some installations there will be no apt-conf file set up. This procedure will either edit an existing apt-conf file or create a new apt-conf file.

gksudo gedit /etc/apt/apt.conf

Add this line to your /etc/apt/apt.conf file (substitute your details for yourproxyaddress and proxyport).

Acquire::http::Proxy "http://yourproxyaddress:proxyport";

Save the apt.conf file.

BASH rc method

This method adds a two lines to your .bashrc file in your $HOME directory. This method is useful if you would like apt-get and other applications for instance wget, to use a http-proxy.

gedit ~/.bashrc

Add these lines to the bottom of your ~/.bashrc file (substitute your details for yourproxyaddress and proxyport)

http_proxy=http://yourproxyaddress:proxyport
export http_proxy

Save the file. Close your terminal window and then open another terminal window or source the ~/.bashrc file:

source ~/.bashrc

Test your proxy with sudo apt-get update and whatever networking tool you desire. You can use firestarter or conky to see active connections.

If you make a mistake and go back to edit the file again, you can close the terminal and reopen it or you can source ~/.bashrc as shown above.

source ~/.bashrc

How to login a proxy user

If you need to login to the Proxy server this can be achieved in most cases by using the following layout in specifying the proxy address in http-proxy. (substitute your details for username, password, yourproxyaddress and proxyport)

http_proxy=http://username:password@yourproxyaddress:proxyport

[Jul 19, 2013] Why I left Ubuntu

Everyday Linux User

13:47 Guest Post, MIR, UBUNTU 25 comments

Introduction
As some of you may know I have recently started a new blog called "My Ubuntu Blog" (www.myubuntublog.com).


Some of you may therefore be alarmed by the title of this post as leaving Ubuntu would be a strange decision to make having committed to a whole blog on the subject.


This article is actually a guest post from Paul Smith who left a well thought out and well written comment at the bottom of the article "Is Unity Bashing a hobby?".


Having read the comment I made the decision that it was too good to languish at the bottom of the post and so I asked for Paul's permission to publish his comment as a full article on this site, which is about Linux in general.


So without further ado here is Paul Smith's article "Why I Left Ubuntu".

Why I left Ubuntu
I was a great fan of Ubuntu and Canonical. I loved the pre-Unity versions of Ubuntu. I found the last Gnome 2 version to be especially functional and polished.

When Canonical switched to Unity on 11.04, I tried it and mostly liked it. Admittedly, there were some issues but I really liked the fact that Unity did a better job of maximizing the screen real-estate available to applications than any other desktop environment I have used previously. I was hopeful that the wrinkles in Unity would be worked out in the next version and was just about ready to pay for support from Canonical for all the systems in my home, mostly as a thank you, when Ubuntu 11.10 came out.

Ubuntu 11.10 seemed to be a lot buggier overall. Unity would do weird things to my applications and sometimes make the desktop unusable, forcing me to drop down to the shell to restart X. Pulse audio on this version was a dog and would simply not work with a sound card I'd been using successfully on Linux for about 5 years. I also discovered a number of newly introduced library compatibility issues that broke some of the commercial software I needed for my job.

The final straws for me was Canonical's decision not to include snd-pcm-oss as a kernel model (which I discovered with Ubuntu 12.04), breaking ALSA's OSS emulation, as well as the inclusion of Amazon search.

I now use Scientific Linux with the Trinity desktop since I really liked KDE 3. I find that I can easily get everything to work with that distribution and it is extremely stable. At this point the only thing I miss is the old Synaptic package manager and some features of the Debian package file format.

Why Mir concerns me

I do a significant amount of technical computing. I could care less if the same OS runs on both my desktop and my phone or tablet. I need a desktop that provides a good environment for code development, modeling, as well as a limited amount of CAD. I do this work on machines at work and, to a lesser extent, on my home systems. Until my phone or tablet can support a large amount of DRAM, many cores, and can plug into a keyboard and several large monitors, I don't see myself migrating away from a desktop. Canonical's direction appears to be to water down the desktop experience in order to make it more like the phone, the same bad mistake Microsoft made with Windows 8. Developing Mir is a result of this direction. I expect to use my desktop and phone for very different tasks and could care less if they use the same OS. As an user, Mir does not appear to offer me anything of real value.

Given the direction Canonical is taking, I am very concerned that NVIDIA and/or AMD will make X and Wayland second class citizens in favor of Mir. I would love to use Nouveau and similar open source drivers; however, they're not functional enough yet, either for the software I use for my job or for recreational use with the games. Some of these games purchased from Loki Games dating back to the late 1990′s.

I am thrilled that Steam and other game developers are beginning to fully embrace Linux and would like to spend some money on these games. Assuming these games are coded to work exclusively with Mir, then buying these Linux games is not an option unless other distributions such as Scientific Linux, Fedora, or Debian also migrate to Mir. For legacy games such as the ones produced by Loki Games, I am concerned that Mir may not emulate X well enough. Full support for legacy applications that depend on X will be more of an issue if the Linux community's effort to develop X emulation is split between Wayland and Mir.

Given the direction of the rest of the Linux ecosystem to standardize on Wayland as well as the concern over OpenGL support from NVIDIA and AMD, I really wish Canonical would have worked with the Wayland team to reach their goals rather than going their own direction. In my opinion, trying to make the same OS and applications work on both big iron and small phones or tablets is just silly at this point. Given this, fragmenting the Linux ecosystem right now to save a little power on low end devices is just plain stupid. I understand Canonical's argument for the other issues, such as, the desire for a more extensible input system; however, Canonical should have been able to work through these issues with the Wayland team.

About the author
Paul Smith is an electrical engineer with 23 years of post college experience. He wrote his first program on an MOS Technology KIM 1 in 1979. Paul has been using Linux since 1998.
Summary
I would like to thank Paul for allowing me to post this article and I hope you enjoyed it as much as I did.


If you think that you have an article worth posting on this site please feel free to get in touch at everydaylinuxuser@gmail.com.

504957 sysv initscripts not started on boot

Binary package hint: upstart

On boot, upstart isn't starting the legacy sysv initscripts. The `runlevel` command returns 'unknown'.

I have a workaround:

axa@artemis:~$ runlevel
unknown

axa@artemis:~$ sudo telinit 2

axa@artemis:~$ runlevel

N 2

The debug information collected with ubuntu-bug is from before switching runlevels.

ProblemType: Bug
Architecture: i386
Date: Fri Jan 8 21:21:57 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /sbin/init
Package: upstart 0.6.3-11
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
SourcePackage: upstart
Uname: Linux 2.6.31-16-generic i686

Binary package hint: upstart

On boot, upstart isn't starting the legacy sysv initscripts. The `runlevel` command returns 'unknown'.

I have a workaround:
axa@artemis:~$ runlevel
unknown
axa@artemis:~$ sudo telinit 2
axa@artemis:~$ runlevel
N 2

The debug information collected with ubuntu-bug is from before switching runlevels.

ProblemType: Bug
Architecture: i386
Date: Fri Jan 8 21:21:57 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /sbin/init
Package: upstart 0.6.3-11
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
SourcePackage: upstart
Uname: Linux 2.6.31-16-generic i686

[Jan 10, 2010] By default sshd is not installed on Ubuntu. sshd can be installed using Synaptic

[Jan 10, 2010] SSHD can be used as remote instead of VNC

[Dec 13, 2009] VFSFTPD has option force_dot_files=YES

[Dec 13, 2009] Synaptic is OK tool for adding and removing packages.

[Dec 13, 2009] Apparix augmenting the command-line with directory bookmarks

[Dec 12, 2009] FTE editor package is available on Ubuntu

[Dec 12, 2009] MC on Ubuntu comes with wrong setting -- external editor (nano). To change go to Options and set internal editor

[Dec 12, 2009] Strange RC settings -- no K files

:/home/serg# cd /etc/init.d
:/etc/init.d# ls
acpid           dns-clean          procps             stop-bootlogd
acpi-support    gdm                pulseaudio         stop-bootlogd-single
alsa-utils      grub-common        rc                 udev
anacron         hal                rc.local           udev-finish
apparmor        halt               rcS                udevmonitor
apport          hwclock            README             udevtrigger
atd             hwclock-save       reboot             ufw
avahi-daemon    kerneloops         rsync              umountfs
binfmt-support  keyboard-setup     rsyslog            umountnfs.sh
bluetooth       killprocs          rsyslog-kmsg       umountroot
bootlogd        laptop-mode        saned              unattended-upgrades
brltty          module-init-tools  screen-cleanup     urandom
console-setup   networking         sendsigs           usplash
cron            network-manager    single             wpa-ifupdown
cups            ondemand           skeleton           x11-common
dbus            pcmciautils        speech-dispatcher
dmesg           pppd-dns           sreadahead

:/etc/init.d# cd /etc/rc1.d

:/etc/rc1.d# ls
K15pulseaudio    K20saned              K99laptop-mode  S70pppd-dns
K20acpi-support  K20speech-dispatcher  README          S90single
K20kerneloops    K74bluetooth          S30killprocs
K20rsync         K80cups               S70dns-clean

:/etc/rc1.d# cd /etc/rc2*

:/etc/rc2.d# ls
README                S50cups        S70dns-clean       S99grub-common
S20kerneloops         S50pulseaudio  S70pppd-dns        S99laptop-mode
S20speech-dispatcher  S50rsync       S90binfmt-support  S99ondemand
S25bluetooth          S50saned       S99acpi-support    S99rc.local
:/etc/rc2.d# cd /etc/rc3*

:/etc/rc3.d# ls
README                S50cups        S70dns-clean       S99grub-common
S20kerneloops         S50pulseaudio  S70pppd-dns        S99laptop-mode
S20speech-dispatcher  S50rsync       S90binfmt-support  S99ondemand
S25bluetooth          S50saned       S99acpi-support    S99rc.local
:/etc/rc3.d# cd /etc/rc5*

:/etc/rc5.d# ls
README                S50cups        S70dns-clean       S99grub-common
S20kerneloops         S50pulseaudio  S70pppd-dns        S99laptop-mode
S20speech-dispatcher  S50rsync       S90binfmt-support  S99ondemand
S25bluetooth          S50saned       S99acpi-support    S99rc.local

Hardening the Linux server

Servers -- whether used for testing or production -- are primary targets for attackers. By taking the proper steps, you can turn a vulnerable box into a hardened server and help thwart outside attackers. Learn how to secure SSH sessions, configure firewall rules, and set up intrusion detection to alert you to any possible attacks on your GNU/Linux server. Once you've gained a solid foundation in the basics of securing your server, you can build on this knowledge to further harden your systems.



Etc

Society

Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy

Quotes

War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotesSomerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose BierceBernard Shaw : Mark Twain Quotes

Bulletin:

Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law

History:

Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOSProgramming Languages History : PL/1 : Simula 67 : C : History of GCC developmentScripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-MonthHow to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Haterís Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least


Copyright © 1996-2018 by Dr. Nikolai Bezroukov. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) in the author free time and without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

 

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.

This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...

You can use PayPal to make a contribution, supporting development of this site and speed up access. In case softpanorama.org is down you can use the at softpanorama.info

Disclaimer:

The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.

The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Last modified: December 26, 2017