SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Src2pkg sounds somewhat similar to checkinstall. Checkinstall was made because of too many source packages with make-target 'install' but no 'uninstall'.
It makes dpkg-packages from the sources and installs them instead.
I've run into source packages a couple of times: eclipse - Mint 13 had indigo, I've been using kepler, and qemu (neither version worked: the Mint 13 default, nor 1.5). Another was Canon printer driver and still another was (some years ago) Ralink wifi driver for debian.
Since src2pkg started with Slackware support, has always been reliably maintained, the maintainer is an active poster here, and numerous senior members recommend it. So whilst I actually don't use it myself, this is the program I generally suggest others to use.
Another option would be slacktrack. This is a much simpler program than src2pkg but it has the nice advantage that it comes prebundled with Slackware. Indeed it was written by the Slackware ARM maintainer.
Last edited by ruario; 07-02-2014 at 12:30 AM.
Reason: This forum uses BBCode not HTML, you would think I would remember that.
Yeah, src2pkg creates proper Slackware packages, doesn't "obfuscate" anything, and it comes with plenty of documentation, and gnashley is one of the most helpful members on LQ. Get it.
Excellent! Thanks!
So basically, with src2pkg (and presumably with deb2pkg?) it makes a real Slackware package, and you then just install them with installpkg?
Awww, C'mon.....sounds too easy!
(I asked about the /var/log stuff, because, thankfully, in other threads, others have hammered-home the importance of doing package management the "right way"- and I guess it sunk-in...)
Excellent! Thanks!
So basically, with src2pkg (and presumably with deb2pkg?) it makes a real Slackware package, and you then just install them with installpkg?
Yep. That's it. When you first install src2pkg you will be prompted to set it it up by running
# src2pkg --setup
After that you can create Slackware packages with:
bash-4.2# slackpkg search wicd
Looking for wicd in package list. Please wait... DONE
The list below shows all packages with name matching "wicd".
[ installed ] - wicd-kde-0.3.0_bcf27d8-i486-1
[uninstalled] - wicd-1.7.2.4-i486-4
Where should I find wicd (wicd-kde)?
In the network configuration I selected Network Manager.
...
This is what iwlist says - even when the connection is lost:
(Aha, it seems to select AES instead of TKIP - doesn't matter.)'
Code:
bash-4.2# iwlist scanning
irda0 Interface doesn't support scanning.
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
eth1 Scan completed :
Cell 01 - Address: 00:1D:73:73:88:EA
ESSID:"kotiverkko-G-AES"
Protocol:IEEE 802.11bg
Mode:Master
Frequency:2.437 GHz (Channel 6)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 11 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=80/100 Signal level=-49 dBm
IE: WPA Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Extra: Last beacon: 55ms ago
Could it be that Network Manager dislikes TKIP? Now with AES it seems to work. (Knocking wood...) I managed to get wicd-package downloaded, but I haven't installed it yet - hopefully I don't have to.
I guess src2pkg might be nice with something like OpenOCD
Checked also eclipse and qemu - looks good. There should be Eclipse Luna available (SBo) already.
Now that everything looks suspiciously good, should I change to some lighter DE?
Now I have Pentium M running KDE with 1GB RAM.
The system feels a bit - but not irritatingly - slow.
Now I have Pentium M running KDE with 1GB RAM.
The system feels a bit - but not irritatingly - slow.
You may wish to give XFCE a try. XFCE is a nice environment that has a fair number of bells and whistles; XFCE runs lighter than KDE. I've been running XFCE for several years and like it a lot.
You may wish to give XFCE a try. XFCE is a nice environment that has a fair number of bells and whistles; XFCE runs lighter than KDE. I've been running XFCE for several years and like it a lot.
I second that!
The OP's 'puter with Slackware will fly with XFCE- They say XFCE is almost as light as the lightweight WMs, like Fluxbox/Openbox.
If you really want something light use a simple window manager like Fluxbox. I happily run KDE on my main laptop, however I also own an old eeePC 4G Surf (4GS-PK008), with only 512 MB RAM (and just 4 GB of disk space!). On this I use Fluxbox and Opera (12.16) as my browser. It works very nicely.
One of the advantages of XFCE for a newcomer to Slackware [speaking from my own experience!] is that it lists pretty much all the available apps in it's menu- even the K-applications- whereas with the lightweight WMs, the menus are pretty sparse, and you have to know what you have and manually add what you want. That's why I'm presently using XFCE- I've intended since day-one to switch to Fluxbos or install Openbox, once I got my feet wet....but to tell you the truth, XFCE has been working just as well on my old stuff. (A while back I read somewhere that in a side-by-side test, XFCE was actually found to use as little or less resources than Openbox. Now I tend to believe it)
Well, the machine didn't fly - not far at least. :-)
Due to network problems with xfce, I decided to reinstall the whole. I think my mistake was to select DHCP instead of Network Manager in the first install. Still using XFCE the "network connections" don't find my IF and wpa_gui can't connect to wpa_supplicant. Network Manager applet, however, works fine.
When you decide to switch to something minimalist like fluxbox, give some consideration to i3, a tiling window manager now available through slackbuilds/sbopkg. No eye candy but maximizes your workspace without much effort, and is especially useful for small screens (laptops) and big screens if you multitask a lot.
Having said that, xfce is a great desktop environment, if your preference lies there.
Well, the machine didn't fly - not far at least. :-)
Due to network problems with xfce, I decided to reinstall the whole. I think my mistake was to select DHCP instead of Network Manager in the first install. Still using XFCE the "network connections" don't find my IF and wpa_gui can't connect to wpa_supplicant. Network Manager applet, however, works fine.
Took an evening, but now things look better.
If you don't have a static IP address, you NEED to set up DHCP. XFCE has the network manager built-in....so I'm not sure what's going with your sytem, but I doubt that it's a DHCP or network manager problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
