/etc/slackware-version

SqdnGuns · 07-08-2009, 08:02 PM

What, if any impact is there system wide if I edit the /etc/slackware-version file?

My reason for asking is I have a .conkyrc that calls upon that file. As it is now in Slackware64-Current, it displays Slackware 13.0.0.0, I have edited it to reflect Slackware64 13.0

Thanks in advance.

Bruce Hill · 07-08-2009, 09:13 PM

What's a .conkyrc?

Code:

root@silas64:~# find / -iname '.conkyrc' 2>/dev/null
root@silas64:~#

I've edited /etc/slackware-version over the years and never had a problem.

Code:

mingdao@silas64:~$ cat /etc/slackware-version
Slackware-x86_64 13.0

Sure would like to see that in a Slackware monitor.

manwichmakesameal · 07-08-2009, 10:18 PM

Conky is a system monitor. Here.

Bruce Hill · 07-08-2009, 10:25 PM

I'm waiting for the transparent theme to work with GKrellM
on KDE4 in Slackware-x86_64. It works with Fluxbox, but
not with KDE 4.2.4. Too much KDE makes my CPU(s) sick.

Bruce Hill · 07-09-2009, 05:04 AM

@ SqdnGuns

I can now tell you from experience that changing /etc/slackware-version
is okay, even with a ~/.conkyrc. After previous posts, and seeing your
post about conky and the screenshot, I decided to build it. So I got the
latest source, conky-1.7.1.1, hacked me up a conky.SlackBuild, edited to
get rid of the Lua language, built, and installed it.

Now I've got to get me a ~/.conkyrc to suit my tastes, but otherwise the
output from /etc/slackware-version is fine however you write it.

And you can forget about my previous request for the superkarmba thing.
Thanks for the conky.

gnashley · 07-09-2009, 11:56 AM

cd /etc ; grep -nrH slackware-version *
should tell you if any init or config files try to read the file.

dive · 07-09-2009, 12:27 PM

I've changed slackware-version manually after an upgrade. No problems at all that I've noticed.

Hope this helps.

SqdnGuns · 07-09-2009, 01:48 PM

Thanks all............I feel at ease now. Off to find something else to break.

@ Bruce, I have actually taken a look at converting my previous Karamba to a Plasmoid, decided I am too lazy for now to do it.

Bruce Hill · 07-09-2009, 04:40 PM

While editing ~/.conkyrc to my tastes, something strange happened. To get
conky transparent, I put

Code:

sleep 1 && fbsetbg ~/Libby-brown-hat.jpg &

into ~/.xinitrc and reloaded X. GKrellM had never been stopped, and that
command made it transparent, also.

However, for both apps, the background and the desktop image are slightly
askew. Is that the proper English word? Studying Chinese has ruined by
Redneck English dialect. Here's a screenshot.

Has anyone else experienced that? SqdnGuns screenshot doesn't seem to have
that issue. I'm running Slackware-x86_64 -current (July 1) with the generic
2.6.29.5 kernel, KDE 4.2.4., Conky 1.7.1.1.

My ~/.conkyrc has "update_interval 1" but the seconds on the clock and all
the other updates only happen every 7 seconds atm. At first it was better,
and has changed with subsequent restarts. I started with SqdnGuns .conkyrc
and have edited it.

Starting conky in a term, then killing it with Ctrl+C, yields this:

Code:

mingdao@silas64:~$ conky
Conky: desktop window (1c0002f) is subwindow of root window (1a7)
Conky: window type - normal
Conky: drawing to created window (0x4400001)
Conky: drawing to double buffer
^CConky: received SIGINT or SIGTERM to terminate. bye!