[vox-tech] Re: {vox-tech] breakinguplongwordsinlatex

[Marc Elliot Hall]

On Wednesday 24 April 2002 01:59, you wrote:
> i'd love to scan it.   i don't suppose *i* could borrow it?   :)


Sure. Just ask Bill to bring it with him to the next LUGOD meeting. His cube 
is right around the corner from my office. 

>
> begin Marc Elliot Hall <[EMAIL PROTECTED]>
>
> > On Tue, Apr 23, 2002 at 05:10:13PM -0700, Peter Jay Salzman wrote:
> > 
> >
> > > btw, there's also a "latex web companion" which is on latex, web and
> > > html stuff.  never read it, so i don't know how good it is.
> >
> > Bill, I have this one on my bookshelf. It's the one we never used on this
> > project. Feel free to borrow it any time.
>
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] breakinguplongwordsinlatex

[Peter Jay Salzman]

i'd love to scan it.   i don't suppose *i* could borrow it?   :)

pete


begin Marc Elliot Hall <[EMAIL PROTECTED]> 
> On Tue, Apr 23, 2002 at 05:10:13PM -0700, Peter Jay Salzman wrote:
> 
> > btw, there's also a "latex web companion" which is on latex, web and
> > html stuff.  never read it, so i don't know how good it is.
> 
> Bill, I have this one on my bookshelf. It's the one we never used on this 
> project. Feel free to borrow it any time. 
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] breakinguplongwordsinlatex

[Marc Elliot Hall]

On Tue, Apr 23, 2002 at 05:10:13PM -0700, Peter Jay Salzman wrote:

> btw, there's also a "latex web companion" which is on latex, web and
> html stuff.  never read it, so i don't know how good it is.

Bill, I have this one on my bookshelf. It's the one we never used on this 
project. Feel free to borrow it any time. 
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] Apache error

[msimons]

On Tue, Apr 23, 2002 at 06:58:19PM -0700, ALLO (Alfredo Lopez) wrote:
> [Tue Apr 23 16:25:09 2002] [error] (13)Permission denied: exec of 
> /var/www/html/iprs_tmp/nobody_23-Apr-2002_7042/merged.htm failed
> [Tue Apr 23 16:25:09 2002] [error] [client 152.73.207.250] Premature end of 
> script headers: /var/www/html/iprs_tmp/nobody_23-Apr-2002_7042/merged.htm
> 
> iprs_tmp points to "/usr/local/iprscan/tmp" 
> I know that iprs_tmp directory is public and has permisions to execute CGI's
> and FollowSymLinks.  "tmp"  is also public.
> The "merged.htm" is actually a symlink to a subdir where the real merged.htm
> page resides.

Alfredo,

  make merged.htm a symlink to the actual file not the subdir and things
would be slightly better.
  You may be able to make nobody_23-Apr-2002_7042 a link to the real
directory where the files are...

> Everything in the servers works fine but this page that displays the "Final
> Result" of a search Arggg!! So close yet so far.
> 
> Does anybody know what is error 13 and where can I start looking in order to
> fix it.

  Apache is trying to execute a directory, for some reason apache is trying
to run things than end in "htm"... what do you have in your ScriptAlias
setting for apache... it sounds like the place where you have the .htm file
is inside one of them.
  Is the real .htm file something you want executed or not?


from Debian apache config files...
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the realname directory are treated as applications and
# run by the server when requested rather than as documents sent to the client.
# The same rules about trailing "/" apply to ScriptAlias directives as to
# Alias.
#
ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] Not able to log into root.

[Charles Polisher]

nbs wrote:
> Rusty Minden wrote:
> > Dohh! Yes I do I flubbed when doing a search using vim sorry. Still can't use 
> > su to log into root.
> 
> You'll probably need to boot into single user mode (err.. if you CAN
> with a botched /etc/passwd), or (more likely) use a rescue disk.
> 
> BTW - use "vipw", not "vim"...  It will, as the man page says,
> "set the appropriate locks to prevent file corruption."  I seem to
> recall it also complaining and not saving/quitting if the file got
> botched up.  (eg, it syntax checks it before committing to disk)
> 
> I could be wrong about that last part, unfortunately... :)
> In that case, I guess VIM is good enough.  Just be CAREFUL! ;)
> 
> -bill!

vipw ensures that multiple admins working on the same
machine won't get crosswise with the password file. 
I make it a habit to use vi -R foo whenever possible,
saves your bacon from making unwanted changes, and it's
a nicer environment than those pager things, for instance
vi/vim/gvim have got row & column indicators, search histories,
syntax hiliting, and bookmarks. If they're configured
correctly. The one time I was forced^W^Wused Slackware
it turned out vi was sym-linked to ...drumroll... pelvis !
With all the tasty bits left out.

-- 
With trembling hands he unfurled the ancient cracked parchment, this was
the place, it had to be. Uncertainly he began to mumble the chant "rdbms,
sql , third normal formal form, java,  table, scalable". Something moved..
>From outside they heard a scream and a thud. The sales department had awoken.
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

[vox-tech] Apache error

[ALLO (Alfredo Lopez)]

Hi, 

I am getting a weird error from Apache and I cannot figure out why I cannot
reach a certain page.
 When I try to access this page I get the following error instead of my
page.

Internal Server Error
The server encountered an internal error or misconfiguration and was unable
to complete your request.


This is the output from the Apache error.log

[Tue Apr 23 16:25:09 2002] [error] (13)Permission denied: exec of 
/var/www/html/iprs_tmp/nobody_23-Apr-2002_7042/merged.htm failed
[Tue Apr 23 16:25:09 2002] [error] [client 152.73.207.250] Premature end of 
script headers: /var/www/html/iprs_tmp/nobody_23-Apr-2002_7042/merged.htm

iprs_tmp points to "/usr/local/iprscan/tmp" 
I know that iprs_tmp directory is public and has permisions to execute CGI's
and FollowSymLinks.  "tmp"  is also public.
The "merged.htm" is actually a symlink to a subdir where the real merged.htm
page resides.

Everything in the servers works fine but this page that displays the "Final
Result" of a search Arggg!! So close yet so far.

Does anybody know what is error 13 and where can I start looking in order to
fix it.

As Always Thanks a Lot Guys.

Alfredo

___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] breakinguplongwordsinlatex

[Peter Jay Salzman]

begin Shawn P. Neugebauer <[EMAIL PROTECTED]> 
> On Tuesday 23 April 2002 05:28 pm, you wrote:
> > begin nbs <[EMAIL PROTECTED]>
> > > On Tue, Apr 23, 2002 at 05:10:13PM -0700, Peter Jay Salzman wrote:
> > > 
> > > > \linebreak[0]: if it's convenient, please consider line breaking here.
> > > > \linebreak[1]: please line break here.
> > > > \linebreak[2]: line break here.
> > > > \linebreak[3]: you better line break here or there's hell to pay
> > > > \linebreak[4]: hello latex, this is god speaking. thou shalt line
> > > > break.
> > >
> > > Hmm.. this doesn't do much for me.  I'm not in control of the data
> > > being sent.  (In this case, if the people making the data would need
> > > to go through the trouble of inserting a "\linebreak" command, they
> > > may as well just stick a space in there instead, since it will Do The
> > > Right Thing, anyway.  -  I'm thinking this is what I'm going to have to
> > > have them do.)
> >
> > ok, i think i understand a bit more.   can you make a parbox of a
> > certain width?   i think sticking everything in the parbox should give
> > you the desired result.
> 
> (fyi--would have been helpful to know up front that you didn't want
> to modify the data).
> 
> the parbox trick, which is usually so useful in controlling tables, does
> not work here.  it does not force a word to break, rather, it causes
> an overfull \hbox situation.  try it out.
 
wow -- cool, another latex user.  you must be a grad student or postdoc
in one of the sciences.  what department are you in?

you're absolutely right.  my bad!

i'd have to agree -- it can be done.  but it's way beyond the abilities
of any latex user i know.

suggestion:
1. use shawn's suggestion.  preprocess the data.
2. post to comp.text.tex.  the people there will know the answer.

pete
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] breakinguplongwordsinlatex

[Shawn P. Neugebauer]

On Tuesday 23 April 2002 05:28 pm, you wrote:
> begin nbs <[EMAIL PROTECTED]>
> > On Tue, Apr 23, 2002 at 05:10:13PM -0700, Peter Jay Salzman wrote:
> > 
> > > \linebreak[0]: if it's convenient, please consider line breaking here.
> > > \linebreak[1]: please line break here.
> > > \linebreak[2]: line break here.
> > > \linebreak[3]: you better line break here or there's hell to pay
> > > \linebreak[4]: hello latex, this is god speaking. thou shalt line
> > > break.
> >
> > Hmm.. this doesn't do much for me.  I'm not in control of the data
> > being sent.  (In this case, if the people making the data would need
> > to go through the trouble of inserting a "\linebreak" command, they
> > may as well just stick a space in there instead, since it will Do The
> > Right Thing, anyway.  -  I'm thinking this is what I'm going to have to
> > have them do.)
>
> ok, i think i understand a bit more.   can you make a parbox of a
> certain width?   i think sticking everything in the parbox should give
> you the desired result.

(fyi--would have been helpful to know up front that you didn't want
to modify the data).

the parbox trick, which is usually so useful in controlling tables, does
not work here.  it does not force a word to break, rather, it causes
an overfull \hbox situation.  try it out.

the problem is one of making a "word" break, without hyphenating it!
i think this is quite a challenge for latex.  i don't think you'll find an
"easy" way to do this.  you might try one of the verbatim-type
environments, or a typewriter-type environment, i'm not sure.

you might consider doing a little pre-processing of the data.  it
wouldn't be hard to write a little script in perl/shell/etc. to insert
spaces or otherwise format the data in a particular column.  it
sounds like you have a lot of data and you don't want to bug
your end-user.  a little utility code would be useful.

BOOKS:  i would add this one (i've mentioned it previously):
_Math_Into_Latex_ by Gratzer.  I consider essential for anyone
doing mathematically-oriented documents with latex.

shawn.
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] breakinguplongwordsinlatex

[Peter Jay Salzman]

begin nbs <[EMAIL PROTECTED]> 
> On Tue, Apr 23, 2002 at 05:10:13PM -0700, Peter Jay Salzman wrote:
> 
> > 
> > \linebreak[0]: if it's convenient, please consider line breaking here.
> > \linebreak[1]: please line break here.
> > \linebreak[2]: line break here.
> > \linebreak[3]: you better line break here or there's hell to pay
> > \linebreak[4]: hello latex, this is god speaking. thou shalt line break.
> 
> Hmm.. this doesn't do much for me.  I'm not in control of the data
> being sent.  (In this case, if the people making the data would need
> to go through the trouble of inserting a "\linebreak" command, they
> may as well just stick a space in there instead, since it will Do The Right
> Thing, anyway.  -  I'm thinking this is what I'm going to have to have
> them do.)
 
ok, i think i understand a bit more.   can you make a parbox of a
certain width?   i think sticking everything in the parbox should give
you the desired result.
 
> I'll dig a little more. Thanks for the suggestions WRT the books.
> I'll see if someone at work here can ok a purchase. :)
> (I've been borrowing someone's "A Guide To LaTeX" by
> Helmut Kopka & Patrieck Daly)

good book, but the lamport / latex companion combo is much better.
especially for the stuff you're doing.

btw, there's also a "latex web companion" which is on latex, web and
html stuff.  never read it, so i don't know how good it is.

pete

___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] breakinguplongwordsinlatex

[nbs]

On Tue, Apr 23, 2002 at 05:10:13PM -0700, Peter Jay Salzman wrote:

> 
> \linebreak[0]: if it's convenient, please consider line breaking here.
> \linebreak[1]: please line break here.
> \linebreak[2]: line break here.
> \linebreak[3]: you better line break here or there's hell to pay
> \linebreak[4]: hello latex, this is god speaking. thou shalt line break.

Hmm.. this doesn't do much for me.  I'm not in control of the data
being sent.  (In this case, if the people making the data would need
to go through the trouble of inserting a "\linebreak" command, they
may as well just stick a space in there instead, since it will Do The Right
Thing, anyway.  -  I'm thinking this is what I'm going to have to have
them do.)


I'll dig a little more. Thanks for the suggestions WRT the books.
I'll see if someone at work here can ok a purchase. :)
(I've been borrowing someone's "A Guide To LaTeX" by
Helmut Kopka & Patrieck Daly)

-bill!
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] CMOS problems, dead battery?

[ME]

On Tue, 23 Apr 2002, Ryan wrote:
> On Tuesday 23 April 2002 04:30 pm, ME wrote:
> > Someone set a jumper on the mb imporperly
> 
> Perhaps, but most motherboards refuse to boot if the CMOS clear jumper is 
> set, and that's about the only jumper on the board (everything else is in the 
> bios)

It is rare, but possible. I dont remember the last time this was an issue
(over 8 years though.)

> > After successive heating and cooling "chip rising" (not so much a problem
> >  on modern machines - mostly with older DIP chip based boards with bios in
> >  sockets instead of integrated.)
> 
> I dislike intergarted BIOS, makes things much more expensive if you botch a 
> flash. (this happened with my laptop, costing me $150 for a new motherboard 
> instead of $15 for an new BIOS chip)
> 
> The one on the affected system IS socketed, and is fairly new. I thought most 
> desktops were like that.

Certainly. My mistake. Even though modern machines are built with sockets
for BIOS chips, it seems those built now do not suffer from "chip
rising" so much as the previous ones made 2+ decades ago.

Having socket based BIOS is a good thing when they are EEPROM based and
you can flash oiver to a new version, but bad when they are EPROM based or
just plain ROM as you have to get them via mail-order.

I agree with you on the risks of having the firware/FlashROM
integrated. 

> How long should a battery last?

It *should* last forever, but rules on energy, perpetual motion machines,
rules of thermodynamics seem to stick their tongues out at me for wishing
for it.

Common lifetimes for batteries on systems is quite variable and can
depend, on some systems, on how much time it is spent witout any AC
power. (Some seem to use AC power when available - even when the system is
powered off, but when unplugged use only the battery.)

To the answer... from 3 to 8 years seems common. (I have seen more and
less, but this range covers most machines.) 5 Years is a safe bet for most
machines before replacement is needed. Less than 5 years, you may want to
check to see if there is a short in you mb somewhere that could drain the
clock. (High resistance short for slower drain for example.)

Hook up a voltmeter/ammeter to the battery and see how "alive" it is. That
is one way to test the battery and try to rule it "out" or "in".

-ME

-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCS/CM$/IT$/LS$/S/O$ !d--(++) !s !a+++(-) C++$() U$(+$) P+$>+++ 
L+++$(++) E W+++$(+) N+ o K w+$>++>+++ O-@ M+$ V-$>- !PS !PE Y+ !PGP
t@-(++) 5+@ X@ R- tv- b++ DI+++ D+ G--@ e+>++> h(++)>+ r*>? z?
--END GEEK CODE BLOCK--
decode: http://www.ebb.org/ungeek/ about: http://www.geekcode.com/geek.html

___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] CMOS problems, dead battery?

[Jeff Newmiller]

On Tue, 23 Apr 2002, Ryan wrote:

> Anything other then a dead battery that'll cause a CMOS checksum error after 
> the computers been off AC for a little while?

Stirring up the innards can dislodge the battery connection.

Shutting down the computer while it is writing to the CMOS.

http://www.computerhope.com/battery.htm
http://www.resource800.com/ibmfaq.html

---
Jeff NewmillerThe .   .  Go Live...
DCN:<[EMAIL PROTECTED]>Basics: ##.#.   ##.#.  Live Go...
  Live:   OO#.. Dead: OO#..  Playing
Research Engineer (Solar/BatteriesO.O#.   #.O#.  with
/Software/Embedded Controllers)   .OO#.   .OO#.  rocks...2k
---

___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] breakinguplongwordsinlatex

[Peter Jay Salzman]

hi bill,

there's a way to make \linebreak into a suggestion, rather than a
command.   off the top of my head, i can't remember how, but leslie
lamport's book should go into that in depth.

pete


ps- there are only two necessary books on latex.  the first is leslie
lamport's book.  is a _must_ for anyone who spends even a small amount of
time with latex:

http://www.nerdbooks.com/item.html?id=0201529831&phpSID=5543e20c30290fdcb16d7d47668ccb02

then there's the "latex companion".  it is a companion to leslie
lamport's book.  where leslie's book is small and light reading,
goossens' book is long and meant to be a reference rather than read.
it's a must for anyone who wants to do intermediate to advanced stuff
with latex.

http://www.nerdbooks.com/item.html?id=0201541998&phpSID=5543e20c30290fdcb16d7d47668ccb02



pps- got off my @ss and looked it up.  page 95 of leslie lamport:

\linebreak[0]: if it's convenient, please consider line breaking here.
\linebreak[1]: please line break here.
\linebreak[2]: line break here.
\linebreak[3]: you better line break here or there's hell to pay
\linebreak[4]: hello latex, this is god speaking. thou shalt line break.



begin nbs <[EMAIL PROTECTED]> 
> Is there a way to force a string to break at a certain length,
> regardless as to whether it contains spaces?
> 
> In other words, some data being printed into columns of a table
> word wrap ok, because it's multiple words:
> 
>This is a really long spaced
>entry for the column
> 
> 
> Others mess up the table (a longtable with specifically assigned widths):
> 
>   Thisisareallylongspacelessentryforthecolumn
> 
> 
> Any way to just force that 2nd kind of text to break at the column's
> width?
> 
> 
> (The data really should be changed, but that's not up to me,
> unfortunately. <:^(  )
> 
> 
> -bill!
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] CMOS problems, dead battery?

[Ryan]

I'm going to see if changing the battery helps when I get around to it.

I was wondering if there was anuything else that could be causing a problem, 
as the battery is less then a year old.

On Tuesday 23 April 2002 04:30 pm, ME wrote:
> Static discharge/short in mb (temporary or on-going)
>
> BIOS/CMOS EEPROM receives bad signal.
>
> Uncommon, but possible on some systems: nvram/BIOS access from OS altered
>  things. There are viruses that can target data stored in nvram and make
> some machines unbootable, but that are rather uncommon.
>
> Non-power supply related:
> Someone set a jumper on the mb imporperly

Perhaps, but most motherboards refuse to boot if the CMOS clear jumper is 
set, and that's about the only jumper on the board (everything else is in the 
bios)

> After successive heating and cooling "chip rising" (not so much a problem
>  on modern machines - mostly with older DIP chip based boards with bios in
>  sockets instead of integrated.)

I dislike intergarted BIOS, makes things much more expensive if you botch a 
flash. (this happened with my laptop, costing me $150 for a new motherboard 
instead of $15 for an new BIOS chip)

The one on the affected system IS socketed, and is fairly new. I thought most 
desktops were like that.

> Bad contact / intermittant contact with chips used for BIOS
> Dead battery or battery getting close to being dead (mentioned by you
>  earlier, but still most common.)

How long should a battery last?

> Failure in chip holding BIOS data


> Introduction of UV Radiation or open photoport for EPROM and light cause
>  damage/erase (Is any vendor using EPROM for BIOS anymore?)
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

[vox-tech] breakinguplongwordsinlatex

[nbs]

Is there a way to force a string to break at a certain length,
regardless as to whether it contains spaces?

In other words, some data being printed into columns of a table
word wrap ok, because it's multiple words:

   This is a really long spaced
   entry for the column


Others mess up the table (a longtable with specifically assigned widths):

  Thisisareallylongspacelessentryforthecolumn


Any way to just force that 2nd kind of text to break at the column's
width?


(The data really should be changed, but that's not up to me,
unfortunately. <:^(  )


-bill!
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] CMOS problems, dead battery?

[ME]

Static discharge/short in mb (temporary or on-going)

BIOS/CMOS EEPROM receives bad signal.

Uncommon, but possible on some systems: nvram/BIOS access from OS altered
 things. There are viruses that can target data stored in nvram and make
some machines unbootable, but that are rather uncommon.

Non-power supply related:
Someone set a jumper on the mb imporperly.
After successive heating and cooling "chip rising" (not so much a problem
 on modern machines - mostly with older DIP chip based boards with bios in
 sockets instead of integrated.)
Bad contact / intermittant contact with chips used for BIOS
Dead battery or battery getting close to being dead (mentioned by you
 earlier, but still most common.)
Failure in chip holding BIOS data
Introduction of UV Radiation or open photoport for EPROM and light cause
 damage/erase (Is any vendor using EPROM for BIOS anymore?)

These were off top of my head.

I'm sure there are others. Any EE majors/graduates out there?

-ME

-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCS/CM$/IT$/LS$/S/O$ !d--(++) !s !a+++(-) C++$() U$(+$) P+$>+++ 
L+++$(++) E W+++$(+) N+ o K w+$>++>+++ O-@ M+$ V-$>- !PS !PE Y+ !PGP
t@-(++) 5+@ X@ R- tv- b++ DI+++ D+ G--@ e+>++> h(++)>+ r*>? z?
--END GEEK CODE BLOCK--
decode: http://www.ebb.org/ungeek/ about: http://www.geekcode.com/geek.html
 Systems Department Operating Systems Analyst for the SSU Library

On Tue, 23 Apr 2002, Ryan wrote:
> Anything other then a dead battery that'll cause a CMOS checksum error
> after the computers been off AC for a little while?

___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

[vox-tech] CMOS problems, dead battery?

[Ryan]

Anything other then a dead battery that'll cause a CMOS checksum error after 
the computers been off AC for a little while?
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] Not able to log into root.

[Peter Jay Salzman]

hi shawn,

i had the same thought myself, but didn't post it.  now that you bring
it up...

rusty, something happened between the last time you were able to su and
the time at which su stopped working.

rusty, is this a woody system?  if so, su belongs to the package
"login".  the current version of login is 2902-12 (you can get this
by 'dpkg -p login').   if your OS and package version number match this,
check your md5sum.  here's mine:

5d324ad212b2ff8f767637ac1a8071ec  /bin/su

pete



begin Shawn P. Neugebauer <[EMAIL PROTECTED]> 
> sounds good peter, but why would it change??  i'd be worried...
> 
> i tried a little experiment (don't try this at home boys and girls).  as a 
> backup, i opened a root shell.  then, in another shell, i changed the
> permissions on /bin/su to 755.  when i try to su to root, i just get
> "incorrect password" (this is RH 7.x).  i tried several combinations of
> permissions (4755, 6755, 755), owner, and group, and all either work or
> return "incorrect password."  
> 
> so, changing the permissions may indeed correct the problem, but i'd
> wonder how it got that way.  do you have any way to know that the
> machine has not been rooted??
> 
> shawn.
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] Not able to log into root.

[ME]

Perhaps a suid-checking script was poorly configured and chmodded the suid
bit out?

Did you install any security software recently?


Coming into the picture recently (SOrry, did not read all of the other
posts yet) some questions:
Does a "normal" login from the console as root work?
Is the only fault in when you su?

The original message makes it sound like you cannot login or su. If that 
is the case, then there are other things to check beyond just su.

-ME

-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCS/CM$/IT$/LS$/S/O$ !d--(++) !s !a+++(-) C++$() U$(+$) P+$>+++ 
L+++$(++) E W+++$(+) N+ o K w+$>++>+++ O-@ M+$ V-$>- !PS !PE Y+ !PGP
t@-(++) 5+@ X@ R- tv- b++ DI+++ D+ G--@ e+>++> h(++)>+ r*>? z?
--END GEEK CODE BLOCK--
decode: http://www.ebb.org/ungeek/ about: http://www.geekcode.com/geek.html

On Tue, 23 Apr 2002, Shawn P. Neugebauer wrote:
> sounds good peter, but why would it change??  i'd be worried...
> 
> i tried a little experiment (don't try this at home boys and girls).  as a 
> backup, i opened a root shell.  then, in another shell, i changed the
> permissions on /bin/su to 755.  when i try to su to root, i just get
> "incorrect password" (this is RH 7.x).  i tried several combinations of
> permissions (4755, 6755, 755), owner, and group, and all either work or
> return "incorrect password."  
> 
> so, changing the permissions may indeed correct the problem, but i'd
> wonder how it got that way.  do you have any way to know that the
> machine has not been rooted??
> 
> shawn.
> 
> On Tuesday 23 April 2002 12:01 pm, you wrote:
> > hi rusty,
> >
> > off the top of my head, i would say that your su needs to be setuid
> > root and it's not.  you should have a permission of 4755 (rwsr-xr-x) on
> > su.
> >
> > to verify this, i went to google groups:
> >
> > http://groups.google.com/advanced_group_search
> >
> > in "with all of the words" i typed:
> >
> > su "cannot set groups"
> >
> > the first item reads:
> >
> > su problem: su: cannot set groups: Operation not permitted
> >
> > i click on it, then click on complete thread.  here's the URL:
> >
> > http://groups.google.com/groups?hl=en&th=4dec5a92aba3e0&rnum=1
> >
> > it looks like all the responses to this question point to the permission
> > problem.   :-)
> >
> > hth,
> > pete
> >
> >
> > begin Rusty Minden <[EMAIL PROTECTED]>
> >
> > > I am not able too loginto root and when I try to su into root I get this
> > > error below any ideas?
> > >
> > > rdm@cc668999-a:~> su
> > > Password:
> > > su: cannot set groups: Operation not permitted

___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] Not able to log into root.

[Shawn P. Neugebauer]

sounds good peter, but why would it change??  i'd be worried...

i tried a little experiment (don't try this at home boys and girls).  as a 
backup, i opened a root shell.  then, in another shell, i changed the
permissions on /bin/su to 755.  when i try to su to root, i just get
"incorrect password" (this is RH 7.x).  i tried several combinations of
permissions (4755, 6755, 755), owner, and group, and all either work or
return "incorrect password."  

so, changing the permissions may indeed correct the problem, but i'd
wonder how it got that way.  do you have any way to know that the
machine has not been rooted??

shawn.

On Tuesday 23 April 2002 12:01 pm, you wrote:
> hi rusty,
>
> off the top of my head, i would say that your su needs to be setuid
> root and it's not.  you should have a permission of 4755 (rwsr-xr-x) on
> su.
>
> to verify this, i went to google groups:
>
>   http://groups.google.com/advanced_group_search
>
> in "with all of the words" i typed:
>
>   su "cannot set groups"
>
> the first item reads:
>
>   su problem: su: cannot set groups: Operation not permitted
>
> i click on it, then click on complete thread.  here's the URL:
>
>   http://groups.google.com/groups?hl=en&th=4dec5a92aba3e0&rnum=1
>
> it looks like all the responses to this question point to the permission
> problem.   :-)
>
> hth,
> pete
>
>
> begin Rusty Minden <[EMAIL PROTECTED]>
>
> > I am not able too loginto root and when I try to su into root I get this
> > error below any ideas?
> >
> > rdm@cc668999-a:~> su
> > Password:
> > su: cannot set groups: Operation not permitted
> >
> > Rusty Minden
> > ___
> > vox-tech mailing list
> > [EMAIL PROTECTED]
> > http://lists.lugod.org/mailman/listinfo/vox-tech
>
> ___
> vox-tech mailing list
> [EMAIL PROTECTED]
> http://lists.lugod.org/mailman/listinfo/vox-tech
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] Debian WOODY ISO

[Peter Jay Salzman]

begin [EMAIL PROTECTED] <[EMAIL PROTECTED]> 
>   .hu is Hungry, there really must be a better place to pull 2+ Gigs
> of files from.
> 
>   Possibly a better place to get the woody cds is "apt-get install debian-cd"
> followed by a bunch of reading I haven't done yet.
 
i guess "jigdo" is the new way of doing this.  i'm using it right now.
we'll see if i can actually generate a good iso from it...

>   For what it's worth the demo machine is coming along nicely,
> (a full report of the system will be following) if someone can bring
> a IDE CD-R/RW drive and blanks to the demo this weekend I may be
> able to burn ISO's while we talk.  (If someone wants to donate
> a CD-R/RW or similar drive that would be even better :).
 
isn't there a scsi card in the system?

maybe lugod should invest in a plextor cdrw for the machine?  we do have the
funds for it; lugod has been pretty thrifty...

pete
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] Debian WOODY ISO

[msimons]

  .hu is Hungry, there really must be a better place to pull 2+ Gigs
of files from.

  Possibly a better place to get the woody cds is "apt-get install debian-cd"
followed by a bunch of reading I haven't done yet.

  For what it's worth the demo machine is coming along nicely,
(a full report of the system will be following) if someone can bring
a IDE CD-R/RW drive and blanks to the demo this weekend I may be
able to burn ISO's while we talk.  (If someone wants to donate
a CD-R/RW or similar drive that would be even better :).

Later,
  Mike

  (A complete debian/woody/i386 mirror is on it's way to the demo machine
right now (the main benefit is if I forgot something we can install it
without anytime without a network connection), but there are other
perks like at the installfest this machine can act as a network install
server, and general purpose archive of semi-current stuff).

On Mon, Apr 22, 2002 at 11:06:50PM -0700, Rusty Minden wrote:
> Yes it is slow, but they are good ISO images I have not had a bad one from
> them yet.
>
> On Monday 22 April 2002 12:19 pm, you wrote:
> > question -- does it come with the woody installer or is it just a big
> > collection of packages?
> >
> > also, i've seen this link before -- if memory serves, it's kind of a
> > slow link.  if someone has a fast connection, it might be nice if
> > someone can mirror it.
> >
> > begin Rusty Minden <[EMAIL PROTECTED]>
> > > This is a good place to get Debian Woody on an ISO
> > >
> > > ftp://ftp.fsn.hu/pub/CDROM-Images/debian-unofficial/woody/
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] Not able to log into root.

[Peter Jay Salzman]

begin nbs <[EMAIL PROTECTED]> 
> On Tue, Apr 23, 2002 at 02:11:33PM -0700, Peter Jay Salzman wrote:
> > why did you post /etc/passwd?
> > 
> > it would be more helpful if you posted the contents of /etc/shadow.
> 
> Why, so we can all try to crack it for a few weeks?  ;) 
> 
> -bill!


nope, i wouldn't want /other/ people to waste CPU cycles on something like that.

just me.

pete "ok, the truth just came out"
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] Not able to log into root.

[nbs]

On Tue, Apr 23, 2002 at 02:11:33PM -0700, Peter Jay Salzman wrote:
> why did you post /etc/passwd?
> 
> it would be more helpful if you posted the contents of /etc/shadow.

Why, so we can all try to crack it for a few weeks?  ;) 

-bill!
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] Not able to log into root.

[Peter Jay Salzman]

why did you post /etc/passwd?

it would be more helpful if you posted the contents of /etc/shadow.


pete "just tryin' to be helpful"



begin Rusty Minden <[EMAIL PROTECTED]> 
> I will from now on use less and more.
> 
> This is /etc/passwd
> root:x:0:0:root:/root:/bin/bash
> bin:x:1:1:bin:/bin:/bin/bash
> daemon:x:2:2:Daemon:/sbin:/bin/bash
> lp:x:4:7:Printing daemon:/var/spool/lpd:/bin/bash
> games:x:12:100:Games account:/var/games:/bin/bash
> at:x:25:25:Batch jobs daemon:/var/spool/atjobs:/bin/bash
> postgres:x:26:2:Postgres database admin:/var/lib/pgsql:/bin/bash
> mdom:x:28:28:Mailing list agent:/usr/lib/majordomo:/bin/bash
> wwwrun:x:30:65534:WWW daemon apache:/var/lib/wwwrun:/bin/bash
> squid:x:31:65534:WWW proxy squid:/var/squid:/bin/bash
> fax:x:33:14:Facsimile agent:/var/spool/fax:/bin/bash
> gnats:x:34:65534:Gnats GNU backtracking system:/usr/lib/gnats:/bin/bash
> adabas:x:36:100:Adabas-D database admin:/usr/lib/adabas:/bin/bash
> amanda:x:37:6:Amanda admin:/var/lib/amanda:/bin/bash
> irc:x:39:65534:IRC daemon:/usr/lib/ircd:/bin/bash
> ftp:x:40:2:FTP account:/usr/local/ftp:/bin/bash
> firewall:x:41:31:Firewall account:/var/lib/firewall:/bin/false
> named:x:44:44:Nameserver daemon:/var/named:/bin/bash
> fnet:x:49:14:FidoNet account:/var/spool/fnet:/bin/bash
> gdm:x:50:15:Gnome Display Manager daemon:/var/lib/gdm:/bin/bash
> postfix:x:51:51:Postfix daemon:/var/spool/postfix:/bin/false
> cyrus:x:96:12:IMAP daemon:/usr/cyrus:/bin/bash
> dpbox:x:61:56:DpBox account:/var/spool/dpbox:/bin/false
> ingres:x:62:3:Ingres database admin:/opt/tngfw/ingres:/bin/bash
> vscan:x:65:65534:Vscan account:/var/spool/vscan:/bin/false
> wnn:x:66:100:Wnn system account:/var/lib/wnn:/bin/false
> pop:x:67:100:POP admin:/var/lib/pop:/bin/false
> perforce:x:68:60:Perfoce admin:/var/lib/perforce:/bin/false
> sapdb:x:69:61:SAPDB demo account:/var/opt/sapdb:/bin/bash
> db4web:x:70:100:DB4Web account:/opt/db4web:/bin/bash
> nobody:x:65534:65534:nobody:/var/lib/nobody:/bin/bash
> rdm:x:500:100:Roland (Rusty) Minden:/home/rdm:/bin/bash
> man:x:13:62:Manual pages viewer:/var/cache/man:/bin/bash
> news:x:9:13:News system:/etc/news:/bin/bash
> uucp:x:10:14:Unix-to-Unix CoPy system:/etc/uucp:/bin/bash
> 
> On Tuesday 23 April 2002 12:07 pm, you wrote:
> > as mike pointed out to me in email, it's just better to use a pager like
> > less.  it's a good habit to get into.
> >
> >
> > begin nbs <[EMAIL PROTECTED]>
> >
> > > On Tue, Apr 23, 2002 at 11:58:33AM -0700, Rusty Minden wrote:
> > > > Dohh! Yes I do I flubbed when doing a search using vim sorry. Still
> > > > can't use su to log into root.
> > >
> > > You'll probably need to boot into single user mode (err.. if you CAN
> >
> > not quite -- you still need to enter a password in single user mode.
> >
> > > with a botched /etc/passwd), or (more likely) use a rescue disk.
> >
> > you need to boot a rescue disk (the linux BBC or linuxcare cd's are
> > perfect for this sort of thing.  debian rescue disks will work too).
> >
> > then you need to manually mount the root partition read/write.
> >
> > then you need to change the permission on /mnt/bin/su (not on /bin/su,
> > if that makes sense).
> >
> > it's just like when you forget the root password, except you'll be using
> > chmod to change permissions instead of vim to change text between the
> > 2nd and 3rd ":" in /etc/shadow.
> >
> > pete
> >
> > > BTW - use "vipw", not "vim"...  It will, as the man page says,
> > > "set the appropriate locks to prevent file corruption."  I seem to
> > > recall it also complaining and not saving/quitting if the file got
> > > botched up.  (eg, it syntax checks it before committing to disk)
> > >
> > > I could be wrong about that last part, unfortunately... :)
> > > In that case, I guess VIM is good enough.  Just be CAREFUL! ;)
> > >
> > > -bill!
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] Not able to log into root.

[Rusty Minden]

I will from now on use less and more.

This is /etc/passwd
root:x:0:0:root:/root:/bin/bash
bin:x:1:1:bin:/bin:/bin/bash
daemon:x:2:2:Daemon:/sbin:/bin/bash
lp:x:4:7:Printing daemon:/var/spool/lpd:/bin/bash
games:x:12:100:Games account:/var/games:/bin/bash
at:x:25:25:Batch jobs daemon:/var/spool/atjobs:/bin/bash
postgres:x:26:2:Postgres database admin:/var/lib/pgsql:/bin/bash
mdom:x:28:28:Mailing list agent:/usr/lib/majordomo:/bin/bash
wwwrun:x:30:65534:WWW daemon apache:/var/lib/wwwrun:/bin/bash
squid:x:31:65534:WWW proxy squid:/var/squid:/bin/bash
fax:x:33:14:Facsimile agent:/var/spool/fax:/bin/bash
gnats:x:34:65534:Gnats GNU backtracking system:/usr/lib/gnats:/bin/bash
adabas:x:36:100:Adabas-D database admin:/usr/lib/adabas:/bin/bash
amanda:x:37:6:Amanda admin:/var/lib/amanda:/bin/bash
irc:x:39:65534:IRC daemon:/usr/lib/ircd:/bin/bash
ftp:x:40:2:FTP account:/usr/local/ftp:/bin/bash
firewall:x:41:31:Firewall account:/var/lib/firewall:/bin/false
named:x:44:44:Nameserver daemon:/var/named:/bin/bash
fnet:x:49:14:FidoNet account:/var/spool/fnet:/bin/bash
gdm:x:50:15:Gnome Display Manager daemon:/var/lib/gdm:/bin/bash
postfix:x:51:51:Postfix daemon:/var/spool/postfix:/bin/false
cyrus:x:96:12:IMAP daemon:/usr/cyrus:/bin/bash
dpbox:x:61:56:DpBox account:/var/spool/dpbox:/bin/false
ingres:x:62:3:Ingres database admin:/opt/tngfw/ingres:/bin/bash
vscan:x:65:65534:Vscan account:/var/spool/vscan:/bin/false
wnn:x:66:100:Wnn system account:/var/lib/wnn:/bin/false
pop:x:67:100:POP admin:/var/lib/pop:/bin/false
perforce:x:68:60:Perfoce admin:/var/lib/perforce:/bin/false
sapdb:x:69:61:SAPDB demo account:/var/opt/sapdb:/bin/bash
db4web:x:70:100:DB4Web account:/opt/db4web:/bin/bash
nobody:x:65534:65534:nobody:/var/lib/nobody:/bin/bash
rdm:x:500:100:Roland (Rusty) Minden:/home/rdm:/bin/bash
man:x:13:62:Manual pages viewer:/var/cache/man:/bin/bash
news:x:9:13:News system:/etc/news:/bin/bash
uucp:x:10:14:Unix-to-Unix CoPy system:/etc/uucp:/bin/bash

On Tuesday 23 April 2002 12:07 pm, you wrote:
> as mike pointed out to me in email, it's just better to use a pager like
> less.  it's a good habit to get into.
>
>
> begin nbs <[EMAIL PROTECTED]>
>
> > On Tue, Apr 23, 2002 at 11:58:33AM -0700, Rusty Minden wrote:
> > > Dohh! Yes I do I flubbed when doing a search using vim sorry. Still
> > > can't use su to log into root.
> >
> > You'll probably need to boot into single user mode (err.. if you CAN
>
> not quite -- you still need to enter a password in single user mode.
>
> > with a botched /etc/passwd), or (more likely) use a rescue disk.
>
> you need to boot a rescue disk (the linux BBC or linuxcare cd's are
> perfect for this sort of thing.  debian rescue disks will work too).
>
> then you need to manually mount the root partition read/write.
>
> then you need to change the permission on /mnt/bin/su (not on /bin/su,
> if that makes sense).
>
> it's just like when you forget the root password, except you'll be using
> chmod to change permissions instead of vim to change text between the
> 2nd and 3rd ":" in /etc/shadow.
>
> pete
>
> > BTW - use "vipw", not "vim"...  It will, as the man page says,
> > "set the appropriate locks to prevent file corruption."  I seem to
> > recall it also complaining and not saving/quitting if the file got
> > botched up.  (eg, it syntax checks it before committing to disk)
> >
> > I could be wrong about that last part, unfortunately... :)
> > In that case, I guess VIM is good enough.  Just be CAREFUL! ;)
> >
> > -bill!
>
> ___
> vox-tech mailing list
> [EMAIL PROTECTED]
> http://lists.lugod.org/mailman/listinfo/vox-tech
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] IDE interface question

[Peter Jay Salzman]

fwiw, i do the same thing as rusty; i have ata133 drives on a ata100
interface.

pete


begin Rusty Minden <[EMAIL PROTECTED]> 
> In short yes, but it will only work at the speed supported IE an ATA100 drive 
> will work at ATA33-66-and 100. I buy ATA133 drives and use them on my ATA100 
> interface all the time.
> Rusty
> 
> On Tuesday 23 April 2002 11:47 am, you wrote:
> > I know next to nothing about IDE hardware. Is it possible to install a new
> > (ATA-100) IDE hard drive into an old system (say a first-generation
> > Pentium) whose controllers support only basic IDE?
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] Not able to log into root.

[Peter Jay Salzman]

as mike pointed out to me in email, it's just better to use a pager like
less.  it's a good habit to get into.


begin nbs <[EMAIL PROTECTED]> 
> On Tue, Apr 23, 2002 at 11:58:33AM -0700, Rusty Minden wrote:
> > Dohh! Yes I do I flubbed when doing a search using vim sorry. Still can't use 
> > su to log into root.
> 
> You'll probably need to boot into single user mode (err.. if you CAN

not quite -- you still need to enter a password in single user mode.

> with a botched /etc/passwd), or (more likely) use a rescue disk.
 
you need to boot a rescue disk (the linux BBC or linuxcare cd's are
perfect for this sort of thing.  debian rescue disks will work too).

then you need to manually mount the root partition read/write.

then you need to change the permission on /mnt/bin/su (not on /bin/su,
if that makes sense).

it's just like when you forget the root password, except you'll be using
chmod to change permissions instead of vim to change text between the
2nd and 3rd ":" in /etc/shadow.

pete

> BTW - use "vipw", not "vim"...  It will, as the man page says,
> "set the appropriate locks to prevent file corruption."  I seem to
> recall it also complaining and not saving/quitting if the file got
> botched up.  (eg, it syntax checks it before committing to disk)
> 
> I could be wrong about that last part, unfortunately... :)
> In that case, I guess VIM is good enough.  Just be CAREFUL! ;)
> 
> -bill!
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] Not able to log into root.

[nbs]

On Tue, Apr 23, 2002 at 11:58:33AM -0700, Rusty Minden wrote:
> Dohh! Yes I do I flubbed when doing a search using vim sorry. Still can't use 
> su to log into root.

You'll probably need to boot into single user mode (err.. if you CAN
with a botched /etc/passwd), or (more likely) use a rescue disk.

BTW - use "vipw", not "vim"...  It will, as the man page says,
"set the appropriate locks to prevent file corruption."  I seem to
recall it also complaining and not saving/quitting if the file got
botched up.  (eg, it syntax checks it before committing to disk)

I could be wrong about that last part, unfortunately... :)
In that case, I guess VIM is good enough.  Just be CAREFUL! ;)

-bill!
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] Not able to log into root.

[Peter Jay Salzman]

hi rusty,

off the top of my head, i would say that your su needs to be setuid
root and it's not.  you should have a permission of 4755 (rwsr-xr-x) on
su.

to verify this, i went to google groups:

http://groups.google.com/advanced_group_search

in "with all of the words" i typed:

su "cannot set groups"

the first item reads:

su problem: su: cannot set groups: Operation not permitted

i click on it, then click on complete thread.  here's the URL:

http://groups.google.com/groups?hl=en&th=4dec5a92aba3e0&rnum=1

it looks like all the responses to this question point to the permission
problem.   :-)

hth,
pete


begin Rusty Minden <[EMAIL PROTECTED]> 
> I am not able too loginto root and when I try to su into root I get this 
> error below any ideas?
> 
> rdm@cc668999-a:~> su
> Password: 
> su: cannot set groups: Operation not permitted
> 
> Rusty Minden
> ___
> vox-tech mailing list
> [EMAIL PROTECTED]
> http://lists.lugod.org/mailman/listinfo/vox-tech
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] Not able to log into root.

[Rusty Minden]

Dohh! Yes I do I flubbed when doing a search using vim sorry. Still can't use 
su to log into root.
Rusty

On Tuesday 23 April 2002 11:55 am, you wrote:
> Sorry to reply to my own thread, but in /etc/passwd I do not have root. I
> didn't remove it though.
> Rusty Minden
>
> On Tuesday 23 April 2002 11:52 am, you wrote:
> > I am not able too loginto root and when I try to su into root I get this
> > error below any ideas?
> >
> > rdm@cc668999-a:~> su
> > Password:
> > su: cannot set groups: Operation not permitted
> >
> > Rusty Minden
> > ___
> > vox-tech mailing list
> > [EMAIL PROTECTED]
> > http://lists.lugod.org/mailman/listinfo/vox-tech
>
> ___
> vox-tech mailing list
> [EMAIL PROTECTED]
> http://lists.lugod.org/mailman/listinfo/vox-tech
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] RH keeps crashing

[Henry House]

On Mon, Apr 22, 2002 at 02:52:03PM -0700, Peter Jay Salzman wrote:
> begin Richard S. Crawford <[EMAIL PROTECTED]> 
> > 
> > Thanks for the tip.  I'll remember that.  As it is, I'm unable to ping, 
> > browse to, ssh to, tel-net to, telepathically link to, or otherwise 
> > communicate with the machine.  I'll try smoke signals next.
> 
> this is a good indication that the kernel is truly dead.  smoked.  it's
> almost 100% certain to be a hardware problem of some sort.
> 
> the most important question now is -- what recently changed?  did you
> install any new packages?  any new hardware?  change bios?

Mike Simons recently alerted me to the possibility of APM (advanced power
mangement? I believe) causing havok when the machine is idle if (1) kernel
APM support is on and (2) the APM support in the BIOS is not properly
supported by your version of Linux. I have subsequently found that APM
support only works properly on very new desktops (a wider range of notebooks
work, though). You might check whether your machine is using APM by scanning
the output of dmesg for 'apm'.

-- 
Henry House
The attached file is a digital signature. See 
for information.  My OpenPGP key: .



msg02278/pgp0.pgp
Description: PGP signature

Re: [vox-tech] Not able to log into root.

[Rusty Minden]

Sorry to reply to my own thread, but in /etc/passwd I do not have root. I 
didn't remove it though.
Rusty Minden

On Tuesday 23 April 2002 11:52 am, you wrote:
> I am not able too loginto root and when I try to su into root I get this
> error below any ideas?
>
> rdm@cc668999-a:~> su
> Password:
> su: cannot set groups: Operation not permitted
>
> Rusty Minden
> ___
> vox-tech mailing list
> [EMAIL PROTECTED]
> http://lists.lugod.org/mailman/listinfo/vox-tech
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

[vox-tech] Not able to log into root.

[Rusty Minden]

I am not able too loginto root and when I try to su into root I get this 
error below any ideas?

rdm@cc668999-a:~> su
Password: 
su: cannot set groups: Operation not permitted

Rusty Minden
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] IDE interface question

[Rod Roark]

On Tuesday 23 April 2002 11:47, Henry House wrote:
> I know next to nothing about IDE hardware. Is it possible to install
> a new (ATA-100) IDE hard drive into an old system (say a
> first-generation Pentium) whose controllers support only basic IDE?

I think this is usually true, but you need to check the specs
for the drive, or ask the manufacturer.

-- Rod
   http://www.sunsetsystems.com/

___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

Re: [vox-tech] IDE interface question

[Rusty Minden]

In short yes, but it will only work at the speed supported IE an ATA100 drive 
will work at ATA33-66-and 100. I buy ATA133 drives and use them on my ATA100 
interface all the time.
Rusty

On Tuesday 23 April 2002 11:47 am, you wrote:
> I know next to nothing about IDE hardware. Is it possible to install a new
> (ATA-100) IDE hard drive into an old system (say a first-generation
> Pentium) whose controllers support only basic IDE?
___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech

[vox-tech] IDE interface question

[Henry House]

I know next to nothing about IDE hardware. Is it possible to install a new
(ATA-100) IDE hard drive into an old system (say a first-generation Pentium)
whose controllers support only basic IDE?

-- 
Henry House
The attached file is a digital signature. See 
for information.  My OpenPGP key: .



msg02273/pgp0.pgp
Description: PGP signature

Re: [vox-tech] My Wayward RH Box

[ME]

On Tue, 23 Apr 2002, Richard S. Crawford wrote:
[chop]
> I deactivated the screen saver, and simply left it on "blank screen". 
> That appears to have helped.
[chop]

That was a known problem (mentioned before). Just setting a screensaver
seems to be one of the "fixes". Use of blank screen is a good, low CPU
consuming choice.

> Also, executing df -h indicates that the root filesystem was at 100%
> capacity.  I removed a few minor rpm's that I didn't need, and am now at
> 99% capacity; I need to figure out how to increase the size of the root
> partition, or move some more files off that partition and onto another
> monster unused partition that I have set up.
[chop]

Partitions that tend to use up a lot of space and are mostly safe for
re-allocation:
/usr ( A *huge* user in many systems )
/home (A good idea so that you can clobber all other partitions in an
   upgrade but keep your user stuff safe)
/usr/local (I like to install my own packaged here and my own src trees
 here, separate from the distro's install and then change the search path
 to include /usr/local/bin and /usr/local/sbin before /usr/bin and
 /usr/sbin. If you do not use this system , then /usr/local will likely
 not be a filesystem to move and help with your root fs being full.)
/tmp (not much help in having this be off "/" but insulates you if you
 have users who want to use gimp and use /tmp for their images or cdrom
 ISO for burning.)
/var ( a good one to relocate to another partition / mounted-volume as it
 often contains your web stuff (default in many instances /var/www) and
 your log files (/var/log) and you dont want a runaway daemon spewing
 fourth jibberish to fill up your root partition.
/var/log even better to give /var/log its own place after you have a
 separate place for /var so the logging services wont impact your web
 users

Brief (for me) steps on moving data to new partitions...
Partition new space (on a new disk, or existing free space)

(Broken to 2 choices.
The first one is long, time consuming and is the "right" way. (Opinion) 
The second one is a short "hack" or "patch" that can be used, but is not
an ideal solution. It is of course shorter, but not as well liked unless
you are in an emergency and need to ave the least downtime and can do it
"right" later when you can schedule down-time for the server.
)

You can use other filesystems if your kernel has support for them - make
sure they are compiled as part of the kernel - not as a module. This is
really critical for the "/" volume

Let us assume it is /deb/hdd1 (a second Hard disk on an IDE/ATAPI
interface that is on the secondary bus and is a slave, and its first
partition)

(Side note: Primary IDE/ATAP Master = /dev/hdaN where /dev/hda is the
whole device, and if a number is where "N" is, that describeds the
partition (1-4 = primary while 5+ extended partitions of a Primary
partition.) and then /dev/hdbN is primary slave, /dev/hdcN is secondary
master, and /dev/hddN secondary slave. SCSI would be /dev/sdaN,
/dev/sdbN, /dev/sdcN, /dev/sddN, /dev/sdeN  with "s" = SCSI, "d"=disk,
(letter, "a", "b", "c"..) based on SCSI ID, and "N" same as hda... series
above)

Format the partition (the deletes all data on that partition)
# mkfs -t ext2 /dev/hdd1
This assumes you are formatting with ext2. If you are more advanced, note
that reiserfs and ext3 have more features that many consider better. There
are also other filesystems available too. ext2 is just one of the easier
ones to setup as it is older supported and still popular.)

Create a mount point (Say we are going to move /usr tree to the newly
mounted partition, let's call this one /usr2)
# mkdir /usr2

Now mount the partition to the mount point:
# mount -t ext2 /dev/hdd1 /usr2

Now copy all of the stuff from the old /usr tree to the new /usr2 tree. It
is not a simple copy, because you want to make sure all of the information
(ownership privs) is copied over and that you do a recursive copy.
# cp -aR /usr/* /usr2/

This will take a while. The -a flag does an archive copy to maintain
ownership and privs. The -R does a recursive and is different from a -r in
that the -R can better handle device special files (fifos, named pipes,
block special devices, character special devices, etc.) It is unlikely
that you would have such a device special file in /usr (outside of
/dev) but is still possible.

(At this point, you may want to boot your machine in Single user mode, or
kill all daemons in multiusermode and force all users to log out. You
want nothing with open files in the /usr tree or umount of it will fail.)

After the system finishes doing the copy, you should be able to:
# sync
(not really necessary, but I thinit is safer)
# umount /usr2
# mv /usr2 /usr
# mv /usr /usr.bak
# mount -t ext2 /dev/hdd1 /usr

But you are not done yet!

Now you should edit /etc/fstab
(sample of before with a monolithic filesystem, proc and a swap)

# /etc/fstab: static file system information.
#
#   

[vox-tech] My Wayward RH Box

[Richard S. Crawford]

Thanks to everyone who sent me suggestions and ideas yesterday regarding
my RH box that seems to have crashed three times within a 24-hour
period.  I played around with it last night, and it appears to have
maintained an uptime of about twelve hours now, a significant
improvement.

I deactivated the screen saver, and simply left it on "blank screen". 
That appears to have helped.

Also, executing df -h indicates that the root filesystem was at 100%
capacity.  I removed a few minor rpm's that I didn't need, and am now at
99% capacity; I need to figure out how to increase the size of the root
partition, or move some more files off that partition and onto another
monster unused partition that I have set up.

I ran a pretty complete hardware diagnostic on the machine under Windows
(because, I'm afraid, I'm more familiar with the hardware maintenance
tools under Windows than I am with the hardware maintenance tools under
Linux) and couldn't find any problems there.

Thanks again to everyone. This is a great list!


-- 
Sliante,
Richard S. Crawford

mailto:[EMAIL PROTECTED]  http://www.mossroot.com
AIM:  Buffalo2K   ICQ: 11646404  Yahoo!: rscrawford
MSN:  [EMAIL PROTECTED]

"It is only with the heart that we see rightly; what is essential is
invisible to the eye."  --Antoine de Saint Exupery

___
vox-tech mailing list
[EMAIL PROTECTED]
http://lists.lugod.org/mailman/listinfo/vox-tech