Linux-Misc Digest #462, Volume #26 Mon, 4 Dec 00 04:13:02 EST
Contents:
Re: Corel Linux VS Redhat 7 ([EMAIL PROTECTED])
Re: Network problem: don't know where to look ([EMAIL PROTECTED])
Re: Badly need help with a freezing box ([EMAIL PROTECTED])
Re: Mouse is jumpy in X (Eric)
Trident CyberBlade i7 on HP Omnibook Xe2 doesn't work under X!! Help me!!
("Morpheus")
Re: Cannot telnet nor ftp to server ([EMAIL PROTECTED])
thread, task and process (Snoopy)
Re: HELP, need original smb.conf ([EMAIL PROTECTED])
Monitoring host with ping (Jimmy Navarro)
Re: RedHat, Compaq Proliant 4500R, & NCR53C825 EISA ("Jeremy Rogers")
Re: Freezing Box - *whimper* ("Peter T. Breuer")
Re: Kernel won't mount raid0 ("Peter T. Breuer")
Re: NFS setup question (insecure port??) ("Peter T. Breuer")
Re: Corel Linux VS Redhat 7 ("William Pelish")
----------------------------------------------------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Corel Linux VS Redhat 7
Date: 4 Dec 2000 08:26:27 +0100
Rex Dieter <[EMAIL PROTECTED]> wrote:
> This is a multi-part message in MIME format.
> --------------47B62F93EF32F83EEDBE59F5
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
To put it in just a few words: don't use MIME in non binary newsgroups ;-)
> [EMAIL PROTECTED] wrote:
>>
>> William Pelish <[EMAIL PROTECTED]> wrote:
>> > I wish to know if anyone here has used Corel Linux Deluxe and if you have
>> > found any bugs. Also if you have also tried RH 7 and found any difference
>> > between the too. I am trying to decide which one to use for a server for my
>> > webhosting.
>>
>> Don't use Redhat 7: stick with 6.2.
> V7 really is much better than the 6.x series. I doubt that I'll be able
> to convince you, but I hope others don't base their opinions on your
> rant.
>>Version 7.0 may well be the worst Redhat release
>> ever! It's got quite a lot of bugs,
> Do you have any evidence of this?
Let's see: it won't configure your keyboard properly if you select a non-US layout.
The up2date daemon shipping with the distribution will lock up the system after
a few days because it leaks file descriptors.
the standard compiler is an unstable development snapshot of gcc, so that cygnus
themselves
(now owned by redhat) have had to announce that 2.96 was _not_ an official release.
This really sounds like a .0 distribution to me...
>>ships with an unstable compiler unable to
>> build the LInux kernel, and so on.
> For fact to refute this mis-information, see:
> http://www.redhat.com/support/docs/gotchas/7.0/gotchas-7-6.html#ss6.1
I'm not saying that it's impossible to correct some of those bu^H^Hfeatures,
but it shouldn't be necessary in the first place.
> --------------47B62F93EF32F83EEDBE59F5
> Content-Type: text/x-vcard; charset=us-ascii;
> name="rdieter.vcf"
Don't do that either!
--
Alain Borel
<[EMAIL PROTECTED]>
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Network problem: don't know where to look
Date: Mon, 04 Dec 2000 07:23:25 GMT
In article <[EMAIL PROTECTED]>,
Jan Erik Mostr�m <[EMAIL PROTECTED]> wrote:
> I'm slowly getting desperate over my Linux machine ...
> frankly I (and yes I'm a newbie to Linux) have no idea
> what to do to get it to connect to my network at home.
> And I would be VERY GRATEFUL if someone could help me
> in getting it up and running.
>
> Here are the facts:
>
> My network at home
>
> Mac G4 ----------- Hub -------- PowerBook
> (IP 10.1.1.2) | (IP 10.1.1.3)
> |
> |
> PC running SuSE
> (IP 10.1.1.11)
I don't know much about MACs, so I have to ask if they are running
TCP/IP? I'm wondering if these computers are using the same protocol?
Dan
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Badly need help with a freezing box
Date: Mon, 04 Dec 2000 07:30:03 GMT
I had a box doing something similar, although not at a particular time.
My problem turned out to be my graphics card. System only locked up
when I was running X. If your box is freezing at a certain time, I
would take a look at any cron jobs starting around that time period.
HTH
In article <90eo20$qkt$[EMAIL PROTECTED]>,
[EMAIL PROTECTED] wrote:
> Please help! I am but a humble trainee with no clue as to why this is
> happening. Any more freezes ( it's now once a day, at half three in
the
> afternoon, bang on time - sometimes more ), and they are probably
going
> to cancel the contract, and as we are such a new company, we need all
> the contracts we can get!
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: Eric <[EMAIL PROTECTED]>
Subject: Re: Mouse is jumpy in X
Date: Mon, 04 Dec 2000 08:43:44 +0100
Reply-To: [EMAIL PROTECTED]
> hi thankx for the help
> but it didnt work i have a serial mouse im not sure what protocal to use
> but i tried mousesystems,IMPS/2 and microsoft,
> the microsoft one works ok outside of X but not in
> if u have any other surgestions please post
> thanx again
>
Okay, then take a look at the manpages (xf86config, XF86Config etc) to
see what other mouse protocols are possible. The are a few there for
serial mice.
Eric
------------------------------
From: "Morpheus" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware,comp.os.linux.x,free.it.linux
Subject: Trident CyberBlade i7 on HP Omnibook Xe2 doesn't work under X!! Help me!!
Date: Mon, 04 Dec 2000 07:48:28 GMT
I've an HP Omnibook Xe2 with a Trident CyberBlade i7 video card, it should
be supported by newer versions of XFree such as XFree86 3.6 or XFree86 4.0
but I can't make it work! I've installed Linux Red Hat 6.0 with XFree 3.3
first and XFree 3.6 after but the graphic can't start. I've also tried to
enable the VESA frame buffer by adding the line VGA=789 in my lilo.conf and
by using the XFree86_FBDEV server but the message is:
XFree86 Version 3.3.3.1 / X Window System
(protocol Version 11, revision 0, vendor release 6300)
Release Date: January 4 1999
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.1-ac1 i686 [ELF]
Configured drivers:
FBDev: Server for frame buffer device
(Patchlevel 10): mfb, cfb8, cfb16, cfb24, cfb32
(using VT number 7)
XF86Config: /usr/X11R6/lib/X11/XF86Config
(**) stands for supplied, (--) stands for probed/default values
(**) XKB: keycodes: "xfree86"
(**) XKB: types: "default"
(**) XKB: compat: "default"
(**) XKB: symbols: "us(pc101)"
(**) XKB: geometry: "pc"
(**) XKB: rules: "xfree86"
(**) XKB: model: "pc101"
(**) XKB: layout: "it"
(**) Mouse: type: PS/2, device: /dev/mouse, buttons: 3
(**) Mouse: 3 button emulation (timeout: 50ms)
(**) FBDev: Graphics device ID: "CyberBlade"
(**) FBDev: Monitor ID: "LCD Panel 800x600"
(--) FBDev: Mode "800x600" needs hsync freq of 48.08 kHz. Deleted.
(--) FBDev: Mode "800x600" needs hsync freq of 55.84 kHz. Deleted.
(--) FBDev: Mode "800x600" needs hsync freq of 64.02 kHz. Deleted.
(**) FontPath set to "unix/:-1"
(**) FBDev: Using XF86Config video mode database
Fatal server error:
No valid modes found.
same as when I try with XFree86_SVGA server.
I've configured the server by editing the XF86Config file as:
# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
RgbPath "/usr/X11R6/lib/X11/rgb"
# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.
FontPath "unix/:-1"
EndSection
# **********************************************************************
# Server flags section.
# **********************************************************************
Section "ServerFlags"
# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
#NoTrapSignals
# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
#DontZap
# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
#DontZoom
EndSection
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Keyboard section
# **********************************************************************
Section "Keyboard"
Protocol "Standard"
# when using XQUEUE, comment out the above line, and uncomment the
# following line
#Protocol "Xqueue"
AutoRepeat 500 5
# Let the server do the NumLock processing. This should only be
# required when using pre-R6 clients
#ServerNumLock
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#Xleds 1 2 3
#To set the LeftAlt to Meta, RightAlt key to ModeShift,
#RightCtl key to Compose, and ScrollLock key to ModeLock:
LeftAlt Meta
RightAlt Meta
ScrollLock Compose
RightCtl Control
# To disable the XKEYBOARD extension, uncomment XkbDisable.
# XkbDisable
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# XkbModel "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# XkbModel "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# XkbLayout "de"
# or:
# XkbLayout "de"
# XkbVariant "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# XkbOptions "ctrl:swapcaps"
# These are the default XKB settings for XFree86
# XkbRules "xfree86"
# XkbModel "pc101"
# XkbLayout "us"
# XkbVariant ""
# XkbOptions ""
XkbKeycodes "xfree86"
XkbTypes "default"
XkbCompat "default"
XkbSymbols "us(pc101)"
XkbGeometry "pc"
XkbRules "xfree86"
XkbModel "pc101"
XkbLayout "it"
EndSection
# **********************************************************************
# Pointer section
# **********************************************************************
Section "Pointer"
Protocol "PS/2"
Device "/dev/mouse"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Protocol "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice
# BaudRate 9600
# SampleRate 150
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
Emulate3Buttons
Emulate3Timeout 50
# ChordMiddle is an option for some 3-button Logitech mice
# ChordMiddle
EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
Section "Monitor"
Identifier "LCD Panel 800x600"
VendorName "Unknown"
ModelName "Unknown"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
HorizSync 31.5-37.9
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
VertRefresh 56-62
# 800x600 @ 56 Hz, 35.15 kHz hsync
ModeLine "800x600" 36 800 824 896 1024 600 601 603 625
# 800x600 @ 60 Hz, 37.8 kHz hsync
Modeline "800x600" 40 800 840 968 1056 600 601 605 628 +hsync
+vsync
# 800x600 @ 72 Hz, 48.0 kHz hsync
Modeline "800x600" 50 800 856 976 1040 600 637 643 666 +hsync
+vsync
# 800x600 @ 85 Hz, 55.84 kHz hsync
Modeline "800x600" 60.75 800 864 928 1088 600 616 621
657 -HSync -VSync
# 800x600 @ 100 Hz, 64.02 kHz hsync
Modeline "800x600" 69.65 800 864 928 1088 600 604 610
640 -HSync -VSync
EndSection
# **********************************************************************
# Graphics device section
# **********************************************************************
# Device configured by myself :
Section "Device"
Identifier "CyberBlade"
VendorName "Trident"
BoardName "CyberBlade i7"
VideoRam 4096
Clocks 25.18
EndSection
# **********************************************************************
# Screen sections
# **********************************************************************
# The Colour SVGA server
Section "Screen"
Driver "svga"
Device "CyberBlade"
Monitor "LCD Panel 800x600"
Subsection "Display"
Depth 8
Modes "800x600"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "800x600"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 32
Modes "800x600"
ViewPort 0 0
EndSubsection
EndSection
# The frame buffer server
Section "Screen"
Driver "fbdev"
Device "CyberBlade"
Monitor "LCD Panel 800x600"
Subsection "Display"
Depth 8
# Omit the Modes line for the "Generic VGA" device
Modes "800x600"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "800x600"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 32
Modes "800x600"
ViewPort 0 0
EndSubsection
EndSection
I can't understand what doesn't work with my graphic card, so I pray someone
to help me to resolve this problem. Thanks for all!!!
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Cannot telnet nor ftp to server
Date: Mon, 04 Dec 2000 07:40:38 GMT
Check:
/etc/hosts.allow
Also, since your running ipchains, check:
/etc/ppp/ipmasq
In article <[EMAIL PROTECTED]>,
"Rick Goh" <[EMAIL PROTECTED]> wrote:
> I cannot telnet nor FTP to my server: linux kernel 2.2.17.
> i am running IP MASQ (i wonder if this would affect).
>
> Error msg:
> "Connection closed by foreign host."
>
> Note: Yes, i have inet started. i even started xinetd. But just can't
work.
>
> If have come across this same problem, please reply..
>
> Regards.
>
>
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: Snoopy <[EMAIL PROTECTED]>
Subject: thread, task and process
Date: Mon, 04 Dec 2000 00:45:45 -0700
Hello
I was reading Linux Kernel document and found some questions I did
not understand.
The author states that TASK and PROCESS are used interchangeable in
this document and I can understand this but where is the concept of
THREAD? Are they all the SAME concept? If they ARE the same, the max
number of threads is restricted within 512, does it means that only 512
threads are allowed in a Linux system?
Thanks
STC
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: HELP, need original smb.conf
Date: Mon, 04 Dec 2000 07:47:04 GMT
Try re-installing the RPM. I would email you mine, but it's been
modified...if you want it anyways, send me an email and I will attach
it to you.
[EMAIL PROTECTED]
In article <[EMAIL PROTECTED]>,
"Evan Panagiotopoulos" <[EMAIL PROTECTED]> wrote:
> In the process of configuring smb.conf I must of erased the contents
of it!
> I was using vi, I don't understand how it happened. Where can I get a
copy
> of it?
>
> Thanks,
>
> --
> Evan Panagiotopoulos
> Technology, Library and Media Director
> Poughkeepsie City School District
>
>
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: Jimmy Navarro <[EMAIL PROTECTED]>
Subject: Monitoring host with ping
Date: Mon, 04 Dec 2000 00:02:56 -0800
SSB3YXMgdHJ5aW5nIGEgc2FtcGxlIHNoZWxsIHNjcmlwdCBuYW1lZCBXcGluZy5zaCB0byBt
b25pdG9yIGFuDQpleHBlcmltZW50YWwgdmlydHVhbCBkb21haW4gV2ViIHNlcnZlciB0byBw
aW5nIGV2ZXJ5IDEwIG1pbnV0ZXMsIGlmIG5vDQpkYXRhIHBhY2tldHMgcmVjZWl2ZWQgYmFj
ayBmcm9tIHJlbW90ZSBob3N0IGl0IHNlbmRzIG1lIGUtbWFpbCBsaWtlOg0KDQojIS9iaW4v
YmFzaA0Kd2hpbGUgWyAxIF0NCmRvDQogICBQSU5HPWBwaW5nIC1jIDMgLXMgNTYgbXl3ZWJz
ZXJ2ZXIgfCBncmVwIHJlY2llaXZlZCB8IGF3ayAtRiwNCiAgICd7cHJpbnQgJDIgfScgfCBh
d2sgJ3twcmludCAkMX0nYA0KICAgaWYgWyAkUElORyAtZXEgMCBdOyB0aGVuDQogICAgICAg
ZWNobyAiWW91ciBzZXJ2ZXIgaXMgb2ZmIG5ldHdvcmsiIHwgbWFpbCAtcyAiUElORyBGQUlM
RUQiDQogICAgICAgamltbXlAZXh0cmEubGFmbi5vcmcNCiAgIGZpDQogc2xlZXAgNjAwDQog
ZG9uZQ0KDQpTb21laG93IGl0IGtlcHQgZ2V0dGluZyBlcnJvcjoNCi4vV3BpbmcuYmFzaDog
WzogLWVxOiB1bmFyeSBvcGVhdG9yIGV4cGVjdGVkDQoNClNvIEkgdGhlbiB0cmllZDoNCg0K
aWYgWyAiJFBJTkciIC0gZXEgIjAiIF07IHRoZW4gZWNobyAuLi4NCg0KaXQgc2V6Og0KDQou
L1dwaW5nLnNoOiBbOiA6IGludGVnZXIgZXhwcmVzc2lvbiBleHBlY3RlZA0KDQpBbnlvbmUg
Y2FuIGhlbHAgZm9yIGNvcnJlY3Qgc3ludGF4aW5nIHRvIHdvcmsgd2l0aCBMaW51eD8gIFRo
YW5rcy4NCg==
------------------------------
From: "Jeremy Rogers" <[EMAIL PROTECTED]>
Subject: Re: RedHat, Compaq Proliant 4500R, & NCR53C825 EISA
Date: Mon, 04 Dec 2000 08:23:07 GMT
Neil Cherry <[EMAIL PROTECTED]> wrote in article
<[EMAIL PROTECTED]>...
> I have a nice Compaq Proliant 4500R (EISA box), 3 PII/133, 128M ram,
> 1G SCSI disk. I can get RedHat to boot from the floppy and try to
> install. But when it comes time to select the SCSI device it can't
> find anything! The CDROM is good as it is needed to boot and
> initialize the machine the first time you set it up.
>
> So how do I create a RedHat 6.2 driver disk? What driver do I use (I
> tried the SYM/NCR53C8xx)? Any suggestions? I've tried the Compaq site
> and it doesn't say the 4500R/4500 is supported.
I and much fun and games with a compaq prosignia 300 and an EISA bus smart
array controller. The trick with that was to specify modules parameters of
"eisa=0x3000" where 3 represents the eisa slot number. It too had a SYM/NCR
scsi controller, but with only the CDROM attached.
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: Freezing Box - *whimper*
Date: Mon, 4 Dec 2000 09:21:07 +0100
[EMAIL PROTECTED] wrote:
> In article <90enkp$qee$[EMAIL PROTECTED]>,
> [EMAIL PROTECTED] (Bill Unruh) wrote:
>> In <90eh4g$lg1$[EMAIL PROTECTED]> [EMAIL PROTECTED] writes:
>> ]In article <[EMAIL PROTECTED]>,
>> ] [EMAIL PROTECTED] wrote:
>> ]> [EMAIL PROTECTED] wrote:
>> ]> > I work for Ossec International (ossec.com, if you're interested
>> ]> > The only clues we have to what may or may not be happening is one
>> ]entry
>> ]> > in the Apache access_log which gives a line that looks like this:
>> ]> > ^@^@^@^@^@^@^@^@^@^@^@
>> ]> > right after the freeze is registered as happening.
>> Well, I would suspect a hacker attack. Make sure that you have updated
>> all of the security stuff on the system. If suse uses rpm do
>> rpm -Va |grep '^..5'>/tmp/verify
>> and see if thee is anything suspicious. (Some of the files will
I would also suspect a hack attempt, given that signature in the logs.
> We cannot use the rpm command because our distribution of SuSE is not
> the standard one. It's a slimmed down copy of it, for security reasons.
Well, if you installed with rpm, you can check with rpm. I don't follow
your logic. You must use a stored copy of the rpm database, however.
> We check the files using MD5, and nothing appears to have been changed.
If you boot with a different kernel (from a floppy) to check, and your
stored md5sums are correct and off-machine, then you are OK.
Peter
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: Kernel won't mount raid0
Date: Mon, 4 Dec 2000 09:33:06 +0100
In comp.os.linux.misc Stephan A Suerken <[EMAIL PROTECTED]> wrote:
> "Peter T. Breuer" <[EMAIL PROTECTED]> writes:
>> In comp.os.linux.misc Stephan A Suerken <[EMAIL PROTECTED]> wrote:
>> > /dev/md0 raid0,16k,0,802eab69 /dev/hda3 /dev/hdc2
>> > oo Kernel 2.2.18pre23 and Kernel 2.2.17pre6 (both tried), with the
>> > necessary RAID options (raid0, boot) enabled. Not as modules of course.
>> > image = /vmlinuz
>> > label = Orlok_Kernel
>> > root = /dev/md0
>> > read-only
>> > vga=4
>> > append="md=0,0,16,0,/dev/hda3,/dev/hdc2"
>>
>> waaaaaaaaaaah. Raid mirror root. Bad bad bad. Can you really do this?
> No! Good (tm) idea! ;) However, I never talked of mirror mode.
Oh, raid0 isn't mirror? What is it then? Oh, I see, raid1 is simple
mirroring and raid0 is striping. Sorry, I really only use linear mode
in earnest, so I forgot.
> There is support to boot linear and striped (raid0) arrays since
> 2.2.x. I can really do this. Or, that is, I should really ought to be
> able to be doing this ;).
Yes, I know. However, very few people are doing so, and I doubt if
anyone is doing so on a pre-release kernel. Go back and try it on some
other kernels.
>> > ---
>> > EXT2-fs error (device md(9,0)): ext2_check_descriptors: Block bitmap for group 64
>not
>> > in group (block 3670038)!
That block is very far upstream for a root device! Your root is at
least 60MB in size. Well, I suppose that's OK.
>> > EXT2-fs: group descriptors corrupted!
>> > ---
>>
>> Yes, well, not surprised. Go find a kernel that is guaranteed to do
>> raid mirror root,
> As said above. All kernels >=2.2.0. There is only the uncertainty of
> me being able to read or not.
And whether or not it's been messed up in the pre-release you are
looking at.
>> CONFIG_BLK_DEV_MD=y
>> CONFIG_MD_MIRRORING=y
>> CONFIG_MD_BOOT=y
> I don't need MD_MIRRORING (raid0 only), although I actually have it in
> the kernel. As for the rest, I have it all of course.
> Imho, there must be some slight difference in creating the /dev/md0
> device between doing it from userspace via raidtools, or directly in
Well, did you say you chunked at 16? 1KB chunks would be normal if the
device file system has 1KB blocksize.
> the kernel via boot options. The second imho most likely thing is that
> I give the wrong chunk size factor. Kernel's md.txt isn't really clear
> about that.
It shouldn't matter, provided your whole device size is a multiple, of
course.
Why are you striping root? I can't think of an advantage. Root is
essentially only read once for daemons and libs and stays in memory
thereafter, so you don't get a speed up. There would be an advantage
(robustness) in having a mirrored root.
Peter
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,alt.linux,alt.os.linux
Subject: Re: NFS setup question (insecure port??)
Date: Mon, 4 Dec 2000 09:37:27 +0100
In comp.os.linux.misc Jerry McBride <[EMAIL PROTECTED]> wrote:
> In article <8s1tun$9t0$[EMAIL PROTECTED]>, [EMAIL PROTECTED] wrote:
>>When trying to mount a directory exported from a Linux (Mandrake
>>7.0) box on an AIX 4.3.2 box, the Linux box is refusing
>>the connection and giving the console message: "nfsd: request
>>from insecure port (mac addr):64971"
Change the exports entry to "insecure" (default is "secure").
> Being a NFS newbie and learning it by setting up NFS across PLIP... I ran into
> a similar mount problem that I "fixed" by using the "no-root-squashing" in the
> exports file for the target resource.
No, this is a different (non-)problem. He is making nfs calls from a
non-priviliged port. His daemon has to be configured to let that
happen. Normally it only trusts calls made by root through low (i.e.
privileged) ports.
Peter
------------------------------
From: "William Pelish" <[EMAIL PROTECTED]>
Subject: Re: Corel Linux VS Redhat 7
Date: Mon, 4 Dec 2000 03:48:38 -0500
Yes its called local bbs.
Will
<[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Rex Dieter <[EMAIL PROTECTED]> wrote:
> > This is a multi-part message in MIME format.
> > --------------47B62F93EF32F83EEDBE59F5
> > Content-Type: text/plain; charset=us-ascii
> > Content-Transfer-Encoding: 7bit
> To put it in just a few words: don't use MIME in non binary newsgroups ;-)
>
> > [EMAIL PROTECTED] wrote:
> >>
> >> William Pelish <[EMAIL PROTECTED]> wrote:
> >> > I wish to know if anyone here has used Corel Linux Deluxe and if you
have
> >> > found any bugs. Also if you have also tried RH 7 and found any
difference
> >> > between the too. I am trying to decide which one to use for a server
for my
> >> > webhosting.
> >>
> >> Don't use Redhat 7: stick with 6.2.
>
> > V7 really is much better than the 6.x series. I doubt that I'll be able
> > to convince you, but I hope others don't base their opinions on your
> > rant.
>
> >>Version 7.0 may well be the worst Redhat release
> >> ever! It's got quite a lot of bugs,
>
> > Do you have any evidence of this?
> Let's see: it won't configure your keyboard properly if you select a
non-US layout.
> The up2date daemon shipping with the distribution will lock up the system
after
> a few days because it leaks file descriptors.
> the standard compiler is an unstable development snapshot of gcc, so that
cygnus themselves
> (now owned by redhat) have had to announce that 2.96 was _not_ an official
release.
> This really sounds like a .0 distribution to me...
>
> >>ships with an unstable compiler unable to
> >> build the LInux kernel, and so on.
>
> > For fact to refute this mis-information, see:
> > http://www.redhat.com/support/docs/gotchas/7.0/gotchas-7-6.html#ss6.1
> I'm not saying that it's impossible to correct some of those
bu^H^Hfeatures,
> but it shouldn't be necessary in the first place.
>
> > --------------47B62F93EF32F83EEDBE59F5
> > Content-Type: text/x-vcard; charset=us-ascii;
> > name="rdieter.vcf"
> Don't do that either!
>
> --
> Alain Borel
> <[EMAIL PROTECTED]>
------------------------------
** 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 (and comp.os.linux.misc) via:
Internet: [EMAIL PROTECTED]
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-Misc Digest
******************************
