Re: Why some say "rpm hell"
by AP
On Tue, Nov 26, 2013 at 10:26 PM, Ian Malone <ibmalone(a)gmail.com> wrote:
> (I think, google do tend to change things).
Yes.
10 years, 4 months
ssh "GSSAPIAuthentication yes"
by Timothy Murphy
I see that in /etc/ssh/ssh_config I have the above setting
in both Fedora-19 and CentOS-6.4 .
In both cases ssh (openssh) tries and fails to use gssapi-with-mic
authentication, with the message
=======================
Unspecified GSS failure. Minor code may provide more information
No Kerberos credentials available
=======================
It then goes on to use publickey authentication, successfully.
As far as I can see, this is because openssh has over-ridden
the default
# GSSAPIAuthentication no
with
GSSAPIAuthentication yes
I've googled for this, and see that some people recommend
reverting to the default No.
But I assume openssh has some reason for making this change.
What would I do if I actually wanted to use GSSAPIAuthentication?
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin 2, Ireland
10 years, 4 months
Re: Why some say "rpm hell"
by AP
On Mon, Nov 25, 2013 at 5:54 AM, Tim <ignored_mailbox(a)yahoo.com.au> wrote:
> What happens when you break mail, in one way or another: Your replies
> are not seen with the messages that they're related to. They get
> missed, they get overlooked. It gets very hard to follow an ongoing
> thread when all the messages in that thread are scattered randomly
> amongst hundreds of other messages, especially when it's important to be
> able to follow the progress of something along the thread (and no,
> quoting the entire thread in each message is not the answer). Some
> helpers will give up helping after finding it a pain to follow an
> prolonged on-going conversation. Some will give up immediately. And if
> this converstion was on traditional usenet, rather than an email list,
> you'd be needing flameproof pants by now. ;-)
Well, I agree but I simply reply in Firefox and by typing
www.gmail.com and nothing else!! This is the only way I do. Once I
log-in, I don't log-out ever (unless I have to check other gmail
account also, which I rarely use) and even if I have to use PC in
two-three days, I get directly Inbox because I didn't log out earlier!
I know since I am using Linux and with the addons like No Script, this
all is secured even when I am not logged out. But really I never
thought such technical aspects which are written above!
10 years, 4 months
optimus laptops and the 3.12 kernel
by Alexander Volovics
Reading about the 3.12 kernels I noticed that there should now
be 'dynamic' power management for laptops with an Optimus design
(DIS Nvidia + IGD Intel).
It is not quite clear what I should expect from the patches:
drastic power down for the nautilus driver or complete switching
off of the Nvidia GPU.
I tried a 3.12 kernel (from Rawhide: a no debug 3.12.1-2.fc21.x86_64)
but notice no effect at all. With this 3.12 kernel, mesa-9.2 and
xorg-x11-drv-nouveau-1.0.9-2 the battery lasts about 1 hour 40 min.
(I tried with Fed19 and Fed20 beta updated).
Using 'bbswitch' (which switches off the Nvidia GPU completely) I
get more than 3 hours battery live.
What has changed is the output of 'vgaswitcheroo', namely:
# cat /sys/kernel/debug/vgaswitcheroo/switch
0:IGD:+:Pwr:0000:00:02.0
1:DIS: :DynOff:0000:01:00.0
This seems to indicate something should happen but nothing
in the logs indicates any changes to a 'deep sleep state'
or a 'switching off' of the GPU.
Anybody else with an Optimus tried the 3.12 kernel?
And by the way how can I check the 'power state' of the DIS GPU.
AV
10 years, 4 months
rsync errors (selinux?)
by Wolfgang S. Rupprecht
For several years I've been doing an rsync across-the-lan backup for
home directories. All has worked well until recently (well, since the
fedup to f20 last night). Now backups are failing with an inscrutable
rsync error. While the errors mention selinux, I don't see any errors
in either the sending or receiving machines /var/log/secure logfiles.
exclude="
--exclude=.gvfs
--exclude=simplelock
--exclude=.popmail.lock
--exclude=SingletonLock
--exclude=SingletonCookie
--exclude=SingletonSocket
"
rsync -axHAX --log-file=/var/log/rsync.log --log-file-format="%t [%p] $host %o %f %l" --delete --delete-excluded $exclude /home/ $host:/home/
/var/log/rsync.log:
...
2013/11/24 09:35:21 [15417] rsync: rsync_xal_set: lremovexattr(""/home/wolfgang/dotfiles-f19/.local/share/zeitgeist/fts.index/record.baseB"","security.selinux") failed: Permission denied (13)
2013/11/24 09:35:21 [15417] rsync: rsync_xal_set: lremovexattr(""/home/wolfgang/dotfiles-f19/.local/share/zeitgeist/fts.index/termlist.baseA"","security.selinux") failed: Permission denied (13)
2013/11/24 09:35:21 [15417] rsync: rsync_xal_set: lremovexattr(""/home/wolfgang/dotfiles-f19/.local/share/zeitgeist/fts.index/termlist.baseB"","security.selinux") failed: Permission denied (13)
2013/11/24 09:35:21 [15417] rsync: rsync_xal_set: lremovexattr(""/home/wolfgang/hackbin/monitor-layout"","security.selinux") failed: Permission denied (13)
2013/11/24 09:35:23 [15417] rsync error: unexplained error (code 255) at rsync.c(634) [sender=3.1.0pre1]
Any ideas what's up and what I need to do to get this working again?
-wolfgang
10 years, 4 months
Better way to upgrade fc18->fc19
by Bill Davidsen
NOTE: an early draft of this question was sent somehow, ignore it
I have has miserable luck with fedup, is there a better way, anything? I really
don't want to leave this machine down for days, and the 18->19 on a test machine
took about 36 hours to complete, and another 3-4 to redo all the scripts from
the ones on other machines which all use ethN to meaningless interface names. In
18 I just changed a single script to use (or not use) biosnames, and all was
well, but on my test conversion to 19 that doesn't work, or the file was
rewritten, and I finally used the name which changes every time the machine gets
shuffled a bit.
Is there a better way than fedup, and why is it so slow?
--
Bill Davidsen <davidsen(a)tmr.com>
"'Nothing to hide' does not imply 'nothing to fear'"
- me
"AT&T could not seriously contend that a reasonable entity in its position
could have believed that the alleged domestic dragnet was legal."
-judge Vaughn R. Walker of the U.S. District Court
for the Northern District of California, EFF vs. AT&T
10 years, 4 months
Terminal signal handling
by Peter Oliver
I've started having a couple of odd issues with terminals in the last week or so on my Fedora 19 desktop machine and I think they're probably related. My laptop, also running Fedora 19, appears to be unaffected.
Sometimes, terminals are unresponsive to ^Z, and I'm unable to suspend a process by using 'kill -TSTP' on that process. However, 'kill -STOP' works. Running 'stty -a' shows 'susp = ^Z' as expected.
This affects both xterm and gnome-terminal. It affects all children of an affected process. However, sometimes if I start a new terminal from Gnome Shell it will not be affected.
A workaround is to run "exec ksh -c 'exec $SHELL'" from an affected terminal. It appears that ksh does some initialisation that bash, dash and tcsh do not.
My second problem is that alpine is sometimes unresponsive to changes in terminal size. I suspect that SIGWINCH is not being handled correctly.
See http://superuser.com/questions/667380/sigint-and-sigtstp-ignored-by-most-... for an example of someone with similar but slightly different symptoms (he has problems with SIGINT, but my SIGINT works fine).
Using 'pstree -ps $$' and then working my way up the tree with 'grep SigBlk /proc/$pid/status' shows 'SigBlk: 016717d03fdb4a00' for gnome-session but 'SigBlk: 0000000000000000' for its parents. This makes me suspect that the problem originates in gnome-session.
Any ideas?
--
Peter Oliver
10 years, 4 months
NetworkManager-l2tp requires kernel-debug ??
by Ed Greshko
I'm on an F19 system running KDE and wanting to install kde-plasma-nm-l2tp. One of its dependencies is NetworkManager-l2tp which is pulling in kernel-debug and kernel-debug-modules-extra.
Does anyone know why this would be the case?
--
Getting tired of non-Fedora discussions and self-serving posts
10 years, 4 months
Re: Why some say "rpm hell"
by AP
On Sun, Nov 24, 2013 at 6:50 PM, Tim <ignored_mailbox(a)yahoo.com.au> wrote:
> It doesn't require gmail to get messages threaded. Threading is done by
> the message headers, each message has its own message ID, each reply has
> another header saying which message ID it's in reply to, and there's
> another header listing all the message IDs that belong in the same
> thread.
> The last one (in-reply-to) is used by mail clients to group all messages
> in a thread together. The middle one (references) is used to thread
> them all together in the right order.
> Any mail client can do this. Any mail client can break this, and some
> do, by not not adding in-reply-to headers, and not adding and
> maintaining the references header. When they do that, they bugger it up
> for everyone else, as the data has been lost.
> Message threading is NOT done by whatever text is written in the subject
> line. Though some broken clients think so. Some helpful clients will
> try to use it, as well as threading headers, to fit in orphaned messages
> into a thread (broken by other crappy clients), or to break apart a new
> thread out of the middle of an existing one (when the subject line
> changed). The latter not being a particularly good idea, either.
> To see messages in their properly threaded order, one needs to use a
> mail client that isn't broken in that regard (Evolution, Thunderbird,
> and many others work), and pick the option that threads messages in the
> message list window.
> Conversely, one can unpick that option, and sort messages via some other
> criteria - such as by "date," making a mess of the order of messages
> (hint - the generational order of which message came first, is done by
> what's a reply to what, not the date that it was read or written, dates
> are coincidental, not relational).
Thanks for taking time to explain this, I am re-reading to fully grasp it.
10 years, 4 months