On Wed, Jul 17, 2013 at 12:27:43AM -0400, D. Hugh Redelmeier wrote:
When I'm asked by debian (dpkg) what I want to do in the face of a
config file change, I'm not in a great position to deal with it (my
system is in a halfway state and out of production). The tools they
give for dealing with
| From: Heinz Diehl h...@fritha.org
| Only speaking for myself: I always try to upgrade first, having a
| complete backup, of course. If it doesn't work, I reinstall. There's
| nothing to loose, since I'm expecting to reinstall anyway.
There is a risk: things can be subtly wrong, in such a way
| From: Reindl Harald h.rei...@thelounge.net
| what he menat was showing the difference between
| present and new config file before updates and the
| option to merge them - not that the merge is useful
| in many cases but *that* is was Debian offers
Yes.
Perhaps it is my greater time with Red
Frank Murphy frankl...@gmail.com writes:
On Mon, 15 Jul 2013 00:51:50 +0200
lee l...@yun.yagibdah.de wrote:
Frank Murphy frankl...@gmail.com writes:
On Sun, 14 Jul 2013 00:51:05 +0200
lee l...@yun.yagibdah.de wrote:
make systemd send mails in case a service
couldn't be started or
Joe Zeff j...@zeff.us writes:
On 07/13/2013 03:51 PM, lee wrote:
Automatic updates? I'd rather not do that since it sometimes seems
advisable to reboot after an update.
If you want to be sure, run needs-restarting in a terminal, as
root. About the only thing it doesn't list that I've seen
Eddie G. O'Connor Jr. eoconno...@gmail.com writes:
On 07/13/2013 06:51 PM, lee wrote:
It's not simply about knowing which packages have been or are to be
updated --- that I can see when running 'yum update'. It's about
information what has actually changed when a package was updated.
For
On Sun, Jul 14, 2013 at 12:51:05AM +0200, lee wrote:
The package management tools in Debian send you emails about changes
like that, even about very little changes, when packages are being
replaced by more recent versions. Maybe this could be done in Fedora as
well?
You could try using
On Sun, Jul 14, 2013 at 09:54:49AM +0200, lee wrote:
Something like 'yum-seth-plugin', sending you messages with a subject
like Seth reminds you: package-name, and make yum depend on it?
Let's not name something after Seth unless we're sure it's something he
would have liked.
--
Matthew
On Sun, 14 Jul 2013 00:51:05 +0200
lee l...@yun.yagibdah.de wrote:
Why not make it one of the great features of Fedora? Then take it
to the next step and make systemd send mails in case a service
couldn't be started or has issues,
You can do that yourself currently.
--
Regards,
Frank When
On 07/14/2013 03:54 AM, lee wrote:
Eddie G. O'Connor Jr. eoconno...@gmail.com writes:
On 07/13/2013 06:51 PM, lee wrote:
It's not simply about knowing which packages have been or are to be
updated --- that I can see when running 'yum update'. It's about
information what has actually changed
On 07/14/2013 08:35 AM, Matthew Miller wrote:
On Sun, Jul 14, 2013 at 12:51:05AM +0200, lee wrote:
The package management tools in Debian send you emails about changes
like that, even about very little changes, when packages are being
replaced by more recent versions. Maybe this could be done
Frank Murphy frankl...@gmail.com writes:
On Sun, 14 Jul 2013 00:51:05 +0200
lee l...@yun.yagibdah.de wrote:
Why not make it one of the great features of Fedora? Then take it
to the next step and make systemd send mails in case a service
couldn't be started or has issues,
You can do that
Matthew Miller mat...@fedoraproject.org writes:
On Sun, Jul 14, 2013 at 12:51:05AM +0200, lee wrote:
You could try using yum-cron.
Automatic updates? I'd rather not do that since it sometimes seems
advisable to reboot after an update.
It's often advisable, but usually only because the
Am 14.07.2013 14:35, schrieb Matthew Miller:
On Sun, Jul 14, 2013 at 12:51:05AM +0200, lee wrote:
The package management tools in Debian send you emails about changes
like that, even about very little changes, when packages are being
replaced by more recent versions. Maybe this could be
Am 14.07.2013 14:41, schrieb Frank Murphy:
On Sun, 14 Jul 2013 00:51:05 +0200
lee l...@yun.yagibdah.de wrote:
Why not make it one of the great features of Fedora? Then take it
to the next step and make systemd send mails in case a service
couldn't be started or has issues,
You can do
Am 14.07.2013 15:12, schrieb Frank Murphy:
On Sun, 14 Jul 2013 14:55:02 +0200
Reindl Harald h.rei...@thelounge.net wrote:
Didn't know wherer you wanted to post back to list?
If yes, I will.
i had the list also as RCPT a well as now
so no need to re-post
it makes pretty no sense having a
Eddie G. O'Connor Jr. eoconno...@gmail.com writes:
On 07/14/2013 03:54 AM, lee wrote:
Eddie G. O'Connor Jr. eoconno...@gmail.com writes:
On 07/13/2013 06:51 PM, lee wrote:
It's not simply about knowing which packages have been or are to be
updated --- that I can see when running 'yum
On Mon, 15 Jul 2013 00:51:50 +0200
lee l...@yun.yagibdah.de wrote:
Frank Murphy frankl...@gmail.com writes:
On Sun, 14 Jul 2013 00:51:05 +0200
lee l...@yun.yagibdah.de wrote:
Why not make it one of the great features of Fedora? Then take
it to the next step and make systemd send
Eddie G. O'Connor Jr. eoconno...@gmail.com writes:
ALL!).And now for..fedup-cli --network 19...and I'll keep my
fingers crossedbut what's the time frame?like an
hour?2?...2+1/2?
About an hour or two --- it depends on how fast you can download
packages and on how fast
Matthew Miller mat...@fedoraproject.org writes:
On Fri, Jul 12, 2013 at 09:57:04PM +0200, lee wrote:
The upgrade from 17 to 18 silently broke apache because the
configuration had changed. That is something that shouldn't happen, the
devs know when there are changes like that and make sure
On Sat, Jul 13, 2013 at 03:34:18PM +0200, lee wrote:
The package management tools in Debian send you emails about changes
like that, even about very little changes, when packages are being
replaced by more recent versions. Maybe this could be done in Fedora as
well?
You could try using
On Sat, Jul 13, 2013 at 05:57:57PM +0200, Reindl Harald wrote:
what he menat was showing the difference between
present and new config file before updates and the
option to merge them - not that the merge is useful
in many cases but *that* is was Debian offers
Oh, I see. There used to be a
On 07/13/2013 09:44 AM, lee wrote:
Eddie G. O'Connor Jr. eoconno...@gmail.com writes:
ALL!).And now for..fedup-cli --network 19...and I'll keep my
fingers crossedbut what's the time frame?like an
hour?2?...2+1/2?
About an hour or two --- it depends on how fast you can
Am 13.07.2013 17:50, schrieb Matthew Miller:
On Sat, Jul 13, 2013 at 03:34:18PM +0200, lee wrote:
The package management tools in Debian send you emails about changes
like that, even about very little changes, when packages are being
replaced by more recent versions. Maybe this could be
Am 12.07.2013 21:57, schrieb lee:
The upgrade from 17 to 18 silently broke apache because the
configuration had changed. That is something that shouldn't happen, the
devs know when there are changes like that and make sure the users are
informed accordingly.
don't get me wrong but if you
On Fri, Jul 12, 2013 at 9:10 AM, Eddie G. O'Connor Jr.
eoconno...@gmail.com wrote:
On 07/12/2013 03:19 AM, Joe Zeff wrote:
On 07/11/2013 11:38 PM, Heinz Diehl wrote:
Only speaking for myself: I always try to upgrade first, having a
complete backup, of course. If it doesn't work, I reinstall.
Reindl Harald h.rei...@thelounge.net writes:
Am 12.07.2013 21:57, schrieb lee:
The upgrade from 17 to 18 silently broke apache because the
configuration had changed. That is something that shouldn't happen, the
devs know when there are changes like that and make sure the users are
informed
On Sat, Jul 13, 2013 at 10:59:23PM +0200, lee wrote:
don't get me wrong but if you hvae manually configured services
especially a webserver it's your job to look *before* you upgrade
if there is a major change and prepare your manual configuration
for it - untouched configuration is
Matthew Miller mat...@mattdm.org writes:
On Sat, Jul 13, 2013 at 05:57:57PM +0200, Reindl Harald wrote:
what he menat was showing the difference between
present and new config file before updates and the
option to merge them - not that the merge is useful
in many cases but *that* is was
Reindl Harald h.rei...@thelounge.net writes:
Am 13.07.2013 17:50, schrieb Matthew Miller:
On Sat, Jul 13, 2013 at 03:34:18PM +0200, lee wrote:
The package management tools in Debian send you emails about changes
like that, even about very little changes, when packages are being
replaced by
Reindl Harald h.rei...@thelounge.net writes:
Am 13.07.2013 22:59, schrieb lee:
Reindl Harald h.rei...@thelounge.net writes:
don't get me wrong but if you hvae manually configured services
especially a webserver it's your job to look *before* you upgrade
if there is a major change and
On 07/13/2013 03:51 PM, lee wrote:
Automatic updates? I'd rather not do that since it sometimes seems
advisable to reboot after an update.
If you want to be sure, run needs-restarting in a terminal, as root.
About the only thing it doesn't list that I've seen is the kernel, but
for most
On 07/13/2013 06:51 PM, lee wrote:
Matthew Miller mat...@fedoraproject.org writes:
On Sat, Jul 13, 2013 at 03:34:18PM +0200, lee wrote:
The package management tools in Debian send you emails about changes
like that, even about very little changes, when packages are being
replaced by more
On 12.07.2013, Joe Zeff wrote:
Yes, but is their experience recent enough to matter? If they tried to
upgrade using the earliest version of preupgrade, had problems and decided
never to try again, how relevant is that, especially when preupgrade's been
replaced with fedup? Unless you know
On 07/11/2013 11:38 PM, Heinz Diehl wrote:
Only speaking for myself: I always try to upgrade first, having a
complete backup, of course. If it doesn't work, I reinstall. There's
nothing to loose, since I'm expecting to reinstall anyway.
I've had an update fail too, once. Being retired and
On 07/12/2013 03:19 AM, Joe Zeff wrote:
On 07/11/2013 11:38 PM, Heinz Diehl wrote:
Only speaking for myself: I always try to upgrade first, having a
complete backup, of course. If it doesn't work, I reinstall. There's
nothing to loose, since I'm expecting to reinstall anyway.
I've had an
On 07/12/2013 09:10 AM, Eddie G. O'Connor Jr. wrote:
See?...it's stuff like the stories above that make me hesitant to go
from 18 to 19
Why? Something went wrong. Once. I spent several days, off and on,
cleaning up cruft and duplicate packages from a CLI, got the GUI working
and all was
On 07/12/2013 03:33 PM, Joe Zeff wrote:
On 07/12/2013 09:10 AM, Eddie G. O'Connor Jr. wrote:
See?...it's stuff like the stories above that make me hesitant to go
from 18 to 19
Why? Something went wrong. Once. I spent several days, off and on,
cleaning up cruft and duplicate packages from
Eddie G. O'Connor Jr. eoconno...@gmail.com writes:
On 07/12/2013 03:19 AM, Joe Zeff wrote:
On 07/11/2013 11:38 PM, Heinz Diehl wrote:
Only speaking for myself: I always try to upgrade first, having a
complete backup, of course. If it doesn't work, I reinstall. There's
nothing to loose, since
Joe Zeff j...@zeff.us writes:
On 07/11/2013 01:27 PM, lee wrote:
I have been assuming that people re-install because their experience is
that upgrading is so troublesome that they figure that they're better
off re-installing. Why would anyone go to the lengths of re-installing
if there
On Fri, Jul 12, 2013 at 09:57:04PM +0200, lee wrote:
The upgrade from 17 to 18 silently broke apache because the
configuration had changed. That is something that shouldn't happen, the
devs know when there are changes like that and make sure the users are
informed accordingly.
Where/how do
moved over to F19
and it might be fixed there, who knows. Just making a bug report
without real information doesn't seem a very useful thing to do, and I
didn't really have time to look into it yet.
The question is still: What has 'yum update' done? I only know it did
something to the boot
On 07/11/2013 01:27 PM, lee wrote:
I have been assuming that people re-install because their experience is
that upgrading is so troublesome that they figure that they're better
off re-installing. Why would anyone go to the lengths of re-installing
if there weren't very serious problems with
On 08.07.2013, Joe Zeff wrote:
It might be a good idea for everybody who's already moved to F19 to say so,
including what method, what results and how many machines. That way we can
get a (slightly) better idea of how well different ways work. And, before
anybody asks, clean installs are
Reindl Harald h.rei...@thelounge.net writes:
Am 09.07.2013 07:13, schrieb lee:
Reindl Harald h.rei...@thelounge.net writes:
Am 09.07.2013 02:46, schrieb lee:
well, here you have to make a choice as often in life
* learn to deal with the networking part is extremely difficult
* take money
snipIt might be a good idea for everybody who's already moved to
F19 to say so, including what method, what results and how many
machines. That way we can get a (slightly) better idea of how well
different ways work. And, before anybody asks, clean installs are
also a way of upgrading./snip
On 07/10/2013 12:37 AM, lee wrote:
Well, I have a file like rpmfusion-free-rawhide.repo in
/etc/yum.repos.d/ which is there because I need the NVIDIA drivers. I
was just following the instructions and have no way of knowing if
there's something wrong with that or not. If you can show that it
Joe Zeff j...@zeff.us writes:
On 07/10/2013 12:37 AM, lee wrote:
Well, I have a file like rpmfusion-free-rawhide.repo in
/etc/yum.repos.d/ which is there because I need the NVIDIA drivers. I
was just following the instructions and have no way of knowing if
there's something wrong with that
Joe Zeff j...@zeff.us writes:
On 07/08/2013 05:52 PM, lee wrote:
If that is true, then why does it happen to me? Why didn't the upgrade
work last time, and why does a simple yum update try to trick me into
upgrading, and why does booting fail after that? There isn't anything
special here.
On 07/10/2013 03:06 PM, lee wrote:
When upgrading Fedora the way it's recommended works so well, then how
come that people are suggesting that it's better/easier to re-install or
to use an alternative, untested method?
There are always going to be people who prefer to start fresh with a
On 07/10/2013 03:22 PM, lee wrote:
It doesn't seem to be enabled:
OK, then, don't worry about it. I asked because unless you're actually
working with rawhide it shouldn't be enabled. I have that file too, but
like you, it's disabled.
--
users mailing list
users@lists.fedoraproject.org
To
Am 09.07.2013 00:39, schrieb lee:
Reindl Harald h.rei...@thelounge.net writes:
Besides, I don't find it easy at all to set one up because the
networking part is extremely difficult.
using VMware Workstation it is trivial to
get a VM running in it's own NAT network
works out of the box
Am 09.07.2013 02:46, schrieb lee:
well, here you have to make a choice as often in life
* learn to deal with the networking part is extremely difficult
* take money in your hand and avoid this part
None of these would solve the problem because I cannot clone my system.
None of these are
Am 09.07.2013 07:13, schrieb lee:
Reindl Harald h.rei...@thelounge.net writes:
Am 09.07.2013 02:46, schrieb lee:
well, here you have to make a choice as often in life
* learn to deal with the networking part is extremely difficult
* take money in your hand and avoid this part
None of
Am 07.07.2013 17:53, schrieb lee:
Heinz Diehl h...@fritha.org writes:
On 07.07.2013, lee wrote:
What kind of crap is that?
I don't know.
And does it mean that there again will be problems with updating when I try
to move to F19?
In general, I would always prefer a fresh install over
Am 07.07.2013 19:21, schrieb lee:
Reindl Harald h.rei...@thelounge.net writes:
Am 07.07.2013 17:53, schrieb lee:
If Fedora cannot be updated without major problems, it's
not useable.
if you follow this guides *strictly* and willing to learn to deal
wtih package-cleanup --leaves |
I've been using Fedora and before that Red Hat Linux for over 15 years.
I've never trusted any update process. I've always done a
re-installation.
This time, I thought I'd give fedup a chance. I've done it on three
systems. Each mostly worked. The problems were minor and could
essentially
Garry T. Williams gtwilli...@gmail.com writes:
On 7-7-13 19:21:33 lee wrote:
So we have three options to upgrade:
1.) the recommended fedup which probably doesn't work
2.) the untested and unsupported way using yum which might work or
not
3.) move away from Fedora and install a different
Heinz Diehl h...@fritha.org writes:
On 07.07.2013, lee wrote:
That is not an option. I can't start from scratch every half year and
waste a week or two to get the system back to how I need it.
Have you considered to switch to some kind of rolling distribution,
then? I for myself like
Frank Murphy frankl...@gmail.com writes:
No. 2.) might not work anymore
sooner or later, if it works at all to begin with --- and it's all
guesswork anyway.
yum is not guesswork.
Upgrading Fedora is guesswork, especially when using yum to upgrade.
All I have updated with yum since F16,
Mateusz Marzantowicz mmarzantow...@osdf.com.pl writes:
If you don't want to upgrade to F19 yet, try to regenerate grub boot
menu manually using grub2-mkconfig. You'll gain some time to track
package that is trying to make you happy and then remove or
reconfigure it.
You mean messing up
Reindl Harald h.rei...@thelounge.net writes:
Am 07.07.2013 19:21, schrieb lee:
Considering that Fedora does not have a working (and tested and
supported) upgrade method at all, such packaging guidelines seem very
questionable. That means you're simply lucky if you manage to upgrade.
That
On Mon, 08 Jul 2013 18:09:13 +0200
lee l...@yun.yagibdah.de wrote:
So it seems that most ppl use yum to upgrade and that it mostly works.
The sample size of people in this thread isn't really enough to
extrapolate to 'most people', IMHO.
If that is so, then why did they ever come up with
On 07/08/2013 08:56 AM, lee wrote:
Now consider the possible consequences of running a presumably pretty
harmless yum update: You can be left stranded with a non-working
system and you can lose your data. What kind of reliability is that?
For well over 99% of the people using Fedora this is
On 07/08/2013 09:02 AM, lee wrote:
When you do that, how do you make sure that you don't run into a
situation in which your system becomes unusable? You might end up with
crucial software not running or not working anymore because other
software already has been updated or hasn't been updated
On 07/08/2013 11:40 AM, Heinz Diehl wrote:
And taking into account the simple fact that usually those who
encounter(ed) problems are dominating the list, you have to deal with
publication bias :-)
You make an excellent point. I'm still running F17, but I plan to
upgrade my laptop to 19 RSN,
On 08.07.2013, Kevin Fenzi wrote:
The sample size of people in this thread isn't really enough to
extrapolate to 'most people', IMHO.
And taking into account the simple fact that usually those who
encounter(ed) problems are dominating the list, you have to deal with
publication bias :-)
On Mon, 8 Jul 2013, Joe Zeff wrote:
You make an excellent point. I'm still running F17, but I plan to upgrade my
laptop to 19 RSN, and once that's working properly, I'll do the same to my
desktop. I skipped 18 because of all the upgrade issues I read about here
and other Fedora help
On 08.07.2013, Joe Zeff wrote:
I'm still running F17, but I plan to upgrade
my laptop to 19 RSN, and once that's working properly, I'll do the same to
my desktop. I skipped 18 because of all the upgrade issues I read about
here and other Fedora help groups I infest.
I have two machines
Reindl Harald h.rei...@thelounge.net writes:
Am 08.07.2013 20:19, schrieb lee:
i do not buy you're simply lucky after around 400 dist-upgrades
with yum on workstations and production servers with all sort
of services - i *never* rely on luck, i simply *test* and *prepare*
upgrades after test
On 07/08/2013 01:10 PM, lee wrote:
Your conclusion would have to be that Fedora can only reasonably be used
in a professional environment like you have at your disposal and that it
is totally unsuited for what they say that their user base is.
No, that's *your* conclusion. I run Fedora on my
Am 08.07.2013 17:47, schrieb D. Hugh Redelmeier:
| if you follow this guides *strictly* and willing to learn to deal
| wtih package-cleanup --leaves | --problems | --orphans and
| to understand how your OS basically works you are fine
|
Am 08.07.2013 22:10, schrieb lee:
Reindl Harald h.rei...@thelounge.net writes:
Am 08.07.2013 20:19, schrieb lee:
i do not buy you're simply lucky after around 400 dist-upgrades
with yum on workstations and production servers with all sort
of services - i *never* rely on luck, i simply
Am 08.07.2013 20:19, schrieb lee:
i do not buy you're simply lucky after around 400 dist-upgrades
with yum on workstations and production servers with all sort
of services - i *never* rely on luck, i simply *test* and *prepare*
upgrades after test them carefully on clones with note all needed
Reindl Harald h.rei...@thelounge.net writes:
Am 08.07.2013 22:10, schrieb lee:
Reindl Harald h.rei...@thelounge.net writes:
Am 08.07.2013 20:19, schrieb lee:
it is easy to setup a virtual machine with any for your
wokrload critical software configured 1:1 like on the
working system and
Reindl Harald h.rei...@thelounge.net writes:
Am 09.07.2013 00:39, schrieb lee:
Reindl Harald h.rei...@thelounge.net writes:
Besides, I don't find it easy at all to set one up because the
networking part is extremely difficult.
using VMware Workstation it is trivial to
get a VM running in
Joe Zeff j...@zeff.us writes:
On 07/08/2013 01:10 PM, lee wrote:
Your conclusion would have to be that Fedora can only reasonably be used
in a professional environment like you have at your disposal and that it
is totally unsuited for what they say that their user base is.
No, that's *your*
Joe Zeff j...@zeff.us writes:
It might be a good idea for everybody who's already moved to F19 to
say so, including what method, what results and how many machines.
That way we can get a (slightly) better idea of how well different
ways work.
That might be interesting to see.
And, before
D. Hugh Redelmeier h...@mimosa.com writes:
| From: lee l...@yun.yagibdah.de
| Reindl Harald h.rei...@thelounge.net writes:
|
| Am 07.07.2013 17:53, schrieb lee:
| If Fedora cannot be updated without major problems, it's
| not useable.
Until you do it, you cannot know if you will have
Kevin Fenzi ke...@scrye.com writes:
On Mon, 08 Jul 2013 18:09:13 +0200
lee l...@yun.yagibdah.de wrote:
So it seems that most ppl use yum to upgrade and that it mostly works.
The sample size of people in this thread isn't really enough to
extrapolate to 'most people', IMHO.
It goes only
Joe Zeff j...@zeff.us writes:
On 07/08/2013 08:56 AM, lee wrote:
Now consider the possible consequences of running a presumably pretty
harmless yum update: You can be left stranded with a non-working
system and you can lose your data. What kind of reliability is that?
For well over 99% of
Joe Zeff j...@zeff.us writes:
On 07/08/2013 09:02 AM, lee wrote:
When you do that, how do you make sure that you don't run into a
situation in which your system becomes unusable? You might end up with
crucial software not running or not working anymore because other
software already has
Reindl Harald h.rei...@thelounge.net writes:
Am 09.07.2013 02:46, schrieb lee:
well, here you have to make a choice as often in life
* learn to deal with the networking part is extremely difficult
* take money in your hand and avoid this part
None of these would solve the problem because
On 07/08/2013 05:52 PM, lee wrote:
If that is true, then why does it happen to me? Why didn't the upgrade
work last time, and why does a simple yum update try to trick me into
upgrading, and why does booting fail after that? There isn't anything
special here.
It happens to you because it's
On 07/07/2013 03:52 PM, Heinz Diehl wrote:
On 07.07.2013, lee wrote:
What kind of crap is that?
I don't know.
And does it mean that there again will be problems with updating when I try
to move to F19?
In general, I would always prefer a fresh install over any
update. Experience over the
Heinz Diehl h...@fritha.org writes:
On 07.07.2013, lee wrote:
What kind of crap is that?
I don't know.
And does it mean that there again will be problems with updating when I try
to move to F19?
In general, I would always prefer a fresh install over any
update. Experience over the
On 07.07.2013, lee wrote:
That is not an option. I can't start from scratch every half year and
waste a week or two to get the system back to how I need it.
Have you considered to switch to some kind of rolling distribution,
then? I for myself like very much Arch..
--
users mailing list
Reindl Harald h.rei...@thelounge.net writes:
Am 07.07.2013 17:53, schrieb lee:
If Fedora cannot be updated without major problems, it's
not useable.
if you follow this guides *strictly* and willing to learn to deal
wtih package-cleanup --leaves | --problems | --orphans and
to understand
On Sun, 07 Jul 2013 19:21:33 +0200
lee l...@yun.yagibdah.de wrote:
Reindl Harald h.rei...@thelounge.net writes:
No. 1.) didn't work last time, and there is some indication that it
won't work this time, either.
It has had success and failure for some
Failed on the box, I tried.
(Could be
On 07.07.2013 17:53, lee wrote:
Heinz Diehl h...@fritha.org writes:
On 07.07.2013, lee wrote:
What kind of crap is that?
I don't know.
And does it mean that there again will be problems with updating when I try
to move to F19?
In general, I would always prefer a fresh install over any
On 7-7-13 19:21:33 lee wrote:
So we have three options to upgrade:
1.) the recommended fedup which probably doesn't work
2.) the untested and unsupported way using yum which might work or
not
3.) move away from Fedora and install a different distribution
No. 1.) didn't work last time,
Hi,
so I've been running 'yum update' today and when I wanted to reboot, I
found that grub now has an entry to boot some vmlinuz-fedup instead of a
normal kernel, and that even as default :(
The vmlinuz-fedup isn't bootable --- apparently it tries to start some
sort of rescue mode and then says
On 07.07.2013, lee wrote:
What kind of crap is that?
I don't know.
And does it mean that there again will be problems with updating when I try
to move to F19?
In general, I would always prefer a fresh install over any
update. Experience over the years has shown (for me) that updating is
93 matches
Mail list logo
