LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
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 03-16-2011, 01:47 PM   #1
Skaperen
Senior Member
 
Registered: May 2009
Location: WV, USA
Distribution: Slackware, CentOS, Ubuntu, Fedora, Timesys, Linux From Scratch
Posts: 1,777
Blog Entries: 20

Rep: Reputation: 115Reputation: 115
Rethinking the description during install?


Back in the days of slow machines, displaying the package description during an install provided for some reading to break up the boredom (if one was inspired to sit there and watch it do the install). Now days, the descriptions just fly by, several a second most of the time (unless doing things manually).

Do we really need this anymore? It's unreadable.

I'd rather see a list of packages being installed scroll by, one package name per line (with size info). Even that might get hard to read during the buzz of small packages being installed causing rapid scrolls.
 
Click here to see the post LQ members have rated as the most helpful post in this thread.
Old 03-16-2011, 02:12 PM   #2
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 875

Rep: Reputation: 1816Reputation: 1816Reputation: 1816Reputation: 1816Reputation: 1816Reputation: 1816Reputation: 1816Reputation: 1816Reputation: 1816Reputation: 1816Reputation: 1816
Hasn't it been fun to see the speed increase over the years?
 
5 members found this post helpful.
Old 03-16-2011, 02:15 PM   #3
szboardstretcher
Senior Member
 
Registered: Aug 2006
Location: Detroit, MI
Distribution: GNU/Linux systemd
Posts: 3,274
Blog Entries: 1

Rep: Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056Reputation: 1056
Quote:
Originally Posted by volkerdi View Post
Hasn't it been fun to see the speed increase over the years?
Yes it has.

I agree that the packages fly by too quickly to be read anymore. Perhaps a slideshow of some sort would be better utilized in the installation.

I remember typing 'dir' on the old 8088 and having a 20 file directory go by slowly enough to read it.
 
Old 03-16-2011, 03:16 PM   #4
Skaperen
Senior Member
 
Registered: May 2009
Location: WV, USA
Distribution: Slackware, CentOS, Ubuntu, Fedora, Timesys, Linux From Scratch
Posts: 1,777
Blog Entries: 20

Original Poster
Rep: Reputation: 115Reputation: 115
I don't know that a slideshow would be the Slackware way. A scrolling list of packages, in text mode, of course, seems right to me. Well, if you can make a text slideshow, then maybe.
 
2 members found this post helpful.
Old 03-16-2011, 03:24 PM   #5
marafa
LQ Newbie
 
Registered: Sep 2008
Posts: 26

Rep: Reputation: 1
Quote:
Originally Posted by Skaperen View Post
Back in the days of slow machines, displaying the package description during an install provided for some reading to break up the boredom (if one was inspired to sit there and watch it do the install). Now days, the descriptions just fly by, several a second most of the time (unless doing things manually).

Do we really need this anymore? It's unreadable.

I'd rather see a list of packages being installed scroll by, one package name per line (with size info). Even that might get hard to read during the buzz of small packages being installed causing rapid scrolls.
skaperen you may have a point but then again. i know some ppl who install from media or worse over a 512kb dsl line that doesnt get its full advertised speed.

and to volkerding - slackware 2 with a 100 diskettes (download, format floppy, copy to floppy, start install, insert requested floppy, remove floppy for next requested floppy) was too much for me - maybe i will revisit slackware soon but still my hat is off to you
 
Old 03-16-2011, 04:06 PM   #6
Skaperen
Senior Member
 
Registered: May 2009
Location: WV, USA
Distribution: Slackware, CentOS, Ubuntu, Fedora, Timesys, Linux From Scratch
Posts: 1,777
Blog Entries: 20

Original Poster
Rep: Reputation: 115Reputation: 115
Quote:
Originally Posted by marafa View Post
slackware 2 with a 100 diskettes (download, format floppy, copy to floppy, start install, insert requested floppy, remove floppy for next requested floppy) was too much for me - maybe i will revisit slackware soon but still my hat is off to you
I remember those days But I don't think it was quite 100 diskettes. More like 80.
 
Old 03-16-2011, 04:29 PM   #7
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,592
Blog Entries: 2

Rep: Reputation: 4047Reputation: 4047Reputation: 4047Reputation: 4047Reputation: 4047Reputation: 4047Reputation: 4047Reputation: 4047Reputation: 4047Reputation: 4047Reputation: 4047
Quote:
Originally Posted by Skaperen View Post
Well, if you can make a text slideshow, then maybe.
LOL, maybe some ASCII art.
 
Old 03-16-2011, 10:14 PM   #8
sahko
Senior Member
 
Registered: Sep 2008
Distribution: Slackware
Posts: 1,041

Rep: Reputation: Disabled
I agree with Skaperen. In my own packages i use 3-lined slack-desc's.
1 for package description, 1 blank, 1 for homepage of the application.

The rest is a waste of time and space, writing, maintaining, scrolling and in any way dealing with. Thanks for bringing this up.

edit: Although i have to admit, some of them are actually educational.

Last edited by sahko; 03-16-2011 at 10:16 PM.
 
Old 03-17-2011, 06:15 AM   #9
fskmh
Member
 
Registered: Jun 2002
Location: South Africa
Distribution: Slackware64-current multilib
Posts: 235

Rep: Reputation: 55
The short duration with which the messages are displayed may lessen their value during installation, but their utility after installation is undeniable because:
a) You can simply less /var/log/packages/pkgnam-blah-blah to get a description. (If it's a Slack dist package you can also see what "diskset" it came from.)
b) AFAIK gslapt displays this info when you click on a package.
c) The pkgnam-blah-blah.txt file is generated from slack-desc when the package is made, and this text file is very useful for reading about a package that you might be unfamiliar with before downloading it.
d) Some of the seemingly dated wisdom that went into the design of Slackware is timeless and can potentially save your butt when unanticipated problems arise.
 
3 members found this post helpful.
Old 03-17-2011, 08:42 AM   #10
Skaperen
Senior Member
 
Registered: May 2009
Location: WV, USA
Distribution: Slackware, CentOS, Ubuntu, Fedora, Timesys, Linux From Scratch
Posts: 1,777
Blog Entries: 20

Original Poster
Rep: Reputation: 115Reputation: 115
I'm not against having descriptions somewhere. I just don't see the need to having the screen flashing a bunch of different sized blocks real fast. OTOH, it can make me look like Mr. Data if I stare at this when people walk by
 
Old 03-17-2011, 04:58 PM   #11
Wed
Member
 
Registered: Sep 2005
Location: Sweden
Distribution: Slackware
Posts: 147

Rep: Reputation: 26
Isn't it actually even worse?

During a system install from scratch, and browsing packages in the categories list, the description doesn't fit on the screen and thus unreadable. While installing, the descriptions flash by quicker than readable.

If installing manually, the package is already installed when you can see the description. You must have opted to install the package before the description is visible.

The only package descriptions I have ever read to the full extent, are those on slackbuilds.org.

My preference for system install, would be to see the package names scroll by. If anything catches the eye, there are some second to focus before it escapes off the screen.
 
Old 03-17-2011, 05:12 PM   #12
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,267

Rep: Reputation: 652Reputation: 652Reputation: 652Reputation: 652Reputation: 652Reputation: 652
Or perhaps a persistent indication of the current package set being installed in the title bar of each installing package dialog so you can have an idea of the actual progress at a glance without having to memorize which packages are in each package set...
 
Old 03-17-2011, 05:17 PM   #13
lumak
Member
 
Registered: Aug 2008
Location: Phoenix
Distribution: Arch
Posts: 799
Blog Entries: 32

Rep: Reputation: 109Reputation: 109
Lets add a toggle option!

Hrmmms perhaps write to a fifo buffer the list of packages processed and display that in one mode while displaying the descriptions in the other mode?
 
Old 03-18-2011, 08:10 AM   #14
Skaperen
Senior Member
 
Registered: May 2009
Location: WV, USA
Distribution: Slackware, CentOS, Ubuntu, Fedora, Timesys, Linux From Scratch
Posts: 1,777
Blog Entries: 20

Original Poster
Rep: Reputation: 115Reputation: 115
I was installing slackware64-current last night, within qemu in 64-bit emulation, on a 32-bit system. I could read the descriptions!
 
Old 03-18-2011, 09:39 AM   #15
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,465

Rep: Reputation: 852Reputation: 852Reputation: 852Reputation: 852Reputation: 852Reputation: 852Reputation: 852
You can always modify the installer.
Dump the -infobox option to installpkg and add an echo for the $package variable.
Do not try to be too cute as this runs in BusyBox.
Code:
installseries() {
  if [ -d $SRCPATH/$1 ]; then
    # First, make sure our tagfiles are in order:
    if [ ! -r $TMP/tagfiles/$1/tagfile -a ! $MODE = full ]; then
      updatetagfiles $1
    fi
    # First, make sure there's at least one package:
    if ! ls $SRCPATH/$series/*.t?z 1> /dev/null 2> /dev/null ; then
      return 1
    fi
    dialog --infobox "
Installing package series ==>$1<==
" 5 45
    sleep 1
    # Install the package series:
    for package in $SRCPATH/$series/*.t?z ; do
      [ "x$REMOTESVR" != "x" ] && get_pkg $series $(basename $package) '-q'
      if [ "$MODE" = "full" ]; then # install the package
        installpkg -root $ROOTDIR -infobox -priority ADD $package
        ERROR=$?
      else
        installpkg -root $ROOTDIR -menu -tagfile $TMP/tagfiles/$1/tagfile $package
        ERROR=$?
      fi
      if [ ! $ERROR = 0 ]; then
        errorcode $ERROR $package
      fi
      [ "x$REMOTESVR" != "x" ] && zap_pkg $series $(basename $package)
    done
    # A "README_SPLIT.TXT" file means the series continues on another CD:
    if [ -r $SRCPATH/$series/README_SPLIT.TXT -o -r $SRCPATH/$series/readme_split.txt ] ; then
      # Defer until later.
      echo $1 >> $TMP/series/series.out
    fi
  else # requested, but not on media.  defer until later.
    echo $1 >> $TMP/series/series.out
  fi 
}
From /usr/lib/setup/slackinstall in the 13.1 initrd.img
 
  


Reply


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
LXer: Rethinking the Open Desktop LXer Syndicated Linux News 0 11-09-2010 03:11 PM
LXer: Rethinking Emphathy in Ubuntu 9.10 LXer Syndicated Linux News 0 08-25-2009 04:10 AM
LXer: Drizzle: Rethinking the MySQL Database Kernel LXer Syndicated Linux News 0 06-17-2009 01:20 AM
LXer: Linux: Rethinking Suspend and Resume LXer Syndicated Linux News 0 05-26-2007 06:02 PM
LXer: Rethinking Community Documentation LXer Syndicated Linux News 0 07-07-2006 07:03 PM


All times are GMT -5. The time now is 08:36 PM.

Main Menu
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