Hello,

I'm trying to install gsb-current with Slackware 12.2. I'm not even done with the upgrades that I have errors on my bootup. All I did was install slapt-get, added the sources of slackware 12.2 and gsb-current, changed the exclude section of the slapt-getrc file, ran slapt-get --update and --upgrade, installed the glib2 and libwnck, and rebooted. I was about to log in as root init level 3 and install gsb-complete this time, wishing the errors would go away, but what a surprise, I didnt even install gsb yet that errors start to pop. Is that normal? Is there a way to look at the logs of my bootup sequence and see what is wrong? Am I the only one getting these errors? I would love to copy paste them, but I dont know where the logs are. Did I need to install glib2 and libwnck on level 3 too or I was ok in kde level 4?

Anyone has help?

All the logs are in the /var/log directory. Also after the bootup process, you can type dmesg to see the buffer of the bootup, also there is a dmesg file in /var/log but you must log into root to see it, but it will also contain the startup messages during boot.

I think though for GSB, it would have been easier just to go through the GSB's site and download a package for installation. I don't know of GSB does that, but DROPLINE GNOME does have an installer package, you install that, and then run the program from that package (as root), which will continue the installation of that particular version of GNOME. I don't know how GSB works, so all I can say is go to their site, and see the documentation.

Yeah well thanks for the answer. /var/log. Ill check it out. In the meantime, going to wait for 12.2 to come out. Maybe reinstall 12.1. I just dont like kde.

Cheers,

Go to the GSB site and check-out the how to on installing GSB. GSB has an installer that you will download and run. I haven't run GSB in awhile ,but, it was a good, solid version of Gnome for Slackware. GSB doesn't replace a lot of stock Slackware files.

I think GSB (maybe even Freerock), are the only two versions that still do not incorporate PAM. I wonder just how long can these alternate forms of GNOME will work, until maybe sooner or later PAM becomes mandatory for GNOME.

Well, I might want ot read a few more files like changes and hints.txt... I just dont know why when I update my system, and change the glib2 file, errors pop, and when I install the firefox and pidgin updates, they stop working. Its weird. I've never seen this before, where when you install an update, chances are it might not start anymore. Slackware is all new to me. I try to read the most of it, but sometimes, I need help, so I ask for it...

As for the installer, I use slapt-get.

And yeah, you're right, thats what I heard, gsb doesnt replace too many files. So yeah, cant wait to get this working with 12.2...

I would have used 12.1, but dma isnt enabled by default. So this is what I did. I booted the hugesmp.s file this way:

hugesmp.s hda=noprobe hdc=noprobe libata.atapi_enabled=1

With this, my hda and hdc become sda and sdc, and dma works for the installation. But after, when you reboot, hum hum, surprises. I need to edit the fstab file and lilo.conf file. But I dont know how. If I cant boot, I cant edit the files... Unless this has to be done right after the installation? Where is the lilo.conf file anyway? And how do you search for a file on the filesystem? An option of ls? I might want to read the manual for ls too...

I'm happy though, Slackware keeps me busy. With a little chance, I'll be good at it. And there are so many great people that help, so, I dont feel alone, wich is reassuring.

Cheers,

Spoken like a true Slacker! Be persistent and you will prevail. From what I've read on the site it looks like the developers are timing their next release of GSB to coincide with the release of Slackware 13.0.

Well, I found the lilo.conf, but without the ls or dir command. I thought that this one would find it, like
ls -R lilo.conf
done from the / folder, but no luck. Still, what do I write in the lilo.conf file? And when do I do it? I need to write the hda=noprobe and hdc=noprobe in that file... Plus, when I finished the installation of slackware 12.1, I gave a peak at fstab, and it was empty. Shall I take a chance and write everything right after the installation, and do the same with the lilo.conf file?

I know I was patient enough when I started with slackwre; I waited the whole hour of installation of 12.1 without the dma, cause I didnt know where to look to enable it. And once I was done, gsb installed fine, cause I followed all the info on the gsb web site and install files in the repo's. And yeah, it started, and was stable. No errors.

Another option would be maybe to wait for gsb to be stable for 12.2... I just aint the patient type It had to work yesterday :P And since everyone else seems to be able to do it...

Hum, so, maybe I should start a new thread and ask help to configure my dma with 12.1. I just want gsb to work. I really dont like kde.

Well, there we go. Opened a thread, and just expressing myself to myself, I found the answer. Pass the info to the kernel, again at the end of the setup, and dma is enabled and configured. I feel so happy.

Viva Slackware.

All thats left, is to test the stable version of gsb for 12.2 when its released. Now for the install of 12.1.

Cheers,