Linux-Setup Digest #665, Volume #20 Mon, 19 Feb 01 17:13:10 EST
Contents:
Re: split linux in several partition (Michael Pellaton)
Re: Why can't I telnet to my machine (John Thompson)
Re: LILO Boot Problem ("John Shaw")
no sound as user (wyat)
Re: Replicate/Clone RH6.2 Linux (Scott Nolde)
Re: replacing startx with startx -- +xinerama ([EMAIL PROTECTED])
Re: Modem -- lights flash but no-ones in... (Linus Rees)
----------------------------------------------------------------------------
From: Michael Pellaton <[EMAIL PROTECTED]>
Subject: Re: split linux in several partition
Date: Mon, 19 Feb 2001 20:11:09 +0100
> I would like to partition my hard disk as follows and install linux.
> The question is do I have to install the operating system manually or
> the install knows how to split itself in various partition?
I only know SuSE and with the recent versions (7.0 and 7.1) this is
absolutely no problem. You just need to define the mountpoints when the
setup program prompts the partitioning dialog.
> here is the partition:
>
> primary boot 20MB
> Primary winnt 200MB
> logical / 600MB
> logical / home 300MB
> logical /user 600MB
> logical FAT 600MB
> logical FAT 600MB
> I like to know how to proceed installing WINNT and Linux on this system.
I usually install WinNT first (just create one single primary partition
with the WinNT setup). Then I install Linux where I create all other
partitions during the stup procedure.
Note: If I look at your table above, I miss a Swap-Partition for Linux.
Hope this helps...
------------------------------
From: John Thompson <[EMAIL PROTECTED]>
Subject: Re: Why can't I telnet to my machine
Date: Mon, 19 Feb 2001 12:18:34 -0600
"Sandeep M. Yelwatkar" wrote:
> Sanjay Agrawal wrote:
>
> > what error message do you get?
> telnet: Unable to connect to remote host: Connection refused
>
> There is no problem with the network as I am able to connect to other
> machines from this machine
If you're running tcp_wrappers to launch telnetd on the remote
machine you may want to check the /etc/hosts.allow file to see
that it is allowing connections from the network.
--
-John ([EMAIL PROTECTED])
------------------------------
From: "John Shaw" <[EMAIL PROTECTED]>
Subject: Re: LILO Boot Problem
Date: Mon, 19 Feb 2001 14:31:32 -0500
I already did the extracting the boot record part to get it into a file
for windows. That apparently works because when I choose Linux off the NT
Loader list it starts to load LILO (gets to the first stage, or "LI" mode).
LILO is installed on the /boot partition which is /dev/hdg5 and the root
partition is /dev/hdg7. Anyway, its seams as though it can't find /dev/hdg5
or something to get to the second stage boot loader. I have tried doing the
disk = /dev/hdg
bios = 0x80
disk = /dev/hde
bios = 0x81
route which should make the bios thing hdk is the bootable drive but that
doesn't appear to help at all. Any one else have any other insight on what
the problem might be?
"Fu" <[EMAIL PROTECTED]> wrote in message
news:96qfk5$dk6$[EMAIL PROTECTED]...
> In article <[EMAIL PROTECTED]>, "Suzanne Dunphy"
> <[EMAIL PROTECTED]> wrote:
>
> > Here is the situation.
> >
> > I have a system with the Promise Ultra100 controller and two harddrives,
> > one on each channel of the controller (/dev/hde and /dev/hdg). I have
> > Windows2000 on /dev/hde. Linux is installed on /dev/hdg with root on
> > /dev/hdg7 and boot on /dev/hdg5. LILO is installed on /dev/hdg5 which
> > is /boot.
> >
> > NT Loader loads when the system is started and gives me the choice to
> > run either Windows2k or Linux. The problem is when I choose linux it
> > gives me
> > "LI" and nothing else. I was told by somebody it had to do with LILO
> > not
> > wanting to look at the second physical HD for the second stage
> > bootloader.
> > This doesn't quite make sense to me since the first stage bootloader is
> > located on the second physical hd but eitherway I was wondering if
> > anyone had a fix?
> >
> > Thanks
>
> this web site should provide a solution.
>
> http://www.littlewhitedog.com/reviews_other_00011.asp
>
> in short it tells you to copy the boot sector of your linux partition into
a
> 512 byte file and store it on your windows drive. you then point the win2k
boot
> manager to the file so it can load linux.
>
> read before trying or you might have to re-install you linux. especially
> since may or may not apply your particular partition arrangement.
> --
> know Jesus, know peace... no Jesus, no peace.
>
>
> fu
------------------------------
From: wyat <[EMAIL PROTECTED]>
Subject: no sound as user
Date: Mon, 19 Feb 2001 19:40:56 GMT
chmod 777 ?
Reinstalled linux and cannot remember the command to get sound as user
Thanks wyat
------------------------------
From: Scott Nolde <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.misc,comp.os.linux.hardware,comp.os.linux.help,comp.os.linux.networking
Subject: Re: Replicate/Clone RH6.2 Linux
Date: Mon, 19 Feb 2001 20:12:20 GMT
Wow, all that crossposting. Anyway, this is how I'd do it:
1. Make boot disk of system.
2. Collect partition info (fdisk -l /dev/hda) and save on extra
floppy. Print it, too.
3. Shutdown system and install new hard drive (as /dev/hdb perhaps).
Reboot into runlevel 1 since it's the fastest.
4. fdisk /dev/hdb in similar fashion of /dev/hda. mkfs.ext2
/dev/hdbx. mkswap too.
5. mount partitions of /dev/hdb into /mnt/whatever
6. cp -avf / /bin /sbin, etc... to /mnt/whatever (you are copying files
to their respective directories on the new drive. Don't copy the /proc
directory.)
7. To test, move /dev/hdb into /dev/hda position and reboot. You may
have to use the boot floppy and /sbin/lilo the new drive.
You could do the above, or use tomsrtbt to
dd if=/dev/hda of=/dev/hdb (assuming identical hard drive geometry.
I haven't tested the second method, but the first works well.
- Scott
Steven Conway wrote:
>
> I have painstakingly set up old OS/2 Warp (urgh) workstation with
> RedHat 6.2.
>
> 1) I have correctly configured all of the devices by downloading
> patches, recompiling, etc.
>
> 2) Updated and changed the kernel.
>
> 3) Updated the numerous packages with the latest patches (up2date)
> RPMS & .tar.gz).
>
> 4) Installed, and tested numerous other third party software packages.
>
> 5) tested, tweeked and finally have the computer working exactly how I
> want it to.
>
> I now need to replicate/clone this workstation to 25 IDENTICAL
> workstations that are all connected over a Private internal network.
>
> I was told to look at RedHats Kickstart but I am not sure if this
> approach is the best way to do this as it assumes you are installing
> off of a CD and not off of an existing system. Am I correct in this
> assumption? Can I even do what I am trying to do.
>
> Steven Conway
--
Never do Windows again with | Scott M. Nolde
Linux! No streaks, haze or | [EMAIL PROTECTED]
glaze! |
3:01pm up 1 day, 14:17, 1 user, load average: 1.00, 1.00, 1.00
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To:
alt.os.linux.redhat,comp.os.linux.hardware,comp.os.linux.admin,comp.os.linux.misc
Subject: Re: replacing startx with startx -- +xinerama
Date: Tue, 20 Feb 2001 07:02:34 +1000
I have this itchy feeling that you want to do a bit of research on
gdm, (gnome display manager AFAIK). This is the thing that you first see
with the choice of window managers. The man pages are broken on my
system, so I dont know where to point you. It may also be a case of
having to poke around in your /etc/X11/xinit/ directory, there are a
couple of scripts in there that are run when you startx.
Sorry for the complete vagueness
J
-=<************************************>=-
The list of specs for my
PC is longer than my willy.
jaredATcelab21DOTpcDOTelecDOTuqDOTeduDOTau
On Mon, 19 Feb 2001, Chris Nelson wrote:
> Hello: This weekend I finally got a working config file for using 2
> monitors on a g400 max.
>
> My problem however is that right now my etc/inittab file has me going to
> only run level 3. if I change this value to 5, the systems takes me to a
> graphical logon..but with only one monitor. My guess is that the system
> is still strying to run startx as opposed to startx -- +xinerama. Where
> do I need to make a change so this can be automoated? Any advice is
> appreciated...
>
> P.S. Any idea how I can have the system default to KDE as opposed to
> gnome? Thought I would throw this in as well
>
> Chris
> Enclosed ar emy XF86Config filke and my /etc/inittab files
>
> *********MY inittab file*************
> #
> # inittab This file describes how the INIT process should set up
> # the system in a certain run-level.
> #
> # Author: Miquel van Smoorenburg, <[EMAIL PROTECTED]>
> # Modified for RHS Linux by Marc Ewing and Donnie Barnes
> #
>
> # Default runlevel. The runlevels used by RHS are:
> # 0 - halt (Do NOT set initdefault to this)
> # 1 - Single user mode
> # 2 - Multiuser, without NFS (The same as 3, if you do not have
> networking)
> # 3 - Full multiuser mode
> # 4 - unused
> # 5 - X11
> # 6 - reboot (Do NOT set initdefault to this)
> #
> id:3:initdefault:
>
> # System initialization.
> si::sysinit:/etc/rc.d/rc.sysinit
>
> l0:0:wait:/etc/rc.d/rc 0
> l1:1:wait:/etc/rc.d/rc 1
> l2:2:wait:/etc/rc.d/rc 2
> l3:3:wait:/etc/rc.d/rc 3
> l4:4:wait:/etc/rc.d/rc 4
> l5:5:wait:/etc/rc.d/rc 5
> l6:6:wait:/etc/rc.d/rc 6
>
> # Things to run in every runlevel.
> ud::once:/sbin/update
>
> # Trap CTRL-ALT-DELETE
> ca::ctrlaltdel:/sbin/shutdown -t3 -r now
>
> # When our UPS tells us power has failed, assume we have a few minutes
> # of power left. Schedule a shutdown for 2 minutes from now.
> # This does, of course, assume you have powerd installed and your
> # UPS connected and working correctly.
> pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down"
>
> # If power was restored before the shutdown kicked in, cancel it.
> pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled"
>
>
> # Run gettys in standard runlevels
> 1:2345:respawn:/sbin/mingetty tty1
> 2:2345:respawn:/sbin/mingetty tty2
> 3:2345:respawn:/sbin/mingetty tty3
> 4:2345:respawn:/sbin/mingetty tty4
> 5:2345:respawn:/sbin/mingetty tty5
> 6:2345:respawn:/sbin/mingetty tty6
>
> # Run xdm in runlevel 5
> # xdm is now a separate service
> x:5:respawn:/etc/X11/prefdm -nodaemon
>
>
> **********My XF86Config File*****************
> # File generated by xf86config.
>
> #
>
> Section "Module"
>
> # This loads the DBE extension module.
>
> Load "dbe" # Double buffer extension
>
> # This loads the miscellaneous extensions module, and disables
> # initialisation of the XFree86-DGA extension within that module.
> SubSection "extmod"
> Option "omit xfree86-dga" # don't initialise the DGA extension
> EndSubSection
>
> # This loads the Type1 and FreeType font modules
> Load "type1"
> Load "freetype"
>
> # This loads the GLX module
> # Load "glx"
>
> EndSection
>
> Section "Files"
>
> RgbPath
> "/usr/X11R6/lib/X11/rgb"
>
>
> FontPath "/usr/X11R6/lib/X11/fonts/local/"
> FontPath "/usr/X11R6/lib/X11/fonts/misc/"
> FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
> FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
> FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
> FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
> FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
> FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
>
> EndSection
>
> # **********************************************************************
> # Server flags section
> # **********************************************************************
>
> Section "ServerFlags"
>
> EndSection
>
> # **********************************************************************
> # Input devices
> # **********************************************************************
>
> # **********************************************************************
> # Core keyboard's InputDevice section
> # **********************************************************************
>
> Section "InputDevice"
>
> Identifier
> "Keyboard1"
> Driver
> "Keyboard"
> # For most OSs the protocol can be omitted (it defaults to "Standard").
> # When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
> # uncomment the following line.
>
> # Option "Protocol" "Xqueue"
>
> Option "AutoRepeat" "500 30"
> Option "XkbRules" "xfree86"
> Option "XkbModel" "pc101"
> Option "XkbLayout" "us"
> Option "XkbCompat" ""
>
> EndSection
>
>
> # **********************************************************************
> # Core Pointer's InputDevice section
> # **********************************************************************
>
> Section "InputDevice"
>
> # Identifier and driver
>
> Identifier
> "Mouse1"
> Driver
> "mouse"
> Option "Protocol" "PS/2"
> Option "Device" "/dev/mouse"
>
> EndSection
>
> # **********************************************************************
> # Monitor section
> # **********************************************************************
>
> # Any number of monitor sections may be present
>
> Section "Monitor"
>
> Identifier "817-1"
> HorizSync 30-130
> VertRefresh 50-180
>
> EndSection
>
> Section "Monitor"
>
> Identifier "815"
> HorizSync 30-130
> VertRefresh 50-180
>
> EndSection
>
> # **********************************************************************
> # Graphics device section
> # **********************************************************************
>
> # Any number of graphics device sections may be present
>
> # Standard VGA Device:
>
> Section "Device"
> Identifier
> "Standard VGA"
> VendorName
> "Unknown"
> BoardName
> "Unknown"
>
> # The chipset line is optional in most cases. It can be used to override
> # the driver's chipset detection, and should not normally be specified.
>
> # Chipset "generic"
>
> # The Driver line must be present. When using run-time loadable driver
> # modules, this line instructs the server to load the specified driver
> # module. Even when not using loadable driver modules, this line
> # indicates which driver should interpret the information in this section.
>
> Driver "vga"
> # The BusID line is used to specify which of possibly multiple devices
> # this section is intended for. When this line isn't present, a device
> # section can only match up with the primary video device. For PCI
> # devices a line like the following could be used. This line should not
> # normally be included unless there is more than one video device
> # intalled.
>
> # BusID "PCI:0:10:0"
>
> # VideoRam 256
>
> # Clocks 25.2 28.3
>
> EndSection
>
> # Device configured by xf86config:
>
> Section "Device"
> Identifier "maxxx"
> Driver "mga"
> # unsupported card
> #VideoRam 32777
> VideoRam 32768
> # Insert Clocks lines here if appropriate
> EndSection
>
> Section "Device"
> Identifier "G400_1"
> Driver "mga"
> BusID
> "PCI:1:0:0"
> Screen
> 0
> EndSection
>
> Section "Device"
> Identifier "G400_2"
> Driver "mga"
> BusID
> "PCI:1:0:0"
> Screen
> 1
> EndSection
>
> # **********************************************************************
> # Screen sections
> # **********************************************************************
>
> # Any number of screen sections may be present. Each describes
> # the configuration of a single screen. A single specific screen section
> # may be specified from the X server command line with the "-screen"
> # option.
> Section "Screen"
> Identifier "Screen 15"
> Device "maxxx"
> Monitor "817-1"
> DefaultDepth 16
>
> Subsection "Display"
> Depth 8
> # Modes "640x480" "800x600" "1024x768" "1280x1024"
> Modes
> "1280x1024"
> ViewPort 0 0
> EndSubsection
> Subsection "Display"
> Depth 16
> # Modes "640x480" "800x600" "1024x768" "1280x1024"
> Modes
> "1280x1024"
> ViewPort 0 0
> EndSubsection
> Subsection "Display"
> Depth 24
> # Modes "640x480" "800x600" "1024x768" "1280x1024"
> Modes
> "1280x1024"
> ViewPort 0 0
> EndSubsection
> EndSection
>
> Section "Screen"
> Identifier "Screen 1"
> Device "G400_1"
> Monitor "817-1"
> DefaultDepth 16
>
> Subsection "Display"
> Depth 8
> Modes "1280x1024"
> ViewPort 0 0
> EndSubsection
>
> Subsection "Display"
> Depth 16
> Modes "1280x1024
> ViewPort 0 0
> EndSubsection
>
> Subsection "Display"
> Depth 24
> Modes "1280x1024"
> ViewPort 0 0
> EndSubsection
> EndSection
>
> Section "Screen"
> Identifier "Screen 2"
> Device "G400_2"
> Monitor "815"
> DefaultDepth 16
>
> Subsection "Display"
> Depth 8
> Modes "1280x1024"
> ViewPort 0 0
> EndSubsection
>
> Subsection "Display"
> Depth 16
> Modes "1280x1024"
> ViewPort 0 0
> EndSubsection
>
> Subsection "Display"
> Depth 24
> Modes "1280x1024"
> ViewPort 0 0
> EndSubsection
> EndSection
>
> # **********************************************************************
> # ServerLayout sections.
> # **********************************************************************
>
> # Any number of ServerLayout sections may be present. Each describes
> # the way multiple screens are organised. A specific ServerLayout
> # section may be specified from the X server command line with the
> # "-layout" option. In the absence of this, the first section is used.
> # When now ServerLayout section is present, the first Screen section
> # is used alone.
>
> Section "ServerLayout"
>
> # The Identifier line must be present
> Identifier "Simple Layout"
>
> # Each Screen line specifies a Screen section name, and optionally
> # the relative position of other screens. The four names after
> # primary screen name are the screens to the top, bottom, left and right
> # of the primary screen. In this example, screen 2 is located to the
> # right of screen 1.
>
> # Screen "Screen 1"
> Screen "Screen 1" LeftOf "Screen 2" Screen "Screen 2"
>
>
> # Each InputDevice line specifies an InputDevice section name and
> # optionally some options to specify the way the device is to be
> # used. Those options include "CorePointer", "CoreKeyboard" and
> # "SendCoreEvents".
>
> InputDevice "Mouse1" "CorePointer"
> InputDevice "Keyboard1" "CoreKeyboard"
>
> EndSection
>
>
>
------------------------------
From: Linus Rees <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.suse
Subject: Re: Modem -- lights flash but no-ones in...
Date: Mon, 19 Feb 2001 21:13:51 +0000
Thanks everyone for your replies.
> > My external "Mr Modem" by Microcomputer Research Ltd (UK)
> > http://www.mri.co.uk/ does not appear to be responding. The modem has a
> > Rockwell chipset.
> Check the modem.inf file on the setup floppy for Windows that came
> with the modem; most probably all you need is a correct init string.
>
> Michael
I haven't checked the modem.inf file yet (I'm sitting at my Mac @home)
but I'll have a look.
> Try a simplier program like minicom.
> issue the command.
> "ATD123-4567" to see if it would dial the number 123-4567
I tried Minicom, as suggested, and got the modenm to dial up (using ATDT
followed by the ISP number); but I didn't get any further than that. But
that's some good news! And I feel much better!
> or better -- AT would reply with OK.
> I go through an OS/2 box but did setup wvdial one time and recall the
> command
> line version would test the modem when you first ran it. It would probe
> to get
> an "OK" response from the modem. You may want to install wvdial and try
> it to
> see if it can find your modem and get the correct init string. It has
> been a
> while, but even a couple of yearrs ago, wvdial was pretty easy to
> configure
> using the text file and a simple to use editor like mcedit included with
> mc.
> If wvdial finds the correct init string you can use it in YaST.
> good luck
>
> joe
>
I tried wvdial but to no avail. It didn't recognise the modem.
Anyway I'm rather slowly getting there. I know the modem works (I can
get it to dial up with minicom) but I can't get Kppp to do the same. One
of the lights comes on but nothing happens. When I query the modem in
Kppp it suggests that the modem is not responding, though I'm not sure
exactly what it's supposed to do!?
I think that I need to put in a different string into Kppp. Any
suggestions?
Linus
--
SuSE Linux 6.3; NEC 486dx 64 Mb ram
[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 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
******************************
