mÃ¥n 2004-04-05 klockan 15.20 skrev Colin Watson:
> On Mon, Apr 05, 2004 at 02:10:19PM +0200, smurfd aka nicklas boman wrote:
> > l??r 2004-04-03 klockan 18.43 skrev smurfd:
> > > BUT, after some usage i found a file called /1 wich contained
> > > something about /etc/emacs and /2 and i dont use emacs. Though in
> > > /etc/emacs there was some that could have been installed by devhelp.
> > >
> > > My question is, has anyone else had this /1 file? was i rooted? is
> > > it a known bug? Anyway i had to wipe my drive, so i cant paste the
> > > exact containment in the /1 file.
> > Okey, a short update.
> > The installer, still kick-ass, though, i wasnt able to make it install
> > lilo instead of grub. i skipped the "install grub" and choosed "install
> > lilo" instead, bud as i hit enter, i see the installer saying
> > "installing Grub" .. not lilo.
> > Weird.. (i know its still under development.. just wanted to let ya
> > know)
> Installation reports are best sent to debian-boot.
> > I have narrowed down the possibillities of things that could be the
> > cause of that file.
> > 1st) I had a visitioir, simple as that. i was kindof unprotected, though
> > still it feels pretty stupit to leave a file that visible...
> > 2nd) What i can think of, the only package i havent installed that was
> > on this box before is the mldonkey-server & mldoneky-gui packages, wich
> > i was using..
> > anyway, would appreciate some opinions. what could have caused this..
> > shall i post a bug report?
> It seems very likely that the files are the result of a maintainer
> script bug rather than any kind of attack. However, you'd need to be
> able to narrow it down to a particular package before you wipe the disk
> in order to file a bug, really.
> Colin Watson [email@example.com]
Okey will look/send to debian-boot.
Okidoki, will try to see if i can "recreate" the bug
/smurfd aka. nicklas boman
- From: smurfd <firstname.lastname@example.org>
- Re: Root1
- From: smurfd aka nicklas boman <email@example.com>
- Re: Root1
- From: Colin Watson <firstname.lastname@example.org>