Linux-Misc Digest #670, Volume #24 Thu, 1 Jun 00 01:13:02 EDT
Contents:
Re: redhat 6.2 file sharing/transfer crashes linux (Mark Bratcher)
forgot root password ([EMAIL PROTECTED])
Re: Loop Device (Dances With Crows)
Re: forgot root password (Dances With Crows)
Re: Kernel Building Question ("Walter L. Williams")
Re: forgot root password (Minko Markov)
Re: Can't Mount 6GB FAT32 (Brett Rosselle)
Re: Redirecting the stdout of a running process? (Floyd Davidson)
Re: Linux 2.4.0-test1 (Stewart Honsberger)
Re: Chuckle for the day (Stewart Honsberger)
Re: RH Linux 6.2 and FAT32. (Danger Mouse)
/tmp/acout.* files (Neil Zanella)
Re: /tmp/acout.* files (Prasanth A. Kumar)
Multi-Distribution System Partitioning for Business Evaluation? (Jon McLin)
Re: recursively deleting selected files ("Andrew N. McGuire ")
Re: /tmp/acout.* files (Paul Kimoto)
Re: <><>StartX???<><> ("Peter T. Breuer")
Re: LILO won't boot after update to 2.2.14: "LIWrong loader: giving up." ("Michael
Perry")
Re: forgot root password ("Andrew N. McGuire ")
----------------------------------------------------------------------------
From: Mark Bratcher <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking,comp.os.linux.setup
Subject: Re: redhat 6.2 file sharing/transfer crashes linux
Date: Wed, 31 May 2000 22:16:02 -0400
shahzad bhatti wrote:
>
> I have a small network and I have machines running linux 6.2 and windows 98.
> I exported
> some dirs on linux machine using samba. However, when I try to access or
> copy files from windows 98, after a few minutes it crashes my linux machine.
> I also noticed that
> this happens when I transfer files using ftp. Also, I tried sharing cdrom on
> my linux machine and same thing happen if I try to load files from cdrom
> (after sometime).
> Is this a known bug or is there any solution. Here are messages that I
> sometime see
> before crash:
>
> localhost kernel: VFS: busy inodes on changed media.
> or
> localhost kernel: hdb: irq timeout: status=0xd0 { Busy }
>
> PS: hdb is my cdrom
I have RedHat 6.2 running as a samba server for Win95, Win98, and WinNT4
clients without any problems. I don't think your problem is a bug in the
samba server.
When you say "crash" what do you mean? Does Linux just totally freeze?
Does it reboot? I've never seen it do either of these, but knowing what
yours does might help try to find the problem.
>From the couple of messages you've quoted, it sounds like you might have
a hardware issue. Do you have any problems accessing these shared
devices locally on the Linux box to the extent that you've tried
accessing them on Win98?
--
Mark Bratcher
mailto:[EMAIL PROTECTED]
=========================================================
Escape from Microsoft's proprietary tentacles: use Linux!
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: linux.redhat.misc
Subject: forgot root password
Date: Thu, 01 Jun 2000 02:21:39 GMT
I have forgotten the root password (silly me), how
do I get into the system without reinstall everything ?
Thanks a lot
Sent via Deja.com http://www.deja.com/
Before you buy.
------------------------------
From: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: Loop Device
Date: 31 May 2000 22:32:13 EDT
Reply-To: [EMAIL PROTECTED]
On 1 Jun 2000 01:34:33 GMT, Steve
<<[EMAIL PROTECTED]>> shouted forth into the ether:
>You can create a swap space that sits in a file rather than a partition of a
>disk. These swap files are mounted as swap space st boot time.
Granted, but you don't need the loop device for *that*!
# dd if=/dev/zero of=/swap1 bs=1M count=32
# sync
# mkswap /swap1
# swapon /swap1
# cat >> /etc/fstab
/swap1 swap swap defaults 0 0
^D
...creates a 32M swapspace, enables it, and makes sure that this new
swapspace is automagically mounted at boot time. This is nice when you
temporarily need more swap space, but has disadvantages for a permanent
solution, as swapfiles are slower than dedicated swap partitions. Oh
yeah, you can disable the space at any time with "swapoff" and then
reclaim it for whatever. Despite all the nifty things AIX does, it can't
quite manage that trick yet. :-P.
--
Matt G / Dances With Crows \###| You have me mixed up with more
There is no Darkness in Eternity \##| creative ways of being stupid?
But only Light too dim for us to see \#| Beer is a vegetable. WinNT
(Unless, of course, you're working with NT)\| is the study of cool. --MegaHAL
------------------------------
From: [EMAIL PROTECTED] (Dances With Crows)
Crossposted-To: linux.redhat.misc
Subject: Re: forgot root password
Date: 31 May 2000 23:08:39 EDT
Reply-To: [EMAIL PROTECTED]
On Thu, 01 Jun 2000 02:21:39 GMT, [EMAIL PROTECTED]
<<8h4hbb$5ag$[EMAIL PROTECTED]>> shouted forth into the ether:
>I have forgotten the root password (silly me), how
>do I get into the system without reinstall everything ?
(Re)Boot the system, and at the LILO: prompt, enter
linux S
or
linux init=/bin/sh
The first will work on many systems, giving you root access in single-user
mode. Then you can edit /etc/shadow and change the contents of root's
password field from
root:x4G9sd(@!jk:blah:blah:blah:
to
root::blah:blah:blah:
which will make it so that root has no password at all! After doing this,
you can log in as root and change the password for root to whatever you
want by using the "passwd" command.
The second option will give you a slightly more limited set of options,
but you can still edit /etc/shadow with a bit of fiddling. Some distros,
like SuSE, always require the root password, even in single-user mode, and
the "init=/bin/sh" bypasses that feature. HTH, good luck...
--
Matt G / Dances With Crows \###| You have me mixed up with more
There is no Darkness in Eternity \##| creative ways of being stupid?
But only Light too dim for us to see \#| Beer is a vegetable. WinNT
(Unless, of course, you're working with NT)\| is the study of cool. --MegaHAL
------------------------------
Date: Wed, 31 May 2000 21:33:31 -0600
From: "Walter L. Williams" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,alt.os.linux,alt.linux
Subject: Re: Kernel Building Question
Thank you for the responces. I will go in and look for the unix98
option and enable it and see if that doesn't fix it so I can have a clean
booting kernel.
Walt in Colorado
------------------------------
Crossposted-To: linux.redhat.misc
Subject: Re: forgot root password
From: Minko Markov <[EMAIL PROTECTED]>
Date: Thu, 01 Jun 2000 03:41:03 GMT
[EMAIL PROTECTED] writes:
> I have forgotten the root password (silly me), how
> do I get into the system without reinstall everything ?
>
> Thanks a lot
No need to reinstall, with a bit of luck.
=========== on a typical installation ============
After the PC is powered up, you get the "LILO: "
boot prompt, where the system waits for a while
and then boots the default kernel (or OS). If
you press Tab during the wait, you see all the
available boot options.
Suppose your Linux is booted by "redhat".
Then you type "redhat 1" and press Enter.
Thus you start Linux into run level 1,
which is intended for emergencies (like
your case). Runlevel 1 means minimal boot,
and after no time you are dropped at a
command prompt, as a root, without having
to enter any password.
Then you can type "passwd" and change the
root's password. Have in mind that in runlevel 1
you are in a basic shell (I think "sh"), your
log-in scripts are not executed, so there
are no paths. So, the commands (I think) must
be in full names, e.g. "/bin/ls", rather than
"ls". "passwd" is "/usr/bin/passwd".
=========== your installation may not be typical ========
The bit of luck I was refering to is that
this procedure does not always work. Depending
on how LILO is installed, it *may* be impossible
to boot into runlevel 1, for security reasons.
1) LILO may not wait at all - thus booting into
runlevel 1 is impossible, or
2) you may be asked for a password by LILO, in
order to boot into runlevel 1.
Of course, you realize that the ability for anyone
to boot into r/level 1 is a security risk.
If you cannot boot into r/level 1, try
1) boot diskette (LILO may be installed in a
different way on it) and booting into r/level 1
from it,
2) another Linux installation, if you have one
(I have RedHat and a minimal SuSE, so, if
anything goes really bad in RH, I can boot
SuSE and try to fix it from there),
3) Tom's boot disk: http://www.toms.net/rb/
Some say it is great, I have not tried it.
Good luck.
--
Minko
------------------------------
From: Brett Rosselle <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: Can't Mount 6GB FAT32
Date: Wed, 31 May 2000 22:37:37 -0500
Thanks to everyone who tried to help me. I found the problem.
In the past, I always had Windows installed before I installed Linux, thus the
install would configure LILO for me. Well, this time I was adding Windows after
the fact, and attempting to configure LILO myself. I made one error in my
LILO.CONF file. I used boot=/dev/hda1, when I should have used boot=/dev/hda.
Even with this error, LILO would still boot Linux, but not Windows. It also
apparently screwed up the drive just enough that the mount command would fail.
After I re-ran LILO with the correct setting (boot=/dev/hda), then did a sys c:
from a Windows boot disk, everything worked as it should. LILO now boots both
OS's and the mount command works. Sorry to have bothered you all with this, as
it was my own brainfart that caused the problem.
Thanks for trying to help,
Brett
"Lonni J. Friedman" wrote:
> So you're using:
> mount -t vfat /dev/hda1 /mnt
> to attempt to mount it?
>
> What is the full output of "fdisk -l"?
>
> Brett Rosselle wrote:
> >
> > Error is wring FS type, bad option, bad superblock, on /dev/hda1, or too
> > many mounted file systems. FDISK reports ID c, Win95 FAT32 (LBA) on the
> > 6GB drive.
> >
> > On the 1.6 GB FAT32 drive that I can mount, FDISK reports ID c Win95 FAT32
> > (LBA). They appear to be the same type.
> >
> > I am using Mandrake 7.0, kernel version 2.2.14.
> >
> > Thanks,
> >
> > Brett
> >
> > "Lonni J. Friedman" wrote:
> >
> > > Kinda hard for anyone to help when you fail to state what is wrong.
> > > Error msgs would be nice.
> > >
> > > Brett Rosselle wrote:
> > > >
> > > > Hi all,
> > > >
> > > > Can anyone tell me why I can not mount my 6GB FAT32 drive, but I can
> > > > mount my 1.6 GB FAT32 drive. I'm not a newbie. I know all about the
> > > > FSTAB/MOUNT parameters. This is really bizarre, unless there is some
> > > > size/cylinder limitation that I am unaware of, or there are differences
> > > > between Win95/FAT32 and Win98/FAT32.
> > > >
> > > > Any ideas are greatly appreciated.
------------------------------
From: Floyd Davidson <[EMAIL PROTECTED]>
Subject: Re: Redirecting the stdout of a running process?
Date: 31 May 2000 19:02:06 -0800
"Peter T. Breuer" <[EMAIL PROTECTED]> wrote:
>Dances With Crows <[EMAIL PROTECTED]> wrote:
>: On Wed, 31 May 2000 21:04:53 GMT, George Smiley
>: <<8h3upe$pdo$[EMAIL PROTECTED]>> shouted forth into the ether:
>:>
>:> nohup a.out >& /dev/null &
>:>
>:> I then log out of the workstation and go home. The next day,
>
>In any case, surely the nohup will divert output of the a.out to
>nohup.out? It's the (nonexistent) output of the nohup that you are
>diverting to /dev/null.
>
>: $ nohup a.out >& logfile &
>: (from an xterm, whenever you want it:)
>: $ tail -f logfile
>
>I think (a) you'll be disappointed, that's the output from nohup, not
>from a.out, (b) he's already got the output in nohup.out.
Not so.
tanana:floyd ~/tst >nohup ls >& log.out &
[1] 12036
tanana:floyd ~/tst >ls -l *.out
-rw-r--r-- 1 floyd user 283 May 31 18:58 log.out
[1]+ Done nohup ls >log.out
The output is redirected to the log file first.
--
Floyd L. Davidson [EMAIL PROTECTED]
Ukpeagvik (Barrow, Alaska)
------------------------------
From: [EMAIL PROTECTED] (Stewart Honsberger)
Subject: Re: Linux 2.4.0-test1
Reply-To: [EMAIL PROTECTED]
Date: Thu, 01 Jun 2000 03:57:20 GMT
Regarding the new kernel, a couple of things;
Firstly, on one machine (Intel PII-400, 64M, 6.4G) I run an RC5 personnal
proxy server and the ppstats application to generate HTML statistics. PPStats
uses "gnuplot" as part of its course, and as of kernel 2.4.0-test1 I can no
longer run this application. Even if I run it re-directed to /dev/null and
in the background (&), it still manages to scramble my video (looks somewhat
like an old TV test pattern) and cause a hardware lockup (to the point where
I have to pull the plug on the ATX case I use).
In the mean-time, I've reverted this system back to the 2.2.14 level.
Secondly, I use WMMon both on my personnal machine, and the aforementioned
Intel box, and in both cases the CPU monitoring portion has, for some reason,
decided that while Seti@Home utilizes 100% of the CPU, it will only report
50% usage. Along the same lines, I've just recompiled 2.4.0-test1 on my
personnal machine to optimize for the AMD K62/400 3D processor I just obtained,
and now wmmon won't display any I/O statistics anymore. I switched to wmsysmon
(for other reasons), and it won't show I/O stats anymore, either.
Has anybody else experienced these problems with the 2.4.0-test1 kernel? If
so, is it the kernel, or the application I should be looking into?
Thanks in advance for any input.
--
Stewart Honsberger (AKA Blackdeath) @ http://sprk.com/blackdeath/
[EMAIL PROTECTED] (Remove 'thirteen' to reply privately)
Humming along under SuSE 6.4, Linux 2.2.14
------------------------------
From: [EMAIL PROTECTED] (Stewart Honsberger)
Subject: Re: Chuckle for the day
Reply-To: [EMAIL PROTECTED]
Date: Thu, 01 Jun 2000 04:04:49 GMT
On Tue, 30 May 2000 06:42:47 -0400, Yan Seiner wrote:
>Leave it to MS to convince the public that going from totally
>unacceptable lack of stability to an unacceptable lack of stability is
>progress.
ROTFL!
Point, set, match. {smile}
--
Stewart Honsberger (AKA Blackdeath) @ http://sprk.com/blackdeath/
[EMAIL PROTECTED] (Remove 'thirteen' to reply privately)
Humming along under SuSE 6.4, Linux 2.2.14
------------------------------
From: [EMAIL PROTECTED] (Danger Mouse)
Subject: Re: RH Linux 6.2 and FAT32.
Date: 1 Jun 2000 04:06:26 GMT
I have 3 fat32 partitions. I can get linux to read 2 of them, the other I
cannot get to mount at all.
How can I get the other one to mount (I am going through the gui linuxconf),
and how can I get the other two to Write-To (I was logged in as root).
DM
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] says...
>
>THis has nothing to do with Redhat. Linux does not get installed on a
>fat32 filesystem. Linux gets installed on an ext2 file system. Linux
>can read/write fat32.
>
>Michael Brailsford wrote:
>>
>> Are there any problems installing RH 6.2 on a FAT32 system? I've read the
>> kernal 2.2 and higher can read understand FAT32, but RedHat.com said the
>> make sure that you are not using FAT32. Is RedHat.com just behind the
>> times, or can RH 6.2 just not support FAT32?
------------------------------
From: Neil Zanella <[EMAIL PROTECTED]>
Subject: /tmp/acout.* files
Date: Thu, 1 Jun 2000 02:00:57 -0230
Hello,
I have the following files on my RHL 5.2 system under /tmp and I would
like to know what they are all about. Any ideas?
-rw------- 1 root root 0 May 27 21:00 acout.a00507
-rw------- 1 root root 0 May 24 04:59 acout.a00548
-rw------- 1 root root 0 May 23 23:35 acout.a01472
-rw------- 1 root root 0 May 23 21:53 acout.a01527
-rw------- 1 root root 0 May 24 05:20 acout.a02751
-rw------- 1 root root 0 May 23 21:56 acout.a04095
-rw------- 1 root root 0 May 27 21:17 acout.a04529
-rw------- 1 root root 0 May 24 00:37 acout.a06189
-rw------- 1 root root 0 May 27 21:31 acout.a06450
-rw------- 1 root root 0 May 24 00:41 acout.a06966
-rw------- 1 root root 0 May 27 21:32 acout.a07662
-rw------- 1 root root 0 May 23 22:28 acout.a10767
-rw------- 1 root root 0 May 27 21:36 acout.a11099
-rw------- 1 root root 0 May 27 21:38 acout.a13013
-rw------- 1 root root 0 May 27 21:42 acout.a15298
-rw------- 1 root root 0 May 27 21:46 acout.a17218
-rw------- 1 root root 0 May 27 21:52 acout.a20220
-rw------- 1 root root 0 May 27 22:07 acout.a26305
-rw------- 1 root root 0 May 27 22:10 acout.a27253
Thanks,
Neil
------------------------------
Subject: Re: /tmp/acout.* files
From: [EMAIL PROTECTED] (Prasanth A. Kumar)
Date: Thu, 01 Jun 2000 04:34:22 GMT
Neil Zanella <[EMAIL PROTECTED]> writes:
> Hello,
>
> I have the following files on my RHL 5.2 system under /tmp and I would
> like to know what they are all about. Any ideas?
>
> -rw------- 1 root root 0 May 27 21:00 acout.a00507
> -rw------- 1 root root 0 May 24 04:59 acout.a00548
> -rw------- 1 root root 0 May 23 23:35 acout.a01472
> -rw------- 1 root root 0 May 23 21:53 acout.a01527
> -rw------- 1 root root 0 May 24 05:20 acout.a02751
> -rw------- 1 root root 0 May 23 21:56 acout.a04095
> -rw------- 1 root root 0 May 27 21:17 acout.a04529
> -rw------- 1 root root 0 May 24 00:37 acout.a06189
> -rw------- 1 root root 0 May 27 21:31 acout.a06450
> -rw------- 1 root root 0 May 24 00:41 acout.a06966
> -rw------- 1 root root 0 May 27 21:32 acout.a07662
> -rw------- 1 root root 0 May 23 22:28 acout.a10767
> -rw------- 1 root root 0 May 27 21:36 acout.a11099
> -rw------- 1 root root 0 May 27 21:38 acout.a13013
> -rw------- 1 root root 0 May 27 21:42 acout.a15298
> -rw------- 1 root root 0 May 27 21:46 acout.a17218
> -rw------- 1 root root 0 May 27 21:52 acout.a20220
> -rw------- 1 root root 0 May 27 22:07 acout.a26305
> -rw------- 1 root root 0 May 27 22:10 acout.a27253
>
> Thanks,
>
> Neil
Those are temporary storage files created by programs for short term
use. They can generally be erased if not touched for a while or if you
are sure no program is using them.
--
Prasanth Kumar
[EMAIL PROTECTED]
------------------------------
Date: Thu, 01 Jun 2000 04:41:29 +0000
From: Jon McLin <[EMAIL PROTECTED]>
Subject: Multi-Distribution System Partitioning for Business Evaluation?
Due to his personal experience with excessive Microsoft Moments and the
associated productivity impacts, the CEO has issued an edict that MS Windows
will not be the primary OS at our company within the next 12 months. (No, I did
NOT set him up!)
For several years I've been running RH and more recently Mandrake at home, but
I'd like to evaluate all Linux distributions (and potentially FreeBSD et. al.)
for workstation usage before a full deployment. For this purpose, I wish to set
up a single machine upon which I can install many distributions (plus Win4Lin
and VMWare, for legacy purposes).
I see two basic alternatives:
a. A physical disk-swapping system. In this configuration, I'd put one of
the removable IDE trays in a machine, and purchase an IDE drive and drawer for
each distribution to be evaluated. A non-swappable drive would contain /home,
Windows 98, Windows NT, and probably /tmp and a swap partition. All other
partitions (plus another swap partition) would be on the removable drive.
b. Fixed disk with a set of partitions per distribution. In this
configuration, I'd just use really big disks, and create a set of unique
partitions for each distribution.
Queries, for those more knowledgeable:
Which option is best, and why? (beyond the obvious procurement cost
distinctions)
What filesystems should be shared vs. unique to a distibution?
Any thoughts on the partioning scheme in this case?
Any other recommendations for constructing an evaluation system?
Presently I do not have a concise set of evaluation criteria, so recommendations
on such are also solicited. My primary focus here is workstation evaluation,
although I also need to configure workgroup servers for file sharing, mail,
calendaring, source-code control, business databases, and internal web serving.
(Once I've selected a few - two or three - distributions as candidates for
deployment, I'll move to a trial usage phase, with actual users evaluating the
distributions in day-to-day activities. I also solicit thoughts on
criteria/evaluation techniques to use during this phase. Obviously, this is
presently a lower priority than the former.)
Workstation usage is primarily:
Business applications (word processing and spreadsheets)
Database clients (porting our legacy internal applications from VB to Java is
presently considered trivial).
SW Development (C, C++, Java, Python)
Presently I am supporting about 25 users at a single location, but need to
increase this to three locations and 50 users in one year.
Thanks in advance for your reasoned input,
Jon
------------------------------
From: "Andrew N. McGuire " <[EMAIL PROTECTED]>
Subject: Re: recursively deleting selected files
Date: Wed, 31 May 2000 23:55:40 -0500
On 31 May 2000, Bastian wrote:
+ On Wed, 31 May 2000 19:08:49 GMT, Thomas Clancy wrote:
+ >Hey All,
+ >
+ >Okay, this is a very dumb question. I want to be able to recursively delete
+ >selected files in a subdirectory. Bascially I have a java project and
+ >various packages. I want to just start from the top and delete all *.class
+ >files. This doesn;t work
+ >
+ >rm -r *.class
+ >
+ >not this:
+ >
+ >rm -R com/*.class
+ >
+ >nor any combination therein. I know there has got to be a simple
+ >explanation. Can anyone help?
+ >
+ >-tom
+
+ for i in $(find /yourdirectory -name '*.class' -printf "%p%n "); do rm $i; done
Yikes! From the current working directory:
find . -type f -name '*.class' -exec rm {} \;
anm
--
/*-------------------------------------------------------.
| Andrew N. McGuire |
| [EMAIL PROTECTED] |
`-------------------------------------------------------*/
------------------------------
From: [EMAIL PROTECTED] (Paul Kimoto)
Subject: Re: /tmp/acout.* files
Date: 1 Jun 2000 00:56:12 -0500
Reply-To: [EMAIL PROTECTED]
In article <[EMAIL PROTECTED]>,
Neil Zanella wrote:
> I have the following files on my RHL 5.2 system under /tmp and I would
> like to know what they are all about. Any ideas?
>
> -rw------- 1 root root 0 May 27 21:00 acout.a00507
> -rw------- 1 root root 0 May 24 04:59 acout.a00548
[etc.]
Aren't these names characteristic of "autoconf"?
--
Paul Kimoto <[EMAIL PROTECTED]>
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: <><>StartX???<><>
Date: 1 Jun 2000 04:47:20 GMT
Floyd Davidson <[EMAIL PROTECTED]> wrote:
: "Peter T. Breuer" <[EMAIL PROTECTED]> wrote:
:>N/A <[EMAIL PROTECTED]> wrote:
:>: Fatal server error:
:>: No Valid Fontpath could be found
:>
:>: X Connection to :0.0 broken (explicit kill or server shutdown).
:>
:>: that describes the error i get when typing "startx" to enter into linux as
:>: either the 'root' user or my username. What is the Problem please!!!
:>
:>No Server. Read its error messages when it starts up. You probably forgot
:>to configure it.
: No Server??? The message above is *from* the server (the X
Yes, quite right. I didn't see the first message. I meant the second
message, which I thought was the one being referred to. The second
message says "no server". And indeed there is none, as we can see from
the first message, which is from the server and says "I am dead".
: server, and a font server is not required).
The server died because it couldn't find any valid fonts, because its
fontpath does not correspond to anything with usable fonts in. The
usual reason is that the server is relying exclusively on a separate
fontserver (so the fontpath will be something like "unix:7100") and the
fontserver is not starting up. Usually that's because of a corrupted
fontdir database or leftover xfs.pid file.
: But obviously you are right that the font configuration for the
: server is not correct. In the XF86Config file there should be a
: section named "Files", and in that section should be a number of
: statements for paths to font files. It should look something
: like this:
: Section "Files"
: FontPath "/var/X11R6/lib/fonts/misc/"
: FontPath "/var/X11R6/lib/fonts/75dpi/"
: EndSection
: With perhaps several FontPath entries, and/or if a font server is
: in use there might be an entry like this:
: FontPath "tcp/localhost:7000"
: Where "localhost" is the host where a fonts sever is found, and 7000
: is the port.
: It may be that the XF86Config file has the configuration, but the
: fonts were never installed.
Very possibly. I suppose he's relying on a non-functioning xfs.
Peter
------------------------------
From: "Michael Perry" <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.setup,alt.uu.comp.os.linux.questions,hannover.uni.comp.linux,de.comp.os.unix.linux.newusers,alt.os.linux.suse
Subject: Re: LILO won't boot after update to 2.2.14: "LIWrong loader: giving up."
Date: Wed, 31 May 2000 22:04:17 -0800
In article
<[EMAIL PROTECTED]>, Andrei
Dumitrescu <[EMAIL PROTECTED]> wrote:
>
> Hi there folks, maybe some of you could help me (please please please)
> with my problem here. I have a PC with Win NT and Linux. I'm using NT's
> boot manager to select what OS to boot. Last week I updated my linux
> distro (SuSE 6.2) to 2.2.14
> (SuSE 6.4), using the (semi)automatic update procedure from SuSE's setup
> tool. After completion of the process I tried to reboot from hdd, but
> after selecting Linux (as usual) from NT's boot manager, LILO wouldn't
> boot linux, saying
> LIWrong loader: giving up.
> I then tried to reinstall/reconfigure LILO either using Yast (the SuSE
> setup tool), or manually by editing lilo.conf and then running
> /sbin/lilo, but it still wouldn't work, and I can still boot linux only
> from the boot/install floppy, which is quite cumbersome esp. since I
> frequently need apps from both Linux and NT. Here's what my lilo.conf
> looks like at the moment:
>
> # LILO configuration file
> # Start LILO global Section
> # If you want to prevent console users to boot with init=/bin/bash,
> # restrict usage of boot params by setting a passwd and using the
> option
> # restricted.
> #password=bootpwd
> #restricted
> boot=/dev/hda5
> #compact # faster, but won't work on all systems.
> vga=normal read-only prompt timeout=050
> # End LILO global Section
> #
> image = /boot/vmlinuz
> root = /dev/hda5 label = linux
>
> Please post any suggestions. TIA, Andrei
>
Did you strip away the bootsector from your linux partition and put it onto the ntfs
partition
that your NT bootloader is installed into after you upgraded? I bet if you restripped
the 512
bytes of boot sector information from your suse linux partition and placed it on the
ntfs
partition that you would get Linux back booting from the NT boot loader.
--
Michael Perry
[EMAIL PROTECTED]
==================
------------------------------
Crossposted-To: linux.redhat.misc
From: "Andrew N. McGuire " <[EMAIL PROTECTED]>
Subject: Re: forgot root password
Date: Thu, 1 Jun 2000 00:08:34 -0500
On Thu, 1 Jun 2000, [EMAIL PROTECTED] wrote:
+ I have forgotten the root password (silly me), how
+ do I get into the system without reinstall everything ?
What I usually do is boot from the installation media,
or boot diskette, mount my root partition under /mnt,
then edit /etc/shadow and just null out the passwd field.
Then unmount the root partition, reboot, and set the passwd
one keystroke at a time. :-)
Regards,
anm
--
/*-------------------------------------------------------.
| Andrew N. McGuire |
| [EMAIL PROTECTED] |
`-------------------------------------------------------*/
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.misc) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Misc Digest
******************************
