Hi Seth, On Fri, 2013-10-11 at 10:34 -0500, Seth Call wrote: > Ok, I enabled the service again, rebooted, and I'm OK again. I > believe disabling the service disables the kernel module loading, and > if I wanted to manually bring up the service like that, I would have > first needed to bring up the modules. You'll want to make sure that configfs.ko is loaded, and that configfs is mounted via: mount -t configfs configfs /sys/kernel/configfs Even better, include configfs into /etc/fstab so that it's automatically mounted at boot. --nab > > Thanks, > Seth > > On Fri, Oct 11, 2013 at 10:27 AM, Seth Call <sethcall@xxxxxxxxx> wrote: > > I've just started playing with targetcli, and because of zfs bringing > > issues on boot, I tried to disable targetcli by doing this: > > > > sudo update-rc.d target disable > > > > Then, I rebooted my machine, and tried to start target manually: > > > > sudo /etc/init.d/target start > > > > I get this error: > > > > OSError: [Errno 2] No such file or directory: '/sys/kernel/config/target' > > > > I have tried to just add/remove targetcli and lio-utils, but the file > > isn't coming back. I'm not sure how it's created. Any pointers? > > > > Thanks, > > Seth > -- > To unsubscribe from this list: send the line "unsubscribe target-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
