[gentoo-amd64] KDE is dead...

[gentoo-amd64] KDE is dead...

[Peter Davoust]

[-- Attachment #1: Type: text/plain, Size: 483 bytes --]

Ok, so I've been hibernate-ram-ing my computer recently, and it got to the
point where /tmp was full. I thought it was time for a restart, and I did
shutdown -r now, and when I rebooted, logged into kdm, I was taken right
back to kdm. I tried it a few more times, and the same thing happened. I
tried an fvwm session: diddo. I ended up logging into a console, editing my
.xinitrc to include exec fvwm, and then startx. I'll try reinstalling kdm,
but what went wrong?

Thanks,
-Peter

[-- Attachment #2: Type: text/html, Size: 497 bytes --]

Re: [gentoo-amd64] KDE is dead...

[Andrei Slavoiu]

--- Peter Davoust <worldgnat@gmail.com> wrote:

> Ok, so I've been hibernate-ram-ing my computer
> recently, and it got to the
> point where /tmp was full. I thought it was time for
> a restart, and I did
> shutdown -r now, and when I rebooted, logged into
> kdm, I was taken right
> back to kdm. I tried it a few more times, and the
> same thing happened. I
> tried an fvwm session: diddo. I ended up logging
> into a console, editing my
> .xinitrc to include exec fvwm, and then startx. I'll
> try reinstalling kdm,
> but what went wrong?
Does `df` tell you that /tmp is not full now?

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] KDE is dead...

[Peter Davoust]

[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]

Woah! This is weird, it says that /dev/hda is 100% full! How is that
possible? I have a 60 gig hard drive, and I'm on a 27ish gig partition!?!

-Peter

On 8/15/06, Andrei Slavoiu <ansla80@yahoo.com> wrote:
>
> --- Peter Davoust <worldgnat@gmail.com> wrote:
>
> > Ok, so I've been hibernate-ram-ing my computer
> > recently, and it got to the
> > point where /tmp was full. I thought it was time for
> > a restart, and I did
> > shutdown -r now, and when I rebooted, logged into
> > kdm, I was taken right
> > back to kdm. I tried it a few more times, and the
> > same thing happened. I
> > tried an fvwm session: diddo. I ended up logging
> > into a console, editing my
> > .xinitrc to include exec fvwm, and then startx. I'll
> > try reinstalling kdm,
> > but what went wrong?
> Does `df` tell you that /tmp is not full now?
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
> --
> gentoo-amd64@gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 1522 bytes --]

Re: [gentoo-amd64] KDE is dead...

[Marcel Treis]

[-- Attachment #1: Type: text/plain, Size: 636 bytes --]

On Tuesday 15 August 2006 16:17, Peter Davoust wrote:
> Ok, so I've been hibernate-ram-ing my computer recently, and it got to the
> point where /tmp was full. I thought it was time for a restart, and I did
> shutdown -r now, and when I rebooted, logged into kdm, I was taken right
> back to kdm. I tried it a few more times, and the same thing happened. I
> tried an fvwm session: diddo. I ended up logging into a console, editing my
> .xinitrc to include exec fvwm, and then startx. I'll try reinstalling kdm,
> but what went wrong?

Have you checked wheter your / or /home/ is full?
Sounds like an error a friend of mine once had...

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-amd64] KDE is dead...

[Mike Doty]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Peter Davoust wrote:
> Woah! This is weird, it says that /dev/hda is 100% full! How is that
> possible? I have a 60 gig hard drive, and I'm on a 27ish gig partition!?!
> 
> -Peter
'du' is your friend...

- --
=======================================================
Mike Doty                      kingtaco -at- gentoo.org
Gentoo/AMD64 Strategic Lead
Gentoo Developer Relations
Gentoo Recruitment Lead
Gentoo Infrastructure
GPG: E1A5 1C9C 93FE F430 C1D6  F2AF 806B A2E4 19F4 AE05
=======================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iQCVAwUBROHbfIBrouQZ9K4FAQLDWQP9HlVmXYBM6P3IkJEft6uIdgy9Q/e9Hz2y
K/xgqq+9OzRbXBp9cLxpqLvaiS3qtbXsSq6Lenxox36mX+69+IU8cOR13Ku+ridA
D/NJhLxshNEMcyekGj0CW/27/qxMbeOVELCQSrzZTDJ5IhfKDhV4l4VavTDTIx5N
9pZF8DHfz6s=
=ACM1
-----END PGP SIGNATURE-----
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] KDE is dead...

[Hemmann, Volker Armin]

On Tuesday 15 August 2006 16:24, Peter Davoust wrote:
> Woah! This is weird, it says that /dev/hda is 100% full! How is that
> possible? I have a 60 gig hard drive, and I'm on a 27ish gig partition!?!
>

/tmp full
or a several gb big ~/.xsession-errors
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] KDE is dead...

[Peter Davoust]

[-- Attachment #1: Type: text/plain, Size: 1493 bytes --]

Ok, so I had a 5 gig disk image I was using for a guest OS. I deleted it and
it brought be down to about 93% usage, and gave me back KDE. Then I did a
series of du -s /* etc, which took me to a directory I created for a Java
application I'm writing. Somehow, a file called fool was created, and it was
enourmous. I deleted it and it brought me down to 22% usage. Is that insane
or what? I guess the file was appropriately named.....

Thanks

-Peter

On 8/15/06, Mike Doty <kingtaco@gentoo.org> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Peter Davoust wrote:
> > Woah! This is weird, it says that /dev/hda is 100% full! How is that
> > possible? I have a 60 gig hard drive, and I'm on a 27ish gig
> partition!?!
> >
> > -Peter
> 'du' is your friend...
>
> - --
> =======================================================
> Mike Doty                      kingtaco -at- gentoo.org
> Gentoo/AMD64 Strategic Lead
> Gentoo Developer Relations
> Gentoo Recruitment Lead
> Gentoo Infrastructure
> GPG: E1A5 1C9C 93FE F430 C1D6  F2AF 806B A2E4 19F4 AE05
> =======================================================
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (GNU/Linux)
>
> iQCVAwUBROHbfIBrouQZ9K4FAQLDWQP9HlVmXYBM6P3IkJEft6uIdgy9Q/e9Hz2y
> K/xgqq+9OzRbXBp9cLxpqLvaiS3qtbXsSq6Lenxox36mX+69+IU8cOR13Ku+ridA
> D/NJhLxshNEMcyekGj0CW/27/qxMbeOVELCQSrzZTDJ5IhfKDhV4l4VavTDTIx5N
> 9pZF8DHfz6s=
> =ACM1
> -----END PGP SIGNATURE-----
> --
> gentoo-amd64@gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 2242 bytes --]

Re: [gentoo-amd64] KDE is dead...

[Hemmann, Volker Armin]

On Tuesday 15 August 2006 16:51, Peter Davoust wrote:
> Ok, so I had a 5 gig disk image I was using for a guest OS. I deleted it
> and it brought be down to about 93% usage, and gave me back KDE. Then I did
> a series of du -s /* etc, which took me to a directory I created for a Java
> application I'm writing. Somehow, a file called fool was created, and it
> was enourmous. I deleted it and it brought me down to 22% usage. Is that
> insane or what? I guess the file was appropriately named.....
>

a long time ago, gimp created a temp file with a size of 4gb.. which was 
pretty deadly on a 8gb partition with 4gb free ;)

sometimes temp files are running completly mad.. a check once in a while is 
not a bad thing. 
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] KDE is dead...

[Peter Davoust]

[-- Attachment #1: Type: text/plain, Size: 903 bytes --]

Point taken. Thanks.

On 8/15/06, Hemmann, Volker Armin <volker.armin.hemmann@tu-clausthal.de>
wrote:
>
> On Tuesday 15 August 2006 16:51, Peter Davoust wrote:
> > Ok, so I had a 5 gig disk image I was using for a guest OS. I deleted it
> > and it brought be down to about 93% usage, and gave me back KDE. Then I
> did
> > a series of du -s /* etc, which took me to a directory I created for a
> Java
> > application I'm writing. Somehow, a file called fool was created, and it
> > was enourmous. I deleted it and it brought me down to 22% usage. Is that
> > insane or what? I guess the file was appropriately named.....
> >
>
> a long time ago, gimp created a temp file with a size of 4gb.. which was
> pretty deadly on a 8gb partition with 4gb free ;)
>
> sometimes temp files are running completly mad.. a check once in a while
> is
> not a bad thing.
> --
> gentoo-amd64@gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 1277 bytes --]

[gentoo-amd64] Re: KDE is dead...

[Duncan]

"Peter Davoust" <worldgnat@gmail.com> posted
7c08b4dd0608150751o418c99e5gcbae8cc9a96460ad@mail.gmail.com, excerpted
below, on  Tue, 15 Aug 2006 14:51:51 +0000:

> Ok, so I had a 5 gig disk image I was using for a guest OS. I deleted it
> and it brought be down to about 93% usage, and gave me back KDE. Then I
> did a series of du -s /* etc, which took me to a directory I created for
> a Java application I'm writing. Somehow, a file called fool was created,
> and it was enourmous. I deleted it and it brought me down to 22% usage.
> Is that insane or what? I guess the file was appropriately named.....

Let's see... 5 gig = 7%, 1.4% per gig.  93%-22%=71%  71/1.4=...  about 50
gigs.  A 50 gig "fool" file!  (This assumes you didn't delete some other
small stuff you failed to mention.)  Yeah, appropriately named, I'd say.

Did you check the contents of the thing to see what in the world (um..
what on the disk :) it was?  Maybe the creation/modification times,
perhaps in comparison to other files?

That name is ... strange... to say the least.  Going just on the name, and
the fact that it grew so huge, the possibility that immediately came to my
mind was a cracker.  Following the thought, the file would have been put
there as a DoS, possibly because the cracker couldn't get access to
anything else but could create a huge file as a disruption, or perhaps
there was a trojan plant and it was an activity log the cracker planned on
harvesting at some point for password hints or personal details.

Hopefully it's nothing of the sort, but the name... f001d might have been
a bit more suspicious, but not by much.  Of course, I haven't done Java
since about time I switched from MSWormOS as it's proprietary/slaveryware
if you are using Sun or Blackdown, and somewhat limited at present with
the Freedomware alternatives, and I don't know what you are developing, so
for all I know, "fool" was a legit file.  However, it still /sounds/
suspicious.  I'd not be comfortable until I knew exactly why it was there,
or at least until I had done a bit of forensics on my system and could be
relatively sure I hadn't been compromised.

Of course, one other possibility is a filesystem gone badly wrong, a small
file and a file system accident, that an fsck on reboot reconstructed as
using all the free space on the entire partition!  That would account for
the size, but not for the name, which would still need some sort of
explanation.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: KDE is dead...

[Peter Davoust]

[-- Attachment #1: Type: text/plain, Size: 3625 bytes --]

Well, I've picked up the habit from my computer science teacher of naming
variables and files things like doofus, fool, etc. The project I was working
on was a program that would download and replace itself as an upgrade. It
never worked because java would always change a few characters, but I guess
something downloaded a lot. I may have also created a disk image I was using
for something, and then forgot to delete it. I tried to open it with nano,
but it crashed the computer, which would make this the first time. I have a
gig of RAM, and that file was on a 30 gig partition, so I don't even want to
know what happened when nano tried to read the entire file into RAM. I did
shutdown -HF now at one point and fsck checked out fine. I'll have to do
that again, considering I just deleted a several gig file.

Thanks,
-Peter

On 8/16/06, Duncan <1i5t5.duncan@cox.net> wrote:
>
> "Peter Davoust" <worldgnat@gmail.com> posted
> 7c08b4dd0608150751o418c99e5gcbae8cc9a96460ad@mail.gmail.com, excerpted
> below, on  Tue, 15 Aug 2006 14:51:51 +0000:
>
> > Ok, so I had a 5 gig disk image I was using for a guest OS. I deleted it
> > and it brought be down to about 93% usage, and gave me back KDE. Then I
> > did a series of du -s /* etc, which took me to a directory I created for
> > a Java application I'm writing. Somehow, a file called fool was created,
> > and it was enourmous. I deleted it and it brought me down to 22% usage.
> > Is that insane or what? I guess the file was appropriately named.....
>
> Let's see... 5 gig = 7%, 1.4% per gig.  93%-22%=71%  71/1.4=...  about 50
> gigs.  A 50 gig "fool" file!  (This assumes you didn't delete some other
> small stuff you failed to mention.)  Yeah, appropriately named, I'd say.
>
> Did you check the contents of the thing to see what in the world (um..
> what on the disk :) it was?  Maybe the creation/modification times,
> perhaps in comparison to other files?
>
> That name is ... strange... to say the least.  Going just on the name, and
> the fact that it grew so huge, the possibility that immediately came to my
> mind was a cracker.  Following the thought, the file would have been put
> there as a DoS, possibly because the cracker couldn't get access to
> anything else but could create a huge file as a disruption, or perhaps
> there was a trojan plant and it was an activity log the cracker planned on
> harvesting at some point for password hints or personal details.
>
> Hopefully it's nothing of the sort, but the name... f001d might have been
> a bit more suspicious, but not by much.  Of course, I haven't done Java
> since about time I switched from MSWormOS as it's proprietary/slaveryware
> if you are using Sun or Blackdown, and somewhat limited at present with
> the Freedomware alternatives, and I don't know what you are developing, so
> for all I know, "fool" was a legit file.  However, it still /sounds/
> suspicious.  I'd not be comfortable until I knew exactly why it was there,
> or at least until I had done a bit of forensics on my system and could be
> relatively sure I hadn't been compromised.
>
> Of course, one other possibility is a filesystem gone badly wrong, a small
> file and a file system accident, that an fsck on reboot reconstructed as
> using all the free space on the entire partition!  That would account for
> the size, but not for the name, which would still need some sort of
> explanation.
>
> --
> Duncan - List replies preferred.   No HTML msgs.
> "Every nonfree program has a lord, a master --
> and if you use the program, he is your master."  Richard Stallman
>
> --
> gentoo-amd64@gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 4372 bytes --]

[gentoo-amd64] Re: Re: KDE is dead...

[Duncan]

"Peter Davoust" <worldgnat@gmail.com> posted
7c08b4dd0608160958g260c52cwa44dc502493e793e@mail.gmail.com, excerpted
below, on  Wed, 16 Aug 2006 16:58:20 +0000:

>  I've picked up the habit from my computer science teacher of naming
> variables and files things like doofus, fool, etc.

That explains it.  I can rest much easier now, as the prospect of someone
wandering around exploiting a hole on Gentoo systems to create
double-digit gigabyte "fool" files was a not a good one. =8^)  Thanks for
the followup!

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list