Hello Andreas,
Andreas Glaeser [2017-03-17 8:31 +0100]:
> I am not convinced, that what you claim is true, since the
> hybrid-filesystem-concept
> worked on pure debian-stable
For some value of "works" -- the change between stable and testing (and perhaps
some backports) is that some libraries
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am not convinced, that what you claim is true, since the
hybrid-filesystem-concept
worked on pure debian-stable, it should be workable with backports included and
on current
testing, too.
You can have /usr in a separate partition, the symlink-work
On Tue, 14 Mar 2017 17:05:48 +0100 Andreas Glaeser <
bugs.andreas.glae...@freenet.de> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Package: installation-reports
> Version: 2.58
> Severity: minor
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where
Please stop
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Now I was sitting down again to install without md-raid and without XFS-root.
I can reconfirm, that the described problem does not appear with BTRFS-raid
only:
> /dev/sda5 btrfs 46872576 2298224 44044944 5% /
> udev devtmpfs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Disk /dev/mmcblk0: 59.5 GiB, 63864569856 bytes, 124735488 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: gpt
> Disk identi
On Tue, 2017-03-14 at 14:45 -0300, Felipe Sateler wrote:
> On Tue, 14 Mar 2017 17:05:48 +0100 Andreas Glaeser
> wrote:
>
>
> > So the root-filesystem looks like this:
> >
> > > drwxr-xr-x 2 root root 4096 Mar 14 16:02 bin
> > > drwxr-xr-x 3 root root 4096 Mar 14 16:32 boot
> > > drwxr-xr-x
On Tue, 14 Mar 2017 17:05:48 +0100 Andreas Glaeser
wrote:
> So the root-filesystem looks like this:
>
> > drwxr-xr-x 2 root root 4096 Mar 14 16:02 bin
> > drwxr-xr-x 3 root root 4096 Mar 14 16:32 boot
> > drwxr-xr-x 20 root root 3520 Mar 14 16:35 dev
> > drwxr-xr-x 139 root root 8192 Mar 14
Control: reassign -1 systemd
On Tue, 2017-03-14 at 17:05 +0100, Andreas Glaeser wrote:
[...]
> Kernel-Panic appears both with Kernel 3.16 and 4.9, when all backports are
> installed,
> see attachment [k-panic-sshot.JPG],
[...]
That shows that the kernel panicked because init (systemd) exited.
T
9 matches
Mail list logo