|
|
Sponsored Content
Special Forums
News, Links, Events and Announcements
Software Releases - RSS News
kexec-loader 1.1 (Default branch)
Post 302186150 by Linux Bot on Wednesday 16th of April 2008 02:00:06 PM
04-16-2008
kexec-loader 1.1 (Default branch)
kexec-loader is a Linux-based bootloader that aims to fit on a floppy and have a grub-like interface and configuration system. It loads kernels using the kexec system calls. License: BSD License (revised) Changes:
Directives for creating devices were removed; inodes for all devices should be included with the initramfs. mkinitramfs.sh was redesigned to create a CPIO archive and to use fakeroot if the script is not being run as root. A separate debug console and /proc/kmsg monitor were added. Support was added for detecting ext2, ext3, XFS, ReiserFS, minix, FAT, and NTFS filesystem types. The list_devices() function was implemented; pressing L at the menu displays a list of all devices listed in /proc/diskstats.
More...
Directives for creating devices were removed; inodes for all devices should be included with the initramfs. mkinitramfs.sh was redesigned to create a CPIO archive and to use fakeroot if the script is not being run as root. A separate debug console and /proc/kmsg monitor were added. Support was added for detecting ext2, ext3, XFS, ReiserFS, minix, FAT, and NTFS filesystem types. The list_devices() function was implemented; pressing L at the menu displays a list of all devices listed in /proc/diskstats.
More...
|
|
LEARN ABOUT LINUX
network_namespaces
NETWORK_NAMESPACES(7) Linux Programmer's Manual NETWORK_NAMESPACES(7) NAME
network_namespaces - overview of Linux network namespaces DESCRIPTION
Network namespaces provide isolation of the system resources associated with networking: network devices, IPv4 and IPv6 protocol stacks, IP routing tables, firewall rules, the /proc/net directory (which is a symbolic link to /proc/PID/net), the /sys/class/net directory, various files under /proc/sys/net, port numbers (sockets), and so on. In addition, network namespaces isolate the UNIX domain abstract socket namespace (see unix(7)). A physical network device can live in exactly one network namespace. When a network namespace is freed (i.e., when the last process in the namespace terminates), its physical network devices are moved back to the initial network namespace (not to the parent of the process). A virtual network (veth(4)) device pair provides a pipe-like abstraction that can be used to create tunnels between network namespaces, and can be used to create a bridge to a physical network device in another namespace. When a namespace is freed, the veth(4) devices that it contains are destroyed. Use of network namespaces requires a kernel that is configured with the CONFIG_NET_NS option. SEE ALSO
nsenter(1), unshare(1), clone(2), veth(4), proc(5), sysfs(5), namespaces(7), user_namespaces(7), brctl(8), ip(8), ip-address(8), ip- link(8), ip-netns(8), iptables(8), ovs-vsctl(8) Linux 2018-02-02 NETWORK_NAMESPACES(7)