Re: [arch-general] Qemu / KVM 9p rootfs not booting automatically
On 10/06/2015 08:55 AM, Martti Kühne wrote: > Kernel parameter root= appears to be missing. Unless you know for > absolutely certain that the early userspace is capable to figure out > the root partition on its own, you'd rather put it into your > bootloader's config. Thanks but I don't have any bootloader config nor need any[1]. The parameter should handle anything initramfs needs -append 'root=r rw rootfstype=9p rootflags=trans=virtio console=ttyS0' In my opinion with `root=r` it defines root, where `r` is the mount_tag: ` -virtfs local,id=r,path=/root/arch,security_model=passthrough,mount_tag=r,' the mountpoint is /root/arch (on the hostsystem) On the recovery shell I can type mount -t 9p -o trans=virtio r new_root/ and `r` does exactly what I want, it mounts `r` which is /root/arch on the host system to the `new_root` directory as a VirtFs Filesystem. So I don't know why I does not find `r` by itself: ERROR: device 'r' not found. Skipping fsck. ERROR: Unable to find root device 'r'. Do I have to 'swap' anything in here? MODULES="9p 9pnet virtio virtio_blk virtio_pci virtio_net" HOOKS="base udev block autodetect modconf filesystems keyboard fsck" [1] (see section Can 9p used as root file system?) http://blog.allenx.org/2015/07/03/virtio-9p-note/ Cheers Chris
[arch-general] Qemu / KVM 9p rootfs not booting automatically
Hi I'm trying to paravirtualize my archs. Therefore I've created a directory and fill it with `pacstrap -d /root/arch base` After that I've chrooted into `arch-chroot /root/arch /bin/bash` Inside I've changed the /etc/mkinitcpio.conf MODULES="9p 9pnet virtio virtio_blk virtio_pci virtio_net" HOOKS="base udev block autodetect modconf filesystems keyboard fsck" (Don't know if all the stuff is necessary) I've saved that file and run `mkinitcpio -p linux` I've exit chroot and start vm on the host system qemu-system-x86_64 -kernel "/root/arch/boot/vmlinuz-linux" \ -initrd "/root/arch/boot/initramfs-linux.img" \ -virtfs local,id=r,path=/root/arch,mount_tag=r,security_model=passthrough \ -device virtio-9p-pci,fsdev=r,mount_tag=r \ -enable-kvm \ -nographic \ -append 'root=r rw rootfstype=9p rootflags=trans=virtio console=ttyS0' As you can see it drops a recovery shell. But I can survive ... i think the same way the parameter append does. I don't know why this does not work automatically!? Any hints? Thanks :: running early hook [udev] starting version 226 :: running hook [udev] :: Triggering uevents... ERROR: device 'r' not found. Skipping fsck. ERROR: Unable to find root device 'r'. You are being dropped to a recovery shell Type 'exit' to try and continue booting sh: can't access tty; job control turned off [rootfs /]# mount -t 9p -o trans=virtio r new_root/ [rootfs /]# Trying to continue (this will most likely fail) ... :: mounting 'r' on real root mount: you must specify the filesystem type You are now being dropped into an emergency shell. sh: can't access tty; job control turned off [rootfs /]# Trying to continue (this will most likely fail) ... :: running cleanup hook [udev] Welcome to Arch Linux! [ OK ] Reached target Swap. [ OK ] Created slice System Slice. [ OK ] Started Forward Password Requests to Wall Directory Watch. [ OK ] Listening on Device-mapper event daemon FIFOs. [ OK ] Listening on Journal Socket (/dev/log). [ OK ] Created slice system-getty.slice. [ OK ] Reached target Encrypted Volumes. [ OK ] Listening on /dev/initctl Compatibility Named Pipe. [ OK ] Reached target Remote File Systems. [ OK ] Started Dispatch Password Requests to Console Directory Watch. [ OK ] Reached target Paths. [ OK ] Listening on Journal Socket. Mounting POSIX Message Queue File System... Starting Setup Virtual Console... Mounting Debug File System... Starting Create list of required st... nodes for the current kernel... Starting Apply Kernel Variables... Starting Journal Service... Mounting Huge Pages File System... [ OK ] Listening on udev Control Socket. Mounting Temporary Directory... [ OK ] Listening on LVM2 metadata daemon socket. Starting Remount Root and Kernel File Systems... [ OK ] Listening on udev Kernel Socket. [ OK ] Created slice system-serial\x2dgetty.slice. [ OK ] Created slice User and Session Slice. [ OK ] Reached target Slices. [ OK ] Set up automount Arbitrary Executab...ats File System Automount Point. Mounting Configuration File System... [ OK ] Mounted Huge Pages File System. [ OK ] Mounted POSIX Message Queue File System. [ OK ] Mounted Debug File System. [ OK ] Mounted Temporary Directory. [ OK ] Started Journal Service. [ OK ] Started Setup Virtual Console. [ OK ] Started Create list of required sta...ce nodes for the current kernel. [ OK ] Started Apply Kernel Variables. [ OK ] Started Remount Root and Kernel File Systems. [ OK ] Mounted Configuration File System. Starting udev Coldplug all Devices... Starting Load/Save Random Seed... Starting Create Static Device Nodes in /dev... Starting Flush Journal to Persistent Storage... [ OK ] Started Load/Save Random Seed. [ OK ] Started Flush Journal to Persistent Storage. [ OK ] Started Create Static Device Nodes in /dev. [ OK ] Reached target Local File Systems (Pre). [ OK ] Reached target Local File Systems. Starting Create Volatile Files and Directories... Starting udev Kernel Device Manager... [ OK ] Started udev Coldplug all Devices. [ OK ] Started udev Kernel Device Manager. [ OK ] Started Create Volatile Files and Directories. Starting Update UTMP about System Boot/Shutdown... [ OK ] Started Update UTMP about System Boot/Shutdown. [ OK ] Reached target System Initialization. [ OK ] Started Daily verification of password and group files. [ OK ] Started Daily man-db cache update. [ OK ] Listening on D-Bus System Message Bus Socket. [ OK ] Reached target Sockets. [ OK ] Reached target Basic System. Starting Login Service... Starting Permit User Sessions... [ OK ] Started D-Bus System Message Bus. [ OK ] Started Daily Cleanup of Temporary Directories. [ OK ] Started Daily rotation of log files. [ OK ] Reached target Timers. [ OK ] Started Permit
Re: [arch-general] Anyone using virtualbox-5.0.0 yet?
so far no problems here, i've some trouble with the vbox extension pack, updating does not work, but uninstalling and installing the new one fixed it. I run windows xp, 7, 10 without any problems and some vagrant (linux) containers. sorry walt, but what problem do you exactly have?
Re: [arch-general] Add wpa_supplicant to the Group 'Base'
thanks :) It's only ONE damn tool to make all users happy. And some of them bad, because wpa_supplicant has some vulnerabilities. But its only one tool, everything you forgot to install on the live medium can installed afterwards, but not wpa_supplicant or other missing network tools. cheers On 04/28/2015 08:10 PM, Feirlane wrote: > And wpa_supplicant is an opt-depend of netctl, but maybe it should > indicate it's needed for X802.1x as it currently only says it's for > wireless networking. > > -- > GPG Key: 8387FCC3 > > > On Tue, Apr 28, 2015 at 8:00 PM, Paladin wrote: >> On , LoneVVolf wrote: >>> Given that dhcpcd & iproute2 are already in the base group, wired networking >>> is already supported by >>> installing base. >> >> Technical note: It's not enough on all wired networks, X802.1x needs >> wpa_supplicant. I forget it almost always I reinstall one of my >> machines.. >> >> P. >> -- >> There are only two hard things in Computer Science: >> cache invalidation, naming things and off-by-one errors.
Re: [arch-general] Add wpa_supplicant to the Group 'Base'
On 04/27/2015 06:02 PM, LoneVVolf wrote: > Are 2 packages really worth it to create an additonal group or do you > propose to remove dhcpcd & iproute2 from base to this new group ? No two packages are not worth to create an additional group, but if the base group should be as minimal as possible to boot up and since there are no bootloaders in it, why not remove dhcpcd & iproute2 and put these things together in a new group called network. I know that sounds strange, but why should someone who have installed the base group be able to get connected to the world through the wired connection, but not through the wireless? I know that a wired connection is more common, but isn't it better to have a clear distinction between a functional booting system, a functional booting system including network stuff and such things. Don't get me wrong, but it is annoying to configure the whole wirless stuff and netctl just said, STOP! There is ONE missing dependency: wpa_supplicant. ONLY ONE PACKAGE I MISSED TO REACH THE WORLD :-( :-) cheers h8h
Re: [arch-general] Add wpa_supplicant to the Group 'Base'
> Right. I'm not actually arguing for wpa_supplicant's inclusion in > `base`, just pointing out that things like, `netctl` (and imho, the > variety of text editors) might not make sense either if we assume `base` > is exclusively for a bootable install. I totally agree to you Sam, if this is what base is supposed to be, a very very basic group, then I don't want to see wpa_supplicant in there, but then netctl, dhcpcd and such things should also be kicked out. Is it possible to create a new 'network' group, with netctl wpa_supplicant dhcpcd? ~# `pacstrap -i /mnt base base-devel network` and pleeeaaasss stop talking about editors. thanks. cheers
[arch-general] Add wpa_supplicant to the Group 'Base'
Hi I recently installed archlinux over the air (wifi) and after a reboot I realizied sh**t you forgot to install wpa_supplicant to get connect to the world (over wifi / wpa/wpa2) and install more packages. So I had to restart, boot to the live system, mount the whole crypt stuff, (arch-chroot) and install wpa_supplicant. In my opinion wpa_supplicant is an important tool, so is it possible to add it to the group 'base'? Cheers H8H
[arch-general] How secure is wifi-menu
hi I recently switched to a new laptop and therefore I copied all my wifi-configuration files (/etc/netctl) to the new one. Too bad that the wifi interface has changed (thanks to sysctl) and I wrote a small bash script, which should change the `interface` variable. By the way the script doesn't work very well, but I place it in the same folder with all the wifi-configuration files (/etc/netctl/) and I noticed that the tool `wifi-menu` is executing my script. I don't think this is a big vulnerability nor a bug, but if an attacker has the opportunity to place a bash file there, the system could be damaged by simple executing `wifi-menu`. Yes I know that the folder is not world / user writeable, but maybe some thoughts from the archlinux community? The reason for executing is sourceing all the files in /etc/netctl, maybe this could be improved by using eval and grep, see [1] Cheers Christian Homeyer H8H [1] https://bbs.archlinux.org/viewtopic.php?id=85726
Re: [arch-general] Smartcard troubles on Arch
Hey Mathias, have you checked the wiki[1]? What's ``dmesg`` or ``lsusb`` printing out? cheers h8h [1] https://wiki.archlinux.org/index.php/GnuPG#Smartcards On 04.08.2014 21:18, Mathias Huber wrote: > Dear Archers, > > I am trying to get my Gemalto USB Shell Token V2 (GPG-Smartcard-Reader > in a USB-Stick) to work on Arch. I've set up Udev in the way I did > successfully in Ubuntu 12.04.LTS. However, no success. > > I am still trying to figure out where the trouble lies. I can never see > the card using > gpg --card-status > But sometimes I see its fields when using > pcscs_scan. > > Possible culprits: pcscd, which sometimes gives errors, gpg's USB support? > > Has anyone had success in setting up this reader or similar smartcard > readers? Or had similar troubles? I would love to hear from you. > > Best, > Mathias >
