log by "alphabet" & installation process by "time created"?

Other talk about Salix
Post Reply
User avatar
zAchAry
Posts: 804
Joined: 11. May 2010, 09:02
Location: Israel

log by "alphabet" & installation process by "time created"?

Post by zAchAry »

I installed b43-fwcutter and b43-firmware packed by pwatk and all seem to be alright.

I'm researching (or at least trying to research) the log and I've noticed that a SLKBUILD is archived (at /usr/src/<name_of_package>/SLKBUILD) in the end of the installation, which is very god, and shows that the people that engineered Slackware are definitely (and for sure are) not stupid :P

I also bothered to look inside /var/log/packages:

Code: Select all

/var/log/packages/b43-fwcutter-013-i486-1pw

/var/log/packages/b43-firmware-4.178.10.4-fw-1pw
and wondered about the orders with the system (or just the following case)

from the installation of b43-fwcutter

Code: Select all

root[~]# cd build
root[build]# ls
slkbuild-b43-firmware  slkbuild-b43-fwcutter
root[build]# slkbuild -X slkbuild-b43-fwcutter
No SLKBUILD found in directory, see slkbuild --help
root[build]# ls
b43-firmware  b43-fwcutter
root[build]# cd b43-fwcutter
root[b43-fwcutter]# slkbuild -X SLKBUILD
Automatically setting arch to i486

Downloading b43-fwcutter-013.tar.bz2

--2010-08-22 10:18:49--  http://bu3sch.de/b43/fwcutter/b43-fwcutter-013.tar.bz2
Resolving bu3sch.de (bu3sch.de)... 80.190.117.144
Connecting to bu3sch.de (bu3sch.de)|80.190.117.144|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 15359 (15K) [application/x-bzip2]
Saving to: “b43-fwcutter-013.tar.bz2”

100%[======================================>] 15,359      65.8K/s   in 0.2s    

2010-08-22 10:18:50 (65.8 KB/s) - “b43-fwcutter-013.tar.bz2” saved [15359/15359]

build-b43-fwcutter.sh has been created
tar -xf b43-fwcutter-013.tar.bz2
     DEPEND   dep/md5.d
     DEPEND   dep/fwcutter.d
     CC       obj/fwcutter.o
fwcutter.c: In function ‘to_be16’:
fwcutter.c:76: warning: dereferencing type-punned pointer will break strict-aliasing rules
fwcutter.c: In function ‘to_be32’:
fwcutter.c:102: warning: dereferencing type-punned pointer will break strict-aliasing rules
     CC       obj/md5.o
     CC       b43-fwcutter
/home/etf/build/b43-fwcutter/pkg:
total 8
drwxr-xr-x 2 root root 4096 2010-08-22 10:18 install
drwxr-xr-x 6 root root 4096 2010-08-22 10:18 usr

/home/etf/build/b43-fwcutter/pkg/install:
total 4
-rw-r--r-- 1 root root 525 2010-08-22 10:18 slack-desc

/home/etf/build/b43-fwcutter/pkg/usr:
total 16
drwxr-xr-x 2 root root 4096 2010-08-22 10:18 bin
drwxr-xr-x 3 root root 4096 2010-08-22 10:18 doc
drwxr-xr-x 3 root root 4096 2010-08-22 10:18 man
drwxr-xr-x 3 root root 4096 2010-08-22 10:18 src

/home/etf/build/b43-fwcutter/pkg/usr/bin:
total 20
-rwxr-xr-x 1 root root 18440 2010-08-22 10:18 b43-fwcutter

/home/etf/build/b43-fwcutter/pkg/usr/doc:
total 4
drwxr-xr-x 2 root root 4096 2010-08-22 10:18 b43-fwcutter-013

/home/etf/build/b43-fwcutter/pkg/usr/doc/b43-fwcutter-013:
total 4
-rw-r--r-- 1 root root 1730 2010-08-22 10:18 README

/home/etf/build/b43-fwcutter/pkg/usr/man:
total 4
drwxr-xr-x 2 root root 4096 2010-08-22 10:18 man1

/home/etf/build/b43-fwcutter/pkg/usr/man/man1:
total 4
-rw-r--r-- 1 root root 671 2010-08-22 10:18 b43-fwcutter.1.gz

/home/etf/build/b43-fwcutter/pkg/usr/src:
total 4
drwxr-xr-x 2 root root 4096 2010-08-22 10:18 b43-fwcutter-013

/home/etf/build/b43-fwcutter/pkg/usr/src/b43-fwcutter-013:
total 4
-rw-r--r-- 1 root root 947 2010-08-22 10:18 SLKBUILD

Slackware package maker, version 3.14159.

Searching for symbolic links:

No symbolic links were found, so we won't make an installation script.
You can make your own later in ./install/doinst.sh and rebuild the
package if you like.

This next step is optional - you can set the directories in your package
to some sane permissions. If any of the directories in your package have
special permissions, then DO NOT reset them here!

Would you like to reset all directory permissions to 755 (drwxr-xr-x) and
directory ownerships to root.root ([y]es, [n]o)? n

Creating Slackware package:  /home/etf/build/b43-fwcutter/b43-fwcutter-013-i486-1pw.txz

./
usr/
usr/src/
usr/src/b43-fwcutter-013/
usr/src/b43-fwcutter-013/SLKBUILD
usr/man/
usr/man/man1/
usr/man/man1/b43-fwcutter.1.gz
usr/doc/
usr/doc/b43-fwcutter-013/
usr/doc/b43-fwcutter-013/README
usr/bin/
usr/bin/b43-fwcutter
install/
install/slack-desc

Slackware package /home/etf/build/b43-fwcutter/b43-fwcutter-013-i486-1pw.txz created.

Package has been built.
Cleaning pkg and src directories
root[b43-fwcutter]# ls
SLKBUILD		       b43-fwcutter-013.tar.bz2
b43-fwcutter-013-i486-1pw.md5  build-b43-fwcutter-013-i486-1pw.log
b43-fwcutter-013-i486-1pw.txz
root[b43-fwcutter]# installpkg b43-fwcutter-013-i486-1pw.txz
Installing package b43-fwcutter-013-i486-1pw...
| b43-fwcutter (Broadcom BCM43xx firmware extracter)
| 
| The Broadcom wireless chip needs software, called "firmware", that
| runs on the wireless chip itself during operation. This firmware is
| copyrighted by Broadcom and must be extracted from Broadcom's
| proprietary drivers.
| You can extract the firmware from the Broadcom driver by using
| b43-fwcutter (or bcm43xx-fwcutter)
| 
| 
| 
| 
| 
root[b43-fwcutter]#
The order of the (created) directories is not in accord to the order of the alphabet (a, b, c, d, e, f, g, ...), so is that mean that the order is by the time created?

from the log at /var/log/packages/b43-fwcutter-013-i486-1pw

Code: Select all

PACKAGE NAME:              b43-fwcutter-013-i486-1pw
COMPRESSED PACKAGE SIZE:   10 K
UNCOMPRESSED PACKAGE SIZE: 21 K
PACKAGE LOCATION:          b43-fwcutter-013-i486-1pw.txz
PACKAGE DESCRIPTION:
b43-fwcutter: b43-fwcutter (Broadcom BCM43xx firmware extracter)
b43-fwcutter: 
b43-fwcutter: The Broadcom wireless chip needs software, called "firmware", that
b43-fwcutter: runs on the wireless chip itself during operation. This firmware is
b43-fwcutter: copyrighted by Broadcom and must be extracted from Broadcom's
b43-fwcutter: proprietary drivers.
b43-fwcutter: You can extract the firmware from the Broadcom driver by using
b43-fwcutter: b43-fwcutter (or bcm43xx-fwcutter)
b43-fwcutter: 
b43-fwcutter: 
b43-fwcutter: 
FILE LIST:
./
install/
usr/
usr/bin/
usr/bin/b43-fwcutter
usr/doc/
usr/doc/b43-fwcutter-013/
usr/doc/b43-fwcutter-013/README
usr/man/
usr/man/man1/
usr/man/man1/b43-fwcutter.1.gz
usr/src/
usr/src/b43-fwcutter-013/
usr/src/b43-fwcutter-013/SLKBUILD
The order of the files is according to the alphabet.

A question about Gslapt:
Glapt doesn't seem to have an access for a log, will there be, soon, a feature to view an installation log, of what package/software installed and when, from Gslapt?
Can I view a log of "what package/software installed and when" from slapt?

Right now, my way to a log f this kind is only via /var/log/packages, and sorting the files by the date of modification.
Image
Help to make Slackware easier Donate to Salix
Top
User avatar
pwatk
Posts: 474
Joined: 14. Mar 2010, 23:56
Location: United Kingdom

Re: log by "alphabet" & installation process by "time created"?

Post by pwatk »

Have a look at the makepkg and installpkg scripts, AFAIK this is what's happening:

This is the output from makepkg which in-turn is the output of tar creating the archive:

Code: Select all

./
usr/
usr/src/
usr/src/b43-fwcutter-013/
usr/src/b43-fwcutter-013/SLKBUILD
usr/man/
usr/man/man1/
usr/man/man1/b43-fwcutter.1.gz
usr/doc/
usr/doc/b43-fwcutter-013/
usr/doc/b43-fwcutter-013/README
usr/bin/
usr/bin/b43-fwcutter
install/
install/slack-desc
This is the output from installpkg which in-turn is the output of tar extracting the archive:

Code: Select all

./
install/
usr/
usr/bin/
usr/bin/b43-fwcutter
usr/doc/
usr/doc/b43-fwcutter-013/
usr/doc/b43-fwcutter-013/README
usr/man/
usr/man/man1/
usr/man/man1/b43-fwcutter.1.gz
usr/src/
usr/src/b43-fwcutter-013/
usr/src/b43-fwcutter-013/SLKBUILD
Your question might be better directed at the tar developers!
Image
Top
Post Reply

Return to “Misc”