Le 11/12/2018 à 08:12, Tim via users a écrit :
> Allegedly, on or about 11 December 2018, François Patte sent:
>> For an unknown reason the installation of the new kernel wrote a
>> wrong grub.cfg pointing as the root partition an unused partition on
>> my system Strangely when I run grub2-mkco
On 12/11/18 3:10 PM, Tim via users wrote:
> Allegedly, on or about 8 December 2018, sean darcy sent:
>> What I want is:
>>
>> nameserver 127.0.0.1
>> nameserver
> Is the DHCP server configurable by you? If so, then enter the list of
> DNS servers that you want clients to use into the DHCP serve
On 12/11/18 4:51 PM, Ed Greshko wrote:
> dnssec is a concern
is *not* a concern
--
Right: I dislike the default color scheme Wrong: What idiot picked the default
color scheme
___
users mailing list -- users@lists.fedoraproject.org
To unsubscrib
On 11/12/2018 12:37 am, Rick Stevens wrote:
Also, how did you get it to start?
Once I found the right log file I saw that there were a few incompatible
entries in my.cnf
I'll take a look at the other errors when I'm awake :)
___
users mailing list
On 11/12/2018 12:37 am, Rick Stevens wrote:
Yup. Some of those are fixable via mysql_upgrade, others are fairly
important and appear to be caused by using a newer mysqld that's not
backwards compatible with your previous version. You didn't say which
version of MySQL you were running before and
Hello,
On Sun, 28 May 2017 21:20:13 +0200 Branko Grubic wrote:
> On Sun, 2017-05-28 at 15:12 +0200, wwp wrote:
> > Hello there,
> >
> > (after a looong time not using Fedora, just back to it!)
> >
> > I've tried installing Fedora on a Zotac Zbox CI327 (Intel Celeron
> > N3450 inside) but this
Hello Danny and everybody else,
MariaDB & MySQL maintainer here!
I see I made it late, however I'll drop here some more answers & tips:
> I don't know where else to ask.
This is a right place.
Other good places could be Fedora IRC, create bugzilla ticket
... or write me personal mail as a last r
Folks,
this morning I rebooted one of my systems. The system ended up
dropping into emergency mode. I ran journalctl -xb to see why it failed
to boot and I saw the following errors:
Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symbol gfn_to_memslot
(err -2)
Dec 11 08:02:46 terrapin ker
Le 11/12/2018 à 17:34, Paolo Galtieri a écrit :
> Folks,
> this morning I rebooted one of my systems. The system ended up
> dropping into emergency mode. I ran journalctl -xb to see why it failed
> to boot and I saw the following errors:
>
> Dec 11 08:02:46 terrapin kernel: kvmgt: Unknown symb
On 12/11/18 12:54 AM, Samuel Sieb wrote:
On 12/10/18 4:22 PM, sean darcy wrote:
I'm trying to get the interface on a multi-homed machine named "internal"
ifconfig
enp1s0: flags=4099 mtu 1500
ether 50:7b:9d:0b:8a:ab txqueuelen 1000 (Ethernet)
Is that the full ifconfig output for th
On 12/11/18 11:52 AM, sean darcy wrote:
On 12/11/18 12:54 AM, Samuel Sieb wrote:
On 12/10/18 4:22 PM, sean darcy wrote:
I'm trying to get the interface on a multi-homed machine named
"internal"
ifconfig
enp1s0: flags=4099 mtu 1500
ether 50:7b:9d:0b:8a:ab txqueuelen 1000 (Ethernet)
Hi,
On my Fedora 29, the command dvipdfmx does not work:
$ rpm -q texlive-dvipdfmx
texlive-dvipdfmx-20180414-28.fc29.x86_64
$ dvipdfmx
bash: dvipdfmx: command not found
Indeed, the executable file '/usr/bin/dvipdfmx' is a broken link that
points to a nonexistent file:
$ ls -al /usr/bin/dvipdfmx
On 12/11/18 8:52 AM, sean darcy wrote:
> On 12/11/18 12:54 AM, Samuel Sieb wrote:
>> On 12/10/18 4:22 PM, sean darcy wrote:
>>> I'm trying to get the interface on a multi-homed machine named
>>> "internal"
>>>
>>> ifconfig
>>> enp1s0: flags=4099 mtu 1500
>>> ether 50:7b:9d:0b:8a:ab txque
(Samuel said)
> I would say to comment out all the lines from 91-98.
Done. Re-booted. No more error messages before the grub menu appears.
Thank-you!
Now to the greater problem...
When I upgraded to Fedora-28, the text of the grub menu was
significantly down-sized. It also seems to be a (d
Den 2018-12-11 kl. 18:43, skrev Marco Guazzone:
> Hi,
>
> On my Fedora 29, the command dvipdfmx does not work:
>
> $ rpm -q texlive-dvipdfmx
> texlive-dvipdfmx-20180414-28.fc29.x86_64
> $ dvipdfmx
> bash: dvipdfmx: command not found
>
> Indeed, the executable file '/usr/bin/dvipdfmx' is a broken
On Sun, 09 Dec 2018 15:27:32 -0700, stan wrote:
> On Sun, 9 Dec 2018 19:00:25 + (UTC)
> I Beartooth wrote:
>
>> I do some of my email and all of my Gmane activity (including
>> this list) at the address above, from my local access provider,
>> Comcast; but I do most of my email (and my
On Tue, 11 Dec 2018 19:04:17 + (UTC)
Beartooth wrote:
> According to them, my own firewall cuts us (i.e., our whole IP)
> off when we try too many times too soon to connect. (We do that, of
> course, by hitting up arrow and Enter.)
>
> Am I making any more sense yet?
I think I un
On 12/11/18 11:04 AM, Beartooth wrote:
We've been unable for days to connect to our email at my domain;
when we try our usual ssh -p , we get
nothing but eventually "Connection timed out" -- even after having left
it all night.
How are you using ssh to get your email?
What port are you us
On 12/11/18 11:04 AM, Beartooth wrote:
> On Sun, 09 Dec 2018 15:27:32 -0700, stan wrote:
>
>> On Sun, 9 Dec 2018 19:00:25 + (UTC)
>> I Beartooth wrote:
>>
>>> I do some of my email and all of my Gmane activity (including
>>> this list) at the address above, from my local access provider,
On Tue, 11 Dec 2018 12:53:03 -0700, stan wrote:
> I think I understand better what is happening. Whether I can help I
> don't know. A summary:
>
> You have no problem with your ISP (Comcast). Your problem is with the
> third party that handles your private domain for email. When you try to
>
On Tue, Dec 11, 2018 at 8:00 PM Jon Ingason wrote:
>
> You need to install texlive-xetex-7:20180414-28.fc29.x86_64 which
> provide /usr/bin/xdvipdfmx.
>
> --
> Regards
>
> Jon Ingason
>
Hi Jon,
Thank you very much. It works.
I'll add your suggestion in the reported bug page.
Best regards,
Ma
On Tue, 11 Dec 2018 11:59:20 -0800, Samuel Sieb wrote:
> On 12/11/18 11:04 AM, Beartooth wrote:
>> We've been unable for days to connect to our email at my domain;
>> when we try our usual ssh -p , we
>> get nothing but eventually "Connection timed out" -- even after having
>> left it all ni
On Sat, 8 Dec 2018 23:29:35 -0500, Robert McBroom via users
wrote:
> Upgraded to F29. On KDE desktop starting EMACS in a privileged command
> window locks the system. Starting EMACS with sudo locks the system. On
> XFCE4 normal EMACS access with privilege.
>
> Other file managers don't like ro
On 12/11/18 12:11 PM, Beartooth wrote:
ssh -v bearto...@beartooth.info -p 999
debug1: Connecting to beartooth.info [208.100.51.176] port 999.
debug1: connect to address 208.100.51.176 port 999: Connection timed out
ssh: connect to host beartooth.info port 999: Connection timed out
I can connect
On 12/11/18 12:53 PM, Samuel Sieb wrote:
> On 12/11/18 12:11 PM, Beartooth wrote:
>> ssh -v bearto...@beartooth.info -p 999
>> debug1: Connecting to beartooth.info [208.100.51.176] port 999.
>> debug1: connect to address 208.100.51.176 port 999: Connection timed out
>> ssh: connect to host beartoot
On 12/12/18 5:25 AM, Rick Stevens wrote:
> I just did the same. From a Spectrum IP here in Orange County, CA,
> the system doesn't respond (and Spectrum is a Comcast company).
>
> From a monitoring system in our ASN (a /22 network), it works peachy:
Interesting
Could you try it a second time?
On Tue, 11 Dec 2018 12:53:03 -0800, Samuel Sieb wrote:
> On 12/11/18 12:11 PM, Beartooth wrote:
>> ssh -v bearto...@beartooth.info -p 999 debug1: Connecting to
>> beartooth.info [208.100.51.176] port 999.
>> debug1: connect to address 208.100.51.176 port 999: Connection timed
>> out ssh: connect t
On 12/11/18 1:52 PM, Ed Greshko wrote:
> On 12/12/18 5:25 AM, Rick Stevens wrote:
>> I just did the same. From a Spectrum IP here in Orange County, CA,
>> the system doesn't respond (and Spectrum is a Comcast company).
>>
>> From a monitoring system in our ASN (a /22 network), it works peachy:
>
>
On 12/11/18 1:54 PM, Beartooth wrote:
On Tue, 11 Dec 2018 12:53:03 -0800, Samuel Sieb wrote:
I can connect to that port fine. Do you have something like fail2ban on
the server that would block your connection? Can you try connecting
from another location?
I thought I had fail2ban, bu
On 12/12/18 6:12 AM, Rick Stevens wrote:
> On 12/11/18 1:52 PM, Ed Greshko wrote:
>>
>> I get the feeling the folks at Netwisp, Inc. are doing something to
>> "prevent" hacking.
> Yup. Tried three times from our ASN from two different machines. All
> the test machines are behind a firewall (Cisco
On Tue, 11 Dec 2018 14:23:59 -0800, Samuel Sieb wrote:
> On 12/11/18 1:54 PM, Beartooth wrote:
>> On Tue, 11 Dec 2018 12:53:03 -0800, Samuel Sieb wrote:
>>> I can connect to that port fine. Do you have something like fail2ban
>>> on the server that would block your connection? Can you try
>>> co
On 12/11/18 3:04 PM, Beartooth wrote:
Hoo, boy! I haven't so much as heard of traceroute in ten or
fifteen years, and never did grep its uses. I can look it up, of course,
but it might be worth your while to just tell me a command (and to use it
as root if that should be desirable).
tra
On 12/11/2018 04:04 PM, Beartooth wrote:
Hoo, boy! I haven't so much as heard of traceroute in ten or
fifteen years, and never did grep its uses. I can look it up, of course,
but it might be worth your while to just tell me a command (and to use it
as root if that should be desirable).
On 12/11/18 2:36 PM, Ed Greshko wrote:
> On 12/12/18 6:12 AM, Rick Stevens wrote:
>> On 12/11/18 1:52 PM, Ed Greshko wrote:
>>>
>>> I get the feeling the folks at Netwisp, Inc. are doing something to
>>> "prevent" hacking.
>> Yup. Tried three times from our ASN from two different machines. All
>>
On 12/12/18 7:15 AM, Samuel Sieb wrote:
>
> traceroute beartooth.info
> traceroute -I beartooth.info
> traceroute -T -p 999 beartooth.info
>
> Some (or all) or those might require root, so best to just use root.
I was able to get the failure condition again.
This is from a working system
[r
On 12/11/18 12:54 PM, Rick Stevens wrote:
On 12/11/18 8:52 AM, sean darcy wrote:
On 12/11/18 12:54 AM, Samuel Sieb wrote:
On 12/10/18 4:22 PM, sean darcy wrote:
I'm trying to get the interface on a multi-homed machine named
"internal"
ifconfig
enp1s0: flags=4099 mtu 1500
ether 50:7
Allegedly, on or about 11 December 2018, Joe Zeff sent:
> If you can't ping someplace, traceroute will show you where the
> problem is, because it will stop getting responses.
Though you still have to think about it (it's only part of a
diagnosis). That failure just means the device doesn't respo
On 12/12/18 9:44 AM, Ed Greshko wrote:
> I will check again in a few hours, but I think the defense may drop after a
> time.
Yep, 1 hour later and "traceroute -n -T -p 999 beartooth.info" reaches
208.100.51.176.
--
Right: I dislike the default color scheme Wrong: What idiot picked the default
On 12/11/18 3:34 PM, George Avrunin wrote:
On Sat, 8 Dec 2018 23:29:35 -0500, Robert McBroom via users
wrote:
Upgraded to F29. On KDE desktop starting EMACS in a privileged command
window locks the system. Starting EMACS with sudo locks the system. On
XFCE4 normal EMACS access with privilege.
On 12/11/18 9:59 AM, home user via users wrote:
Now to the greater problem...
When I upgraded to Fedora-28, the text of the grub menu was
significantly down-sized. It also seems to be a (darker?) gray. It is
split into two pieces into the corners of the left side of the left
monitor. It is
On 12/11/18 9:22 AM, sean darcy wrote:
cat /etc/udev/rules.d/40-persistent-net.rules
# this is the pci ethernet port
# udevadm info -a -p /sys/class/net/enp1s0/
# r8169 :01:00.0 eth0: RTL8168g/8111g, 50:7b:9d:0b:8a:ab, XID
50900880, IRQ 44
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
AT
On 12/4/18 8:07 AM, Tom Horsley wrote:
I have a GeForce GTX 750 Ti in my system at work, using the
rpmfusion nvidia drivers (because nouveau can't go more than
a few hours without crashing). Every so often, when the X
server starts or is restarted by logging out, the screen will
go blank and the
$ gnome-session &
(process:1024): dconf-WARNING **: 00:49:24.721: unable to open file
'/etc/dconf/db/local': /etc/dconf/db/local: invalid gvdb header; expect
degraded performance
(process:1024): dconf-WARNING **: 00:49:24.721: unable to open file
'/etc/dconf/db/site': /etc/dconf/db/site: inva
On 12/11/18 10:40 PM, Robert McBroom via users wrote:
Looked in the path and no such files were there. Created them but the
messages still occur. What creates the real ones in the correct format?
You wouldn't have created them in the correct format. Those files are
not owned by any package.
Hi all,
I've experienced some strange behavior on Fedora 28 client systems. I have some
of them virtualized on a qemu-kvm hypervisor. All these systems take the
hypervisor uptime as their own. This is really annoying, since I can not
determine how long a host is up.
If I take a look in the boo
45 matches
Mail list logo
