[02:13] So, I see Nehalem and Nehalem-IBRS cooked into qemu-2.11+dfsg/target/i386/cpu.c. [02:16] I wonder if my host is too old to have CPUID_7_0_EDX_SPEC_CTRL or something. I'm not 100% sure how that works as yet. [02:20] I don't know. I migrate the thing over, and Nehalem-IBRS no longer shows up in the list of possible models, but it does show up as the active CPU model. Weird. [02:20] Oh well. [09:25] mason: those are libvirt specific types [09:26] mason: for qemu that is some-base-cpu+feature-bits [09:26] libvirt does host probing for capabilities, so maybe due to that it differs [09:26] well your question was so many hours ago, did you find anything already? [13:53] Ooh, here's an opportunity to use the memo-bot! === RoyK^ is now known as RoyK === Xbert is now known as Guest41621 [22:47] why am i now getting "kinghat is not in the sudoers file. This incident will be reported." on my server? [22:47] was there a recent update that changed something? never seen this before except for on fedora. [22:56] kinghat: you have changed either the sudoers file, or you're users group membership [23:01] hmm [23:03] i think i added the user to the group `web-content` for apache, would that have done it? [23:03] i thought the user could be apart of multiple groups? [23:04] kinghat: I suspect you've added the user to the group and at the same time removed it from the admin / wheel group [23:04] yes, a user can be a member of many groups [23:04] type "id" against your user [23:04] uid=1000(kinghat) gid=1000(kinghat) groups=1000(kinghat),1001(web-content) [23:04] ya i was just going looking for the commands to get a table of users and groups on the system. [23:09] ikonia: so you are saying i need to get root, then add my user to `sudo` user group? [23:09] what groups is your user in ? [23:09] because i cant add my account via sudo atm because its not part of sudo. [23:10] i posted it above i thought. [23:10] oh yes [23:10] so boot into single user mode and add your user to the sudo group [23:10] single user mode = root? [23:11] what ? [23:11] what is single user mode? [23:11] it boots the user into just that - single user mode, rather than the multi-user mode and permissions system you currently have [23:12] or you can just become root if you've set a root password and know it [23:13] i feel like ive logged into root using the same password as the initial account before w/o having set an actual root password. [23:14] then su - [23:14] ya i just did that and it says su: Authentication failure. [23:14] then you don't know the password [23:15] if anything i made it the same as the initial account. actually i figured thats what the installer did by default. [23:17] nope [23:17] it does what you tell it to do [23:18] so i have to give root a password before i can use root? [23:18] yes [23:18] (the correct model is to not set a root password and have a sane sudo setup) [23:19] sure but how do i get my only user back to sudo then? [23:20] boot into single user mode [23:20] can that be done via ssh? [23:20] possibly, but it normally requires console access as single user mode is not on the network [23:22] why would adding this user to another group take it out of another group? [23:22] depends how you added it [23:22] sudo adduser username groupname [23:22] kinghat: that's creating a new user [23:22] that's not adding a user to a group [23:23] sorry it was this: `usermod -G web-content alice` [23:23] but `kinghat` over alice. [23:24] and i also added apache to that group. [23:24] so that's just told the system to put the user kinghat in the group web-content only [23:24] that's not adding a user to a group, that's setting a user to that single group [23:24] well that explains it [23:24] I suggest you read the man page of commands if you don't know how to use them [23:25] https://wiki.apache.org/httpd/FileSystemPermissions [23:25] ? [23:25] what has that got to do with anything ? [23:25] i feel like there should be a warning or something. are you sure you want to remove this user from all groups? especially the sudo group. [23:25] no [23:26] you should read the man page of commands you don't know about, more so if executing them with root access [23:26] the man page is really clear on the syntax [23:26] well now i have to figure out how to get single user w/o console access. [23:27] what about giving root a password then doing what i need and then removing the password from root? [23:27] I suspect that will be exceptionally hard [23:27] how do you plan to set a root password without having root access ? [23:27] you mean w/o being apart of the sudo group? ya i was just realizing that. [23:28] fak [23:28] please control the languge [23:29] so basically i cant really do anything w/o having physical access? [23:29] you'll find it exceptionally hard [23:29] and high risk [23:30] apparently im high risk. [23:30] what ? [23:31] im the risk. [23:31] clearly [23:31] no direct access makes it just a little complicated [23:35] you have to edit grub? [23:36] that is one of the high risk ways, however if you did it right and it boots into single user mode, how will you interact with it ? [23:38] no im asking thats how you get into single user mode? [23:39] right, there are a few options, but what's the plan if you did get it into single userm ode [23:39] you said add my user to `sudo`? [23:39] how will you do that remote [23:41] i dont have physical access atm but i will have to get physical access apparently so. [23:42] so I'd deal with that when you get access as the access you get / how you get it will guide you the best way to get access to the root user [23:44] i mean i have to go there to get physical keyboard/monitor console access. its going to happen once i figure out how its done before i go. [23:45] aka im going as soon as i figure out how to get single user mode. [23:52] so adding a user to another group and not ONLY this group is: `sudo usermod -a -G sudo username`?