So, I've been looking into this systemd "Predictable Network Interface Names" for quite some time and got some understanding on how it works, but I can't for the love of Thor figure out the naming scheme with enpXsY, I know that it's supposed to indicate the physical location of the device, but what exactly does the X and Y mean? Which one is the physical location? What exactly does the other indicate, a bus index, perhaps? I have no idea and really want to know. I searched high and low and could find nothing explaining in detail how this naming scheme works.
I'm new to QEMU and playing around with its chardev
s. I faced the option called -chardev pty,id=id
. So I tried to create a VM with -chardev pty,id=pty0
and got the message.
char device redirected to /dev/pts/9 (label pty0)
So I tried to send some data to it:
root@super-pc:~# cat /dev/pts/9
and didn't see any output.
What is the use case of this chardev?
I am preparing for a certification and have a locally installed CentOS7 (VirtualBox) and another instance in a cloud-based service.
On the local system I have a /dev/sda
and on the cloud-based i have a /dev/vda
.
Now I am wondering what this difference exactly means? Is there a standard (documentation?) for the naming of this devices, and what the different names stand for?
Edit:
I think this document is very useful to understand the naming: https://www.kernel.org/doc/Documentation/admin-guide/devices.txt
8 block SCSI disk devices (0-15)
0 = /dev/sda First SCSI disk whole disk
16 = /dev/sdb Second SCSI disk whole disk
32 = /dev/sdc Third SCSI disk whole disk
...
240 = /dev/sdp Sixteenth SCSI disk whole disk
But I could not find some information about /dev/vda.
I've just 'inherited' a system that consists of a bunch of Linux servers (running Ubuntu, but probably not important) that uses iSCSI devices. These show up as /dev/sdb, /dev/sdc etc. when you log them in using the iscsiadm command.
However, the way that these devices have had filesystems formatted on them is not something I've done before, although I have heard of it. The filesystems (ext4 in this case) have been formatted directly on them, so a mkfs /dev/sdb command was probably issued. In the past I have always created partition(s) on a device using fdisk or parted, /dev/sdb1 etc., and formatted my filesystems on the partition.
Has anyone ever seen filesystems formatted directly on a device with no partitioning before and would you recommend it? Are there any reasons you might strongly argue against doing things that way?
Thanks,
Our Linux kernel is 2.6.31 running on an embedded MIPS processor with busybox.
The initialisation script (rcS) starts mdev with:
echo "/sbin/stbhotplug" > /proc/sys/kernel/hotplug
mdev -s
Can anyone tell me what the Linux utility mdev does?
It looks like it does auto hot plugging as the stbhotplug is a script that handle ethernet interfaces.
Also, the rootfs we have been given only has a console device i.e. /dev/console
is the only file in /dev
.
However, when the system is running, the /dev
directory is full of device files (e.g. /dev/mtd
, etc.).
The reason I ask is that occasionally we get an error whereby it is reported that /dev/ubi_ctrl
is not found or /dev/ubi1
is not found.
How or when does Linux create these devices?
Thanks.