Sorry for the length:-) I have used RedHat/Fedora since the company
started. But for the last few years (since F9) I have been doing
science. I tried to install F14 and found many changes. Much of what one
used accomplish by editing configuration files is now done using GUIs
I would like to know how the system works at the configuration file
level. What are the switches that can be included on the kernel command
line? Is there any way to control Plymouth so that the commands are
visible and one drops to a login prompt at the end? What is upstart
calling and what files does it modify? When one configures a dual head
display under gnome, what tools are used and what files are modified?
What auto configurations are controlled by HAL and udev and whatever?
Is there a document or book that can purchased/downloaded that explains
what is going on under the covers? I have found fragments via Google.
The software development I preform does not lend itself well to the
desktop environment. Most of my work is done from the command line
and/or under emacs. I currently use fvwm2 with a 6X6 grid of desktops.
If this query is not appropriate for this list, please suggest the
Not sure where to find the answer to this question. Google wasn't
helpful. The users on this list are a great repository of knowledge so
I thought to try here.
Is there a bash command that tells an executing script what *its* path
is? Not the path where the user is but where the script is. If not
that then a series of commands that yield the same result? Maybe some
way of using 'ps'?
Has me stumped and my dog-eared "UNIX in a Nutshell" hasn't exposed the
goodies either ;)
It all started with Puppy Linux 5.2. I setup a LiveCD and jumped in to get
familiar with it. I had some trouble with connectivity. I eventually got
around to trying my linksys Wireless-G dongle. This showed some promise
although I was unable to find the correct Puppy driver for the dongle and
eventually removed the Wireless-G and shelved that project. Later on, I
tried to log on with Fedora and found that NetworkManager was now unusable.
Okay, after fiddling around with it for a while, I did a complete reinstall
of Fedora (including reformatting the disk) and low-and-behold
NetworkManager still doesn't work. I would have thought the Fedora reinstall
would have installed the correct driver but apparently it didn't. I am able
to send this because I have plugged the Wireless-G back in. (aargh!) Has
anyone ever seen this sort of thing?
We have some RPM packages which have been built on a system with RPM
version 188.8.131.52 and are being installed on F14 based systems with
4.8.1.. We are creating the delta RPM packages on the F14 system with
So package foo version 1 installs on the F14 systems just fine. But
when running applydeltarpm with the drpm created against foo version 2,
we get "md5 mismatch of result" errors.
I'm guessing this is an issue with the fact that the RPM packages are
being built with an older version of RPM? If that's the case, is there
any way around this problem?
Thanks in advance...Paul...
Paul B Schroeder
<paulbsch "at" vbridges "dot" com>
I recently installed Oracle-XE using yum --nogpgcheck localinstall
oracle...rpm. No problem except that I screwed up the configuration. My
coworker told me that I should use rpm(8) because the installation
manual specified it rather than yum(8). My question is that is there any
specific advantage using yum(8) over rpm(8).
Jerry Feldman <gaf(a)blu.org>
Boston Linux and Unix
PGP key id: 537C5846
PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB CA3B 4607 4319 537C 5846
I have the above named tv tuner card ( which has usb connection ) .
I can tune to any tv channel that i wish but the problem is that
i can´t hear any sound . lsusb would print
Bus 001 Device 002: ID 2304:0208 Pinnacle Systems, Inc. Studio PCTV USB2
The output of lsusb -v concerning the above tuner is a bit more
lengthy so i saved it in an Xemacs document and attached it to this
email . The problem with the sound is persistent and it can´t be
resolved by changing the application that am using ( the same problem
exists with both Tv Time and xawtv ) . I was wondering if someone could
give me any pointers on what course to follow in order to find the exact
problem and resolve it .
I have a question for any wireless expert who can help.
At home I have two wireless access points - one upstairs and one
downstairs - to give a good signal anywhere in the house.
What I would like is to have a seamless wireless access from any
laptop whether mine or a visitor with the appropriate encryption
Now my thinking is that using the *same* ssid and encryption protocol
and password for both APs should do the trick nicely - so that is how
I have things set up (with different channel for each AP's output) and
indeed if I power up a laptop running F14 upstairs it connects nicely
with a lovely strong signal - but if I then go downstairs and boot the
same machine then it tries to connect to the upstairs AP despite the
nearest signal about 10 feet away being a great deal stronger! So
the system tries to connect to the last AP it connected to even if a
local signal is stronger - this is illogical behaviour and it is not
clear if NetworkManager or wpa_supplicant is the culprit - or if I am
not supposed to expect things to work that way!
I had a visitor who had a laptop here this weekend - and the same
problem arose - I decided to try to set up two connections in
NetworkManager both with the same ssid and encryption/password but tag
them with the MAC address of each AP - the box steadfastly refused to
reconnect to the nearest (and strongest) AP after having been
connected to the weak one first, and I had to remove the definition
for the weak signal altogether in NM's list of connections, and only
leave the connection tagged with the MAC address of the nearest strong
signal before restarting the NetworkManager service before I could
persuade NM to connect to the near and strong AP!
I don't know if the design of NetworkManager ever considered this
scenario and whether any developer ever put in place code to hook up
to a valid strong signal even if a previously valid signal (which is
currently weaker) still exists - but it seems to me that the decision
logic in NetworkManager is both perverse and flawed?
Anyone help with some knowledge here?