LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 02-28-2009, 09:01 PM   #391
GazL
Senior Member
 
Registered: May 2008
Posts: 3,502

Rep: Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024Reputation: 1024

Quote:
Originally Posted by mRgOBLIN View Post
sissies :P
Yeah, real men edit files by hand-crafting diff listings on the stdin of patch!
 
Old 02-28-2009, 10:51 PM   #392
tuxdev
Senior Member
 
Registered: Jul 2005
Distribution: Slackware
Posts: 2,014

Rep: Reputation: 115Reputation: 115
Hey, we can't have a proper editor war without mentioning ed (modernized slightly):
Quote:
Of course, on the system *I* administrate, vi is symlinked to ed.
Emacs has been replaced by a shell script which 1) Generates a syslog
message at level LOG_EMERG; 2) reduces the user's disk quota by 100M;
and 3) RUNS ED!!!!!!

"Ed is the standard text editor."
 
Old 03-01-2009, 01:33 AM   #393
sahko
Senior Member
 
Registered: Sep 2008
Distribution: Slackware
Posts: 1,041

Rep: Reputation: Disabled
What i would like is zsh to support regexp by enabling pcre in configure.
I sent an email already asking for this. I think its a much desired feature for zsh users.
 
Old 03-01-2009, 04:28 AM   #394
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 7,135
Blog Entries: 52

Rep: Reputation: Disabled
When are they going to fix that bug in Vim? The one where when you want to type h, j, k, or l, the cursor starts jumping about all over the place.
 
Old 03-01-2009, 04:53 AM   #395
arubin
Senior Member
 
Registered: Mar 2004
Location: Middx UK
Distribution: Slackware64 14.1 (multilib)
Posts: 1,210

Rep: Reputation: 55
I would like to see automated clearing of some of the junk that accumulates in /tmp
 
Old 03-01-2009, 04:56 AM   #396
DragonM15
Member
 
Registered: Sep 2003
Location: USA
Distribution: Slackware (Multiple Versions)
Posts: 455

Rep: Reputation: 31
Quote:
Originally Posted by Jeebizz View Post
I honestly can't tell the difference between nano and pico though.
Me either... Although I will say it drives me insane when I get on a linux box that doesnt have pico, but has nano instead.. i am still in the habit of typing pico....
 
Old 03-01-2009, 04:58 AM   #397
DragonM15
Member
 
Registered: Sep 2003
Location: USA
Distribution: Slackware (Multiple Versions)
Posts: 455

Rep: Reputation: 31
Quote:
Originally Posted by arubin View Post
I would like to see automated clearing of some of the junk that accumulates in /tmp
I would like to see this as well. It stacks up fairly quick.
 
Old 03-01-2009, 05:12 AM   #398
Toods
Member
 
Registered: Dec 2005
Location: UK
Distribution: Slackware 12.1
Posts: 249

Rep: Reputation: 32
Quote:
Originally Posted by DragonM15 View Post
I would like to see this as well. It stacks up fairly quick.
Yes, I didn't like how things gradually accumulated in '/tmp'. What I did to overcome it for me was to make sure that the '/tmp' directory was created essentially on a 'ramdrive' by putting the following line in '/etc/fstab':

Code:
tmpfs            /tmp             tmpfs       defaults         0   0
Never ran into any problems at all with it and still use in my 2 Slackware 12.1 installations.

Bill.
 
Old 03-01-2009, 05:15 AM   #399
DragonM15
Member
 
Registered: Sep 2003
Location: USA
Distribution: Slackware (Multiple Versions)
Posts: 455

Rep: Reputation: 31
Quote:
Originally Posted by Toods View Post
Yes, I didn't like how things gradually accumulated in '/tmp'. What I did to overcome it for me was to make sure that the '/tmp' directory was created essentially on a 'ramdrive' by putting the following line in '/etc/fstab':

Code:
tmpfs            /tmp             tmpfs       defaults         0   0
Never ran into any problems at all with it and still use in my 2 Slackware 12.1 installations.

Bill.
Thanks for the advice, I never really thought of doing that.
 
Old 03-01-2009, 05:20 AM   #400
Toods
Member
 
Registered: Dec 2005
Location: UK
Distribution: Slackware 12.1
Posts: 249

Rep: Reputation: 32
I also configure my Firefox to have it's disk cache in '/tmp' by having the following line in 'user.js':

Code:
user_pref("browser.cache.disk.parent_directory", "/tmp");
Less hard drive activity then when browsing.

Bill.
 
Old 03-01-2009, 05:23 AM   #401
DragonM15
Member
 
Registered: Sep 2003
Location: USA
Distribution: Slackware (Multiple Versions)
Posts: 455

Rep: Reputation: 31
Quote:
Originally Posted by Toods View Post
I also configure my Firefox to have it's disk cache in '/tmp' by having the following line in 'user.js':

Code:
user_pref("browser.cache.disk.parent_directory", "/tmp");
Less hard drive activity then when browsing.

Bill.
I wonder if that would speed things up on an old laptop I have been playing with. Flash pages in particular. I know flash is rather CPU intensive, but I might have to test it out.
 
Old 03-01-2009, 07:23 AM   #402
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,517

Rep: Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873Reputation: 873
Quote:
I honestly can't tell the difference between nano and pico though.
I can, nano has search and replace!

More seriously,
I would like to see an update of UPGRADE.TXT that includes a warning at step 3 that the little script will install all the kernels in slackware/a and not just the kernel currently in use. This can have the unintended consequence of installing a -smp kernel on hardware that does not support it, leading to an unbootable system.

Also, now that slackpkg is part of the official release, I think that the instructions in UPGRADE.TXT could include the alternative of using slackpkg to perform the upgrade.
i.e Step 3 - Edit /etc/slackpkg/mirrors and change mirror to cdrom://root/slackware. Edit /etc/slackpkg/blacklist to exclude unwanted kernels and kernel-modules as well as kdei. Then
'slackpkg install-new'
'slackpkg upgrade-all'

Step 4 - slackpkg currently prompts you to run lilo after a kernel upgrade, but it would be nice if slackpkg could recognise the presence of a kernel using an initrd and offer to do mkinitrd as well.

Step 5 - 'slackpkg clean-system'

Step 6 - slackpkg already searches for .new files in /etc and prompts for what you want to do.

Last edited by allend; 03-01-2009 at 07:25 AM.
 
Old 03-01-2009, 09:30 AM   #403
shadowsnipes
Senior Member
 
Registered: Sep 2005
Distribution: Slackware
Posts: 1,442

Original Poster
Rep: Reputation: 70
Quote:
Originally Posted by bergman View Post
Id like to see fsck moved from boot, to something which executes upon shutown (if its possible).

It only happens once every 30 boots, but its the most annoying thing when your in a hurry.
You can easily edit the boot scripts yourself to do this.
Also, man tune2fs

Quote:
Originally Posted by Jeebizz View Post
I honestly can't tell the difference between nano and pico though.
nano is not tied to pine and has syntax highlighting, smooth scrolling, regex search and replace, and uses meta keys to toggle behavior. I particularly appreciate the syntax highlighting, but you have to edit /etc/nanorc (or users nanorc) to activate it. I mostly use it to edit scripts, and since not all shell scripts end in ".sh", I use an alias called "snano" which is equivalent to 'nano -Y sh'.

Quote:
Originally Posted by allend View Post
More seriously,
I would like to see an update of UPGRADE.TXT that includes a warning at step 3 that the little script will install all the kernels in slackware/a and not just the kernel currently in use. This can have the unintended consequence of installing a -smp kernel on hardware that does not support it, leading to an unbootable system.
That seems reasonable. A lot of people don't realize that the last one installed will be your default kernel.

Quote:
Originally Posted by allend View Post
Also, now that slackpkg is part of the official release, I think that the instructions in UPGRADE.TXT could include the alternative of using slackpkg to perform the upgrade.
i.e Step 3 - Edit /etc/slackpkg/mirrors and change mirror to cdrom://root/slackware. Edit /etc/slackpkg/blacklist to exclude unwanted kernels and kernel-modules as well as kdei. Then
'slackpkg install-new'
'slackpkg upgrade-all'

Step 4 - slackpkg currently prompts you to run lilo after a kernel upgrade, but it would be nice if slackpkg could recognise the presence of a kernel using an initrd and offer to do mkinitrd as well.

Step 5 - 'slackpkg clean-system'

Step 6 - slackpkg already searches for .new files in /etc and prompts for what you want to do.
For now Slackware users can refer to my HowTos for this information (see my signature). I will try to do a new HowTo for each release as I am able.
 
Old 03-02-2009, 03:46 PM   #404
business_kid
Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 6,610

Rep: Reputation: 583Reputation: 583Reputation: 583Reputation: 583Reputation: 583Reputation: 583
If I install kde, I just watch an hourglass for five seconds every time I want to do something. I have an Athlon XP 2.6Ghz w/1Gig ram, which is not slow. Is kde all bash scripts or something?

I would like:

1. a well tuned alternative to high cholesterol window managers. Tune up XFCE, and preferably drop kde and grab gnome.

2. PACKAGE MANAGEMENT. If work was put into the /usr/lib/pkgconfig requirements lists they could be checked. There should be a very simple script to do that. Explode a package somewhere, cd to the binaries and run
for files in i do;
ldd $i |grep found

and your output is the missing libs. One could work the dependencies out quickly. Also, much of the actual dependency is already done and displayed on the relevant page from the linuxfromscratch books. You have the failed compiles of LFSers to thank for that.

3. Line up your kernel with wine. I had to rebuild to get some programs working (Internal Program information stuff not enabled IIRC)

4. You make these halfassed binary and library directories (e.g. /usr/share/texmf/bin) and add them to the $PATH, but rarely add the libraries to LD_LIBRARY_PATH. The result is My system can only find half the libraries it has.
 
Old 03-02-2009, 04:06 PM   #405
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,944

Rep: Reputation: Disabled
This thread gets more absurd every day...

Quote:
Originally Posted by business_kid View Post
I would like:

1. a well tuned alternative to high cholesterol window managers. Tune up XFCE, and preferably drop kde and grab gnome.
Xfce is available already. Removing an easily maintained and well-liked choice seems dumb.

Quote:
2. PACKAGE MANAGEMENT. If work was put into the /usr/lib/pkgconfig requirements lists they could be checked. There should be a very simple script to do that.
If you'd ever tried to do that, you'd know that you're wrong.
More importantly, what you're wanting is antithetical to Slackware philosophy at this point in time.

Quote:
3. Line up your kernel with wine. I had to rebuild to get some programs working (Internal Program information stuff not enabled IIRC)
You want a distribution to build its kernel based on what *wine* needs? You're kidding, right?

On a serious note, if there are kernel options that can be added to Slackware's kernel which *help* with wine *and* don't cause other issues, then feel free to recommend them here. However, a vague statement like what's above isn't good enough.

Quote:
4. You make these halfassed binary and library directories (e.g. /usr/share/texmf/bin) and add them to the $PATH, but rarely add the libraries to LD_LIBRARY_PATH. The result is My system can only find half the libraries it has.
Give me an example - I think you've got a case of mistaken cause/effect relationship.
 
  


Reply

Tags
cd, live


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Slackware future? coyctecm Slackware 12 02-01-2006 11:03 PM
Future of Slackware kratunko Slackware 30 08-12-2005 01:31 PM
Slackware features? rusty_slacker Slackware 49 12-02-2004 05:45 AM
what are the features of the new slackware 9? ethanchic Slackware 2 09-27-2002 07:15 PM


All times are GMT -5. The time now is 08:26 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration