| === james is now known as Guest41816 | ||
| === james is now known as Guest92917 | ||
| === james is now known as Guest3185 | ||
| === akk_ is now known as Guest13346 | ||
| === james is now known as Guest30623 | ||
| === me is now known as Guest82024 | ||
| === james is now known as Guest9511 | ||
| === james is now known as Guest74111 | ||
| === cyphase_eviltwin is now known as cyphase_ | ||
| === cyphase_ is now known as cyphase | ||
| willubuntu | ok | 13:16 |
|---|---|---|
| willubuntu | slt | 13:16 |
| strk | Hi, I have a silly question. Is it *really* so dangerous to "resize a partition" at install time ? (for my data) | 14:58 |
| strk | I've to decide whether or not I want to take the risk of loosing data, basically | 14:58 |
| strk | is the installer using gparted, for that ? | 14:59 |
| kc2bez[m] | strk: There is a potential any time you manipulate partitions for things to go wrong. The only sure thing is to make sure you have a backup of your data. The installer uses the core libraries from the KDE Patition manager. | 16:12 |
| lubot | [telegram] <aptghetto> If you don't have a backup yet, you already decided to take a risk and that you don't have important data. | 16:19 |
| strk | I kind of *could* support the risk (I do have backup, just not very handy) | 19:12 |
| strk | "core libs fro mKDE Partition Manager" means it's NOT GParted ? | 19:13 |
| wxl | right | 19:14 |
| strk | so, do those libraries reorganize inodes to make space, for new partitions ? | 19:15 |
| * strk is tempted to give that a try | 19:15 | |
| honeycomb | test | 19:34 |
| === theloudspeaker_ is now known as The_LoudSpeaker | ||
| === E_Eickmeyer is now known as Eickmeyer | ||
| === BrianG61UK__ is now known as BrianG61UK | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!