[opensuse] Idiot Question about Btrfs
For historical reasons my longstanding practice has been to keep two, sometimes three, separate installations of openSUSE on this multi-boot machine. I use one of them as the principal productive installation, with the other(s) available for experiments or as recovery tools if I screw something up in the main installation. Each of the installations has its own segregated (ie non-shared) /home. But, also for historical reasons, they do all share three additional custom mounts, two for general data and one for images, videos and soundfiles. All installations including the three custom mounts are in ext4 only. Currently I have Leap 42.3 as the main daily use installation, with Leap 42.2 and Tumbleweed “in reserve”. My intention is to replace 42.2 with Leap 15 as a fresh installation (not an upgrade), for use as the principal productive installation. My question is about filesystems. I’ve watched the various discussions about Btrfs with interest, though I haven’t understood much of it and have so far chosen to stick with ext4 throughout. But Btrfs seems to be improving, including in the context of rollback. So, what are the implications, if any, of installing Leap 15 using its default Btrfs and xfs filesystems in place of the existing Leap 42.2 installation but leaving the three additional data partitions (and the other installations) formatted in ext4? Alternatively, should I also convert the three shared data partitions now in ext4 to Btrfs? If so, does that mean that the root filesystem for each of the other installations should also be converted to Btrfs? Or doesn’t it matter? -- Robin K Wellington "Harbour City" New Zealand -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 26/05/2018 à 07:38, Robin Klitscher a écrit :
For historical reasons my longstanding practice has been to keep two, sometimes three
(...) I use a similar system
So, what are the implications, if any, of installing Leap 15 using its default Btrfs
the main problem in this situation with BTRFS is that it have to get at least x3 or x4 times the ext4 one, simply because some updates are very different from the original system and snapshots uses much room. This may need as much as 100Gb for /. I presently have only 30Gb and was recently hit by the "no more room" error - though t's not the first time and now I can fix it. this is not a problem per se when 2Tb disks are easy to find, but in our organization, it's not always easy to enlarge the previous ext4 partition and xfs filesystems I think the difference is mostly the inode number problem of ext4, but never had to suffer of this one myself in place of the existing Leap 42.2
installation but leaving the three additional data partitions (and the other installations) formatted in ext4?
no problem there all file systems lives together
Alternatively, should I also convert the three shared data partitions now in ext4 to Btrfs? If so, does that mean that the root filesystem for each of the other installations should also be converted to Btrfs?
better not, just in case BTRFS could show an unexpected problem just know that some distros do not like BTRFS in openSUSE way so, default ubuntu or debian install may not read or fix BTRFS. jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op zaterdag 26 mei 2018 08:27:20 CEST schreef jdd@dodin.org:
Le 26/05/2018 à 07:38, Robin Klitscher a écrit :
For historical reasons my longstanding practice has been to keep two, sometimes three
(...)
I use a similar system
So, what are the implications, if any, of installing Leap 15 using its default Btrfs
the main problem in this situation with BTRFS is that it have to get at least x3 or x4 times the ext4 one, simply because some updates are very different from the original system and snapshots uses much room. This may need as much as 100Gb for /. I presently have only 30Gb and was recently hit by the "no more room" error - though t's not the first time and now I can fix it.
this is not a problem per se when 2Tb disks are easy to find, but in our organization, it's not always easy to enlarge the previous ext4 partition
and xfs filesystems
I think the difference is mostly the inode number problem of ext4, but never had to suffer of this one myself
in place of the existing Leap 42.2
installation but leaving the three additional data partitions (and the other installations) formatted in ext4?
no problem there all file systems lives together
Alternatively, should I also convert the three shared data partitions now in ext4 to Btrfs? If so, does that mean that the root filesystem for each of the other installations should also be converted to Btrfs?
better not, just in case BTRFS could show an unexpected problem
just know that some distros do not like BTRFS in openSUSE way so, default ubuntu or debian install may not read or fix BTRFS.
jdd 100 GB is overkill. 50 GB is enough, IME.
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 02/06/2018 à 00:18, Knurpht @ openSUSE a écrit :
100 GB is overkill. 50 GB is enough, IME.
what is sure is that 30Gb is not enough (recently hit by no more space symptom), so on large rotating disk 100Gb seems ok. On ssd less than 500Gb, probably not :-( jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-02 00:18, Knurpht @ openSUSE wrote:
Op zaterdag 26 mei 2018 08:27:20 CEST schreef jdd@dodin.org:
Le 26/05/2018 à 07:38, Robin Klitscher a écrit :
For historical reasons my longstanding practice has been to keep two, sometimes three
(...)
I use a similar system
So, what are the implications, if any, of installing Leap 15 using its default Btrfs
the main problem in this situation with BTRFS is that it have to get at least x3 or x4 times the ext4 one, simply because some updates are very different from the original system and snapshots uses much room. This may need as much as 100Gb for /. I presently have only 30Gb and was recently hit by the "no more room" error - though t's not the first time and now I can fix it.
this is not a problem per se when 2Tb disks are easy to find, but in our organization, it's not always easy to enlarge the previous ext4 partition
...
100 GB is overkill. 50 GB is enough, IME.
My rule of thumb is at least three times as much as "/" has in use. As mine has 66 GB now, I would need at least 198 GB btrfs root partition. I don't see 100 GB as overkill for typical user. :-} And planing for the future, as repartitioning an existing hard disk is a chore, I would make that even bigger. Me, I would allocate 500 GB on a 4 TB rotating rust disk. Once upon a time, I thought that a 200 MB /boot partition was ample enough. It wasn't, after some years... -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 2 June 2018 at 13:01, Carlos E. R. <robin.listas@telefonica.net> wrote:
100 GB is overkill. 50 GB is enough, IME.
My rule of thumb is at least three times as much as "/" has in use. As mine has 66 GB now, I would need at least 198 GB btrfs root partition. I don't see 100 GB as overkill for typical user. :-}
And planing for the future, as repartitioning an existing hard disk is a chore, I would make that even bigger. Me, I would allocate 500 GB on a 4 TB rotating rust disk.
Once upon a time, I thought that a 200 MB /boot partition was ample enough. It wasn't, after some years...
A separate /boot partition can be more harmful than beneficial these days; for example on openSUSE distributions it prevents the use of boot-to-snapshot features which are really nice to have by default My rule of thumb is to avoid needless partitioning - have as few partitions as possible, and have each as large as possible So my in my case my boot SSD/HDD device is almost always dominated by a large btrfs partition with /, with the only other partitions being the minimum needed for UEFI booting. That does not include a /boot. I occasionally mount /home on a different SSD/HDD if the machine in question has multiple drives. I'm just as likely to have /home part of the / partition and make a /data partition on that second disk and symlink across folders containing large amounts of data (Downloads, VM images, etc) And as btrfs is heavily mentioned in this thread I'd like to make sure that everyone with an interest in using btrfs watches my lightning talk from oSC - https://media.ccc.de/v/1915-btrfs-is-awesome-except-when-it-isn-t It covers topics like analysing space in use, tidying up snapshots, and repairing a broken filesystem, all of which I've seen significant amounts of misinformation about in the past. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-02 13:07, Richard Brown wrote:
On 2 June 2018 at 13:01, Carlos E. R. <robin.listas@telefonica.net> wrote:
100 GB is overkill. 50 GB is enough, IME.
My rule of thumb is at least three times as much as "/" has in use. As mine has 66 GB now, I would need at least 198 GB btrfs root partition. I don't see 100 GB as overkill for typical user. :-}
And planing for the future, as repartitioning an existing hard disk is a chore, I would make that even bigger. Me, I would allocate 500 GB on a 4 TB rotating rust disk.
Once upon a time, I thought that a 200 MB /boot partition was ample enough. It wasn't, after some years...
A separate /boot partition can be more harmful than beneficial these days; for example on openSUSE distributions it prevents the use of boot-to-snapshot features which are really nice to have by default
I see you didn't catch the intended irony :-) I said "once upon a time", ie, long ago. At a time when /boot was needed. It was just an example of "this size is big enough", proven wrong later. Not to be taken as "use /boot separate partition", but as "50 GB is ample enough for '/'". Well, it is now... -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 2 June 2018 at 13:26, Carlos E. R. <robin.listas@telefonica.net> wrote:
A separate /boot partition can be more harmful than beneficial these days; for example on openSUSE distributions it prevents the use of boot-to-snapshot features which are really nice to have by default
I see you didn't catch the intended irony :-)
I said "once upon a time", ie, long ago. At a time when /boot was needed. It was just an example of "this size is big enough", proven wrong later. Not to be taken as "use /boot separate partition", but as "50 GB is ample enough for '/'". Well, it is now...
omg. That means...we AGREE ABOUT SOMETHING? Everyone mark this date I'm pretty sure this is one of the signs of the apocalypse! // Seriously, thanks for the clarification, and yes, exactly, I'm of the school that's it better to use all the space available rather than start small and find it's not enough down the road. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-26 07:38, Robin Klitscher wrote:
For historical reasons my longstanding practice has been to keep two, sometimes three, separate installations of openSUSE on this multi-boot machine. I use one of them as the principal productive installation, with the other(s) available for experiments or as recovery tools if I screw something up in the main installation.
Each of the installations has its own segregated (ie non-shared) /home. But, also for historical reasons, they do all share three additional custom mounts, two for general data and one for images, videos and soundfiles. All installations including the three custom mounts are in ext4 only.
Currently I have Leap 42.3 as the main daily use installation, with Leap 42.2 and Tumbleweed “in reserve”. My intention is to replace 42.2 with Leap 15 as a fresh installation (not an upgrade), for use as the principal productive installation.
My question is about filesystems. I’ve watched the various discussions about Btrfs with interest, though I haven’t understood much of it and have so far chosen to stick with ext4 throughout. But Btrfs seems to be improving, including in the context of rollback.
So, what are the implications, if any, of installing Leap 15 using its default Btrfs and xfs filesystems in place of the existing Leap 42.2 installation but leaving the three additional data partitions (and the other installations) formatted in ext4?
None. Well, size: the root partition with btrfs must be big, else it will not be able to cope with snapshots, unless the default settings in 15.0 are much better than previously (means being less aggressive or even disabling snapshots). You should need above 50 GB. A rule of thumb is three times what you would use without btrfs.
Alternatively, should I also convert the three shared data partitions now in ext4 to Btrfs?
No.
If so, does that mean that the root filesystem for each of the other installations should also be converted to Btrfs?
No.
Or doesn’t it matter?
You would have to install them new. Why bother? One change at a time. What if you are not happy with the first one? -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Robin Klitscher wrote:
So, what are the implications, if any, of installing Leap 15 using its default Btrfs and xfs filesystems in place of the existing Leap 42.2 installation but leaving the three additional data partitions (and the other installations) formatted in ext4?
I would strongly recommend doing this. If only to get used to btrfs and be able to (safely) play with it and its capabilities. I'm sure you'll like them :) As others mentioned, there is a chance the snapshots (if enabled) can cause irritations about the disk usage and lead to filled disks during updates. I've been running my laptop on a 40GB partition for more than a year. With lots of development stuff installed this is tight, and with Tumbleweed and it's massive updates this can indeed be an issue if you don't check remaining space before updates. But: I did not lose any data because of such fills (that happened twice or so to me), I'm still running the original instance of the FS and never had any issues. Nevertheless, I do have enlarged it in the meantime, and even moved it to a different disk (which is bloody easy with btrfs). So yes, rather go with something like 60GB for /
Alternatively, should I also convert the three shared data partitions now in ext4 to Btrfs? If so, does that mean that the root filesystem for each of the other installations should also be converted to Btrfs?
No, I wouldn't do that. If anything, you could convert the video one to XFS, which is said to have better handling of large files. Don't use it for a partition with games, if the partition is larger than 2TB. There are games around that cannot handle this. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 27/05/2018 à 09:56, Peter Suetterlin a écrit :
Nevertheless, I do have enlarged it in the meantime, and even moved it to a different disk (which is bloody easy with btrfs).
any link? I'm interested, thanks jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Отправлено с iPhone
27 мая 2018 г., в 11:09, "jdd@dodin.org" <jdd@dodin.org> написал(а):
Le 27/05/2018 à 09:56, Peter Suetterlin a écrit :
Nevertheless, I do have enlarged it in the meantime, and even moved it to a different disk (which is bloody easy with btrfs).
any link? I'm interested, thanks
You can simply replace one disk with another online. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 27/05/2018 à 10:13, Andrei Borzenkov a écrit :
Отправлено с iPhone
27 мая 2018 г., в 11:09, "jdd@dodin.org" <jdd@dodin.org> написал(а):
Le 27/05/2018 à 09:56, Peter Suetterlin a écrit :
Nevertheless, I do have enlarged it in the meantime, and even moved it to a different disk (which is bloody easy with btrfs).
any link? I'm interested, thanks
You can simply replace one disk with another online.
but howto move /? thanks jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
jdd@dodin.org wrote:
You can simply replace one disk with another online.
but howto move /?
From my notes: Basically it's
btrfs replace start /dev/oldroot /dev/newroot / In my case /dev/newroot was a larger partition, so after that you do btrfs filesystem resize 1:max / Then the standard stuff (grub install if it's a different disk), check /etc/fstab if there are other partitions (swap, home) involved that have changed. (In my case I move a server root between mdadm raids, so I had to also adjust mdadm.conf and grub.cfg that referenced the md uuid) There's a nice webpage at https://www.howtoforge.com/a-beginners-guide-to-btrfs -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-27 10:37, Peter Suetterlin wrote:
jdd@dodin.org wrote:
You can simply replace one disk with another online.
but howto move /?
From my notes: Basically it's
btrfs replace start /dev/oldroot /dev/newroot /
In my case /dev/newroot was a larger partition, so after that you do
btrfs filesystem resize 1:max /
Then the standard stuff (grub install if it's a different disk), check /etc/fstab if there are other partitions (swap, home) involved that have changed. (In my case I move a server root between mdadm raids, so I had to also adjust mdadm.conf and grub.cfg that referenced the md uuid)
There's a nice webpage at https://www.howtoforge.com/a-beginners-guide-to-btrfs
It also copies the volumes structure? Can this be used to create backups? Or just one backup per disk? -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
On 2018-05-27 10:37, Peter Suetterlin wrote:
jdd@dodin.org wrote:
You can simply replace one disk with another online.
but howto move /?
From my notes: Basically it's
btrfs replace start /dev/oldroot /dev/newroot /
In my case /dev/newroot was a larger partition, so after that you do
btrfs filesystem resize 1:max /
Then the standard stuff (grub install if it's a different disk), check /etc/fstab if there are other partitions (swap, home) involved that have changed. (In my case I move a server root between mdadm raids, so I had to also adjust mdadm.conf and grub.cfg that referenced the md uuid)
There's a nice webpage at https://www.howtoforge.com/a-beginners-guide-to-btrfs
It also copies the volumes structure?
Yes, of course.
Can this be used to create backups? Or just one backup per disk?
No, it replaces things. The old partition is emptied (likely, only all relevant superblocks are zeroed - I didn't check). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-27 10:48, Peter Suetterlin wrote:
Carlos E. R. wrote:
On 2018-05-27 10:37, Peter Suetterlin wrote:
jdd@dodin.org wrote:
You can simply replace one disk with another online.
but howto move /?
From my notes: Basically it's
btrfs replace start /dev/oldroot /dev/newroot /
In my case /dev/newroot was a larger partition, so after that you do
btrfs filesystem resize 1:max /
Then the standard stuff (grub install if it's a different disk), check /etc/fstab if there are other partitions (swap, home) involved that have changed. (In my case I move a server root between mdadm raids, so I had to also adjust mdadm.conf and grub.cfg that referenced the md uuid)
There's a nice webpage at https://www.howtoforge.com/a-beginners-guide-to-btrfs
It also copies the volumes structure?
Yes, of course.
Can this be used to create backups? Or just one backup per disk?
No, it replaces things. The old partition is emptied (likely, only all relevant superblocks are zeroed - I didn't check).
Uh oh... if the procedure fails for some reason, you have neither the initial disk nor the final disk. With XFS I can "image" an entire XFS filesystem or partition to a file on another partition, and this image can be used to create a copy of that on another disk later on. The file is a full backup. I mention xfs because xfs and btrfs share some developers, so some features appears on both. xfs_copy(8) xfs_copy - copy the contents of an XFS filesystem xfs_copy copies an XFS filesystem to one or more targets in parallel (see xfs(5)). The first (source) argument must be the pathname of the device or file containing the XFS filesystem. The remaining arguments specify one or more target devices or file names. If the pathnames specify devices, a copy of the source XFS filesystem is created on each device. The target can also be the name of a regular file, in which case an image of the source XFS filesystem is created in that file. If the file does not exist, xfs_copy creates the file. The length of the resulting file is equal to the size of the source filesystem. However, if the file is created on an XFS filesystem, the file consumes roughly the amount of space actually used in the source filesystem by the filesystem and the XFS log. The space saving is because xfs_copy seeks over free blocks instead of copying them and the XFS filesystem supports sparse files efficiently. xfsdump(8) xfsdump - XFS filesystem incremental dump utility xfsdump backs up files and their attributes in a filesystem. The files are dumped to storage media, a regular file, or standard output. Options allow the operator to have all files dumped, just files that have changed since a previous dump, or just files contained in a list of pathnames. The xfsrestore(8) utility re-populates a filesystem with the contents of the dump. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
On 2018-05-27 10:48, Peter Suetterlin wrote:
Carlos E. R. wrote:
It also copies the volumes structure?
Yes, of course.
Can this be used to create backups? Or just one backup per disk?
No, it replaces things. The old partition is emptied (likely, only all relevant superblocks are zeroed - I didn't check).
Uh oh... if the procedure fails for some reason, you have neither the initial disk nor the final disk.
I don't think those guys are stupid, and would expect the clearing to be the last step after the new setup is working. But all three times I've done it so far succeeded without issues.
With XFS I can "image" an entire XFS filesystem or partition to a file on another partition, and this image can be used to create a copy of that on another disk later on. The file is a full backup.
I haven't looked for similar things in btrfs so far. The solution seems to be to either play around with seed devices and mirror raid, or use partclone, which is in the OS repos. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 27/05/18 20:48, Peter Suetterlin wrote:
Carlos E. R. wrote:
On 2018-05-27 10:37, Peter Suetterlin wrote:
jdd@dodin.org wrote:
You can simply replace one disk with another online.
etc
Thank you to all who responded. Most useful -- Robin K Wellington "Harbour City" New Zealand -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 27/05/2018 à 10:37, Peter Suetterlin a écrit :
jdd@dodin.org wrote:
You can simply replace one disk with another online.
but howto move /?
From my notes: Basically it's
ok, great, thanks jdd
btrfs replace start /dev/oldroot /dev/newroot /
In my case /dev/newroot was a larger partition, so after that you do
btrfs filesystem resize 1:max /
Then the standard stuff (grub install if it's a different disk), check /etc/fstab if there are other partitions (swap, home) involved that have changed. (In my case I move a server root between mdadm raids, so I had to also adjust mdadm.conf and grub.cfg that referenced the md uuid)
There's a nice webpage at https://www.howtoforge.com/a-beginners-guide-to-btrfs
-- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 27/05/18 03:56 AM, Peter Suetterlin wrote:
Nevertheless, I do have enlarged it in the meantime, and even moved it to a different disk (which is bloody easy with btrfs).
It is also easy if you use LVM. What I don't like about BtrFS is its "One FS To Rule Them All" attitude. Its not just a FS, but also, as many point out like Peter and JDD, a volume manager. Choose to use separation of function. If and when I run BtrFS I still run it in a LVM Logical Volume. Using LVM I can snapshot, do disk-to-disk backup or disk-to-disk-to-net-to-disk backups quite easily. I can also easily implement "thin provisioning". Ha! talk about putting "ten pounds in a five pound bag"! I can put (logical) 250Mb in a (physical) 50Mb partition! LVM lets me do the 'virtual memory' of disks! -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Late to the party, but... On 05/26/2018 01:38 AM, Robin Klitscher wrote:
For historical reasons my longstanding practice has been to keep two, sometimes three
(...) I, too, use a similar multi-boot strategy for my primary work system for similar reasons. (I'm feeling less weird.) It's a good for using OpenSuSE as a platform to do something on, including developing apps not part of "OpenSuSE." Sadly, these aren't idiot questions you ask. Answers based on a deep dive a couple months ago into docs and arguments around BTRFS n ZFS. It seems like BTRFS does a lot of admin-y stuff; stuff you need somewhere, once, in your setup. ZFS is more like "What prior file systems do, but done better." Also ZFS been in deployed use longer, though not via OpenSuSE. So far I've had no problems running a fresh install of 15.0 on an expendable machine: EXT4 root n home, ZFS data puddle. I haven't yet tried 15.0 into my multi-boot primary laptop. I am not a developer of these components, or of OpenSuSE. YMMV. (...)
So, what are the implications, if any, of installing Leap 15 using its default Btrfs and xfs filesystems in place of the existing Leap 42.2 installation
You'll need more space for "root". And have to get used to the additional stuff BTRFS does. Leaving 15.0 root on NotBTRFS loses only the unique stuff BTRFS does beyond the capabilities any filesystem has. Possibly later OpenSuSE comes to depend on BTRFS-only features for "root" or other uses.
... leaving the three additional data partitions (and the other installations) formatted in ext4?
AFAIK should work fine (For now.)
Alternatively, should I also convert the three shared data partitions now in ext4 to Btrfs?
Good question. Not required by the technology at this time.
If so, does that mean that the root filesystem for each of the other installations should also be converted to Btrfs?
"Should" work just fine as is, which is what I think you are asking. Whether you "should" convert all to BTRFS to do stuff the new way is a policy and political question. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I'd be happy to take a shot at contributing a half page on the current fs buffet in OpenSuSE (LEAP 15.0) Questions about the fs buffet in LEAP 15.0 keep coming up from computer literate users trying to use OpenSuSE, trying to get oriented to what's going on with these components. It seems like a findable, authoritative half-page orientation with some links would help with that. Could someone point me to the OpenSuSE guidelines for: -- Where something like that might go -- Contribution & acceptance protocol -- Writing and style standards Or where's the better place to ask this question? In general, it seems like a bunch of half-page "start here"'s would help people who don't wrangle OpenSuSE full time get oriented enough to use it. Difficulty getting oriented sometimes stops people from using OpenSuSE, or even "upgrading" when they'd like to (and probably should.) I'd likely contribute one of these every couple months based on technical topics I unwind for my own use, if I could figure out how to contribute what I've gathered in solving my own problem. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-03 22:07, James Bullock wrote:
I'd be happy to take a shot at contributing a half page on the current fs buffet in OpenSuSE (LEAP 15.0) Questions about the fs buffet in LEAP 15.0 keep coming up from computer literate users trying to use OpenSuSE, trying to get oriented to what's going on with these components. It seems like a findable, authoritative half-page orientation with some links would help with that.
Could someone point me to the OpenSuSE guidelines for:
-- Where something like that might go -- Contribution & acceptance protocol -- Writing and style standards
Or where's the better place to ask this question?
<opensuse-web@opensuse.org> :-) <https://en.opensuse.org/Portal:Wiki> -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 06/03/2018 04:54 PM, Carlos E. R. wrote:
Could someone point me to the OpenSuSE guidelines for:
-- Where something like that might go -- Contribution & acceptance protocol -- Writing and style standards
Or where's the better place to ask this question?
<opensuse-web@opensuse.org> :-)
Thanks, man. I'll ask them & there. Prior peruse of portal left me: - Less than confident about contact protocol - Vague at about standards and approval process - Pretty clear that what I'm contemplating doesn't fit the def of any acceptable content type established for the wiki I'll take a shot over this coming weekend n see what happens. -- Jim Bullock, Rare Bird Enterprises, "Conscious Development" LinkedIn: http://www.linkedin.com/in/rarebirdenterprises Listen to a round table of experts in these books from Dorset House: Roundtable on Project Management, http://www.dorsethouse.com/books/rpm.html Roundtable on Technical Leadership, http://www.dorsethouse.com/books/rtl.html -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Forgot to snip my .sig out of the reply. Sorry. Sorry. Sorry. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op zondag 3 juni 2018 22:07:21 CEST schreef James Bullock:
I'd be happy to take a shot at contributing a half page on the current fs buffet in OpenSuSE (LEAP 15.0) Questions about the fs buffet in LEAP 15.0 keep coming up from computer literate users trying to use OpenSuSE, trying to get oriented to what's going on with these components. It seems like a findable, authoritative half-page orientation with some links would help with that.
Could someone point me to the OpenSuSE guidelines for:
-- Where something like that might go -- Contribution & acceptance protocol -- Writing and style standards
Or where's the better place to ask this question?
In general, it seems like a bunch of half-page "start here"'s would help people who don't wrangle OpenSuSE full time get oriented enough to use it. Difficulty getting oriented sometimes stops people from using OpenSuSE, or even "upgrading" when they'd like to (and probably should.)
I'd likely contribute one of these every couple months based on technical topics I unwind for my own use, if I could figure out how to contribute what I've gathered in solving my own problem. Hi James,
The openSUSE Project strives to make contributing as easy as looking out of a window. Create an account and you can start contributing to the wiki, build packages in OBS, access the forums and so on. Thanks for offering, -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (9)
-
Andrei Borzenkov -
Anton Aylward -
Carlos E. R. -
James Bullock -
jdd＠dodin.org -
Knurpht ＠ openSUSE -
Peter Suetterlin -
Richard Brown -
Robin Klitscher