| 1 |
On Thu, Mar 29, 2012 at 2:15 PM, Dale <rdalek1967@×××××.com> wrote: |
| 2 |
> Canek Peláez Valdés wrote: |
| 3 |
> |
| 4 |
>> Can you try doing |
| 5 |
>> |
| 6 |
>> dracut -H /boot/initramfs-<kernel version here> |
| 7 |
>> |
| 8 |
>> ?? |
| 9 |
>> |
| 10 |
>> The man page from dracut says that -H is for the "current host" |
| 11 |
>> instead of a "generic host". Maybe the "generic host" configuration is |
| 12 |
>> messing up something with su that your actual host configuration |
| 13 |
>> needs. |
| 14 |
>> |
| 15 |
>> I use -H. As I have ben saying, my initramfs it's pretty up in sync |
| 16 |
>> with my normal system. |
| 17 |
>> |
| 18 |
>> Regards. |
| 19 |
> |
| 20 |
> |
| 21 |
> Notice, I make the distinction between Console and Konsole by making the |
| 22 |
> first letter capitalized. It kind of gets confusing. :/ |
| 23 |
> |
| 24 |
> I had to reboot so I made a new init thingy with the -H switch. It |
| 25 |
> works in Console but nothing root works in KDE. I get the same error. |
| 26 |
> Heck, Konsole won't even try to come up much less ask for my password. |
| 27 |
> Krusader asks for password and says that su is not in the path. This is |
| 28 |
> similar to what I got when I was in a Console too. |
| 29 |
> |
| 30 |
> So, boot without init thingy, everything works fine. Boot with the init |
| 31 |
> thingy, I can't access things in KDE as root. All I do is reboot. I |
| 32 |
> don't change or edit anything other than selecting a different entry in |
| 33 |
> grub. |
| 34 |
> |
| 35 |
> I use Konsole when I emerge and such as that. I use Krusader, since |
| 36 |
> Konqueror developed a bug, to edit config files. I don't care to switch |
| 37 |
> to a Console to emerge something or edit a config file. This is not |
| 38 |
> going to work for me long term. |
| 39 |
> |
| 40 |
> Also, keep in mind, I boot the EXACT same kernel whether I use the init |
| 41 |
> thingy or not. All I do is remove the stuff the init thingy needs to |
| 42 |
> work. |
| 43 |
> |
| 44 |
> Go figure. |
| 45 |
|
| 46 |
I'm a little confused: you log in KDE as a regular user, open a |
| 47 |
Konsole, type "su -", and what happens? |
| 48 |
|
| 49 |
What do you mean with "Konsole won't even try to come up"? |
| 50 |
|
| 51 |
In the shell that Krusader provides (which I assume you run as a |
| 52 |
regular user), what it's the result of "which su"? And also, what |
| 53 |
happens when (inside the shell from Krusader) you run /bin/su? |
| 54 |
|
| 55 |
If not for the fact that you say that in a virtual console su works, I |
| 56 |
would be willing to suggest that your initramfs never does the |
| 57 |
switch_root, and so you end up with the minimal / from the initramfs, |
| 58 |
and your normal /usr. That would be beyond bizarre, but if you *can* |
| 59 |
use su in a virtual console, then it should be there. |
| 60 |
|
| 61 |
I usally log in in GNOME, open a gnome-terminal, and set a fixed |
| 62 |
number of tabs in gnome-terminal where I "su -", and work as root in |
| 63 |
there. I also can run an X11 program as root with "su -lc |
| 64 |
/usr/bin/gedit", but I almost never do that (although it works; I just |
| 65 |
checked). |
| 66 |
|
| 67 |
I don't think I understand how do you use su. Could you explain it to |
| 68 |
me, please? |
| 69 |
|
| 70 |
One last thing: create a directory /tmp/whatever, and inside it |
| 71 |
unpack your initramfs: |
| 72 |
|
| 73 |
zcat /boot/init-thingie | cpio -i |
| 74 |
|
| 75 |
Could you do a "ls -R /tmp/whatever" so we can see what actually ends |
| 76 |
up in yout initramfs? |
| 77 |
|
| 78 |
Regards. |
| 79 |
-- |
| 80 |
Canek Peláez Valdés |
| 81 |
Posgrado en Ciencia e Ingeniería de la Computación |
| 82 |
Universidad Nacional Autónoma de México |
Archives