[Bug 586529] New: kiwi: call custom skript after recovery was called
http://bugzilla.novell.com/show_bug.cgi?id=586529 http://bugzilla.novell.com/show_bug.cgi?id=586529#c0 Summary: kiwi: call custom skript after recovery was called Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEEDINFO Severity: Normal Priority: P5 - None Component: System Imaging AssignedTo: ms@novell.com ReportedBy: ms@novell.com QAContact: adrian@novell.com CC: jlee@novell.com Found By: --- Blocker: --- it would be nice to let kiwi call a custom script after the recovery process finished. Therefore I have the following questions: 1) I can call the script only before init is called. Is that ok for you ? if not the script should be a runlevel script and kiwi only activates it via insserv. 2) We need to specify a name and a location for the script. Please suggest one as you like it. If we need a runlevel script the location must be in /etc/init.d and the script itself must self-deactivate it after the call if it's enough to run before init is called there are no rules the script has to take care for -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=586529
http://bugzilla.novell.com/show_bug.cgi?id=586529#c
Marcus Schaefer
http://bugzilla.novell.com/show_bug.cgi?id=586529
http://bugzilla.novell.com/show_bug.cgi?id=586529#c
Marcus Schaefer
http://bugzilla.novell.com/show_bug.cgi?id=586529
http://bugzilla.novell.com/show_bug.cgi?id=586529#c2
Yun-Seok Jang
From our image release to them, Samsung factory usually needs to change/adjust values like Mouse pointer speed, Speaker Volume and etc. Currently these changes will be gone if factory recovery is performed by end user. Samsung want to have these small changes done by them could be reflected after factory recovery process. So Samsung think they need to have a tool that they could change/make/save recovery image by themselves.
I figured Samsung is expecting us to provide/support similar tools/function as Microsoft does. Microsoft support OEM Audit mode. and provide tools like Sysprep, OOBE ( PreOOBE, PostOOBE ), Reseal. Discussed about YaST first boot with Samsung engineers. They want some improvement on YaST 1st boot also. Will " post script " solution solve Samsung request that they currently have? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=586529
http://bugzilla.novell.com/show_bug.cgi?id=586529#c3
Marcus Schaefer
Samsung's factory process is to install the OS using our delivered image, and then make any necessary modifications on the system. Then they clone this hard disk out as an image file, which is sent to their factory for manufacturing. But the problem is they cannot modify the recovery partition, and hence after the system is recovered, their modifications are lost.
If Samsung can store the changes they have done before they deliver the image to the customer in for example a tar file with a specific name and location like: /usr/local/recovery/factory-restore.tgz I could change kiwi's recovery process to pick that file up and make sure the data inside is restored after the recovery is done. I could do that by moving the file into the recovery partition or into a tmpfs. The downside here is that we have a size limitation for the recovery partition and also for RAM. According to your explanation a post script after recovery doesn't help to solve the problem -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com