InstallFest Fall '09

[securitybreach]

Thats one way to do it. Why not just add

feh --bg-center '<path to wallpaper>

to ~/.config/openbox/autostart.sh, instead of making a ~/.fehbg and using autostart.sh to link it? Seems a little backwards, you could of just put the command in autostart.sh?Thanks

Edited November 8, 2009 by securitybreach

[V.T. Eric Layton]

As explained above Openbox does NOT initialize the ~/.config/openbox/autostart.sh when startx from the run level 3 (no X running) is invoked. I would have to be using a graphic login on RL 5 for that autostart.sh to run. Since I'm starting in RL 3 with no X, I have to place the startup stuff in /etc/xdg/xsession/lxde/autostart.sh file instead. There are two commands to invoke an openbox session. One is "openbox", which is what's used by LXDE when you startx from the non-graphical RL 3. This will NOT run Openbox's autostart.sh script. The other command to invoke an openbox session is "openbox-session". This one is for non-graphical startups and needs to be in xsession because xsession starts before openbox. At least this is how I understand it. It's the only way for it to work on a non-graphical (RL 3) startup, though. I tried every other way the past two days. ;)Oh, and my sound is OK.

[securitybreach]

As explained above Openbox does NOT initialize the ~/.config/openbox/autostart.sh when startx from the run level 3 (no X running) is invoked. I would have to be using a graphic login on RL 5 for that autostart.sh to run. Since I'm starting in RL 3 with no X, I have to place the startup stuff in /etc/xdg/xsession/lxde/autostart.sh file instead. There are two commands to invoke an openbox session. One is "openbox", which is what's used by LXDE when you startx from the non-graphical RL 3. This will NOT run Openbox's autostart.sh script. The other command to invoke an openbox session is "openbox-session". This one is for non-graphical startups and needs to be in xsession because xsession starts before openbox. At least this is how I understand it. It's the only way for it to work on a non-graphical (RL 3) startup, though. I tried every other way the past two days. Oh, and my sound is OK.

Wow and I thought Arch was complicated. Openbox starts the "autostart.sh" just fine with startx on RL3 using Arch. To start openbox/autostart, I just use "exec openbox-session" in ~/.xinitrc and the autostart.sh works just fine. I figured something like this would be in Sidux too. Did you make autostart.sh executable? Just throwing out ideals since it seems overly complicated to simply autostart something in Sidux.Since LXDE is a bit different from regular Openbox, maybe try this from Archwiki LXDE???:

The default system-wide startup config files can be found at /etc/xdg/lxsession/LXDE/autostart. If you choose to edit the autostart programs for all users you can open the file /etc/xdg/lxsession/LXDE/autostart with a text editor and add the name of the program(s) you want to start at login.The system-wide autostart file can also be overridden by user-specific ones. If custom user specific config files are found in ~/.config/lxsession, the ones in /etc/xdg/lxsession will be overridden.Another way to start programs on session startup is to add their *.desktop files in ~/.config/autostart.

http://wiki.archlinux.org/index.php/LXDEIt might be the same in Sidux since Arch tries to use the program defaults for config locations.Thanks Edited November 8, 2009 by securitybreach

[V.T. Eric Layton]

It's funny, but I get a lot of answers from that Arch Wiki about stuff that I'm doing in other distros. This wouldn't be the first time I get info that way.

Did you make autostart.sh executable?

Yuppers!

[V.T. Eric Layton]

We're still shaping up here.

[V.T. Eric Layton]

OK, spent some time this evening setting up PCLOS-Phoenix. It's about done now... just need to install some of my fav apps. All else is taken care of. Easy-peasy, actually. No screaming or hair-pulling with PCLOS-Phoenix.

[securitybreach]

It's funny, but I get a lot of answers from that Arch Wiki about stuff that I'm doing in other distros. This wouldn't be the first time I get info that way. Yuppers!

Yeah the wiki is great. I have a couple of friends on Ubuntu (sorry just not my cup of tea) and I frequently send them references from the Archwiki to solve various linux problems. I am not saying this because I use Archlinux, but I think the Archlinux wiki has some of the best documentation of any distribution out there. Just my opinion though.Thanks Edited November 10, 2009 by securitybreach

[V.T. Eric Layton]

Here's PCLinuxOS - Phoenix w/ Xfce:Simple but... it works! =====I agree. Arch has exceptionally well done and maintained documentation and wiki pages. Too bad all distros don't have excellent support like that.

Edited November 10, 2009 by V.T. Eric Layton

[securitybreach]

Here's PCLinuxOS - Phoenix w/ Xfce: ===== I agree. Arch has exceptionally well done and maintained documentation and wiki pages. Too bad all distros don't have excellent support like that. Simple but... it works!

Looks nice and I agree!!!

[V.T. Eric Layton]

I need numlockx for Slackware 13-64, but all I can find are the Slack Build and the source. Neither will compile properly. I keep getting some gc c error. What am I doing wrong?

[V.T. Eric Layton]

Part of the config.log in the SBo directory after attempting to run the SlackBuild script:

gc>c: '-V' option must have argumentconfigure:2072: $? = 1configure:2095: checking for C compiler default output file nameconfigure:2098: gc>c -O2 -march=i486 -mtune=i686 conftest.c >&5conftest.c:1: error: CPU you selected does not support x86-64 instruction setconfigure:2101: $? = 1configure: failed program was:| /* confdefs.h. */| | #define PACKAGE_NAME ""| #define PACKAGE_TARNAME ""| #define PACKAGE_VERSION ""| #define PACKAGE_STRING ""| #define PACKAGE_BUGREPORT ""| #define PACKAGE "numlockx"| #define VERSION "1.1"| /* end confdefs.h. */| | int| main ()| {| | ;| return 0;| }configure:2140: error: C compiler cannot create executables

Note anywhere above that there was a g c c, I had to make it like this --> gc>c or the board wouldn't let me post it.

[V.T. Eric Layton]

Here's the terminal output when trying to compile from source:

bash-3.1# ./configurechecking for a BSD-compatible install... /bin/ginstall -cchecking whether build environment is sane... yeschecking for gawk... gawkchecking whether make sets $(MAKE)... yeschecking for gc>c... gc>cchecking for C compiler default output file name... a.outchecking whether the C compiler works... yeschecking whether we are cross compiling... nochecking for suffix of executables... checking for suffix of object files... ochecking whether we are using the GNU C compiler... yeschecking whether gc>c accepts -g... yeschecking for gc>c option to accept ANSI C... none neededchecking for style of include used by make... GNUchecking dependency style of gc>c... gc>c3checking for ranlib... ranlibchecking how to run the C preprocessor... gc>c -Echecking for X... configure: error: Can't find X includes. Please check your installation and add the correct paths!

[sunrat]

Do you have dev files for xorg and xorg-server?

[V.T. Eric Layton]

Uh... I dunno.

[V.T. Eric Layton]

Hmm... I'm sorely disappointed with Slackware 13-64. I can't run it with that buggy KDE4. I can't seem to get Xfce to function well in it either. Man! It's so terrible. I feel like I'm losing my best friend. I'm so aggravated with Slack that I haven't even booted into my 12.2 primary installation this week. I've been using Debian instead.

[securitybreach]

Hmm... I'm sorely disappointed with Slackware 13-64. I can't run it with that buggy KDE4. I can't seem to get Xfce to function well in it either. Man! It's so terrible. I feel like I'm losing my best friend. I'm so aggravated with Slack that I haven't even booted into my 12.2 primary installation this week. I've been using Debian instead.

Looking out the window for flying pigs......Eric not happy with Slackware. Oh no!!!!Thanks

[V.T. Eric Layton]

Sad, ain't it?

[securitybreach]

Sad, ain't it?

Well do not forget about Arch.....Thanks

[V.T. Eric Layton]

I spent most of the day in Arch on Monday, actually. It works. It's nice. Arch with Gnome has been rock solid... I have no complaints about that distro, my friend. :)I spent yesterday with Slack 13-64. I'm using Slack 13-64 right now, actually... trying to iron out a few things. Wish I could figure out why I can't compile that numlockx. :(Made my first GRUB splash yesterday. It's simple, but I think it's cool.

[securitybreach]

Made my first GRUB splash yesterday. It's simple, but I think it's cool.

Thats pretty cool!! I like it.Thanks Edited November 12, 2009 by securitybreach

[V.T. Eric Layton]

It looks really good with white GRUB menu fonts. Wish I knew how to screenshot GRUB or had a digital camera to take a pic. =====Anyway, back to the numlockx in Slack13-64 issue. It seems to be some sort of issue with this particular SlackBuild. I just install Pysolfc from SlackBuild with no probs at all. *scratching head* I can't compile numlock from source either. I'll bet this is some 64 bit do-do.

[V.T. Eric Layton]

Want to see something utterly ridiculous? Here's what is required to add/remove menu entries in Xfce 4.6 --> http://wiki.xfce.org/howto/customize-menuI just spent two hours trying to add one crummy entry to my menu. Still didn't get it to work. I give up. :(I can't even begin to imagine needing to do this for all the apps I add to Slack 13 w/ Xfce.

[V.T. Eric Layton]

If I could get this numlockx issue and a few other minor ones solved in Slackware 13-64/Xfce, I think it would be ready-for-prime-time (moving to the primary distro slot) on my system. I can live with the menu editing issue. Besides, I could make one lump category and put all my added apps in there. It would be easier that way. I could call it "Eric's Apps" or something like that. The editing would be simplified if I used on category like that. However, it's a real pain in the posterior area to remember to click the Num Lock button on my keyboard at startup every time. I sure would like to get numlockx to compile on this system. *sigh* Wish I knew more about configuring/building from source.

[V.T. Eric Layton]

I'd like to get Slack experimental finalized so that I can be sure that it will be satisfactory to me as my primary distro. I want to clear that last set of partitions that I'm currently using for the experimental Slack so that I can install either Mandriva Free x86_64 or OpenSuse x86_64. I don't know which; I may just flip a coin.

[V.T. Eric Layton]

Once I succeed in setting up Slack 13-64 w/ Xfce as my primary distro and then set up either Mandy or Suse as my 5th experimental, the Installfest Fall '09 will be officially ended and I can close out this boring thread that no one reads anymore anyway. I could probably post porn here and no one would notice. :(Off I go...

[kamicota]

Now Now Eric enough of the doldrums Cheers for YearsColin

[securitybreach]

Once I succeed in setting up Slack 13-64 w/ Xfce as my primary distro and then set up either Mandy or Suse as my 5th experimental, the Installfest Fall '09 will be officially ended and I can close out this boring thread that no one reads anymore anyway. I could probably post porn here and no one would notice. Off I go...

So I take it that Archlinux is more than just one of your "experiments".... I read this thread so feel free to post porn, I wont mind Thanks Edited November 13, 2009 by securitybreach

[sunrat]

It's a major pain not having a menu editor. Hopefully it does return in Xfce 4.8 as mentioned in the linked page. Xfce is a very nice DE, but I wouldn't be bothered doing menus manually. It's easier in LXDE isn't it? I'm still tempted to try E17, but have a major model helicopter build project ATM, so not yet.My sidux install fest is finished now. I switched totally from Lenny to momos almost overnight. Got Flash, Nvidia drivers, bookmarks, mail, favourite apps all set up in record time. It actually is much faster with KDE4.2.3 than Lenny ever was with KDE3.5. Please don't post any pr0n here, I only like looking at funny pics of cute kitties. Maybe kitty pr0n?

[V.T. Eric Layton]

WAAAAAAAAAAHOOOOOOOOOOOOO!I solved the numlockx problem in Slack 13-64. YAY! I decided earlier today to just go ahead and take the plunge. I backed up my important stuff in Slack 12 and plowed that baby under. I installed Slack 13-64 w/ Xfce as my primary distro. I've been working on it all night, with a short break to watch Alien vs. Predator on the Friday Night Movie a little while ago. I'm downloading and working on installing some of my most needed apps (OpenOffice, Xfburn, etc.) from SlackBuilds right now. Everything seems to be going smoothly. 13 is one of my lucky numbers, actually. :yes:The problem with the numlockx SlackBuild was that I need to specify my ARCH in the command line like this:

# ARCH=x86_64 ./numlockx.SlackBuild

Once I did that, it compiled flawlessly. Silly me. I just haven't gotten the hang of this fancy, new-fangled 64 bit computing stuff yet. ;)So, I'll be putting the finishing touches on my new Slack 13 over the coming weekend, then I'll be installing something (leaning toward OpenSuse) on those available experimental partitions left over from the experimental Slack 13-64.And no, SB... Arch is something more than just an experiment now. I will always have Arch on my system from now on. The main purpose for me to have all these different distros on my system is to learn how the all work. You'll notice that I try to install distros with completely different windows and desktop managers, different package managers, etc. I have a couple Gnomes, an old KDE3.5, a couple Xfces, and an LXDE/Openbox. I use Apt, Yum, Slackpkg, Pacman to manage .tgz, .txz, .deb, .rpm, etc. It's definitely a learning environment. :)Well, off I go now...

[sunrat]

I won't comment on this, I'll just post the link:Slacker Madness!