# equo cleanup
# equo update
# equo upgrade
# equo conf update
# equo libtest
# equo deptest
shade304 wrote:It was installed from an older sabayon disk and somewhere along the way converted from /etc/initd to the new system d.
shade304 wrote:So I abandoned that computer all together and switched to my laptop, no problems until one day on reboot it give the prompt to "Ctl D" to continue or login, of course Ctl D doesn't work, but luckily I was able to log in. Tracing back to what changes happened I had added 2 lines to /etc/fstab I was looking in all kinds of places for systemd errors but it never occurred to me to look in fstab! The lines in question:
192.168.1.10:/export/My-Company /media/My\040Company nfs rw,soft,rsize=32768,wsize=32768,intr 0 0
/media/My\040Company/Pictures /home/myuser/Pictures/ none bind 0 0
#192.168.1.10:/export/My-Company /media/My\040Company nfs rw,soft,rsize=32768,wsize=32768,intr 0 0
#/media/My\040Company/Pictures /home/myuser/Pictures/ none bind 0 0
and everything works fine, except that after every startup I need to edit those out, and mount -a then put them back.. I little bit of a hassle..
Is it breaking because of the spaces? What scripts are handling fstab? It seams like it might dynamically generate systemd scripts based on the content, but it scrolls so fast that might not be accurate, any information would be appreciated.
# crontab -e
@reboot sleep 30 ; mount <your_nfs_mount_point> && mount <your_bind_mount_point>
@reboot sleep 30 ; mount /media/My\040Company && mount /home/myuser/Pictures/
Users browsing this forum: No registered users and 1 guest