Linux-Misc Digest #1, Volume #25 Fri, 30 Jun 00 14:13:02 EDT
Contents:
Re: Gnome vs KDE (Roberto Alsina)
Re: Security problem ("David ..")
Re: Partition problems NT station (Leonard Evens)
Re: Command or piped commands to show directory size... (Grant Edwards)
Re: Emergency boot diskette (Leonard Evens)
Re: kernel panic (Leonard Evens)
Re: NC or Midnight Commander: which came first? (Dmitri V)
startup processes
fetchmail: needs more features (jason varsoke)
APM goes bonkers on Toshiba notebook (Lauren Weinstein)
Re: Sun Sparc faster then intel pentium: SISC / RISC (Super-User)
Re: Gnome vs KDE
Re: Need clarification: what really is 'MBR' and what is 'BOOT SECTOR'? (Gregory
Phillips)
Re: Emergency boot diskette ("David ..")
Re: Gnome file manager ("David ..")
----------------------------------------------------------------------------
From: Roberto Alsina <[EMAIL PROTECTED]>
Subject: Re: Gnome vs KDE
Date: Fri, 30 Jun 2000 16:58:26 GMT
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] () wrote:
> On Thu, 29 Jun 2000 15:08:51 GMT, Roberto Alsina <[EMAIL PROTECTED]>
wrote:
> >In article <[EMAIL PROTECTED]>,
> > [EMAIL PROTECTED] wrote:
> >> From: Matthew Matchura <[EMAIL PROTECTED]>
> >>
> >> [EMAIL PROTECTED] wrote:
> [deletia]
> >>
> >> Red Hat wanted to use entirely GNU based software. This includes
teh
> >> underlying libs.
> >>
> >> KDE is QT based, proprietory/commercial.
> >
> >You must have a very slow newsfeed, if you have not heard that Qt is
> >free software.
>
> No, you're just being willfully misleading.
Jedi, you are confusing me with you.
> >
> >> GNOME is GTK based, entirely GNU.
> [deletia]
>
> The proof is in the ports (and the 3rd party contributions).
> If QT is genuinely 'free' then there should be plenty of
> developers that share this perception and have been adding
> little things to QT like BeOS or MacOS support.
Why? Have you seen a XFree port to MacOS? is XFree not free?
Have you seen a glibc port to Be? is glibc not free?
> Until that starts happening, what Troll (or you) choose to
> label the product is moot.
Believe it or not, I don't give a rat's ass about what you think is
moot.
The product (Qt Free edition) is there for anyone to get, modify,
redistribute, port, or sell, without charge, as long as you don't
restrict anyone else from those rights.
If that's not free for you, then you have a problem, because the GPL
is, in practice, just as restrictive as the QPL, except for technical
details on the form of redistribution (for which there are simple
technical solutions).
Let's just say this: I say it's free. I tell anyone reading this, go
read the license. Decide for yourself if it's free. Act based on
that information.
If you want to trust other's opinion on the freedom of the license, I'll
also say, Eric Raymod (creator of the term "open source" says it is
open source, and that Richard Stallman, chief of the Free Software
Foundation, says it's free software.
Alll you, Jedi, have to offer, is "if it's free why is it not ported
to MAC and Be". That's way too lame to be taken seriously, and only
shows you have a bias in the matter. So do I. But at least I offer
people something to decide if what I say is just bias or not.
--
Roberto Alsina (KDE developer, MFCH)
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: "David .." <[EMAIL PROTECTED]>
Subject: Re: Security problem
Date: Fri, 30 Jun 2000 11:59:42 -0500
Miguel wrote:
>
> "David .." wrote:
> >
> > Miguel wrote:
> > >
>
> > You have to tell the system to use "limits.conf"
> > Add a line like this down at the bottom above any optional settings like
> > this.
> >
> > vi /etc/pam.d/login
> >
> > session required /lib/security/pam_limits.so
>
> I already have that line in that file
>
> Miguel
You have to log out and log in for the change to be read.
--
Registered with the Linux Counter. http://counter.li.org
ID # 123538
------------------------------
From: Leonard Evens <[EMAIL PROTECTED]>
Subject: Re: Partition problems NT station
Date: Fri, 30 Jun 2000 12:02:19 -0500
oksigen wrote:
>
> I have a NT station with a new 14 Gig HD. The newly installed HD have
> been set in such a way that 4 gig of space has been left unpartitioned
> and unformated for furutre Linux Installation.
> The unpartitioned portion of the HD is at the end of the two other NTFS
> partitioned (c: and d:).
>
> Problem: When I try to set an extended logical partition and install
> linux with a swap an a native Linux partition, I can't reboot the
> machine. The blue NT screen appears with something like "no bootable
> partion found " .....
>
> What should I do to successfully partition the last blocks of the
> HD and install Linux (RH6.2) ?
>
> Thanks
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
You don't say exactly what you did. But if you can't boot NT,
there is a good chance you chose the default to put the lilo
boot loader in the master boot record. This usually causes
problems for NT. There are a couple of ways around this.
The most straightforward is described in the Linux document
Linux+NT-loader. This is a (mini) HOWTO and should be on the
RH6.2 CD.
If you completed the RedHat 6.2 installation, there is a good
chance Linux was installed. Also, a Linux boot floppy should
have been created during the installation. If you have such
a floppy, try to boot from it and report to us what happened.
But note on some machines it make take a very long time to
start booting. Give it at least 10 minutes. If you can
boot Linux, try the command
fdisk -l /dev/hda
and let us know what partitioning it reports.
In order to be able to boot NT, you will have to restore the
master boot record. While running linux, the command
/sbin/lilo -u
should do that. If not, the standard method is to use
a DOS/Windows startup disk to boot and run the DOS command
fdisk/mbr
but I've heard that this may not work for NT. But the NT
installer should have some means to fix the master boot record
without having to reinstall NT.
If you can get that far, try using the method described in the
Linux+NT-loader document.
In addition, the RH6.1 installer had problems when there was more
than one NT partition. I don't know if RH6.2 also has this
problem. There should be a discussion of this on the RedHat
web page. You can also do a search with deja.com. This issue
has come up on several occasions in the past.
Finally, it is likely with the Linux partitions at the end of
the disk that you may encounter the 1024 cylinder problem.
All methods of booting Linux from the hard disk involve using
lilo, possibly as a secondary boot loader. The version of lilo
shipped with RH6.2 can only boot Linux if the kernel is entirely
contained in a partition below cylinder 1024 because of assumptions
it makes about what the BIOS is capable of doing. There is
a newer version of lilo which does not suffer from this restriction
if you have a relatively up to date BIOS. If this is a problem
for you, it ought to be clear from the partitioning information
obtained from fdisk -l. In that case I would advise concentrating
on getting NT running and Linux installed so you can boot it from
a floppy. (There are other means we can tell you about to create
a faster booting floppy.) When you are more familiar with Linux,
you can get the latest version of lilo and install it so as to
boot Linux from the hard drive.
--
Leonard Evens [EMAIL PROTECTED] 847-491-5537
Dept. of Mathematics, Northwestern Univ., Evanston, IL 60208
------------------------------
From: [EMAIL PROTECTED] (Grant Edwards)
Crossposted-To: alt.os.linux
Subject: Re: Command or piped commands to show directory size...
Date: Fri, 30 Jun 2000 17:26:26 GMT
In article <[EMAIL PROTECTED]>, Hendrix wrote:
>Actually, I remember awhile back that somebody posted a method of piping
>the 'ls -l' command to the 'bc' calculation tool in order to calculate
>the amount of space that is being used in a particular directory...
Reminder: the sum of the filesizes shown by 'ls' is different
than the amount of disk space being used. Usually it's going
to be fairly close, but sometimes, a file's "size" as listed by
'ls' is going to be orders of magnitude larger than the actual
disk space used.
If you want the sum of the file "sizes", then that's cool, but
if you want to know how much disk space is used 'du' is your
friend.
--
Grant Edwards grante Yow! I HIJACKED a 747 to
at get here!! I hope those
visi.com fabulous CONEHEADS are
at HOME!!
------------------------------
From: Leonard Evens <[EMAIL PROTECTED]>
Subject: Re: Emergency boot diskette
Date: Fri, 30 Jun 2000 12:17:52 -0500
Jeff Malka wrote:
>
> I am a newbie who has installed TurboLinux 6 workstation just fine. However
> I do not recall during the installation being asked to create an emergency
> boot diskette (that I read about in books). How do I go about that in an
> installed system?
>
> Thank you.
>
> --
> Jeff Malka <[EMAIL PROTECTED]>
You can make a boot floppy which loads the kernel from the
floppy but runs the system from you hard disk. You should
be able to do this with the mkbootdisk command. Do
man mkbootdisk to see how.
A rescue floppy which runs in a ramdisk is another matter.
Tom's root/boot disk is a good choice, but the last time I
looked, it used a fairly old kernel which might not work with
your system. It can be found at
www.toms.net/rb/home.html
--
Leonard Evens [EMAIL PROTECTED] 847-491-5537
Dept. of Mathematics, Northwestern Univ., Evanston, IL 60208
------------------------------
From: Leonard Evens <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.suse,alt.os.linux,comp.os.linux.setup
Subject: Re: kernel panic
Date: Fri, 30 Jun 2000 12:14:01 -0500
beo wrote:
>
> Hello all,
>
> When I reboot my SuSE 6.2 , my computer just freeze after the message below.
> Does anyone know how to fix this problem? Thanks!!
>
> *Partition check:
> *request_module[block_major_8]: root fs not mounted
> *VFS:cannot open root device 08:01
> *Kernel Panic:VFS:Unable to mount root fs on 08:01
Your kernel seems to think the kernel is on /dev/sda1, which
would be the first partition of a SCSI disk. If you do in
fact have a SCSI disk, and you are using a generic kernel,
SCSI support is a module. As a result there has to be
an initial ramdisk with some vestigal SCSI support built in
so that you can actually load the kernel. This is handled
in /etc/lilo.conf with an initrd statement. But for that
to work, you need to run mkinitrd.
You should still be able to boot from a floppy and fix it
all.
--
Leonard Evens [EMAIL PROTECTED] 847-491-5537
Dept. of Mathematics, Northwestern Univ., Evanston, IL 60208
------------------------------
From: Dmitri V <[EMAIL PROTECTED]>
Subject: Re: NC or Midnight Commander: which came first?
Date: Fri, 30 Jun 2000 14:25:08 +0300
>
> As a newbie to Linux (and an old fan of Norton Commander) I was delighted to
> find MC on my distribution. I was curious though: which is the clone of
> which? That is which one came first?
>
Obviously Norton Commander was the first. MC was written in 1994 (as far
as I remember its story), while I worked with NC back in mid-eighties.
Good lick.
Dmitri
------------------------------
From: <[EMAIL PROTECTED]>
Subject: startup processes
Date: Fri, 30 Jun 2000 17:30:05 GMT
How do I make a program or process run during the startup?
--
Posted via CNET Help.com
http://www.help.com/
------------------------------
From: jason varsoke <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.admin
Subject: fetchmail: needs more features
Date: Fri, 30 Jun 2000 17:33:24 GMT
Does anyone know of a program like fetchmail that has a few more
features. Specifically I need a fetchmail type program that will delete
messages on the POP3 server that are N number of days old.
-jason
------------------------------
From: Lauren Weinstein <[EMAIL PROTECTED]>
Subject: APM goes bonkers on Toshiba notebook
Date: Fri, 30 Jun 2000 17:33:34 +0000
Greetings. I've run into a very annoying situation with a new
Toshiba notebook, which *had* been running just fine until
recently. Under Win98, everything regarding APM (power management)
is fine--screen blanks after half an hour, disk spins down
when expected, etc.--so I assume the APM bios is working
properly. (Note that this notebook does not have any way
to directly access the APM settings in the bios or disable them,
all setting is done through a Toshiba app that allows setting
the various parameters for full power or battery modes, respectively.)
Everything was fine under Linux too, though I had only been
running it under A.C. The trouble started after I first ran
Linux on batteries. The monitor started blanking after only
three minutes of inactivity, and the disk spins down after a
few minutes of inaction as well. The system works, and everything
lights up again when a key is pressed, but this is very suboptimal
and I've found no way to stop it. Setterm is not involved anywhere.
I've disabled the apmd daemon (latest version). I've decompiled
apm support from the kernel. Still this keeps happening, and still
only with linux (2.2.14 by the way).
Any clues? Any suggestions? Thanks very much.
--Lauren--
------------------------------
From: Super-User <[EMAIL PROTECTED]>
Crossposted-To: comp.sys.sun.hardware,comp.sys.sun.misc
Subject: Re: Sun Sparc faster then intel pentium: SISC / RISC
Date: Fri, 30 Jun 2000 19:36:54 +0100
"Carl J. Boll" wrote:
>
> The term processor battle was previously used in this thread. I'm
> curious,
So the processor war thread is still alive : - )
I was just at the library reading in a book about the history of computing etc.
They said something interesting about the origins of the RISC architecture. This
was according to the book conceived at Standford by some guy (I can never can
remeber a name) which of course explaines in part why Sun adopted the ideas
after a while.
Anyway the book argued that one of the reasons for the CISC architecture was
that memory in the sixties and seventies was originally ferrite core memory
which is of course *very* slow (but non volatile which must have been sort of
nice, I guess things wherent the same until flash memory appeared) Therefore the
processors tended to do alot of fancy stuff with the data for each instruction
and there were many differnet instructions for many different data manipulations
since retreiving and storing data took so much time.
When silicon memory was beginning to be commonly used the memory to processor
speed was so great the RISC arhitecture was able to achieve greater performanse
by using few instruction and use them extensively.
Now it occured to me that as the processor speed clock frequncies go up etc. the
RISC arhitecture should start loosing again in the performanse race. Nowadays
processors have cache memory at different levels to avoid accessing the slower
memory external to the processor.
Its sort of like the ferrite core memory problem all over again but on a
completely differnet time scale. So maybe the CISC architecture of the Intel
architecture will keep on being faster as long as they can speed up the
processor, increase the clock speed. Of course if memory technology would take a
quantum leap the tables might turn in favor of RISC again.
Is there any substance to this idea or am I being delusional..... (many thought
the RISC idea was delusional at the time, according to the book, and someone at
IBM was actually first with the idea I think : -)
Peter
------------------------------
From: [EMAIL PROTECTED] ()
Subject: Re: Gnome vs KDE
Date: Fri, 30 Jun 2000 17:38:47 GMT
On Fri, 30 Jun 2000 16:58:26 GMT, Roberto Alsina <[EMAIL PROTECTED]> wrote:
>In article <[EMAIL PROTECTED]>,
> [EMAIL PROTECTED] () wrote:
>> On Thu, 29 Jun 2000 15:08:51 GMT, Roberto Alsina <[EMAIL PROTECTED]>
>wrote:
>> >In article <[EMAIL PROTECTED]>,
>> > [EMAIL PROTECTED] wrote:
>> >> From: Matthew Matchura <[EMAIL PROTECTED]>
>> >>
>> >> [EMAIL PROTECTED] wrote:
[deletia]
>>
>> No, you're just being willfully misleading.
>
>Jedi, you are confusing me with you.
>
>> >
>> >> GNOME is GTK based, entirely GNU.
>> [deletia]
>>
>> The proof is in the ports (and the 3rd party contributions).
>> If QT is genuinely 'free' then there should be plenty of
>> developers that share this perception and have been adding
>> little things to QT like BeOS or MacOS support.
>
>Why? Have you seen a XFree port to MacOS? is XFree not free?
Now you are quite willfully indulging in misrepresentation.
So, I can be quite certain I am not confusing you for me.
XFree is just one of many implementations of an open specification
including implementations for Win16 & NT as well as the classic
MacOS.
Although Xfree86 itself has been ported to OS/2.
>Have you seen a glibc port to Be? is glibc not free?
Yup. You really should get out more. Your blinders are
quite a handicap.
>
>> Until that starts happening, what Troll (or you) choose to
>> label the product is moot.
>
>Believe it or not, I don't give a rat's ass about what you think is
>moot.
>
>The product (Qt Free edition) is there for anyone to get, modify,
>redistribute, port, or sell, without charge, as long as you don't
>restrict anyone else from those rights.
QT is still owned by Troll.
[deletia]
Linux is merely one stop on the road towards standards based
computing where computers and software are infact perfectly
replaceable in a genuinely free market.
Linux-centric solutions are no less shortsighted than
Windows-centric ones.
--
|||
/ | \
------------------------------
From: Gregory Phillips <[EMAIL PROTECTED]>
Crossposted-To: microsoft.public.windowsnt.misc,linux.redhat.misc
Subject: Re: Need clarification: what really is 'MBR' and what is 'BOOT SECTOR'?
Reply-To: [EMAIL PROTECTED]
Date: Fri, 30 Jun 2000 17:44:45 GMT
This is the command you are really looking for:
"BOOTPART WIN95 BOOT:C:"
See the FREE utility:
Boot Partition 2.0 for WinNT(c)1995-96 G. Vollant
([EMAIL PROTECTED])
WEB : http://ourworld.compuserve.com/homepages/gvollant/bootpart.htm
Add a partition to the Windows NT Multi-boot loader
Usage : When running under Windows NT or MS-Dos
BOOTPART
List all partitions, with numbers
BOOTPART <part_number> <filename> [<name_of_system>]
where : part_number : a number of a partition (or A: for floppy)
filename : the file name of the bootfile to create
name_of_system : the name to be added in BOOT.INI
Create a boot file for the partition, and if name_of_system
is specified, register it in BOOT.INI
You can also replace <part_number> by DOS622 or WIN95 to create
boot sectors for these systems.
BOOTPART LIST
List the entries in BOOT.INI (you can remove them after with
BOOTPART)
Under MS-Dos (MS-Dos 6.22 or the "MS-Dos 7.0" from Windows 95) only:
BOOTPART <part_type> BOOT:C:
where <part_type> is DOS622, WIN95 or WINNT, rewrite the boot
sector
of C: to boot MS-Dos 6.22, Win95, or the NT Boot loader
BOOTPART REWRITEROOT:C:
Move the IO.SYS and MSDOS.SYS files from MS-Dos 6.22 to the
beginning
of the partition
====================================
BOOTPART lets you add partitions to the Windows NT Multiboot menu. Usually,
the only partitions on the Windows NT multiboot are the one or more
installations of
Windows NT.
With BOOTPART, you can add any partition to the menu. You can add OS/2
Multiboot or Linux Partitions (with Lilo) to the menu.
It seems it's actually impossible to add an HPFS partition with OS/2 boot.
If you find a workaround, please let me know.
BOOTPART creates a 512 byte file that contains an image of a boot sector
that loads the boot sector of the partition. That is, it creates a small
program
that loads and executes the specified partition's boot sector.
Thereafter, this file is
declared in C:\BOOT.INI (a text file used by the Windows NT boot menu). The
boot sector comes from FDFormat and WinImage.
Note that under Windows NT, BOOTPART must be run from the Administrator
account.
FDFormat can be downloaded under the name FDFORM.ZIP in the PCHW compuserve
forum, or by ftp (ftp://ftp.coast.net/SimTel/msdos/diskutil/fdform18.zip).
This tool, written by C.H. Hochstatter, formats floppies under MSDOS in
normal (1.44 MB) or special (1.68 MB) capacity. It will also write a boot
sector that
boots the harddisk.
WinImage, a Windows (Windows 3.1, 95 and NT) shareware I've written, can
read, write, and format floppies in any capacity (including 1.68 MB), and
build an image file of a floppy. It can extract from, or inject files into
an image, and change the image size. The WinImage web site is :
http://ourworld.compuserve.com/homepages/gvollant/winimage.htm
It can be downloaded under name WINIMA25.ZIP in the WUGNET compuserve forum,
or by ftp (ftp://ftp.coast.net/SimTel/win3/diskutil/winima25.zip).
(and soon WINIMA30.ZIP with image file compression !!)
Example :
You create and move to a directory for the boot file, and display the
list of partitions :
C:\>MD BOOTFILE
C:\>CD BOOTFILE
C:\BOOTFILE>BOOTPART
Boot Partition 2.00 for WinNT(c)1995-96 G. Vollant
([EMAIL PROTECTED])
WEB : http://ourworld.compuserve.com/homepages/gvollant/bootpart.htm
Add partition in the Windows NT Multi-boot loader
Run "bootpart /?" for more information
0 : C:* type=6 (BIGDOS Fat16), size = 1044193 KB
1 : C: type=a (OS/2 Boot Manag.), size = 8032 KB
2 : C: type=5 (Extended), size = 8032 KB
3 : C: type=7 (HPFS/NTFS), size = 8001 KB
4 : D: type=6 (BIGDOS Fat16), size = 261104 KB
5 : D: type=5 (Extended), size = 769024 KB
6 : D: type=7 (HPFS/NTFS), size = 102384 KB
7 : D: type=5 (Extended), size = 369664 KB
8 : D: type=7 (HPFS/NTFS), size = 369648 KB
9 : D: type=83 (Linux native), size = 296944 KB
Note : Extended partitions (type 5) are the only partitions that can contain
other partitions. It's not useful to add extended partitions to the NT boot
menu !
The * after C: means that partition 0: is the active partition.
Now, you add some partitions :
C:\BOOTFILE>BOOTPART 9 BOOTLINX.BIN Linux
C:\BOOTFILE>BOOTPART 1 BOOTLINX.BIN Boot Manager OS/2
C:\BOOTFILE>BOOTPART a: BOOTLINX.BIN Boot floppy A:
The last line (A:) is special, and is designed for a BIOS configured for
booting from C: before reading from the floppy (A:) .
The next time you boot, the Windows NT menu will show Linux, OS/2 Boot
Manager, and the floppy !
BOOTPART is a Win32 console application written in C++ and compiled with
Visual C++ 2.2
bootpa32.mak is the Visual C++ Makefile, bootpart.cpp is the source file,
bootpart.exe is the executable, and bootpart.txt is this documentation.
=============================================================================
Fast tips :
To repair the Windows NT boot sector
====================================
Windows NT installs a boot sector that lauches NTLDR and displays the
Windows NT boot menu. If you lose this boot sector, Bootpart can restore
it.
Boot under MS-Dos (this can be MS-Dos 6.22 on your hard disk, on an MS-Dos
bootable floppy, or the "MS-Dos 7.0" included in Windows 95 (you can obtain
it
by pressing Shift+F5 when Win95 loads). Then, enter the command :
BOOTPART WINNT BOOT:C:
If you want to remove the WinNT boot sector, you can replace it with the
command "BOOTPART DOS622 BOOT:C:" or "BOOTPART WIN95 BOOT:C:"
To have both MS-Dos 6.22 and Windows 95 in the NT menu (forgot F4 !)
=======================================================================
The standard situation for a computer that multiboots to Windows NT,
Windows 95, or MS-Dos 6.22 is : the user selects a "Windows 95" entry
in NT menu, and, then must press F4 if he wants to boot MS-Dos 6.22.
If you don't have this situation (i.e. : you don't have both Win95 and
MS-Dos 6.22 on your system, but want to have both), see the next section.
Just enter these bootpart command :
BOOTPART DOS622 C:\BOOTSECT.622 "MS-Dos 6.22"
BOOTPART WIN95 C:\BOOTSECT.W95 "Windows 95"
BOOTPART REWRITEROOT:C:
The last line (REWRITEROOT:C:) MUST BE EXECUTED UNDER MSDOS, and moves the
MS-Dos IO.* and MSDOS.* files to the beginning of the root directory.
You can visit the page : http://www.bcpl.lib.md.us/~dbryan/directboot.html
for more information on booting WinNT/Win95/DOS.
If you have WinNT & Win95 and you only want to add MS-Dos
=========================================================
Take an MSDos 6.22 floppy, copy the files IO.SYS, MSDOS.SYS, and
COMMAND.COM to C:\ as IO.DOS, MSDOS.DOS, and COMMAND.DOS (warning :
these files can be hidden, but you can ask File Manager or Explorer to
display hidden files). Then go to the section "To have both MS-Dos
6.22 and Windows 95 in the NT menu"
If you have WinNT & MS-Dos and you only want to add Win95
=========================================================
Install Win95 in a new directory (start the install under MS-Dos 6.22
or Windows 3.1) and go to the section "To have both MS-Dos 6.22 and
Windows 95 in the NT menu"
To add OS/2
===========
Unfortunatelly, I can't directly add an OS/2 partition by itself (if you
have a workaround or fix, I'd be happy to hear about it !).
Install the OS/2 Boot Manager (you need 1 MB free on your first hard disk),
add the OS/2 partition in the boot menu with automatic start (0 sec.
waiting), and then add the OS/2 Boot Manager partition on your NT menu with
BootPart. Sometimes, when you install OS/2 Boot Manager, it becomes the
active
partition of your first hard disk. You can use FDISK to set the
partition with NT boot manager as the active partition later.
To add Linux
============
For Linux, you must install Lilo at the beginning of the Linux partition
(as with OS/2 boot manager) and then add the Linux partition with Bootpart:
When you install Linux or run liloconfig, select "Superblock of the root
linux partition" as location of Lilo. In my sample, this adds the line
"boot=/dev/sdb4" on the file /etc/lilo.conf
Bootpart is designed for hard drives with 4 GB or less. If this is a problem
for you, contact me.
=================================================================================
Bootpart is cardware.
If you like it, please send me a postcard from your city to:
Gilles Vollant
13, rue F. Mansart
F-91540 Mennecy
France
And try WinImage :
http://ourworld.compuserve.com/homepages/gvollant/winimage.htm
I want thank a lot Matthew Gardiner and Dave Bryan for review of this
documentation.
=================================================================================
This program comes without any warranty either implied or expressed. In no
case shall the author be liable for any damage or unwanted behavior of any
computer hardware and/or software.
=================================================================================
---
Gregory Phillips Seattle, Washington, USA [EMAIL PROTECTED]
------------------------------
From: "David .." <[EMAIL PROTECTED]>
Subject: Re: Emergency boot diskette
Date: Fri, 30 Jun 2000 12:31:10 -0500
Jeff Malka wrote:
>
> I am a newbie who has installed TurboLinux 6 workstation just fine. However
> I do not recall during the installation being asked to create an emergency
> boot diskette (that I read about in books). How do I go about that in an
> installed system?
Emergency Boot Disk
To make an Emergency Boot Disk insert a blank floppy and give the
commands:
fdformat /dev/fd0H1440 # formats 1.44MB floppy
mkbootdisk --device /dev/fd0 x.x.xx # x.x.xx is kernel
version.
Rescue Disk
To make an Emergency boot disk you need a blank floppy and to give the
command:
fdformat /dev/fd0H1440 # formats 1.44 MB floppy
cp /boot/vmlinuz /dev/fd0 # copies the kernel (vmlinuz) to
floppy
rdev # Shows kernel root device such as "/dev/hda5"
rdev /dev/fd0 /dev/hdaX # hdaX root device shown by command
above.
rdev -R /dev/fd0 1 # This makes the root device read only
If you wish to test the new disks simply put one of the disks in A:
and reboot with the command
shutdown -r now
--
Registered with the Linux Counter. http://counter.li.org
ID # 123538
------------------------------
From: "David .." <[EMAIL PROTECTED]>
Subject: Re: Gnome file manager
Date: Fri, 30 Jun 2000 12:33:15 -0500
[EMAIL PROTECTED] wrote:
>
> Hi,
>
> How do I remove this annoying message that comes
> up with I start the Gnome file manager?
>
> 'Warning: You are running file manager as root.
> You can do much damage...'
Don't login as root.
--
Registered with the Linux Counter. http://counter.li.org
ID # 123538
------------------------------
** 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
******************************
