Linux-Setup Digest #646, Volume #19 Mon, 18 Sep 00 17:13:11 EDT
Contents:
Re: Problems when compiling kernel (Vilmos Soti)
Re: Problems when compiling kernel ("Cl�ment Idelon")
lilo and Solaris (�smund �stvold)
@@@ El BUS-X, Sexo en Directo GRATIS @@@ ("Info")
Re: how to configure PPP ("Gregory D. Horne")
Re: xfree 4.0.1 (Hammer)
Re: "Installing SUSE 6.4 on SCSI hard drives from SCSI CD" (Dirk Schenkewitz)
Re: mount, samba, and permissions (D G)
Re: Linux and Microsoft together (D G)
Re: Linux and Microsoft together (D G)
Re: Problems when compiling kernel ("Lonni J. Friedman")
Re: Very Newbie (Colin Watson)
Dual Boot Blues ("GreatSage")
Re: aic7xxx 2.4.0 kernel module...gone (Jonathan)
----------------------------------------------------------------------------
Subject: Re: Problems when compiling kernel
From: Vilmos Soti <[EMAIL PROTECTED]>
Date: Mon, 18 Sep 2000 19:18:54 GMT
chuckle <[EMAIL PROTECTED]> writes:
> I am using Redhat 6.2 with kernel 2.2.14. I thought it sounds not bad
> to make a kernel
Go with the latest stable kernel which is 2.2.17 now. (If I am correct.)
There were an ugly bug upto 2.2.15 which has been corrected in 2.2.16.
> I followed instructions in the README file in /usr/src/linux. This is
> what I did.
> make xconfig, make dep, make clean, make zImage ,
> make modules, make modules_install
Don't do make zImage. instead, do make bzImage.
> However, LILO was saying the new zImage "is too big", although is much
> smaller than the previous one.
again, do make bzImage.
Vilmos
------------------------------
From: "Cl�ment Idelon" <[EMAIL PROTECTED]>
Subject: Re: Problems when compiling kernel
Date: Mon, 18 Sep 2000 21:18:48 +0200
Reply-To: "Cl�ment Idelon" <[EMAIL PROTECTED]>
Hello
Type 'make bzImage' instead of 'make zImage' to get a smaller image.
You should copy the '/usr/src/linux/System.map' into your '/boot'
directory.
And you should remove or rename the '/lib/modules/2.2.xx' directory
before typing 'make modules_install'.
good luck.
chuckle <[EMAIL PROTECTED]> a �crit dans le message :
[EMAIL PROTECTED]
> Hi, all,
>
> I need help recompiling the kernel.
> I am using Redhat 6.2 with kernel 2.2.14. I thought it sounds not bad
> to make a kernel
> which only support the hardwares that I have.
> I followed instructions in the README file in /usr/src/linux. This is
> what I did.
> make xconfig, make dep, make clean, make zImage ,
> make modules, make modules_install
>
> However, LILO was saying the new zImage "is too big", although is much
> smaller
> than the previous one.
> Anyway I tried to reboot the new kernel. I got thousands of lines of
> rubbish message like
> "unresolved symbol in /lib/modules/xxx...".
------------------------------
From: [EMAIL PROTECTED] (�smund �stvold)
Subject: lilo and Solaris
Date: 18 Sep 2000 21:21:08 +0200
Hi
I have installed Solaris on a x86 computer on a SCSI disk.
Partition: /dev/sdb1. Because last time I ran lilo, I had to reinstall
a lot, I ran:
lilo -t -v
I got this output:
LILO version 21, Copyright 1992-1998 Werner Almesberger
Reading boot sector from /dev/hda
Merging with /boot/boot.b
Boot image: /boot/vmlinuz-2.4.0-test8
Added linux-240test8 *
Boot image: /boot/vmlinuz-2.2.14-5.0
Mapping RAM disk /boot/initrd-2.2.14-5.0.img
Added linux
Boot other: /dev/hda1, loader /boot/chain.b
Added dos
Boot other: /dev/sdb1, loader /boot/chain.b
Warning: BIOS drive 0x82 may not be accessible
Warning: BIOS drive 0x82 may not be accessible
Added solaris
The boot sector and the map file have *NOT* been altered.
"man lilo" says the following about the error
"Warning: BIOS drive 0x82 may not be accessible":
Warning: BIOS drive 0x<number> may not be accessible
Because most BIOS versions only support two floppies and two hard
disks, files located on additional disks may be inaccessible. This
warning indicates that some kernels or even the whole system may be
unbootable.
I have one IDE disk and to SCSI disks. Solaris is installed on SCSI
/dev/sdb1.
I have the following disk configuration:
hda 20 GB
sda 2.1 GB
sdb 6.4 GB
/etc/lilo.conf looks like this:
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
linear
image=/boot/vmlinuz-2.4.0-test8
label=linux-240test8
read-only
root=/dev/sda1
image=/boot/vmlinuz-2.2.14-5.0
label=linux
initrd=/boot/initrd-2.2.14-5.0.img
read-only
root=/dev/sda1
other=/dev/hda1
label=dos
other=/dev/sdb1
label=solaris
Is there a danger that I might not be able to boot linux or dos if i
was to run lilo?
If so, are there any known workarounds?
Regards,
Asmund Ostvold
------------------------------
From: "Info" <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.hardware,comp.os.linux.m68k,comp.os.linux.misc,comp.os.linux.networking,comp.os.linux.portable,comp.os.linux.powerpc,comp.os.linux.security,comp.os.linux.x,comp.sys.sgi.misc,comp.sys.sinclair,comp.sys.stratus
Subject: @@@ El BUS-X, Sexo en Directo GRATIS @@@
Date: Mon, 18 Sep 2000 19:27:03 GMT
http://www.elbus-x.net
Sexo en directo GRATIS!!!. Webcams las 24h del d�a para que las puedas
disfrutar t� cuando quieras y sin pagar ni un duro.Recuerda, todo es GRATIS
sin altas ni formularios.
http://www.elbus-x.net
------------------------------
From: "Gregory D. Horne" <[EMAIL PROTECTED]>
Crossposted-To: linux.redhat.ppp
Subject: Re: how to configure PPP
Date: Mon, 18 Sep 2000 14:31:36 -0500
Try pppconfig - works very well if you are not into hand editing files.
Dave Stanton wrote:
> "Jack Kessler" <[EMAIL PROTECTED]> wrote in message
> news:8ph763$5uu$[EMAIL PROTECTED]...
> > That certainly is the conventional wisdom and all the right buzzwords and
> > credentials. Yet connecting to an ISP in Windows consists of clicking on
> an
> > icon, entering a phone number, and when prompted, one's username and
> > password, and it works every time. In Linux one follows Unruh's 16 page
> > HOW-TO line by line and may or may not get connected. (In my case still
> > not.) By contrast, Linux has several busy newsgroups devoted to
> frustrated
> > users trying unsuccessfully to connect. Sneering at paperclips does not
> > make unfriendly software better than software that is easy to use. Is an
> > operating system that puts users like Nishat Shah through "a nightmare" in
> > order to use it, really all that useful?
> >
> > Do you think it is an accident that Red Hat has to provide 30 days of
> > installation support with each copy of its OS and Microsoft doesn't?
>
> I don't think thats a fair comment !. I have had horrendous problems with
> win9x, at least with Linux if the gui fails, the whole system stays stable
> and does not force you to shutdown, reinstall. If the guy tries KPPP I think
> he will find it very easy to setup.
>
> Cheers
>
> Dave
--
Gregory D. Horne L I N U X .~.
Systems Analyst The Choice /V\
of a GNU /( )\
Generation ^^-^^
------------------------------
From: Hammer <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Re: xfree 4.0.1
Date: Mon, 18 Sep 2000 19:44:05 GMT
In article <5KNw5.84933$[EMAIL PROTECTED]>,
"Norman Zhang" <[EMAIL PROTECTED]> wrote:
[snip]
> (==) Using config file: "/etc/X11/XF86Config"
> Parse warning on line 78 of section Keyboard in file
/etc/X11/XF86Config
> Ignoring obsolete keyword "LeftAlt".
> Parse error on line 78 of section Keyboard in file /etc/X11/XF86Config
> "Meta" is not a valid keyword in this section.
> (EE) Problem parsing the config file
> (EE) Error from xf86HandleConfigFile()
>
> Fatal server error:
> no screens found
You've got multiple, not-unexpected problems here. The format/keywords
in the config file between XFree 3.3* and XFree 4.x have changed
slightly. The info above tells you what XF86Config file is being read
(i.e., it is the one you were using with XFree 3.*). The keywords that
were fine w/that version of XFree are *not* fine with this version.
I had this problem as well, so don't feel singled out :)
Backup that file and generate a new one using XFree86 --configure (and
hope that works). If it doesn't, you're in for a bit of a ride.
It would likely also be a good idea for you to have a look at some of
the README and INSTALL files in the distribution, it will clue you in to
a few of these problems, and their recommended solution. The docs are
also at www.xfree.org, if you can't find them in your distribution.
GL.
-=hammer
--
MC
"I've been trying to get as far away from myself as I can" - Bob Dylan
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: Dirk Schenkewitz <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware,comp.os.linux.misc
Subject: Re: "Installing SUSE 6.4 on SCSI hard drives from SCSI CD"
Date: Mon, 18 Sep 2000 21:23:16 +0200
Hi Tom,
Tom Millington wrote:
>
> Sorry - sent two messages and got the titles mixed up!
>
> "Tom Millington" <[EMAIL PROTECTED]> wrote in message news:...
> > I am a newbie trying to put Linux on another server, namely an old
> > P133 (Altos) that has 3 x 4.5Gb SCSI hard drives and a SCSI CDROM.
> > ...
> > I have tried to use the Linux boot floppy but neither the hard drives
> > nor the CD are seen - in other words it says I have no hard drives or
> > CD player.
How far did you came with the SuSE boot disk?
In case you just did not get the right idea:
- find out what kind of SCSI controller you have, if you can.
- enter the menu "load kernel modules" --> "load scsi driver" or so.
- select the right module and watch what happens when it loads.
(if you cannot find out what scsi driver you have, try loading all
of them one by one until one of them loads successfully AND FINDS
YOUR HARDWARE ! Perhaps you need the 'modules'-floppy, too.)
If that works, go back and continue with "Installation from CD", the
system now tries to mount the CD, if that fails, well come back here :-)
> > Where do I go from here? Help! I am a newbie so simple steps please.
hope this helps
dirk
--
Dirk Schenkewitz
InterFace AG phone +49 (0)89 / 610 49 - 126
Leipziger Str. 16 fax +49 (0)89 / 610 49 - 85
D-82008 Unterhaching
http://www.InterFace-AG.com mailto:[EMAIL PROTECTED]
------------------------------
From: D G <[EMAIL PROTECTED]>
Subject: Re: mount, samba, and permissions
Date: Mon, 18 Sep 2000 12:48:45 -0700
Skip wrote:
>
> I want users to be able to mount a smbfs share, but I can't seem to
> get it to work.
>
> Here's some stuff that illustrates my problems:
>
> [skip@Linux skip]$ ls /mnt/terminator -l
> total 16
> drwsrwsrwx 2 root root 4096 Apr 7 15:23 c/
> drwsrwsrwx 2 root root 4096 Apr 8 08:26 d/
> drwsrwsrwx 2 root root 4096 Apr 8 08:26 dvd/
> drwsrwsrwx 2 root root 4096 Apr 8 08:26 zip/
>
> [skip@Linux skip]$ which mount
> /bin/mount
>
> [skip@Linux skip]$ ls /bin/mount -l
> -rwsr-sr-x 1 root root 53620 Sep 13 1999 /bin/mount*
>
> [skip@Linux skip]$ cat /etc/fstab
> //terminator/c /mnt/terminator/c smbfs user,intr,noauto
> //terminator/d /mnt/terminator/d smbfs user,intr,noauto
> //terminator/zip /mnt/terminator/zip smbfs user,intr,noauto
> //terminator/dvd /mnt/terminator/dvd smbfs user,intr,noauto
> /dev/hda6 / ext2 defaults 1 1
> /dev/hda1 /boot ext2 defaults 1 2
> /dev/cdrom /mnt/cdrom iso9660 noauto,owner,ro 0 0
> /dev/hda5 swap swap defaults 0 0
> /dev/fd0 /mnt/floppy ext2 noauto,owner 0 0
> none /proc proc defaults 0 0
> none /dev/pts devpts gid=5,mode=620 0 0
I couldn't get this to work, either. Instead, I changed the fstab to
have root mount it at boot time, and used the uid, fmask, and dmask
options to allow user access. Here's part of my (censored) /etc/fstab
for mounting to either unix or windows samba shares:
//unix.machine.ip.address/unixhome /mnt/unix_samba smbfs
uid=###,fmask=660,dmask=770,username=uuu,password=ppp 0 0
//windows_machine_name/share_name /mnt/windos_share smbfs
uid=###,fmask=660,dmask=770,username=uuu,password=ppp,workgroup=www 0
0
Make sure that if you don't have the workgroup set the same on both
machines (you can fix this in the /etc/smb.conf file by adding
'workgroup = [workgroup_name]'), then you specify the workgroup option
as above.
If you want to mount as a regular user, the only success I have had is
using smbmount. Make sure smbmount and smbmnt are setuid (and smbumount
if you want to unmount). Mine are in /usr/bin.
smbmount -t smbfs //machine/share /unix/mntpoint -o
username=uuu,password=ppp,workgroup=www
Also, make sure that /unix/mntpoint has permission for the user to
overwrite, or the mount won't be successful.)
[detail snipped]
> Once I get that going, I have one more related problem. I want
> certain users to have read/write accesss to the NT share, but for some
> reason, only root seems to have that capability as well. Right now
> users can browse the NT share, but not write to it.
Can't help you here.
--
DG
e-mail is: [EMAIL PROTECTED]
(remove the Z's--they're what I do when I read SPAM!)
------------------------------
From: D G <[EMAIL PROTECTED]>
Subject: Re: Linux and Microsoft together
Date: Mon, 18 Sep 2000 13:00:56 -0700
Harry Lewis wrote:
> Pardon me for butting in, but does VMWare run the guest OS in a linux
> process? In other words, do you still enjoy pre-emptive multitasking
> between guest OSs?
As long as each guest OS is withing a different process, then sure. How
it handles preemptive multitasking withing a guest OS, I don't know.
Check out www.plex86.org. You might find some clues there.
> How does VMWare overcome NT's steely determination to
> control access to the hardware itself>
I believe the VM in VMware stands for Virtual Machine. You just give NT
a virtual device and it doesn't know the difference. It's all just bits
and bytes when you get down to it.
--
DG
e-mail is: [EMAIL PROTECTED]
(remove the Z's--they're what I do when I read SPAM!)
------------------------------
From: D G <[EMAIL PROTECTED]>
Subject: Re: Linux and Microsoft together
Date: Mon, 18 Sep 2000 13:03:37 -0700
William McBrine wrote:
>
> Has anyone compared VMWare and Win4Lin?
Sure. Win4Lin (actually, Trelos) has. And they are quite honest. Check
out www.trelos.com for more info.
One big difference is that Win4Lin only runs windows95/98 and probably
dos6.x or dos7. It won't run other operating systems or windowsNT or
2000. I don't know about windowsME, but I doubt it.
--
DG
e-mail is: [EMAIL PROTECTED]
(remove the Z's--they're what I do when I read SPAM!)
------------------------------
From: "Lonni J. Friedman" <[EMAIL PROTECTED]>
Subject: Re: Problems when compiling kernel
Date: Mon, 18 Sep 2000 15:59:20 -0400
chuckle wrote:
>
> Hi, all,
>
> I need help recompiling the kernel.
> I am using Redhat 6.2 with kernel 2.2.14. I thought it sounds not bad
> to make a kernel
> which only support the hardwares that I have.
> I followed instructions in the README file in /usr/src/linux. This is
> what I did.
> make xconfig, make dep, make clean, make zImage ,
> make modules, make modules_install
>
> However, LILO was saying the new zImage "is too big", although is much
> smaller
> than the previous one.
> Anyway I tried to reboot the new kernel. I got thousands of lines of
> rubbish message like
> "unresolved symbol in /lib/modules/xxx...".
> I thought I had got new kernel working because the contents in dmesg
> changed a lot and
> I was no longer informed about nonexisting things like scsi devices.
>
> The new kernel caused two anoying problems. The first is now I got much
> less
> free memory. (1 or 2 M,previously I got about 30M).
> The second is the IDE led is always on. Is this harmful to the hard
> disk?
you should have done 'make bzImage' instead of make zImage and that
would have fixed ALL of your problems.
------------------------------
From: [EMAIL PROTECTED] (Colin Watson)
Subject: Re: Very Newbie
Date: 18 Sep 2000 20:29:02 GMT
[EMAIL PROTECTED] wrote:
>I am running Linux RedHat 6.2 on a Sun Ultra Sparc. I am trying to
>install any applications and I mean any. Someone mentioned that I have
>to compile the application to the Sparc Platform. How in the H@ll do I
>do that??
Get the source code for it (usually distributed as a .tar.gz file),
unpack it with 'tar xzvf whatever.tar.gz', and read whatever
documentation is there. There's often an INSTALL file, for instance. A
very large number of programs use the GNU autoconf/automake system, and
there all you need to do is type './configure' (having changed into the
top-level source directory), 'make', and 'make install'.
You'll need the usual array of development tools installed; Red Hat's
installer should have had the option to install some for you. gcc, make,
binutils, and any -devel packages that look appropriate are the usual
candidates.
Alternatively, you could install Debian 2.2, which has over 4000
packages already compiled, tested, and supported for SPARC. :)
--
Colin Watson [[EMAIL PROTECTED]]
"By our very nature as humans interacting with each other it is
impossible to remove politics completely." - Emma Pease, news.groups
------------------------------
From: "GreatSage" <[EMAIL PROTECTED]>
Subject: Dual Boot Blues
Date: Mon, 18 Sep 2000 13:47:33 -0700
Hi,
I have a computer that has one SCSI hard drive which I have partitioned for
WIN2000 and Red Hat Linux. I first installed WIN2000 on the first partition
and then installed Linux on the second partition. I had LILO installed in
the Linux partition and NOT in the master boot record. I can currently boot
to Win 2000 and can also boot to Linux but to linux via a boot disk. I am
currently trying to utilize the Win2000 boot loader to load both Linux and
Windows but Im having problems. This is what I did:
1) I stripped from the Linux partiiton the bootsector (dd if=/dev/sda6
of=/LINXLOAD.LNX bs=1300 count=1).
2) I copied this to a floppy.
3) Then in Windows 2000 I copied this file to the root directory c:\
4) I edit the boot.ini file (after removing the system and read only
attributes) to add the following line (C:\LINXLOAD.LNX="Linux")
So, when I reboot, I indeed get the boot menu and can successfully load
Win2000 but when I select "Linux" the screen goes black and just prints the
two leters "LI" at the left of the top most line. The computer never loads
Linux and seems to just hang ??
Does anyone have any insight into what I have done incorrectly.
Any help will be greatly appreciated.
Cheers
Jerry
------------------------------
From: Jonathan <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,comp.os.linux.development.system,comp.os.linux.misc
Subject: Re: aic7xxx 2.4.0 kernel module...gone
Date: Mon, 18 Sep 2000 20:49:59 GMT
In article <[EMAIL PROTECTED]>,
Josef Oswald <[EMAIL PROTECTED]> wrote:
> Remember Darren those Kernels are _unstable_ Versions :-(
>
> I tried to kompile one 2.4.test8 now three times and for some reason
> when I want to access my fvat partitions I get the message vfat not
> supported by kernel...... ( and yes I even compiled it fix in the
kernel
> and not as a module)
>
> I know that is not a answer to your question though..:-( Sorry
>
> Darren Welson wrote:
> >
> > Every time I recompile 2.4.0-test 6,7, and 8 kernel, I cannot seem
to
> > successfully load the AIC7XXX module, or at least have it made.
Anyone know
> > how I can check to make sure I am actually making this module, or
find a way
> > I can to compile it into the kernel? I have added it as a module
and IN the
> > kernel in all three test versions as a low-level SCSI option, but
what am I
> > missing?
> >
> > darren
>
> --
> Josef Oswald [EMAIL PROTECTED]
> registered-linux-user # 13.818 at http://counter.li.org
>
Offtopic from the top-level post, but ...
I had that problem with the vfat modules also. Read
/Documentation/Changes. I had to upgrade modutils and rename
conf.modules to modules.conf.
As you said, however - this also does not address the aic7xxx problem ;)
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
** 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
******************************
