It seems like it would work for normal services but logging and udev are pretty integrated. They are listed as static services and many services depend them. It doesn't seem that trivial. Thanks

On Jun 30, 2013 8:46 PM, "Akram Hameed" <akramh@aq1systems.com> wrote:
Howdy,

I'm learning a fair bit about systemd myself. I am sure you could probably dig in to where the *.service files are kept, but you can disable services using systemctl IIRC:

systemctl disable servicename.service

Not sure if that persists (can't test right this minute) over a reboot, but one would assume so.

Service files are stashed someplace like /lib/systemd/system

Cheers,

Akram


On Sat, Jun 29, 2013 at 6:19 AM, dtran11 <dtran11@gmail.com> wrote:
Hi I am currently using Yocto (danny) for my overo. I would like to disable
stuff from systemd to make things boot faster (disable system logging, udev,
etc..). Has anyone done this before with systemd? I have been able to do it
before with the old init.d but systemd seems to be very integrated with udev
and logging.

Thanks



--
View this message in context: http://gumstix.8.x6.nabble.com/Systemd-optimization-tp4967465.html
Sent from the Gumstix mailing list archive at Nabble.com.

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
gumstix-users mailing list
gumstix-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gumstix-users


------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
gumstix-users mailing list
gumstix-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gumstix-users