Re: Fedora Notifications System.
by Mahmoud Abdul Jawad
On Thu, Aug 26, 2010 at 5:07 PM, Matthias Clasen <mclasen(a)redhat.com> wrote:
> On Thu, 2010-08-26 at 06:30 +0200, Kevin Kofler wrote:
>
> I have to agree with Kevin here (!). Employing a notification system in
> parallel to the ones already provides by the desktop environment is a
> total nonstarter.
>
in fact, your point means there will be two versions, KDE version &
other desktops version, which imo is not the best call.
however, after seeing the big number of the alternative solutions, &
the bigger number of the disagreements, i'm going to stop for a while
before i make sure whether i should continue or not.
--
Regards,,
Mahmoud Abdul Jawad
@meGenius
13 years, 8 months
rpm -e question
by JD
Running rpm -e <pkgname>
does not delete the binaries and other files that
were installed by the package; and I see no option
to rpm in the man page to remove the package's files.
So far I have had to remove them manually after I
remove the package. But that is a hit and miss operaton
because I cannot always remember to do
rpm -ql --provides <pkgname>
and delete the files listed (after doing rpm -e).
I know there are dangers to providing such a feature
and use it accidentally and do damage:
for example, you need the ability to boot different
version of the kernel.
Since a kernel package also installs header files in /usr/include
and firmware files in /lib, then such an accidental usage
of such an option could wreak havoc.
But isn't that always the case with so many other commands,
which if they are used without full knowledge of the consequences,
then indeed we get to be hit by those consequences.
Does anyone agree that rpm should have an option such as
--delete-files to delete tha package's installed files ??
13 years, 8 months
No VLC snapshot -
by Bob Goodwin
I was quite pleased when I found vlc could take a snapshot from a
video stream. Yesterday I found it no longer works and I recalled a
recent vlc yum update. From the log file:
Aug 23 07:30:47 Updated: vlc-core-1.1.3-1.fc13.i686
Aug 23 07:31:02 Updated: vlc-1.1.3-1.fc13.i686A
[Up to date F-13 Linux box9 2.6.33.8-149.fc13.i686.PAE #1 SMP
Tue Aug 17 22:39:27 UTC 2010 i686 i686 i386 GNU/Linux]
Has anyone else observed this problem or is it just me?
Bob
--
13 years, 8 months
faster /dev/random
by Wolfgang S. Rupprecht
Is there an approved way to increase the speed at which the random pool
for /dev/random fills up? I'm playig with dnssec and getnerating 2k rsa
keys is taking up to 3 hours. I've been googling a bit and Intel x86_64
machines seem to have random number hardware built in (perhaps also
AMD???) Is there a way to funnel this into the entropy pool?
-wolfgang
--
Wolfgang S. Rupprecht http://www.wsrcc.com/wolfgang/ (IPv6-only)
13 years, 8 months
Random kernel update breakage
by Sam Varshavchik
Every once in a while, something breaks when a kernel update gets installed.
It doesn't happen every time, I'd say that once in every thirty or so kernel
updates, grub fails to come up after a subsequent reboot.
This is just a minor annoyance -- I'd have to boot the install CD in rescue
mode, let it mount Fedora on /mnt/sysimage, chroot to it, and execute
/sbin/grub-install -- but I'm wondering if anyone else is seeing this.
This just happened again -- after installing 2.6.33.8-149.fc13, rebooting my
laptop only results in a black screen, with a BIOS cursor uselessly blinking
away in the top-left corner. Whip out the rescue CD, and now a few minutes
later I'm back in business.
But then, I updated a different server to 2.6.33.8-149.fc13, and it booted
the new kernel just fine. Previously, this same server got similarly
de-grubbed by an earlier kernel update, but the laptop had no issues being
updated to the same kernel.
13 years, 8 months
Re: Fedora Notifications System.
by g
On 08/24/2010 06:41 PM, Mahmoud Abdul Jawad wrote:
<snip>
> thanx for the worthless discussion with you, g
you are most welcome.
> i guess your (ZERO) points about the application are very great, & i'm
> going to implement them all.
if you read back thru post, you will see that i did post a '+1' to point
made that i fully agree with and did not see need to write them all
over again.
personally, see no benefit of adding something else to desktop that will
somewhere along the line be a potential problem. especially when desktops,
ie, kde, are always changing and in changing, breaking.
therefore, to insure that users are notified, notices should be sent thru
list subscriptions.
i subscribe to user, announce, xen, admin, redhat security, and kde list
and i am considering subscribing to dev list.
in so doing, i do keep up with most of what is happening and i see no
reason why notifications can not be cross posted to list to inform one
and all when needed.
nor do i see any reason that there would be any complaints of such cross
posting by subscribers of list.
something that you may not have given consideration to, what happens
when a fedora user has fedora system off for a few days of he is using
another distribution and is still reading his emails and something
critical comes up like an exploit that can wipe entire installation as
soon as he runs a program that has a time delayed bomb in it and this
bomb is set for while he is out of fedora?
very simple, he loses everything. why, because he was running a distrib
that was unaware and he did not get notified because notification did not
come via email.
this to me is a big flaw in a very fine distribution.
there is nothing wrong with your concept if you not only have a
notification system and an email notification and ability to disable
notification system.
another plus would be if notification system was designed to watch for
emails with a key in them that would trigger notification system to pop
up a notice on desktop, as long as feature had ability to disable.
another flaw in automatic checking is what would happen if crazies decided
to run a DoS for url that check is made thru. in so running DoS, they
intercept and respond with a bogus 'all clear' of send a false 'danger'
with an update notice. then when user tries to run update, another DoS is
running against url for updates and another intercept is set up to download
some form of malware or bomb.
yes, this is a lot of 'what ifs', but what if it was done?
therefore, i still say, *BAD IDEA*. it gains nothing.
in closing, thank you for posting 'text/plain'. now your post will be
easier to follow and read by others who trap 'text/html'.
--
peace out.
tc,hago.
g
.
****
in a free world without fences, who needs gates.
**
help microsoft stamp out piracy - give linux to a friend today.
**
to mess up a linux box, you need to work at it.
to mess up an ms windows box, you just need to *look* at it.
**
learn linux:
'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html
'The Linux Documentation Project' http://www.tldp.org/
'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html
'HowtoForge' http://howtoforge.com/
****
13 years, 8 months
I need a jabber client, like real fast
by Robert Moskowitz
We are suppose to have a WebEX meeting going, but having problems. So
the coordinator told everyone to jump on a jabber session.
I don't know what to use for jabber on my FC12 system.
??
13 years, 8 months
Problem when upgrading from F12 to F13
by Jon Ingason
Hi,
Have to computer where I run Fedora. One is i686 (Pentium III
(Coppermine) 800 MHz), 512 Mbytes memory and the other one is x86_64
(AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ 1800 MHz, 2 Gbytes
memory. I had installed F12 on both of them. The /boot (ext4) is 200
Mbytes on both computer. I decided to do preupgrade on both (F12 ->
F13). Since the /boot is only 200 Mbytes I followed the instructions
published on Fedora wiki "How to use PreUpgrade"
(http://fedoraproject.org/wiki/PreUpgrade).
The preupgrade of the i686 went fine. It only did do the first step so
when I rebooted the computer I only needed to configure the network as
stated in the wiki. When I tried to preupgrade the x86_64 using same
method as with the i686 the /boot got full and the preupgrade program
crashed.
I have goggled and not found this problem. Have other same problem with
x86_64 or is there other way to do this without resizing /boot?
PS The rest of the disk is LVM on both computers.
--
Regards
Jon Ingason
13 years, 8 months
Fedora updates getting more like Windows every day
by Bill Davidsen
Remember the old joke GIF image, with the box which said
you have moved your mouse
in order for this change to be effective you must reboot your system
It's getting so keeping systems up to date with current patches is
incompatible with reasonable uptime goals. More and more upgrades
require a reboot, and even reading the CVE data behind the update it's
not always possible to tell if a fix is urgent. I'd like to encourage a
bit more detail in the info with the upgrade, and a little more thought
about what can be done to reduce reboots.
More operations are specifying maximum outage figures, running 7x24, and
running things which have long run times and bad checkpoint code.
At least two companies are done with reminding people to shut off the
desktop overnight, they are putting cloud software on desktops and using
cloud tech to offload mainframes. Not just new tech such as SETI@home
and folding use, but things like PVM. I was admin of a PVM group 21
years ago, but people are still using it.
To some extent RHEL suffers from this as well, though systems seem to
have fewer and more stable things running.
--
Bill Davidsen <davidsen(a)tmr.com>
"We can't solve today's problems by using the same thinking we
used in creating them." - Einstein
13 years, 8 months