PClinuxOS-8 Install

[Dard]

I'm just about to give pclos-8 a try, that is if it will boot and run the livecd on my box. I have it burned to cd, just havent rebooted this system since the burn so I really don't know if it will work or not. :oI do believe that I have most of the information that I need to get this done, one area of interest is the large amount of updates.With so many updates to be had all at once, I'm thinking that these should be done at the command line and a reboot after they have been installed. ( Have broadband will download. )Is there a nice link that explains the commands and what they do?I think it's the apt-get application that I would need to use for this instead of synaptic because I don't think that having kde open while updating it's base libs and stuff works.If memory serves me correctly, when formatting a partition the partition ( /dev/hda3 ) should be in a unmounted state.Lastly can I choose not to install open office and the gimp? I never use open office and seldom use the gimp.I'm open to any tips for installing pclos-8.

[ross549]

Hi Dard......You can do all the updates from synaptic... it is not a problem.If you wish to do it in the command line.... (as root)apt-get updateapt-get dist-upgradeWill have you 100% up to date.

[Bruno]

Lastly can I choose not to install open office and the gimp? I never use open office and seldom use the gimp.

<{POST_SNAPBACK}>

Nope but you can remove them after the install . . . . .The install is pretty generic it just installs all that is on the Live CD too . . . but later you can remove or add whatever you want with synaptic or apt get ;) Bruno

[Dard]

Hi Dard......If you wish to do it in the command line.... (as root)

<{POST_SNAPBACK}>

I think that it sould be done in runlevel 3 so that no part of the KDE gui is running, because I also see xorg x server stuff needs to be updated or upgraded?What do you think, runlevel 3 or runlevel 5?Oops almost forgot, install lilo or not? I have yoper and slackware 10 already installed here, and use the slackware lilo for the boot loader.Thanks Ross, and Bruno.

[Bruno]

Oops almost forgot, install lilo or not? I have yoper and slackware 10 already installed here, and use the slackware lilo for the boot loader.Thanks Ross, and Bruno.

<{POST_SNAPBACK}>

I would not install Lilo in that case . . and we will add it to the Slackware lilo . . . . no problem.I would do the updates in the GUI . . . because it does not change KDE version it is no probelm. . . So runlevel 5 ( also the xorg is just an upgrade, it does not switch from XFree to Xorg ) BrunoPS: If you can tell me now what partition it will be on I will post the commands you will have to give in Slack to add it to Slacks lilo . . . found it: hda3

[Dard]

Thanks BrunoIf I do not install lilo, will there be a populated pclos /etc/lilo.conf so that I could get that information there to add to the slackware lilo? or just do a generic entrys?I have to go out and clean the battery cables on the car before I can start this, otherwise I'll disturb the domestic tranquility here. I'm sure you understand how that works. :lol:Must be getting late in Amsterdam so I'll see you later Bruno.

[ross549]

I think that it sould be done in runlevel 3 so that no part of the KDE gui is running, because I also see xorg x server stuff needs to be updated or upgraded?What do you think, runlevel 3 or runlevel 5?Oops almost forgot, install lilo or not? I have yoper and slackware 10 already installed here, and use the slackware lilo for the boot loader.Thanks Ross, and Bruno.

<{POST_SNAPBACK}>

I do x.org updates and KDE updates in runlevel 5 all the time.... never had a problem yet..... just usually reboot right after that.

[Dard]

PS: If you can tell me now what partition it will be on I will post the commands you will have to give in Slack to add it to Slacks lilo . . . found it: hda3

<{POST_SNAPBACK}>

Yes yoper is on /dev/hda1 slackware is on /dev/hda2 and pclos will be on /dev/hda3.

[Bruno]

DardNot installing lilo is no problem because I have all the entries right here:This is what you do when PCLos is installed and you are booted in Slackware:

$ su# mkdir /mnt/hda3# mount /dev/hda3 /mnt/hda3# cp -r /mnt/hda3/boot  /boot/pclos# umount /mnt/hda3

Then you open the /etc/lilo.conf in your favorite editor: ( as root )

# kwrite /etc/lilo.conf

And you add this part:

image=/boot/pclos/vmlinuz-2.6.7-2.tmb.6mdk        label="PCLos-8"        root=/dev/hda3        initrd=/boot/pclos/initrd-2.6.7-2.tmb.6mdk.img        append="devfs=nomount acpi=ht nomce splash=silent"        vga=788        read-only

Then you save the file and do:

# /sbin/lilo

And the job is done and you can boot into PCLos . . . from the Slackware Lilo( Is this simple or what ? ) Bruno

[Dard]

I do x.org updates and KDE updates in runlevel 5 all the time.... never had a problem yet..... just usually reboot right after that.

<{POST_SNAPBACK}>

Ok ross that works for me, thanks. :DDard likes it when things work easy. is vga=788 for 1024x768?I have never seen the 'nomce' before in the append line, any idea what that part is for?

[Bruno]

is vga=788 for 1024x768?

<{POST_SNAPBACK}>

Yep it is . . . . . And I found this on no-mce it explains it better then I can:

With some research, I found out that this is a Machine Check Exception.   Apparently the Linux Kernel does intermittent hardware checks, and panics when something is out of whack.  Anyway, all of my hardware runs fine under the default OS (to remain nameless - use your imagination), so it doesn't actually appear to be a hardware problem.  So with a little more research I discovered that there is a Kernel parameter that'll solve this pesky problem.  Just add nomce to lilo.conf (or the bootloader at install time).

Bruno* I am logging out because it is getting late . . . but I will surely see in the morning that you were successful and are posting from PCLos

[Dard]

Ok Bruno, and thanks for all of your help, and I shall post back and let you know how this all works out. :)I see that it's midnight in Amsterdam, pleasent dreams.

[Bruno]

Thanks Dard !! Will do ! ;)The best of luck with the install, but you will see that it is really really simple. Bruno

[steel]

hi Dard here are a few simple apt-get commands that i use myself to update your system all in one shot do this

# apt-get update; apt-get -u upgrade

all you updates from apt-get go to /var/cache/apt/archivesif you wanted to update them so later you can copy them to your cdrom you would do this

# apt-get autoclean

what that does is ..example say that you have emac 2.1 and emac 2.2 it will delete the old one which is emac 2.1 and keep emac 2.2 ....if you dont want to save any of your updates you would do

 # apt-get clean

that will clean all your updates and free up your /var/cache/apt/archivesalso install

# apt-get install deborphan

then you would use

# deborphan

now to get rid off your orphan files you would use

 # deborphan | xargs apt-get -y remove --purge

you could also use apt-spy but you have to configure it properly if you wanted to use it and what that does is find the fast sources close to you and when everything is all done you would use

$ apt-get moo

[Dard]

Thanks steelLater I'll have to look up what the -u part does in the apt-get -u upgrade command.

[ikerekes]

dard you might want to hold on and get the new release hot from the press

[Dard]

Works for me Ivan!Now all I have to do is locate the ftp site link , thanks! Talk about "hold the presses" I caught this just in time.Who knew that cleaning battery cables on the car would save the day and keep the domestic tranquility.

Edited February 19, 2005 by Dard

[steel]

dard you might want to hold on and get the new release hot from the press

New Release?

[steel]

Thanks steelLater I'll have to look up what the -u part does in the apt-get -u upgrade command.

<{POST_SNAPBACK}>

Your Welcome Dard and the -u option causes APT to show the complete list of packages which will be upgraded. Without it, you'll be upgrading blindlyalso you can do searches with apt-get example, we will use games as an example

$ apt-cache search games

now if you see one that looks interesting and you wanted some info on it you would do thiswe will use "supertux "as an example

$ apt-cache show supertux

that will tell you about the game this is if you ever have to reinstall anything

# apt-get --reinstall install "packagename"

that will give discription of the game if you ever want to remove a package

apt-get remove "packagename"

Running apt-get as below will cause the packages to be removed but their configuration files, if any, will remain intact on the system. For a complete removal of the package,run.

# apt-get --purge remove "packagename"

just small amount of my own notes, hope it helps a little,Dard ...

Edited February 19, 2005 by steel

[Dard]

Yeah, that sure does help steel, thanks! :)I just got through downloading the .iso I did not see any md5sum file there though, so I couldn't check the .iso against what was downloaded.Here is the md5sum that I got.$ md5sum pclinuxos-p81.iso3b99685dde873dff4969f2cdd5e33f5c pclinuxos-p81.isoSo all that I can do is burn it and see if it works ok.I got it from here:ftp://ibiblio.org/pub/linux/distributions...english/previewFor http:http://www.ibiblio.org/pub/linux/distribut...nglish/preview/If this keeps up I'll never get the thing installed. The nerve of Texstar, releasing bugfixes and securtiy updates behind Bruno's back. He goes to sleep and bam... a new iso it available to everyone! What's this world coming to?

[steel]

Yeah, that sure does help steel, thanks!  :)I just got through downloading the .iso I did not see any md5sum file there though, so I couldn't check the .iso against what was downloaded.The nerve of Texstar, releasing bugfixes and securtiy updates behind Bruno's back. He goes to sleep and bam... a new iso it available to everyone!  What's this world coming to?       

Hi Dard your welcome if there is any questions about debian and apt i know a lil bit about that so just ask away .. as for checking your md5 if you use k3b there is build in checker that you can use before burning that will give you the same numbers as you have there ... and whats the matter with the site was it slow?? i am sure by the time Bruno wakes up you will have everything up and running :thumbsup:ohhh i checked for you and md5 looks good 3b99685dde873dff4969f2cdd5e33f5c pclinuxos-p81.iso Edited February 19, 2005 by steel

[Dard]

Well First thing that I did was to format /dev/hda3 to the reiserfs in this distro.

# mkreiserfs /dev/hda3

Then I did the unthinkable and rebooted, with the PCLos CD. After checking out the new -p81 in livecd mode I wouldn't install it.Looks like a lot of thought went into this release, however I just couldn't get out of 800x600 60Hz resolution. Did the XFdrake to set the monitor correctly then did the video card, it was ati radeon 9200SE fgl-something, changed that to just radeon, did the test, looked ok, then loged out and back in as guest as the dialog box said to do, still nogo.Stuck in 800x600 60Hz resolution. And I want 1024x768 at 85Hz.I spent a little time checking this distro out and it looks decent, the Corona theme is not there, so thats a let down for me, but with the .iso at 634.9 megs, something had to be left out. PCLos did correctly identify my sound card. NIC, mouse, burner. I can't say that I'm impressed with the galaxy theme, or whatever it is in this release though. I changed that to plastik and that was more to my liking.I used X-Chat on the internet so my connection was there, and solid. I had to bail out because of the eyestrain. For whatever reason the drop down menus had a pink tint to it, most likely video card related.I may try this again later today, maybe even try the -p8 and see if it will let me change resolutions. But for now I have to give my eyes a rest. steel, I believe those apt-get commands are for debian, not PCLos which is rpm based, but I copied them to a file anyways, cause you never know I may try debian some day.

[Bruno]

Hi DardThere might be help on the way . . . . because if you check:ftp://ibiblio.org/pub/Linux/distributions...nglish/preview/There is a file called "pclinuxos-ATI-p81a.asc" ( a checksum file ) what makes me believe that later today there will be a special ATI iso up there Bruno

[Dard]

Hi DardThere is a file called "pclinuxos-ATI-p81a.asc" ( a checksum file ) what makes me believe that later today there will be a special ATI iso up there Bruno

<{POST_SNAPBACK}>

Looks that way to me also Bruno, can't imagine they would upload that -p81a.asc without a .iso to follow at some point in time.Whats odd is that I have excellent resolution in yoper and slackware 10 with this video card and monitor setup.

[Bruno]

Anyway Dard, most of the Lilo-instructions I gave you will still be valid for this release . . . only the numbers of the vmlinuz and intird.img will have to change in the section I posted to insert in the Slack Lilo.conf ( So please do keep an eye on that ) Burno

[steel]

steel, I believe those apt-get commands are for debian, not PCLos which is rpm based, but I copied them to a file anyways, cause you never know I may try debian some day. 

Dard the was going to be one of my questions, was going to ask you what Debian based distro did ya have, cos all i seen was talk about PClos and yet in post #1 you said

I think it's the apt-get application that I would need to use for this instead of synaptic because I don't think that having kde open while updating it's base libs and stuff works.

.. so i guess thats where i thought you had another debian distro, anyway good luck with Pclos its a fun distro and i am sure that you will love the new one ..

[Dard]

Hi DardThere might be help on the way . . . . because if you check:ftp://ibiblio.org/pub/Linux/distributions...nglish/preview/There is a file called "pclinuxos-ATI-p81a.asc" ( a checksum file ) what makes me believe that later today there will be a special ATI iso up there Bruno

<{POST_SNAPBACK}>

Behold... pclinuxos-ATI-p81a.iso (639.3 MB) is now on the ftp server. :DAlong with... pclinuxos-NV-p81a.iso (639.7MB) now that's service! :DAnd keeping the .ISO's below 650megs means every burner should have no trouble burning them.

[Bruno]

Hi DardHere is the adapted version of the lilo instructions from earlier in this thread:( So do not write Lilo to the MBR during the install )This is what you do when PCLos is installed and you are booted in Slackware:

$ su# mkdir /mnt/hda3# mount /dev/hda3 /mnt/hda3# cp -r /mnt/hda3/boot  /boot/pclos# ls -al /boot/pclos# umount /mnt/hda3

And just to be 100% sure, check in the output of the before last command if the ATI version has the same vmlinuz as I include in the lilo.conf below ;)Then you open the /etc/lilo.conf in your favorite editor: ( as root )

# kwrite /etc/lilo.conf

And you add this part:

image=/boot/pclos/vmlinuz-2.6.10-oci7        label="PCLos-81"        root=/dev/hda3        initrd=/boot/pclos/initrd-2.6.10-oci7.img        append="splash=silent"        vga=788        read-only

Then you save the file and do:

# /sbin/lilo

And the job is done and you can boot into PCLos . . . from the Slackware LiloB) Bruno

[Dard]

Bruno, thanks, here is my slackware lilo.conf and it looks like I should change vga=773 to vga=791 while I'm editing for pclos. :)It is now time to burn the new pclos.iso $ cat lilo.conf# LILO configuration file# generated by 'liloconfig'## Start LILO global sectionboot = /dev/hdamessage = /boot/boot_message.txtprompttimeout = 1200# Override dangerous defaults that rewrite the partition table:change-rules reset# VESA framebuffer console @ 1024x768x256vga = 773# Normal VGA console# vga = normal# VESA framebuffer console @ 1024x768x64k# vga=791# VESA framebuffer console @ 1024x768x32k# vga=790#original slack10 kernel# image = /boot/vmlinuz# root = /dev/hda2# label = Slack10# read-onlyimage = /boot/vmlinuz-2.6.10 root = /dev/hda2 label = Slack-10-2.6.10 read-onlyimage=/mnt/yoper/boot/vmlinuz-2.6.8.1-7label=YOPER-2.6.8.1-7 read-only root=/dev/hda1append = "splash=silent "initrd=/mnt/yoper/boot/initrd-2.6.8.1-7.imgI'm thinking that I could just reboot after the pclos install into slackware and copy the pclos stanza from this thread into slackwares lilo.conf, then run /sbin/lilo which is probably what you had in mind all along.Of course I would have to have 1024x76@85Hz otherwise I won't install it. :)But somehow that would be to easy, perhaps it would be more difficult, errr fun to install pclos's lilo then mount the slack lilo.conf copy all the stanza's over to pclos and go round robin with the three distros. I'd like to burn the .iso just like mom used to do at the command line, but K3B works so well I'll use that.

[Bruno]

perhaps it would be more difficult, errr fun to install pclos's lilo then mount the slack lilo.conf copy all the stanza's over to pclos and go round robin with the three distros.

Then you will have to add Slack first to the PCLos lilo to be able to boot . . . . I think it is more work and not needed because Slack is the stable distro here and that should be the LILO you use.So better not install the PCLos lilo at all and add it to the Slack Lilo

I'm thinking that I could just reboot after the pclos install into slackware and copy the pclos stanza from this thread into slackwares lilo.conf, then run /sbin/lilo which is probably what you had in mind all along.

Almost correct . . . but you need to "cp -r /mnt/hda3/boot /boot/pclos" first or the lilo will complain that it can not find the files lilo.conf is pointing to :DB) Bruno