On 18/1/17 7:51 am, Ed Greshko wrote:
On 01/18/17 04:39, Stephen Morris wrote:
Thanks Ed. I haven't written my own systemd units as I haven't investigated how
to do
that, so at the moment I don't have the expertise to do so.
I've written in another response to my original thread that I may hav
On 18/1/17 8:14 am, Rick Stevens wrote:
On 01/17/2017 01:12 PM, Stephen Morris wrote:
On 18/1/17 6:40 am, Rick Stevens wrote:
On 01/17/2017 12:12 PM, Stephen Morris wrote:
On 17/1/17 7:49 am, Rick Stevens wrote:
On 01/16/2017 12:22 PM, Joe Zeff wrote:
On 01/16/2017 12:17 PM, Stephen Morris w
On 18/1/17 7:44 am, Terry Polzin wrote:
In my experience, you won't get any further than lsusb "seeing" the
device if you haven't the firmware. It may be blacklisted.
How do I determine if it or wifi has been blacklisted? On reflecting on
this issue there is a possibility that I may have manual
How to install all games with dnf?
I tried both:
$ dnf group install with-optional games
and
$ dnf group install games
but my children still complain they do not have all the games they had
before I reinstalled the system.
Cheers,
Frédéric
___
users ma
for checkout list of all groups run this command :
#dnf group list
and for install group use this command :
#dnf group install "Games and Entertainment"
On Wed, Jan 18, 2017 at 1:58 PM, Frédéric Bron
wrote:
> How to install all games with dnf?
> I tried both:
> $ dnf group install wi
On 01/18/17 18:28, Frédéric Bron wrote:
> How to install all games with dnf?
> I tried both:
> $ dnf group install with-optional games
> and
> $ dnf group install games
>
> but my children still complain they do not have all the games they had
> before I reinstalled the system.
>
You may want to
One of my servers was a bit "unresponsive". After waiting about 20 seconds
for an ssh connection, the root shell seemed fine, but top showed this:
top - 06:31:36 up 3 days, 21:37, 2 users, load average: 6.00, 6.00, 6.00
Tasks: 294 total, 1 running, 277 sleeping, 0 stopped, 16 zombie
%Cpu
On Wed, 2017-01-18 at 00:42 +, James Hogarth wrote:
> On 17 Jan 2017 10:44 pm, "Greg Woods" wrote:
>
>
> On Tue, Jan 17, 2017 at 3:23 PM, Rick Stevens wrote:
>
> > I really don't care about the performance of Windows. I
>
>
> Up to a point, I don't either. But the performance is so bad u
On Tue, 2017-01-17 at 20:10 -0500, Tom Horsley wrote:
> On Tue, 17 Jan 2017 16:58:45 -0800
> Samuel Sieb wrote:
>
> > Not entirely true. There was some work done on a virtio GL driver. I
> > don't have the references handy, but there was a working Linux Mesa
> > driver for it. Any other OS
Hello,
When you log from the graphics interface (gnome) and provide the
password, if the system is slow (long response time), then the
password can appear in clear !!!
This my be annoying!
===
Patrick DUPRÉ | | email: pdu..
On 01/18/17 15:51, Patrick Dupre wrote:
Hello,
When you log from the graphics interface (gnome) and provide the
password, if the system is slow (long response time), then the
password can appear in clear !!!
Hi Patrick,
having the same issue if booting into runlevel 3 and then login:
if I'm t
On 01/18/2017 03:41 AM, Sam Varshavchik wrote:
top - 06:31:36 up 3 days, 21:37, 2 users, load average: 6.00, 6.00, 6.00
Tasks: 294 total, 1 running, 277 sleeping, 0 stopped, 16 zombie
Why do you have 16 zombies after just under 4 days?
___
use
On 01/18/2017 08:25 AM, Joachim Backes wrote:
> On 01/18/17 15:51, Patrick Dupre wrote:
>> Hello,
>>
>> When you log from the graphics interface (gnome) and provide the
>> password, if the system is slow (long response time), then the
>> password can appear in clear !!!
>
> Hi Patrick,
>
> having
On 01/18/2017 03:41 AM, Sam Varshavchik wrote:
> One of my servers was a bit "unresponsive". After waiting about 20
> seconds for an ssh connection, the root shell seemed fine, but top
> showed this:
>
> top - 06:31:36 up 3 days, 21:37, 2 users, load average: 6.00, 6.00, 6.00
> Tasks: 294 total,
On 01/18/2017 09:20 AM, Rick Stevens wrote:
And yes, I agree...systemd is a spectacular failure.
This March, systemd will celebrate its 7th birthday. Complaints like
this are about as useful as King Canute's attempt to hold back the tide.
Don't you think it's time that you learned to stop w
On 01/18/2017 01:54 AM, Stephen Morris wrote:
> On 18/1/17 7:44 am, Terry Polzin wrote:
>> In my experience, you won't get any further than lsusb "seeing" the
>> device if you haven't the firmware. It may be blacklisted.
> How do I determine if it or wifi has been blacklisted? On reflecting on
> t
On 1/18/2017 12:24 PM, Rick Stevens wrote:
That's normal. The system (or shell) is echoing the input because the
program you expect to consume the input isn't running or hasn't
finished initializing yet. What do you expect the system to do? Not
echo anything unless explicitly told to?
Perhaps I
On 01/18/2017 09:33 AM, Joe Zeff wrote:
> On 01/18/2017 09:20 AM, Rick Stevens wrote:
>> And yes, I agree...systemd is a spectacular failure.
>
> This March, systemd will celebrate its 7th birthday. Complaints like
> this are about as useful as King Canute's attempt to hold back the tide.
> Don'
On 01/18/2017 10:09 AM, Tom Rivers wrote:
> On 1/18/2017 12:24 PM, Rick Stevens wrote:
>> That's normal. The system (or shell) is echoing the input because the
>> program you expect to consume the input isn't running or hasn't
>> finished initializing yet. What do you expect the system to do? Not
>
On 01/18/2017 10:18 AM, Rick Stevens wrote:
On 01/18/2017 09:33 AM, Joe Zeff wrote:
On 01/18/2017 09:20 AM, Rick Stevens wrote:
And yes, I agree...systemd is a spectacular failure.
This March, systemd will celebrate its 7th birthday. Complaints like
this are about as useful as King Canute's
Okay ... now I have your attention ...
A funny thing happened to me the other day ...
I tried upgrading a Fedora 22 VM which was running on about 30 different
VMware architectures to Fedora 23. All but a couple worked perfectly but a
couple (Both Dell servers) didn't. On these I can only describe
On 1/18/2017 1:25 PM, Rick Stevens wrote:
That's not what's happening here. The user is starting a program, then
immediately typing in the expected password before the program starts,
essentially making use of the type-ahead capability of the shell.
The program hasn't, well, "registered" its stdi
On 17/1/17 6:36 am, Stephen Morris wrote:
Hi,
My Nas device now fails to mount at boot time via the CIFS
definition in fstab but the corresponding NFS definition mounts quite
happily. Also after the system comes up and I log into KDE I can
manually mount the CIFS device. As far as I am a
On Thu, 19 Jan 2017 07:02:28 +1100
Stephen Morris wrote:
> Given
> that both the CIFS and NFS mount points are being mounted in parallel it
> is now potentially looking like SYSTEMD is problematic in its ability to
> handle those mounts in parallel properly.
Nah, it isn't parallel mounting, it
Trying to compile a hello world cpp on Fedora 25 with clang++ and libc++.
sudo dnf install clang libcxx-devel
#include
#include
int main()
{
std::string a = "abc";
std::cout << a;
}
clang++ -stdlib=libc++ hello.cpp
This results in a bunch of linker errors. What am I missing?
Best r
Hello,
My system:
description: Laptop
product: Inspiron 13-5368 (073B)
vendor: Dell Inc.
width: 64 bits
capabilities: smbios-2.8 dmi-2.8 smp vsyscall32
configuration: boot=normal chassis=docking sku=073B uuid=44454C4C-
5700-1035-8043-B6C04F564232
*-core
description:
Check dmesg with intel driver fifo underrun.
2017-01-18 21:36 GMT+01:00 Brian Millett :
> Hello,
> My system:
> description: Laptop
> product: Inspiron 13-5368 (073B)
> vendor: Dell Inc.
> width: 64 bits
> capabilities: smbios-2.8 dmi-2.8 smp vsyscall32
> configuration: bo
On 19/1/17 3:43 am, Rick Stevens wrote:
On 01/18/2017 01:54 AM, Stephen Morris wrote:
On 18/1/17 7:44 am, Terry Polzin wrote:
In my experience, you won't get any further than lsusb "seeing" the
device if you haven't the firmware. It may be blacklisted.
How do I determine if it or wifi has bee
On 19/1/17 6:11 am, Tom Horsley wrote:
On Thu, 19 Jan 2017 07:02:28 +1100
Stephen Morris wrote:
Given
that both the CIFS and NFS mount points are being mounted in parallel it
is now potentially looking like SYSTEMD is problematic in its ability to
handle those mounts in parallel properly.
Nah,
On 01/18/2017 01:39 PM, Stephen Morris wrote:
What I don't understand is when there is a problem why it is always the
CIFS mount that is the one that fails, I would have expected it to be
random as to which one is the one that fails.
Is it possible that the NAS doesn't handle it well when both m
On Wed, 18 Jan 2017 21:21:17 +0100
cen wrote:
> Trying to compile a hello world cpp on Fedora 25 with clang++ and
> libc++.
>
> sudo dnf install clang libcxx-devel
>
> #include
> #include
>
> int main()
> {
> std::string a = "abc";
> std::cout << a;
> }
>
> clang++ -stdlib=libc++
That is what worries me actually. Apparently libc++abi has to be linked
to libc++ but that is not the case with current package:
ldd /usr/lib64/libc++.so
linux-vdso.so.1 (0x7ffe1c7d8000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x7f09d5072000)
libc.so.6 => /lib64/libc.so.6
On Wed, 18 Jan 2017 06:22:29 +, arnaud gaboury wrote:
> > > At the begining of my build, I need:
> > > - mkdir src/github.com/mattermost
> > > -unzip the source in src/github.com/mattermost/plateform-master
> > > - cd src/github.com/mattermost/plateform-master to start make.
> >
> > Why do y
On Wed, 18 Jan 2017 23:27:03 +0100
cen wrote:
> That is what worries me actually. Apparently libc++abi has to be
> linked to libc++ but that is not the case with current package:
>
> ldd /usr/lib64/libc++.so
> linux-vdso.so.1 (0x7ffe1c7d8000)
> libpthread.so.0 => /lib64/libpthread.
On Wed, 2017-01-18 at 10:29 -0800, Joe Zeff wrote:
> On 01/18/2017 10:18 AM, Rick Stevens wrote:
> > On 01/18/2017 09:33 AM, Joe Zeff wrote:
> > > On 01/18/2017 09:20 AM, Rick Stevens wrote:
> > > > And yes, I agree...systemd is a spectacular failure.
> > >
> > > This March, systemd will celebrate
On 01/18/2017 01:21 PM, Stephen Morris wrote:
> On 19/1/17 3:43 am, Rick Stevens wrote:
>> On 01/18/2017 01:54 AM, Stephen Morris wrote:
>>> On 18/1/17 7:44 am, Terry Polzin wrote:
In my experience, you won't get any further than lsusb "seeing" the
device if you haven't the firmware. It
On 01/18/2017 02:08 PM, Samuel Sieb wrote:
> On 01/18/2017 01:39 PM, Stephen Morris wrote:
>> What I don't understand is when there is a problem why it is always the
>> CIFS mount that is the one that fails, I would have expected it to be
>> random as to which one is the one that fails.
>>
> Is it
On Wed, Jan 18, 2017 at 04:37:34PM -0800, Rick Stevens wrote:
> I think the issue here is that systemd is non-determinate as to when
> things actually get done. systemd simply spawns off some command, flags
> itself saying "Ok, that's done" and then goes off on its merry way. It
> doesn't verify th
Once upon a time, Rick Stevens said:
> So, it launches
> the network, says the network is up and moves along even though the
> network isn't actually up. Your mount is sometimes attempted with a
> functioning network and sometimes not. You're left to figure out why.
That's not true. systemd dist
Allegedly, on or about 18 January 2017, Joe Zeff sent:
> I made that comment just to get in a reference to a movie from the
> '60s, and that's all the response I get?
I'm tempted to make some comment about Bat Guano...
--
Boilerplate: All mail to my mailbox is automatically deleted, there is
Once upon a time, Tim said:
> Allegedly, on or about 18 January 2017, Joe Zeff sent:
> > I made that comment just to get in a reference to a movie from the
> > '60s, and that's all the response I get?
>
> I'm tempted to make some comment about Bat Guano...
If you do that, you'll have to answer
On 19/1/17 11:28 am, Matthew Miller wrote:
On Wed, Jan 18, 2017 at 04:37:34PM -0800, Rick Stevens wrote:
I think the issue here is that systemd is non-determinate as to when
things actually get done. systemd simply spawns off some command, flags
itself saying "Ok, that's done" and then goes of
42 matches
Mail list logo
