Forum Home
Press F1
Thread ID: 48802	2004-09-01 10:16:00	Yoper Installation	Murray P (44)	Press F1

Post ID	Timestamp	Content	User
267989	2004-09-04 16:10:00	You should really _never_ need to login to the GUI as root - Its too easy to break things! Always use: su - from the command-line, Or try: kdesu if you want an easy way to run a program that requires use of the GUI.	Chilling_Silence (9)
267990	2004-09-05 04:26:00	Na, not working, cannot write file, no permission. kdesu cannot start X server. Have checked permission in fstab properties and I have read write permissions, will take another step backward in order to go forward, ie, read an article on permissions. BTW, I thought the logon as root was generally a no no, just general ramblings of a desperate person. Off to see Mr P senior now. Thought I might gift him a used CDr disc for fathers day, knowing the old codger, he'll have permissions sorted out well before me. Cheers Murray P	Murray P (44)
267991	2004-09-05 05:52:00	Hi again Murray :) >will take another step backward in order to go forward The pre-determined permissions on fstab should be fine for only allowing root to edit this file and you don't need to modify these at all. There are two easy ways of editing root permission files: 1. Use File Manager - Super User Mode (found under the KMenu > System > More Applications > File Manager - Super User Mode. Selecting this will give you a prompt for root's password. The title bar of the File Manger will say "root - Konqueror". Anywhere you go using this window, you will have full root powers. You should be able to use the Up arrow to navigate to /, and then head for /etc/fstab. Selecting fstab will open up Kwrite and you can edit and save your changes. 2. Hit the command line text editor. Open up a konsole shell and "su -" to root. Then enter in: nano -w /etc/fstab Use the keyboard arrows to move around and make your changes. When you are finished, use CTRL-O (letter O) to write the changes. You wll see a prompt that says "File Name to Write: /etc/fstab", so just hit Enter. To exit nano, use CTRL-X. > Na, not working, cannot write file, no permission. If you are already doing this as root, then you should have full permission. >BTW, I thought the logon as root was generally a no no As Chill mentions, you don't need to launch the full desktop as root, but just use "su -" or the Super User Mode file manager to perform root tasks. I have only logged into the full desktop twice as root since installing Core 2 in May, and that was purely to see if a bug in editing the KMenu occurred as root as well. Did you sort out LILO to get your machine to triple boot Win2K, Yoper and Mepis?	Jen C (20)
267992	2004-09-05 06:32:00	Well, Yoper seems pretty good to me, but it will have to wait untill I re-arrange my HDA a bit . Currently, it appears to think that hda1 and 2 are a bit dodgy - since that is (part of) the Windows residence, I don't much care . Sooner or later I must look and decide if I can be bothered playing with XP any more, but at present it can just fester in there . (with SP2 to help it doze) I too would be interested to learn of a triple boot with two flavours of Linux without disk swapping . >> . . . purely to see if a bug in editing the KMenu occurred as root as well . And did it Jen C ? Is this the "now you see it, now you don't" bug ? I had this last night with Mandrake 10, and assumed from prior experience that it was me, not a bug . The Menu Editor appears to have caused the Kmenu to vanish . If that's not the bug, I must see what stupid act I have pulled this time .	R2x1 (4628)
267993	2004-09-05 06:56:00	> I too would be interested to learn of a triple boot > with two flavours of Linux without disk swapping . Read the instructions I gave for Murray above for copying over the initrd and vmlinuz to whichever Linux OS controls the bootloader . Basically to set it up, you install your first Linux OS alongside your Windows OS and let it write a bootloader to the MBR to dual boot doze and Linux . You then install your second Linux OS, this time making sure you select no bootloader to be installed at all . Once that is installed, boot to your first Linux OS and mount the second Linux OS root's partition . Copying over the 2nd Linux OS's kernel files to the first Linux OS's /boot and then editing either Grub or Lilo to add the new OS's . I currently have Yoper and SuSE 9 . 1 dual booting with Yoper controlling LILO . > > > . . . purely to see if a bug in editing the KMenu occurred as root as well . > > And did it Jen C ? Yes, it was a genuine bug . Basically if I loaded Gnome, and then went back to KDE I could no longer edit the KMenu - you could go through the motions but it just ignored the new entry and wouldn't display it . It was a bug with Gnome not being nice to KDE and this affected the ~/ . config file . A work around was to delete the ~/ . config and let KDE create a new one after each visit to Gnome . I don't use Gnome at all anymore on Fedora .	Jen C (20)
267994	2004-09-05 10:56:00	Well I'm got there in the end, thanks Jen & Chill :) I still don't know what was happening with permissions in kdesu or whatever other variation I was using but it worked opening a super user terminal and nano w- /etc/fstab or I should say it worked once I figured out that I no mount points then I wrongly named a mount point which further threw a spanner because I assumed the others had the same issue but did not know what it was, and then sorted out that mounting Linux partitions (users,exec 0 0) and browsing them and putting a ",' between stuff without white space also made a huge difference and was definintely different to windows (users,exec,umask=000, 0 0) but I can access all ten partions now so, I'm a happy chappy :D > Did you sort out LILO to get your machine to triple boot Win2K, Yoper and > Mepis? Not tonight, pleeeease pleeeeease, don't make me do it tonight :_| It's all there though, Mepis that is, and being able to browse it and my Mepis home partition is very reassuring, thanks for the sep home partition advice Chill, I can now go and get my bookmarks with my Linux How To's Cheers Murray P	Murray P (44)
267995	2004-09-05 11:03:00	Oh! and BTW R2, I'm obviously not the person to take advice re Linux from but, from the disto's I have managed to get going, MDK 9.1 (sort of), Mepis and Yoper, Yoper has a heck of a lot going for it. There is very little extraneous app's as per most distro's and it seems to be at least on a par with Mepis for speed if not quicker with browsers and files appearing to be faster to open although, I haven't played with any of the more resource hungry apps yet. Cheers Murray P	Murray P (44)
267996	2004-09-05 11:55:00	I _love_ the KDE-OOo look, Its great :-) I agree - There's not an overload of apps, but enough to get all the _real_ work done! There's a heap of extras you can get from Synaptic, including a GNOME or Xfce4 Desktop :-) Chill.	Chilling_Silence (9)
267997	2004-09-10 11:46:00	Ok, would you kind people have a look at the following /lilo/conf file and let me know if I'm going to toast my MBR with this . The mepis boot is from a sample of the mepis /lilo/conf not the real thing which has shut me out, I suspect until I can boot it and logon, if there is an alternative source to this info, I'd be most grateful . I also suspect the the append line should read more like append = "splash=silent " as per Jen's above . On the image = line is the /mnt/mepis . . . . . . . . . . . . . . . -modular necessary, given that my MBR is on hdb (it's very own partition, at the mo) not hda where you might expect, I got the impression from reading a how to that I should mnt the mepis partition although this could now be redundant in this ver of Lilo? No honest, I'm not drowning, how could you think such a thing :O I just stepped into a tiny wee hole, the tides coming in, the rips going out and I just don't want to get a hole in my Lilo because I might need it soon . That's all, honest :| prompt timeout=60 default=YOS vga=791 boot=/dev/hdb lba32 bitmap = /boot/yoper_boot . bmp bmp-colors = 1,,0,2,,0 bmp-table = 120p,173p,1,15,17 bmp-timer = 254p,432p,1,0,0 image=/boot/yos label=YOS read-only root=/dev/hdd9 append = "splash=silent " initrd=/boot/initrd-2 . 6 . 8 . 1-3 . img other=/dev/hda1 label=Windows image=/mnt/mepis/boot/vmlinuz-2 . 4 . 22-modular vga=794 label=mepis append="nomce hdc=ide-scsi hdd=ide-scsi " root=/dev/hdd6 So instead the mepis part of /lilo/conf could look like: image=/boot/mepis vga=794 label=mepis append="splash=silent" root=/dev/hdd6 That ok, do I need the initrd line, hows the white space? I'll tell you what, I'll do the spelling :D Cheers Murray P	Murray P (44)
267998	2004-09-10 12:18:00	> The mepis boot is from a sample of the mepis > /lilo/conf not the real thing which has shut me out, > I suspect until I can boot it and logon, if there is > an alternative source to this info, I'd be most > grateful . I thought you were able to mount and browse your Mepis paritions? You should be able to go and view /etc/lilo or /etc/grub whatever one Mepis uses . > I also suspect the the append line should read more > like append = "splash=silent " as per Jen's above . On > the image = line is the > /mnt/mepis . . . . . . . . . . . . . . . -modular necessary, given > that my MBR is on hdb (it's very own partition, at > the mo) not hda where you might expect, I got the > impression from reading a how to that I should mnt > the mepis partition although this could now be > redundant in this ver of Lilo? /etc/lilo . conf ---------------------------------------------------------------------------------- > prompt > timeout=60 > default=YOS > vga=791 > boot=/dev/hdb > > lba32 > > bitmap = /boot/yoper_boot . bmp > bmp-colors = 1,,0,2,,0 > bmp-table = 120p,173p,1,15,17 > bmp-timer = 254p,432p,1,0,0 > > image=/boot/yos > label=YOS > read-only > root=/dev/hdd9 > append = "splash=silent " > initrd=/boot/initrd-2 . 6 . 8 . 1-3 . img > > > other=/dev/hda1 > label=Windows > > > image=/mnt/mepis/boot/vmlinuz-2 . 4 . 22-modular > vga=794 > label=mepis > append="nomce hdc=ide-scsi hdd=ide-scsi " > root=/dev/hdd6 image=/boot/vmlinuz-2 . 4 . 22-modular vga=794 label=mepis append="nomce hdc=ide-scsi hdd=ide-scsi " root=/dev/hdd6 you need to copy Mepis's kernel (and initrd if it uses one) into to Yopers /boot directory . You had it pointing to the Mepis /boot partition . > So instead the mepis part of /lilo/conf could look > like: > > image=/boot/mepis > vga=794 > label=mepis > append="splash=silent" > root=/dev/hdd6 If Mepis requires those other append options to boot, I would probably leave them there . > That ok, do I need the initrd line, hows the white > space? I'll tell you what, I'll do the spelling :D Does Mepis have a initrd in its /boot? Not all will have . Here is what my dual booting Yoper / SuSE 9 . 1 lilo . conf looks like: prompt timeout=60 default=YOS-2 . 6 . 8 . 1-6 vga=791 boot=/dev/hda lba32 bitmap = /boot/yoper_boot . bmp bmp-colors = 1,,0,2,,0 bmp-table = 120p,173p,1,15,17 bmp-timer = 254p,432p,1,0,0 image=/boot/yos label=YOS read-only root=/dev/hda2 append = "splash=silent " initrd=/boot/initrd-2 . 6 . 8 . 1-3 . img image=/boot/vmlinuz-2 . 6 . 8 . 1-6 label=YOS-2 . 6 . 8 . 1-6 read-only root=/dev/hda2 append = "splash=silent " initrd=/boot/initrd-2 . 6 . 8 . 1-6 . img image=/boot/vmlinuz-2 . 6 . 4-52-suse label=SuSE_9 . 1 read-only root=/dev/hda6 append = "splash=silent " initrd=/boot/initrd-2 . 6 . 4-52-suse	Jen C (20)
1 2 3 4