Tom Brinkman ([EMAIL PROTECTED]) wrote:
> On Saturday 11 December 2004 03:50 pm, RickSisler wrote:
> > Also drawing from your experience,
> > wouldn't *dmidecode* be of use in this case to see what a bios
> > supports ?
> About all you can do with Linux is to try trial'n error to see
> if your
On Saturday 11 December 2004 03:50 pm, RickSisler wrote:
> Also drawing from your experience,
> wouldn't *dmidecode* be of use in this case to see what a bios
> supports ?
>
> The reason I ask, IIRC ..was of a post about what the bios
> reporting information, on this list or the expert list ..
> ar
On Sunday 12 December 2004 06:01, Keith Powell wrote:
> Also, there are no Newbie archives for December.
> So I can't check there.
Keith, there are more than one archive. Try here :
http://www.mail-archive.com/newbie@linux-mandrake.com/maillist.html
Kaj Haulrich.
--
*sent from a 100% Microso
On Saturday 11 December 2004 07:03, Tom Brinkman wrote:
> On Friday 10 December 2004 09:37 pm, care free wrote:
> > I wonder if it is acpi=on or set you acpi on in your bios
> >
> > J.T.
>
>According to past and present kernel-parameters.txt, acpi=on
> is _not_ a valid option.
>
ction
automatically. I wonder if it has anything to do with the bios.
J.T.
From: Keith Powell <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
Subject: Re: [newbie] Shutdown problem (update)
Date: Sat, 11 Dec 2004 16:14:26 +
Things have changed regarding my
Tom Brinkman ([EMAIL PROTECTED]) wrote:
> I appreciate the addition Rick. Let me take this opportunity
> to add a caution to your post, but more so to previous replies I
> sent in this thread.
>
> ** Unless you know what you're doing, don't edit kernel config
> files by hand and then
On Saturday 11 Dec 2004 16:14, Keith Powell wrote:
> Things have changed regarding my shutdown problem, but have got even more
> confusing.
>
> I have installed several distributions in turn, on my spare hard drive to
> see what shutdown problems there are with other distros. There were none
> with
Things have changed regarding my shutdown problem, but have got even more
confusing.
But first, I have just connected for the first time today, to get my e-mails
and postings. I have found that there is nothing from the list between about
eight o'clock last night (GMT, or UTC) and mid-day today
On Friday 10 December 2004 09:37 pm, care free wrote:
> I wonder if it is acpi=on or set you acpi on in your bios
>
> J.T.
According to past and present kernel-parameters.txt, acpi=on
is _not_ a valid option.
...
acpi= [HW,ACPI] Advanced Configuration and
On Friday 10 December 2004 07:30 pm, RickSisler wrote:
> Kaj Haulrich ([EMAIL PROTECTED]) wrote:
> > On Friday 10 December 2004 21:47, Tom Brinkman wrote:
> > > On Friday 10 December 2004 08:53 am, Keith Powell wrote:
> > > > > In /etc/lilo.conf try editing the append-line,
> > > > > especially the
I wonder if it is acpi=on or set you acpi on in your bios
J.T.
From: Keith Powell <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [newbie] Shutdown problem
Date: Fri, 10 Dec 2004 10:37:13 +
I KNOW that this has been asked before, but I can't find th
Kaj Haulrich ([EMAIL PROTECTED]) wrote:
> On Friday 10 December 2004 21:47, Tom Brinkman wrote:
> > On Friday 10 December 2004 08:53 am, Keith Powell wrote:
> > > > In /etc/lilo.conf try editing the append-line, especially the
> > > > apic thing. Remove it completely or set it to apic=ht or
> > > >
On Friday 10 December 2004 21:47, Tom Brinkman wrote:
> On Friday 10 December 2004 08:53 am, Keith Powell wrote:
> > > In /etc/lilo.conf try editing the append-line, especially the
> > > apic thing. Remove it completely or set it to apic=ht or
> > > noapic.
> > >
> > > HTH
> > > Kaj Haulrich.
> >
>
Keith Powell wrote:
Margot wrote:
Kaj Haulrich wrote:
On Friday 10 December 2004 11:37, Keith Powell wrote:
I have a new machine, and now, when I close down, everything
closes down correctly, but then Mandrake does not actually switch
the computer off.
If I remember correctly, there is something to
On Friday 10 December 2004 02:20 pm, Keith Powell wrote:
>
> Sometime, I must find out the difference between apic and apci - I
> thought they were almost the same!
APIC - Advanced Programmable Interrupt Controller
ACPI - Advanced Configuration and Power Interface
--
Alan
__
Margot wrote:
Kaj Haulrich wrote:
On Friday 10 December 2004 11:37, Keith Powell wrote:
I have a new machine, and now, when I close down, everything
closes down correctly, but then Mandrake does not actually switch
the computer off.
If I remember correctly, there is something to change in the
lilo.
Tom Brinkman wrote:
On Friday 10 December 2004 08:53 am, Keith Powell wrote:
apic=off has solved it.
The append line was already apic=ht, so I first changed it to
noapic and then apic=noapic. Neither had any effect.
APIC, advance programable interrupt control. If your system
works better wit
On Friday 10 December 2004 08:53 am, Keith Powell wrote:
> > In /etc/lilo.conf try editing the append-line, especially the
> > apic thing. Remove it completely or set it to apic=ht or
> > noapic.
> >
> > HTH
> > Kaj Haulrich.
>
> Thanks, Kaj.
>
> apic=off has solved it.
>
> The append line was alr
On Friday 10 December 2004 15:48, Margot wrote:
> Kaj, I think you're mixing up apic and acpi!
Yes. Sorry. Never came to grips with this alphabet-thingy.
Kaj Haulrich.
--
*sent from a 100% Microsoft-free workstation*
* http://haulrich.net *
*Running Linux (Mandrake 10.1) - kernel 2
Kaj Haulrich wrote:
On Friday 10 December 2004 11:37, Keith Powell wrote:
I KNOW that this has been asked before, but I can't find the
answer in the archives or in twiki. Sorry for asking it again.
I have a new machine, and now, when I close down, everything
closes down correctly, but then Mandrake
Kaj Haulrich wrote:
On Friday 10 December 2004 11:37, Keith Powell wrote:
I KNOW that this has been asked before, but I can't find the
answer in the archives or in twiki. Sorry for asking it again.
I have a new machine, and now, when I close down, everything
closes down correctly, but then Mandrake
On Friday 10 December 2004 11:37, Keith Powell wrote:
> I KNOW that this has been asked before, but I can't find the
> answer in the archives or in twiki. Sorry for asking it again.
>
> I have a new machine, and now, when I close down, everything
> closes down correctly, but then Mandrake does not
I KNOW that this has been asked before, but I can't find the answer in
the archives or in twiki. Sorry for asking it again.
I have a new machine, and now, when I close down, everything closes down
correctly, but then Mandrake does not actually switch the computer off.
If I remember correctly, the
Hello!
Not a big issue, but...
I run two dual processor machines and both are unable
to shutdown completely. It stops at the black screen
saying "power down", but I have to press the power
switch. There was a kernel setting on BeOS to allow
complete shutdown. Is there a similar trick in
Mandrake
Thank you.
Jeff Malka <[EMAIL PROTECTED]>
Registered Linux user 183185
- Original Message -
From: A V Flinsch <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, September 02, 2000 5:11 PM
Subject: Re: [newbie] Shutdown problem
> On Sat, 02 Sep 2000,
> Run junkbuster & squid as procies
What are these? Are they included in Mandrake 7.1?
Jeff Malka <[EMAIL PROTECTED]>
Registered Linux user 183185
On Fri, 01 Sep 2000, you wrote:
> Hi,
>
> I'm a new user of Linux from India. I've with me LM 7.1 Complete. I've two
> problems
>
> 1. When I issue the Shutdown command from the console of KDE desktop, it
> will close X-Windows and restarts (without rebootng) Linux in character
> based single
>
> 1. When I issue the Shutdown command from the console of KDE desktop, it
> will close X-Windows and restarts (without rebootng) Linux in character
> based single user mode. Here it automatically logins as root without asking
> any password, even if I was logged as a normal user when issuin
Hi,
I'm a new user of Linux from India. I've with me LM 7.1 Complete. I've two
problems
1. When I issue the Shutdown command from the console of KDE desktop, it
will close X-Windows and restarts (without rebootng) Linux in character
based single user mode. Here it automatically logins as root
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, June 11, 2000 6:56 PM
> Subject: Re: [newbie] Shutdown problem with v7.0...
>
> > flupke wrote:
> >
> > > Sorry, I didn't follow this tread from the begining, so I hope I won't
> say
> > > anything
56 PM
Subject: Re: [newbie] Shutdown problem with v7.0...
> flupke wrote:
>
> > Sorry, I didn't follow this tread from the begining, so I hope I won't
say
> > anything stoopid or something that has already been said.
> > If I understand, the problem here is all the dum
Dennis Myers wrote:
> Followup to this thread, I figured out how to edit (hooray!!!) and went
> in to the above listed /etc/ files and deleted the -p and voila! the
> error message is gone when I "halt" the sys. I think that I am
> beginning to get the hang of some of this and am falling in l
Dacia and AzureRose wrote:
> hmmm...both of the computers I've seen this problem on
> had Via chipsets on their motherboards.
>
> Dacia
> --- flupke <[EMAIL PROTECTED]> wrote:
> > Sorry, I didn't follow this tread from the begining,
> > so I hope I won't say
> > anything stoopid or something that
Thanks Ronald...I will try this.
Seems funny though that if it doesn't find it there (and
it does look there) it also looks in my /home/fran directory
and still doesn't find it.
Not sure what the problem is there, but will put it in the
share directory and see if it helps.
Thanks,
Bambi
"Ronal
On Sun, 11 Jun 2000, Dennis Myers wrote:
> flupke wrote:
>
> > Sorry, I didn't follow this tread from the begining, so I hope I won't say
> > anything stoopid or something that has already been said.
> > If I understand, the problem here is all the dump of the stack and
> > registers caused by a
Fran Parker wrote:
> Now do you you know how to get lxdoom to work..it says it can't
> find an IWAD...I have downloaded the shareware 1.8 wad file,
> I have gone to get the iwad file they had and unzipped it...doom1.wad
> Anyway it can't find it and I tried to run it in terminal window to see
> i
Dacia and AzureRose wrote:
>
> hmmm...both of the computers I've seen this problem on
> had Via chipsets on their motherboards.
>
> Dacia
Not sure if I have a Via chipset or not? I do
have a socket 7 MB, (Gigabyte GA-5AX), and it
uses the ALI Aladdin V AGPset... Oh well.
Fran Parker wrote:
> That could be true flupke, mine is a VIA chipset.
>
> It doesn't seem to hurt anything, if I accidentally choose
> shutdown, I just choose alt-cntrl-del and it finishes it.
>
> But if it can be fixed...cool. I will look into it with my system.
>
> Thanks,
> Bambi
>
> Now do
That could be true flupke, mine is a VIA chipset.
It doesn't seem to hurt anything, if I accidentally choose
shutdown, I just choose alt-cntrl-del and it finishes it.
But if it can be fixed...cool. I will look into it with my system.
Thanks,
Bambi
Now do you you know how to get lxdoom to work
flupke wrote:
> Sorry, I didn't follow this tread from the begining, so I hope I won't say
> anything stoopid or something that has already been said.
> If I understand, the problem here is all the dump of the stack and
> registers caused by a page default or something at the end of a shutdown.
>
hmmm...both of the computers I've seen this problem on
had Via chipsets on their motherboards.
Dacia
--- flupke <[EMAIL PROTECTED]> wrote:
> Sorry, I didn't follow this tread from the begining,
> so I hope I won't say
> anything stoopid or something that has already been
> said.
> If I understan
That probably will not work. My brother disabled the
apm daemon in linux not advanced power management in
his BIOS. I had to do BOTH to make mine work.
The easiest way I know to disable the apmd is to open
DrakConf, click startup services and uncheck the box
by apmd. It won't take affect until
That worked on my brother computer. He has a SOYO
socket 7 motherboard. I forget the exact model. He
disabled apmd and it got better. When I had that same
motherboard in my old computer I had to disable
Advanced power management in my bios and apmd to get
it to stop.
Dacia
--- Paul <[EMAIL P
Sorry, I didn't follow this tread from the begining, so I hope I won't say
anything stoopid or something that has already been said.
If I understand, the problem here is all the dump of the stack and
registers caused by a page default or something at the end of a shutdown.
I have the same problem
"Ronald J. Hall" wrote:
> Paul wrote:
>
> > APM is a service in Linux. You can disable it by running 'setup' as root,
> > it is in 'system services'.
> >
> > Paul
>
> Ah, got it. I just printed out your reply, will
> try that next. Ignore my earlier question! ;-)
Dennis M. here, It also can be
On Sun, 11 Jun 2000, Ronald J. Hall wrote:
>> Oops, it was not APM in the BIOS, but the APMD daemon that Dacia
>> said that was disabled!!
>> Sorry!
>
>Argh, I missed that too...anyways, I turned off
>power management in Bios and of course, it made
>nary a difference.
>
>So...how do I disable the
Paul wrote:
> APM is a service in Linux. You can disable it by running 'setup' as root,
> it is in 'system services'.
>
> Paul
Ah, got it. I just printed out your reply, will
try that next. Ignore my earlier question! ;-)
Thanks Paul will look into that end of things. I didn't
think I had that enabled in the bios.
Bambi
Paul wrote:
> On Sun, 11 Jun 2000, Ronald J. Hall wrote:
>
> >Hi Dacia. Hmm. I'll go into my Bios and try that
> >then. Power management -is- working here though.
> >My system goes through the s
Paul wrote:
> Oops, it was not APM in the BIOS, but the APMD daemon that Dacia
> said that was disabled!!
> Sorry!
>
> Paul
Argh, I missed that too...anyways, I turned off
power management in Bios and of course, it made
nary a difference.
So...how do I disable the APMD daemon? ;-)
Thanks!
Hi Ronald,
I have a dual boot system with Win98 and Linux Mandrake 7.0 (Air).
Actually I have a Celeron 366mhz ...I do not use power-management.
I have one hard drive that doesn't recover from power-management
on the hard drives (old 540 meg - my 3rd drive - is actually mainly a place
holder mo
On Sun, 11 Jun 2000, Ronald J. Hall wrote:
>Hi Dacia. Hmm. I'll go into my Bios and try that
>then. Power management -is- working here though.
>My system goes through the stages, the screen-
>saver kicks in (love that Matrix one!), then a
>few minutes later, the monitor goes black, etc,
>etc,...
On Sat, 10 Jun 2000, Fran Parker wrote:
>Same hereI don't shutdown the computer...I only reboot and shut
>off the computer from there, I hate getting error messages! :)
>
>> BTW, I can shutdown and restart, and I do NOT
>> get this problem. Odd, eh?
Did you all get the message Dacia sent in?
On Sat, 10 Jun 2000, Fran Parker wrote:
>Same hereI don't shutdown the computer...I only reboot and shut
>off the computer from there, I hate getting error messages! :)
>
>Bambi
Oops, it was not APM in the BIOS, but the APMD daemon that Dacia
said that was disabled!!
Sorry!
Paul
--
Read t
I don't have your original message here...but I think you said you were using
an AMD CPU...I think there was a shutdown problem and a subsequent patch for
itmaybe that is the problem. (if I am remembering your hardware
correctly)
HTH
Jaguar
"Ronald J. Hall" <[EMAIL PROTECTED]> wrote:
> Paul
Same hereI don't shutdown the computer...I only reboot and shut
off the computer from there, I hate getting error messages! :)
Bambi
"Ronald J. Hall" wrote:
> Paul wrote:
>
> > You listed your hardware well, but could you also be more specific about
> > the error message?
> > It is difficu
My brother had this same problem and we found that in
his case it was because of a conflict between his
motherboard advanced power management features and the
way linux was trying to access those functions.
He disabled apmd and it stopped happening.
Dacia
--- "Ronald J. Hall" <[EMAIL PROTECTE
Paul wrote:
> You listed your hardware well, but could you also be more specific about
> the error message?
> It is difficult to understand what happens when "something to do with
> rec.d" is all the info we have.
>
> Thanks for segmenting again,
> Paul
>
> --
> I'm not a complete idiot.
> Some
On Sat, 10 Jun 2000, Ronald J. Hall wrote:
>Until shutdown. No matter how I shutdown, from
>the graphical logon screen, to "shutdown now"
>from a shell, I always get a final B&W text
>screen that displays a segmentation error, with
>an error in line x, something to do with rec.d.
You listed your
Here is my setup:
AMD K6-3 @475mhz
128 megs of Ram
Voodoo 3000
SB Xgamer
Gigabyte MB
Award BIOS
Western Digital Caviar series HD
Diamond Supra internal (ISA) v.90 modem
Mandrake v7.0 PowerPack
I built this system, and installed everything by
myself, (and I'm a newbie) so beware...
Anyways, eve
halt
Angel Claudio Alvarez
-Mensaje original-
De: evan light [mailto:[EMAIL PROTECTED]]
Enviado el: Jueves 13 de Abril de 2000 17:41
Para: newbie
Asunto: [newbie] shutdown problem
Hi there...having a bit of a problem with shutting down 7.0. When I
issue the "shutdow
For problems of this sort, try reading the man page for the program or
utility you're trying to use and don't seem to be able to get to work as
you want.
E.g.,
% man shutdown
-h now is correct, but it's also important for newbies to be aware of
the man pages and knowing this ca
evan light <[EMAIL PROTECTED]> wrote:
> Hi there...having a bit of a problem with shutting down 7.0. When I
> issue the "shutdown now" command, everything seems fine and dandy until
> it switches into "single-user" mode. If I try ctl-ald-del at the
> single-user prompt, I get the message "no aut
evan light wrote:
>
> Hi there...having a bit of a problem with shutting down 7.0. When I
> issue the "shutdown now" command, everything seems fine and dandy until
> it switches into "single-user" mode.
That doesn't at all fine and dandy to me. It shouldn't be going into
single user mode, it sh
shutdown -h now
--- evan light <[EMAIL PROTECTED]> wrote:
> Hi there...having a bit of a problem with shutting
> down 7.0. When I
> issue the "shutdown now" command, everything seems
> fine and dandy until
> it switches into "single-user" mode. If I try
> ctl-ald-del at the
> single-user prompt
shutdown -h now
--- evan light <[EMAIL PROTECTED]> wrote:
> Hi there...having a bit of a problem with shutting
> down 7.0. When I
> issue the "shutdown now" command, everything seems
> fine and dandy until
> it switches into "single-user" mode. If I try
> ctl-ald-del at the
> single-user prompt
Hi there...having a bit of a problem with shutting down 7.0. When I
issue the "shutdown now" command, everything seems fine and dandy until
it switches into "single-user" mode. If I try ctl-ald-del at the
single-user prompt, I get the message "no authorized users logged in."
If I try shutdown ag
On Tue, 13 Jul 1999, you wrote:
>
> You did just "su", not "su -". The difference is that "su -" reruns the
> login scripts, etc., so you get the right PATH for root.
>
Ah. I just learned something new. :-) I didn't know about
"su -" Thanks. :-)
--
John Aldrich
COL Tech Support
On Tue, 13 Jul 1999, you wrote:
>
> When you do "su" you don't always get the PATH environment of root
> (depending on the system)
> The above error was because "timed" is not in your path - not
> because you cannot run it. Try "/usr/sbin/timed" instead.
>
Ahh...Ok. That makes a bit of sense the
On Tue, 13 Jul 1999, John Aldrich wrote:
> Okone I can give you right off the top is "timed" It
> will NOT run as SuperUser, but it WILL run as "root." It
> comes back with "timed command not found." This is from a
> text-mode prompt, not a window prompt, just a standard
> shell prompt. Howev
John Aldrich wrote:
> Okone I can give you right off the top is "timed" It
> will NOT run as SuperUser, but it WILL run as "root." It
> comes back with "timed command not found." This is from a
It will still run just fine as su, but you need to specify the path to
it. When you su, i
At 12:20 13/07/99 -0400, you wrote:
>On Tue, 13 Jul 1999, you wrote:
>
>> For a program to run as root and not when su - root, it would have to
>> step thru parent pid's looking specificly for su (it could test the parent
>> pids uid, they all eventualy lead to root), which is posible but ugly.
>>
On Tue, 13 Jul 1999, you wrote:
> For a program to run as root and not when su - root, it would have to
> step thru parent pid's looking specificly for su (it could test the parent
> pids uid, they all eventualy lead to root), which is posible but ugly.
> As for editing system files, I am quite c
On Tue, 13 Jul 1999, John Aldrich wrote:
> On Tue, 13 Jul 1999, you wrote:
>
> >
> > there isn't a single difference between su - and loging in as root (ok one
> > the utmp entry, but that has nothing todo with anything major)
> >
> Well, MY experience has been that there are some
> applica
On Tue, 13 Jul 1999, you wrote:
>
> there isn't a single difference between su - and loging in as root (ok one
> the utmp entry, but that has nothing todo with anything major)
>
Well, MY experience has been that there are some
applications that can ONLY be run as "root." Editing system
files a
a single difference between su - and loging in as root (ok one
the utmp entry, but that has nothing todo with anything major)
> - Original Message -
> From: Rhichard Barth & Family <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, July 11, 1999 5:22 PM
&g
IL PROTECTED]>
Sent: Sunday, July 11, 1999 5:22 PM
Subject: Re: [newbie] shutdown problem fixed
>
>
> John Aldrich wrote:
>
> > Log in as "root" instead of a normal user. Try that instead of SU.
> > John
>
> I did log on as "root"
got to be one of the greatest sites there is.
I owe you guys.
I'll be back!
Rhich
"The Phoneless Guy"
Icq 8150164
>
> - Original Message -
> From: Rhichard Barth & Family <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday
Log in as "root" instead of a normal user. Try that instead of SU.
John
- Original Message -
From: Rhichard Barth & Family <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, July 11, 1999 7:54 AM
Subject: Re: [newbie] shutdown problem fixed
John Aldrich wrote:
Are you editing the file as "root"? If not, that's
a "system file" and only
"root" can edit it.
- Original Message -
From: Rhichard Barth & Family <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, J
Are you editing the file as "root"? If not, that's a "system file" and only
"root" can edit it.
- Original Message -
From: Rhichard Barth & Family <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, July 10, 1999 6:48 PM
Subject:
On Sat, 10 Jul 1999, Rhichard Barth & Family wrote:
>
>
> Axalon wrote:
>
> > On Wed, 30 Jun 1999, Flight16 wrote:
> >
> > > For anybody else having the problem I was of a huge error crashing their system
> > > whenever the shutdown script tried to halt, it is because of the power off
>comm
Axalon wrote:
On Wed, 30 Jun 1999, Flight16 wrote:
> For anybody else having the problem I was of a huge error crashing
their system
> whenever the shutdown script tried to halt, it is because of the
power off command,
> like Axalon said, but the specific problem comes from the -p parameter
tha
Axalon wrote:
> On Wed, 30 Jun 1999, Flight16 wrote:
>
> > For anybody else having the problem I was of a huge error crashing their system
> > whenever the shutdown script tried to halt, it is because of the power off command,
> > like Axalon said, but the specific problem comes from the -p par
Flight16 wrote:
For anybody else having the problem I was of a huge
error crashing their system
whenever the shutdown script tried to halt, it is because of the power
off command,
like Axalon said, but the specific problem comes from the -p parameter
that tries to
power down your pc. This comm
Hmm...really? I didn't know you could edit a symlinkOTOH, I suppose you
can, now that I think about it... :-)
- Original Message -
From: Axalon <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 30, 1999 8:35 PM
Subject: Re: [newbie] shutdown problem
On Wed, 30 Jun 1999, John Aldrich wrote:
> BTW, on my machine (RedHat 6.0) it was not called SShalt, I believe it was
> calles S0halt. :-) I took a guess that it was the right script and opened it
> with joe. It was. :-)
those are all symlinks anyway the true filename is /etc/rc.d/init.d/halt
2000 1:55 PM
Subject: Re: [newbie] shutdown problem fixed
>
>
> On Wed, 30 Jun 1999, Flight16 wrote:
>
> > For anybody else having the problem I was of a huge error crashing their
system
> > whenever the shutdown script tried to halt, it is because of the power
off co
On Wed, 30 Jun 1999, Flight16 wrote:
> For anybody else having the problem I was of a huge error crashing their system
> whenever the shutdown script tried to halt, it is because of the power off command,
> like Axalon said, but the specific problem comes from the -p parameter that tries to
> p
For anybody else having the problem I was of a huge error crashing their system
whenever the shutdown script tried to halt, it is because of the power off command,
like Axalon said, but the specific problem comes from the -p parameter that tries to
power down your pc. This command is near the end
89 matches
Mail list logo
