Re: [arch-general] unreadable characters login screen after install

On Sat, 26 Nov 2016 17:08:06 +0100 Ralf Mardorf wrote > Which login screen? > > A display manager's greeter? If so, xorg.conf or display manager settings > might solve the issue. Oops, I was confusing keyboard with fonts. Not xorg.conf, but much

Re: [arch-general] unreadable characters login screen after install

Which login screen? A display manager's greeter? If so, xorg.conf or display manager settings might solve the issue. Or tty?

[arch-general] unreadable characters login screen after install

hi everyone after an install following the wiki installation guide and rebooting the login screen shows unreadable characters, the char displays as rectangular and square blocks, locale.conf is set to LANG=en_GB.UTF-8 vconsole.conf is set to KEYMAP=uk i also tried adding a FONT= line to

Re: [arch-general] On containers. WAS: Re: snapcraft.io ...

On Sat, Nov 26, 2016 at 3:23 PM, Maarten de Vries > To my knowledge, makechrootpkg uses systemd-nspawn, which means it is > already using a container. Reproducible builds will need quite a bit more > work than simply using containers though. I only meant reproducible

Re: [arch-general] On containers. WAS: Re: snapcraft.io ...

On Sat, Nov 26, 2016 at 3:23 PM, Bennett Piater wrote: >> Another very useful case would be using containers as a chroot replacement >> for having clean (only what's in the recipe), reproducable build environments >> for building arch packages. It would also allow installing

Re: [arch-general] On containers. WAS: Re: snapcraft.io ...

On Sat, Nov 26, 2016 at 3:23 PM, Maarten de Vries wrote: > > > On 26 November 2016 at 15:08, Carsten Mattner via arch-general > wrote: >> >> >> Another very useful case would be using containers as a chroot replacement >> for having clean (only

Re: [arch-general] On containers. WAS: Re: snapcraft.io ...

On 26 November 2016 at 15:08, Carsten Mattner via arch-general < arch-general@archlinux.org> wrote: > > Another very useful case would be using containers as a chroot replacement > for having clean (only what's in the recipe), reproducable build > environments > for building arch packages. It

Re: [arch-general] On containers. WAS: Re: snapcraft.io ...

> Another very useful case would be using containers as a chroot replacement > for having clean (only what's in the recipe), reproducable build environments > for building arch packages. It would also allow installing makedeps only in > the container/chroot or make cross-compilation easier to

Re: [arch-general] On containers. WAS: Re: snapcraft.io ...

On Fri, Nov 25, 2016 at 7:01 PM, pelzflorian (Florian Pelz) wrote: > Containers are an attempt to solve multiple issues. One is being a > replacement for bundles. When people sell and distribute a proprietary > app/game, they presumably want it to run on as many