Get a copy of the new default files and compare with yours?
Right. Using the Packages-Section of Archlinux Homepage. Shame on me. Thank you
]]>Hi all
I have read this thread two times now and still cannot find an overall answer what needs to be done if one (like me) has suppressed the changes (that means I have kept the old files and deleted the 4 new _.pacnew ones).
Can someone help me out what I might need to change in a quick summary?
Would be very nice. TIA
Get a copy of the new default files and compare with yours?
]]>I have read this thread two times now and still cannot find an overall answer what needs to be done if one (like me) has suppressed the changes (that means I have kept the old files and deleted the 4 new _.pacnew ones).
Can someone help me out what I might need to change in a quick summary?
Would be very nice. TIA
]]>jasonwryan wrote:amadar wrote:My family's from down south, and that's not a bad thing, so I'm going to assume you meant automounting has not gone bad.
Not as far south as where I am from. Also, please do not attempt to troll me in a support thread...
Further south than Peru, South America?
Do NOT troll this thread, you are totally off-topic and add no value at all here.
]]>Well, you could. It is probably easier to copy the new dbus line to the old customised file, though.
If there is no entry for dbus in the new files, something is wrong.
Re. uid of uuid: I didn't mean you should generally ignore uid changes - just I know it is OK to stay with the old uid for uuid specifically.
WellI updated, I did nothing, I rebooted, prayed (a lot) and all the same (well) without any error log. Review the differences between my files and pacnew and are virtually identical except as regards my own settings. So I left it as is (my old ones). Anyway I do not like leaving pacnew's "loose" out there. So for now I will not by "Solved" my case and will apply the saying that "if it goes well ... do not touch it!
In addition, I research by the forums (even in several languages) for a week, and if this were so critical should have dozens and dozens of posts from people who screwed up. So I assume that most have done this.
Thanks...
(sorry for my english)
amadar wrote:jasonwryan wrote:I can confirm that, using udiskie, automounting has gone south with the new dbus.
My family's from down south, and that's not a bad thing, so I'm going to assume you meant automounting has not gone bad.
Not as far south as where I am from. Also, please do not attempt to troll me in a support thread...
Further south than Peru, South America?
]]>If there is no entry for dbus in the new files, something is wrong.
Re. uid of uuid: I didn't mean you should generally ignore uid changes - just I know it is OK to stay with the old uid for uuid specifically.
]]>You don't need to change the uuid uid - I checked this with a developer when the change first arose and it is perfectly fine to leave whatever uid you were using before for uuid. So I ignore that difference.
Do you mean that any reference to uid in *.pacnew files (passwd, group, shadow, gshadow) I can ignore it? Then I must leave it as *pacnew say, Is it?
I just replaced old dbus lines with new dbus lines where old and new were different.
Oh... I am confused. There are a lot of lines in my passwd, group, shadow, gshadow files (old) with my config. Among these lines there are always a dbus line. Do you mean that I must copy everything related my config from my (old) files and paste in the right place in *pacnew.... but.... I must leave the dbus line as the *pacnew say (even if there is no dbus line? (and then renaming the pacnew files without ".pacnew)
Excuse me for so many questions, but is because the language.
Thank you very much again
You don't need to change the uuid uid - I checked this with a developer when the change first arose and it is perfectly fine to leave whatever uid you were using before for uuid. So I ignore that difference.
I didn't make any other changes - just replaced old dbus lines with new dbus lines where old and new were different.
(Note: I'm not even sure that was necessary. But that's what I did.)
]]>For me was the other way around: automounting now works with this update, and I removed the .pacnew (didn't even bother to see it).
That is most likely because with the latest update the 'hack' that was removed has been restored as stated here.
As for simply deleting the .pacnew I am not sure if it was the wise way to handle the update. Check mcloaked's message for additional info.
]]>If you kept a copy of your original set of files it may be worth reverting and doing only these changes that I outlined above.
]]>cfr said:
I'm by no means certain but I don't think keeping the old dbus entries *and* adding the new ones would be a good idea since you will then have conflicting definitions for the dbus user/group's home/shell/etc.
Thank you cfr. You bring up a good point. I must assume a lot with Arch and will correct as you recommended.
]]>I merged the .pacnew files, except for gshadow and shadow. The only differences in gshadow apart from root and user entries is the dbus entry
current has
dbus:!::
pacnew has
dbus:x::
In shadow, current has
dbus:!:15629:0:99999:7:::
pacnew has
dbus:x:14871::::::
Trouble I am having now is that after grub, Arch begins to boot, but I cannot get a graphical login screen. I tried to also boot just to a shell (commented out my exec command in .xinitrc), but same thing happens. All i see is the beginning of a boot and then the screen goes black.
]]>