Figured it was time. Nothing special
-
Posts: 4,164
- Joined: 20 Feb 2009
-
Posts: 51
- Joined: 09 Jun 2008
#2
Very nice! Is the 2nd screenie using conky as well?
-
Posts: 4,164
- Joined: 20 Feb 2009
#3
My post is over at
post18383.html?hilit=%20conky#p18383
Yep nats007.nats007 wrote:Very nice! Is the 2nd screenie using conky as well?
My post is over at
post18383.html?hilit=%20conky#p18383
-
Posts: 51
- Joined: 09 Jun 2008
#4
Thank you sir! That's pretty slick, I might check this out with my Mepis 11 using conky setup.
-
Posts: 4,164
- Joined: 20 Feb 2009
#5
AntiX 11 Frugal on a Stick. Listening to pianobar on earbuds.
-
Posts: 1,520
- Joined: 07 Oct 2007
#6
Nice ride!
-
Posts: 609
- Joined: 02 Jun 2008
#7
which one? __{{emoticon}}__
-
Posts: 4,164
- Joined: 20 Feb 2009
#8
Pendrive Setup on my Acer Aspire One ZG5. Had to work on Conky to get temps and such to work. Finished tonight,
-
Posts: 4,164
- Joined: 20 Feb 2009
#9
AntiX 11 Patch 3 Fluxbox
-
Posts: 4,164
- Joined: 20 Feb 2009
#10
Latest Install on Ibm A22m. Fluxbox shot. I won't run wbar since I only have 256MB of ram available. So I made my menu pretty instead.
-
Posts: 128
- Joined: 31 Jan 2009
#11
Rokytnji,
what a hilarious wallpaper! Great!
what a hilarious wallpaper! Great!
-
Posts: 1,062
- Joined: 20 Jan 2010
#12
Nice shots roky,
just to make note, wbar should run fine on 256 mb of ram wbar uses 2.7% of it. I am running wbar with that amount of ram no problems.
Here is my inxi output
and a screenshot in fluxbox to match, conky shows higher ram usage from iceweasel.
just to make note, wbar should run fine on 256 mb of ram wbar uses 2.7% of it. I am running wbar with that amount of ram no problems.
Here is my inxi output
Code: Select all
CPU: Single core mobile AMD Athlon XP 1500+ (-UP-) cache 256 KB flags (sse) bmips 2600.23 clocked at 1299.948 MHz
Graphics: Card S3 VT8636A [ProSavage KN133] AGP4X VGA Controller (TwisterK) X.Org 1.7.7 Res: 1024x768@60.0hz
GLX Renderer Mesa DRI Twister 20061110 AGP 1x x86/MMX+/3DNow!+/SSE GLX Version 1.2 Mesa 7.7.1 Direct Rendering Yes
Audio: Card VIA VT82C686 AC97 Audio Controller driver VIA 82xx Audio at ports e000 e100 e104 BusID: 00:11.5
Sound: Advanced Linux Sound Architecture Version 1.0.21
Network: Card-1 Broadcom BCM4306 802.11b/g Wireless LAN Controller driver ndiswrapper v: 1.56 BusID: 02:00.0
Card-2 VIA VT6102 [Rhine-II] driver via-rhine at port e800 BusID: 00:12.0
Disks: HDD Total Size: 80.0GB (5.8% used) 1: /dev/sda FUJITSU_MHV2080A 80.0GB
Partition: ID:/ size: 36G used: 4.4G (13%) fs: ext4 ID:swap-1 size: 1.98GB used: 0.00GB (0%) fs: swap
Sensors: System Temperatures: cpu: 29.8C mobo: 2.1C
Fan Speeds (in rpm): cpu: 0 fan-2: 0
Info: Processes 110 Uptime 1 min Memory 88.4/231.9MB Runlevel 5 Client Shell inxi 1.4.23
-
Posts: 4,164
- Joined: 20 Feb 2009
#13
Edit: I see you figured out Lxpanel also. Curious on how you deleted fluxbox slit and got lxpanel to stick on reboot and logout.
Thanks for that info Dave __{{emoticon}}__ . Was worried I was going to lock up things if I added weight to running processes.Nice shots roky,
just to make note, wbar should run fine on 256 mb of ram wbar uses 2.7% of it. I am running wbar with that amount of ram no problems.
Edit: I see you figured out Lxpanel also. Curious on how you deleted fluxbox slit and got lxpanel to stick on reboot and logout.
-
Posts: 1,062
- Joined: 20 Jan 2010
#14
Here are the steps that I used to run lxpanel and wbar
1) open ~/.fluxbox/init in leafpad or another editor and found the line
remove iconbar and system tray from the line so it looks similar to this
2) edited ~/.fluxbox/startup and added the lines ( can be done using add-start in M11 )
the sleeps are added to allow my slow machine time to set wallpaper, fluxbox menu / taskbar, etc... Without the sleeps wbar will need to be refreshed to match background and lxpanel may not have a working system tray. If you find you need to refresh wbar, or there is no system tray in lxpanel, then increase the sleep times.
As for the slit, I have not seen a need to delete it, probably because I have not yet figured out how it works __{{emoticon}}__
EDIT
As a side note I have found that applications that were maximized before having lxpanel would maximize under lxpanel. To solve the issue I had set lxpanel to autohide, setting it to a lower layer via ~/.fluxbox/apps also helps resolve the issue but will not resolve it completely .
Here is the code from ~/.fluxbox/apps
1) open ~/.fluxbox/init in leafpad or another editor and found the line
Code: Select all
session.screen0.toolbar.tools: workspacename, prevworkspace, nextworkspace, iconbar, systemtray, prevwindow, nextwindow, clock
Code: Select all
session.screen0.toolbar.tools: workspacename, prevworkspace, nextworkspace, prevwindow, nextwindow, clock
Code: Select all
sleep 2 && lxpanel &
sleep 6 && wbar &
As for the slit, I have not seen a need to delete it, probably because I have not yet figured out how it works __{{emoticon}}__
EDIT
As a side note I have found that applications that were maximized before having lxpanel would maximize under lxpanel. To solve the issue I had set lxpanel to autohide, setting it to a lower layer via ~/.fluxbox/apps also helps resolve the issue but will not resolve it completely .
Here is the code from ~/.fluxbox/apps
Code: Select all
[app] (name=lxpanel)
[Tab] {no}
[Deco] {NONE}
[Hidden] {yes}
[Layer] {2}
[end]
-
Posts: 4,164
- Joined: 20 Feb 2009
#15
Thanks Dave. Will give it a shot first in gear where I have wbar installed first. Appreciate the feed back as always from you.