LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
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 11-24-2010, 11:16 AM   #31
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,197
Blog Entries: 3

Rep: Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425

Hi,

I use both fdisk & cfdisk. You can get the blocks assigned when setting up a fresh install. Part of my documentation for a new install. Plus for cfdisk being curses based and as a plus you get the total applied size for the partition(s).

Original block size is convenient to have on hand if you do have problems later if you need recovery. Just a habit.
 
Old 11-24-2010, 11:39 AM   #32
neymac
Member
 
Registered: May 2009
Distribution: Slackware64-14.0
Posts: 117

Rep: Reputation: 13
Back to top (wrong link)

Quote:
Originally Posted by 2handband View Post
The new desktop setup page is up for KDE 4.5.3 on Slackware -current.

http://genek.net/LinuxAdventures/ins.../desktop1.html
Both link at the bottom of the page:
"Back to Top"
and
"Back to Desktops Index"
send us to the http://genek.net/LinuxAdventures/ins...p/desktop.html
Should correct the first one.
(I think just missed the "1" at the link's end)

Last edited by neymac; 11-24-2010 at 11:41 AM.
 
Old 11-24-2010, 08:37 PM   #33
2handband
Member
 
Registered: Jan 2009
Location: Alexandria, Minnesota
Distribution: Slackware 13.1
Posts: 809

Original Poster
Rep: Reputation: 96
Quote:
Originally Posted by neymac View Post
Both link at the bottom of the page:
"Back to Top"
and
"Back to Desktops Index"
send us to the http://genek.net/LinuxAdventures/ins...p/desktop.html
Should correct the first one.
(I think just missed the "1" at the link's end)
Oops... fixed. Thanks!
 
Old 11-25-2010, 07:46 AM   #34
2handband
Member
 
Registered: Jan 2009
Location: Alexandria, Minnesota
Distribution: Slackware 13.1
Posts: 809

Original Poster
Rep: Reputation: 96
I added a section to the KDE 4.5.3 desktop setup page; a quick orientation on some of the software that comes with a basic Slack installation. The next lesson will be on software management.

http://genek.net/LinuxAdventures/ins.../desktop1.html
 
Old 11-27-2010, 10:00 AM   #35
2handband
Member
 
Registered: Jan 2009
Location: Alexandria, Minnesota
Distribution: Slackware 13.1
Posts: 809

Original Poster
Rep: Reputation: 96
I just added a lengthy tutorial on Slackware package management. I'm bound to have screwed something up or left something important out; please correct me where I err.

http://genek.net/LinuxAdventures/sysadmin/slackpkg.html

Thanks to all who commented on the other three tutorials. They're much better thanks to your suggestions.
 
Old 11-27-2010, 10:12 AM   #36
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,257

Rep: Reputation: Disabled
Quote:
Originally Posted by 2handband View Post
I just added a lengthy tutorial on Slackware package management. I'm bound to have screwed something up or left something important out; please correct me where I err.

http://genek.net/LinuxAdventures/sysadmin/slackpkg.html

Thanks to all who commented on the other three tutorials. They're much better thanks to your suggestions.
Ermmm.... in the section about my packages, you write "His packages come in the form of pre-compiled binaries, and for that reason alone I use the Slackbuilds.org repo over his when I can... I want that build script!".

Have you ever looked inside the "build" directory of any of my packages? You'll find everything you need to build that package - SlackBuild script, slack-desc file, all sources and patches!

Eric
 
Old 11-27-2010, 10:19 AM   #37
2handband
Member
 
Registered: Jan 2009
Location: Alexandria, Minnesota
Distribution: Slackware 13.1
Posts: 809

Original Poster
Rep: Reputation: 96
Quote:
Originally Posted by Alien Bob View Post
Ermmm.... in the section about my packages, you write "His packages come in the form of pre-compiled binaries, and for that reason alone I use the Slackbuilds.org repo over his when I can... I want that build script!".

Have you ever looked inside the "build" directory of any of my packages? You'll find everything you need to build that package - SlackBuild script, slack-desc file, all sources and patches!

Eric

Oops, sorry... will revise at once!
 
Old 11-27-2010, 10:29 AM   #38
2handband
Member
 
Registered: Jan 2009
Location: Alexandria, Minnesota
Distribution: Slackware 13.1
Posts: 809

Original Poster
Rep: Reputation: 96
Okay, fixed. My deepest apologies, Eric... I simply never noticed that was there before. I've always had good luck with your stuff, particuarly your excellent KDE packages. At least you caught that within a few minutes of upload!
 
Old 11-27-2010, 12:15 PM   #39
2handband
Member
 
Registered: Jan 2009
Location: Alexandria, Minnesota
Distribution: Slackware 13.1
Posts: 809

Original Poster
Rep: Reputation: 96
Just discovered and corrected a gross error in my discussion of the slackware source tree... i somehow identified the doinst.sh file as the source code! Never write under the influence...
 
Old 11-28-2010, 07:26 AM   #40
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,197
Blog Entries: 3

Rep: Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425
Hi,

I would add that Slackware has always had package management: 'pkgtool' comes with the install and is used for maintenance of the install. 'pkgtool' is still in use and useful to maintain the system. How do you think the Slackware system initial install is done? Surely not from the curses menu for the initial install!

Quote:
excerpt 'man pkgtool';
pkgtool - software package maintenance tool.

SYNOPSIS
pkgtool

pkgtool [ --sets #a#b#c# ] [ --source_mounted ] [ --ignore_tagfiles ] [
--tagfile tagfile ] [ --source_dir directory ] [ --target_dir directory ] [
--source_device device ]

DESCRIPTION
pkgtool is a menu-driven package maintenance tool provided with the Slackware
Linux distribution. It allows the user to install, remove, or view software
packages through an interactive system. Pkgtool can also be used to re-run
the menu-driven scripts normally executed at the end of a Slackware installa-
tion. This is useful for doing basic reconfiguration (like changing the
mouse type).
OPTIONS
Most users will not want to use any options when running pkgtool. These are
generally used only when pkgtool is run during the initial system installa-
tion. Feel free to try them, but be careful.

--sets #A#B#C#
Install the disk sets A, B, C. Seperate the disk set names by '#' sym-
bols.

--source_mounted
When this flag is present, pkgtool will not attempt to unmount and
remount the source device with each disk.

--ignore_tagfiles
When this flag is present, pkgtool will install every package encoun-
tered no matter what the tagfiles say.

--tagfile tagfile
This flag is used to specify from the command line which tagfile
should be used for the installation.

--source_dir directory
Used when installing multiple packages from disk sets. This is the
directory in which the subdirectories for each disk are found. This
isn't used when installing from floppy.
--target_dir directory
The directory where the target root directory is located. This is '/'
when installing on the hard drive, or typically '/mnt' when installing
from an install disk.

--source_device device
The source device to install from. This is not used if you've provided
the --source_mounted flag. It's usually used when installing from
floppy, as in:
--source_device /dev/fd0u1440 or
--source_device /dev/fd1h1200.

AUTHOR
Patrick J. Volkerding <volkerdi@slackware.com>

SEE ALSO
makepkg(8), explodepkg(8), installpkg(8), removepkg(8), upgradepkg(8)
Quote:
In this tutorial I'll teach you to use Slackware's package management tools, and direct you to some places where you can get software for your Slackware machine.
'pkgtool' is a very valuable tool to be aware of and to utilize when maintaining the system, not an after thought. If you want to service or support something then present the information in a manner that will provide the user options and not opinionated.

I believe it would be useful to add this before slackpkg presentation as implication that pkgtool is a after thought. Slackpkg, sBopkg are tools that utilize and streamline the utilities of Slackware. I don't have a problem with your intentions but Slackware has always had a management tool and that is 'pkgtool'. Not 'slackpkg' or 'sbopkg' but the package tool or management is 'pkgtool'.

If your going to do it, then do it right. Don't forget makepkg, explodepkg, installpkg, removepkg, upgradepkg which are tools that the user should be aware of when doing maintenance. A breif statement does no justice.You might look at 'SlackwareŽ Essentials (Slackbook) for some good examples.

If you want a slackpkg HOWTO then say so. 'slackpkg' is a good tool for the user to be aware of and to use properly then the user will be able to maintain with ease a Slackware system. But 'pkgtool' will always be the Slackware package management tool.
 
Old 11-28-2010, 07:42 AM   #41
diwljina
Member
 
Registered: Jun 2009
Distribution: Slackware, Debian
Posts: 105

Rep: Reputation: 8
Nice work, man. When I recommend Slack to someone I will definitely send them links with your tutorials.

BTW, I always thought that dependency hell is something you have to deal with when you use distro with package manager that uses automatic dependency resolution. Tried a few of them and it is HELL!
 
Old 11-28-2010, 07:44 AM   #42
2handband
Member
 
Registered: Jan 2009
Location: Alexandria, Minnesota
Distribution: Slackware 13.1
Posts: 809

Original Poster
Rep: Reputation: 96
@Onebuck: I'm planning a second package management tutorial to tie up loose ends. Things like explodepkg, removepkg, and so on will be covered there. The purpose of the first one was to get beginners installing software; don't forget that I'm making the assumption that the reader has zero knowledge of Linux! In my opinion that tutorial bordered on being too long as it is.

As for pkgtool, I've never found it to be all that handy; the commands are faster! Maybe my description of it was too much of a brush-off; I'll give that some thought. All the same, it IS very self-explanatory and doesn't bear a whole lot of explanation.

I may change the title; it's perhaps a bit misleading since the tutorial is not comprehensive (and is not intended to be). I'll give it some thought.

Thanks very much for taking the time to consider this and respond.
 
Old 11-28-2010, 08:14 AM   #43
2handband
Member
 
Registered: Jan 2009
Location: Alexandria, Minnesota
Distribution: Slackware 13.1
Posts: 809

Original Poster
Rep: Reputation: 96
BTW, I went through yesterday and made revisions to every page in the Applications section of the site; some of them major.
 
Old 11-28-2010, 09:26 AM   #44
Lufbery
Senior Member
 
Registered: Aug 2006
Location: Harrisburg, PA
Distribution: Slackware 64 14.0
Posts: 1,142
Blog Entries: 29

Rep: Reputation: 119Reputation: 119
Quote:
Originally Posted by brianL View Post
I've always used cfdisk, because I haven't got round to learning how to use fdisk yet.
I've always used nano, because I haven't got round to learning how to use vi\vim\elvis yet.
I've got a lot to learn...
*grin*

FWIW, I think Nano is a darned fine editor! I set it up in the temporary toolchain portion of my LFS build and then built it again when I was done with the full build.

If I had one editor I had to rely on, I'd use Emacs, but Nano is a close second and it's a heck of a lot smaller than Emacs and is nearly as good an editor.

Regards,
 
Old 11-28-2010, 10:40 AM   #45
2handband
Member
 
Registered: Jan 2009
Location: Alexandria, Minnesota
Distribution: Slackware 13.1
Posts: 809

Original Poster
Rep: Reputation: 96
Quote:
Originally Posted by diwljina View Post
Nice work, man. When I recommend Slack to someone I will definitely send them links with your tutorials.

BTW, I always thought that dependency hell is something you have to deal with when you use distro with package manager that uses automatic dependency resolution. Tried a few of them and it is HELL!
Well... I was a longtime Debian user before switching to Slack. Automatic dependency resolution works all right so long as you don't stray too far from the official repositories. It was when I started wanting to pick and choose software versions and heavily customize my system that automatic dependency resolution started to become a big problem.
 
  


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
-have read stickies and tutorials no no avail- configuring nvidia 8800gt cbruffin Linux - Newbie 20 03-10-2010 07:46 AM
Looking for GOOD tutorials on Slack 12.1 that would be nice for a newbie tribal_kid Linux - Newbie 2 08-15-2008 02:38 AM
suggestions for slack dns tutorials fazz Slackware - Installation 0 06-27-2004 05:10 AM
Configuring dail-up on slack the_rydster Linux - Newbie 1 02-16-2004 09:59 AM
Help configuring ALSA in Slack 9.1 dazzlehank Slackware 1 01-12-2004 04:22 PM


All times are GMT -5. The time now is 02:55 AM.

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