Some little problems with 2.1.129

Alex Buell (alex.buell@tahallah.demon.co.uk)
Mon, 23 Nov 1998 08:38:26 GMT


Guys,

I have been off line for most of the weekend since a hard disk decided
to have some downtime of its own. :o( What with the backup tapes being
unreadable due to a bloody well shagged tape streamer, I'm royally
fucked for now. I'm having to use *cough* *cough* WINDOWS fucking 95.
:o(

Never mind, I have my other puter at work, and I'll put my home Linux
system back together but it'll be quite a while before I'll be back in
the saddle (fiddling with sendmail/procmail/dns shit isn't my idea of
fun, guys) Thank fuck I keep my /home partition on a separate drive.

Ok, now, whilst rebuilding my system, I noticed a couple of problems

1) dcron-2.3.3 isn't Y2K compliant. It happens to use %y as a
parameter to some sscanf/printf stuff, and this only yields 2 digits.
That particular package needs sorting out. This reminded me to warn
you to keep an eye out for user land problems of this nature.

2) e2fsprogs1.12 doesn't compile quite well with 2.1.129. It appears
that major.h in /include/linux/... references to SCSI_MAJOR(x),
whilst e2fsprogs refers to this as SCSI_MAJOR - notice the missing
parameter. Removing HAVE_LINUX_MAJOR_H fixes this.

3) I've come across a very annoying but not essentially fatal problem
with mount and filesystems. Apparently, even with the right
permissions, and even though I can create/copy files to the target
file system and these succeeds quite well, Linux complains about
"illegal operation" even though it does succeed. I'll have a fuller
report when I get my Linux system back online.

Any comments?

Cheers,
Alex.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/