Şöyle yaparız
gpsmon /dev/ttyS0
gpsmon /dev/ttyS0
...this tool is focused on querying the database of installed packages, and can output information in particular format(-f option plus -W action).Şöyle yaparız.
$ dpkg-query -W -f='PACK:${Package}\nARCH:${Architecture}\nSTAT:${Status}\n---\n' libc6
PACK:libc6
ARCH:amd64
STAT:install ok installed
---
PACK:libc6
ARCH:i386
STAT:install ok installed
---
-L seçeneğidpkg-query -L dia-shapes
-S seçeneği-S, --search filename-search-pattern...
Search for packages that own files corresponding to the given
pattern. Standard shell wildcard characters can be used in the
pattern, where asterisk (*) and question mark (?) will match a
slash, and blackslash (\) will be used as an escape character.
If the first character in the filename-search-pattern is none of
‘*[?/’ then it will be considered a substring match and will be
implicitly surrounded by ‘*’ (as in *filename-search-pattern*).
If the subsequent string contains any of ‘*[?\’, then it will
handled like a glob pattern, otherwise any trailing ‘/’ or ‘/.’
will be removed and a literal path lookup will be performed.
This command will not list extra files created by maintainer
scripts, nor will it list alternatives.
Şöyle yaparızdpkg-query -S .shape
zdump -v right/UTC
Çıktı olarak şunu alırız23:59:60 en son leap second'ın olduğu tarihtir.right/UTC Tue Jun 30 23:59:60 2015 UT = Tue Jun 30 23:59:60 2015 UTC isdst=0 gmtoff=0 right/UTC Wed Jul 1 00:00:00 2015 UT = Wed Jul 1 00:00:00 2015 UTC isdst=0 gmtoff=0
Thu Nov 17 19:50:43 2016 UTC
Host Machine-[Ubuntu 16.04][185.82.xx.xx]
- Container1 [10.0.8.9]
- Container2 [10.0.8.100]
- Container3 [10.0.8.101]
- Container4 [10.0.8.102]
The container history started 1979 with Unix V7 Chroot and continued, 2000 FreeBSD Jails, 2001 Linux VServer, 2004 Solaris Containers, 2005 Open VZ, 2006 Process Containers, 2008 LXC, etc.
Container technology was first introduced in 2001 through Jacques Gélinas’s Linux-VServer project. This early form of container technology underwent several redesigns such as the addition of cgroup functionality that allows the limitation and prioritization of resources (CPU, memory, block I/O, network) without the need for starting any virtual machines; and also the namespace isolation functionality that allows for the complete isolation of an application’s view of the operating environment, including process trees, networking, user IDs and mounted file systems and namespaces (source: Resource management: Linux kernel Namespaces and cgroups).
In 2008, IBM engineers added a layer of userspace tooling to make the technology more palatable to developers. In 2014, the LXC 1.0 release further addressed LXC security concerns by leveraging existing Linux technologies such as seccomp and SELinux to control and protect against DoS attacks from malicious code-breaking out of containers.
Launched in 2013, Docker was initially based on LXC and added user-friendly tools to attract developers looking for alternatives to bulky VMs. Eventually, Docker diverged from LXC by developing its own containerized architecture.
LXD has been described as the next-generation system container. It enhances system-level containerization with a REST API that can connect to the LXC libraries. Written in Go, it creates a system daemon that apps access through a UNIX socket via HTTPS further expanding the possibilities of distributed systems portability. LXD builds on top of LXC and extends its capabilities through the kernel rather than sitting independent of the OS. It acts much like a VM with a hypervisor, but without the resource overhead.
wpa_supplicant -iwlan0 -Dnl80211 -c/etc/wpa_supplicant.conf