From stayvoid at gmail.com Tue Sep 11 12:42:20 2012 From: stayvoid at gmail.com (Stayvoid) Date: Tue, 11 Sep 2012 16:42:20 +0400 Subject: [Assist] How to resolve conflicts? Message-ID: Hi, I'm not very knowledgeable about pacman. How to resolve these conflicts? # pacman -S util-linux resolving dependencies... looking for inter-conflicts... Targets (1): util-linux-2.21.2-5 Total Installed Size: 7.59 MiB Net Upgrade Size: 0.07 MiB checking package integrity... loading package files... checking for file conflicts... util-linux: /bin/login exists in filesystem util-linux: /etc/pam.d/chfn exists in filesystem util-linux: /etc/pam.d/chsh exists in filesystem util-linux: /etc/pam.d/login exists in filesystem util-linux: /usr/bin/chfn exists in filesystem util-linux: /usr/bin/chsh exists in filesystem util-linux: /usr/bin/newgrp exists in filesystem util-linux: /usr/sbin/vigr exists in filesystem util-linux: /usr/sbin/vipw exists in filesystem util-linux: /usr/share/man/man1/chfn.1.gz exists in filesystem util-linux: /usr/share/man/man1/chsh.1.gz exists in filesystem util-linux: /usr/share/man/man1/login.1.gz exists in filesystem util-linux: /usr/share/man/man1/newgrp.1.gz exists in filesystem util-linux: /usr/share/man/man8/vigr.8.gz exists in filesystem util-linux: /usr/share/man/man8/vipw.8.gz exists in filesystem Errors occurred, no packages were upgraded. I'm still [1] running from this stick (mounted rw). That's why I don't really want to upgrade lots of packages etc. [1] https://lists.parabolagnulinux.org/pipermail/assist/2012-August/000013.html Thanks From mtjm at mtjm.eu Tue Sep 11 12:45:02 2012 From: mtjm at mtjm.eu (=?utf-8?Q?Micha=C5=82_Mas=C5=82owski?=) Date: Tue, 11 Sep 2012 14:45:02 +0200 Subject: [Assist] How to resolve conflicts? In-Reply-To: (stayvoid@gmail.com's message of "Tue, 11 Sep 2012 16:42:20 +0400") References: Message-ID: <877gs03f01.fsf@mtjm.eu> > How to resolve these conflicts? Update all packages or ask someone to make an updated tarball. Partial upgrades are unsupported and sometimes lead to unbootable systems. We usually don't specify versioned dependencies. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: From stayvoid at gmail.com Wed Sep 12 15:05:23 2012 From: stayvoid at gmail.com (Stayvoid) Date: Wed, 12 Sep 2012 19:05:23 +0400 Subject: [Assist] How to resolve conflicts? In-Reply-To: <877gs03f01.fsf@mtjm.eu> References: <877gs03f01.fsf@mtjm.eu> Message-ID: > Update all packages How to do it? Here is my attempt: # pacman -Syu --noconfirm :: Synchronizing package databases... libre is up to date core is up to date extra is up to date community is up to date :: Starting full system upgrade... :: Replace libusb with core/libusbx? [Y/n] :: Replace procps with core/procps-ng? [Y/n] warning: cannot replace procps by procps-ng :: Replace procps with community/procps-ng? [Y/n] :: Replace udev with core/systemd? [Y/n] :: Replace udev with core/systemd-tools? [Y/n] resolving dependencies... warning: dependency cycle detected: warning: dbus-core will be installed before its systemd dependency warning: dependency cycle detected: warning: systemd-tools will be installed before its systemd dependency looking for inter-conflicts... warning: removing 'systemd-tools' from target list because it conflicts with 'systemd' Targets (86): acl-2.2.51-2 archlinux-keyring-20120812-1 attr-2.4.46-2 bash-4.2.037-1 bzip2-1.0.6-4 ca-certificates-20120623-1 coreutils-8.17-3 cracklib-2.8.19-1 cronie-1.4.8-3 cryptsetup-1.5.0-2 curl-7.27.0-1 db-5.3.21-1 dbus-core-1.6.4-1 device-mapper-2.02.97-1 dhcpcd-5.6.0-1 e2fsprogs-1.42.5-1 filesystem-2012.8-1.2 gc-7.2.d-1 gcc-libs-4.7.1-6 glib2-2.32.4-1 glibc-2.16.0-4 gmp-5.0.5-1 grep-2.14-1 gzip-1.5-1 hwids-20120831-1 iana-etc-2.30-3 inetutils-1.9.1-4 initscripts-2012.09.1-1 iproute2-3.5.1-1 iputils-20101006-4 kbd-1.15.3-3 keyutils-1.5.5-3 kmod-9-2 krb5-1.10.3-1 ldns-1.6.13-1 libcap-2.22-3 libedit-20120601_3.0-1 libldap-2.4.32-1 libnl-3.2.11-1 libpcap-1.3.0-1 libpipeline-1.2.1-1 libssh2-1.4.2-1 libusb-1.0.9-1 [removal] libusbx-1.0.12-2 licenses-libre-2.9-1 linux-libre-3.5.2-1.1 linux-libre-api-headers-3.5.1-1 logrotate-3.8.2-1 lvm2-2.02.97-1 man-db-2.6.2-1 man-pages-3.42-1 mdadm-3.2.5-2 mkinitcpio-0.10-1 mkinitcpio-busybox-1.20.1-1 openssh-6.1p1-1 openssl-1.0.1.c-1 pacman-4.0.3-3 pacman-mirrorlist-libre-20120522-1 pam-1.1.5-4 pambase-20120701-1 parabola-keyring-20120816-1 pciutils-3.1.10-1 pcre-8.31-1 perl-5.16.1-1 pinentry-0.8.1-4 procps-3.2.8-5 [removal] procps-ng-3.3.3-3 psmisc-22.19-1 readline-6.2.004-1 run-parts-4.3.2-1 shadow-4.1.5.1-1 sudo-1.8.5.p3-1 sysfsutils-2.1.0-8 systemd-189-4 sysvinit-2.88-7 sysvinit-tools-2.88-7 tzdata-2012e-1 udev-182-1 [removal] usbutils-006-1 util-linux-2.21.2-5 wpa_supplicant-1.0-1 xfsprogs-3.1.8-2 xz-5.0.4-1 your-freedom-20120912-1 zile-2.4.8-1 zlib-1.2.7-1 Total Installed Size: 333.33 MiB Net Upgrade Size: 18.78 MiB Proceed with installation? [Y/n] checking package integrity... loading package files... checking for file conflicts... error: failed to commit transaction (conflicting files) glibc: /lib exists in filesystem filesystem: /var/run exists in filesystem Errors occurred, no packages were upgraded. Thanks From mtjm at mtjm.eu Wed Sep 12 15:16:45 2012 From: mtjm at mtjm.eu (=?utf-8?Q?Micha=C5=82_Mas=C5=82owski?=) Date: Wed, 12 Sep 2012 17:16:45 +0200 Subject: [Assist] How to resolve conflicts? In-Reply-To: (stayvoid@gmail.com's message of "Wed, 12 Sep 2012 19:05:23 +0400") References: <877gs03f01.fsf@mtjm.eu> Message-ID: <87vcfji84i.fsf@mtjm.eu> > :: Replace udev with core/systemd? [Y/n] > :: Replace udev with core/systemd-tools? [Y/n] We should remove systemd-tools and maybe other packages from repos. > error: failed to commit transaction (conflicting files) > glibc: /lib exists in filesystem Upgrading with --ignore glibc and then separately pacman -S glibc might fix it. There might be more problems with it. > filesystem: /var/run exists in filesystem Separately force the filesystem upgrade. Will try making a new base tarball, might be easier. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: From stayvoid at gmail.com Wed Sep 12 17:41:11 2012 From: stayvoid at gmail.com (Stayvoid) Date: Wed, 12 Sep 2012 21:41:11 +0400 Subject: [Assist] How to resolve conflicts? In-Reply-To: <87vcfji84i.fsf@mtjm.eu> References: <877gs03f01.fsf@mtjm.eu> <87vcfji84i.fsf@mtjm.eu> Message-ID: > Upgrading with --ignore glibc and then separately pacman -S glibc might > fix it. ?There might be more problems with it. Okey, I'll give it a try. >> filesystem: /var/run exists in filesystem > Separately force the filesystem upgrade. What do you mean? Could you be more specific? Thanks From mtjm at mtjm.eu Wed Sep 12 18:26:12 2012 From: mtjm at mtjm.eu (=?utf-8?Q?Micha=C5=82_Mas=C5=82owski?=) Date: Wed, 12 Sep 2012 20:26:12 +0200 Subject: [Assist] How to resolve conflicts? In-Reply-To: (stayvoid@gmail.com's message of "Wed, 12 Sep 2012 21:41:11 +0400") References: <877gs03f01.fsf@mtjm.eu> <87vcfji84i.fsf@mtjm.eu> Message-ID: <87r4q7hzcr.fsf@mtjm.eu> >>> filesystem: /var/run exists in filesystem > >> Separately force the filesystem upgrade. > > What do you mean? Could you be more specific? https://parabolagnulinux.org/news/archlinux-filesystem-upgrade-manual-intervention-required/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: From stayvoid at gmail.com Thu Sep 13 09:41:10 2012 From: stayvoid at gmail.com (Stayvoid) Date: Thu, 13 Sep 2012 13:41:10 +0400 Subject: [Assist] How to resolve conflicts? In-Reply-To: <87r4q7hzcr.fsf@mtjm.eu> References: <877gs03f01.fsf@mtjm.eu> <87vcfji84i.fsf@mtjm.eu> <87r4q7hzcr.fsf@mtjm.eu> Message-ID: > Will try making a new base tarball, might be easier. How long will it take? (I understood that you're going to make the tarball.) >> :: Replace udev with core/systemd? [Y/n] >> :: Replace udev with core/systemd-tools? [Y/n] > We should remove systemd-tools and maybe other packages from repos. > Upgrading with --ignore glibc and then separately pacman -S glibc might > fix it. ?There might be more problems with it. # pacman -Syu --ignore glibc :: Synchronizing package databases... libre is up to date core is up to date extra is up to date community is up to date :: Starting full system upgrade... warning: glibc: ignoring package upgrade (2.15-10 => 2.16.0-4) :: Replace libusb with core/libusbx? [Y/n] :: Replace procps with core/procps-ng? [Y/n] :: Replace procps with community/procps-ng? [Y/n] warning: cannot replace procps by procps-ng :: Replace udev with core/systemd [Y/n] n resolving dependencies... :: The following packages cannot be upgraded due to unresolvable dependencies: ca-certificates coreutils cronie cryptsetup curl db dbus-core e2fsprogs filesystem gc gcc-libs glib2 gmp grep inetutils initscripts iproute2 iputils krb5 ldns less libldap libssh2 linux-libre logrotate mkinitcpio openssh openssl pacman pam pcre perl shadow sudo sysvinit util-linux wpa_supplicant xfsprogs zile :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 :: gcc-libs: requires glibc>=2.16 Why does it post the same message several times? From mtjm at mtjm.eu Thu Sep 13 10:01:41 2012 From: mtjm at mtjm.eu (=?utf-8?Q?Micha=C5=82_Mas=C5=82owski?=) Date: Thu, 13 Sep 2012 12:01:41 +0200 Subject: [Assist] How to resolve conflicts? In-Reply-To: (stayvoid@gmail.com's message of "Thu, 13 Sep 2012 13:41:10 +0400") References: <877gs03f01.fsf@mtjm.eu> <87vcfji84i.fsf@mtjm.eu> <87r4q7hzcr.fsf@mtjm.eu> Message-ID: <87zk4us0l6.fsf@mtjm.eu> >> Will try making a new base tarball, might be easier. > > How long will it take? > (I understood that you're going to make the tarball.) Try?[0]. > warning: glibc: ignoring package upgrade (2.15-10 => 2.16.0-4) This could be fixed by upgrading first to 2.16.0-1 (e.g. from?[1]) or using the new base tarball. [0] http://mtjm.eu/releases/parabola/parabola-mips64el-20120912.tar.bz2 [1] http://repo.parabolagnulinux.org/other/glibc-2.16.0-1-mips64el.pkg.tar.xz -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: From stayvoid at gmail.com Fri Sep 14 23:33:10 2012 From: stayvoid at gmail.com (Stayvoid) Date: Sat, 15 Sep 2012 03:33:10 +0400 Subject: [Assist] Parabola's main page shows 502 Message-ID: Hello, Main page shows 502, subdomains (e.g. wiki, lists) work fine. Connection via https shows the following: "SSL handshake failed: A TLS packet with unexpected length was received." From stayvoid at gmail.com Sat Sep 15 00:28:02 2012 From: stayvoid at gmail.com (Stayvoid) Date: Sat, 15 Sep 2012 04:28:02 +0400 Subject: [Assist] boot.cfg: encrypted root partition Message-ID: Hello, How would you configure boot.cfg if your root partition is encrypted? For example: /dev/sda1 boot /dev/sda2 swap /dev/sda3 main /dev/sda2 and /dev/sda3 are encrypted, but they can be accessed via /dev/mapper (e.g. /dev/mapper/swap). Thanks From mtjm at mtjm.eu Sat Sep 15 10:59:03 2012 From: mtjm at mtjm.eu (=?utf-8?Q?Micha=C5=82_Mas=C5=82owski?=) Date: Sat, 15 Sep 2012 12:59:03 +0200 Subject: [Assist] Parabola's main page shows 502 In-Reply-To: (stayvoid@gmail.com's message of "Sat, 15 Sep 2012 03:33:10 +0400") References: Message-ID: <87k3vvwo08.fsf@mtjm.eu> > Main page shows 502, subdomains (e.g. wiki, lists) work fine. > Connection via https shows the following: > "SSL handshake failed: A TLS packet with unexpected length was received." There are known problems with the VPS (SSH also doesn't work). The subdomains that work are on the other server (e.g. labs.parabola.nu also doesn't work). -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: From mtjm at mtjm.eu Sat Sep 15 14:29:16 2012 From: mtjm at mtjm.eu (=?utf-8?Q?Micha=C5=82_Mas=C5=82owski?=) Date: Sat, 15 Sep 2012 16:29:16 +0200 Subject: [Assist] boot.cfg: encrypted root partition In-Reply-To: (stayvoid@gmail.com's message of "Sat, 15 Sep 2012 04:28:02 +0400") References: Message-ID: <87boh7we9v.fsf@mtjm.eu> > How would you configure boot.cfg if your root partition is encrypted? > > For example: > /dev/sda1 boot > /dev/sda2 swap > /dev/sda3 main > > /dev/sda2 and /dev/sda3 are encrypted, but they can be accessed via > /dev/mapper (e.g. /dev/mapper/swap). The only things specific to encryption are kernel arguments and the initrd, non-mips64el-specific documentation might explain it. In the example at?[0] you will probably change the args and add an "initrd (wd0,6)/boot/initramfs-linux-libre.img" line. [0] https://wiki.parabolagnulinux.org/MIPS_Installation#Add_the_new_system_to_PMON -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: From stayvoid at gmail.com Sat Sep 15 16:46:59 2012 From: stayvoid at gmail.com (Stayvoid) Date: Sat, 15 Sep 2012 20:46:59 +0400 Subject: [Assist] boot.cfg: encrypted root partition In-Reply-To: <87boh7we9v.fsf@mtjm.eu> References: <87boh7we9v.fsf@mtjm.eu> Message-ID: > In the > example at?[0] you will probably change the args and add an "initrd > (wd0,6)/boot/initramfs-linux-libre.img" line. What about a root partition? What should I use: root=/dev/sda3 or root=/dev/mapper/main? Is it possible not to specify the root partition at all? From mtjm at mtjm.eu Sat Sep 15 16:57:06 2012 From: mtjm at mtjm.eu (=?utf-8?Q?Micha=C5=82_Mas=C5=82owski?=) Date: Sat, 15 Sep 2012 18:57:06 +0200 Subject: [Assist] boot.cfg: encrypted root partition In-Reply-To: (stayvoid@gmail.com's message of "Sat, 15 Sep 2012 20:46:59 +0400") References: <87boh7we9v.fsf@mtjm.eu> Message-ID: <877grvw7fh.fsf@mtjm.eu> > What should I use: root=/dev/sda3 or root=/dev/mapper/main? The second one. > Is it possible not to specify the root partition at all? Probably not. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: From stayvoid at gmail.com Sat Sep 15 20:40:23 2012 From: stayvoid at gmail.com (Stayvoid) Date: Sun, 16 Sep 2012 00:40:23 +0400 Subject: [Assist] boot.cfg: encrypted root partition In-Reply-To: <877grvw7fh.fsf@mtjm.eu> References: <87boh7we9v.fsf@mtjm.eu> <877grvw7fh.fsf@mtjm.eu> Message-ID: > The second one. boot.cfg: title Parabola GNU/Linux-libre kernel (wd0,0)/boot/vmlinuz-linux-libre initrd (wd0,0)/boot/initramfs-linux-libre.img args root=/dev/mapper/main console=tty no_auto_cmd I was able to select "Parabola GNU/Linux-libre," then the following message appeared: file is not set or not exist! path is not complete, haven't selected the device or file! The boot.cfg not existed!System will try default entry from al. What's wrong? From mtjm at mtjm.eu Sun Sep 16 09:13:52 2012 From: mtjm at mtjm.eu (=?utf-8?Q?Micha=C5=82_Mas=C5=82owski?=) Date: Sun, 16 Sep 2012 11:13:52 +0200 Subject: [Assist] boot.cfg: encrypted root partition In-Reply-To: (stayvoid@gmail.com's message of "Sun, 16 Sep 2012 00:40:23 +0400") References: <87boh7we9v.fsf@mtjm.eu> <877grvw7fh.fsf@mtjm.eu> Message-ID: <87zk4q5nzj.fsf@mtjm.eu> > boot.cfg: > > title Parabola GNU/Linux-libre > kernel (wd0,0)/boot/vmlinuz-linux-libre > initrd (wd0,0)/boot/initramfs-linux-libre.img > args root=/dev/mapper/main console=tty no_auto_cmd > > I was able to select "Parabola GNU/Linux-libre," then the following > message appeared: > > file is not set or not exist! > path is not complete, haven't selected the device or file! > The boot.cfg not existed!System will try default entry from al. You have the /boot directory on your /boot filesystem? Would try paths like (wd0,0)/vmlinuz-linux-libre. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: From stayvoid at gmail.com Sun Sep 16 12:21:17 2012 From: stayvoid at gmail.com (Stayvoid) Date: Sun, 16 Sep 2012 16:21:17 +0400 Subject: [Assist] boot.cfg: encrypted root partition In-Reply-To: <87zk4q5nzj.fsf@mtjm.eu> References: <87boh7we9v.fsf@mtjm.eu> <877grvw7fh.fsf@mtjm.eu> <87zk4q5nzj.fsf@mtjm.eu> Message-ID: > You have the /boot directory on your /boot filesystem? Ah, no. > Would try paths like (wd0,0)/vmlinuz-linux-libre. None of the following works, but the first one lights the hard disk icon*. I also get that error message, but now it appears before the menu. * I guess that it's trying to read something from the disk but fails. title 1 kernel (wd0,0)/vmlinuz-linux-libre initrd (wd0,0)/initramfs-linux-libre.img args root=/dev/mapper/main console=tty no_auto_cmd title 2 kernel (wd0,0)vmlinuz-linux-libre initrd (wd0,0)initramfs-linux-libre.img args root=/dev/mapper/main console=tty no_auto_cmd title 3 kernel (wd0,0)/vmlinuz-linux-libre args root=/dev/mapper/main console=tty no_auto_cmd title 4 kernel (wd0,0)vmlinuz-linux-libre args root=/dev/mapper/main console=tty no_auto_cmd title 5 kernel (wd0,0)/vmlinuz-linux-libre initrd (wd0,0)/initramfs-linux-libre.img args console=tty no_auto_cmd title 6 kernel (wd0,0)vmlinuz-linux-libre initrd (wd0,0)initramfs-linux-libre.img args console=tty no_auto_cmd From mtjm at mtjm.eu Sun Sep 16 13:24:12 2012 From: mtjm at mtjm.eu (=?utf-8?Q?Micha=C5=82_Mas=C5=82owski?=) Date: Sun, 16 Sep 2012 15:24:12 +0200 Subject: [Assist] boot.cfg: encrypted root partition In-Reply-To: (stayvoid@gmail.com's message of "Sun, 16 Sep 2012 16:21:17 +0400") References: <87boh7we9v.fsf@mtjm.eu> <877grvw7fh.fsf@mtjm.eu> <87zk4q5nzj.fsf@mtjm.eu> Message-ID: <87vcfe5ceb.fsf@mtjm.eu> > title 1 > kernel (wd0,0)/vmlinuz-linux-libre > initrd (wd0,0)/initramfs-linux-libre.img > args root=/dev/mapper/main console=tty no_auto_cmd Check if the initrd file exists (it should). 2, 4 and 6 seem to have incorrect syntax. Will the following ones get different errors if only the odd entries are left? > title 3 > kernel (wd0,0)/vmlinuz-linux-libre > args root=/dev/mapper/main console=tty no_auto_cmd > > title 5 > kernel (wd0,0)/vmlinuz-linux-libre > initrd (wd0,0)/initramfs-linux-libre.img > args console=tty no_auto_cmd You could also try manually booting without boot.cfg, [0] has commands that work for it (they need different device naming). [0] https://wiki.parabolagnulinux.org/MIPS_Installation/Booting_from_USB_stick -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: From stayvoid at gmail.com Sun Sep 16 15:26:12 2012 From: stayvoid at gmail.com (Stayvoid) Date: Sun, 16 Sep 2012 19:26:12 +0400 Subject: [Assist] boot.cfg: encrypted root partition In-Reply-To: <87vcfe5ceb.fsf@mtjm.eu> References: <87boh7we9v.fsf@mtjm.eu> <877grvw7fh.fsf@mtjm.eu> <87zk4q5nzj.fsf@mtjm.eu> <87vcfe5ceb.fsf@mtjm.eu> Message-ID: > Check if the initrd file exists (it should). There is one. Looks like I'm not patient. I decided to try again and to wait a bit longer (~ 3 mins). Results: 1. This error [1] doesn't appear anymore; 2. This entry [2] drops me to a recovery shell: :: running early hook [udev] :: running hook [udev] :: Triggering uevents... ERROR: device '' not found. Skipping fsck. ERROR: Unable to find root device ''/ 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 /]# exit Trying to continue (this will most likely fail) ... :: mounting '' on real root mount: / is not a block device You are now being dropped into an emergency shell. sh: can't access tty; job control turned off 3. This entry [3] leads to a kernel panic: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) 4. This entry [4] drops me to a recovery shell, but the message is slightly different: :: running early hook [udev] :: running hook [udev] :: Triggering uevents... ERROR: device '/dev/mapper/main' not found. Skipping fsck. ERROR: Unable to find root device '/dev/mapper/main'. You are being dropped to a recovery shell Type 'exit' to try and continue booting sh: can't access tty; job control turned off Trying to continue (this will most likely fail) ... :: mounting '/dev/mapper/main' on real root mount: special device /dev/mapper/main does not exist You are now being dropped into an emergency shell. sh: can't access tty; job control turned off Should it work this way? Should I decrypt the main partition using the recovery shell? By the way, nothing appears on the screen during the boot (in all cases). Is this okey? (It shows some info when I'm loading an initrd image from a stick.) [1] file is not set or not exist! path is not complete, haven't selected the device or file! The boot.cfg not existed!System will try default entry from al. [2] title 5 kernel (wd0,0)/vmlinuz-linux-libre initrd (wd0,0)/initramfs-linux-libre.img args console=tty no_auto_cmd [3] title 3 kernel (wd0,0)/vmlinuz-linux-libre args root=/dev/mapper/main console=tty no_auto_cmd [4] title 1 kernel (wd0,0)/vmlinuz-linux-libre initrd (wd0,0)/initramfs-linux-libre.img args root=/dev/mapper/main console=tty no_auto_cmd From mtjm at mtjm.eu Sun Sep 16 15:36:56 2012 From: mtjm at mtjm.eu (=?utf-8?Q?Micha=C5=82_Mas=C5=82owski?=) Date: Sun, 16 Sep 2012 17:36:56 +0200 Subject: [Assist] boot.cfg: encrypted root partition In-Reply-To: (stayvoid@gmail.com's message of "Sun, 16 Sep 2012 19:26:12 +0400") References: <87boh7we9v.fsf@mtjm.eu> <877grvw7fh.fsf@mtjm.eu> <87zk4q5nzj.fsf@mtjm.eu> <87vcfe5ceb.fsf@mtjm.eu> Message-ID: <87r4q25693.fsf@mtjm.eu> > 4. This entry [4] drops me to a recovery shell, but the message is > slightly different: > > :: running early hook [udev] > :: running hook [udev] > :: Triggering uevents... > ERROR: device '/dev/mapper/main' not found. Skipping fsck. > ERROR: Unable to find root device '/dev/mapper/main'. [...] > Should it work this way? > Should I decrypt the main partition using the recovery shell? The initrd doesn't decrypt it, see e.g.?[0] for how to configure it (mkinitcpio needs the encrypt hook). Wouldn't try using the recovery shell, usually it's needed when initrd doesn't have a needed program (or kernel module), it doesn't help in such cases. [0] https://wiki.archlinux.org/index.php/Dm-crypt_with_LUKS -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: From stayvoid at gmail.com Sun Sep 16 16:30:22 2012 From: stayvoid at gmail.com (Stayvoid) Date: Sun, 16 Sep 2012 20:30:22 +0400 Subject: [Assist] boot.cfg: encrypted root partition In-Reply-To: <87r4q25693.fsf@mtjm.eu> References: <87boh7we9v.fsf@mtjm.eu> <877grvw7fh.fsf@mtjm.eu> <87zk4q5nzj.fsf@mtjm.eu> <87vcfe5ceb.fsf@mtjm.eu> <87r4q25693.fsf@mtjm.eu> Message-ID: > The initrd doesn't decrypt it, see e.g.?[0] for how to configure it > (mkinitcpio needs the encrypt hook). "root=/dev/mapper/root cryptdevice=/dev/sda5:root In this case, /dev/sda5 is the encrypted device, and we give it an arbitrary name of root, which means our root device, once unlocked, is mounted as /dev/mapper/root. On bootup, you will be prompted for the passphrase to unlock it." [1] I'm playing with a plain version of dm-crypt. It doesn't store any metadata on a disk. And I don't want to expose that there is an encrypted data. That's why I'd like to mount and decrypt it by hand. What are my options? [1] https://wiki.archlinux.org/index.php/Mkinitcpio#Using_encrypted_root From stayvoid at gmail.com Sun Sep 16 16:35:59 2012 From: stayvoid at gmail.com (Stayvoid) Date: Sun, 16 Sep 2012 20:35:59 +0400 Subject: [Assist] boot.cfg: encrypted root partition In-Reply-To: References: <87boh7we9v.fsf@mtjm.eu> <877grvw7fh.fsf@mtjm.eu> <87zk4q5nzj.fsf@mtjm.eu> <87vcfe5ceb.fsf@mtjm.eu> <87r4q25693.fsf@mtjm.eu> Message-ID: > And I don't want to expose that there is an encrypted data. And I don't want to expose that my disk is encrypted. From mtjm at mtjm.eu Mon Sep 17 09:34:22 2012 From: mtjm at mtjm.eu (=?utf-8?Q?Micha=C5=82_Mas=C5=82owski?=) Date: Mon, 17 Sep 2012 11:34:22 +0200 Subject: [Assist] boot.cfg: encrypted root partition In-Reply-To: (stayvoid@gmail.com's message of "Sun, 16 Sep 2012 20:30:22 +0400") References: <87boh7we9v.fsf@mtjm.eu> <877grvw7fh.fsf@mtjm.eu> <87zk4q5nzj.fsf@mtjm.eu> <87vcfe5ceb.fsf@mtjm.eu> <87r4q25693.fsf@mtjm.eu> Message-ID: <87ipbdq9gh.fsf@mtjm.eu> > And I don't want to expose that there is an encrypted data. Why else would you have an initrd with dm-crypt support? There might be also other information on the partition. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: From stayvoid at gmail.com Mon Sep 17 12:25:14 2012 From: stayvoid at gmail.com (Stayvoid) Date: Mon, 17 Sep 2012 16:25:14 +0400 Subject: [Assist] boot.cfg: encrypted root partition In-Reply-To: <87ipbdq9gh.fsf@mtjm.eu> References: <87boh7we9v.fsf@mtjm.eu> <877grvw7fh.fsf@mtjm.eu> <87zk4q5nzj.fsf@mtjm.eu> <87vcfe5ceb.fsf@mtjm.eu> <87r4q25693.fsf@mtjm.eu> <87ipbdq9gh.fsf@mtjm.eu> Message-ID: > Why else would you have an initrd with dm-crypt support? ?There might be > also other information on the partition. Could you elaborate? I'm not sure that I understood your question. From mtjm at mtjm.eu Mon Sep 17 13:11:18 2012 From: mtjm at mtjm.eu (=?utf-8?Q?Micha=C5=82_Mas=C5=82owski?=) Date: Mon, 17 Sep 2012 15:11:18 +0200 Subject: [Assist] boot.cfg: encrypted root partition In-Reply-To: (stayvoid@gmail.com's message of "Mon, 17 Sep 2012 16:25:14 +0400") References: <87boh7we9v.fsf@mtjm.eu> <877grvw7fh.fsf@mtjm.eu> <87zk4q5nzj.fsf@mtjm.eu> <87vcfe5ceb.fsf@mtjm.eu> <87r4q25693.fsf@mtjm.eu> <87ipbdq9gh.fsf@mtjm.eu> Message-ID: <87ehm0rdzd.fsf@mtjm.eu> > Could you elaborate? Knowing that your initrd supports dm-crypt strongly suggests that you have an encrypted root. So maybe there is no need to hide which device is that encrypted root. What you want might be similar to?[0]. [0] https://en.wikipedia.org/wiki/Deniable_encryption -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: From stayvoid at gmail.com Mon Sep 17 14:30:50 2012 From: stayvoid at gmail.com (Stayvoid) Date: Mon, 17 Sep 2012 18:30:50 +0400 Subject: [Assist] boot.cfg: encrypted root partition In-Reply-To: <87ehm0rdzd.fsf@mtjm.eu> References: <87boh7we9v.fsf@mtjm.eu> <877grvw7fh.fsf@mtjm.eu> <87zk4q5nzj.fsf@mtjm.eu> <87vcfe5ceb.fsf@mtjm.eu> <87r4q25693.fsf@mtjm.eu> <87ipbdq9gh.fsf@mtjm.eu> <87ehm0rdzd.fsf@mtjm.eu> Message-ID: Is there a free program (as powerful as dm-crypt) that has a support for a deniable encryption? Anyway, my question was technical, not philosophical. How to manually unmount / decrypt partitions during the boot time? From ineiev at gnu.org Thu Sep 27 10:55:56 2012 From: ineiev at gnu.org (Ineiev) Date: Thu, 27 Sep 2012 14:55:56 +0400 Subject: [Assist] Reporting bugs Message-ID: <506430BC.6010806@gnu.org> Hello, When I try to report a bug against pilot-link (I follow a link from that package page [0]), I come to bug tracker page that is not package-specific; after that I follow the "Project" link from the top of that page, then "Packages (i686 and x86_64)"; that leads me to [1] where I fail to find the "New issue" at the top as documented per [2]. How do I report bugs? [0] https://parabolagnulinux.org/packages/extra/i686/pilot-link/ [1] https://labs.parabola.nu/projects/issue-tracker [2] https://www.chiliproject.org/projects/chiliproject/wiki/Reporting_an_issue From mtjm at mtjm.eu Thu Sep 27 11:13:27 2012 From: mtjm at mtjm.eu (=?utf-8?Q?Micha=C5=82_Mas=C5=82owski?=) Date: Thu, 27 Sep 2012 13:13:27 +0200 Subject: [Assist] Reporting bugs In-Reply-To: <506430BC.6010806@gnu.org> (ineiev@gnu.org's message of "Thu, 27 Sep 2012 14:55:56 +0400") References: <506430BC.6010806@gnu.org> Message-ID: <87a9wb4t2g.fsf@mtjm.eu> > When I try to report a bug against pilot-link (I follow > a link from that package page [0]), I come to > bug tracker page that is not package-specific; There was a different bug tracker before, the links were not updated while a redirection to the new one was introduced. (Reported issue #200 for this.) > after that I follow the "Project" link from the top > of that page, then "Packages (i686 and x86_64)"; > that leads me to [1] where I fail to find the "New issue" > at the top as documented per [2]. Register there or convince other developers that you don't need mail notifications and we should allow anonymous submissions. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: From ineiev at gnu.org Thu Sep 27 12:46:28 2012 From: ineiev at gnu.org (Ineiev) Date: Thu, 27 Sep 2012 16:46:28 +0400 Subject: [Assist] Reporting bugs In-Reply-To: <87a9wb4t2g.fsf@mtjm.eu> References: <506430BC.6010806@gnu.org> <87a9wb4t2g.fsf@mtjm.eu> Message-ID: <50644AA4.3070901@gnu.org> On 09/27/2012 03:13 PM, Micha? Mas?owski wrote: > Register there or convince other developers that you don't need mail > notifications and we should allow anonymous submissions. Thank you; I choose not to register. How can I contact those other developers? Basically, my point is as follows: Parabola is known to follow FSF's guidelines for free system distributions; and they imply "a firm commitment to correct mistakes". I'm not sure the commitment may definitely qualify as firm if a random user can't easily report the bugs; personally, so far I've done the next: (0) I tried the described procedure for the first time (months ago). (1) When I failed to report the bug and to find on those pages any contacts of Parabola people, I asked report-nonfree at fsf.org for assistance; after some discussion they pointed to this mailing list. (2) I dropped a message to this list without prior subscription; the message seems to have been rejected. (3) I subscribed to the list, and now I'm discussing how to report the bug. I don't think it is absolutely necessary to accept anonymous submissions (though it would be good IMO); however, Parabola could at least (a) say in the wiki (or better in the bug tracker) that one should register in order to report bugs there; (b) suggest that people may alternatively report bugs e.g. on this list; (c) moderate the messages coming to that list from non-subscribers more carefully. From mtjm at mtjm.eu Thu Sep 27 13:19:51 2012 From: mtjm at mtjm.eu (=?utf-8?Q?Micha=C5=82_Mas=C5=82owski?=) Date: Thu, 27 Sep 2012 15:19:51 +0200 Subject: [Assist] Reporting bugs In-Reply-To: <50644AA4.3070901@gnu.org> (ineiev@gnu.org's message of "Thu, 27 Sep 2012 16:46:28 +0400") References: <506430BC.6010806@gnu.org> <87a9wb4t2g.fsf@mtjm.eu> <50644AA4.3070901@gnu.org> Message-ID: <87r4pn38nc.fsf@mtjm.eu> Ineiev writes: > On 09/27/2012 03:13 PM, Micha? Mas?owski wrote: >> Register there or convince other developers that you don't need mail >> notifications and we should allow anonymous submissions. > > Thank you; I choose not to register. > > How can I contact those other developers? E.g. by writing to the dev at lists.parabolagnulinux.org list. > Basically, my point is as follows: Parabola is known > to follow FSF's guidelines for free system distributions; and > they imply "a firm commitment to correct mistakes". > > I'm not sure the commitment may definitely qualify as firm > if a random user can't easily report the bugs; personally, > so far I've done the next: You can report these in less formal ways, they rarely need to be searchable or discussed on the tracker (most are "solved" by removing a package and listing it on the blacklist). Changing this is needed for technical issues that e.g. prevent users from installing Parabola on their machines. > (0) I tried the described procedure for the first time (months ago). > (1) When I failed to report the bug and to find on those pages > any contacts of Parabola people, I asked report-nonfree at fsf.org > for assistance; after some discussion they pointed to this mailing > list. There are small links to the IRC channel and to the lists (and the main page of the new issue tracker) on the main page. > (2) I dropped a message to this list without prior subscription; > the message seems to have been rejected. I think they are manually approved, I don't know who does it, we need a clearer policy on that. > I don't think it is absolutely necessary to accept anonymous > submissions (though it would be good IMO); however, Parabola could > at least Several users wrote that they won't report bugs since it requires registration, we should fix this. > (a) say in the wiki (or better in the bug tracker) that one > should register in order to report bugs there; > (b) suggest that > people may alternatively report bugs e.g. on this list; This is implicit, would asking to report problems with the bug tracker there be ok? > (c) moderate the messages coming to that list from non-subscribers > more carefully. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 835 bytes Desc: not available URL: From stayvoid at gmail.com Thu Sep 27 13:38:06 2012 From: stayvoid at gmail.com (Stayvoid) Date: Thu, 27 Sep 2012 17:38:06 +0400 Subject: [Assist] Reporting bugs In-Reply-To: <50644AA4.3070901@gnu.org> References: <506430BC.6010806@gnu.org> <87a9wb4t2g.fsf@mtjm.eu> <50644AA4.3070901@gnu.org> Message-ID: > Thank you; I choose not to register. I second this. From ineiev at gnu.org Thu Sep 27 15:15:34 2012 From: ineiev at gnu.org (Ineiev) Date: Thu, 27 Sep 2012 15:15:34 +0000 Subject: [Assist] Reporting bugs In-Reply-To: <87vcezpn4c.fsf@kiwwwi.com.ar> References: <506430BC.6010806@gnu.org> <87a9wb4t2g.fsf@mtjm.eu> <50644AA4.3070901@gnu.org> <87r4pn38nc.fsf@mtjm.eu> <87vcezpn4c.fsf@kiwwwi.com.ar> Message-ID: <50646D96.20905@gnu.org> On 09/27/2012 01:19 PM, Micha? Mas?owski wrote: > Ineiev writes: > >> How can I contact those other developers? > > E.g. by writing to the dev at lists.parabolagnulinux.org list. I see; I should have noticed it when visiting https://lists.parabolagnulinux.org/mailman/listinfo. > There are small links to the IRC channel and to the lists (and the main > page of the new issue tracker) on the main page. Then I was wrong here. sorry. >> (a) say in the wiki (or better in the bug tracker) that one >> should register in order to report bugs there; > >> (b) suggest that >> people may alternatively report bugs e.g. on this list; > > This is implicit, would asking to report problems with the bug tracker > there be ok? I think it would. On 09/27/2012 02:16 PM, Nicol?s Reynolds wrote: > my problem with anonymous bug reports is that if you have to ask for > more details to the reporter you're screwed, and if the bug report is > vague to say the least you have to guess and search by yourself - it's > more work for you and it's annoying. If the user is interested in fixing the bug, there is a chance that she will visit the bug report later; if not, the vague report may be discarded in good conscience after a reasonable period. > (also as of today the registration is immediate, no mail confirmation > required and i think mtjm enabled openid) As a data point: mail confirmation wouldn't be a problem for me; I just do not want to register. >> There are small links to the IRC channel and to the lists (and the main >> page of the new issue tracker) on the main page. > > i personally prefer the irc channel for casual bug reporting On the other hand, I'm not used to IRC; I never use it. > i never saw a bug tracker that doesn't require registration though :D Why? http://savannah.gnu.org/bugs/?group=www-ru doesn't; the reporter even doesn't has to have any email account (my mother has none). From ineiev at gnu.org Fri Sep 21 06:21:38 2012 From: ineiev at gnu.org (Ineiev) Date: Fri, 21 Sep 2012 06:21:38 -0000 Subject: [Assist] Reporting bugs Message-ID: <505C07D9.4070004@gnu.org> Hello, When I try to report a bug against pilot-link (I follow a link from that package page [0]), I come to bug tracker page that is not package-specific; after that I follow the "Project" link from the top of that page, then "Packages (i686 and x86_64)"; that leads me to [1] where I fail to find the "New issue" at the top as documented per [2]. How do I report bugs? [0] https://parabolagnulinux.org/packages/extra/i686/pilot-link/ [1] https://labs.parabola.nu/projects/issue-tracker [2] https://www.chiliproject.org/projects/chiliproject/wiki/Reporting_an_issue From fauno at kiwwwi.com.ar Thu Sep 27 14:16:26 2012 From: fauno at kiwwwi.com.ar (=?utf-8?Q?Nicol=C3=A1s?= Reynolds) Date: Thu, 27 Sep 2012 14:16:26 -0000 Subject: [Assist] [Dev] Reporting bugs In-Reply-To: <87r4pn38nc.fsf@mtjm.eu> References: <506430BC.6010806@gnu.org> <87a9wb4t2g.fsf@mtjm.eu> <50644AA4.3070901@gnu.org> <87r4pn38nc.fsf@mtjm.eu> Message-ID: <87vcezpn4c.fsf@kiwwwi.com.ar> Micha? Mas?owski writes: > Ineiev writes: > >> On 09/27/2012 03:13 PM, Micha? Mas?owski wrote: >>> Register there or convince other developers that you don't need mail >>> notifications and we should allow anonymous submissions. >> >> Thank you; I choose not to register. my problem with anonymous bug reports is that if you have to ask for more details to the reporter you're screwed, and if the bug report is vague to say the least you have to guess and search by yourself - it's more work for you and it's annoying. but i'd implement anonymous bug reports with a bug report template or accept any other idea that tries to solve this problem. (also as of today the registration is immediate, no mail confirmation required and i think mtjm enabled openid) > There are small links to the IRC channel and to the lists (and the main > page of the new issue tracker) on the main page. i personally prefer the irc channel for casual bug reporting >> (2) I dropped a message to this list without prior subscription; >> the message seems to have been rejected. > > I think they are manually approved, I don't know who does it, we need a > clearer policy on that. if assist@ talk to shackra >> I don't think it is absolutely necessary to accept anonymous >> submissions (though it would be good IMO); however, Parabola could >> at least > > Several users wrote that they won't report bugs since it requires > registration, we should fix this. i never saw a bug tracker that doesn't require registration though :D -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 489 bytes Desc: not available URL: