Linux-Setup Digest #907, Volume #19 Thu, 26 Oct 00 11:13:10 EDT
Contents:
Re: Moving /usr From One Partition To Another (Robert Kiesling)
RAID 1 ?? (" �j��")
Re: NFS help... (Robert Kiesling)
Re: mail question (Rod Smith)
Re: Old Compaq linux system? ("Kurt R. Rahlfs")
Re: Help for new Linux users (Murray Eisenberg)
Re: Win2K NTFS + Linux dual boot: LILO where? (Eric)
Installing Linux, Kernel Panic ("Brad K")
Re: Moving /usr From One Partition To Another (Eric)
----------------------------------------------------------------------------
Subject: Re: Moving /usr From One Partition To Another
From: Robert Kiesling <[EMAIL PROTECTED]>
Date: Thu, 26 Oct 2000 14:37:31 GMT
Eric <[EMAIL PROTECTED]> writes:
> Mike Fry wrote:
> >
> > I have a multiboot system, amongst which, one of the systems is RH 6.2 -
> > thus the strange partition arrangement.
> >
> > /dev/hdc5 contains / (root) partition, and
> > /dev/hdc7 contains /usr
> >
> > Now, I'm running out of space on /usr and cannot, for the time being,
> > add another HDD to the machine. I'd like to move /usr from /dev/hdc7 to
> > /dev/hdc5, but am unsure of how to do this. Can someone list the steps
> > that I have to go through?
> >
> > --
> > Regards, Mike Fry
> > email: [EMAIL PROTECTED]
>
> Okay, Then I'll give you a step by step help: (Robert explained the
> same, but I'll split it up in steps for you)
>
> su - root
> mkdir /new_usr
> cp -a /usr/* /new_usr
> umount /usr
> rmdir /usr
> mv /new_usr /usr
I don't *think* that /usr being a mount point should affect the
ability to rename it, but I haven't tried anything like this,
specifically, for quite some time. If that _does_ turn out to be the
case, it might be better to 'umount /usr' before renaming ('mv'ing)
the /new-usr-system to /usr.
> *now edit fstab: comment out the line with /dev/hdc7
Meaning, place a '#' at the beginning of the line using a text editor.
I doubt that's even critical with this partition setup: only the one
partition being mounted. But, as a rule, it should definitely be done
before the next reboot.
--
Robert Kiesling
Linux FAQ Maintainer
[EMAIL PROTECTED]
http://www.mainmatter.com/linux-faq/toc.html http://www.mainmatter.com/
------------------------------
From: " �j��" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware,tw.bbs.comp.linux
Subject: RAID 1 ??
Date: Thu, 26 Oct 2000 22:39:59 +0800
Hi All,
I'm trying to config a PC with 3 SCSI disks, 1 is 9.1GB , and the remain
is 18.2GB each. I would like to create a RAID 1 (mirror) for the 2 18.2GB
disks
so, I grabbed the 2.4.0-test9 kernel for testing. But during the lilo boot
process, I saw alot of "Oct 26 22:23:48 cheetah kernel: (checking disk #)" ,
what does this mean ?
Oct 26 22:23:48 cheetah kernel: raid1: device sdc1 operational as mirror 1
Oct 26 22:23:48 cheetah kernel: raid1: device sdb1 operational as mirror 0
I have configurated it with RAID 1 only, why it show sdb1 operational as
mirror 0 ??
Rgds,
Simon.H
============================================================================
============================================================================
============================
Oct 26 22:23:48 cheetah kernel: Linux version 2.4.0-test9 (root@cheetah)
(gcc version 2.95.2 20000220 (Debian GNU/Linux)) #1 Wed Oct 25 19:37:35 HKT
2000
Oct 26 22:23:48 cheetah kernel: BIOS-provided physical RAM map:
Oct 26 22:23:48 cheetah kernel: BIOS-e820: 00000000000a0000 @
0000000000000000 (usable)
Oct 26 22:23:48 cheetah kernel: BIOS-e820: 0000000000010000 @
00000000000f0000 (reserved)
Oct 26 22:23:48 cheetah kernel: BIOS-e820: 000000000fefe000 @
0000000000100000 (usable)
Oct 26 22:23:48 cheetah kernel: BIOS-e820: 0000000000002000 @
000000000fffe000 (reserved)
Oct 26 22:23:48 cheetah kernel: BIOS-e820: 0000000000080000 @
00000000fff80000 (reserved)
Oct 26 22:23:48 cheetah kernel: BIOS-e820: 0000000000010000 @
00000000fec00000 (reserved)
Oct 26 22:23:48 cheetah kernel: BIOS-e820: 0000000000010000 @
00000000fee00000 (reserved)
Oct 26 22:23:48 cheetah kernel: On node 0 totalpages: 65534
Oct 26 22:23:48 cheetah kernel: zone(0): 4096 pages.
Oct 26 22:23:48 cheetah kernel: zone(1): 61438 pages.
Oct 26 22:23:48 cheetah kernel: zone(2): 0 pages.
Oct 26 22:23:48 cheetah kernel: Kernel command line: auto BOOT_IMAGE=Linux
ro root=802 BOOT_FILE=/vmlinuz
Oct 26 22:23:48 cheetah kernel: Initializing CPU#0
Oct 26 22:23:48 cheetah kernel: Detected 797.541 MHz processor.
Oct 26 22:23:48 cheetah kernel: Console: colour VGA+ 80x25
Oct 26 22:23:48 cheetah kernel: Calibrating delay loop... 1592.52 BogoMIPS
Oct 26 22:23:48 cheetah kernel: Memory: 255672k/262136k available (1242k
kernel code, 6080k reserved, 91k data, 168k init, 0k highmem)
Oct 26 22:23:48 cheetah kernel: Dentry-cache hash table entries: 32768
(order: 6, 262144 bytes)
Oct 26 22:23:48 cheetah kernel: Buffer-cache hash table entries: 16384
(order: 4, 65536 bytes)
Oct 26 22:23:48 cheetah kernel: Page-cache hash table entries: 65536 (order:
6, 262144 bytes)
Oct 26 22:23:48 cheetah kernel: Inode-cache hash table entries: 16384
(order: 5, 131072 bytes)
Oct 26 22:23:48 cheetah kernel: CPU: Intel Pentium III (Coppermine) stepping
06
Oct 26 22:23:48 cheetah kernel: Enabling fast FPU save and restore... done.
Oct 26 22:23:48 cheetah kernel: Enabling unmasked SIMD FPU exception
support... done.
Oct 26 22:23:48 cheetah kernel: Checking 'hlt' instruction... OK.
Oct 26 22:23:48 cheetah kernel: POSIX conformance testing by UNIFIX
Oct 26 22:23:48 cheetah kernel: PCI: PCI BIOS revision 2.10 entry at
0xfc79e, last bus=1
Oct 26 22:23:48 cheetah kernel: PCI: Using configuration type 1
Oct 26 22:23:48 cheetah kernel: PCI: Probing PCI hardware
Oct 26 22:23:48 cheetah kernel: PCI: ServerWorks host bridge: secondary bus
00
Oct 26 22:23:48 cheetah kernel: PCI: ServerWorks host bridge: secondary bus
01
Oct 26 22:23:48 cheetah kernel: PCI: Using IRQ router default [1166/0200] at
00:0f.0
Oct 26 22:23:48 cheetah kernel: Linux NET4.0 for Linux 2.4
Oct 26 22:23:48 cheetah kernel: Based upon Swansea University Computer
Society NET3.039
Oct 26 22:23:48 cheetah kernel: NET4: Unix domain sockets 1.0/SMP for Linux
NET4.0.
Oct 26 22:23:48 cheetah kernel: NET4: Linux TCP/IP 1.0 for NET4.0
Oct 26 22:23:48 cheetah kernel: IP Protocols: ICMP, UDP, TCP
Oct 26 22:23:48 cheetah kernel: IP: routing cache hash table of 2048
buckets, 16Kbytes
Oct 26 22:23:48 cheetah kernel: TCP: Hash tables configured (established
16384 bind 16384)
Oct 26 22:23:48 cheetah kernel: ACPI: "DELL" found at 0x000fdc90
Oct 26 22:23:48 cheetah kernel: Starting kswapd v1.8
Oct 26 22:23:48 cheetah kernel: ACPI: "DELL" found at 0x000fdc90
Oct 26 22:23:48 cheetah kernel: Starting kswapd v1.8
Oct 26 22:23:48 cheetah kernel: pty: 256 Unix98 ptys configured
Oct 26 22:23:48 cheetah kernel: Uniform Multi-Platform E-IDE driver
Revision: 6.31
Oct 26 22:23:48 cheetah kernel: ide: Assuming 33MHz system bus speed for PIO
modes; override with idebus=xx
Oct 26 22:23:48 cheetah kernel: PCI_IDE: unknown IDE controller on PCI bus
00 device 79, VID=1166, DID=0211
Oct 26 22:23:48 cheetah kernel: PCI_IDE: chipset revision 0
Oct 26 22:23:48 cheetah kernel: PCI_IDE standard IDE storage device detected
Oct 26 22:23:48 cheetah kernel: hda: CRD-8482B, ATAPI CDROM drive
Oct 26 22:23:48 cheetah kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Oct 26 22:23:48 cheetah kernel: hda: ATAPI 48X CD-ROM drive, 128kB Cache
Oct 26 22:23:48 cheetah kernel: Uniform CD-ROM driver Revision: 3.11
Oct 26 22:23:48 cheetah kernel: Floppy drive(s): fd0 is 1.44M
Oct 26 22:23:48 cheetah kernel: FDC 0 is a National Semiconductor PC87306
Oct 26 22:23:48 cheetah kernel: Serial driver version 5.02 (2000-08-09) with
MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
Oct 26 22:23:48 cheetah kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A
Oct 26 22:23:48 cheetah kernel: ttyS01 at 0x02f8 (irq = 3) is a 16550A
Oct 26 22:23:48 cheetah kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
Oct 26 22:23:48 cheetah kernel: eepro100.c: $Revision: 1.33 $ 2000/05/24
Modified by Andrey V. Savochkin <[EMAIL PROTECTED]> and others
Oct 26 22:23:48 cheetah kernel: eth0: Intel Corporation 82557 [Ethernet Pro
100], 00:B0:D0:78:A7:5D, IRQ 11.
Oct 26 22:23:48 cheetah kernel: Board assembly 07195d-000, Physical
connectors present: RJ45
Oct 26 22:23:48 cheetah kernel: Primary interface chip i82555 PHY #1.
Oct 26 22:23:48 cheetah kernel: General self-test: passed.
Oct 26 22:23:48 cheetah kernel: Serial sub-system self-test: passed.
Oct 26 22:23:48 cheetah kernel: Internal registers self-test: passed.
Oct 26 22:23:48 cheetah kernel: ROM checksum self-test: passed
(0x04f4518b).
Oct 26 22:23:48 cheetah kernel: Receiver lock-up workaround activated.
Oct 26 22:23:48 cheetah kernel: SCSI subsystem driver Revision: 1.00
Oct 26 22:23:48 cheetah kernel: (scsi0) <Adaptec AIC-7899 Ultra 160/m SCSI
host adapter> found at PCI 1/2/0
Oct 26 22:23:48 cheetah kernel: (scsi0) Wide Channel A, SCSI ID=7, 32/255
SCBs
Oct 26 22:23:48 cheetah kernel: (scsi0) Downloading sequencer code... 392
instructions downloaded
Oct 26 22:23:48 cheetah kernel: (scsi1) <Adaptec AIC-7899 Ultra 160/m SCSI
host adapter> found at PCI 1/2/1
Oct 26 22:23:48 cheetah kernel: (scsi1) Wide Channel B, SCSI ID=7, 32/255
SCBs
Oct 26 22:23:48 cheetah kernel: (scsi1) Downloading sequencer code... 392
instructions downloaded
Oct 26 22:23:48 cheetah kernel: scsi0 : Adaptec AHA274x/284x/294x
(EISA/VLB/PCI-Fast SCSI) 5.2.1/5.2.0
Oct 26 22:23:48 cheetah kernel: <Adaptec AIC-7899 Ultra 160/m SCSI
host adapter>
Oct 26 22:23:48 cheetah kernel: scsi1 : Adaptec AHA274x/284x/294x
(EISA/VLB/PCI-Fast SCSI) 5.2.1/5.2.0
Oct 26 22:23:48 cheetah kernel: <Adaptec AIC-7899 Ultra 160/m SCSI
host adapter>
Oct 26 22:23:48 cheetah kernel: (scsi0:0:0:0) Synchronous at 80.0 Mbyte/sec,
offset 63.
Oct 26 22:23:48 cheetah kernel: Vendor: QUANTUM Model: ATLAS V 9 WLS
Rev: 0201
Oct 26 22:23:48 cheetah kernel: Type: Direct-Access
ANSI SCSI revision: 03
Oct 26 22:23:48 cheetah kernel: (scsi0:0:1:0) Synchronous at 160.0
Mbyte/sec, offset 63.
Oct 26 22:23:48 cheetah kernel: Vendor: SEAGATE Model: ST318404LW
Rev: 0002
Oct 26 22:23:48 cheetah kernel: Type: Direct-Access
ANSI SCSI revision: 03
Oct 26 22:23:48 cheetah kernel: (scsi0:0:2:0) Synchronous at 160.0
Mbyte/sec, offset 63.
Oct 26 22:23:48 cheetah kernel: Vendor: SEAGATE Model: ST318404LW
Rev: 0002
Oct 26 22:23:48 cheetah kernel: Type: Direct-Access
ANSI SCSI revision: 03
Oct 26 22:23:48 cheetah kernel: Detected scsi disk sda at scsi0, channel 0,
id 0, lun 0
Oct 26 22:23:48 cheetah kernel: Detected scsi disk sdb at scsi0, channel 0,
id 1, lun 0
Oct 26 22:23:48 cheetah kernel: Detected scsi disk sdc at scsi0, channel 0,
id 2, lun 0
Oct 26 22:23:48 cheetah kernel: SCSI device sda: 17783249 512-byte hdwr
sectors (9105 MB)
Oct 26 22:23:48 cheetah kernel: Partition check:
Oct 26 22:23:48 cheetah kernel: sda: sda1 sda2 sda3 < sda5 sda6 >
Oct 26 22:23:48 cheetah kernel: SCSI device sdb: 35843670 512-byte hdwr
sectors (18352 MB)
Oct 26 22:23:48 cheetah kernel: sdb: sdb1
Oct 26 22:23:48 cheetah kernel: SCSI device sdb: 35843670 512-byte hdwr
sectors (18352 MB)
Oct 26 22:23:48 cheetah kernel: sdb: sdb1
Oct 26 22:23:48 cheetah kernel: SCSI device sdc: 35843670 512-byte hdwr
sectors (18352 MB)
Oct 26 22:23:48 cheetah kernel: sdc: sdc1
Oct 26 22:23:48 cheetah kernel: Linux PCMCIA Card Services 3.1.20
Oct 26 22:23:48 cheetah kernel: options: [pci] [cardbus] [pm]
Oct 26 22:23:48 cheetah kernel: md driver 0.90.0 MAX_MD_DEVS=256,
MAX_REAL=12
Oct 26 22:23:48 cheetah kernel: raid1 personality registered
Oct 26 22:23:48 cheetah kernel: md.c: sizeof(mdp_super_t) = 4096
Oct 26 22:23:48 cheetah kernel: autodetecting RAID arrays
Oct 26 22:23:48 cheetah kernel: (read) sdb1's sb offset: 17920384 [events:
00000006]
Oct 26 22:23:48 cheetah kernel: (read) sdc1's sb offset: 17920384 [events:
00000006]
Oct 26 22:23:48 cheetah kernel: autorun ...
Oct 26 22:23:48 cheetah kernel: considering sdc1 ...
Oct 26 22:23:48 cheetah kernel: adding sdc1 ...
Oct 26 22:23:48 cheetah kernel: adding sdb1 ...
Oct 26 22:23:48 cheetah kernel: created md0
Oct 26 22:23:48 cheetah kernel: bind<sdb1,1>
Oct 26 22:23:48 cheetah kernel: bind<sdc1,2>
Oct 26 22:23:48 cheetah kernel: running: <sdc1><sdb1>
Oct 26 22:23:48 cheetah kernel: now!
Oct 26 22:23:48 cheetah kernel: sdc1's event counter: 00000006
Oct 26 22:23:48 cheetah kernel: sdb1's event counter: 00000006
Oct 26 22:23:48 cheetah kernel: md0: max total readahead window set to 124k
Oct 26 22:23:48 cheetah kernel: md0: 1 data-disks, max readahead per
data-disk: 124k
Oct 26 22:23:48 cheetah kernel: raid1: device sdc1 operational as mirror 1
Oct 26 22:23:48 cheetah kernel: raid1: device sdb1 operational as mirror 0
Oct 26 22:23:48 cheetah kernel: (checking disk 0)
Oct 26 22:23:48 cheetah kernel: (really checking disk 0)
Oct 26 22:23:48 cheetah kernel: (checking disk 1)
Oct 26 22:23:48 cheetah kernel: (really checking disk 1)
Oct 26 22:23:48 cheetah kernel: (checking disk 2)
Oct 26 22:23:48 cheetah kernel: (checking disk 3)
Oct 26 22:23:48 cheetah kernel: (checking disk 4)
Oct 26 22:23:48 cheetah kernel: (checking disk 5)
Oct 26 22:23:48 cheetah kernel: (checking disk 6)
Oct 26 22:23:48 cheetah kernel: (checking disk 7)
Oct 26 22:23:48 cheetah kernel: (checking disk 8)
Oct 26 22:23:48 cheetah kernel: (checking disk 9)
Oct 26 22:23:48 cheetah kernel: (checking disk 10)
Oct 26 22:23:48 cheetah kernel: (checking disk 11)
Oct 26 22:23:48 cheetah kernel: (checking disk 12)
Oct 26 22:23:48 cheetah kernel: (checking disk 13)
Oct 26 22:23:48 cheetah kernel: (checking disk 14)
Oct 26 22:23:48 cheetah kernel: (checking disk 15)
Oct 26 22:23:48 cheetah kernel: (checking disk 16)
Oct 26 22:23:48 cheetah kernel: (checking disk 17)
Oct 26 22:23:48 cheetah kernel: (checking disk 18)
Oct 26 22:23:48 cheetah kernel: (checking disk 19)
Oct 26 22:23:48 cheetah kernel: (checking disk 20)
Oct 26 22:23:48 cheetah kernel: (checking disk 21)
Oct 26 22:23:48 cheetah kernel: (checking disk 22)
Oct 26 22:23:48 cheetah kernel: (checking disk 23)
Oct 26 22:23:48 cheetah kernel: (checking disk 24)
Oct 26 22:23:48 cheetah kernel: (checking disk 25)
Oct 26 22:23:48 cheetah kernel: (checking disk 26)
Oct 26 22:23:48 cheetah kernel: raid1: device sdb1 operational as mirror 0
Oct 26 22:23:48 cheetah kernel: (checking disk 0)
Oct 26 22:23:48 cheetah kernel: (really checking disk 0)
Oct 26 22:23:48 cheetah kernel: (checking disk 1)
Oct 26 22:23:48 cheetah kernel: (really checking disk 1)
Oct 26 22:23:48 cheetah kernel: (checking disk 2)
Oct 26 22:23:48 cheetah kernel: (checking disk 3)
Oct 26 22:23:48 cheetah kernel: (checking disk 4)
Oct 26 22:23:48 cheetah kernel: (checking disk 5)
Oct 26 22:23:48 cheetah kernel: (checking disk 6)
Oct 26 22:23:48 cheetah kernel: (checking disk 7)
Oct 26 22:23:48 cheetah kernel: (checking disk 8)
Oct 26 22:23:48 cheetah kernel: (checking disk 9)
Oct 26 22:23:48 cheetah kernel: (checking disk 10)
Oct 26 22:23:48 cheetah kernel: (checking disk 11)
Oct 26 22:23:48 cheetah kernel: (checking disk 12)
Oct 26 22:23:48 cheetah kernel: (checking disk 13)
Oct 26 22:23:48 cheetah kernel: (checking disk 14)
Oct 26 22:23:48 cheetah kernel: (checking disk 15)
Oct 26 22:23:48 cheetah kernel: (checking disk 16)
Oct 26 22:23:48 cheetah kernel: (checking disk 17)
Oct 26 22:23:48 cheetah kernel: (checking disk 18)
Oct 26 22:23:48 cheetah kernel: (checking disk 19)
Oct 26 22:23:48 cheetah kernel: (checking disk 20)
Oct 26 22:23:48 cheetah kernel: (checking disk 21)
Oct 26 22:23:48 cheetah kernel: (checking disk 22)
Oct 26 22:23:48 cheetah kernel: (checking disk 23)
Oct 26 22:23:48 cheetah kernel: (checking disk 24)
Oct 26 22:23:48 cheetah kernel: (checking disk 25)
Oct 26 22:23:48 cheetah kernel: (checking disk 26)
Oct 26 22:23:48 cheetah kernel: raid1: raid set md0 active with 2 out of 2
mirrors
Oct 26 22:23:48 cheetah kernel: md: updating md0 RAID superblock on device
Oct 26 22:23:48 cheetah kernel: sdc1 [events: 00000007](write) sdc1's sb
offset: 17920384
Oct 26 22:23:48 cheetah kernel: sdb1 [events: 00000007](write) sdb1's sb
offset: 17920384
Oct 26 22:23:48 cheetah kernel: .
Oct 26 22:23:48 cheetah kernel: ... autorun DONE.
Oct 26 22:23:48 cheetah kernel: ds: no socket drivers loaded!
Oct 26 22:23:48 cheetah kernel: VFS: Mounted root (ext2 filesystem)
readonly.
Oct 26 22:23:48 cheetah kernel: Freeing unused kernel memory: 168k freed
Oct 26 22:23:48 cheetah kernel: Adding Swap: 128484k swap-space
(priority -1)
Oct 26 22:23:49 cheetah /usr/sbin/cron[153]: (CRON) INFO (pidfile fd = 3)
Oct 26 22:23:49 cheetah /usr/sbin/cron[154]: (CRON) STARTUP (fork ok)
============================================================================
============================================================================
============================
------------------------------
Subject: Re: NFS help...
From: Robert Kiesling <[EMAIL PROTECTED]>
Date: Thu, 26 Oct 2000 14:41:35 GMT
DeAnn Iwan <[EMAIL PROTECTED]> writes:
> You should not need to recompile to use NFS. Do you have your
> network files (portmapper, hosts....) set up so the machines can see
> each other? For example, can the two machines ping each other? If the
> hostsallow/deny files seem ok, then check the permissions you used in
> fstab and exports. Sorry to not be more specific...I only do this stuff
> now and then.
>
> fail006 wrote:
> >
> > Hi,
> > I am trying to get nfs working between two computers, both of them running
> > linux redhat 7 and windows 98.
> > One PC is setup as a nfs server and when i try to mount the shared directory
> > on my client machine, it gives me and error saying that permission denied.
> > On my server i have edited my /etc/exports file.
> > And on my client pc i have edited my /etc/fstab file.
> > I was wondering do i need to recompile the kernel so it will support nfs
> > file system or does it support nfs by default?
> > How do i see the shared nfs directory on my windows machine? Is there a
> > windows nfs client?
You'll first need to determine if /sbin/portmap is running, using ps.
Red Hat (at least 6.2) has two packages that implement NFS: portmap,
and nfs-utils. Everything besides portmap is in /usr/sbin, so
you'll need to be root to have that directory in the path. If
the packages seem to have installed ok, then you could try
starting /sbin/portmap from the command line, or better, starting
everything in NFS with '/etc/rc.d/init.d/nfs start'.
--
Robert Kiesling
Linux FAQ Maintainer
[EMAIL PROTECTED]
http://www.mainmatter.com/linux-faq/toc.html http://www.mainmatter.com/
------------------------------
Reply-To: [EMAIL PROTECTED]
From: [EMAIL PROTECTED] (Rod Smith)
Subject: Re: mail question
Date: Thu, 26 Oct 2000 14:41:47 GMT
[Posted and mailed]
In article <[EMAIL PROTECTED]>,
Lyle Hanson <[EMAIL PROTECTED]> writes:
> hi!
>
> Just set up postfix on my firewall. Not useful for much except mail ON
> THAT MACHINE. ISP firewalls port 25, and I know how to get postfix to
> listen on a different port, but will that allow me to receive
> mail? Because after all, every other mail server is going to try to
> deliver to 25 (and get rejected).
Ideally, you shouldn't run servers on a firewall system. If the server
contains a bug, that might provide a way for outsiders to break into the
firewall, thus compromising your entire network.
Ideally, you'd run the mail server on a computer in a "DMZ"
("de-militarized zone"), which is a machine or set of machines that's
firewalled from both the outside and the inside, thus:
+----------+
| Internet |
+----------+
|
+----------+ +-------------+
| Firewall |--| Mail Server |
+----------+ +-------------+
|
+----------+
| Intranet |
+----------+
The firewall can then control access to the mail server from both inside
and outside, and can block mail server access to both inside and outside
in case it's compromised. The rules on the mail server will be very
strict, allowing through only those protocols that are necessary, such
as SMTP from the outside and SMTP and perhaps POP or IMAP from the
inside. (Also probably SSH or some such from the inside, for ease of
administration.)
To more directly answer your question, whether you put the mail server
on a separate machine or put it on the firewall, if you want it to do
any good, you must open a hole in your firewall for port 25 traffic. If
your ISP blocks incoming port-25 traffic, there's not much you can do
about it; you cannot effectively run a mail server on that machine,
unless you can configure some machine on another network to serve as a
relay using a non-standard port or unless you control every potential
sender. If you simply want to have your own domain name, you can
contract with an ISP to do the domain hosting for you. You'll get some
number of POP or IMAP e-mail accounts, so you can grab mail via POP or
IMAP, then serve them internally using whatever you like.
--
Rod Smith, [EMAIL PROTECTED]
http://www.rodsbooks.com
Author of books on Linux & multi-OS configuration
------------------------------
From: "Kurt R. Rahlfs" <[EMAIL PROTECTED]>
Subject: Re: Old Compaq linux system?
Date: Thu, 26 Oct 2000 09:36:14 -0500
me wrote:
> Does anyone know of any problems I might have installing linux on a 486
> Compaq? I tried to install a small version of linux, made for a smaller
> (older) computer, and it said it could not mount my hard drive. Could this
> be due to the fact that I didn't reformat and left Windows on it? Or is it
> more likely a problem with proprietary hard drive drivers? it is a Compaq
> Deskpro XE 433s with 8 MB of RAM and a 210 (about) MB hard drive. It has a
> floppy, but no CD-ROM, so that's not an option. If anyone can help, I would
> greatly appreciate it.
>
> Josh
I've loaded SuSE 6.3 on a Compaq Pentium w/ 250 MB drive and 16 MB of RAM.
I've also loaded non-Compaq 486s with similar sized drives and memory. None
have had problems finding the HD. I would suspect the proprietary HD is
causing you problems.
(The following is a guess since I havn't done this.) On SuSE I started the
load with a floppy with it came another floppy that has modules for unusual
configurations I'm guessing that if you can find a module for your HD and
then start up your installation system and then modprobe the module from that
then you should be able to install.
Good luck,
KurtRR
------------------------------
From: Murray Eisenberg <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.advocacy,comp.os.imux.help,comp.os.linux.misc
Subject: Re: Help for new Linux users
Date: Thu, 26 Oct 2000 14:38:52 GMT
Bless you for saying this!
I'm not in a position to help very much yet, as I'm quite new to Linux
myself. And in that position I _really_ appreciate what you say. But
I've been at computing for 45 years now (starting with assemply language
on a Univac I). And I actually DO read printed and electronic
documentation very carefully. However, the documentation for Linux is
often much too complicated, involves too many assumptions about the
reader's level of expertise, and/or involves long chains of references
to other documentation that leaves my head, at least, spinning.
Ken Schrock wrote:
>
> I am a Linux user and advocate...
> I am a former Windows user myself...
> I want to help other Windows users convert to Linux.
> I feel that this forum and others like it are poorly suited to this
> purpose.
> Most Windows users don't read manuals and aren't programmers and
> therefore...
> Answers like "RTFM", "Have you read the FAQs?", and "Just re-compile the
> kernel"...
> Are not good answers for Windows users trying Linux for the first time.
> This isn't helpful, feels like an attack, and drives these folks away...
>
> Which is not good for Linux in the short term or long run....
--
Murray Eisenberg [EMAIL PROTECTED]
Mathematics & Statistics Dept. phone 413 549-1020 (H)
Univ. of Massachusetts 413 545-2859 (W)
Amherst, MA 01003-4515
------------------------------
From: Eric <[EMAIL PROTECTED]>
Subject: Re: Win2K NTFS + Linux dual boot: LILO where?
Date: Thu, 26 Oct 2000 16:51:08 +0200
Reply-To: [EMAIL PROTECTED]
Murray Eisenberg wrote:
>
> This concerns how to configure LILO with an existing installation of
> Windows 2000 with NTFS (single 45 GB IDE drive) so as to allow
> dual-bootint to Linux (specifically, Red Hat 7.0).
>
> The "NT OS Loader + Linux mini-HOWTO" in section 3.4, says: "...
> specify your Linux-_ROOT_-partition as your boot device.... This means
> that ther root-entry and the boot entry in your /etc/lilo.conf have the
> same value... [emphasis added]."
>
> Is that correct -- that LILO goes to the root partition rather than the
> boot partition? This seems to matter, because I intend to create a
> separate Linux boot partition from the Linux root ( / ) partition. My
> understanding is that the entire _boot_ partition needs to be below the
> 1023 cylinder limit, and since the boot partition can be quite small,
> that's no problem. But if LILO is to to to the _root_ partition, that's
> a different matter entirely; in that case, does the entire root
> partition need to go below 1023, or would it be enough for the root
> partition to start below 1023; or doesn't it matter at all?
>
> --
> Murray Eisenberg [EMAIL PROTECTED]
> Mathematics & Statistics Dept. phone 413 549-1020 (H)
> Univ. of Massachusetts 413 545-2859 (W)
> Amherst, MA 01003-4515
Doesn't really matter, cause you must copy the bootcode to an image file
and supply that file to the NT loader (that file will be on the NTFS
partition IIRC)
May I suggest to use LILO os your main bootloader?
It's much easier to setup:
1) boot linux (using a bootfloppy)
2) dd if=/dev/hda of=MBR.img bs=512 count=1 (just to be able to restore)
3) put LILO in the MBR (line in lilo.conf boot=/dev/hda2 should be
boot=/dev/hda)
4) add an other part to lilo.conf: other=/dev/hda1
label=NT
5) rerun /sbin/lilo -v
6) reboot
There's nothing more to it.
If for any reason either linux or NT won't boot you can put MBR.img back
to put the NT bootloader back in the MBR.
Eric
------------------------------
From: "Brad K" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Installing Linux, Kernel Panic
Date: Thu, 26 Oct 2000 09:59:41 -0500
Hopefully someone can help me with this.
I install Linux (Redhat, Mandrake, and Slackware) and everything goes fine.
Then when I
reboot, I get the error message.
...changing IO-APIC physical APIC ID to 16
Kernel panic: could not set ID
In swapper task - not syncing
Then it just hangs. The system is a Dual PPro 150. When I boot to the boot
disk, it boots fine, albeit, not in SMP.
Does anyone have any idea how to fix this?
Thanks,
Brad K
www.photova.net
------------------------------
From: Eric <[EMAIL PROTECTED]>
Subject: Re: Moving /usr From One Partition To Another
Date: Thu, 26 Oct 2000 16:58:56 +0200
Reply-To: [EMAIL PROTECTED]
> > Okay, Then I'll give you a step by step help: (Robert explained the
> > same, but I'll split it up in steps for you)
> >
> > su - root
> > mkdir /new_usr
> > cp -a /usr/* /new_usr
> > umount /usr
> > rmdir /usr
> > mv /new_usr /usr
>
> I don't *think* that /usr being a mount point should affect the
> ability to rename it, but I haven't tried anything like this,
> specifically, for quite some time. If that _does_ turn out to be the
> case, it might be better to 'umount /usr' before renaming ('mv'ing)
> the /new-usr-system to /usr.
I'm not sure either, wouldn't try it though (mtab is no longer correct)
besides the old /usr is no longer needed anyway, just umount it and add
the
space to / does sound good to me.
> > *now edit fstab: comment out the line with /dev/hdc7
>
> Meaning, place a '#' at the beginning of the line using a text editor.
> I doubt that's even critical with this partition setup: only the one
> partition being mounted. But, as a rule, it should definitely be done
> before the next reboot.
Not critical right away, but it's bound to be forgotten if it's not
being done in the same step.
Eric
> --
> Robert Kiesling
> Linux FAQ Maintainer
> [EMAIL PROTECTED]
> http://www.mainmatter.com/linux-faq/toc.html http://www.mainmatter.com/
------------------------------
** 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.setup) 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-Setup Digest
******************************
