Mailinglist Archive: opensuse (982 mails)

< Previous Next >
Re: [opensuse] Getting rid of systemd and putting sysv back
On Sun, Sep 28, 2014 at 03:34:46AM -0300, Cristian Rodríguez wrote:
El 28/09/14 a las #4, Ruben Safir escribió:
On Sat, Sep 27, 2014 at 05:14:20PM -0700, Sam M. wrote:
Dirk you should probably take your Seroquel before writing to this
list; you not only come across as a complete out of touch with reality
moron but as somebody who's in great need of psychiatric care.




Explain why mount is able to mount files systems without some retarded
other database, but systemd is too stupid to just call for mount?


It calls mount.. but that's not the point..

There is no database, only mount units..in the case of fstab the are
used only internally be systemd ..why?


Does this sentence make sence to you? What are you saying? It clearly
says that the entries in fstab are used to make 'mount units' and that
is only if there is an fstab.


In the case of fstab they are used...?

fstab is a text file. It doesn't use ANYTHING. It is read by init and
mount in order to control their behavior.

because it has to know in
what order to umount them

init systems don't need to unmount anything but the boot image
sometimes.


and interact properly with either system
or user provided service units that need certain mount points
available, or start after, before, etc they are available.



That is NOT the role of an initiation system.


Now, it is a database it created. It is a database of mount points with
further
instructions and other crap. If this in binary so that it is 'secure'?

Guess what. fstab also has an order. and no, it doesn't need to know
if users need mounts and when they need mounts or for what purpose.

It just needs to to store information so that the machine can BOOT
and then mount all mount pointed listed in fstab, low and behold in
the order they are listed.

It does not need to 'interact'. If just needs to do what I tell it to do. It
doesn't need
to guess. It doesn't need to prioritize. It certainly doesn't have to
guess wrong. It doesn't need to start NFS or SAMBA or even mail or cron.

It just needs to mount the partitions that I list in fstab. It doesn't
need to think for me. It just has to do what I tell it to.

As it is, you guys have destroyed the mount command with the same kind of
chatter that ticked off Linus when he was discussing kernel debugging.

Look at all this crap in the output now:

ruben@workstation:~> mount
devtmpfs on /dev type devtmpfs
(rw,relatime,size=943908k,nr_inodes=235977,mode=755)
tmpfs on /dev/shm type tmpfs (rw,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
/dev/sda2 on / type ext4 (rw,relatime,data=ordered)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
securityfs on /sys/kernel/security type securityfs
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup
(rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup
(rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
cgroup on /sys/fs/cgroup/memory type cgroup
(rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup
(rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup
(rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/blkio type cgroup
(rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup
(rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/hugetlb type cgroup
(rw,nosuid,nodev,noexec,relatime,hugetlb)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs
(rw,relatime,fd=27,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
tmpfs on /var/lock type tmpfs (rw,nosuid,nodev,relatime,mode=755)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
tmpfs on /var/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
/dev/sda4 on /home type ext4 (rw,relatime,data=ordered)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse
(rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
gvfsd-fuse on /var/run/user/1000/gvfs type fuse.gvfsd-fuse
(rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
stat11:/home/ruben/ on /home/ruben/laptop type fuse.sshfs
(rw,nosuid,nodev,relatime,user_id=1000,group_id=100)


What are you NUTS? This is my little workstation. It should just say
this:

/dev/sda2 on / type ext4 (rw,relatime,data=ordered)
/dev/sda4 on /home type ext4 (rw,relatime,data=ordered)
stat11:/home/ruben/ on /home/ruben/laptop type fuse.sshfs
(rw,nosuid,nodev,relatime,user_id=1000,group_id=100)



These coders have completely lost their marbles.

I have no CLUE why anything is being mounted any longer or where it is
being mounted. It is a run away frieght train.









--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

--
So many immigrant groups have swept through our town
that Brooklyn, like Atlantis, reaches mythological
proportions in the mind of the world - RI Safir 1998
http://www.mrbrklyn.com

DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002
http://www.nylxs.com - Leadership Development in Free Software
http://www2.mrbrklyn.com/resources - Unpublished Archive
http://www.coinhangout.com - coins!
http://www.brooklyn-living.com

Being so tracked is for FARM ANIMALS and and extermination camps,
but incompatible with living as a free human being. -RI Safir 2013

--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >
This Thread
Follow Ups