On Wednesday, May 23, 2012, Lennart Poettering wrote: > On Wed, 23.05.12 12:10, Gustavo Sverzut Barbieri > (barbi...@profusion.mobi<javascript:;>) > wrote: > > > >> One suggestion at IRC was to just keep systemd mount units. But if we > > >> should go this route, then we should call to deprecate /etc/fstab. > > >> Last time we discussed about it, people said it was not going to > > >> happen since some tools were parsing and relying on it. Whats is the > > >> way to go? > > > > > > We don't really deprecate it. But if people want to they don't have to > > > use it now, and can do this easily by dropping the file and removing > the > > > generator. > > > > > > You know, fewer PIDs are definitely a good thing, but for some things > > > doing them out-of-process is actually a good thing. Unix knows > processes > > > and process isolation for a reason. > > > > In this case I'm still more for having the fstab parser bultin, > > however I understand your point. > > > > In my usage I'll just drop fstab and see what happens. For sure simple > > "mount /mountpoint" will not work anymore, then I wonder if there is > > any plan to provide systemd-mount to be linked as /bin/mount in order > > to get the mount description (device, point, options) from systemd > > mount units instead of fstab. > > We have that already. It has a slightly different syntax though: > > systemctl start mountpoint.mount >
I know this, but it's not a drop in replacement for the default "mount". Shouldn't be hard, do you think it would be accepted in systemd or better to try to patch default mount to use systemd "sd_booted() -> call it for unit" > Lennart > > -- > Lennart Poettering - Red Hat, Inc. > -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -------------------------------------- MSN: barbi...@gmail.com Skype: gsbarbieri Mobile: +55 (19) 9225-2202
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
