Linux-Setup Digest #816, Volume #20 Tue, 13 Mar 01 03:13:10 EST
Contents:
Re: installing KDE2 on RedHat 7 based setup ("Robert L. Cochran Jr.")
Fdisk acting strange ("J.Paul Rinehimer")
X Windows Crashes After Random Period (Darren O'Connor)
Re: LAN server + internet (Slackware 7.1, newbie) ("Phillip Qin")
Re: newbie Telnet question ([EMAIL PROTECTED])
Re: Linux and large (>32GB) hard disk ("Matthew Lam")
Re: DPT SmartRAID VI on BIG server ("Deanna")
Re: Best Partitioning Practice ? ("Eric")
Re: Fdisk acting strange ("Eric")
Re: Squid cache size? (Michael Heiming)
Re: Fdisk acting strange ([EMAIL PROTECTED])
----------------------------------------------------------------------------
From: "Robert L. Cochran Jr." <[EMAIL PROTECTED]>
Subject: Re: installing KDE2 on RedHat 7 based setup
Date: Tue, 13 Mar 2001 00:22:32 -0500
I wonder if Red Hat has a version of YAST or YAST2 (Yet Another Setup =
Tool) that can take care of this for you. The SuSE version of YAST2 is =
really neat for subsequent package upgrades.
"Darin Johnson" <[EMAIL PROTECTED]> wrote in message =
news:[EMAIL PROTECTED]...
> How can I install KDE2 easily on a RedHat 7 based setup? There are a
> lot of dependencies that are tricky to work out. Ie, prerequisite
> libraries; a few existing KDE packages required cause conflicts with
> newer packages, but removing them breaks dependencies, etc. Gnorpm
> isn't working well (behind a firewall, and I can't even set it's
> preferences to look at local disk).
------------------------------
From: "J.Paul Rinehimer" <[EMAIL PROTECTED]>
Subject: Fdisk acting strange
Date: Tue, 13 Mar 2001 00:24:40 -0500
Hi,
I recently installed Linux onto my computer to set up a dual boot
system. The toughest part was the partitioning. For some reason, DOS's
fdisk wouldn't let me create partitions bigger than 2 gigs. I know
about the FAT16 and it not be able to handle partitions larger than 2
gigs. I had done a complete reformat of the drive and was using the
Win98SE version of fdisk and was using a 19.5 GB hd and it just wouldn't
recognize it. I also got no question about using LBA (is that the
acronym?) to set up a large hard drive. Also, when I tryed partitioning
with Linux's fdisk, windoze continued to believe it had the entire hard
drive to itself.
Well I decided to use fips. I had turned the hd into one big
partition and installed Win98SE. When I ran fips, it wouldn't let me
change the partition size in either direction (aka, I hit the keys and
nothing happened....it is the arrow keys right? I tried every other one
and must have looked at the directions like 20 times) Well, I copied a
bunch of stuff onto my hard drive and then when it was as full as I'd
like my win partittion to be, I used fips and everything works. Then I
deleted the stuff and defragmented. (It wasn't the best way, but it
worked)
Anyways, my system is currently working, both Linux and windoze
are running fine. I'm still having trouble getting my ethernet card to
work in Linux and getting the xserver to run, but i'm working on it. I
wrote this to see if anyone would know why I wasn't able to partition it
correctly, especially fdisk not being able to make >2gb partitions when
it should have and fips not being able to change partition sizes.
Thanks for any information in advance.
------------------------------
Date: Mon, 12 Mar 2001 21:13:49 -0800
From: Darren O'Connor <[EMAIL PROTECTED]>
Subject: X Windows Crashes After Random Period
Crossposted-To: comp.os.linux.x
Adding to my previous post...
I logged all of the X windows messages, as follows, in the hope that it
sheds some light.
=================
xauth: creating new authority file /home/odarren/.Xauthority
XFree86 Version 3.3.6 / X Window System
(protocol Version 11, revision 0, vendor release 6300)
Release Date: January 8 2000
If the server is older than 6-12 months, or if your card is newer
than the above date, look for a newer version before reporting
problems. (see http://www.XFree86.Org/FAQ)
Operating System: Linux 2.2.5-22smp i686 [ELF]
Configured drivers:
SVGA: server for SVGA graphics adaptors (Patchlevel 1):
s3_savage, NV1, STG2000, RIVA 128, RIVA TNT, RIVA TNT2,
RIVA ULTRA TNT2, RIVA VANTA, RIVA ULTRA VANTA, RIVA INTEGRATED,
GeForce 256, GeForce DDR, Quadro, ET4000, ET4000W32, ET4000W32i,
ET4000W32i_rev_b, ET4000W32i_rev_c, ET4000W32p, ET4000W32p_rev_a,
ET4000W32p_rev_b, ET4000W32p_rev_c, ET4000W32p_rev_d, ET6000,
ET6100,
et3000, pvga1, wd90c00, wd90c10, wd90c30, wd90c24, wd90c31,
wd90c33,
gvga, r128, ati, sis86c201, sis86c202, sis86c205, sis86c215,
sis86c225, sis5597, sis5598, sis6326, sis530, sis620, sis300,
sis630,
sis540, tvga8200lx, tvga8800cs, tvga8900b, tvga8900c, tvga8900cl,
tvga8900d, tvga9000, tvga9000i, tvga9100b, tvga9200cxr,
tgui9400cxi,
tgui9420, tgui9420dgi, tgui9430dgi, tgui9440agi, cyber9320,
tgui9660,
tgui9680, tgui9682, tgui9685, cyber9382, cyber9385, cyber9388,
cyber9397, cyber9520, cyber9525, 3dimage975, 3dimage985,
cyber9397dvd,
blade3d, cyberblade, clgd5420, clgd5422, clgd5424, clgd5426,
clgd5428,
clgd5429, clgd5430, clgd5434, clgd5436, clgd5446, clgd5480,
clgd5462,
clgd5464, clgd5465, clgd6205, clgd6215, clgd6225, clgd6235,
clgd7541,
clgd7542, clgd7543, clgd7548, clgd7555, clgd7556, ncr77c22,
ncr77c22e,
cpq_avga, mga2064w, mga1064sg, mga2164w, mga2164w AGP, mgag200,
mgag100, mgag400, oti067, oti077, oti087, oti037c, al2101,
ali2228,
ali2301, ali2302, ali2308, ali2401, cl6410, cl6412, cl6420,
cl6440,
video7, ark1000vl, ark1000pv, ark2000pv, ark2000mt, mx, realtek,
s3_virge, AP6422, AT24, AT3D, s3_svga, NM2070, NM2090, NM2093,
NM2097,
NM2160, NM2200, ct65520, ct65525, ct65530, ct65535, ct65540,
ct65545,
ct65546, ct65548, ct65550, ct65554, ct65555, ct68554, ct69000,
ct64200, ct64300, mediagx, V1000, V2100, V2200, p9100, spc8110,
i740,
i740_pci, Voodoo Banshee, Voodoo3, i810, i810-dc100, i810e, smi,
generic
(using VT number 7)
XF86Config: /usr/X11R6/lib/X11/XF86Config
(**) stands for supplied, (--) stands for probed/default values
(**) Mouse: type: PS/2, device: /dev/psaux, buttons: 3
(**) XKB: rules: "xfree86"
(**) XKB: model: "pc101"
(**) XKB: layout: "us"
(**) XKB: variant: ""
(**) XKB: options: ""
(**) SVGA: Graphics device ID: "Cirrus Logic GD5465"
(**) SVGA: Monitor ID: "ViewSonic GT775"
(--) SVGA: Mode "320x240" needs hsync freq of 31.47 kHz. Deleted.
(--) SVGA: Mode "640x480" needs hsync freq of 31.47 kHz. Deleted.
Warning: The directory "/usr/X11R6/lib/X11/fonts/TrueType" does not
exist.
Entry deleted from font path.
(**) FontPath set to "unix/:7100"
(--) SVGA: PCI: Cirrus Logic GD5465 rev 2, Memory @ 0xcc000000, MMIO @
0xcfef0000
(--) SVGA: chipset: clgd5465
(**) SVGA: videoram: 4096k
(--) SVGA: clocks: 25.23 28.32 41.16 36.08 31.50 39.99 45.08
49.87
(--) SVGA: clocks: 64.98 72.16 75.00 80.01 85.23 90.00 95.02
100.23
(--) SVGA: clocks: 108.03 109.77 120.05 126.00 130.06 135.00
(**) SVGA: Using 32 bpp, Depth 24, Color weight: 888
(--) SVGA: Maximum allowed dot-clock: 135.100 MHz
(**) SVGA: Mode "1024x768": mode clock = 75.000, clock used = 74.999
(--) SVGA: clgd5465: Display width padded to 4096 bytes.
(--) SVGA: Virtual resolution set to 1024x768
(--) SVGA: PCI: Memory @ 0xcc000000, I/O @ 0xcfef0000
(--) SVGA: clgd5465: Using linear framebuffer at 0xcc000000 (3264MB)
(--) SVGA: clgd5465: 1048576 bytes off-screen memory available
(--) SVGA: clgd5465: Using hardware cursor
(--) SVGA: clgd5465: Using accelerator functions
(--) SVGA: clgd5465: Using BitBLT engine
(--) SVGA: clgd5465: Using memory-mapped I/O at address 0xCFEF0000
(**) SVGA: clgd5465: Internal memory clock register set to 0x12
(**) SVGA: clgd5465: Approximate DRAM bandwidth for drawing: 215 of 515
MB/s
(--) SVGA: Using XAA (XFree86 Acceleration Architecture)
(--) SVGA: XAA: Solid filled rectangles
(--) SVGA: XAA: Screen-to-screen copy
(--) SVGA: XAA: 8x8 color expand pattern fill
(--) SVGA: XAA: Using 8 128x128 areas for pixmap caching
(--) SVGA: XAA: Caching tiles and stipples
(--) SVGA: XAA: Horizontal and vertical lines and segments
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/702
Xlib: extension "XINERAMA" missing on display ":0.0".
SetKbdSettings - type: 2 rate: 5 delay: 500 snumlk: 0
SetKbdSettings - Succeeded
subshell.c: couldn't get terminal settings: Inappropriate ioctl for
device
** WARNING **: get_task_root_and_frame(): task window id 46137411
invalid?
waiting for X server to shut down
------------------------------
From: "Phillip Qin" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking
Subject: Re: LAN server + internet (Slackware 7.1, newbie)
Date: Tue, 13 Mar 2001 05:47:19 GMT
Look at DSL-HOWTO on linuxdoc.
"Dean Thompson" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
>
> Hi Pawel,
>
> > I have:
> > - router: DSLPipe DSL-HST-E , Lucent Techn. (www.lucent.com),
> > - IP: 62.148.92.226-230,
> > - netmask: 255.255.255.248,
> > - DNS: 195.114.161.2 (and three more),
> > - One PC with two network adapters.
> > - of course I have the network (hub + some computers) :-)
>
> You might like to take a look at the NET-HOWTO and the Mini-Networking
HOWTO
> guides which are located at: http://www.linuxdoc.org. In brief however,
> providing that your network card is actually identified by linux and that
the
> following command returns a line:
>
> cat /var/log/dmesg | grep eth
>
> you can take a look at the /etc/sysconfig/network,
> /etc/sysconfig/network-scripts/ifcfg-eth0 and /etc/resolv.conf file. This
is
> where you define all of the network settings.
>
> This should be a good starting point.
>
> See ya
>
> Dean Thompson
>
> --
>
+____________________________+____________________________________________+
> | Dean Thompson | E-mail - [EMAIL PROTECTED]
|
> | Bach. Computing (Hons) | ICQ - 45191180
|
> | PhD Student | Office - <Off-Campus>
|
> | School Comp.Sci & Soft.Eng | Phone - +61 3 9903 2787 (Gen. Office)
|
> | MONASH (Caulfield Campus) | Fax - +61 3 9903 1077
|
> | Melbourne, Australia |
|
>
+----------------------------+--------------------------------------------+
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: newbie Telnet question
Date: 13 Mar 2001 06:47:42 GMT
148.156.9.91 <[EMAIL PROTECTED]> wrote:
> Here's the stupid question: Where do I configure users and permissions for
> the remote
> telnet clients so that I can administer remotely? I've been unsuccessful in
> locating any
> information on this. Any help?
The remote system must be validated locally, you must define
a user and/or a group, and manage the security of the user/group
locally. Then, you can allow only that user to telnet in.
Davide
------------------------------
From: "Matthew Lam" <[EMAIL PROTECTED]>
Subject: Re: Linux and large (>32GB) hard disk
Date: Tue, 13 Mar 2001 13:31:07 +0800
Hi,
I had the same problem that the IBM-DTLA-307045 isn't detected by my BIOS.
What I did was to leave the jumpers in their default positions, put the hard
disk on a channel other than the Primary Master, set the BIOS to NONE for
that channel, put a smaller hard disk on the Primary Master and boot from
it. Linux will recognize the 45GB even though it's not reported by BIOS. I
was using Redhat 6.2 but think other distro will also do.
"Alan Morgan" <[EMAIL PROTECTED]> wrote in message
news:98k31c$m64$[EMAIL PROTECTED]...
> I've read the HOWTO on this, but it don't really answer my
> question. Actually, I think I have a solution, I just want to
> make sure that I'm on the right track.
>
> My IBM IDE hard disk is 45GB. My BIOS only handles up to 33.8GB.
> IBM has a solution - you tell the hard disk to lie to the BIOS and
> then install a disk overlay (OnTrack disk manager) that reports the
> correct size after the system boots up. The only problem is that
> you have to boot from that hard disk in order for the overlay to
> take effect. If you boot from another disk, or from the CD-ROM, no
> dice.
>
> I'm trying to install a new Slackware and the installation boots off
> of the CD-ROM - so I don't see the full size of the disk.
>
> My solution is to say "to heck with it" and create my partitions anyway,
> putting /home last, and then installing normally. Then when I boot
> up I can use fdisk to extend (actually, destroy and recreate) the last
> partition, format it, and I'm good to go.
>
> At least, that's my hope. The IBM documentation describes how to use
> their software for Linux but it appears to be written for a different
> version of their software and since it is step-by-step instead of
> big-picture instructions it isn't clear to me what they are trying to
> do.
>
> To those who have done this sort of thing before, does my approach make
> sense or is there some incredibly easy approach that I've missed?
> Everything appears to work so far.
>
> Alan
------------------------------
From: "Deanna" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware,comp.os.linux.misc
Subject: Re: DPT SmartRAID VI on BIG server
Date: Tue, 13 Mar 2001 06:59:07 GMT
Hey
I work for Adaptec writing the driver for that card. The problem is that
the default configuration has 1G of vm space for the kernel. When the
kernel initializes the first thing it does is map all of available RAM into
the kernel vm space (leaving a 64M moat at the top). This space is used for
loading modules and ioremapping. The old driver would try to map the 1M of
io space for the i2o transactions plus all of the cache on the card into the
kernel vm space. Depending on how many modules you have loaded and how much
cache you have, you quickly run out of free vm mapping. To compound the
problem the vmalloc routine did not always properly return NULL when it ran
out of space, so when the driver loaded it did not get mapped but it did not
know it.
One fix for the problem is to recompile the kernel with the 2G option set
(BIGMEM does not seem to fix it). The other is to try the new driver. It
has a much smaller memory footprint and does not try to map in the cache.
Contact me at [EMAIL PROTECTED] for the new driver.
Deanna
"Doug Forbush" <[EMAIL PROTECTED]> wrote in message
news:96e1nn$hfm$[EMAIL PROTECTED]...
> I put together a linux box at work here, it has the DPT smartRaid VI.. It
> also has 2G of RAM on it.. The install was great, simple kernel patch,
> compile and install.. The RAID works great IF I tell linux that there is
> only 900M RAM.. I'm not sure exactly how high I can go, but at 960M, the
> RAID initialization fails and /dev/sdc is not there..
>
> Any ideas on why this happens and how to get back over a gig of RAM?
>
> doug
>
>
------------------------------
From: "Eric" <[EMAIL PROTECTED]>
Subject: Re: Best Partitioning Practice ?
Date: Tue, 13 Mar 2001 08:16:41 +0100
> >> I tried to install Linux into an Extended partition and it didn't like
it.
>
> > Sure it does.
> > No reason why linux would even care about it.
> > Booting it may be somewhat more troublesome this way,
> > but even that's not too hard.
>
> I didn't address this question in my other post, but I was wondering if
> he made the extended partition with DOS fdisk. I've never created
extended/
> logical partitions with DOS fdisk for use with anything other than
DOS/Windows.
> I would think/hope that it wouldn't matter, but I normally expect MS to
put
> something in there to break compatibility.
>
It will probably be alright, although whenever you use multiple fdisks to
create a
partition table, you should always check it, and verify that it created the
partitions
as you expected. (correct CHS values, correct type etc.)
Eric
------------------------------
From: "Eric" <[EMAIL PROTECTED]>
Subject: Re: Fdisk acting strange
Date: Tue, 13 Mar 2001 08:32:37 +0100
> I recently installed Linux onto my computer to set up a dual boot
> system. The toughest part was the partitioning. For some reason, DOS's
> fdisk wouldn't let me create partitions bigger than 2 gigs.
So use linux' fdisk
I don't know enough about the DOS FDISK.
> I know
> about the FAT16 and it not be able to handle partitions larger than 2
> gigs. I had done a complete reformat of the drive and was using the
> Win98SE version of fdisk and was using a 19.5 GB hd and it just wouldn't
> recognize it.
Then the BIOS probably didn't recognise it either?
Windows tends to believe whatever the BIOS reports.
> I also got no question about using LBA (is that the
> acronym?) to set up a large hard drive.
It will come up when the number of cylinders are 1024 or above IIRC.
If the BIOS masked that, because it couldn't detect the whole disc,
it indeed wouldn't show up.
> Also, when I tryed partitioning
> with Linux's fdisk, windoze continued to believe it had the entire hard
> drive to itself.
buggy windows.
Was this by any chance an OEM windows disc?
Then it probably wants to take over the entire disc.
Disregarding any current partition-table.
Install it first, and hope you never need to reinstall.
> Well I decided to use fips. I had turned the hd into one big
> partition and installed Win98SE.
probably your only choice.
> When I ran fips, it wouldn't let me
> change the partition size in either direction (aka, I hit the keys and
> nothing happened....it is the arrow keys right? I tried every other one
> and must have looked at the directions like 20 times) Well, I copied a
> bunch of stuff onto my hard drive and then when it was as full as I'd
> like my win partittion to be, I used fips and everything works. Then I
> deleted the stuff and defragmented. (It wasn't the best way, but it
> worked)
Whatever works. It is windows: it acts weird.
> Anyways, my system is currently working, both Linux and windoze
> are running fine. I'm still having trouble getting my ethernet card to
> work in Linux and getting the xserver to run, but i'm working on it. I
> wrote this to see if anyone would know why I wasn't able to partition it
> correctly, especially fdisk not being able to make >2gb partitions when
> it should have and fips not being able to change partition sizes.
FIPS might refuse because some system files existed near the end of the
partition. Defrag first, then use FIPS.
why FDISK failed? I don't have a clue.
Eric
------------------------------
Date: Tue, 13 Mar 2001 08:01:57 +0100
From: Michael Heiming <[EMAIL PROTECTED]>
Subject: Re: Squid cache size?
Rasmus B�g Hansen wrote:
>
> Thanks for the fast answer.
>
> On Mon, 12 Mar 2001, Michael Heiming wrote:
>
> > from my expirience, squid performance depends on the RAM settings in
> > squid.conf, the defaults are very low ~8 MB, if I remember right, just
> > be aware, that squid uses 3 x the memory you set in squid.conf (cache_mem).
> > But if you have enough, why not let squid use it.
>
> Eh, actually it has got no RAM, that's why I ask. I could go for 128Mb
> RAM and a 45 Gb disk or just 256Mb RAM. Perhaps I could find money for
> more, but I do not really think so... The box is not going to do
> anything else than proxying (well, also network filtering, but that
> should not take up huge amounts of memory).
>
> > If the 45 GB disc is not that slow, compared with the 3 GB, I would go for
> > the big one, just remember to check the cache size, from time to time, or
> > even better, write a small script that mails you the cache usage, periodicaly.
>
> Actually I believe the 45Gb disk to be faster than the 3Gb one (I do not
> know the speeds of the 3Gb one)
Check with hdparm -t /dev/your_disc.
>. Yeah, I know the usage of IDE disks is
> discouraged, but there is not money for scsi...
>
> > http://www.squid-cache.org/
> > Has a well written FAQ, if you didn't saw it.
>
> Thanks for the link. I'm still a little puzzled whether to choose the
> 45Gb+128Mb or the 3Gb+256Mb. I think it will be the 3Gb+256Mb - any
> opinions?
Huh, hard to tell, you have to clean up the cache more often if you cache disc
is not that big, I'm a bit curious, as you wrote that you set it up for ~200 users
and your company has no money for RAM and disc, which is both rather cheap.
I would go with the RAM and change chache_mem as I wrote, this will perhaps speed
squid more up than the bigger disc only. But I didn't tried this, cause RAM and disc
needed were never a question were I setup things like this.
Michael Heiming
>
> Rasmus
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Fdisk acting strange
Date: 13 Mar 2001 07:56:43 GMT
J.Paul Rinehimer <[EMAIL PROTECTED]> wrote:
> system. The toughest part was the partitioning. For some reason, DOS's
> fdisk wouldn't let me create partitions bigger than 2 gigs.
Dos fdisk is quite old and does not handle partition bigger than 2 Gb.
The fdisk shipped with Win 98 si better (if you need it).
> I also got no question about using LBA (is that the
> acronym?)
That should be in the BIOS, not in the fdisk...
> with Linux's fdisk, windoze continued to believe it had the entire hard
...Windows is difficult to convince...
Davide
------------------------------
** 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
******************************
