[opensuse] Re: [opensuse-factory] Unnecessary Packages in Yast: Can they be removed without consequence?

newer
[opensuse] XFCE : Purpose of...

older
[opensuse] Browsers :...

Oddball

31 Oct 2012 31 Oct '12

19:58

Op 10/31/2012 8:38 PM, Felix Miata schreef:

...

On 2012-10-31 19:59 (GMT+0100) Carlos E. R. composed:

...
Oddball wrote:

...
...
How to mkinitrd from here if there is no kernel booted? Is it possible to boot the kernel from minimal cli?

...
- From grub console, no, not that I know.

Menu.lst is script. Anything in it can be entered at a grub> prompt. If you have a grub> prompt, and there is an installed and functional kernel and initrd, grub can find it/them, and get you booted by entering appropriate kernel, initrd & boot commands.

that cli is minimal, and lacks the command: find. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Show replies by date

Felix Miata

31 Oct 31 Oct

20:56

New subject: [opensuse] Unnecessary Packages in Yast: Can they be removed without consequence?

On 2012-10-31 20:58 (GMT+0100) Oddball composed:

...

Felix Miata composed:

...

...
Menu.lst is script. Anything in it can be entered at a grub> prompt. If you have a grub> prompt, and there is an installed and functional kernel and initrd, grub can find it/them, and get you booted by entering appropriate kernel, initrd & boot commands.

...

that cli is minimal, and lacks the command: find.

All CLI interfaces I'm familiar with have a prompt of some sort. Do you have any prompt on that screen? Grub Legacy's is grub>. Root's bash shell ends in #. Other's bash shell ends with $. If you have no prompt, you have no CLI, just a useless screen implying no instructions to proceed further. -- "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

Oddball

22:53

New subject: [opensuse] Unnecessary Packages in Yast: Can they be removed without consequence?

...

On 2012-10-31 20:58 (GMT+0100) Oddball composed:

...
Felix Miata composed:

...
...
Menu.lst is script. Anything in it can be entered at a grub> prompt. If you have a grub> prompt, and there is an installed and functional kernel and initrd, grub can find it/them, and get you booted by entering appropriate kernel, initrd & boot commands.

...
that cli is minimal, and lacks the command: find.

All CLI interfaces I'm familiar with have a prompt of some sort. Do you have any prompt on that screen? Grub Legacy's is grub>. Root's bash shell ends in #. Other's bash shell ends with $. If you have no prompt, you have no CLI, just a useless screen implying no instructions to proceed further. Yes, i know, it sounds stupid. But it is very limited. It says grub> _

Op 10/31/2012 9:56 PM, Felix Miata schreef: the only thing it can answer is: error: can't find command, error: filename expected. It has a very limited input size, kernelname and number do not fit. Just behind the bios, nothing is loaded yet. But if you can supply me with the proper comands, i will try what can be done with this prompt. sda3 /boot Kernel: Linux 3.7.0-rc2-4-desktop i686 The other thing is a mistake i made: i never use lvm. This time i thought ok, lets try it. Lvm is not supported yet in Knoppix, so the partitions could not get mounted, only windows and /boot were visible. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata

23:42

New subject: [opensuse] boot without Grub's menu (was: Unnecessary Packages in...)

On 2012-10-31 23:53 (GMT+0100) Oddball composed:

...

Felix Miata composed:

...

...
All CLI interfaces I'm familiar with have a prompt of some sort. Do you have any prompt on that screen? Grub Legacy's is grub>. Root's bash shell ends in #. Other's bash shell ends with $. If you have no prompt, you have no CLI, just a useless screen implying no instructions to proceed further.

...

Yes, i know, it sounds stupid. But it is very limited. It says grub> _ the only thing it can answer is: error: can't find command, error: filename expected.

That's one of the "lovely" things the Grub overhaul gave us. "Find" on Grub Legacy was inexplicably replaced by "search" in Grub 2.

...

It has a very limited input size, kernelname and number do not fit. Just behind the bios, nothing is loaded yet.

...

But if you can supply me with the proper comands, i will try what can be done with this prompt.

Here there's no such limitation, but this is the only Grub 2 prompt I have, on Kubuntu. So I don't know if on openSUSE there may be some difference.

...

sda3 /boot Kernel: Linux 3.7.0-rc2-4-desktop i686

Forget about both find and search. If sda3 is correct, you don't need to bother. If /boot is on LVM, I can't help, other than to suggest a fresh install to get around your mountain of 12.2 problems. If it's a separate boot partition rather than a /boot directory on your / partition, this will probably do it: grub> linux (hd0,msdos3)/vmlinuz root=/dev/sda3 noresume 3 grub> initrd (hd0,msdos3)/initrd grub> boot If /boot is part of / on a normal partition rather than LVM, then: grub> linux (hd0,msdos3)/boot/vmlinuz root=/dev/sda3 noresume 3 grub> initrd (hd0,msdos3)/boot/initrd grub> boot Note the above wouldn't work with Grub Legacy. Instead: If it's a separate boot partition rather than a /boot directory on your / partition, this will probably do it: grub> kernel (hd0,2)/vmlinuz root=/dev/sda3 noresume 3 grub> initrd (hd0,2)/initrd grub> boot If /boot is part of / on a normal partition rather than LVM, then: grub> kernel (hd0,2)/boot/vmlinuz root=/dev/sda3 noresume 3 grub> initrd (hd0,2/boot/initrd grub> boot

...

The other thing is a mistake i made: i never use lvm. This time i thought ok, lets try it. Lvm is not supported yet in Knoppix, so the partitions could not get mounted, only windows and /boot were visible.

If /boot is its own separate partition for booting LVM /, then lack of LVM support in Knoppix doesn't matter. More importantly, to "install" Grub Legacy, no mounting of anything is necessary. http://orgs.man.ac.uk/documentation/grub/grub_3.html#SEC9 completely covers it. -- "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

Oddball

1 Nov 1 Nov

06:48

New subject: [opensuse] boot without Grub's menu

Op 11/1/2012 12:42 AM, Felix Miata schreef:

...

On 2012-10-31 23:53 (GMT+0100) Oddball composed:

...
Felix Miata composed:

...
...
All CLI interfaces I'm familiar with have a prompt of some sort. Do you have any prompt on that screen? Grub Legacy's is grub>. Root's bash shell ends in #. Other's bash shell ends with $. If you have no prompt, you have no CLI, just a useless screen implying no instructions to proceed further.

...
Yes, i know, it sounds stupid. But it is very limited. It says grub> _ the only thing it can answer is: error: can't find command, error: filename expected.

That's one of the "lovely" things the Grub overhaul gave us. "Find" on Grub Legacy was inexplicably replaced by "search" in Grub 2.

...
It has a very limited input size, kernelname and number do not fit. Just behind the bios, nothing is loaded yet.

...
But if you can supply me with the proper comands, i will try what can be done with this prompt.

Here there's no such limitation, but this is the only Grub 2 prompt I have, on Kubuntu. So I don't know if on openSUSE there may be some difference.

...
sda3 /boot Kernel: Linux 3.7.0-rc2-4-desktop i686

Forget about both find and search. If sda3 is correct, you don't need to bother.

If /boot is on LVM, I can't help, other than to suggest a fresh install to get around your mountain of 12.2 problems.

If it's a separate boot partition rather than a /boot directory on your / partition, this will probably do it:

grub> linux (hd0,msdos3)/vmlinuz root=/dev/sda3 noresume 3 grub> initrd (hd0,msdos3)/initrd grub> boot

If /boot is part of / on a normal partition rather than LVM, then: grub> linux (hd0,msdos3)/boot/vmlinuz root=/dev/sda3 noresume 3 grub> initrd (hd0,msdos3)/boot/initrd grub> boot

Note the above wouldn't work with Grub Legacy. Instead: If it's a separate boot partition rather than a /boot directory on your / partition, this will probably do it:

grub> kernel (hd0,2)/vmlinuz root=/dev/sda3 noresume 3 error: can't find command 'kernel' grub> initrd (hd0,2)/initrd grub> boot

If /boot is part of / on a normal partition rather than LVM, then: grub> kernel (hd0,2)/boot/vmlinuz root=/dev/sda3 noresume 3 grub> initrd (hd0,2/boot/initrd grub> boot

...
The other thing is a mistake i made: i never use lvm. This time i thought ok, lets try it. Lvm is not supported yet in Knoppix, so the partitions could not get mounted, only windows and /boot were visible.

If /boot is its own separate partition for booting LVM /, then lack of LVM support in Knoppix doesn't matter.

More importantly, to "install" Grub Legacy, no mounting of anything is necessary. http://orgs.man.ac.uk/documentation/grub/grub_3.html#SEC9 completely covers it.

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata

06:59

New subject: [opensuse] boot without Grub's menu

On 2012-11-01 07:48 (GMT+0100) Oddball composed:

...

Op 11/1/2012 12:42 AM, Felix Miata schreef:

...

...
If it's a separate boot partition rather than a /boot directory on your / partition, this will probably do it:

...

...
grub> linux (hd0,msdos3)/vmlinuz root=/dev/sda3 noresume 3 grub> initrd (hd0,msdos3)/initrd grub> boot

...

...
If /boot is part of / on a normal partition rather than LVM, then: grub> linux (hd0,msdos3)/boot/vmlinuz root=/dev/sda3 noresume 3 grub> initrd (hd0,msdos3)/boot/initrd grub> boot

Above is for Grub2 #########################################################

...

...
Note the above wouldn't work with Grub Legacy. Instead: ######################################################### Below is for Grub Legacy, which I included because of your incomplete installation of Grub Legacy, and for comparison, and an expectation you might eventually need it.

...

...
If it's a separate boot partition rather than a /boot directory on your / partition, this will probably do it:

...

...
grub> kernel (hd0,2)/vmlinuz root=/dev/sda3 noresume 3

...

error: can't find command 'kernel'

Kernel is for Grub Legacy. Grub2, which is what you still have, wants linux instead, as above.

...

...
grub> initrd (hd0,2)/initrd grub> boot

...

...
If /boot is part of / on a normal partition rather than LVM, then: grub> kernel (hd0,2)/boot/vmlinuz root=/dev/sda3 noresume 3 grub> initrd (hd0,2/boot/initrd grub> boot -- "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

Oddball

08:12

New subject: [opensuse] boot without Grub's menu

Op 01-11-12 07:59, Felix Miata schreef:

...

On 2012-11-01 07:48 (GMT+0100) Oddball composed:

...
Op 11/1/2012 12:42 AM, Felix Miata schreef:

...
...
If it's a separate boot partition rather than a /boot directory on your / partition, this will probably do it:

...
...
grub> linux (hd0,msdos3)/vmlinuz root=/dev/sda3 noresume 3 grub> initrd (hd0,msdos3)/initrd grub> boot It booted up to the stage where 'no init' was found.

These are the last words:

...

/dev/sda3: clean, 295/38760 files, 46394/154624 blocks fsck succeeded. Monting root device read-write. Mounting root /dev/sda3 mount -o rw,acl,user_xattr -t ext4 /dev/sda3 /root [ 2.866574] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: acl,user_xattr No init found. Try passing init= option to the kernel. umount: /dev/pts: target is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1) umount: /dev: target is busy.

I tried it it 3 times, the break shows the first and third attempt.

...

...
...
If /boot is part of / on a normal partition rather than LVM, then: grub> linux (hd0,msdos3)/boot/vmlinuz root=/dev/sda3 noresume 3 grub> initrd (hd0,msdos3)/boot/initrd grub> boot

...

Above is for Grub2 #########################################################

...
...
Note the above wouldn't work with Grub Legacy. Instead: ######################################################### Below is for Grub Legacy, which I included because of your incomplete installation of Grub Legacy, and for comparison, and an expectation you might eventually need it.

...
...
If it's a separate boot partition rather than a /boot directory on your / partition, this will probably do it:

...
...
grub> kernel (hd0,2)/vmlinuz root=/dev/sda3 noresume 3

...
error: can't find command 'kernel'

Kernel is for Grub Legacy. Grub2, which is what you still have, wants linux instead, as above.

...
...
grub> initrd (hd0,2)/initrd grub> boot

...
...
If /boot is part of / on a normal partition rather than LVM, then: grub> kernel (hd0,2)/boot/vmlinuz root=/dev/sda3 noresume 3 grub> initrd (hd0,2/boot/initrd grub> boot

-- Enjoy your time around, Oddball (M9.) (Now or never...) OS: Linux 2.6.37.1-1.2-desktop x86_64 Huidige gebruiker: oddball@AMD64x2sfn1 Systeem: openSUSE 11.4 (x86_64) KDE: 4.6.00 (4.6.0) "release 6" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata

08:50

New subject: [opensuse] boot without Grub's menu

On 2012-11-01 09:12 (GMT+0100) Oddball composed:

...

...
...
...
grub> linux (hd0,msdos3)/vmlinuz root=/dev/sda3 noresume 3 grub> initrd (hd0,msdos3)/initrd grub> boot

...

It booted up to the stage where 'no init' was found.

...

These are the last words:

...

...
/dev/sda3: clean, 295/38760 files, 46394/154624 blocks fsck succeeded. Monting root device read-write. Mounting root /dev/sda3 mount -o rw,acl,user_xattr -t ext4 /dev/sda3 /root [ 2.866574] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: acl,user_xattr No init found. Try passing init= option to the kernel. umount: /dev/pts: target is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1) umount: /dev: target is busy.

...

I tried it it 3 times, the break shows the first and third attempt.

I think this is because root=/dev/sda3 is wrong for your LVM configuration. If you can get a look at /etc/fstab booted to openSUSE rescue, Knoppix or other live media, then substitute what you find for /dev/sda3 after root=. Grub.cfg should also have what you need if you can find it and figure it out. Sharing fstab and grub.cfg here might help. If this doesn't work, it's probably time to start with a fresh install, because even if you get it booted, you've still got both the KDM background problem to solve, Grub Legacy to finish installing, and root login trouble to solve. -- "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

Oddball

09:06

New subject: [opensuse] boot without Grub's menu

Op 01-11-12 09:50, Felix Miata schreef:

...

On 2012-11-01 09:12 (GMT+0100) Oddball composed:

...
...
...
...
grub> linux (hd0,msdos3)/vmlinuz root=/dev/sda3 noresume 3 grub> initrd (hd0,msdos3)/initrd grub> boot

...
It booted up to the stage where 'no init' was found.

...
These are the last words:

...
...
/dev/sda3: clean, 295/38760 files, 46394/154624 blocks fsck succeeded. Monting root device read-write. Mounting root /dev/sda3 mount -o rw,acl,user_xattr -t ext4 /dev/sda3 /root [ 2.866574] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: acl,user_xattr No init found. Try passing init= option to the kernel. umount: /dev/pts: target is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1) umount: /dev: target is busy.

...
I tried it it 3 times, the break shows the first and third attempt.

I think this is because root=/dev/sda3 is wrong for your LVM configuration. If you can get a look at /etc/fstab booted to openSUSE rescue, Knoppix or other live media, then substitute what you find for /dev/sda3 after root=. Grub.cfg should also have what you need if you can find it and figure it out. Sharing fstab and grub.cfg here might help.

If this doesn't work, it's probably time to start with a fresh install, because even if you get it booted, you've still got both the KDM background problem to solve, Grub Legacy to finish installing, and root login trouble to solve.

Yes. Probably i am going to download and burn the kde-live cd. Than save /home to another drive, and get rid of lvm. Maybe i had a hunch of why i never wanted to use it before... I always created my partitions myself, and in the early days, there used to be a lot more than only / , swap, /boot and /home... Also /boot i used ext2 for it always. Just start over and install new. -- Enjoy your time around, Oddball (M9.) (Now or never...) OS: Linux 2.6.37.1-1.2-desktop x86_64 Huidige gebruiker: oddball@AMD64x2sfn1 Systeem: openSUSE 11.4 (x86_64) KDE: 4.6.00 (4.6.0) "release 6" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata

08:58

New subject: [opensuse] boot without Grub's menu

On 2012-11-01 09:12 (GMT+0100) Oddball composed:

...

...
...
...
grub> linux (hd0,msdos3)/vmlinuz root=/dev/sda3 noresume 3 grub> initrd (hd0,msdos3)/initrd grub> boot

...

It booted up to the stage where 'no init' was found.

...

These are the last words:

...
/dev/sda3: clean, 295/38760 files, 46394/154624 blocks fsck succeeded. Monting root device read-write. Mounting root /dev/sda3 mount -o rw,acl,user_xattr -t ext4 /dev/sda3 /root [ 2.866574] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: acl,user_xattr No init found. Try passing init= option to the kernel. umount: /dev/pts: target is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1) umount: /dev: target is busy.

...

I tried it it 3 times, the break shows the first and third attempt.

Instead of grub> linux (hd0,msdos3)/vmlinuz root=/dev/sda3 noresume 3 try grub> linux (hd0,msdos3)/vmlinuz noresume 3 It may be that root=/dev/sda3 is overriding a default setting within the initrd that would otherwise work. -- "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

Oddball

09:33

New subject: [opensuse] boot without Grub's menu

Op 01-11-12 09:58, Felix Miata schreef:

...

On 2012-11-01 09:12 (GMT+0100) Oddball composed:

...
...
...
...
grub> linux (hd0,msdos3)/vmlinuz root=/dev/sda3 noresume 3 grub> initrd (hd0,msdos3)/initrd grub> boot

...
It booted up to the stage where 'no init' was found.

...
These are the last words:

...
/dev/sda3: clean, 295/38760 files, 46394/154624 blocks fsck succeeded. Monting root device read-write. Mounting root /dev/sda3 mount -o rw,acl,user_xattr -t ext4 /dev/sda3 /root [ 2.866574] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: acl,user_xattr No init found. Try passing init= option to the kernel. umount: /dev/pts: target is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1) umount: /dev: target is busy.

...
I tried it it 3 times, the break shows the first and third attempt.

Instead of

grub> linux (hd0,msdos3)/vmlinuz root=/dev/sda3 noresume 3

try

grub> linux (hd0,msdos3)/vmlinuz noresume 3

It may be that root=/dev/sda3 is overriding a default setting within the initrd that would otherwise work.

That is worth the try.. ;-) (as the download is stil going on) Another thing: Do you know if .thunderbirds contains all the mail? -- Enjoy your time around, Oddball (M9.) (Now or never...) OS: Linux 2.6.37.1-1.2-desktop x86_64 Huidige gebruiker: oddball@AMD64x2sfn1 Systeem: openSUSE 11.4 (x86_64) KDE: 4.6.00 (4.6.0) "release 6" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Oddball

10:03

New subject: [opensuse] boot without Grub's menu

Op 01-11-12 10:33, Oddball schreef:

...

Op 01-11-12 09:58, Felix Miata schreef:

...
On 2012-11-01 09:12 (GMT+0100) Oddball composed:

...
...
...
...
grub> linux (hd0,msdos3)/vmlinuz root=/dev/sda3 noresume 3 grub> initrd (hd0,msdos3)/initrd grub> boot

...
It booted up to the stage where 'no init' was found.

...
These are the last words:

...
/dev/sda3: clean, 295/38760 files, 46394/154624 blocks fsck succeeded. Monting root device read-write. Mounting root /dev/sda3 mount -o rw,acl,user_xattr -t ext4 /dev/sda3 /root [ 2.866574] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: acl,user_xattr No init found. Try passing init= option to the kernel. umount: /dev/pts: target is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1) umount: /dev: target is busy.

...
I tried it it 3 times, the break shows the first and third attempt.

Instead of

grub> linux (hd0,msdos3)/vmlinuz root=/dev/sda3 noresume 3

try

grub> linux (hd0,msdos3)/vmlinuz noresume 3

It may be that root=/dev/sda3 is overriding a default setting within the initrd that would otherwise work.

That is worth the try.. ;-) (as the download is stil going on)

Another thing: Do you know if .thunderbirds contains all the mail?

That worked, until init 3. startx with root results in moving on, to the same message always:

...

Call to lnuser failed (temporary directories full?). Check your installation.

startx, did not for user. (I set KDM4 before i rebooted, maybe it doesn't exist. (?). Message:oddball@EeePc-Rob-SFN9:~>startx /etc/sysconfig/displaymanager: regel 5: Config:: opdracht niet gevonden (line 5: Config:: command not found) Fatal server error: Cannot move old log file "/var/log/Xorg.0.log" to "/var/log/Xorg.0.log.old" Please consult the The X.Org Foundation support at http://wiki.x.org for help xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error ------------------------------------------------------------------------------------------------------- xinit failed. /usr/bin/Xorg is not setuid, maybe that is the reason? If so either use a display manager (strongly recommended) or adjust /etc/permissions.local oddball@EeePc-Rob-SFN9:~>_ -- Enjoy your time around, Oddball (M9.) (Now or never...) OS: Linux 2.6.37.1-1.2-desktop x86_64 Huidige gebruiker: oddball@AMD64x2sfn1 Systeem: openSUSE 11.4 (x86_64) KDE: 4.6.00 (4.6.0) "release 6" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Oddball

10:23

New subject: [opensuse] boot without Grub's menu

Op 01-11-12 11:03, Oddball schreef:

...

That worked, until init 3.

startx with root results in moving on, to the same message always:

...
Call to lnuser failed (temporary directories full?). Check your installation.

startx, did not for user. (I set KDM4 before i rebooted, maybe it doesn't exist. (?).

Message:oddball@EeePc-Rob-SFN9:~>startx /etc/sysconfig/displaymanager: regel 5: Config:: opdracht niet gevonden (line 5: Config:: command not found)

Fatal server error: Cannot move old log file "/var/log/Xorg.0.log" to "/var/log/Xorg.0.log.old"

Please consult the The X.Org Foundation support at http://wiki.x.org for help

xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error -------------------------------------------------------------------------------------------------------

xinit failed. /usr/bin/Xorg is not setuid, maybe that is the reason? If so either use a display manager (strongly recommended) or adjust /etc/permissions.local oddball@EeePc-Rob-SFN9:~>_

the other ttys work,np, but login in as root to tty2 resulted in: Welcome to openSUSE 12.2 "Mantis" - Kernel 3.7.0-rc2-4-desktopp (tty2). EeePc-Rob-SFN9 login: root Password: Last login: Thu Nov 1 11:59:27 on tty1 Have a lot of fun... (this wish is not sincere, as there is no fun at all if root gets all permissions denied!!!) EeePc-Rob-SFN9:~# /etc/sysconfig/displaymanager -bash: /etc/sysconfig/displaymanager: Permission denied EeePc-Rob-SFN9:~# /etc/permissions.local -bash: /etc/permissions.local: Permission denied EeePc-Rob-SFN9:~# _ (blinking underscore: blinkblink!) So it seems there is another boss in openSUSE 12.2. root is no longer in charge.... Pity, bureaucracy has taken over here also... done with the freedom... -- Enjoy your time around, Oddball (M9.) (Now or never...) OS: Linux 2.6.37.1-1.2-desktop x86_64 Huidige gebruiker: oddball@AMD64x2sfn1 Systeem: openSUSE 11.4 (x86_64) KDE: 4.6.00 (4.6.0) "release 6" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

11:06

New subject: [opensuse] boot without Grub's menu

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-11-01 11:23, Oddball wrote:

...

the other ttys work,np, but login in as root to tty2 resulted in:

Welcome to openSUSE 12.2 "Mantis" - Kernel 3.7.0-rc2-4-desktopp (tty2).

EeePc-Rob-SFN9 login: root Password: Last login: Thu Nov 1 11:59:27 on tty1 Have a lot of fun... (this wish is not sincere, as there is no fun at all if root gets all permissions denied!!!) EeePc-Rob-SFN9:~# /etc/sysconfig/displaymanager -bash: /etc/sysconfig/displaymanager: Permission denied EeePc-Rob-SFN9:~# /etc/permissions.local -bash: /etc/permissions.local: Permission denied EeePc-Rob-SFN9:~# _ (blinking underscore: blinkblink!)

What did you expect? Those are not commands you can run, they are data files. Thus you get permission denied. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iF4EAREIAAYFAlCSV7oACgkQja8UbcUWM1xEdgD+JrzWtIczxhnRV41BaKoPHPp6 ng9cFGILYJzW91+E1DcA/00On5lBBeSBNruDLcRn8anDcr5mCLbd7Zpy1ENtNLnd =KSHQ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Oddball

11:13

New subject: [opensuse] boot without Grub's menu

Op 01-11-12 12:06, Carlos E. R. schreef:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

On 2012-11-01 11:23, Oddball wrote:

...
the other ttys work,np, but login in as root to tty2 resulted in:

Welcome to openSUSE 12.2 "Mantis" - Kernel 3.7.0-rc2-4-desktopp (tty2).

EeePc-Rob-SFN9 login: root Password: Last login: Thu Nov 1 11:59:27 on tty1 Have a lot of fun... (this wish is not sincere, as there is no fun at all if root gets all permissions denied!!!) EeePc-Rob-SFN9:~# /etc/sysconfig/displaymanager -bash: /etc/sysconfig/displaymanager: Permission denied EeePc-Rob-SFN9:~# /etc/permissions.local -bash: /etc/permissions.local: Permission denied EeePc-Rob-SFN9:~# _ (blinking underscore: blinkblink!) What did you expect? Those are not commands you can run, they are data files. Thus you get permission denied.

Ah, to open them i will need an editor like vi. Problem is, i have no idea how to use it, i have tried many times to edit files with it, but i don't understand how it works.

...

- -- Cheers / Saludos,

Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iF4EAREIAAYFAlCSV7oACgkQja8UbcUWM1xEdgD+JrzWtIczxhnRV41BaKoPHPp6 ng9cFGILYJzW91+E1DcA/00On5lBBeSBNruDLcRn8anDcr5mCLbd7Zpy1ENtNLnd =KSHQ -----END PGP SIGNATURE-----

Carlos E. R.

11:13

New subject: [opensuse] boot without Grub's menu

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-11-01 12:13, Oddball wrote:

...

Ah, to open them i will need an editor like vi. Problem is, i have no idea how to use it, i have tried many times to edit files with it, but i don't understand how it works.

So, use joe. Or mcedit. Or pico. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iF4EAREIAAYFAlCSWWkACgkQja8UbcUWM1wt2wD/byMhFHgFtLlMci/whnzf5wvI W0mSW4aOD0gOnXA1V0IA/iYnbMlFVDUbRMyB1e6qO8TA4BB7pOZmmsFI3u0BmrOm =pJob -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Oddball

12:01

New subject: [opensuse] boot without Grub's menu

Op 01-11-12 12:13, Carlos E. R. schreef:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

On 2012-11-01 12:13, Oddball wrote:

...
Ah, to open them i will need an editor like vi. Problem is, i have no idea how to use it, i have tried many times to edit files with it, but i don't understand how it works. So, use joe. Or mcedit. Or pico.

It would be better this suggestion came from bash. What if an internet connection failed, or the only pc one had was the one that malfunctioned? instead of Acces/permission denied, bash should say: no run command, use a file editor: Vi,Joe, Pico, mcedit.

...

- -- Cheers / Saludos,

Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iF4EAREIAAYFAlCSWWkACgkQja8UbcUWM1wt2wD/byMhFHgFtLlMci/whnzf5wvI W0mSW4aOD0gOnXA1V0IA/iYnbMlFVDUbRMyB1e6qO8TA4BB7pOZmmsFI3u0BmrOm =pJob -----END PGP SIGNATURE-----

Carlos E. R.

12:13

New subject: [opensuse] boot without Grub's menu

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-11-01 13:01, Oddball wrote:

...

Op 01-11-12 12:13, Carlos E. R. schreef: On 2012-11-01 12:13, Oddball wrote:

...
...
...
Ah, to open them i will need an editor like vi. Problem is, i have no idea how to use it, i have tried many times to edit files with it, but i don't understand how it works. So, use joe. Or mcedit. Or pico.

...
It would be better this suggestion came from bash. What if an internet connection failed, or the only pc one had was the one that malfunctioned?

...
instead of Acces/permission denied, bash should say: no run command, use a file editor: Vi,Joe, Pico, mcedit.

ROTFL! - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iF4EAREIAAYFAlCSZ4YACgkQja8UbcUWM1xE9QD/Vf6siOQW4gErRYB/J/Mf3lvF e0xPMGKVsZ62TjIff2gA/jWUPisgrfaiGtAyddDe1SC0uZgeB2OEZN2FbKZr/Fnv =zVWG -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Rajko

7 Nov 7 Nov

15:42

New subject: [opensuse] boot without Grub's menu

On Thu, 01 Nov 2012 13:01:42 +0100 Oddball wrote:

...

instead of Acces/permission denied, bash should say: no run command, use a file editor: Vi,Joe, Pico, mcedit.

What when one wants to run a picture, or database file, or device driver. Poor bash would have to know all that one computer knows :) Not that is not possible, but that is not purpose of bash. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Oddball

15:57

New subject: [opensuse] boot without Grub's menu

Op 07-11-12 16:42, Rajko schreef:

...

On Thu, 01 Nov 2012 13:01:42 +0100 Oddball wrote:

...
instead of Acces/permission denied, bash should say: no run command, use a file editor: Vi,Joe, Pico, mcedit. What when one wants to run a picture, or database file, or device driver. Poor bash would have to know all that one computer knows :)

Not that is not possible, but that is not purpose of bash.

No, you are right, but i just did not realize at the time, my bad.. :-( (but it would be very nice AI....:-D, wouldn't you agree? -- Have a nice day, Oddball. OS: Linux 3.7.0-rc3-2-desktop i686 Huidige gebruiker: oddball@EeePc-Rob-SFN9 Systeem: openSUSE 12.2 (i586) KDE: 4.9.2 "release 511" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Hans Witvliet

1 Nov 1 Nov

08:34

New subject: [opensuse] Unnecessary Packages in Yast: Can they be removed without consequence?

On Wed, 2012-10-31 at 23:53 +0100, Oddball wrote:

...

The other thing is a mistake i made: i never use lvm. This time i thought ok, lets try it. Lvm is not supported yet in Knoppix, so the partitions could not get mounted, only windows and /boot were visible.

Instead of kroppix, you can use either the KDE-live-cd, or the install-12.2-DVD and choose "live-KDE". LVM and soft raid are recognized there... And do the repair work hence on. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Oddball

08:53

New subject: [opensuse] Unnecessary Packages in Yast: Can they be removed without consequence?

Op 01-11-12 09:34, Hans Witvliet schreef:

...

On Wed, 2012-10-31 at 23:53 +0100, Oddball wrote:

...
The other thing is a mistake i made: i never use lvm. This time i thought ok, lets try it. Lvm is not supported yet in Knoppix, so the partitions could not get mounted, only windows and /boot were visible.

Instead of kroppix, you can use either the KDE-live-cd, or the install-12.2-DVD and choose "live-KDE". LVM and soft raid are recognized there... And do the repair work hence on.

That is an opportunity, but it is the question if it would boot at all. Install the bootloader and mkinitrd might be done if the system is mounted... I think new install will be better. Maybe keep /home, and lvm for now, or use kde to transfer /home to an external hdd, and get rid of lvm. -- Enjoy your time around, Oddball (M9.) (Now or never...) OS: Linux 2.6.37.1-1.2-desktop x86_64 Huidige gebruiker: oddball@AMD64x2sfn1 Systeem: openSUSE 11.4 (x86_64) KDE: 4.6.00 (4.6.0) "release 6" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Oddball

11:10

New subject: [opensuse] Support and repairtools: A laughing stock! (was:Unnecessary Packages in Yast: Can they be removed without consequence?)

Op 01-11-12 09:53, Oddball schreef:

...

Op 01-11-12 09:34, Hans Witvliet schreef:

...
On Wed, 2012-10-31 at 23:53 +0100, Oddball wrote:

...
The other thing is a mistake i made: i never use lvm. This time i thought ok, lets try it. Lvm is not supported yet in Knoppix, so the partitions could not get mounted, only windows and /boot were visible.

Instead of kroppix, you can use either the KDE-live-cd, or the install-12.2-DVD and choose "live-KDE". LVM and soft raid are recognized there... And do the repair work hence on.

That is an opportunity, but it is the question if it would boot at all. Install the bootloader and mkinitrd might be done if the system is mounted... I think new install will be better. Maybe keep /home, and lvm for now, or use kde to transfer /home to an external hdd, and get rid of lvm.

Nope, lvm is not recognised there... And this was the first and last time i was ever gonna use it. So backing up my files is not an option. I think some serious rethinking should be done about what is the aim on opensuse? Create an os that is useless always broken but looks sometimes shiny? Or a system that uses only tools that work, and that are supported? A repair kit that is usable?, or just something that looks like it, but it is not even good enough to wipe your ass with? (difficult with a laptop or pc i agree.. :-D) I think, if opensuse continous, to go on, on this road, the userbase will shrink further. What is the use of an update tool, if the system is broken? First :1) repair the system, 2) support it, and 3) create a working repairkit, so people who test, do not have use their valuable time on re-installing their system. This is the formula for openSUSE 123. -- Enjoy your time around, Oddball (M9.) (Now or never...) OS: Linux 2.6.37.1-1.2-desktop x86_64 Huidige gebruiker: oddball@AMD64x2sfn1 Systeem: openSUSE 11.4 (x86_64) KDE: 4.6.00 (4.6.0) "release 6" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Patrick Shanahan

15:40

New subject: [opensuse-factory] Re: [opensuse] Support and repairtools: A laughing stock! (was:Unnecessary Packages in Yast: Can they be removed without consequence?)

* Oddball [11-01-12 07:13]:

...

I think some serious rethinking should be done about what is the aim on opensuse?

Create an os that is useless always broken but looks sometimes shiny? Or a system that uses only tools that work, and that are supported? A repair kit that is usable?, or just something that looks like it, but it is not even good enough to wipe your ass with? (difficult with a laptop or pc i agree.. :-D)

I think, if opensuse continous, to go on, on this road, the userbase will shrink further.

What is the use of an update tool, if the system is broken?

While you are certainly allowed to speak your feelings, those utterances are the result of frustration of your own making. Continuing in this manner will definitely, and has already, alienate those inclined to lend you assistance which so far you either dismiss or only half perform. Wipe your disk(s) after backingup your <home>. Make a *new* install w/o selecting *kde3* apps. Boot into your new system with a *new* user and attempt to do *controlled* and *reversable* changes to achieve your needs. Then and only then import your saved <home> a portion at a time checking that something does not change your system adversely. Return and *sanely* request assistance w/o the rants and derogatory. Perhaps you will get help and perhaps not. *You* are *your* own worst enemy. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Oddball

16:16

New subject: [opensuse-factory] Re: [opensuse] Support and repairtools: A laughing stock!

Op 01-11-12 16:40, Patrick Shanahan schreef:

...

* Oddball [11-01-12 07:13]:

...
I think some serious rethinking should be done about what is the aim on opensuse?

Create an os that is useless always broken but looks sometimes shiny? Or a system that uses only tools that work, and that are supported? A repair kit that is usable?, or just something that looks like it, but it is not even good enough to wipe your ass with? (difficult with a laptop or pc i agree.. :-D) This last sentence i take back, it is rude and irrelevant. (the joke is not even funny..)

...

...
I think, if opensuse continous, to go on, on this road, the userbase will shrink further.

What is the use of an update tool, if the system is broken?

I understand the attention needed for this app, but there are things broken that need more attention. But as i can only test, and find things that do not work the way they should, and show them, by using the system, my input is limited, so i will shut my head for now.

...

While you are certainly allowed to speak your feelings, those utterances are the result of frustration of your own making. Continuing in this manner will definitely, and has already, alienate those inclined to lend you assistance which so far you either dismiss or only half perform.

Wipe your disk(s) after backingup your <home>. Make a *new* install w/o selecting *kde3* apps. Boot into your new system with a *new* user and attempt to do *controlled* and *reversable* changes to achieve your needs. Then and only then import your saved <home> a portion at a time checking that something does not change your system adversely.

Return and *sanely* request assistance w/o the rants and derogatory. Perhaps you will get help and perhaps not.

*You* are *your* own worst enemy.

Yes, i admit you are totally right here. Sometimes one gets frustrated, and blows of steam, after days of fruitless tries to achieve some simple looking things, and end up with nothing at all. At the deepest point, one is glad there is some assistance, and grateful to have learned so many things in a very short time. I am no exception on that.. My apologizes for words that were not chosen carefully, and not even meant that strong, however there is truth in them, but i am only human. I also have put a lot of energy in showing what a regular user experiences, and i rather say it in someones face, than behind his back. And it is true that the tools have been better, and that it is a lot of work without proper tools, always. Also, without proper tools, people need more help. I admit, my choice of words was sometimes very bad, and for that i want to apologize once more, And for the help i have had, i am very grateful, and i want to thank for that also once more. Kind regards, -- Have a nice day, Oddball. OS: Linux 3.7.0-rc2-4-desktop i686 Huidige gebruiker: oddball@EeePc-Rob-SFN9 Systeem: openSUSE 12.2 (i586) KDE: 4.9.2 "release 511" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Felix Miata

16:21

New subject: [opensuse] Support and repairtools: A laughing stock!

On 2012-11-01 11:40 (GMT-0400) Patrick Shanahan composed:

...

While you are certainly allowed to speak your feelings, those utterances are the result of frustration of your own making. Continuing in this manner will definitely, and has already, alienate those inclined to lend you assistance which so far you either dismiss or only half perform.

...

Wipe your disk(s) after backingup your <home>. Make a *new* install w/o selecting *kde3* apps. Boot into your new system with a *new* user and attempt to do *controlled* and *reversable* changes to achieve your needs. Then and only then import your saved <home> a portion at a time checking that something does not change your system adversely.

...

Return and *sanely* request assistance w/o the rants and derogatory. Perhaps you will get help and perhaps not.

...

*You* are *your* own worst enemy.

Oddball, this is all good advice. The ranting definitely needs to stop. It does nothing to get you where you want to go. It does make people ignore you, and worse. If you want to continue trying to fix your system as a learning experience, that's fine, but don't expect people to keep hand-holding with detailed steps what you should do next. As to runlevel 3 root login issue, revisit: http://lists.opensuse.org/opensuse-factory/2012-10/msg00352.html For root login in KDM issue, you've been given instructions about kdmrc and displaymanager enough times that if you can't follow through on it all, installing fresh is your best next step. One more thing to try is to see if some other display manager than KDM is being used to cause your changes to kdmrc to be ignored. Make sure gdm, kdebase3-kdm, lightdm and lxdm are not installed, and that /etc/sysconfig/displaymanager contains 'DISPLAYMANAGER="kdm"'. -- "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

Oddball

19:45

New subject: [opensuse] Support and repairtools: A laughing stock!

Op 01-11-12 17:21, Felix Miata schreef:

...

On 2012-11-01 11:40 (GMT-0400) Patrick Shanahan composed:

...
While you are certainly allowed to speak your feelings, those utterances are the result of frustration of your own making. Continuing in this manner will definitely, and has already, alienate those inclined to lend you assistance which so far you either dismiss or only half perform.

...
Wipe your disk(s) after backingup your <home>. Make a *new* install w/o selecting *kde3* apps. Boot into your new system with a *new* user and attempt to do *controlled* and *reversable* changes to achieve your needs. Then and only then import your saved <home> a portion at a time checking that something does not change your system adversely.

...
Return and *sanely* request assistance w/o the rants and derogatory. Perhaps you will get help and perhaps not.

...
*You* are *your* own worst enemy.

Oddball, this is all good advice. The ranting definitely needs to stop. It does nothing to get you where you want to go. It does make people ignore you, and worse.

Yes i know, i lost control. I am sorry.

...

If you want to continue trying to fix your system as a learning experience, that's fine, but don't expect people to keep hand-holding with detailed steps what you should do next.

I am not used to accept/call for help vey often, and i do not want that i feel like an infant that knows nothing. Because there are things i think i know. The 'bugs' kinda overwhelmed me, and your suggestions added up to this stage. However it was most teachable. And i am glad it really worked.

...

As to runlevel 3 root login issue, revisit: http://lists.opensuse.org/opensuse-factory/2012-10/msg00352.html

For root login in KDM issue, you've been given instructions about kdmrc and displaymanager enough times that if you can't follow through on it all, installing fresh is your best next step.

Yes, the upstream theme replaced the openSUSE one, and it is an improvement. I can live with how it looks now. What i want is not possible atm, because the path is somehow really broken.

...

One more thing to try is to see if some other display manager than KDM is being used to cause your changes to kdmrc to be ignored. Make sure gdm, kdebase3-kdm, lightdm and lxdm are not installed, and that /etc/sysconfig/displaymanager contains 'DISPLAYMANAGER="kdm"'.

No others are installed. kdm is displaymanager. I have met nobody that actually could change the standard to an other one. I take a few hours rest, to become fresh again. Thanks for your help, it is really appreciated. ;-) -- Have a nice day, Oddball. OS: Linux 3.7.0-rc2-4-desktop i686 Huidige gebruiker: oddball@EeePc-Rob-SFN9 Systeem: openSUSE 12.2 (i586) KDE: 4.9.2 "release 511" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Hans Witvliet

21:16

New subject: [opensuse] Unnecessary Packages in Yast: Can they be removed without consequence?

On Thu, 2012-11-01 at 09:53 +0100, Oddball wrote:

...

Op 01-11-12 09:34, Hans Witvliet schreef:

...
On Wed, 2012-10-31 at 23:53 +0100, Oddball wrote:

...
The other thing is a mistake i made: i never use lvm. This time i thought ok, lets try it. Lvm is not supported yet in Knoppix, so the partitions could not get mounted, only windows and /boot were visible.

Instead of kroppix, you can use either the KDE-live-cd, or the install-12.2-DVD and choose "live-KDE". LVM and soft raid are recognized there... And do the repair work hence on.

That is an opportunity, but it is the question if it would boot at all. Install the bootloader and mkinitrd might be done if the system is mounted... I think new install will be better. Maybe keep /home, and lvm for now, or use kde to transfer /home to an external hdd, and get rid of lvm.

Re-install is something you can always do. But i meant: boot from SuSE live-media, do a mount the original /root and /boot, do a chroot and re-install grub. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Oddball

2 Nov 2 Nov

09:47

New subject: [opensuse] Unnecessary Packages in Yast: Can they be removed without consequence?

Op 01-11-12 22:16, Hans Witvliet schreef:

...

On Thu, 2012-11-01 at 09:53 +0100, Oddball wrote:

...
Op 01-11-12 09:34, Hans Witvliet schreef:

...
On Wed, 2012-10-31 at 23:53 +0100, Oddball wrote:

...
The other thing is a mistake i made: i never use lvm. This time i thought ok, lets try it. Lvm is not supported yet in Knoppix, so the partitions could not get mounted, only windows and /boot were visible.

Instead of kroppix, you can use either the KDE-live-cd, or the install-12.2-DVD and choose "live-KDE". LVM and soft raid are recognized there... And do the repair work hence on. That is an opportunity, but it is the question if it would boot at all. Install the bootloader and mkinitrd might be done if the system is mounted... I think new install will be better. Maybe keep /home, and lvm for now, or use kde to transfer /home to an external hdd, and get rid of lvm.

Re-install is something you can always do. But i meant: boot from SuSE live-media, do a mount the original /root and /boot, do a chroot and re-install grub. That would be possible, if / or /home would be recognized, but it was not. Only /boot was, and of course windows like: fat32 and ntfs. Felix helped me with the remnants of grub2, so i was able to boot into int 5. Than i used yast to install a new grub legacy. Yast was not used to see /boot having an ext4fs, (proposal of lvm) because that is always ext2, and assumed ext2. So now the loader does not work how it has to. I can boot, but not clean.

I try to find out where the information of the 'assumed' information is stored, so i can change it. But still the 'charm' of lvm, hangs as a dark veil over the install, and there are more things not right. If i just install new, i can avoid some issues to turn up, and, if a rescue is needed, it can be performed more easily when the partitions are recognized, i think. -- Have a nice day, Oddball. OS: Linux 3.7.0-rc2-4-desktop i686 Huidige gebruiker: oddball@EeePc-Rob-SFN9 Systeem: openSUSE 12.2 (i586) KDE: 4.9.2 "release 511" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

JtWdyP

12:58

New subject: [opensuse] Re: Unnecessary Packages in Yast: Can they be removed without consequence?

It would appear that on Nov 2, Oddball did say:

...

Op 01-11-12 22:16, Hans Witvliet schreef:

...
Re-install is something you can always do. But i meant: boot from SuSE live-media, do a mount the original /root and /boot, do a chroot and re-install grub. That would be possible, if / or /home would be recognized, but it was not. Only /boot was, and of course windows like: fat32 and ntfs. Felix helped me with the remnants of grub2, so i was able to boot into int 5. Than i used yast to install a new grub legacy. Yast was not used to see /boot having an ext4fs, (proposal of lvm) because that is always ext2, and assumed ext2. So now the loader does not work how it has to. I can boot, but not clean.

I'm not sure if memory serves me well. But If I remember an old discussion I once had with on an *buntu mailing list with a grub2 proponent, one of the disadvantages of grub legacy was that it couldn't use an ext4 boot partition... My solution was not to use ext4. Since then I heard something about an patch for grub legacy that added an ext4 stage1.5 to it. So hopefully, since you just installed a "new" grub legacy, you now have an ext4 capable version??? But if your stuck with the unpatched version you might want to checkout http://tinylink.in/YQL and think about recreating your grub partition as ext2 or ext3. If your using live-media, you should be able to back up the /boot partition files to your /root partition, recreate /boot with mkfs, restore the files to new ext2 or ext3 fs... -- JtWdyP -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Oddball

13:09

New subject: [opensuse] Re: Unnecessary Packages in Yast: Can they be removed without consequence?

Op 02-11-12 13:58, JtWdyP schreef:

...

It would appear that on Nov 2, Oddball did say:

...
Op 01-11-12 22:16, Hans Witvliet schreef:

...
Re-install is something you can always do. But i meant: boot from SuSE live-media, do a mount the original /root and /boot, do a chroot and re-install grub. That would be possible, if / or /home would be recognized, but it was not. Only /boot was, and of course windows like: fat32 and ntfs. Felix helped me with the remnants of grub2, so i was able to boot into int 5. Than i used yast to install a new grub legacy. Yast was not used to see /boot having an ext4fs, (proposal of lvm) because that is always ext2, and assumed ext2. So now the loader does not work how it has to. I can boot, but not clean. I'm not sure if memory serves me well. But If I remember an old discussion I once had with on an *buntu mailing list with a grub2 proponent, one of the disadvantages of grub legacy was that it couldn't use an ext4 boot partition...

My solution was not to use ext4.

Since then I heard something about an patch for grub legacy that added an ext4 stage1.5 to it.

So hopefully, since you just installed a "new" grub legacy, you now have an ext4 capable version???

But if your stuck with the unpatched version you might want to checkout

http://tinylink.in/YQL

and think about recreating your grub partition as ext2 or ext3. If your using live-media, you should be able to back up the /boot partition files to your /root partition, recreate /boot with mkfs, restore the files to new ext2 or ext3 fs...

This is good advice, because i did not know. I was always used to use ext2 for my /boot partitions. I will check around. The problem is that live media can not see my / and /home partitions, because they were created by lvm. But i can get into my system, just not as 'smooth' as always. Thanx for your input. ;-) -- Have a nice day, Oddball. OS: Linux 3.7.0-rc2-4-desktop i686 Huidige gebruiker: oddball@EeePc-Rob-SFN9 Systeem: openSUSE 12.2 (i586) KDE: 4.9.2 "release 511" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

13:24

New subject: [opensuse] Re: Unnecessary Packages in Yast: Can they be removed without consequence?

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-11-02 13:58, JtWdyP wrote:

...

I'm not sure if memory serves me well. But If I remember an old discussion I once had with on an *buntu mailing list with a grub2 proponent, one of the disadvantages of grub legacy was that it couldn't use an ext4 boot partition...

AFAIK, openSUSE's grub legacy does not have that limitation. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iF4EAREIAAYFAlCTyZAACgkQja8UbcUWM1xEwQD+I7bRZz+PKW151bJJ2skcUwAz VV+6z56+Nk0WdIMUNUoA/1n53KgnbIPn61gZPKZa91fiRPN/hP/4zCcuIHR0dvVa =gtJJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Oddball

13:57

New subject: [opensuse] Re: Unnecessary Packages in Yast: Can they be removed without consequence?

Op 02-11-12 14:24, Carlos E. R. schreef:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

On 2012-11-02 13:58, JtWdyP wrote:

...
I'm not sure if memory serves me well. But If I remember an old discussion I once had with on an *buntu mailing list with a grub2 proponent, one of the disadvantages of grub legacy was that it couldn't use an ext4 boot partition... AFAIK, openSUSE's grub legacy does not have that limitation. Then how do you explain this:

...

root (hd0,2) Filesystem type is ext2fs. (but this is not true, as lvm proposed ext4 for that, and i choose to give it a try.) partition type 0x83 (?)

It expects ext2, and fails to see it is ext4. Now the system does not boot with this config. What i want to know where the file is that contains this info, and change it to the correct readings. a hack, i know, and an ugly one too, but if my eee-pc boots with it, who cares?

...

- -- Cheers / Saludos,

Carlos E. R.

-- Have a nice day, Oddball. OS: Linux 3.7.0-rc2-4-desktop i686 Huidige gebruiker: oddball@EeePc-Rob-SFN9 Systeem: openSUSE 12.2 (i586) KDE: 4.9.2 "release 511" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R.

15:03

New subject: [opensuse] Re: Unnecessary Packages in Yast: Can they be removed without consequence?

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-11-02 14:57, Oddball wrote:

...

Op 02-11-12 14:24, Carlos E. R. schreef:

...

...
AFAIK, openSUSE's grub legacy does not have that limitation. Then how do you explain this:

...
root (hd0,2) Filesystem type is ext2fs. (but this is not true, as lvm proposed ext4 for that, and i choose to give it a try.) partition type 0x83 (?)

LVM? I'm not sure grub can handle that, you need a separate /boot. And anyway, I think that detection doesn't matter.

...

It expects ext2, and fails to see it is ext4. Now the system does not boot with this config. What i want to know where the file is that contains this info, and change it to the correct readings.

I don't think you can do that. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iF0EAREIAAYFAlCT4L4ACgkQja8UbcUWM1zgUAD4haRlmxtRrUOgzVEy6sVOUQ1C 8w83U3C1S83wDVyZsQD+Pbgjwn2MEn3Ab0CsZSxZ5Tw1HaXaRKwZnyuLp2HzRR4= =0mrZ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Oddball

16:30

New subject: [opensuse] Re: Unnecessary Packages in Yast: Can they be removed without consequence?

Op 02-11-12 16:03, Carlos E. R. schreef:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256

On 2012-11-02 14:57, Oddball wrote:

...
Op 02-11-12 14:24, Carlos E. R. schreef:

...
AFAIK, openSUSE's grub legacy does not have that limitation. Then how do you explain this:

...
root (hd0,2) Filesystem type is ext2fs. (but this is not true, as lvm proposed ext4 for that, and i choose to give it a try.) partition type 0x83 (?) LVM? I'm not sure grub can handle that, you need a separate /boot. And anyway, I think that detection doesn't matter. I have a separate /boot, but it is ext4, due to me trusting the proposal by lvm. (worst decision i took lately.) No it does not detect, it assumes.

...

...
It expects ext2, and fails to see it is ext4. Now the system does not boot with this config. What i want to know where the file is that contains this info, and change it to the correct readings. I don't think you can do that.

Neither do i...... :-D

...

- -- Cheers / Saludos,

Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iF0EAREIAAYFAlCT4L4ACgkQja8UbcUWM1zgUAD4haRlmxtRrUOgzVEy6sVOUQ1C 8w83U3C1S83wDVyZsQD+Pbgjwn2MEn3Ab0CsZSxZ5Tw1HaXaRKwZnyuLp2HzRR4= =0mrZ -----END PGP SIGNATURE-----

4192

Age (days ago)

4199

Last active (days ago)

List overview

Download

34 comments

7 participants

participants (7)

Carlos E. R.
Felix Miata
Hans Witvliet
JtWdyP
Oddball
Patrick Shanahan
Rajko