Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][tlug] Root account (was: Accessing microphone)
- Date: Tue, 09 May 2006 08:56:59 +0900
- From: Dave M G <martin@example.com>
- Subject: [tlug] Root account (was: Accessing microphone)
- References: <445EF3D6.9000507@example.com> <d8fcc0800605080038q636dd6cen59e7a4dd12c73e38@example.com> <445F0489.3010400@example.com> <20060508111314.365bede2.godwin.stewart@example.com> <445F23F2.30408@example.com> <d8fcc0800605080437i494e9d6fh1bc97f801f94e6dc@example.com> <445F35AB.2040800@example.com> <20060508143247.bcf3ae40.godwin.stewart@example.com> <20060508133934.GA30878@example.com> <20060508162442.a6fe63ec.godwin.stewart@example.com> <20060508144214.GA49717@example.com> <87wtcwmozm.fsf@example.com>
- User-agent: Mail/News 1.5 (X11/20060309)
(Apologies if this hits the list twice. I think there was an error when sending earlier. In any case, I've edited slightly with new details)Godwin, Stephen, Scott,I'm not sure what the confusion here is. I can get into a root account. I've done it at least three different ways:sudo su - sudo -s PATH=$PATH:/sbin:/usr/sbin sudo -sI have been getting a root account since it was first mentioned here and I've shown the output.If you look at my command prompt, it says root, and it has a '#' at the prompt, like a root account should:root@example.com:~#My question would be, if the above *isn't* the root account you've been wanting me to access, then what is it?But that hasn't changed the fact that, when in a root account or otherwise, it could not find the command you guys are recommending:root@example.com:/usr/sbin# generate-modprobe.conf > /etc/modprobe.conf bash: generate-modprobe.conf: command not found However, using locate, I found the following: dave@example.com:~$ locate generate-modprobe /usr/share/doc/module-init-tools/examples/generate-modprobe.conf.gzActually, that came up in the output I showed before, but I thought nothing of it at the time. Then I hunted around on the web, and this seems to be a gzipped version of the script you guys are saying I should use.So I unzipped it, moved it to /usr/sbin, and made it executable with sudo chmod +x.Then I went back into the thread and tried the command that Godwin said I should use in the first place, before this whole confusion about root users started:dave@example.com:~$ sudo generate-modprobe.conf > /etc/modprobe.confThis ran without any kind of error or any other output. Nothing seemed to change, so I rebooted.Still nothing.However, in my other posting, after the kernel upgraded, I got sound back. So I guess that's where the focus should go.-- Dave M G
- Follow-Ups:
- Re: [tlug] Root account
- From: Stephen J. Turnbull
- References:
- Re: [tlug] Accessing microphone
- From: Dave M G
- Re: [tlug] Accessing microphone
- From: Josh Glover
- Re: [tlug] Accessing microphone
- From: Dave M G
- Re: [tlug] Accessing microphone
- From: Godwin Stewart
- Re: [tlug] Accessing microphone
- From: Dave M G
- Re: [tlug] Accessing microphone
- From: Josh Glover
- Re: [tlug] Accessing microphone
- From: Dave M G
- Re: [tlug] Accessing microphone
- From: Godwin Stewart
- Re: [tlug] Accessing microphone
- From: Scott Robbins
- Re: [tlug] Accessing microphone
- From: Godwin Stewart
- Re: [tlug] Accessing microphone
- From: Scott Robbins
- Re: [tlug] Accessing microphone
- From: Stephen J. Turnbull
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] Accessing microphone (back to actual microphone issues)
- Next by Date: Re: [tlug] Accessing microphone (back to actual microphone issues)
- Previous by thread: Re: [tlug] Accessing microphone
- Next by thread: Re: [tlug] Root account
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links