[opensuse] Moving / and /boot partitions
In preperation for a new motherboard, I'm moving my system from a pair of IDE drives to a SATA drive. I have copied all the partitions by using cp -a to the new drive. However I cannot get the system to boot with / and /boot on the new system. I have tried various things including the Yast Boot Loader and grub2-mkconfig, but can't seem to get the new partitions to work. While I realize I could just reinstall to the new drive, I'd prefer to move the existing system over. BTW, with the original Grub, it was possible to have descriptive titles in the boot menu, so that you knew what you were booting. Why isn't this possible with Grub2. Even in the advanced menu, I only see 4 entries with identical titles. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 23/03/2014 13:19, James Knott a écrit :
this possible with Grub2. Even in the advanced menu, I only see 4 entries with identical titles.
it's the moment to use the grub editor (type "e"), but chance is you have to edit the fstab new entry can't you at least boot your old config? jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
jdd wrote:
Le 23/03/2014 13:19, James Knott a écrit :
this possible with Grub2. Even in the advanced menu, I only see 4 entries with identical titles.
it's the moment to use the grub editor (type "e"), but chance is you have to edit the fstab new entry
can't you at least boot your old config?
jdd
Type e where? It's not a command. I can edit fstab and all the old partitions are commented out. I can boot through the install DVD, but it still loads the old / & /boot. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 23/03/2014 13:34, James Knott a écrit :
Type e where?
at the grub boot menu, this allows to edit the boot grub options or to boot any available root partition It's not a command. I can edit fstab and all the old
partitions are commented out.
but did you add the new ones (on the new disk, of course)? jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
jdd wrote:
Le 23/03/2014 13:34, James Knott a écrit :
Type e where?
at the grub boot menu, this allows to edit the boot grub options or to boot any available root partition
It's not a command. I can edit fstab and all the old
partitions are commented out.
but did you add the new ones (on the new disk, of course)?
jdd
When I hit e, I see what appears to be the contents of some config file listing boot parameters. I don't see any easy way to change where the system boots. Is this properly documented anywhere? By searching with Google, I find bits and pieces, but no coherent picture. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 23/03/2014 15:34, James Knott a écrit :
When I hit e, I see what appears to be the contents of some config file listing boot parameters. I don't see any easy way to change where the system boots.
Is this properly documented anywhere? By searching with Google, I find bits and pieces, but no coherent picture.
curiously, I also have problems finding a conprehensive tutorial on this http://members.iinet.net/~herman546/p20/GRUB2%20CLI%20Mode%20Commands.html gives some honts, but not very clearly. some hints: typing "e" at the grub menu give you the ability to change the kernel boot options, for example add "nomodeset" when necessary or changing the root partition. This is good for very small changes bu then typing "c" gives you a grub command line: grub > there you can navigate the disk, found config files or kernels. TAB key compeltion works what is extremely usefull. for example grub > kernel ( <TAB> shows the hole list of disks available and complete all what is possible letting you choose the rest. say you get after TAB: grub > kernel (hd0, a new TAB will show you all the HD0 partitions grub > kernel (hd0,2)/boot <TAB> will show you the content of the /boot folder if hd0,2 is the root partition. like this you have to load kernel, initrd and give root partition then boot once understood it's quite straightforward, much easier than it seems at first glance. grub2 changed some commands, so I know a bit less this one jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-03-23 08:19 (GMT-0400) James Knott composed:
In preperation for a new motherboard, I'm moving my system from a pair of IDE drives to a SATA drive. I have copied all the partitions by using cp -a to the new drive. However I cannot get the system to boot with / and /boot on the new system. I have tried various things including the Yast Boot Loader and grub2-mkconfig, but can't seem to get the new partitions to work. While I realize I could just reinstall to the new drive, I'd prefer to move the existing system over.
I do what you're trying to do often, and successfully, but I use rsync -av instead of cp, or literally clone followed by changing volume labels and UUIDs on the cloned filesystems. Ultimately Grub needs to be installed/configured correctly on the appropriate new location(s) as well. All my Grub cmdlines and fstab entries for Linux native partitions use volume labels rather than UUIDs, device names or device IDs. I have too many installations successfully created this way to keep track of, though none of my openSUSE installations have Grub2 or os-prober installed, including my 12 13.2m0 and 17 13.1 installations, besides older and other distros. Maybe you should tell us exactly what steps you took rather than summarizing. You might be on the edge of success, missing just one little thing.
BTW, with the original Grub, it was possible to have descriptive titles in the boot menu, so that you knew what you were booting. Why isn't this possible with Grub2. Even in the advanced menu, I only see 4 entries with identical titles.
How about showing us the relevant portions of the file containing those stanzas? Did you do any manual editing of grub.cfg? What if anything have you done with /etc/default/grub on the SATA? Have you done anything in the BIOS to make sure the SATA is HD0, or tried booting the SATA with both PATA removed (power and/or control cables disconnected)? Exactly what is the BIOS setting for HD controller(s) when failure is occurring? Are you already trying to use the new motherboard? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Felix Miata wrote:
On 2014-03-23 08:19 (GMT-0400) James Knott composed:
In preperation for a new motherboard, I'm moving my system from a pair of IDE drives to a SATA drive. I have copied all the partitions by using cp -a to the new drive. However I cannot get the system to boot with / and /boot on the new system. I have tried various things including the Yast Boot Loader and grub2-mkconfig, but can't seem to get the new partitions to work. While I realize I could just reinstall to the new drive, I'd prefer to move the existing system over.
I do what you're trying to do often, and successfully, but I use rsync -av instead of cp, or literally clone followed by changing volume labels and UUIDs on the cloned filesystems. Ultimately Grub needs to be installed/configured correctly on the appropriate new location(s) as well. All my Grub cmdlines and fstab entries for Linux native partitions use volume labels rather than UUIDs, device names or device IDs. I have too many installations successfully created this way to keep track of, though none of my openSUSE installations have Grub2 or os-prober installed, including my 12 13.2m0 and 17 13.1 installations, besides older and other distros.
Maybe you should tell us exactly what steps you took rather than summarizing. You might be on the edge of success, missing just one little thing.
I also use volume labels, rather than device ID. The first thing I did was create mount points for the new partitions, with the usual names, but with x appended. For example, I created /homex, /tmpx etc. and then mounted the new partitions on those mount points. I then copied the contents from the old to new partitions, using cp -a. As I understand it, rsync doesn't make any difference in the end result, when copying to an empty partition. I then went through fstab, removing the trailing x from the new partitions and added it to the old ones. I later disabled mounting the old partitions by inserting a # at the beginning of the lines for the old partitions. I have tried running the Boot Loader in Yast,, grub2-mkconfig and even tried running an update from the install DVD, but that also failed. I also used fdisk to verify the new drive is bootable.
BTW, with the original Grub, it was possible to have descriptive titles in the boot menu, so that you knew what you were booting. Why isn't this possible with Grub2. Even in the advanced menu, I only see 4 entries with identical titles.
How about showing us the relevant portions of the file containing those stanzas? Did you do any manual editing of grub.cfg? What if anything have you done with /etc/default/grub on the SATA? Have you done anything in the BIOS to make sure the SATA is HD0, or tried booting the SATA with both PATA removed (power and/or control cables disconnected)? Exactly what is the BIOS setting for HD controller(s) when failure is occurring? Are you already trying to use the new motherboard?
I have no idea what file contains those. It's whatever appears after selecting Advanced from the initial boot menu. I have the BIOS configured to give the new drive priority for booting. When I disconnect the PATA drives, I cannot even boot through the DVD. Why is something that used to be so simple now so difficult? Back in the DOS/Windows & OS/2 days, it was simply a matter of copying the partition and setting the boot flag. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-03-23 10:46 (GMT-0400) James Knott composed:
Maybe you should tell us exactly what steps you took rather than
When I used the word "exactly" I was not simply asking for some more information. Exactly would entail a lot more what I've seen since.
summarizing. You might be on the edge of success, missing just one little thing.
I also use volume labels, rather than device ID.
The first thing I did was create mount points for the new partitions, ... I also used fdisk to verify the new drive is bootable.
How exactly can fdisk tell you that? It can tell you whether and where boot flag(s) are set, but not whether the MBR contains code required for boot to initialize.
...I have the BIOS configured to give the new drive priority for booting. When I disconnect the PATA drives, I cannot even boot through the DVD.
That sounds like the SATA has no code in its MBR, and the motherboard's BIOS code isn't designed and/or configured to try OM when HD fails. I haven't seen anything in your thread responses to indicate doing anything designed specifically to ensure the SATA MBR has the code it needs. That can be done quickly and simply via an ancient DOS floppy boot (fdisk /mbr) among other ways.
Why is something that used to be so simple now so difficult? Back in the DOS/Windows & OS/2 days, it was simply a matter of copying the partition and setting the boot flag.
You've made a (passive) choice to use Grub2 now (by not choosing a non-default bootloader). Grub2 is an operating system unto itself, magnitudes more complicated that BIOS compatible boot code that boots DOS, WinDOS and OS/2 (and Grub & Gru2 if compatibly installed; anything installed to a primary partition on HD0 and having a boot flag set to its partition alone), and far more complicated than Grub Legacy. 13.1 does still offer you the option to choose a bootloader simpler than Grub2. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Felix Miata wrote:
You've made a (passive) choice to use Grub2 now (by not choosing a non-default bootloader). Grub2 is an operating system unto itself, magnitudes more complicated that BIOS compatible boot code that boots DOS, WinDOS and OS/2 (and Grub & Gru2 if compatibly installed; anything installed to a primary partition on HD0 and having a boot flag set to its partition alone), and far more complicated than Grub Legacy. 13.1 does still offer you the option to choose a bootloader simpler than Grub2.
Hey -- notice I DIDN'T tell people about the benefits of lilo -- and how it still boots 13.1 from hard disk _without_ an initrd?? People want all this new fancy stuff... and then wonder why their system becomes unmaintainable.... I see far too many changes going into OSuse far too fast with inadequate testing and I know compat with previous versions and standards is being tossed out the window... The directive of "new is better", seems to be dominating all else these days.. Problem is that if we are not sold on "new is better", then we won't fuel our consumer-dependent economy. About a decade ago there was a shift from the US *making things*, to being a "service oriented" economy... but to have that, you have to have people with money willing to buy everything as a disposable service so you can keep reselling to them. It's a capitalist's dream to have what the people keep buying, but if they think they are satisfied buying slows down and then it becomes the capitalist's nightmare. Meanwhile... in othernews, (from a little bit into the future...) Firefox 278.00 was released ....to compete with Chrome 300. Meanwhile users of IE6 were still complaining about broken webites... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Linda Walsh wrote:
People want all this new fancy stuff... and then wonder why their system becomes unmaintainable....
Hmmm... Mebe I should go back to core memory. I have some here. ;-) However, I agree that many of the recent changes are creating problems while fixing things that weren't broken. This is one example, broken XDMCP is another, Then we get to dovecot that's non functioning due to apparmor etc. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/24/2014 07:55 AM, James Knott wrote:
Linda Walsh wrote:
People want all this new fancy stuff... and then wonder why their system becomes unmaintainable....
Hmmm... Mebe I should go back to core memory. I have some here. ;-)
However, I agree that many of the recent changes are creating problems while fixing things that weren't broken. This is one example, broken XDMCP is another, Then we get to dovecot that's non functioning due to apparmor etc.
Oh, I don't know. I upgraded my server earlier this year and the move to 13.1 had all the hassle with the upgrade of dovecot and its conflict with apparmor, but it was easy enough to solve. But that new drive died and I've just been though a install rather than an upgrade and there was no conflict between dovecot 2.1 and apparmor. -- Lead and inspire people. Don't try to manage and manipulate people. Inventories can be managed but people must be lead. - Ross Perot -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
But that new drive died and I've just been though a install rather than an upgrade and there was no conflict between dovecot 2.1 and apparmor.
I did a fresh install a couple of months ago and that's when the problem occurred -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-03-29 03:16, James Knott wrote:
Anton Aylward wrote:
But that new drive died and I've just been though a install rather than an upgrade and there was no conflict between dovecot 2.1 and apparmor.
I did a fresh install a couple of months ago and that's when the problem occurred
I use dovecot and apparmour on both my desktop and laptop. They work fine :-) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 03/28/2014 10:16 PM, James Knott wrote:
Anton Aylward wrote:
But that new drive died and I've just been though a install rather than an upgrade and there was no conflict between dovecot 2.1 and apparmor.
I did a fresh install a couple of months ago and that's when the problem occurred
Perhaps ... I did an install from DVD and then a full zypper update before configuring and starting dovecot. Perhaps ... In the update the apparmor config had been fixed. Perhaps .... -- The mantra of any good security engineer is: 'Security is a not a product, but a process.' It's more than designing strong cryptography into a system; it's designing the entire system such that all security measures, including cryptography, work together. -- Bruce Schneier -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
Perhaps ... I did an install from DVD and then a full zypper update before configuring and starting dovecot. Perhaps ... In the update the apparmor config had been fixed. Perhaps ....
I'll have to see if I can set Apparmor back to normal when I get a chance. At the moment that computer is down for a motherboard transplant. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-03-30 15:59, James Knott wrote:
Anton Aylward wrote:
Perhaps ... I did an install from DVD and then a full zypper update before configuring and starting dovecot. Perhaps ... In the update the apparmor config had been fixed. Perhaps ....
I'll have to see if I can set Apparmor back to normal when I get a chance. At the moment that computer is down for a motherboard transplant.
There was a module in YaST to automatically adjust apparmour profiles, scanning the logs for problems and suggesting the appropriate changes. This module has disappeared. Instead, aa-logprof has a similar functionality, in CLI. More awkward. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Anton Aylward wrote:
But that new drive died and I've just been though a install rather than an upgrade and there was no conflict between dovecot 2.1 and apparmor.
I just tried changing Apparmor to enforce rather than complain with Dovecot. It still causes it to fail. Setting it back to complain restored Dovecot. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-04-03 16:01, James Knott wrote:
Anton Aylward wrote:
But that new drive died and I've just been though a install rather than an upgrade and there was no conflict between dovecot 2.1 and apparmor.
I just tried changing Apparmor to enforce rather than complain with Dovecot. It still causes it to fail. Setting it back to complain restored Dovecot.
Did you try aa-logprof yet? Complain will fill your logs. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. wrote:
On 2014-04-03 16:01, James Knott wrote:
Anton Aylward wrote:
But that new drive died and I've just been though a install rather than an upgrade and there was no conflict between dovecot 2.1 and apparmor. I just tried changing Apparmor to enforce rather than complain with Dovecot. It still causes it to fail. Setting it back to complain restored Dovecot. Did you try aa-logprof yet?
Complain will fill your logs.
I get this response: Reading log entries from /var/log/messages. Updating AppArmor profiles in /etc/apparmor.d. Profile: /usr/sbin/dovecot Execute: /usr/bin/doveconf Severity: unknown (I)nherit / (P)rofile / (C)hild / (N)ame / (U)nconfined / (X)ix / (D)eny / Abo(r)t / (F)inish This conflicts with the man page: (A)llow, (D)eny, (N)ew, (G)lob last piece, (Q)uit So, what am I supposed to do? Why should this even be necessary? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-04-03 16:41, James Knott wrote:
Carlos E. R. wrote:
Did you try aa-logprof yet?
Complain will fill your logs.
I get this response:
Reading log entries from /var/log/messages. Updating AppArmor profiles in /etc/apparmor.d.
Profile: /usr/sbin/dovecot Execute: /usr/bin/doveconf Severity: unknown
(I)nherit / (P)rofile / (C)hild / (N)ame / (U)nconfined / (X)ix / (D)eny / Abo(r)t / (F)inish ... So, what am I supposed to do? Why should this even be necessary?
Well, that is what you have to do to correct *your* apparmour installation. I don't know what all the above means, the "man" is close to unreadable, as typical (you noticed). According to the manual, the options are: (A)llow, (D)eny, (N)ew, (G)lob last piece, (Q)uit no more... So you have to make guesses. I take "Inherit" to be a variant of "Allow", so sometimes I use that, or "Allow". In this case it is asking if running "doveconf" should be allowed, and understand it should. Just work with the options in the manual, ignore the rest. When there is an update to AA, your modifications are lost, so it is of no consequence if you could create yourself a better profile by making use of the non-documented options. Let the developers use them. Sigh... -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. wrote:
Well, that is what you have to do to correct *your* apparmour installation. I don't know what all the above means, the "man" is close to unreadable, as typical (you noticed). According to the manual, the options are:
(A)llow, (D)eny, (N)ew, (G)lob last piece, (Q)uit
I let it run. After inherit, there were several allows. Still, after running it, it still won't work with enforce. This is why I complain so much about the "improvements" that have been made that break so many things. This is complete incompetence, that would have got me fired had I done that at IBM, or elsewhere for that matter. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-04-03 23:14, James Knott wrote:
Carlos E. R. wrote:
Well, that is what you have to do to correct *your* apparmour installation. I don't know what all the above means, the "man" is close to unreadable, as typical (you noticed). According to the manual, the options are:
(A)llow, (D)eny, (N)ew, (G)lob last piece, (Q)uit
I let it run. After inherit, there were several allows. Still, after running it, it still won't work with enforce.
You have to restart dovecot, wait a bit, then check again with aa-logprof. It is often several iterations.
This is why I complain so much about the "improvements" that have been made that break so many things. This is complete incompetence, that would have got me fired had I done that at IBM, or elsewhere for that matter.
Calm down... the release notes said that we had to expect problems with apparmour. In case we found them, we had to report them. We did, they created an update or two, and now works now for many people, just not not for you... Wait. Run "rcrpmconfigcheck". Do you see any output related to apparmour or dovecot? If you do, that's your problem. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. wrote:
Run "rcrpmconfigcheck". Do you see any output related to apparmour or dovecot? /etc/apparmor.d/usr.lib.dovecot.deliver.rpmnew /etc/apparmor.d/usr.lib.dovecot.imap.rpmnew /etc/apparmor.d/usr.lib.dovecot.imap-login.rpmnew /etc/apparmor.d/usr.lib.dovecot.managesieve-login.rpmnew /etc/apparmor.d/usr.lib.dovecot.pop3.rpmnew /etc/apparmor.d/usr.lib.dovecot.pop3-login.rpmnew /etc/apparmor.d/usr.sbin.dovecot.rpmnew
If you do, that's your problem.
Why is it my problem when this is a fresh install just a couple of months ago? Shouldn't the distro be expected to work properly "out of the box"? Again, if I did something that failed in such a manner, I would have been fired for incompetence. Part of my work was integration testing, to make sure everything worked properly. This clearly wasn't done with Apparmor and certain other aspects of recent versions of openSUSE. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
Why is it my problem when this is a fresh install just a couple of months ago?
Sorry, that should have said weeks ago, though it also happened back in January with a previous fresh install, but originate with an upgrade to 13.1 from 12.3. Bottom line, installed fresh off the DVD and it's already broken. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-04-04 04:31, James Knott wrote:
James Knott wrote:
Why is it my problem when this is a fresh install just a couple of months ago?
Sorry, that should have said weeks ago, though it also happened back in January with a previous fresh install, but originate with an upgrade to 13.1 from 12.3.
Bottom line, installed fresh off the DVD and it's already broken.
Please. Run the command I asked you to. You are wasting time, I'm about to go to sleep :-) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. wrote:
Bottom line, installed fresh off the DVD and it's already broken. Please. Run the command I asked you to. You are wasting time, I'm about to go to sleep :-)
You mean aa-logprof? Yes, I already did, as I reported in another message and it didn't work. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-04-04 13:55, James Knott wrote:
Carlos E. R. wrote:
Bottom line, installed fresh off the DVD and it's already broken. Please. Run the command I asked you to. You are wasting time, I'm about to go to sleep :-)
You mean aa-logprof? Yes, I already did, as I reported in another message and it didn't work.
No. "rcrpmconfigcheck" And, to use aa-logprof you have to: aa-logprof restart dovecot aa-logprof restart dovecot aa-logprof restart dovecot aa-logprof restart dovecot aa-logprof restart dovecot As many times as needed till there is nothing coming out of aa-logprof -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/05/2014 07:57 AM, Carlos E. R. wrote:
On 2014-04-04 13:55, James Knott wrote:
Carlos E. R. wrote:
Bottom line, installed fresh off the DVD and it's already broken. Please. Run the command I asked you to. You are wasting time, I'm about to go to sleep :-)
You mean aa-logprof? Yes, I already did, as I reported in another message and it didn't work.
No. "rcrpmconfigcheck"
And, to use aa-logprof you have to:
aa-logprof restart dovecot aa-logprof restart dovecot aa-logprof restart dovecot aa-logprof restart dovecot aa-logprof restart dovecot
As many times as needed till there is nothing coming out of aa-logprof
:-) Back when I did that it only took 3 iterations :-) - -- "To ask the right question is already half the solution of a problem". -- Carl Jung. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTQUWsAAoJEGKKOXJjLzXhQ2UQAKHpX9a1EOQySSB+248KyrdV mcdgLd7es5aNwImLduxirUdXTCyLtt9UHoy0QCGnhS2GF+C0Hi+7i5dA3ns0IU/g skElRhW+MPPozeFS4Xt0XSJbN0p14BaiyhizD2N+iuG808Xt4YDJrEOkKoIjy0Ce Sw/FuZMvKtFizWQq28kVbGCK4HJD8sEK3F6wSVDn9mrKiSW5VTiLNpOjAgZICy1D YU07kniKGGq6YzAzEl5uyju6WFqn/Jw+uhrfv1S+fRat9cS3geEgPST4yPmBAwzf t37I9OvkrXhRHFVPxfjSL60khtgXe2TU0Y3KRJH78/pAVsh3d8ppYtFHSIWQUCae a8e3ywGVAD97o/mXk9jZwkOYWmDoKUHltmn0wAe35h3MkwIUg35zCxNI+j8oyLJW FG+X/7w6yUl3pR3966MKysn4J7ofYAp9JemE0DUcM8VFYtJCAOG2kkafR6hJmK08 DeOqs9LJQAJiG4p+y602jU9xrQ69IbY2iNcWPGvDPgUnvBpAUhI3mMLhDprtZN9k MxH4vRDuyleMIyZjW1Gykyitpw7WoiF8W+mLn53xwdpizoCoLyo0Qol/HcT7P3/i jD0BaiJHvWKhbtLrbqp4S1CiBtOWh06bQE3ciL49u75Tc3KM7sTamB5IL5dBOq5m bJyKF2r3iCt9WJxVNdOv =u0v9 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-04-06 14:16, Anton Aylward wrote:
On 04/05/2014 07:57 AM, Carlos E. R. wrote:
As many times as needed till there is nothing coming out of aa-logprof
:-) Back when I did that it only took 3 iterations :-)
Yes, that's typical. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2014-04-03 at 22:22 -0400, James Knott wrote: For some reason I don't know, I missed this post. Sorry.
Carlos E. R. wrote:
Run "rcrpmconfigcheck". Do you see any output related to apparmour or dovecot? /etc/apparmor.d/usr.lib.dovecot.deliver.rpmnew /etc/apparmor.d/usr.lib.dovecot.imap.rpmnew /etc/apparmor.d/usr.lib.dovecot.imap-login.rpmnew /etc/apparmor.d/usr.lib.dovecot.managesieve-login.rpmnew /etc/apparmor.d/usr.lib.dovecot.pop3.rpmnew /etc/apparmor.d/usr.lib.dovecot.pop3-login.rpmnew /etc/apparmor.d/usr.sbin.dovecot.rpmnew
If you do, that's your problem.
Why is it my problem when this is a fresh install just a couple of months ago? Shouldn't the distro be expected to work properly "out of the box"?
"This is your problem" it is not that I say that you caused this problem. I meant that this is the cause of your problem. Even if I'm fluent in English, it is not my first language, and some times maybe I do not express myself well enough. :-) So, your problem is that, even although there was an online update that should have corrected your problem with dovecot and AA, it was not /really/ applied. For instance, you had problems with the "/usr/sbin/dovecot" AA profile. But the update is in "/etc/apparmor.d/usr.sbin.dovecot.rpmnew", while the old and active file is "/etc/apparmor.d/usr.sbin.dovecot". You have to replace /etc/apparmor.d/usr.sbin.dovecot with /etc/apparmor.d/usr.sbin.dovecot.rpmnew, and do that for all the "*rpmnew" files in that list. This is your job as system administrator ;-) The script "rcrpmconfigcheck" runs on every boot, I think. When you boot in text mode you see it, but with modern graphical displays, you miss it. You can also look on the file "/var/adm/rpmconfigcheck". After any update you should have a look at the output of "rcrpmconfigcheck", and decide what to do. Typically I make a backup of the files, then open both with "meld", to compare the differences, keep what I want, and accept the new proposed changes in the update. As I say, it is your job as Linux system administrator, you have to earn your keep >:-) Now you'll ask: why were not the files replaced directly? Well, because maybe you did local changes to them that you want to keep. Although the rpm command is capable of finding out if the configuration files were changed, and if not, replace them directly. Why this happens some times, and not some other times, I don't know. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlNB2Z4ACgkQtTMYHG2NR9Uy6ACfbRfrBNnlMHBEPf6SdsIUj8aO tYYAnjM8XpWcZiMuLnHPf+TpchrUXjNH =Kfzh -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
Did you try aa-logprof yet?
Complain will fill your logs.
Which log? There's nothing under apparmor. If it's log rotated, I could probably live with it or, failing that, see about linking to /dev/null. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2014-04-03 at 17:26 -0400, James Knott wrote:
Carlos E. R. wrote:
Did you try aa-logprof yet?
Complain will fill your logs.
Which log? There's nothing under apparmor. If it's log rotated, I could probably live with it or, failing that, see about linking to /dev/null.
Typically /var/log/audit/* No, instead of having an AA perpetually in complain mode, which causes continuous log activity, just deactivate those profiles. Simply remove the AA profiles for that application, or move to a backup directory. Complain mode does no protection, anyway. Its purpose is to fill the logs, so that you later run aa-logprof and adapt the profiles. But if you are not going to do that anyway, better remove them. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlNB24YACgkQtTMYHG2NR9XpdACeOg/xnet2Z47gw1JntuTSmWyJ o1YAn1onFqvxPbBdrG0YFRzxo3ng4R6V =G+xo -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/03/2014 10:32 AM, Carlos E. R. wrote:
On 2014-04-03 16:01, James Knott wrote:
Anton Aylward wrote:
But that new drive died and I've just been though a install rather than an upgrade and there was no conflict between dovecot 2.1 and apparmor.
I just tried changing Apparmor to enforce rather than complain with Dovecot. It still causes it to fail. Setting it back to complain restored Dovecot.
Did you try aa-logprof yet?
Complain will fill your logs.
Previously I'd used that quite successfully. As I said, on this install, apparmor hasn't been a problem. -- shin (n): A device for finding furniture in the dark. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Sun, 23 Mar 2014 08:19:22 -0400 James Knott <james.knott@rogers.com> пишет:
In preperation for a new motherboard, I'm moving my system from a pair of IDE drives to a SATA drive. I have copied all the partitions by using cp -a to the new drive. However I cannot get the system to boot with / and /boot on the new system. I have tried various things including the Yast Boot Loader and grub2-mkconfig, but can't seem to get the new partitions to work. While I realize I could just reinstall to the new drive, I'd prefer to move the existing system over.
Do you want to install grub2 in MBR or on partition?
BTW, with the original Grub, it was possible to have descriptive titles in the boot menu, so that you knew what you were booting. Why isn't this possible with Grub2. Even in the advanced menu, I only see 4 entries with identical titles.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrey Borzenkov wrote:
Do you want to install grub2 in MBR or on partition?
I though the usual practice with Linux was to have grub on the boot partition, with the MBR pointing to it. That's the way it's configured here. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 23/03/2014 16:13, James Knott a écrit :
I though the usual practice with Linux was to have grub on the boot partition, with the MBR pointing to it. That's the way it's configured here.
it's the way for multiboot. When you have only one linux, you can use MBR. Some installs needs MBR the "MBR pointing" *is* the boot flag jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Sun, 23 Mar 2014 11:13:05 -0400 James Knott <james.knott@rogers.com> пишет:
Andrey Borzenkov wrote:
Do you want to install grub2 in MBR or on partition?
I though the usual practice with Linux was to have grub on the boot partition, with the MBR pointing to it. That's the way it's configured here.
a) mount your new boot partition anywhere; e.g. /newboot b) run "grub2-install --force --boot-directory=/newboot /dev/your-boot-partion" c) use fdisk to mark your boot partition as active. I assume you have valid MBR on this disk ... This will make your new boot partition bootable with grub2 as bootloader and grub2 will use new boot partition to search for executable and configuration files. Assuming your BIOS is set to boot from this disk. To properly create grub.cfg and initrd for new configuration: mount /dev/new-root-device /mnt mount /dev/new-boot-device /mnt/boot mount --bind /dev /mnt/dev mount --bind /proc /mnt/proc mount --bind /sys /mnt/sys mount --bind /run /mnt/run chroot /mnt grub2-mkconfig > /boot/grub2/grub.cfg mkinitrd Do not do it from openSUSE DVD rescue boot, it has weird links in /dev that may screw device detection (at least for LVM or anything that uses device mapper). Having duplicate filesystem labels or uuids may be a problem as well. Probably grub-mkconfig needs better support for off-root rescue root. Patch was floating upstream, need to get a look once more. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
somes images of the boot grub editor http://dodin.info/owncloud/public.php?service=files&t=4da8642793614c6439a6d52191d820ac from graphical boot, type "e", then "Control c" (small change from grub legacy, but it's written on screen) then you can load kernel, initrd, gives root now loading a kernel is no more "kernel" but "linux" complete manal is http://www.gnu.org/software/grub/manual/grub.html#Command_002dline-interface I don't see anymore root? jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-03-23 11:13 (GMT-0400) James Knott composed:
I though the usual practice with Linux was to have grub on the boot partition, with the MBR pointing to it. That's the way it's configured here.
Across the entirety of modern Linux distros, Grub anywhere other than the MBR seems to have become the exception. Grub2 upstream is rather insistent the only place to install Grub2 is on the MBR. Fedora's installer gives only 2 bootloader choices: 1-Grub2 on MBR; 2-install no bootloader (my selection always). Under this roof, Grub is never installed on any MBR, and Grub2 is infrequently installed anywhere at all, most recently yesterday, when Wheezy offered no apparent choice other than Grub2. Most of my systems have Grub Legacy installed on a primary partition that is never mounted to /boot, and is managed entirely by myself via MCedit and Grub shell. Most of my installations, all of my openSUSE installations, have Grub Legacy installed to their / partitions. A few less flexible distros have various Grub2 incarnations installed to their roots. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Felix Miata wrote:
Across the entirety of modern Linux distros, Grub anywhere other than the MBR seems to have become the exception. Grub2 upstream is rather insistent the only place to install Grub2 is on the MBR. Fedora's installer gives only 2 bootloader choices: 1-Grub2 on MBR; 2-install no bootloader (my selection always).
I just checked Yast Boot Loader and it wants to put Grub2 in the boot partition. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (8)
-
Andrey Borzenkov -
Anton Aylward -
Carlos E. R. -
Carlos E. R. -
Felix Miata -
James Knott -
jdd -
Linda Walsh