linux-kernel - Re: The ext3 way of journalling

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1a9da18c0801081007q1ed8ce04x7a78e880ee5bcac7@mail.gmail.com>
Date:	Tue, 8 Jan 2008 10:07:37 -0800
From:	"Masoud Sharbiani \"مسعود شربیانی\"" 
	<masouds@...oud.ir>
To:	"Tuomo Valkonen" <tuomov@....fi>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: The ext3 way of journalling

On 1/8/08, Tuomo Valkonen <tuomov@....fi> wrote:
> On 2008-01-08, Andre Noll <maan@...temlinux.org> wrote:
> > Use tune2fs to deactivate checking.
>
> So, a workaround is the answer to a clear bug. Typical FOSS.

It isn't a bug. It is a feature; Think about silent corruption that
may damage your filesystem; Only an FSCK can see how much of damage is
done and fix it. Journaling will help you to a degree, but not all the
way.

> > Modify the init scripts or use another distro.
>
> Another typical FOSS answer. "You have the source, you can fix it."
> With what time?

heh, the way I look at it, you either have the time, or money. Use one
and get rid of your problem. If you have them and aren't willing to
commit to fix your problem, maybe your problem isn't important enough
to you. If you have no time and no money, ranting here doesn't help
you either.

cheers,
Masoud

> > Don't use udev then. Good old static dev works fine if you have a fixed
> > set of devices.
>
> It doesn't, with the unpredictable SCSI mapping insanity.
>
> > You're using the sil3112 driver? Edit its blacklist and remove the
> > entry for your drive. That gives you the usual speed.
>
> Recompiling? No thanks. Compiling the Linux kernel is too painful.
>
> > Check your tool-chain. Many people compile recent kernels with no problems.
>
> And recompile and recompile and recompile ad infinitum, because always
> some option was missing or wrong, there being far too many of them and
> hidden all over the place.
>
> > Nobody forces you to use udev. Moreover, you can write your own udev
> > rules that match your expectations.
>
> See above on having time to learn over-cryptic systems.
>
> > You're not ranting about Linux but about your Distro. Complain on
> > the corresponding distro-specific mailing list, use another distro
> > and and stop whining.
>
> I don't use a distro kernel. I use a kernel I compiled myself over
> two years ago. I have tried compiling newer ones, but it's too much
> work to get all the options right. And then there's the problem that
> the "good" driver for my SATA disk may not be there anymore in the
> latest kernels, and so on.
>
> --
> Tuomo
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/