Linux-Setup Digest #255, Volume #21 Fri, 18 May 01 09:13:08 EDT
Contents:
Re: Why oh why (disk partitioning) ([EMAIL PROTECTED])
Re: Why oh why (disk partitioning) ([EMAIL PROTECTED])
Re: LILO on MBR fine. LILO on partition no good. ("Colin Wigg")
Problem with smooth running ("Vojta")
Re: Why oh why (disk partitioning) (Lew Pitcher)
No keyboard on X ("Lawrence A. Guirre")
Re: Why oh why (disk partitioning) ("Peter T. Breuer")
Re: filename contains ":" characters in scp? (Colin Watson)
Re: Netscape 4.76 and Scroll Mouse Setup - from koala/colas web site (Ed)
Re: not rpm? ("ne...")
Re: Why oh why (disk partitioning) ("Peter T. Breuer")
Re: Why oh why (disk partitioning) (Gerhard Roth)
Like in windows snmp service, can i get the same in linux? ("v.nagasrinivas")
Re: How do I update RH 7.1 correctly using RPMs? (Jesus Manuel NAVARRO LOPEZ)
smb_print ("Arnd-Eike Br�dern")
----------------------------------------------------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Why oh why (disk partitioning)
Date: Fri, 18 May 2001 11:12:06 +0100
Reply-To: no_replyto@oursite
This message has been posted by: [EMAIL PROTECTED] (Dave Ewart)
On Fri, 18 May 2001 11:19:25 +0200, Alexander Martinez
<[EMAIL PROTECTED]> wrote:
>
>> Anyways, if you think you can convince me, what'd be the best setup
>> for a 2GB disk? (Partition-size wise). PS: I need 128MB Swap.
>
>my suggestion is this:
>
>/ 100MB
>/boot 10MB
>/tmp 200 MB
>/var 100MB
>/home 150MB
>/root 50MB
>swap 128MB
>/usr remaining space
I would advise the original poster against blindly partitioning their
hard drive as above without very careful thought about what you need.
[I said you'd get a different answer from every person!]
I am not disputing that the partitioning is suitable for you, Alexander,
but everyone's needs are different.
Just as an example, to indicate why the above scheme may not be
appropriate, is the /tmp partition. As far as I can tell, FOR MY
WORKSTATION, /tmp is only used by one or two apps (such as Mutt, my
email program) and these files are only ever as large as a single email
message. Thus, if _I_ partitioned as you have suggested, I would have
effectively wasted 200MB of space that could be used elsewhere (e.g.
/home, if you have a lot of "data", or perhaps /usr, if you have a lot
of programs to install). I agree that some users may need a large /tmp
partition, but it is not always appropriate.
Similarly, I don't see any need on my workstation to partition /root
separately, since there is nothing of consequence contained there.
Furthermore, allocating 100MB to /var may be a mistake, since (usually)
only incoming user mail spools and news go here. If it is a single user
system, 100MB is probably too much. Conversely, for a news server, it
is clearly too small.
The underlying point I am trying to make is that the partitioning scheme
should closely reflect your needs. Admittedly, sometimes this is very
difficult! There is no "correct" partition scheme.
I would advise the original poster to have a careful think about what
"data" and programs are to be installed initially, and how that might
change over time. Base your partitioning scheme on this. Two people
with exactly the same specification of PC will probably want different
partitioning schemes because they will be using the PC differently.
Dave.
--
P.S. Apologies for the spam-trapped headers - they are added by my
outgoing news server and I have no control over them.
--
Dave Ewart
[EMAIL PROTECTED]
Computing Manager
ICRF Cancer Epidemiology Unit, Oxford UK
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Why oh why (disk partitioning)
Date: Fri, 18 May 2001 11:18:05 +0100
Reply-To: no_replyto@oursite
This message has been posted by: [EMAIL PROTECTED] (Dave Ewart)
I also meant to add that you should read the Linux Partition HOWTO:
http://www.linuxdoc.org/HOWTO/mini/Partition/
It discusses a lot of the issues surrounding choosing a partition scheme
in section 4.3 ...
Dave.
--
P.S. Apologies for the spam-trapped headers - they are added by my
outgoing news server and I have no control over them.
--
Dave Ewart
[EMAIL PROTECTED]
Computing Manager
ICRF Cancer Epidemiology Unit, Oxford UK
------------------------------
From: "Colin Wigg" <[EMAIL PROTECTED]>
Subject: Re: LILO on MBR fine. LILO on partition no good.
Date: Fri, 18 May 2001 12:29:33 +0100
Thanks Kenny,
All's fine now, I read somewhere to FDISK /MBR and that seems to have sorted
the problem.
The only advantage of BM is it's easier for my kids to understand....
And, yes, I had previously used LILO to boot my 2 WIN98 partitions and it
was fine...
Cheers, Colin
"Kenny McCormack" <[EMAIL PROTECTED]> wrote in message
news:9duk89$2q8$[EMAIL PROTECTED]...
> In article <[EMAIL PROTECTED]>,
> pd <[EMAIL PROTECTED]> wrote:
> >Is the linux boot partition within the first 1024 cylinders
> >
> >I find LILO works fint as a boot selector so I did not install
> >BootMagic. Is there some advantage to BM? (The RH docs seem to think
> >LILO can't boot other OS's, but the LILO docs say otherwise and it works
> >find for me, booting W2K from an NTFS partition.)
>
> Or you could use GRUB, which works very well, and doesn't depend on LILO -
> or hard blocks/sectors - at all.
>
> GRUB looks like the choice of the GNU generation...
------------------------------
From: "Vojta" <[EMAIL PROTECTED]>
Subject: Problem with smooth running
Date: Fri, 18 May 2001 12:56:31 +0200
Hallo,
I'm novice to Linux. I have installed RedHat7.1 with KDE. I have problems
with smooth running when workink with KDE (or GNOME). It's often hardly
swapping, and my system very twitchs. After KDE launchs I run KDE
configurator to see state of my RAM - 99% of it is full and there is about
1MB in swap. Why so much? (I do not run any application except KDE
configurator)I have 64MB of RAM, two HDD connected to one channel, native
partition is on hda, swap partition on hdb, size of swap partition is 164MB,
size of native partition is 3GB, processor Celeron 400MHZ. What is the
problem? I tried to run Win98SE alse and it's all OK. I open for or five IE,
some disk manager and it runs smoothly. Why Linux can't? Please give me an
advice.
Thanks very much :) Vojta
------------------------------
From: [EMAIL PROTECTED] (Lew Pitcher)
Subject: Re: Why oh why (disk partitioning)
Reply-To: [EMAIL PROTECTED]
Date: Fri, 18 May 2001 12:14:48 GMT
On Fri, 18 May 2001 09:09:38 +0200, "Peet Grobler" <peetgr at
absa.co.za> wrote:
>Hi there.
>
>Why would one want to split your Linux over more than one filesystem? E.g.
>something like the following:
>
>/dev/sda1 /root
>/dev/sda2 /usr
>/dev/sda3 /home
>/dev/sda4 /var
>
>etc. What is the benefits of doing it like this? I mean, if one partition
>runs out of space, it's hell to get it fixed. Why not just stuff everything
>on one partition, voila, no space problems? Now, I've heard of many people
>suggesting this, and I'd love to know why. There's gotta be a hidden benefit
>I just keep missing.
Off the top of my head:
- isolates directory trees for easier backup and restore
(think backup to cdrom)
- isolates directory trees for easier upgrade/maintenance
(think distro upgrade)
- isolates directory trees for better hardware failure protection
(think head crash or bad sectors)
- limits the growth of files within certain directory trees
(think /tmp or /var/spool)
- enforces certain rules about physical placement of system files
(think LILO and 2Gb limit)
- permits alternate directory trees
(think umount /usr ; mount /dev/some-other-partition /usr )
- permits hiding of directory tree
(think what happens to files in /mnt when a dev is mounted to /mnt)
>Anyways, if you think you can convince me, what'd be the best setup for a
>2GB disk? (Partition-size wise). PS: I need 128MB Swap.
I'm not about to try to convince you. If you don't think that you need
to partition, that's your business. Personally, though, I've found it
helpfull to partition my harddisk.
Lew Pitcher, Information Technology Consultant, Toronto Dominion Bank Financial Group
([EMAIL PROTECTED])
(Opinions expressed are my own, not my employer's.)
------------------------------
From: "Lawrence A. Guirre" <[EMAIL PROTECTED]>
Subject: No keyboard on X
Date: Fri, 18 May 2001 19:43:56 +0800
Hi,
I am running X4.03 on kernel 2.4.3 for thin clients.
My hardware is an intel i810 and using the package
from LTSP (linux terminal server project) on RHL 7.0
My problem is that when I start xwindows, i could get
the mouse working and the display is ok, but the keyboard
freezes up. The system is still up since I can logout of the
xsession and inspect the Xfree86.0.log file. The error
that I can see from there is
"Couldn't load XKB keymap, falling back to pre-XKB keymap"
Any help is much appreciated!
Thanks!
--
Lawrence
=====BEGIN PGP MESSAGE=====
Version: GnuPG v1.0.4-1 (MingW32)
Comment: For info see http://www.gnupg.org
owGbwMvMwCQ4zaT1zCK9r3cY1zKyJInkJJYXpeYlpzpk5ibqJefn6pVUlFiV71jl
AxVXcNRTcC/NLCpK5eUKLtJTCK4sLknNLVZwTMnNzMssLilKLMkv4uXi5fLMK0kt
ykssyczPS8xR8E0tLk5Mz8xLV3AsLs5PzkwsSS3m5fJIzCsuyc9TcCrNzEkBSuoo
mOm78XK55qYWJeakKDiWpeaVAu3xLyrJTE8sVnBOBZmpoxCQWJyZruCcWVLJyxWQ
kZmTWVCQmZdarACyNqOkpMBKX7+8vFwP6gNerpDUHCsFbTNjBQ0jTQUzY3NdSwNL
A14ut8QKNGELSwterg43FgZBJgY2ViaQvxm4OAVgIdSmyjA/Y/Hzakv2vfrv5sRc
SM32cvR8frKVYb579MKcRvFVWy7PtT9zi6c+uudPbR8A
=qZnw
=====END PGP MESSAGE=====
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: Why oh why (disk partitioning)
Date: Fri, 18 May 2001 14:09:16 +0200
[EMAIL PROTECTED] wrote:
> This message has been posted by: [EMAIL PROTECTED] (Dave Ewart)
> On Fri, 18 May 2001 11:19:25 +0200, Alexander Martinez
> <[EMAIL PROTECTED]> wrote:
>>/ 100MB
>>/boot 10MB
>>/tmp 200 MB
>>/var 100MB
>>/home 150MB
>>/root 50MB
>>swap 128MB
>>/usr remaining space
> [I said you'd get a different answer from every person!]
Correct.
> I am not disputing that the partitioning is suitable for you, Alexander,
> but everyone's needs are different.
Correct.
> Just as an example, to indicate why the above scheme may not be
> appropriate, is the /tmp partition. As far as I can tell, FOR MY
> WORKSTATION, /tmp is only used by one or two apps (such as Mutt, my
> email program) and these files are only ever as large as a single email
> message. Thus, if _I_ partitioned as you have suggested, I would have
/tmp is usually softlinked to /var/tmp, so the question moves itself to
how big should /var be.
But I often compile temporarily in /tmp (i.e. /var/tmp) so I need a lot
of space there 1GB is about by comfort point for /var. I also need about
100MB for log files in /var/log (I prefer to have 6 months of logs, and
if I turn on debugging on codes can fill 50MB a day easily)
> effectively wasted 200MB of space that could be used elsewhere (e.g.
> /home, if you have a lot of "data", or perhaps /usr, if you have a lot
> of programs to install). I agree that some users may need a large /tmp
> partition, but it is not always appropriate.
It's never necessary as _ /tmp _, but is often necessary as /var/tmp.
Burning cd images is an example of how to use 700MB of tmpspace in a
hurry.
> Similarly, I don't see any need on my workstation to partition /root
> separately, since there is nothing of consequence contained there.
Agreed. What's more, it should never be used!
> Furthermore, allocating 100MB to /var may be a mistake, since (usually)
> only incoming user mail spools and news go here. If it is a single user
And logs, and fonts, and various other things that "vary".
> system, 100MB is probably too much. Conversely, for a news server, it
No, I don't think so. I'd suggest 128MB for a minimal install and about
1GB for me!
> is clearly too small.
> The underlying point I am trying to make is that the partitioning scheme
> should closely reflect your needs. Admittedly, sometimes this is very
> difficult! There is no "correct" partition scheme.
Very true.
> I would advise the original poster to have a careful think about what
> "data" and programs are to be installed initially, and how that might
> change over time. Base your partitioning scheme on this. Two people
> with exactly the same specification of PC will probably want different
> partitioning schemes because they will be using the PC differently.
True.
Peter
------------------------------
From: [EMAIL PROTECTED] (Colin Watson)
Crossposted-To: comp.os.linux.networking
Subject: Re: filename contains ":" characters in scp?
Date: 18 May 2001 12:13:37 GMT
Peter T. Breuer <[EMAIL PROTECTED]> wrote:
>In comp.os.linux.setup Colin Watson <[EMAIL PROTECTED]> wrote:
>> is done, which makes tracking very difficult for the maintainer (i.e. I
>> can't do what I do for every other bug, put closes: #nnnnn against the
>> fix in the changelog, and have the bug tracking system remember the rest
>> of it for me).
>
>If you fixed the bug of trying to write in /usr, and made token changes
>to the docs to make them more comprehensible, call it closed! You have
>my "permission", should you need it! Man-db does work nowadays. It's
>stopped behaving strangely (mostly), so there's no need to try and
>fathom the docs any more. Doc bug avoided! And if I disagree with the
>bug closure I'll just make life hell by entering another bug report,
>and we go round again :-). But it's not likely that I'll disagree.
Well, it turns out I've done this now (I decided that if I was going to
be ranting on Usenet I might as well take some time off to write the
code ...), so I'll close it in my next upload.
>BTw, I see only two bugs reported in that report (my numerals):
>
>(1)
> /usr is mounted readonly, yet man insists at times on trying to update
> links and caches and dbs. It should check that the dir is writable
> before trying it!
>
>(2)
> Secondly: many doc bugs. What does "considered \"global\"" in the
> manpath.config connote, if anything. Why is it considered? Isn't
> it? Is there anything apart from "global", whatever you mean by it?
> What does it mean if not nothing? Please remove this GUFF!
I see others:
(3) No way to tell man to just get on with it, and not worry about
bringing the database up to date;
(4) Manpaths in the configuration file aren't reordered, so you have to
put deeper manpaths in the filesystem hierarchy before shallower
ones;
(5) (implied by the discussion) The whole path -> manpath mapping is
just hideously confusing at times.
Feel free to file separate bugs about those. The last will probably just
have to be fixed by better documentation.
>> And, really - if you had thirty-odd open bug reports, and one of them
>> contained stuff like "What does it mean if not nothing? Please remove
>> this GUFF!", would you be inclined to fix that one first? It's the best
>
>Well, I am - if nothing else - qualified to comment on scientific writing!
>So perhaps you should take the criticism of the writing seriously.
>I took the time to say what was wrong with it! The point (2)
>above is the start of the list of specific comments I made about the
>writing, quoting paragraphs and commenting on each. In other words, I
>treated it as if it were a scientific paper, applying the standard
>refereeing practices, the intent of which is to produce a better
>document through negotiation with the author ("peer review" :_).
Oh, I appreciate criticism and take it seriously - note, though, that
neither Fabrizio nor I wrote that in the first place (the text was
direct from 2.3.10, circa 1995), so the more vitriolic bits of
second-person criticism are misdirected. I suppose I should just develop
a thicker skin and get used to it, as people often conflate the author
and the maintainer ... Anyway, I've rewritten the paragraphs in
question, and they should make more sense now.
>> way of making a non-critical bug fall to the bottom of the pile.
>
>The write on /usr problem was functionally critical. It stopped man-db
>working in environments in which /usr is readonly.
I was thinking versus security problems and the like, of which man-db
has had more than its fair share recently. However, when I fixed man to
cope gracefully with permission problems in certain cases, I discovered
that it was key to lots of other stuff, so I owe you an apology. You
should get a copy of the changelog in a couple of days when I close that
bug and quite a few others.
>> I guess I'm trying to make a point (well, perhaps overstated - I
>> apologize for going off half-cocked) about bug reporting, just as about
>> helping people on newsgroups - making sarcastic remarks about the
>> package or its maintainer is almost always the least productive thing
>
>I had no sarcastic intent then. I can't even see any sarcasm in the report
>you mentioned now. Are you perhaps reading something into it? I made
>the debian report after talking directly with the author (I believe I
>recall). Our discussions were fruitful (not fruity!), and I added the
>debian report as a sort of deadline/guarantee that something would be
>done.
Perhaps so - normally I can read past differences in writing style, but
not always. Since the previous maintainer said at one point "just
guessing, no need to be flamed again", I took it that he was feeling
under some pressure as well.
>>>I went on to complain about the documentation, pointing out what made
>>>it so wonderfully incomprehensible. Has that been fixed ...
>
>> I rewrite bits and pieces as I see them. On one point I agree with
>> Fabrizio - since I have lots of code to fix and/or rewrite, any offers
>> to help improve the documentation will be appreciated. Note that
>
>I believe I did that, in a very concrete manner.
Your side of the conversation hasn't been recorded in the bug log,
except by way of quotes in replies, so that wasn't clear to me. The
current source is in CVS at http://sourceforge.net/projects/man-db/; I
can give you write access.
>> Cheers [followups set to poster, as this is getting onto a different
>> topic],
>
>I unset them, probably. Dunno why.
Well, followups away from .networking, anyway ...
>Thanks for the followup (honestly!).
It appears to have borne some useful fruit, to my own surprise as much
as anyone else's. :)
Cheers,
--
Colin Watson [[EMAIL PROTECTED]]
"Everyone, please welcome our new friend Stef. He's here with us
because he thinks he's a penguin." - http://www.userfriendly.org/
------------------------------
From: Ed <[EMAIL PROTECTED]>
Subject: Re: Netscape 4.76 and Scroll Mouse Setup - from koala/colas web site
Reply-To: [EMAIL PROTECTED]
Date: Fri, 18 May 2001 12:28:35 GMT
AS wrote:
> Hi,
>
> I am trying to make scroll mouse work with netscape and tried to follow
> the instruction given in
> http://www-sop.inria.fr/koala/colas/mouse-wheel-scroll/#netscape, but no
> success.
>
> Can someone tell me WHAT to replace and WITH WHAT in this code?
> ^^^^^^^
> ^^^^^^^^^^^
> Thanks,
> AS.
>
> # NETSCAPE
> Netscape*drawingArea.translations: #replace \ <Btn1Down>:
> ArmLink() \n\ <Btn2Down>: ArmLink() \n\
> ~Shift<Btn1Up>: ActivateLink() \n\ ~Shift<Btn2Up>:
> ActivateLink(new-window) \ DisarmLink() \n\
> Shift<Btn1Up>: ActivateLink(save-only) \ DisarmLink() \n\
> Shift<Btn2Up>: ActivateLink(save-only) \ DisarmLink() \n\
> <Btn1Motion>: DisarmLinkIfMoved() \n\ <Btn2Motion>:
> DisarmLinkIfMoved() \n\ <Btn3Motion>:
> DisarmLinkIfMoved() \n\ <Motion>: DescribeLink() \n\
> <Btn3Down>: xfeDoPopup() \n\ <Btn3Up>:
> ActivatePopup() \n\ Ctrl<Btn4Down>: PageUp()\n\
> Ctrl<Btn5Down>: PageDown()\n\
> Shift<Btn4Down>: LineUp()\n\
> Shift<Btn5Down>: LineDown()\n\
> None<Btn4Down>: LineUp()LineUp()LineUp()LineUp()LineUp()LineUp()\n\
> None<Btn5Down>:
> LineDown()LineDown()LineDown()LineDown()LineDown()LineDown()\n\
> Alt<Btn4Down>: xfeDoCommand(forward)\n\ Alt<Btn5Down>:
> xfeDoCommand(back)\n
>
> Netscape*globalNonTextTranslations: #override\n\ Shift<Btn4Down>:
> LineUp()\n\
> Shift<Btn5Down>: LineDown()\n\
> None<Btn4Down>:LineUp()LineUp()LineUp()LineUp()LineUp()LineUp()\n\
>
None<Btn5Down>:LineDown()LineDown()LineDown()LineDown()LineDown()LineDown()\n\
> Alt<Btn4Down>: xfeDoCommand(forward)\n\ Alt<Btn5Down>:
> xfeDoCommand(back)\n
>
There is an easier way. Here is a link to what really works :
http://pclinuxonline.com/Help___How_To/netscape/netscape.html.
Follow instructions closely and you will be all set.
------------------------------
From: "ne..." <[EMAIL PROTECTED]>
Subject: Re: not rpm?
Date: Fri, 18 May 2001 12:32:39 GMT
On May 18, 2001 at 00:43, Mike Flys eloquently wrote:
>I tried intalling some things from the redhat 7.1 cd's and it gives me an error
>saying they're not rpm's. Can anyone tell me whats wrong?
Nope. The reason being we don't know what exactly you did.
What commands did you run? What were the error messages
listed? We need the actual text you input and the text
of the error messages.
--
Registered Linux User # 125653 (http://counter.li.org)
BOFH excuse #108:
The air conditioning water supply pipe ruptured over the machine room
8:31am up 19 days, 14:25, 9 users, load average: 0.13, 0.04, 0.07
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: Why oh why (disk partitioning)
Date: Fri, 18 May 2001 14:11:41 +0200
[EMAIL PROTECTED] wrote:
> This message has been posted by: [EMAIL PROTECTED] (Dave Ewart)
> On Fri, 18 May 2001 09:09:38 +0200, Peet Grobler <peetgratabsa.co.za> wrote:
> I agree with you comment that if one partition runs out of space, it can
> be annoying to know that you have space elsewhere lying unused. A
And of course symlinks are a good way to fix that - temporarily, until
you feel like doing it properly with "parted" or some other tool.
> carefully planned partition scheme should probably avoid that. Remember
> that /usr will only grow in size if you install more software, /home has
> the potential to grow very large, but all of my comments here depend on
> what you want to use the system for.
> Having said that, it almost always make sense to put /home on a separate
> partition, especially if you're still "experimenting" with Linux.
Peter
------------------------------
From: Gerhard Roth <[EMAIL PROTECTED]>
Subject: Re: Why oh why (disk partitioning)
Date: Fri, 18 May 2001 14:29:20 +0200
Peet Grobler wrote:
> etc. What is the benefits of doing it like this? I mean, if one partition
> runs out of space, it's hell to get it fixed. Why not just stuff everything
> on one partition, voila, no space problems?
Many people already mentioned the advantages keeping things in different
partitions. But now let's look at it the other way round: if avoiding space
problems with a single partition is it's only advantage, then it has no
advantage at all. You can avoid space problems with multiple partitions, too,
by using a volume manager.
Gerhard
------------------------------
From: [EMAIL PROTECTED] ("v.nagasrinivas")
Subject: Like in windows snmp service, can i get the same in linux?
Date: Fri, 18 May 2001 12:51:44 +0000 (UTC)
Hi,
Like in windows snmp service, can i get the same in linux also.
Why means i have my own propritery snmp manager to access the mib tables
of my ATM/Frame Relay box, just now i configured the snmp services in
windows2000 server, and through general mib, i am getting my machines
information in the manager by specifying the machine as a node.
Similarly how to configure the snmp service in the linux box. Is the
snmp service integrated inside the kernel, where can i get all these
information.
thanks in advance,
regards,
srinivas.
--
v.naga srinivas
YVL SoftwareConsultancy,
B4,Q1,6th floor,
CyberTowers,Hi-Tec city,
Madhapur,Hyderabad-500033
Andhra Pradesh State
INDIA.
ph(office):091-040-3110200
visitme http://www.nagasrinivasv.com
--
Posted from ns.stph.net [196.12.32.2]
via Mailgate.ORG Server - http://www.Mailgate.ORG
------------------------------
From: Jesus Manuel NAVARRO LOPEZ <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.admin,comp.os.linux.misc
Subject: Re: How do I update RH 7.1 correctly using RPMs?
Date: Fri, 18 May 2001 09:59:02 +0200
Hi, George:
George Adams wrote:
>
> I have a basic question about keeping my RH 7.1 Linux box up-to-date. I see
> that there are already several patches and upgrades of various sorts
> available in the form of RPMs off Redhat's website, which I have downloaded.
>
> Now what? For instance, if I do an "rpm -Uvh
> netscape-common-4.77-1.i386.rpm", I get several warning messages about other
> programs (such as Netscape Navigator and KDE) which are dependent on the
> netscape-common-4.76 files. Should I ignore these warning, and issue a
> "rpm -e -nodeps" for the old netscape-common-4.76 package, then install the
> new package? Or will this break some program or tool that needed the old
> package and doesn't know what to do with the new package?
>
RPMs under RH control dependencies at the shared library level. That
means is *usally* very confiable. Still, it deppends on the RPM
developer to do his work well (he can "mark" a RPM dependant on a strict
given version of a DLL, when it is not so). But usually, doing things
as suggested by de RPM manager is a good idea.
First, if you want to be sligthly more careful, don't do -U, which means
"upgrade or install if no previous version" but -F which means
"freshen", or "upgrade only if previous version exists", and always try
first the install with the --test option so you will see what's going to
hapen. So you should do "rpm -Fhvv --test
netscape-common-4.77-1.i386.rpm", for instance.
The previous command will say that your already installed version of
netscape-navigator (the netscape suit if formed by netscape-common and
netscape-navigator or netscape-communicator) depends on the already
installed version of netscape-common. Your next step then is download
the new version of netscape-navigator and try again:
rpm -Fhvv --test netscape-common-4.77-1.i386.rpm
netscape-navigator-4.77-1.i386.rpm
Then you will see that the warning message about navigator dependencies
disappears
Now, you say that it "conflicts" somehow with some KDE packets: you
should follow simmilar path: either is a package you don't need, then
you can either unistall it (if no further dependencies problems arise),
upgrade, or change the install of the Netscape packages from -F to -i
(that 'i' stays for install: in this case you will install the new
netscape, but the old one will remain in your box too).
The same goes when the message is about the package you're about to
install needs some_library version.so.X >= a.b.c. Then you usually go
to rpmfind.net and search for the mentioned library to see what packages
offer it, then you compare with what you have already installed (rpm -qa
| grep package_name) and upgrade/install/unistall as needed.
As you see these are bit convoluted paths so you are better upgrading
frecuently so you need to manage a short list of packages at a time. If
you're one/two months without upgrade, your bets are that trying to
upgrade some simple package will awake a storm of packages
cross-dependencies.
> Another example:
>
> > rpm -Uvh arts-2.1.2-1.i386.rpm
> error: failed dependencies:
> arts = 2.1.1 is needed by kdelibs-sound-2.1.1-5
>
Look for newer versions of kdelibs-sound (most probably you will end
upgrading the whole KDE bunch), or rpm -i your arts package so you have
both version installed.
> If I force the removal of the old 2.1.1 package, then install 2.1.2, will
> kdelibs-sound be OK with that? Or will it still be looking for arts 2.1.1
> (and therefore break).
>
If you follow that path, your system could be OK... or not (you can't
know for sure). Note that your rpm databse "insists" that it needs
*exactly* version 2.1.1 for kdelibs-sound-2.1.1-5 to be "glad".
> That's just a couple of examples, but I guess what I'm looking for is a more
> general answer - what's the normal procedure for keeping a Linux box
> up-to-date? Is it the same set of commands that I just issue each time I
> download an updated RPM? And can I automate the process (through autorpm or
> some such tool)?
>
I suggest doing it step by step, looking at least once a week for newer
packages, and, although possible, don't try to automate: while most
times the upgrade goes flawlessly, you can't know for sure: some
packages are not too gentle and (for instance) will move the config
files of the older version to config_file.conf.rpmold, or the new will
go as config_file.conf.rpmnew, and you should control it because of new
config file parameters you should review for the new version to work
properly, and so on.
--
SALUD,
Jes�s
***
[EMAIL PROTECTED]
***
------------------------------
From: "Arnd-Eike Br�dern" <[EMAIL PROTECTED]>
Subject: smb_print
Date: Fri, 18 May 2001 15:06:24 +0200
Hi all,
I want to print with samba to a remote NT printer.
But every user need his own settigs(username and pw)
for pay the printjobs.
In the global settingsfile (/etc/apsfilterrc.printer) are the
path of the remoteprinter, usnername and pw.
In the userfile for printjob ($HOMEDIR/.apsfilterrc), i can't
edit this important things.
Can somebody get a solution of this problem.
Thanks.
PS.: My System is SuSe-Linux 7.1
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list by posting to comp.os.linux.setup.
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Setup Digest
******************************
