Re: [yast-devel] Re: Query on btrfs on SLES12
On 13.06.2017 13:14, Suresh K Hosamani wrote:
Conclusion is, nothing can be done from yast install code or controls.xml to change the default root partition type from brtfs to ext3, only option left is to document it, saying for OES root partition needs to be created manaully with ext3 type.
I just checked again in the code where that Btrfs default comes from, and it looks like it is ultimately read from /etc/sysconfig/storage : ... ... ## Type: string(ext2,ext3,ext4,xfs,btrfs) # Default filesystem type. DEFAULT_FS="btrfs" ... This file exists in the inst-sys, too, so it might be possible to replace this file with a driver update disk (DUD). If that works, you could integrate that DUD into the ISO you ship as the base for your OES product. Let me check that. Kind regards -- Stefan Hundhammer <shundhammer@suse.de> YaST Developer SUSE Linux GmbH GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 13.06.2017 15:55, Stefan Hundhammer wrote:
I just checked again in the code where that Btrfs default comes from, and it looks like it is ultimately read from /etc/sysconfig/storage :
... ... ## Type: string(ext2,ext3,ext4,xfs,btrfs) # Default filesystem type. DEFAULT_FS="btrfs" ...
This file exists in the inst-sys, too, so it might be possible to replace this file with a driver update disk (DUD). If that works, you could integrate that DUD into the ISO you ship as the base for your OES product.
Let me check that.
Bingo - works like a charm. See attached ext3.dud. The procedure to create this is as follows: - Make sure to install packages mkdud and mksusecd, then [shundhammer @ morgul] ~ 1 % cd /tmp [shundhammer @ morgul] /tmp 2 % mkdir -p dud-root/etc/sysconfig [shundhammer @ morgul] /tmp 3 % cp /etc/sysconfig/storage dud-root/etc/sysconfig [shundhammer @ morgul] /tmp 5 % vi dud-root/etc/sysconfig/storage ...(edit)... [shundhammer @ morgul] /tmp 6 % diff -u /etc/sysconfig/storage dud-root/etc/sysconfig/storage --- /etc/sysconfig/storage 2017-06-12 12:37:02.074656188 +0200 +++ dud-root/etc/sysconfig/storage 2017-06-13 16:03:46.312521521 +0200 @@ -5,7 +5,7 @@ ## Type: string(ext2,ext3,ext4,xfs,btrfs) # Default filesystem type. -DEFAULT_FS="btrfs" +DEFAULT_FS="ext3" ## Type: string(optimal,cylinder) # Value for partition alignment [shundhammer @ morgul] /tmp 7 % mkdud --create ext3.dud --dist SLE12 /tmp/dud-root/ === Update #1 === [SLE 12] Name: Update 0b59bdc6-f4ba-4937-8a2d-7705616946ce ID: 0b59bdc6-f4ba-4937-8a2d-7705616946ce Installation System: /etc/sysconfig/storage [shundhammer @ morgul] /tmp 8 % mkdud --show ext3.dud === Update #1 === [SLE 12] Name: Update 0b59bdc6-f4ba-4937-8a2d-7705616946ce ID: 0b59bdc6-f4ba-4937-8a2d-7705616946ce Installation System: /etc/sysconfig/storage Then use that DUD directly on the installation disk boot prompt or integrate it into an ISO as decribed here: https://github.com/shundhammer/huha-linux-tips/blob/master/doc/yast-devel-ti... sudo mksusecd --create my-patched-SLE-12.iso \ --initrd \ /tmp/ext3.dud \ SLE-12-SP3-Server-DVD-x86_64-Build0418-Media1.iso I tested this with the latest SP3 beta (as you can see above), and it proposed an ext3 root filesystem for me. There is a catch, though: Since that combo box with the available filesystem types does not contain ext3, this will only work as long as the user doesn't want to change anything in the "proposal settings". Unless you have any pressing reason against that, I suggest you use ext4 instead; this would integrate a whole lot better into the installation. HTH + we will gratefully accept any beer invitations the next time some of you guys come visiting ;-) Kind regards-- Stefan Hundhammer <shundhammer@suse.de> YaST Developer SUSE Linux GmbH GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany
Hi, Till OES2015SP1 (sles11), OES configuration use to happen in second stage of installation, due to initd scripts, all our services were coming up as expected after the second stage. For OES2018 (SLES12SP2), we have introduced <stage>continue</stage> and <mode>installation</mode>, so in the second stage all OES services will be configured and rebooted, during reboot it start network and other services, due to this OES network setting are missing and OES services are not getting started until we start from yast module, even though we have added correct After, Wants and WantedBy as multi-user.target. Once the system is rebooted again after second stage reboot all services comes up properly. Since we have introduced second stage, do we need to handle anything different. Regards, Suresh
participants (2)
-
Stefan Hundhammer -
Suresh K Hosamani