Andrey,
Great work, thank you. I have a little destraught about this over the
years since its inception with having just a label class for itself. Now
that this has all be properly tested it seems like a good idea to me to
split them up into their respective sections as you have done.
Now with t
and test it again by running the same
commands that are run in the 100.chksetuid script ?
Actually I just looked over the script, "That syntax is just fuggin
crazy"
( find /path/to/offending/directory ) should do it.
--
Regards,
J. Hellenthal
WWJD
pgpEXDJbbmQIW.pgp
Description: PGP signature
ed now"
/dev/disk0/
[label]
[guid]
[ufsid]
[zfsid]
[gptid]
[slice1 or part1]
And [label] could be anywhere from msdosfs to ufs with some sort of
priority chain that is followed to determine which label should be
showing.
For instance if it is a msdosfs and no other generic label has been set
then use the msdosfs label else do not show the label.
Of course other prevention would need to be taken to prevent collision
of purposeful user corruption of duplicate labels but it at least
provides a predictable location as to which the disks appear under the
device filesystem.
Just some thoughts but I'm sure this thread is far beyond what it was
originally meant to be about so Ill leave it there.
--
Regards,
J. Hellenthal
WWJD
pgpbFXqOtiikr.pgp
Description: PGP signature
On Tue, Apr 19, 2011 at 08:17:37PM -0400, J. Hellenthal wrote:
>On Tue, Apr 19, 2011 at 02:22:10PM +0200, Ulrich Spörlein wrote:
>>On Tue, 19.04.2011 at 12:15:00 +0100, Bruce Cran wrote:
>>> There's a new tool that can be used to find spelling mistakes in code:
>&
he functional changes. The no-op changes I
just filtered out of the patch to quickly catch the "Bad Thing" changes
above.
It might just be better to build a list of files with spelling errors
and anyone with the next commit to any of those files just runs it
through aspell/ispell or wha
output and also be available for consumption by other utilities that may
need fine tuning without breaking existing interfaces.
--
Regards,
J. Hellenthal
pgphAtxdZ2IbB.pgp
Description: PGP signature
>Although I (and others) keep an eye on the other mailing lists, you'll be
>more likely to get a response if you instead email the wireless list.
>
Hey! good idea.
--
J. Hellenthal
pgphTxkQ9Ow8x.pgp
Description: PGP signature
s simple to use.
zfSnap keeps all information about snapshot in snapshot name. zfs snapshot
names are in form: Time-stamp--TTL where time-stamp is date and time of
snapshot creation and TTL is Time To Live in human readable form.
Did you happen to mix the above two up ? If so then rinse and re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Just to be sure as the long detailed information that you laid before
can lead to confusion, lets take this one step at a time.
Assuming all your bases are covered and it sinks down to a permissions
issue try this:
chown root:wheel /path/to/
