|rahul||jelly: or you don't get nulls if you enable the feature that prevents it|
|action||jelly likes the support for online resize and tuning for raid underneath (stripe size etc)|
|jelly||likes the support for online resize and tuning for raid underneath (stripe size etc)|
|stew||nocti: i'm not sure if they have one, otherwise, /msg dpkg marillat|
|GutterPunk||justin, bwlang but is there any point to using lvm on an md that will only be used for one specific logical volume? namely /storage.... I don't need var or anything on it|
|nocti||ok thanks stew|
|GutterPunk||thus actually creating only one partition on the lvm|
|stew||nocti: mplayer was only recently added to debian, there might not be a backports|
|bwlang||rahul: i read your superblock comment as a boot issue - classic fud re: xfs. if you use grub why would you want to mess with a superblock?|
|justin||GutterPunk: in that case, no|
|rahul||bwlang: 11:29 < jetscreamer> xfs has a grub problem when grub is on the xfs partitionbtw|
bwlang: learn how to read.
|dpkg||O frabjous day! Callooh! Callay! stew has returned!|
could anyone please traceroute velirat.de?
it's my bnc, and I can't connect to it
|bwlang||GutterPunk: lvm gives you flexibility at the expense of complexity... if you don't need the flexibility then you don't need lvm|
|RvGaTe||Hi, i was trying to customize my login, and noticed that i could use sounds \o/, so i downloaded some sounds, put them in /usr/share/sounds/system/login_[fail/success/ready].wav... i configured my login screen to use these sounds, but whener the login is ready, success or failed, i get this anoying system *beep*... meaning that the login sounds are not working... any ideas? (debian etch)|
|jelly||harddisk_wp: stops at static-ip-62-75-135-126.inaddr.intergenia.de|
|GutterPunk||you have been a great help|
|rahul||bwlang: now do you have any other misreadings of what I said to disagree with?|
|jetscreamer||!greet abrotman & stew|
|dpkg||Hello, abrotman & stew|
|HardDisk_WP||jelly, ok, thanks...that is the same I see. It seems my provider has problems|
|bwlang||rahul: you state that xfs waits to write data, that's false it can be configured to sync very quickly|
|rahul||bwlang: uh, I said the opposite, actually|
by default it writes quickly (actually waits)
(in recent kernels)
so I guess that was a yes. you do have misreadings of what I said to disagree with.
"Barrier support will flush the write back cache at the appropriate times (such as on XFS log writes)."
|bwlang||rahul: sounds like we both think xfs is a usable filesystem ... lets just leave it there. i'm sorry for any offense|
|rahul||(yeah, I've been using XFS since 2.5.59) anyway, let's move on :)|
|RvGaTe||anyone ? :(|