On Tue, Feb 25, 2014 at 4:03 AM, Nicolas Sebrecht wrote:
> The 20/02/14, Canek Peláez Valdés wrote:
>
>> > Thinking about this more, since apparently using a separate profile may
>>just
>> > be 'overkill', how about something simpler, like, for example, using
>> > eselect...
>> >
>> > Somethin
Am 25.02.2014 12:38, schrieb Nicolas Sebrecht:
> The way systemd services handle network whatever "network manager" you
> enable is the last thing preventing me from using systemd on servers.
> Seting up manual advanced setups on systemd looks crappy (if even
> possible with the provided tools) co
On Feb 25, 2014 10:40 AM, "Canek Peláez Valdés" wrote:
>
> On Tue, Feb 25, 2014 at 5:38 AM, Nicolas Sebrecht
wrote:
>
> [snip]
>
> > The way systemd services handle network whatever "network manager" you
> > enable is the last thing preventing me from using systemd on servers.
> > Seting up manua
What is the largest thread of emails ever gentoo-user@lists.gentoo.org
The debian just voted..
could possibly be a winner?
Or can anyone else remember back into the depths of time.
Long live Gentoo that's all I can say. Intelligent, well argued (but
not always agreeing) emails chains
On Tue, Feb 25, 2014 at 10:52 PM, Grant Edwards
wrote:
> On 2014-02-25, Grant Edwards wrote:
>
> > On a newly installed system, I'm getting error messages from vixie cron
> > about PAM authentication errors:
> >
> > Feb 25 09:52:01 alpha crond[23085]: (root) PAM ERROR (Authentication
> failure)
>
On 2014-02-25, Grant Edwards wrote:
> On a newly installed system, I'm getting error messages from vixie cron
> about PAM authentication errors:
>
> Feb 25 09:52:01 alpha crond[23085]: (root) PAM ERROR (Authentication failure)
> Feb 25 09:52:01 alpha crond[23085]: (root) FAILED to authorize user
On Tue, Feb 25, 2014 at 9:29 PM, Grant Edwards wrote:
> On a newly installed system, I'm getting error messages from vixie cron
> about PAM authentication errors:
>
> Feb 25 09:52:01 alpha crond[23085]: (root) PAM ERROR (Authentication
> failure)
> Feb 25 09:52:01 alpha crond[23085]: (root) FAILED
On Tue, Feb 25, 2014 at 5:38 AM, Nicolas Sebrecht wrote:
[snip]
> The way systemd services handle network whatever "network manager" you
> enable is the last thing preventing me from using systemd on servers.
> Seting up manual advanced setups on systemd looks crappy (if even
> possible with the
On Mon, Feb 24, 2014 at 3:09 AM, thegeezer wrote:
[snip]
> using openrc if i reboot a system that requires fsck on /mnt/data it
> will do an fsck. but not log anything anywhere about the result, which
> is why i put this as a pro.
Oh, I see; I hadn't understood this.
> does systemd have config
On Tue, Feb 25, 2014 at 6:58 AM, Alan McKinnon wrote:
> On 25/02/2014 14:40, Tanstaafl wrote:
>> On 2014-02-24 4:48 PM, Canek Peláez Valdés wrote:
>>> In Gentoo you need systemd, but that's a decision from the Gentoo
>>> maintainers. They do the job, they make the choices.
>>
>> Interesting. Now
On a newly installed system, I'm getting error messages from vixie cron
about PAM authentication errors:
Feb 25 09:52:01 alpha crond[23085]: (root) PAM ERROR (Authentication failure)
Feb 25 09:52:01 alpha crond[23085]: (root) FAILED to authorize user with PAM
(Authentication failure)
Feb 25 09:53
On 25/02/2014 14:40, Tanstaafl wrote:
> On 2014-02-24 4:48 PM, Canek Peláez Valdés wrote:
>> In Gentoo you need systemd, but that's a decision from the Gentoo
>> maintainers. They do the job, they make the choices.
>
> Interesting. Now I have to spin off a new thread as to why this decision
> was
On 2014-02-24 4:48 PM, Canek Peláez Valdés wrote:
In Gentoo you need systemd, but that's a decision from the Gentoo
maintainers. They do the job, they make the choices.
Interesting. Now I have to spin off a new thread as to why this decision
was made if it isn't forced by GNOME itself...
The 23/02/14, Canek Peláez Valdés wrote:
> >> networkd (again, netctl is the command-line front-end) is not for
> >> enterprise networks; on the contrary, is for the trivial cases. For
> >> example, in a little web server I administer I have:
> >>
> >> $ cat /etc/systemd/system/network.service
> >
The 20/02/14, Canek Peláez Valdés wrote:
> > Thinking about this more, since apparently using a separate profile may
>just
> > be 'overkill', how about something simpler, like, for example, using
> > eselect...
> >
> > Something like:
> >
> > # eselect init list
> > Available init systems:
> >
15 matches
Mail list logo