Hey everyone!
So this week I worked on chain loading the scripts to make things
working all good and proper.
(Okay this sounds kinda short, but I started to pick apart all the
scripts in charge of booting - Dracut.
So after I tracked down which one to remove, which one to keep, I
started re-writing my scripts, once again.
Now I have three services, three scripts, in order to have the dialog
displayed, do preparation, and boot the final system.)
Uhm well, today is testing day. Wrote my script that copies everything
written into my Dropbox folder
(so I can keep my changes saved all the time), and will move the scripts
to my pendrive and give it a go.
Well, that's it for this week.
Meanwhile I also kept my quickblog up-to-date (which I haven't posted
here yet, but I will do later on.)
Good luck for everyone!
Regards,
Peter
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hello Community,
This week I started with email notifications. James said the listed 5
notifications
* Notify all participants when Conference dates/Registration dates are
updated.Highlight dates.
* Notify all participants when venue is changed.Highlight address and
Venue name.
* Notify all participants when a supporter level added.Also to notify,
when the price of the supporter level in changed.
* Notify all participants when Call for papers dates are added/updated.
* Notify all participants when the schedule is made public.
are good to go.So I completed the first and the second, both are in
pipeline and is not merged yet.The other thing I thought while
implementing is that it takes lot of time to send email to
participants in the middle of updating the conference for the first
(say).So sending emails while updating data is a really bad idea, so I
thought of putting these in the background jobs, well in layman terms
Queue them to get processed later so that the UX is not hampered.
I thought of using https://github.com/collectiveidea/delayed_job . But
using this didn't seem to worked well.The emails are getting delivered
without using the gem and on using it is throwing errors. So major
time went on fixing this and still I am not been to fix this issue.I
worked with James and it figured out that for new emails I should
first write tests and then reproduce the error that I got with
delated_jobs on specs.
So probably, I try to finish email notifications with the gem.Well,
that's all this week.
Happy Hacking!!! :)
Gopesh Tulsyan
ROR Enthusiast,
Final Year Information Technology,
National Institute of Technology, Durgapur
On Sat, Jul 5, 2014 at 11:56 PM, Gopesh Tulsyan <gopesh.7500(a)gmail.com> wrote:
> Hello Community,
> This week I finished the remaining components: Gallery and Footer and
> added Markdown for description fields that are rendered in the
> splash.The gallery is designed such that the splash page load is not
> affected.When the user clicks the "Gallery" button for the first time,
> the photos are loaded in a modal with the carousel via AJAX.After that
> for preceding clicks only the modal is invoked, until the page is
> refreshed. I did this by keeping a countdown variable in Javascript.
>
> For the footer I just made a up-arrow button which is displayed when
> the user scrolls down length of 100px.On clicking the button the user
> is taken to the topmost component, i,e the banner via smoothscroll.So
> the navigation and UX is built properly by using animation, tabs on
> the header and a button at the footer.
>
> I implemented markdown for only description fields that are rendered
> directly on to the splash.I did this using redcarpet gem and also
> added bootstrap-markdown(toopay) editor for description fields so that
> easily markdown tags are added by click without any hassle.
>
> Next week, I will start with email notifications.I have listed some
> notifications on my Trello board as suggested by James, to keep track
> of things.I still has to discuss what notifications are relevant to
> be sent.
>
> Well thats it!! for this week.
> Happy Hacking!!
> Gopesh Tulsyan
> ROR Enthusiast,
> Final Year Information Technology,
> National Institute of Technology, Durgapur
>
>
> On Sat, Jun 28, 2014 at 11:12 PM, Gopesh Tulsyan <gopesh.7500(a)gmail.com> wrote:
>> Hello Community,
>> I happy to say that I passed my mid-term evaluations, thank you for
>> the support and guidance so far.
>>
>> This week I integrated a theme inspired by onassis of
>> http://www.blacktie.co(licensehttp://www.blacktie.co/about-themes/).
>> I also integrated FontAwesome(license
>> http://fortawesome.github.io/Font-Awesome/license/) and smoothscroll
>> for better effects and animation for the splash.Although I am open any
>> kind of addition to view level be it animations, assets, layouts.My
>> mentor said that theme would be generally changed by the admins using
>> OSEM, so I wrote only one css file for the time being, if time is left
>> I can write one more theme for the splash.
>>
>> So I am left with three components(Press, Footer and Gallery) which I
>> will finish and push next week and as per my proposal I would be
>> working on Email Notifications. The email notifications needs
>> attention because whenever a conference is updated there is no check
>> which part is updated and the participants are not informed about the
>> update which is very essential.
>>
>> This is the link to the folder Week 6, which contains some snaps with
>> theme implemented.
>>
>> https://drive.google.com/folderview?id=0B8TQsfyoffN5cWNPaUU1OE1UWms&usp=sha…
>>
>> Happy Hacking :)
>>
>> Gopesh Tulsyan
>> ROR Enthusiast,
>> Final Year Information Technology,
>> National Institute of Technology, Durgapur
>>
>>
>> On Sat, Jun 21, 2014 at 4:41 PM, Gopesh Tulsyan <gopesh.7500(a)gmail.com> wrote:
>>>
>>> Hello Community,
>>> This week I completed the Location component with lodgings and added a
>>> banner component to the splash.This banner component is in place of
>>> carousel, it contains a background image, conference title, start-end
>>> dates and description.
>>>
>>> I also added the checkboxes for each component in admin dashboard as
>>> decided previous week, so that admins/organizer now can enable the
>>> component on the splash when they think it's completed.On a different
>>> note, we locked down on the carousel to be implemented as gallery in a
>>> lightbox.This enabled me to use the carousel code that I have written
>>> for taking photos for carousel. Only thing I have to do for gallery is
>>> to make the frontend the backend code for taking photos form the admin
>>> dashboard is merged.
>>>
>>> Next week is mid-term evaluation.Next, I will implement some styling
>>> onto the splash as decided by James.This won't take much time as I
>>> have to implement styling by looking at the themes.However, James and
>>> I decided that I will next improvise the email notifications as
>>> mentioned in my proposal.The email notifications have to implemented
>>> in a way so that the Users attending the Conference are aware about
>>> each and every update that the admins make to the conference and these
>>> mails will be fired by the admins explicitly.
>>>
>>> Some snaps of the splash page with test data are attatched.
>>>
>>> Google Drive link to the folder ----> Splash till Mid-Term(folder name)Week 5
>>> https://drive.google.com/folderview?id=0B8TQsfyoffN5UF8yMno4S3ZvTTg&usp=sha…
>>>
>>> Happy Hacking!!
>>>
>>> Gopesh Tulsyan
>>> ROR Enthusiast,
>>> 3rd Year Information Technology,
>>> National Institute of Technology, Durgapur
>>>
>>>
>>> On Sat, Jun 14, 2014 at 9:34 AM, Gopesh Tulsyan <gopesh.7500(a)gmail.com> wrote:
>>> > Hello Community,
>>> > This week was less work and more review.My mentor was not well so I
>>> > got my components reviewed later this week.However, the Sponsor and
>>> > Social Media components are merged now.I need to little refactoring
>>> > with with Location component and that will be merged too.
>>> >
>>> > Well I did the carousel component but Henne said that carousel are
>>> > useless so indeed we decided to have fold as in
>>> > https://conference.opensuse.org/index.html#home.
>>> > and we discussed here
>>> > https://github.com/openSUSE/osem/pull/222.
>>> >
>>> > So on discussing with James I have to redo this component again.
>>> >
>>> > Next Week Plans:
>>> > Right now there is no admin check on the components like whenever the
>>> > data for components are entered in the admin dashboard for the
>>> > conference they are rendered.So I will go ahead and create checkboxes
>>> > for each and every component so that the components are only visible
>>> > in the splash when the admin/organizers wants them to be displayed.
>>> >
>>> > Happy Hacking!!
>>> > Gopesh Tulsyan
>>> > ROR Enthusiast,
>>> > 3rd Year Information Technology,
>>> > National Institute of Technology, Durgapur
>>> >
>>> >
>>> > On Sat, Jun 7, 2014 at 9:54 AM, Gopesh Tulsyan <gopesh.7500(a)gmail.com> wrote:
>>> >> Hello Community,
>>> >>
>>> >> This week I completed the remaining components namely Sponsors, Social
>>> >> Media, Location with Lodging.The sponsor component involved in
>>> >> building a dashboard which was is currently absent in OSEM. Similarly,
>>> >> lodging component involves building a lodging dashboard under Venue
>>> >> section.The social media involved addition of fields in conference
>>> >> section to take urls for the conference in different social media like
>>> >> Google+, Twitter and Facebook.
>>> >> I built these components in pieces so that my commits are atomic,
>>> >> following the coding style suggested by James.
>>> >>
>>> >> These components are currently in review, once reviewed and merged I
>>> >> will focus on the style and theme integration.
>>> >>
>>> >> That's all this week. Happy Hacking!
>>> >>
>>> >> Gopesh Tulsyan
>>> >> ROR Enthusiast,
>>> >> 3rd Year Information Technology,
>>> >> National Institute of Technology, Durgapur
>>> >>
>>> >>
>>> >> On Sat, Jun 7, 2014 at 9:46 AM, Gopesh Tulsyan <gopesh.7500(a)gmail.com> wrote:
>>> >>>
>>> >>> Hello Community,
>>> >>>
>>> >>> This week I completed the remaining components namely Sponsors, Social Media, Location with Lodging.The sponsor component involved in building a dashboard which was is currently absent in OSEM. Similarly, lodging component involves building a lodging dashboard under Venue section.The social media involved addition of fields in conference section to take urls for the conference in different social media like Google+, Twitter and Facebook.
>>> >>> I built these components in pieces so that my commits are atomic, following the coding style suggested by James.
>>> >>>
>>> >>> These components are currently in review, once reviewed and merged I will focus on the style and theme integration.
>>> >>>
>>> >>> That's all this week. Happy Hacking!
>>> >>>
>>> >>> Gopesh Tulsyan
>>> >>> ROR Enthusiast,
>>> >>> 3rd Year Information Technology,
>>> >>> National Institute of Technology, Durgapur
>>> >>>
>>> >>>
>>> >>> On Sat, May 31, 2014 at 2:09 PM, Gopesh Tulsyan <gopesh.7500(a)gmail.com> wrote:
>>> >>>>
>>> >>>> Hello Community,
>>> >>>> This week my previously built components were reviewed by the OSEM
>>> >>>> maintainer Henne and my mentors James & Cornelius. James pointed out
>>> >>>> my mistakes I had done while coding those components.I had built these
>>> >>>> segments in a way that was hard to review, as well as my code was
>>> >>>> redundant as I was doing lot of compound work. So James thought me to
>>> >>>> do cherry-pick commits(for those pieces which I require in multiple
>>> >>>> components and which is not yet merged), so that my commits are more
>>> >>>> granular and atomic.Out of the five components Sponsors is still
>>> >>>> pending to reviewed, but the rest four(Header, Program, Registration,
>>> >>>> Cfp) are merged now. I did the components again in small patches which
>>> >>>> was easily reviewed and was merged.
>>> >>>>
>>> >>>>
>>> >>>> So I faced problems this week in understanding the procedure to code
>>> >>>> in a way that is accepted.My logic was clear, but I was not following
>>> >>>> the norms due to which I had to redo my work. I am still working on
>>> >>>> the coding style suggested by James.
>>> >>>>
>>> >>>> Since the larger chunks are over I plan to complete the remaining five
>>> >>>> segments the upcoming week, so the structure of the splash page with
>>> >>>> all the data is in place.And to test the splash page with test data so
>>> >>>> that it doesn't break in any possible case.
>>> >>>>
>>> >>>> That's all this week, my progress on OSEM can be found in
>>> >>>> https://github.com/gopesht/osem .Here's the link to drive folder
>>> >>>>
>>> >>>> OSEM Event Splash Page for Visitors Week 2 updates snaps ->
>>> >>>> https://drive.google.com/folderview?id=0B8TQsfyoffN5emVsNzAzV1VVZFE&usp=sha…
>>> >>>>
>>> >>>> Happy Hacking!!
>>> >>>>
>>> >>>> Gopesh Tulsyan
>>> >>>> ROR Enthusiast,
>>> >>>> 3rd Year Information Technology,
>>> >>>> National Institute of Technology, Durgapur
>>> >>>>
>>> >>>>
>>> >>>> On Sat, May 24, 2014 at 12:52 PM, Gopesh Tulsyan <gopesh.7500(a)gmail.com> wrote:
>>> >>>> >
>>> >>>> > Hello Community,
>>> >>>> > This week I had built three components namely Program component, Call
>>> >>>> > for Papers component and Registration component for the splash page. I
>>> >>>> > had built these components as a whole, both the frontend and
>>> >>>> > backend.Migrations for the missing attributes are done for the proper
>>> >>>> > display of these components.These components are designed with
>>> >>>> > conditional rendering of attributes so that the splash doesn't break
>>> >>>> > if one or more attributes are blank.
>>> >>>> >
>>> >>>> > What I intentded to do this week according to my proposal ->
>>> >>>> > Create models and associations, and decide what all can be given to
>>> >>>> > the admin to customize the splash page apart from the things discussed
>>> >>>> > above.Test with one sample conference how things are working.
>>> >>>> >
>>> >>>> > So the initial base is setup, the features(components are already
>>> >>>> > decided and it in the trello board as told by my mentor james).The
>>> >>>> > backend modeling are being done simultaneously as I will build these
>>> >>>> > components.
>>> >>>> >
>>> >>>> > Though I had this components, but they are still in review. I will
>>> >>>> > make suggested changes as will be told by my mentors James &
>>> >>>> > Cornelius.
>>> >>>> > Also as James suggested to built the structure of the components with
>>> >>>> > plain and simple layout, rather than focussing on styling and looks.
>>> >>>> > As when the data will be in place with the desired components, then I
>>> >>>> > will intregrate some themes to beautify the splash page.
>>> >>>> >
>>> >>>> > What I intent to do next week->
>>> >>>> > Currently, the sponsor dashboard is missing, and we require the
>>> >>>> > sponsor component for the splash.So I will first built the sponsor
>>> >>>> > dashboard with the modeling suggested by James.After that I will go
>>> >>>> > ahead and build the remaining components in the trello board.
>>> >>>> >
>>> >>>> > Happy Hacking!
>>> >>>> >
>>> >>>> > Gopesh Tulsyan
>>> >>>> > ROR Enthusiast,
>>> >>>> > 3rd Year Information Technology,
>>> >>>> > National Institute of Technology, Durgapur
>>> >>>> >
>>> >>>> >
>>> >>>> > On Sat, May 17, 2014 at 8:28 AM, Gopesh Tulsyan <gopesh.7500(a)gmail.com> wrote:
>>> >>>> > > Hello,
>>> >>>> > > This week I learnt testing, some basics and written controller test
>>> >>>> > > for admin/users, feature test for users, volunteers.I will be writing
>>> >>>> > > more tests for views as suggested my mentor James Mason.He tells
>>> >>>> > > writing view specs will make me implement my features better.I had
>>> >>>> > > also fixed bugs while testing like modal view in admin/users page,
>>> >>>> > > display users in admin/users page, fix attachment for proposals.
>>> >>>> > > I also reviewed and and added navigation for event splash page(initial kick-off)
>>> >>>> > > Tasks for the next week ->
>>> >>>> > > Write view specs, and start building components as mentioned in trello
>>> >>>> > > board for my GSoC project.
>>> >>>> > >
>>> >>>> > > Happy Hacking!
>>> >>>> > > Gopesh Tulsyan
>>> >>>> > > ROR Enthusiast,
>>> >>>> > > 3rd Year Information Technology,
>>> >>>> > > National Institute of Technology, Durgapur
>>> >>>> > >
>>> >>>> > >
>>> >>>> > > On Fri, May 9, 2014 at 9:04 PM, Gopesh Tulsyan <gopesh.7500(a)gmail.com> wrote:
>>> >>>> > >> I recently pushed a commit to kick start my GSoC project.The commit
>>> >>>> > >> consisted of a view displaying just the title of the conference.This
>>> >>>> > >> is the result of clicking the event on the home page.
>>> >>>> > >>
>>> >>>> > >> I had also setup the trello board where James assigned tasks to me such as
>>> >>>> > >> 1) Read the Ruby on Rails Guidelines for selected topics.
>>> >>>> > >> 2) Asked me to see 20 splash pages and figure out the components to
>>> >>>> > >> create a list for the OSEM splash page.
>>> >>>> > >>
>>> >>>> > >> Currently, I am done with the listing of the components and waiting
>>> >>>> > >> for the review.I am continuing with the guides.
>>> >>>> > >>
>>> >>>> > >> Looking forward to a great summers ahead.
>>> >>>> > >>
>>> >>>> > >> Happy Hacking!
>>> >>>> > >> Gopesh Tulsyan
>>> >>>> > >> ROR Enthusiast,
>>> >>>> > >> 3rd Year Information Technology,
>>> >>>> > >> National Institute of Technology, Durgapur
>>> >>>
>>> >>>
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hello everyone,
This is a brief summary of my progress last week.
There were 2 primary objectives i.e.
1) implement a validation to ensure that requests cannot be submitted
with empty expenses and write a spec to test the same
2) move the implementation of dynamic code to a method which can be
accordingly invoked upon update and create actions
The code for the first objective is completed and tested as well. For
the second objective, I have been able to identify the spots where the
method needs to be invoked and tested for one particular case. I will
implement the same for remaining places after getting some suggestions
about it from my mentor.
Thank You
Karthik.S
2nd Year,Information Technology
NITK,Surathkal
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi,
this is my eleventh weekly status report for my GSoc project.
This week I continued working on MATE volume control application as well
as libmatemixer. I have decided to dig a little deeper into the
application, clean up the code, rewrite a few parts and fix problems
related to an unfinished GTK3 port. This turns out to be a large amount
of work, but I think the extra spent time is well worth. There have also
been many fixes to both the application and libmatemixer and
libmatemixer gained support for accessing PulseAudio stream database,
which is needed for the application to provide event volume control and
move streams to different devices.
At this moment all the previous functionality of the application is
restored and the code is in a much better shape than before. There is
still some work left, but I intend to finish it within a couple of days.
After that I'd like to engage more people to test the application and
get back to working on libmatemixer.
Thank you,
Michal
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hello to everyone. It was recommended to me by someone who works with
openSUSE to join this mailing list and introduce myself since I am
very interested in getting involved again with a Linux/open source
project.
My name is Lee Ward. I previously worked with the Fuduntu Linux
project a couple years ago and was in charge of communications/public
relations and was in charge of managing all the social media,
interviews, and press releases. Additionally, I worked with packaging,
testing, and supporting end users. I have a little programming
knowledge and about intermediate understanding of administration, etc.
of Linux. I've been using Linux since 1998 and SuSE was one of the
first distros I used.
As I stated above, I am very interested in getting involved again with
a Linux or other open source project. Towards the end of the Fuduntu
distro, I was working closely with some openSUSE team members as some
of us were looking at our options of moving forward within the Linux
community. The experience was one of the best ones I ever had with a
project and is why openSUSE was my first thought now that I'm ready to
get my hands dirty again.
I'm not really sure who to talk to or where to go from here on getting
involved and that was why someone with the distro team told me to make
an introduction in hopes that perhaps someone else can help me get
steered in the right direction. Thank you very much and I look forward
to the opportunity to work with openSUSE.
Lee Ward
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
On Wed, Jul 9, 2014 at 11:47 AM, Shawn W Dunn
<sfalken(a)cloverleaf-linux.org> wrote:
> Sure, now you crawl out from under your rock =p
Hey! How's it going? I had to take a step away after everything. I
needed some breathing room and a little break. Then, I realized how
much I miss working on this stuff and I remember how well things went
with our interactions with openSUSE and it was a no-brainer about who
to start talking to.
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Sure, now you crawl out from under your rock =p
On Jul 9, 2014 5:43 AM, Lee Ward <leeward1982(a)gmail.com> wrote:
>
> Hello to everyone. It was recommended to me by someone who works with
> openSUSE to join this mailing list and introduce myself since I am
> very interested in getting involved again with a Linux/open source
> project.
>
> My name is Lee Ward. I previously worked with the Fuduntu Linux
> project a couple years ago and was in charge of communications/public
> relations and was in charge of managing all the social media,
> interviews, and press releases. Additionally, I worked with packaging,
> testing, and supporting end users. I have a little programming
> knowledge and about intermediate understanding of administration, etc.
> of Linux. I've been using Linux since 1998 and SuSE was one of the
> first distros I used.
>
> As I stated above, I am very interested in getting involved again with
> a Linux or other open source project. Towards the end of the Fuduntu
> distro, I was working closely with some openSUSE team members as some
> of us were looking at our options of moving forward within the Linux
> community. The experience was one of the best ones I ever had with a
> project and is why openSUSE was my first thought now that I'm ready to
> get my hands dirty again.
>
> I'm not really sure who to talk to or where to go from here on getting
> involved and that was why someone with the distro team told me to make
> an introduction in hopes that perhaps someone else can help me get
> steered in the right direction. Thank you very much and I look forward
> to the opportunity to work with openSUSE.
>
> Lee Ward
> --
> To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
> To contact the owner, email: opensuse-project+owner(a)opensuse.org
>
Hi all, below are the minutes from todays IRC Project Meeting
Review of Action Items from the Last Meeting
---
Sources for the new openSUSE Marketing Materials are temporarily
available at https://github.com/sysrich/opensuse-newbrandguidelines
Kenneth and Zvezdana are still working on a new website which will
provide these materials along with guidences on fonts, colours, etc.
Discussions are ongoing in opensuse-artwork(a)opensuse.org, feel free to
join the conversation
ACTION: Henne to help Richard setup the website for the marketing
materials/guidelines once they're completed
GSoC Status
---
Great News! - All GSoC participants passed their mid term evaluations
Past issues with Mentor Stipends + Travel Payments all cleared up. Manu
and Dominik are expected to attend the Mentors Summit on behalf of
openSUSE
Booth Boxes/Events
---
We've still got plenty of Booth Boxes just waiting for people to use
them to represent openSUSE at events.
If you're going to a FOSS event around the world and would like to
represent openSUSE, we'd love to hear from you and ship all the
materials you'll need to make a real splash
The openSUSE Team have put together a great application for processing
requests, but we'd like to make sure it works, so please contact
board(a)opensuse.org to let us know and we'll talk you through the process
The next event we're likely to be at is GUADEC at the end of this month.
If you're going and willing to help at an openSUSE booth there, please
contact rbrownccb(a)opensuse.org
We're also going to have an openSUSE Summit in Bejing
It's website is live! http://summit.opensuse.org
Next meeting date
----
The next openSUSE Project IRC meeting will be 15:00 UTC on 23rd July, in
#opensuse-project on irc.freenode.org as usual. See you there!
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hi there,
As I said last time the goals of the project changed slightly because
there was not a lot of enthusiasm by xen developers on snapshot
support in xen so after the patch I wrote for libvirt I moved on and I
am now writing a xen-xl parser for libvirt.
This week I refactored the code in xen_xm.c as I want to reuse.
Reading directly from the diff, here is what I have:
For the function xenParseXM, I split it into
xenParseXMGeneral; parse the general configs such as
uuid, OS type etc, tagged for reuse.
xenParseXMMem; parses memory configuration options,
tagged for reuse in the xen-xl parser.
xenParseXMVif ;parses the virtual frame-buffer
configuration, I will also reuse this one.
xenParseXMDisk ; parse the disk configuration but this
will have to be redone.
xenParseXMPCI; parses the pci devices config, I will
reuse this at first but I will redo it latter.
xenParseXMSerial; parses the serial devices config,
also to be reused.
xenParseXMActions; parses the actions the take place at
certain events, that is power_off, c
xenParseXMCPU ; parses the cpu allocation, also to be reused.
xenParseXMOS ; parses the OS config options for HVM and
paravirtualized domains.
xenParseXMVif ;parse the xm network configuration but
will have to be redone.
For the function xenFormatXM, I split it into a similar set of functions.
Next week, I move to the xen-xl parser where I will start by writing
the missing functions such as xenParseXLDisk and xenParseXLVif.I will
also write xenParseXLGraphicsSplice for latter use.
Regards,
David.
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org
Hello everyone!
This week I spent my time with crafting my scripts and making the boot
pretty.
Pretty as in, work normally. Because so far I used a trick (rd.break,
anyone?) to get things up.
Taming Dracut is not the easiest thing, if you have no former experience
doing so.
But I managed to dig through all the modules scripts now (literally, all
of them),
and now I'm working on the correct way of injecting our system into it.
A bulleted list with a somewhat accurate timeline:
- Made a quick blog, so my mentor can follow my progress much easier.
It's also good for me to backtrack my process a lot easier.
- Fixed up the CLF system script, so it mounts up 'modules'. Basically
squashfs files, which can contain software, or modules, for example.
Currently it's used to update the image's modules.
- Fixed up the scripts so they would chainload perfectly. The system
gets mounted flawless after the user selects his image of choice.
- Learned a ton about Dracut again. One such thing was it's conf and
switches. How they behave.
- Spent a ton of time with pivot_root, switch_root and the like (manual
mount).
Because pivot_root and switch_root would fail miserably at boot.
Michal (my mentor) had a great idea. The default mount point and a
clean exit booted up the new system.
This took me to the right track.
- 'exec' fooled me great at debugging. ;_;
- Learned how to use expect, where to execute it. Not sure if we will
need it in the final version without breaks...
But expect is so powerful, it may come in handy later on.
- Debugging, debugging, debugging.
So CLF is at the stage where automagic is being worked on.
Mount is done = booting, working system.
I need to add syslinux to the equation and it's a thing people could
already install on a pendrive.
(Of course, we are far from the final goals, as there are so many things
I could improve,
and so many things I could implement, even if the basics are done. Which
is not the case at the moment,
so yeah.)
Thanks to the quickblog, expect lenghtier reports from now on.
(I did work a lot before as well, but I just summed things up real fast
each week.)
Regards,
Peter
--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
To contact the owner, email: opensuse-project+owner(a)opensuse.org