LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Home Forums Tutorials Articles Register
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 07-18-2007, 11:48 AM   #76
kite
Member
 
Registered: Aug 2003
Location: Shenzhen, China
Distribution: Slackware
Posts: 306

Rep: Reputation: 47

jong357,in fact auto-mounting is working already provided that you enable this behavior at System -> Preference -> Removable Disks and Media. Although unmounting thereafter is not working.

Another problem now is that I could not mount removable Disks manually if I have not put entry into /etc/fstab, the error message was: can't find /dev/sdaxx in /etc/fstab or /etc/mtab. Obviously mount point in /media/xx should be used instead. Something must be missing here. Notes: I have no problem with thunar under Xfce, so I think I have the right permission set.

I understand that I could put entries into /etc/fstab, but it looks like a workaround only. Mount points should be created and selected automatically. Suppose someone bring me a USB hard disk with 5 partitions, should I add 5 entries into /etc/fstab promptly? This is not productive at all. He must be standing behind me,laughing at me when I am doing so
 
Old 07-18-2007, 02:34 PM   #77
jong357
Senior Member
 
Registered: May 2003
Location: Columbus, OH
Distribution: DIYSlackware
Posts: 1,914

Original Poster
Rep: Reputation: 52
Quote:
Originally Posted by kite
jong357,in fact auto-mounting is working already provided that you enable this behavior at System -> Preference -> Removable Disks and Media. Although unmounting thereafter is not working.
Ah... Thanks for the info. Didn't know you had to enable anything. I'm completely ignorant when it comes to automounting. I'm heading out of town for the night but will be back tommorrow. I'll mess around with it some when I get home.

Quote:
Another problem now is that I could not mount removable Disks manually if I have not put entry into /etc/fstab, the error message was: can't find /dev/sdaxx in /etc/fstab or /etc/mtab. Obviously mount point in /media/xx should be used instead. Something must be missing here. Notes: I have no problem with thunar under Xfce, so I think I have the right permission set.
Yes, this seems to be conflicting with the idea of automounting. As far as I understand, your not supposed to put an entry in fstab if your using HAL to automount. It should figure this stuff out on it's own.

Quote:
Suppose someone bring me a USB hard disk with 5 partitions, should I add 5 entries into /etc/fstab promptly? This is not productive at all. He must be standing behind me,laughing at me when I am doing so
Only if he thinks computers should hold your hand... But yes, this wouldn't be an ideal situation. I have one NAS drive that I mount via fstab at boot and a usb stick that has been MIA for over 6 months. That's how much I use removeable media. One of the reasons why I have no use for HAL. If I need to transfer something from one computer to the next (that's not on my network) I burn a CD/DVD/DVD-DL....

I'll see if I can't find that USB stick or buy a new one just to see what it's supposed to be like in the 21st century...

Thanks again for the info. You know more about this than I do.
 
Old 07-18-2007, 05:10 PM   #78
dizzi
Member
 
Registered: Jun 2004
Location: Yorkshire, UK
Distribution: Mint, Slackware
Posts: 146

Rep: Reputation: 15
Hi

Thanks, yup I had the suspicion that order was important that's why I wanted to hang on a bit before random reinstallation of packages using upgradepkg. That for loop fits the bill perfectly cheers.

On another note I have decided to build one or two other Gnome packages. I had a go at Gnumeric (using checkinstall) and it worked perfectly. One particular statement from your earlier posts with regard to building Gnome packages caught my attention though, namely

Quote:
Originally Posted by jong357
Just be aware that I use --sysconfdir=/etc/gnome for anything gconf related. You'll have to pass that switch to get things in the right place (if applicable).
My question is how does one determine whether something is "gconf related"?

Cheers

Last edited by dizzi; 07-18-2007 at 05:12 PM.
 
Old 07-18-2007, 10:11 PM   #79
b3rx
Member
 
Registered: Mar 2006
Distribution: Slackware 13.0
Posts: 75

Rep: Reputation: 15
dizzi, im sorry for giving you the wrong answer. I should have known that the order is important. I stand corrected.
 
Old 07-19-2007, 03:14 AM   #80
dizzi
Member
 
Registered: Jun 2004
Location: Yorkshire, UK
Distribution: Mint, Slackware
Posts: 146

Rep: Reputation: 15
b3rx

Not a problem m8. Actually your solution was not altogether "wrong" since in many multiple package installation situations, it would be the most efficient method. Thanks for the help.

Cheers

Last edited by dizzi; 07-19-2007 at 07:28 AM.
 
Old 07-19-2007, 07:05 AM   #81
b3rx
Member
 
Registered: Mar 2006
Distribution: Slackware 13.0
Posts: 75

Rep: Reputation: 15
nevertheless it is still wrong... thanks anyway..
 
Old 07-19-2007, 06:13 PM   #82
jong357
Senior Member
 
Registered: May 2003
Location: Columbus, OH
Distribution: DIYSlackware
Posts: 1,914

Original Poster
Rep: Reputation: 52
Quote:
Originally Posted by dizzi
On another note I have decided to build one or two other Gnome packages. I had a go at Gnumeric (using checkinstall) and it worked perfectly. One particular statement from your earlier posts with regard to building Gnome packages caught my attention though, namely



My question is how does one determine whether something is "gconf related"?

Cheers
Well, you pretty much just have to build it with:

./configure --prefix=/usr
make
make install DESTDIR=~/test

and then have a look see if anything is in the wrong place. Stuff like /usr/etc or /usr/var or /etc/gconf/schemas are all the wrong place. You could just use standard switches for everything even if you don't need to I guess.

./configure --prefix=/usr \
--libexecdir=/usr/libexec \
--localstatedir=/var/lib \
--sysconfdir=/etc/gnome

basically if you see schema files in the package then you need to use --sysconfdir=/etc/gnome... If it's just a conf file then --sysconfdir=/etc is fine. Have a look at your /etc/gnome directory. If a package has the same directories then you need to use /etc/gnome. Also don't forget about all the doinst.sh commands. Look at the control-center build script and doinst.sh. That is a good example. It runs all the gnome doinst.sh commands that are available except for the gdk-pixbuf-query-loaders one, which is rare. It runs them all because it contains all the directories and files that mandates the use of said commands.

Anything in:
/usr/share/icons - Run gtk-update-icon-cache
/usr/share/mime - Run update-mime-database
/etc/gnome/gconf/schemas - Run gconftool-2
/var/lib/scrollkeeper - Run scrollkeeper-update
/usr/share/applications - Run update-desktop-database

This is how I build gnemeric:
http://jaguarlinux.com/pub/DIY/sourc...numeric-1.6.3/

Looking at my script it does look to be scrollkeeper, schema, mime and .desktop related. Also if you find man pages in /usr/share/man then use --mandir=/usr/man. If you find info pages in /usr/share/info then use --infodir=/usr/info... It's all a matter of being anal and making sure it all gets to where it should be.

Last edited by jong357; 08-08-2007 at 12:12 PM.
 
Old 07-20-2007, 04:42 AM   #83
dizzi
Member
 
Registered: Jun 2004
Location: Yorkshire, UK
Distribution: Mint, Slackware
Posts: 146

Rep: Reputation: 15
Ok Thanks

To build Gnumeric I used the:

./configure --prefix=/usr \
--sysconfdir=/etc/gnome \
--mandir=/usr/man


options. I was not too sure what the "--localstatedir=/var/lib" switch means so I did not include it. Thanks for the slackbuild.

Cheers
 
Old 07-20-2007, 06:48 AM   #84
gnashley
Amigo developer
 
Registered: Dec 2003
Location: Germany
Distribution: Slackware
Posts: 4,928

Rep: Reputation: 612Reputation: 612Reputation: 612Reputation: 612Reputation: 612Reputation: 612
localstatedir and sysconfdir should be set for many gnome packages and are safe to set for anything gnome-related. Anything that won't accept either of those options will tell you so.
 
Old 07-23-2007, 08:27 AM   #85
dizzi
Member
 
Registered: Jun 2004
Location: Yorkshire, UK
Distribution: Mint, Slackware
Posts: 146

Rep: Reputation: 15
Hi

Is it possible to configure the Gnome file manager to display just one graphical window showing "back" and "next" buttons instead of the current behaviour where a new window pops up when navigating through subdirectories?

Oh can someone please post or email me a MANIFEST file?

Cheers

Last edited by dizzi; 07-23-2007 at 08:33 AM.
 
Old 07-23-2007, 08:41 AM   #86
Feinom
Member
 
Registered: Mar 2004
Location: Norway
Distribution: Slackware 12.2
Posts: 40

Rep: Reputation: 17
Quote:
Originally Posted by dizzi
Hi

Is it possible to configure the Gnome file manager to display just one graphical window showing "back" and "next" buttons instead of the current behaviour where a new window pops up when navigating through subdirectories?

Oh can someone please post or email me a MANIFEST file?

Cheers
In Nautilus, go to Edit -> Preferences -> Behavior and tick the "Always open in browser windows" box. That'll do the trick :-)
 
Old 07-23-2007, 09:12 AM   #87
dizzi
Member
 
Registered: Jun 2004
Location: Yorkshire, UK
Distribution: Mint, Slackware
Posts: 146

Rep: Reputation: 15
Oh brilliant, thanks for the help.

cheers
 
Old 07-23-2007, 03:18 PM   #88
jong357
Senior Member
 
Registered: May 2003
Location: Columbus, OH
Distribution: DIYSlackware
Posts: 1,914

Original Poster
Rep: Reputation: 52
Manifest

/var/log/gnome-2.18.3/MANIFEST
Code:
intltool-0.35.5-noarch-1
docbook-xml-4.5-noarch-1
scrollkeeper-0.3.14-i486-1
docbook-xsl-1.72.0-noarch-1
gtk-doc-1.8-noarch-1
gnome-common-2.18.0-noarch-1
orbit2-2.14.7-i486-1
libbonobo-2.18.0-i486-1
gconf-2.18.0.1-i486-1
gnome-mime-data-2.18.0-noarch-1
pygobject-2.13.2-i486-1
pycairo-1.4.0-i486-1
pyorbit-2.14.3-i486-1
pygtk-2.10.6-i486-1
pyxdg-0.15-i486-1
iso-codes-1.2-noarch-1
libnotify-0.4.4-i486-1
libdaemon-0.11-i486-1
gnome-vfs-2.18.1-i486-1
libgnome-2.18.0-i486-1
libgnomecanvas-2.14.0-i486-1
libbonoboui-2.18.0-i486-1
xml-simple-2.16-i486-1
icon-naming-utils-0.8.2-noarch-1
gnome-icon-theme-2.18.0-noarch-1gnome2183
gnome-keyring-0.8.1-i486-1
libgnomeui-2.18.1-i486-1
gtk-engines-2.10.2-i486-1
gnome-themes-2.18.1-noarch-1
gnome-doc-utils-0.10.3-noarch-1
gnome-desktop-2.18.3-i486-1
libwnck-2.18.2-i486-1
libsoup-2.2.100-i486-1
evolution-data-server-1.10.2-i486-1
gnome-menus-2.18.3-i486-1
gnome-panel-2.18.3-i486-1
libcm-0.1.1-i486-1
metacity-2.18.5-i486-1
libcroco-0.6.1-i486-1
libgnomecups-0.2.2-i486-1
libgnomeprint-2.18.0-i486-1
libgnomeprintui-2.18.0-i486-1
gail-1.18.0-i486-1
eel-2.18.0.1-i486-1
nautilus-2.18.3-i486-1
libxklavier-3.2-i486-1
gstreamer-0.10.13-i486-1
liboil-0.3.12-i486-1
gst-plugins-base-0.10.13-i486-1
libgnomekbd-2.18.2-i486-1
control-center-2.18.1-i486-1
gnome-session-2.18.3-i486-1
gnome-terminal-2.18.1-i486-1
libgtop-2.14.9-i486-1
system-tools-backends-1.4.2-noarch-1
gnome-applets-2.18.0-i486-1
mozilla-firefox-2.0.0.4-i686-1gnome2183
yelp-2.18.1-i486-1
bug-buddy-2.18.1-i486-1
gtksourceview-1.8.5-i486-1
gnome-python-2.18.2-i486-1
gnome-python-extras-2.14.3-i486-1
nautilus-cd-burner-2.18.2-i486-1
gst-plugins-good-0.10.6-i486-1
gst-plugins-bad-0.10.5-i486-1
gst-plugins-ugly-0.10.6-i486-1
totem-2.18.2-i486-1
gnome-media-2.18.0-i486-1
gnome-python-desktop-2.18.0-i486-1
enchant-1.3.0-i486-1
gedit-2.18.1-i486-1
eog-2.18.2-i486-1
gconf-editor-2.18.0-i486-1
gnome-utils-2.18.1-i486-1
gnome-system-monitor-2.18.2-i486-1
gnome-netstatus-2.12.1-i486-1
gcalctool-5.9.14-i486-1
zenity-2.18.2-i486-1
gnome-games-2.18.2.1-i486-1
gnome-user-docs-2.18.2-noarch-1
file-roller-2.18.4-i486-1
gnome-nettool-2.18.0-i486-1
vino-2.18.1-i486-1
gnome-volume-manager-2.17.0-i486-1
gnome-backgrounds-2.18.3-noarch-1
sound-juicer-2.16.4-i486-1
gnome-device-manager-0.1-i486-1
gtkhtml-3.14.2-i486-1
lib1394-1.2.1-i486-1
pwlib-1.10.7-i486-1
opal-2.2.8-i486-1
ekiga-2.0.9-i486-1
evince-0.8.1-i486-1
gnome-keyring-manager-2.18.0-i486-1
gnome-screensaver-2.18.2-i486-1
gnome-power-manager-2.18.3-i486-1
Still haven't messed with automounting stuff. Noticed firefox-2.0.0.5 is out too. Also noticed that we'll need dbus-python for hal-device-manager... I build it on DIY but not sure why I left it out on Slack. In the mean time, gnome-device-manger is the exact same thing only has nicer icons. hal-device-manager doesn't even show in the applications menu anyway. I'll jump on those in a couple days.

In the middle of a PPC DIY build right now so my free time is pretty scarce...

Last edited by jong357; 07-23-2007 at 03:33 PM.
 
Old 07-23-2007, 05:55 PM   #89
Ilgar
Senior Member
 
Registered: Jan 2005
Location: Istanbul, Turkey
Distribution: Slackware64 15.0, Slackwarearm 14.2
Posts: 1,157

Rep: Reputation: 237Reputation: 237Reputation: 237
Hi jong357,

Thanks for the nice work. Yesterday I used your script on my laptop. It worked smoothly. For those interested: The compilation time is around 3-4 hours and after removing the cached files it takes about 600-700 MB of disk space. I didn't have much time to test it but all seems OK. On the GNOME desktop you have multiple icons for certain things, because the KDE icons show up too, but as mentioned earlier this is related to the way GNOME and KDE work.
 
Old 07-23-2007, 08:19 PM   #90
dizzi
Member
 
Registered: Jun 2004
Location: Yorkshire, UK
Distribution: Mint, Slackware
Posts: 146

Rep: Reputation: 15
Thanks for the MANIFEST file

Incidentally, has anyone built a working gdm? It felt a bit incongruous login into Gnome using kdm so I decided to attempt a gdm build. Although the build went ok, gdm did not quite work properly. To begin with, the sessions menu contained only Gnome and no, KDE, XFCE, Blackbox etc even though they were installed. I was able to log successfully into Gnome though but when I logged out and logged in again, there was a error message stating that some parts of Gnome will not work properly. Sure enough, some desktop icons changed into greyish symbols (resembling sheets of paper) and generated errors when clicked. Everything looked and worked fine again when gdm was uninstalled.

I would be quite grateful therefore if someone who has gotten gdm to work on this Gnome build to post instructions or a slackbuild.

Incidentally, I used the gdm-2.18.2.tar.bz2 source and my configure options were as follows:

./configure \
--prefix=/usr \
--sysconfdir=/etc/X11 \
--localstatedir=/var/lib


Cheers

Last edited by dizzi; 07-24-2007 at 05:44 AM.
 
  


Reply

Tags
gnome



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
what is vanilla kernel dogslayer Linux - Kernel 1 01-30-2007 02:43 AM
X's blank screen: ATI drivers+Radeon A9250+Xorg+Vanilla 2.6.14.3+Slackware 10.2 Slack-Rulez Linux - Hardware 8 12-27-2005 03:19 PM
Vanilla Kernel paddyjoy Linux - Newbie 3 06-08-2005 12:49 AM
Vanilla kernel RichardSimmons Linux - General 2 03-21-2004 12:25 PM
slackware 8.0 vanilla 2.4.18 ethernet problems bluskyambition Linux - Networking 8 08-24-2003 12:12 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:38 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
Open Source Consulting | Domain Registration