On Fri, Feb 14, 2014 at 3:21 AM, Jakub Klinkovský wrote:
> I have moved ~/.vim to ~/.config/vim, the configuration is as follows:
>
> in ~/.profile:
> export VIMINIT='let $MYVIMRC="$XDG_CONFIG_HOME/vim/vimrc" | source $MYVIMRC'
>
> in ~/.config/vim/vimrc:
> set viminfo+=n$XDG_CACHE_HOME/vim/vi
Hi,
Recently I had to fix a corrupted pacman db from a 3 month old livecd
and realized that this process is not so innocent. Specifically, there is a
chance to get a trojaned package on the system simply because the
archlinux-keyring package on the iso is outdated. Of course, other similar
On Thu, 13 Feb 2014 19:00:49 +0100
arnaud gaboury wrote:
> >
> > This feature is relatively new and is not enabled in the default Arch
> > Linux kernel:
> > $ zgrep USER_NS /proc/config.gz
> > # CONFIG_USER_NS is not set
> >
> > You'll have to build a custom kernel.
> >
> > --
> > Timothée Ravier
I have moved ~/.vim to ~/.config/vim, the configuration is as follows:
in ~/.profile:
export VIMINIT='let $MYVIMRC="$XDG_CONFIG_HOME/vim/vimrc" | source $MYVIMRC'
in ~/.config/vim/vimrc:
set viminfo+=n$XDG_CACHE_HOME/vim/viminfo
set
runtimepath=$XDG_CONFIG_HOME/vim,$XDG_CONFIG_HOME/vim/aft
>
> This feature is relatively new and is not enabled in the default Arch
> Linux kernel:
> $ zgrep USER_NS /proc/config.gz
> # CONFIG_USER_NS is not set
>
> You'll have to build a custom kernel.
>
> --
> Timothée Ravier
now I rebuilt the kernel with user space set.
Shall I do another new install
On Thu, Feb 13, 2014 at 5:19 PM, Paul Gideon Dann wrote:
> On Thursday 13 Feb 2014 13:36:35 Denis A. Altoé Falqueto wrote:
>> On Thu, Feb 13, 2014 at 1:29 PM, Paul Gideon Dann wrote:
>> > Yeah, though actually I'm just really surprised that, given the incredible
>> > administrative benefits of sy
>
> Yeah, I think it's possible to get systemd to poll a script, or there's
> always cron (or a timer
> unit) that should allow us to manually inspect a process and restart it if
> necessary. But it
> would be cooler if there were shortcuts to features that we see in Monit
> and other similar
> sy
On Thursday 13 Feb 2014 13:36:35 Denis A. Altoé Falqueto wrote:
> On Thu, Feb 13, 2014 at 1:29 PM, Paul Gideon Dann wrote:
> > Yeah, though actually I'm just really surprised that, given the incredible
> > administrative benefits of systemd, there isn't currently anything that
> > leverages it for
On Thu, Feb 13, 2014 at 1:29 PM, Paul Gideon Dann wrote:
> Yeah, though actually I'm just really surprised that, given the incredible
> administrative
> benefits of systemd, there isn't currently anything that leverages it for
> actual process
> monitoring and reporting. As far as I can tell, s
On Thursday 13 Feb 2014 16:05:05 Rodrigo Rivas wrote:
> Ok... I'll take the chance to practice my DBus abilities...
> It is a bit long, but it kind of works. Just replace the print() call
> with your favourite sendmail function and you'll get a notification
> every time any of the units specified i
On Thursday 13 Feb 2014 16:11:56 Thomas Bächler wrote:
> Am 13.02.2014 16:05, schrieb Rodrigo Rivas:
> > Ok... I'll take the chance to practice my DBus abilities...
> > It is a bit long, but it kind of works. Just replace the print() call
> > with your favourite sendmail function and you'll get a n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 13.02.2014 16:11, schrieb Thomas Bächler:
> Am 13.02.2014 16:05, schrieb Rodrigo Rivas:
>> Ok... I'll take the chance to practice my DBus abilities... It is
>> a bit long, but it kind of works. Just replace the print() call
>> with your favourite s
Am 13.02.2014 16:05, schrieb Rodrigo Rivas:
> Ok... I'll take the chance to practice my DBus abilities...
> It is a bit long, but it kind of works. Just replace the print() call
> with your favourite sendmail function and you'll get a notification
> every time any of the units specified in the comm
On Thu, Feb 13, 2014 at 1:35 PM, Thomas Bächler wrote:
>
> Am 13.02.2014 13:04, schrieb Paul Gideon Dann:
> > Does anyone know of any standard system for receiving
> > notifications from systemd for unit state changes? I currently
> > use Monit for the monitoring of many processes, and it'll e-ma
On Thursday 13 Feb 2014 13:41:21 Damien Churchill wrote:
> You could use unit overrides[0] to add the OnFailure to provided
> units. So should be able to set it up for any service you are
> interested in receiving notifications for, I would assume.
Yes, absolutely, but this only works for a subset
On 13 February 2014 13:35, Paul Gideon Dann wrote:
> On Thursday 13 Feb 2014 14:21:36 ushi wrote:
>> Am 13.02.2014 13:04, schrieb Paul Gideon Dann:
>> > Hello all,
>> >
>> > Does anyone know of any standard system for receiving notifications
>> > from systemd for unit state changes? I currently u
On Thursday 13 Feb 2014 14:21:36 ushi wrote:
> Am 13.02.2014 13:04, schrieb Paul Gideon Dann:
> > Hello all,
> >
> > Does anyone know of any standard system for receiving notifications
> > from systemd for unit state changes? I currently use Monit for the
> > monitoring of many processes, and it'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 13.02.2014 13:04, schrieb Paul Gideon Dann:
> Hello all,
>
> Does anyone know of any standard system for receiving notifications
> from systemd for unit state changes? I currently use Monit for the
> monitoring of many processes, and it'll e-mail
On Thursday 13 Feb 2014 13:35:59 Thomas Bächler wrote:
> Am 13.02.2014 13:04, schrieb Paul Gideon Dann:
> > Does anyone know of any standard system for receiving
> > notifications from systemd for unit state changes? I currently
> > use Monit for the monitoring of many processes, and it'll e-mail
Am 13.02.2014 13:04, schrieb Paul Gideon Dann:
> Does anyone know of any standard system for receiving
> notifications from systemd for unit state changes? I currently
> use Monit for the monitoring of many processes, and it'll e-mail
> me when things happen (e.g. a process was restarted). Sin
Hello all,
Does anyone know of any standard system for receiving
notifications from systemd for unit state changes? I currently
use Monit for the monitoring of many processes, and it'll e-mail
me when things happen (e.g. a process was restarted). Since
switching to systemd, it's felt a bit s
>
> That's what makes ArchLinux so awesome: once you're done, your
> understanding will be greatly expanded. As you move from project
> to project, the curve flattens out, you find it easier to understand how
> everything is fitting together, and you suddenly discover that you've
> landed in the t
On Wednesday 12 Feb 2014 21:00:54 arnaud gaboury wrote:
> > You'll have to build a custom kernel.
>
> ah...
> Another new step for me.
> fine, I learn, I learn.
That's what makes ArchLinux so awesome: once you're done, your
understanding will be greatly expanded. As you move from project
to pr
23 matches
Mail list logo
