From: pbrunnen <PBrunnen@bccnetworks.net>
To: xfs@oss.sgi.com
Subject: Re: XFS Filesystem not mounting
Date: Tue, 14 Sep 2010 09:35:58 -0700 (PDT) [thread overview]
Message-ID: <29710491.post@talk.nabble.com> (raw)
In-Reply-To: <4C8F9E29.2000803@hardwarefreak.com>
Hi Stan,
Stan Hoeppner wrote:
>
> I've been using Debian for headless servers for many years.
> Distribution upgrades via apt-get or aptitude have been smooth and easy
> for many years. I have one server that's been in-place upgraded from
> Woody through Lenny with only minor dependency issues--that's 4
> distribution upgrades over 5 years--Woody, Sarge, Etch, Lenny.
>
Part of my reasoning for looking towards debian is because I was forced into
it about two years ago. I manage a solution for one of my company partners
which is based on etch with backported kernels. There are many things I
like about it... and I agree on the clean upgrade path and very good package
management.
But the downsides to debian have been holding me back...
1) I miss yast. aptitude is just not the same.
2) Vendor support is officially non-existant. We are a Dell shop and
upgrading openmanage is a pain. With SuSE its download and go.
3) I understand the ideology and legal reasons debian removes firmware blobs
(broadcom anyone) from their kernel modules... but this is always a real
pain. I end up monkeying about with the initrd image to get the firmware
blobs in... and often I just recompile with the blobs and forget it.
Stan Hoeppner wrote:
>
> Then again, I don't use Debian kernels, so my kernels were never
> upgraded during the dist upgrade. This may have prevented some
> headaches. I roll my own kernels from kernel.org source and tend to
> keep fairly current. So, when I do a dist upgrade my current kernel is
> usually newer than what the dist upgrade provides. The fact I leave out
> features I don't need may play a role in preventing problems as well.
>
;-) That makes a huge difference. But generally my experience thus far
with debian has been positive. Enough to make me consider switching. And
I know the XFS has never given me a lick of trouble.
*Didn't want to seem off topic. Had to throw in the XFS reference at the
end. lol.
Thanks again for everyone's input.
Its Much Appreciated!
-Cheers, Peter.
--
View this message in context: http://old.nabble.com/XFS-Filesystem-not-mounting-tp29704010p29710491.html
Sent from the Xfs - General mailing list archive at Nabble.com.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-14 16:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 23:45 XFS Filesystem not mounting pbrunnen
2010-09-14 1:21 ` Dave Chinner
2010-09-14 4:29 ` pbrunnen
2010-09-14 5:40 ` Michael Monnerie
2010-09-14 6:25 ` Emmanuel Florac
2010-09-14 12:32 ` pbrunnen
2010-09-14 14:03 ` Michael Monnerie
2010-09-14 16:09 ` Stan Hoeppner
2010-09-14 16:35 ` pbrunnen [this message]
2010-09-14 18:03 ` Now: Debian issues, WAS: " Stan Hoeppner
2010-09-14 20:32 ` Emmanuel Florac
2010-09-15 1:07 ` pbrunnen
2010-09-15 3:51 ` Stan Hoeppner
2010-09-15 13:15 ` pbrunnen
2010-09-15 0:44 ` Dave Chinner
2010-09-15 2:54 ` Stan Hoeppner
2010-09-15 0:49 ` pbrunnen
2010-09-14 16:25 ` pbrunnen
2010-09-14 4:43 ` pbrunnen
2010-09-14 5:40 ` Dave Chinner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=29710491.post@talk.nabble.com \
--to=pbrunnen@bccnetworks.net \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.