-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/17/2014 07:54 PM, Adriano Moura wrote:
> Does the same happens with speaker-test? (included in alsa-utils)
> Try running it like this:
> speaker-test -c 6
>
>
> 2014-03-17 2:40 GMT-03:00 Kyle Terrien :
>
>> On 03/16/2014 10:21 PM, Kyle Terri
Does the same happens with speaker-test? (included in alsa-utils)
Try running it like this:
speaker-test -c 6
2014-03-17 2:40 GMT-03:00 Kyle Terrien :
> On 03/16/2014 10:21 PM, Kyle Terrien wrote:
> > Are you using PulseAudio?
>
> D'oh! I noticed the subject line said "Pulseaudio" right after se
Hi all,
Am 09.03.2014 20:58 schrieb Friedrich Strohmaier:
> I run a Lenovo x200 which usually is put on the docking station with lid
> closed.
> after the Upgrade of systemd-208-11 -> systemd-210-3 while booting it
> immediately suspends when systemd somehow reaches suspend.service at startup.
Salutations and Felicitations.
Not long ago, a call was put out to the Arch community to assist in the
monitoring and reporting of Common Vulnerabilities and Exposures. [1][2]
The Arch community has responded by creating the Arch CVE Monitoring Team
(ACMT). The wiki page contains all of the infor
Op 17 mrt. 2014 19:25 schreef "message" het
volgende:
>
> Readers,
>
> A previously existing /home directory was mounted into the file system
during the installation process; this directory contained files in a
directory 'a'.
>
> A user was created from the root user account:
>
> useradd -M -p [pa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/17/2014 02:50 PM, Gerald Stuhrberg wrote:
> Hello,
>
> /etc/passwd does not store the password, a hashed version of the password
> is stored in /etc/shadow
>
> If the directory isn't being mounted, can you please post the contents of
> /etc/f
Hello,
/etc/passwd does not store the password, a hashed version of the password
is stored in /etc/shadow
If the directory isn't being mounted, can you please post the contents of
/etc/fstab ?
You can also check dmesg and journalctl to see if you have messages
relating to the mounting of the /ho
On 17.03.14 at 18:25, message wrote:
> Readers,
>
> A previously existing /home directory was mounted into the file system
> during the installation process; this directory contained files in a
> directory 'a'.
>
> A user was created from the root user account:
>
> useradd -M -p [password] -s /b
Readers,
Initially lxdm, gdm have been installed, but neither recognise a dvorak
keyboard. How to configure the graphical display manager so that a user
can specify the keyboard layout before to enter sign-in credentials?
--
digest-mode subscriber; please cc to maintain message thread
Readers,
A previously existing /home directory was mounted into the file system
during the installation process; this directory contained files in a
directory 'a'.
A user was created from the root user account:
useradd -M -p [password] -s /bin/bash [username'a']
After reboot, the system is
On Monday 17 Mar 2014 12:00:10 Mauro Santos wrote:
> I suspect we might have been talking about 2 different things all along.
> What I and Arnaud have been talking about is the tap interface on the
> host, not the interface inside the container, which of course should be
> properly configured by th
On 17-03-2014 10:01, Paul Gideon Dann wrote:
> I don't get this: it seems normal to me that the interface would be down
> until it's
> configured by the container, pretty much like on a normal machine. The only
> situation
> in which you can expect an interface to be up already is in a network-
On 17-03-2014 08:55, arnaud gaboury wrote:
> After I related this issue (interfaces not being UP) on the
> systemd-devel mailing list, Tom Gundersen did a commit yesterday nite
> to change this behavior. So if you run systemd-git, just upgrade and
> interfaces will now be UP, and you will be able
On Monday 17 Mar 2014 09:55:11 arnaud gaboury wrote:
> > I guess someone will have to ask about it, either in the mailing list or
> > irc, I haven't done so before because systemd-{nspawn,networkd} have
> > lots of new functionality and I'm not sure I understand them all.
>
> After I related this
> I guess someone will have to ask about it, either in the mailing list or
> irc, I haven't done so before because systemd-{nspawn,networkd} have
> lots of new functionality and I'm not sure I understand them all.
>
After I related this issue (interfaces not being UP) on the
systemd-devel mailing
15 matches
Mail list logo
