On Friday 30 Jan 2015 7:12:18 PM arnaud gaboury wrote:
> I have happily used a second Arch as a container booted with systemd-nspawn.
>
> I would like now install a CentOS container, but I am not sure how to
> proceed the install. What is the correct way ?
> - first install minimal CentOS from an
On Fri, Jan 30, 2015, at 08:11 PM, William Gathoye wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 01/29/2015 07:01 PM, Georg Altmann wrote:
> > On 29.01.2015 17:40, Don deJuan wrote: I am merely _suggesting_ to
> > implement a warning message. It certainly _is_ easy to miss
> >
On Fri, Jan 30, 2015, at 08:11 PM, William Gathoye wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 01/29/2015 07:01 PM, Georg Altmann wrote:
> > On 29.01.2015 17:40, Don deJuan wrote: I am merely _suggesting_ to
> > implement a warning message. It certainly _is_ easy to miss
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/29/2015 07:01 PM, Georg Altmann wrote:
> On 29.01.2015 17:40, Don deJuan wrote: I am merely _suggesting_ to
> implement a warning message. It certainly _is_ easy to miss
> something in the "pacman -Suy" output. As such, I think this would
> be
> > So I just installed clamav but when I'm trying to start it with:
> >>
> > 'sudo systemctl start clamd.service'
> >>
> >> I get:
> >> Job for clamd.service failed. See "systemctl status clamd.service" and
> >> "journalctl -xe" for details.
> >>
> >> 'systemctl status clamd.service'
> >> clamd.s
> > So I just installed clamav but when I'm trying to start it with:
> >>
> > 'sudo systemctl start clamd.service'
> >>
> >> I get:
> >> Job for clamd.service failed. See "systemctl status clamd.service" and
> >> "journalctl -xe" for details.
> >>
> >> 'systemctl status clamd.service'
> >> clamd.s
>> Your pacman log and journalctl might give some clues.
> I guess he meant more or less complete logs. Give a journalctl log of a
> boot where you had the issue together with a pacman log including your
> latest updates (maybe since the problem began/ reappeared together with
> exact dates)
>
>>
>
>
> >> Your pacman log and journalctl might give some clues.
>
I guess he meant more or less complete logs. Give a journalctl log of a
boot where you had the issue together with a pacman log including your
latest updates (maybe since the problem began/ reappeared together with
exact dates)
> > I
2015-01-30 21:10 GMT+01:00 Csányi Pál :
> 2015-01-30 20:33 GMT+01:00 Christian Demsar :
>> On January 30, 2015 2:21:34 PM EST, "Csányi Pál" wrote:
>>>2015-01-30 20:04 GMT+01:00 Csányi Pál :
Hi Damjan,
2015-01-30 19:39 GMT+01:00 Damjan Georgievski :
>> I'm thinking now about foll
2015-01-30 20:33 GMT+01:00 Christian Demsar :
> On January 30, 2015 2:21:34 PM EST, "Csányi Pál" wrote:
>>2015-01-30 20:04 GMT+01:00 Csányi Pál :
>>> Hi Damjan,
>>>
>>> 2015-01-30 19:39 GMT+01:00 Damjan Georgievski :
> I'm thinking now about following.
> Whether to purge my Desktop Arch li
On January 30, 2015 2:21:34 PM EST, "Csányi Pál" wrote:
>2015-01-30 20:04 GMT+01:00 Csányi Pál :
>> Hi Damjan,
>>
>> 2015-01-30 19:39 GMT+01:00 Damjan Georgievski :
I'm thinking now about following.
Whether to purge my Desktop Arch linux installation from hard disk
>and
install a fr
2015-01-30 20:04 GMT+01:00 Csányi Pál :
> Hi Damjan,
>
> 2015-01-30 19:39 GMT+01:00 Damjan Georgievski :
>>> I'm thinking now about following.
>>> Whether to purge my Desktop Arch linux installation from hard disk and
>>> install a fresh Arch linux again, or not?
>>>
>>> What would you do in my cas
Hi Damjan,
2015-01-30 19:39 GMT+01:00 Damjan Georgievski :
>> I'm thinking now about following.
>> Whether to purge my Desktop Arch linux installation from hard disk and
>> install a fresh Arch linux again, or not?
>>
>> What would you do in my case? ( I'm not a bash and Arch linux guru. )
>
> Fir
> I'm thinking now about following.
> Whether to purge my Desktop Arch linux installation from hard disk and
> install a fresh Arch linux again, or not?
>
> What would you do in my case? ( I'm not a bash and Arch linux guru. )
First thing is, how did it happen to become broken again.
Normally it s
Hello again,
the kernel panic error appeares again.
I fix my desktop system with commands:
lsblk
mkdir /mnt/arch
mount /dev/sda3 /mnt/arch
systemd-nspawn -D /mnt/arch
pacman -S base
mkinitcpio -p linux
exit
reboot
I'm thinking now about following.
Whether to purge my Desktop Arch linux installat
I have happily used a second Arch as a container booted with systemd-nspawn.
I would like now install a CentOS container, but I am not sure how to
proceed the install. What is the correct way ?
- first install minimal CentOS from an iso in a dedicated partition
(in my case it will be a ssd), then
I'm having an issue with Plasma 5 themes, and the Application
Launcher. I'm trying to use Breeze Dark. I've also specified it for
Colors, and Icons. The problem is, the background of the Application
Launcher is still a light gray color. It's so light it's almost
impossible to read the light text on
17 matches
Mail list logo
