Sponsored Content
Operating Systems Linux Slackware Which Unix for Fileserving with NTFS partitions as one sole purpose use? Post 55612 by HamidNassiby on Wednesday 15th of September 2004 03:10:14 PM
Old 09-15-2004
Hi
Fedora has a low level of stability;
If you want a more stable distribution you can use
"Libranet GNU/Linux"
Its a disto built on the base of debian sarge and has a high stability;
But if you have a high speed connection to internet I prefer
you to download the debian sarge after 15 september.
That distro has 14 CD`s but is new stable and fastest
distribution yet;
Good Luck
 

9 More Discussions You Might Find Interesting

1. Linux

File Sharing among NTFS Partition & RH Linux 9 Partitions

Well Guys, will anybody solve my problem? I have installed Win XP and RH Linux 9 (Dual Boot) on an Intel x86 Machine. Everything is going fine except that I cannot share files among the two operating systems. For example, if I download a PDF file from internet and save it in my Win XP partition... (1 Reply)
Discussion started by: Jawwad
1 Replies

2. Linux

GRUB cannot boot NTFS partitions?

I have an issue with booting NTFS partitions with Grub. I have two HHD 1st HDD with Red Hat 9.0 and Grub as bootloader 2nd HDD with 8 Win partitions all ntfs. I have added the following line in my grub.conf: title Windows2000/Domino 6 root (hd1,0) makeactive chainloader +1 When I... (4 Replies)
Discussion started by: KDE Man
4 Replies

3. UNIX for Dummies Questions & Answers

Purpose of lint in UNIX

Can Any One let me know abut the use on "lint" in UNIX...... (1 Reply)
Discussion started by: kumar_saurabh
1 Replies

4. UNIX for Dummies Questions & Answers

unix partitions

how to access/sliceing different partions using divvy (1 Reply)
Discussion started by: sobin
1 Replies

5. UNIX for Dummies Questions & Answers

SCO Unix; possible to resize partitions?

If anyone is willing to help I would defenitely appreciate it! The situtation is that we have a client that had a "falling out" with their software/hardware vendor and now aren't able to get support for their machines and software. What's happening is they're using SCO-Unix and a medical... (5 Replies)
Discussion started by: PartieHonteuse
5 Replies

6. Ubuntu

Gparted, NTFS, Partitions, and power failures.

Having just installed mint on my new raptor, I decided I was going to removel the old unix partition from my NTFS back up drive, and resize the NTFS partition to fill the full 500gigs instead of just 300. While resizing the 300 gig to fill the full drive my computer shut off. When I booted back... (1 Reply)
Discussion started by: Methal
1 Replies

7. UNIX for Dummies Questions & Answers

Purpose of /etc/cron.d

What is the purpose of /etc/cron.d? (3 Replies)
Discussion started by: proactiveaditya
3 Replies

8. Solaris

NTFS HDD readable from UNIX

I have somehow taken on the collateral duties of System Administrator for our small internal network. At current we have one main file server with 48 SATA swappable drives under the Solaris 10 OS. My question is this. Our analysts are bringing back data from the field in Windows formatted... (8 Replies)
Discussion started by: cbrowne20
8 Replies

9. UNIX for Dummies Questions & Answers

Purpose of <>

Hi, I have read from the book that , <> causes the file to be used as both input as well as output. Can anyone give me the scenario where <> will be useful? Thanks (10 Replies)
Discussion started by: pandeesh
10 Replies
sort(3pm)						 Perl Programmers Reference Guide						 sort(3pm)

NAME
sort - perl pragma to control sort() behaviour SYNOPSIS
use sort 'stable'; # guarantee stability use sort '_quicksort'; # use a quicksort algorithm use sort '_mergesort'; # use a mergesort algorithm use sort 'defaults'; # revert to default behavior no sort 'stable'; # stability not important use sort '_qsort'; # alias for quicksort my $current; BEGIN { $current = sort::current(); # identify prevailing algorithm } DESCRIPTION
With the "sort" pragma you can control the behaviour of the builtin "sort()" function. In Perl versions 5.6 and earlier the quicksort algorithm was used to implement "sort()", but in Perl 5.8 a mergesort algorithm was also made available, mainly to guarantee worst case O(N log N) behaviour: the worst case of quicksort is O(N**2). In Perl 5.8 and later, quicksort defends against quadratic behaviour by shuffling large arrays before sorting. A stable sort means that for records that compare equal, the original input ordering is preserved. Mergesort is stable, quicksort is not. Stability will matter only if elements that compare equal can be distinguished in some other way. That means that simple numerical and lexical sorts do not profit from stability, since equal elements are indistinguishable. However, with a comparison such as { substr($a, 0, 3) cmp substr($b, 0, 3) } stability might matter because elements that compare equal on the first 3 characters may be distinguished based on subsequent characters. In Perl 5.8 and later, quicksort can be stabilized, but doing so will add overhead, so it should only be done if it matters. The best algorithm depends on many things. On average, mergesort does fewer comparisons than quicksort, so it may be better when complicated comparison routines are used. Mergesort also takes advantage of pre-existing order, so it would be favored for using "sort()" to merge several sorted arrays. On the other hand, quicksort is often faster for small arrays, and on arrays of a few distinct values, repeated many times. You can force the choice of algorithm with this pragma, but this feels heavy-handed, so the subpragmas beginning with a "_" may not persist beyond Perl 5.8. The default algorithm is mergesort, which will be stable even if you do not explicitly demand it. But the stability of the default sort is a side-effect that could change in later versions. If stability is important, be sure to say so with a use sort 'stable'; The "no sort" pragma doesn't forbid what follows, it just leaves the choice open. Thus, after no sort qw(_mergesort stable); a mergesort, which happens to be stable, will be employed anyway. Note that no sort "_quicksort"; no sort "_mergesort"; have exactly the same effect, leaving the choice of sort algorithm open. CAVEATS
As of Perl 5.10, this pragma is lexically scoped and takes effect at compile time. In earlier versions its effect was global and took effect at run-time; the documentation suggested using "eval()" to change the behaviour: { eval 'use sort qw(defaults _quicksort)'; # force quicksort eval 'no sort "stable"'; # stability not wanted print sort::current . " "; @a = sort @b; eval 'use sort "defaults"'; # clean up, for others } { eval 'use sort qw(defaults stable)'; # force stability print sort::current . " "; @c = sort @d; eval 'use sort "defaults"'; # clean up, for others } Such code no longer has the desired effect, for two reasons. Firstly, the use of "eval()" means that the sorting algorithm is not changed until runtime, by which time it's too late to have any effect. Secondly, "sort::current" is also called at run-time, when in fact the compile-time value of "sort::current" is the one that matters. So now this code would be written: { use sort qw(defaults _quicksort); # force quicksort no sort "stable"; # stability not wanted my $current; BEGIN { $current = print sort::current; } print "$current "; @a = sort @b; # Pragmas go out of scope at the end of the block } { use sort qw(defaults stable); # force stability my $current; BEGIN { $current = print sort::current; } print "$current "; @c = sort @d; } perl v5.12.1 2010-04-26 sort(3pm)
All times are GMT -4. The time now is 02:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy