Re: On what is helpful and what is not [was: Re: Wifi]

[Ralf Mardorf]

On Sun, 2014-03-16 at 13:05 +1100, Zenaan Harkness wrote:
> (Also as a reminder to self:) Please refer to offtopic list rather
> than bog down debian-user. Thanks Ralph for pointing me at o-t list.
> Apologies for raising this non-technical issue on d-u.
> Zenaan

For those who don't know the OT list:

http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1394950696.9232.28.camel@archlinux

Re: .Xresources not loading on start

[Anubhav Yadav]

Solved.

I edited the file /etc/X11/Xsession.d/30x11-common_xresources and
changed the "xorg -merge ..." lines to "xorge ..." and it worked.
I don't know if it is a good solution or not!


Regards,
Anubhav Yadav
Imperial College of Engineering and Research,
Pune.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/ca+jf9ah0pe1eq+krgvgzmabfv+cy4eeguz_zsef2waymgeo...@mail.gmail.com

Re: [Resolved] Re: When fogetting assigned login name rather than password

[Paul E Condon]

On 20140315_090852, Richard Owlett wrote:
> Scott Ferguson wrote:
> >On 15/03/14 22:29, Tom Furie wrote:
> >>On Sat, Mar 15, 2014 at 10:09:33PM +1100, Scott Ferguson wrote:
> >>>On 15/03/14 21:45, Richard Owlett wrote:
> >>
> If another OS had not been available but I knew the root
> password, is there some way I could have gained access as
> root?
> >>
> >>># passwd `grep 1000 /etc/passwd | cut -d : -f1`
> >>
> >>That doesn't help him until he's logged into the system.
> >
> >Richard has clearly said "if I knew the root password" "as root"
> >So he *can* login to the system.
> >Why he didn't, is the question. ;)
> >
> >Perhaps he tried from a GUI login which only permitted a userlogin
> >(but didn't prompt with the username and didn't, or couldn't
> >(Crtl+backspace etc) didn't work - still wouldn't explain why he
> >didn't just boot into the rescue console. Perhaps his fu was low?
> >
> 
> "Fu"? Evidently I had no fu to be low on.
> 
> Sequence was:
>   Do full install install of Squeeze to sda1. Only non-default was
>  size of install partition.
>   Do very minimal install to sda7 - i.e. no GUI, CLI only.
>   Do nothing for a week thus forgetting the "user name" associated
> with install on sda7.
> 
> I thought I had tried to respond "root" at the "login:" prompt and
> not being surprised that it didn't work. I thought that was what
> happened several months ago in a similar situation - that time I just
> wiped the disk and started over.
> 
> To other questions raised explicitly/implicitly:
>   1. I accept all defaults except allowing networks, size/location of
>  install partition, and what packages installed.
>   2. The user name for the install on sda1 is always "richard". I
> "users"
>  share the same password. "root" on all partitions share the same
> password.
>  I'm the only one to have physical or electronic access ;)
>   3. My boot system is Grub 1.98 .
>   4. Ralf was correct saying "IOW the OP remembers the password for
> UID 1000,
>  but not the name for UID".
> 

I think that before the boot process actually begins one is offered
the possibility of booting into single user mode. This allows one to
poke around on the hard disk. The only requirement to enter this mode
is that one give the password, not the user name.

The misspelling of forget is an amusing indication of your state of
mind while all this transpired. ;-)

-- 
Paul E Condon   
pecon...@mesanetworks.net


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140316025919.gb26...@big.lan.gnu

Help setting permissions on a thumb drive

[Paul E Condon]

I have a 4GB thumb drive that I have formatted with two
partitions: 

#1 is 100MB with vfat format
#2 is all the rest with ext4 format

I want to set permissions so that I can read/write on partition #1 on
both my Squeeze computer and on a Windows box, both as a
non-privileged user.  The last time that I ever had any real contact
with Windows was in the early days of Windows95, back in the last
century. I know that back then there was not much that one could do to
make this data interchange 'user friendly'. Has anything changed? Or
do I still have to use root to write on a vfat partition? I wouldn't even
bother to ask except I read in man-pages, for things related to mount,
that a distinction is sometimes made among 'user', 'users', and the
'owner of the device'.  So, I think maybe some software has been written
to clean up this mess, but probably not. So, has there been
improvement?

On the other hand, I have no problem with partition #2. It behaves as it 
should under Squeeze, and Windows does not give any hint that it knows of
its existence, Which is OK for me. 

But I would like to have a better way to move data on and off the vfat
partition, if such a way actually exists.

Ideas? Information?
TIA

-- 
Paul E Condon   
pecon...@mesanetworks.net


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140316022941.ga26...@big.lan.gnu

Re: On what is helpful and what is not [was: Re: Wifi]

[Zenaan Harkness]

(Also as a reminder to self:) Please refer to offtopic list rather
than bog down debian-user. Thanks Ralph for pointing me at o-t list.
Apologies for raising this non-technical issue on d-u.
Zenaan


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAOsGNSRQ1=xdkrksde0htazkfmioh-ey6zenyoq7fsgjnrt...@mail.gmail.com

Re: Wodim: Was: My experiences with three CD players on Gnome

[Zenaan Harkness]

On 3/16/14, Steve Litt of Troubleshooters.Com  wrote:
> On Sun, 16 Mar 2014 10:35:36 +1100
> Zenaan Harkness  wrote:
>
>> > Conclusion:  Gnome Player wins.
>>
>> Correction: The command line wins :)
>>
>> cdcd wodim (contains readom)  bashburn
>> cdargs cdrskin cdtool FTW
>
> Hi Zenaan,
>
> Are you doing -pad and padsize=63s? Back in the day, Linux had a flaw,
> called the Linux read-ahead buffer bug, that caused errors on
> raw-reading a CD if you didn't use both those arguments.

You haven't specified which program. Do all the above programs take
that option? Evidently I haven't used them. I use wodim and readom the
last few years and never had a problem, never had to learn about that
argument. I used to use some other program - maybe cdrecord, but only
for recording data discs. I don't remember the option.

> I wrote about it here:
> http://www.troubleshooters.com/linux/coasterless.htm

I put that link in my snippets/dvd.txt file the last time I saw it in
one of your posts. Thanks again.

> Are you using those arguments, and do you read your written CDs/DVDs as
> a device to check the md5sum against that of the iso you burned?

When I read an audio CD I use cdparanoia - should have added that to the list:

cdparanoia FTW!!! RAH RAH RAH

Other things from my snippets/dvd.txt file:

When I read data cds and dvds (haven't needed to do so for a couple of
years, I used to use dd, which on chained read-write-read would create
a larger image, so nowadays I use the following:
sudo readom dev=/dev/scd0 f=my-image.iso

and this to record:
sudo wodim -v -eject dev=/dev/scd0 my-image.iso
sudo wodim -v -eject -format dev=/dev/scd0 # if you need to format an R/W first

 To write a tar archive directly to a CD that will later contain a  simple
# ISO9660 filesystem with the tar archive call:
tar cf - . | genisoimage -stream-media-size 333000 | wodim dev=b,t,l
-dao tsize=333000s -

# combine gen image/ write:
genisoimage -J -r -f -V myvolname -graft-points /=symlink-farm-dir
-stream-media-size 333000 | wodim dev=/dev/sr0 -dao tsize=333000s -
???

And here's one which I used, this one time, to copy off all the Debian
packages off a set of Debian DVDs, into a local archive (running
'quick and dirty archive creation command' afterwards of course):
# Example of two alternating (actually, parallel), commands,
# to optimally read in a bunch of DVDs into a local mirror:
sudo readom dev=/dev/scd0 f=s && eject   # (alternate with filename
't' instead of 's')
sudo mount -o loop /media/s /media/u && sudo nice rsync -av /media/u/
./ && sudo umount /media/u && sudo rm /media/s  # ditto

To create an ISO image from a set of files or symlinks:
genisoimage -J -r -f -V myvolname -o image.iso -graft-points /=symlink-farm-dir


Some flac audio commands I use (always store your master audio in flac
of course):
Rip an audio cd into a single master flac file, with cue sheet for tracks:
abcde -1npV -o flac -a default,cue -S 32

Convert the tracks in the file my_disc.flac into another format (in
this case vorbis):
abcde -o vorbis -d my_disc.flac

Creating a bootable USB stick on gnu:
> Which instructions or program are you using to create the pen drive?
cat  filename.iso.hybrid  > /dev/sdb,c,d,x
cp /my/debian-boot-dvd.iso /dev/sdWHATEVER
dd if=/my/debian-boot-dvd.iso of=/dev/sdBLAH bs=1M

Regards
Zenaan


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/caosgnst9dshjpkctyrmzutf+da+y3ddcutaz1a55cuor5bo...@mail.gmail.com

Wodim: Was: My experiences with three CD players on Gnome

[Steve Litt of Troubleshooters.Com]

On Sun, 16 Mar 2014 10:35:36 +1100
Zenaan Harkness  wrote:

> > Conclusion:  Gnome Player wins.
> 
> Correction: The command line wins :)
> 
> cdcd wodim (contains readom)  bashburn
> cdargs cdrskin cdtool FTW

Hi Zenaan,

Are you doing -pad and padsize=63s? Back in the day, Linux had a flaw,
called the Linux read-ahead buffer bug, that caused errors on
raw-reading a CD if you didn't use both those arguments. I wrote about
it here:

http://www.troubleshooters.com/linux/coasterless.htm

Are you using those arguments, and do you read your written CDs/DVDs as
a device to check the md5sum against that of the iso you burned?

Thanks,

SteveT

Steve Litt*  http://www.troubleshooters.com/
Troubleshooting Training  *  Human Performance


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140315212220.7d6cb22b@mydesk

Re: My experiences with three CD players on Gnome

[Zenaan Harkness]

> Conclusion:  Gnome Player wins.

Correction: The command line wins :)

cdcd wodim (contains readom)  bashburn
cdargs cdrskin cdtool FTW

RAH RAH RAH Command Line RAH RAH RAH

Ok, I'll just, take my chamomile tea now...


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/caosgnsr430t5wyxqzoyfykttm4mvoeenusuvidquvat-k-6...@mail.gmail.com

Re: .Xresources not loading on start

[Anubhav Yadav]

On Sun, Mar 16, 2014 at 4:51 AM, John D. Hendrickson and Sara Darnell
 wrote:
> i wrote this:
>
> http://sourceforge.net/p/xdm-options/
>
> it launches window manager desktop pairs.  you might see something in it
> that helps
>
>
> this seems simple.  back off your recent changes and change only one thing
> at a time.  you can then say which change caused a problem
>
>
> i would guess an "exit 1" signaled by any app during the X starup might give
> you headaches.  it's better to wait until after X starts (run a script then)
> unless you got everything down or are doing something special.

Hi, Thanks for taking out time and replying. Is that a complete new
display manager. Does it have a package for debian?
Also I pressed the send button my mistake, so I completed my question
in the next mail. Its link is,
https://lists.debian.org/debian-user/2014/03/msg00888.html
-- 
Regards,
Anubhav Yadav
Imperial College of Engineering and Research,
Pune.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/ca+jf9ahem0fsdwaoanx0nbhx4z8doh74qylwzo3zfqjzzfo...@mail.gmail.com

Re: Xorg and composite UNICODE characters

[Siard]

Matej Kosik wrote:
> Then I tried to make:
> 
>   ɔ̃
> 
> accessible via
> 
>   Alt+Shift+o
> 
> No I am not sure how can I do that.
> 
> Neither:
> 
>   key  { [ o, O, U0254, U02540303 ] };
> 
> nor
> 
>   key  { [ o, O, U0254, U03030254 ] };
> 
> works.
> 
> What is the right way to do it (i.e. how to map some existing key
> to ɔ̃ ?)

'ɔ̃' has a so-called multiple keycode (ɔ with added tilde).
What you can do is this:

key  { [ o, O, U0254, U0303 ] };

To get a ɔ̃, first type Alt+o --> ɔ appears;
then type Alt+Shift+o --> ɔ changes to ɔ̃.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140316003317.3656f943.shiems...@kpnplanet.nl

Re: can't build modules after update

[Tamer Higazi]

Hallo Selim!
Thank you for your response.

I was downloading with git mISDN. I know mISDN is in the kernel, but the
recent version has the mISDN_oslec echo canceler included.

As well, I need the sources to patch that mISDN version for my new
openvox isdn board with an hc.

I was capable to build any kernel module with:

"make modules"

which is now no more possible. Even if I delete the source folder, grab
it again with git, the result remains the same.


The old kernel version was, 3.4 which I updated to 3.12-1.

For any further suggestions I would kindly thank you.



Tamer



Am 14.03.2014 14:24, schrieb Selim T. Erdogan:
> Tamer Higazi, 11.03.2014:
>> Hi people!
>>
>> I have updated the kernel, and removed the old one, sources,
>> kbuild,linux-header and modules from the old kernel.
>> I have installed the updated, kernel, modules,kbuild,headers with the
>> same version number from the current one.
>>
>> Now I want to compile manually a module and I receive the error message:
>>
>> make: *** No rule to make target `modules'.  Stop.
>>
>>
>>
>> what did I make wrong ?!
> 
> What command(s) did you run?  What module are you trying to compile?
> What are the old and new kernel versions?  Were you able to compile the
> module successfully with the old kernel?
> 
> 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5324dfaa.80...@googlemail.com

Re: .Xresources not loading on start

[Anubhav Yadav]

On Sun, Mar 16, 2014 at 4:36 AM, Anubhav Yadav  wrote:
> Hello,
> Suddenly my .Xresources are not working on startup. Meaning I have to
> manually startup a terminal and issue "xrdb .Xresources" and restart
> the shell to see my colors.
>
> I am using(learning to use) i3 although I have xfce installed, and I
> start i3/xfce from lightdm.
>
> Now I remember doing two things after which this started happening:
>
> 1) I changed the colors of my .Xresources from base16-tomorrow to molokai.
> Here is my .Xresources http://paste.debian.net/87922
>
> To be a little more precise, the previous scheme had the colors
> defined like this:
>
> #define t_background #1d1f21
> #define t_current_line #282a2e
> #define t_selection #373b41
> #define t_foreground #c5c8c6
> #define t_comment #969896
> #define t_red #cc
> #define t_orange #de935f
> #define t_yellow #f0c674
> #define t_green #b5bd68
> #define t_aqua #8abeb7
> #define t_blue #81a2be
> #define t_purple #b294bb
>
>
> *.foreground: t_foreground
> *.background: t_background
> *.cursorColor: #aeafad
>
> ! Black / Grey
> *.color0: #00
> *.color8: #66
>
> ! Red / Bright Red
> *.color1: t_red
> *.color9: #FF3334
>
> ! Green + Bright Green
> *.color2: t_green
> *.color10: #9ec400
> ..
> [snipped]
>
> And the new colors are directly put like this
>
> !Molokai terminal colours
> *foreground:#a0a0a0
> *background:#1b1d1e
>
> !molokai inspired colors
>
> !black
> *color0:#1b1d1e
> *color8:#505354
> !red
> *color1:#f92672
> *color9:#ff5995
> !green
> *color2:#82b414
> *color10:   #b6e354
> !yellow
> *color3:#fd971f
> *color11:   #feed6c
> !blue
> *color4:#56c2d6
> *color12:   #8cedff
>
> [..snipped..]
>
> 2) I edited the file /etc/lightdm/lightdm.conf and added this line:
> user-session=i3
> to make i3 as default in i3.
>
> 3) I created a file ~/.xessionrc and added the line to it
> export PATH=$HOME/bin:$PATH

Sorry pressed the send button by mistake: Here is the continuation

So I created the above file so that I could run scripts from ~/bin in dmenu.

These 3 steps I remember doing after which my .Xresources failed to
load on startup.

Now I already reverted steps 2 and 3, but even now that won't help.

These are the things I tried:

1) I changed to format of the colors from
*background to xterm*background or Xterm.VT100.background but that wont help.

2) I created a symlink .Xdefaults to .Xresources but that won't work either.

3) I also created ~/.xinitrc and added the line "xrdb -load
.Xresources" to it, but that won't help either.

Interesting thing to note is that only "xrdb .Xresources" will work
after boot. Not  "xrdb -merge .Xresources" neither "xrdb -overide
.Xresources"

Any help? And sorry for the reply to my own mail to complete my question!



-- 
Regards,
Anubhav Yadav
Imperial College of Engineering and Research,
Pune.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/ca+jf9agxeykw_ooedjqnqzxb-q2qecjutdnrezun0hzinbn...@mail.gmail.com

.Xresources not loading on start

[Anubhav Yadav]

Hello,
Suddenly my .Xresources are not working on startup. Meaning I have to
manually startup a terminal and issue "xrdb .Xresources" and restart
the shell to see my colors.

I am using(learning to use) i3 although I have xfce installed, and I
start i3/xfce from lightdm.

Now I remember doing two things after which this started happening:

1) I changed the colors of my .Xresources from base16-tomorrow to molokai.
Here is my .Xresources http://paste.debian.net/87922

To be a little more precise, the previous scheme had the colors
defined like this:

#define t_background #1d1f21
#define t_current_line #282a2e
#define t_selection #373b41
#define t_foreground #c5c8c6
#define t_comment #969896
#define t_red #cc
#define t_orange #de935f
#define t_yellow #f0c674
#define t_green #b5bd68
#define t_aqua #8abeb7
#define t_blue #81a2be
#define t_purple #b294bb


*.foreground: t_foreground
*.background: t_background
*.cursorColor: #aeafad

! Black / Grey
*.color0: #00
*.color8: #66

! Red / Bright Red
*.color1: t_red
*.color9: #FF3334

! Green + Bright Green
*.color2: t_green
*.color10: #9ec400
..
[snipped]

And the new colors are directly put like this

!Molokai terminal colours
*foreground:#a0a0a0
*background:#1b1d1e

!molokai inspired colors

!black
*color0:#1b1d1e
*color8:#505354
!red
*color1:#f92672
*color9:#ff5995
!green
*color2:#82b414
*color10:   #b6e354
!yellow
*color3:#fd971f
*color11:   #feed6c
!blue
*color4:#56c2d6
*color12:   #8cedff

[..snipped..]

2) I edited the file /etc/lightdm/lightdm.conf and added this line:
user-session=i3
to make i3 as default in i3.

3) I created a file ~/.xessionrc and added the line to it
export PATH=$HOME/bin:$PATH


-- 
Regards,
Anubhav Yadav
Imperial College of Engineering and Research,
Pune.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/ca+jf9aefw0j-crpxyelbshnptkiy22fewndq5kgc+y2w26l...@mail.gmail.com

Re: galternatives

[Brian]

On Sat 15 Mar 2014 at 17:04:44 -0400, Ric Moore wrote:

> I am currently running Jessie with galternatives 0.13.5+nmu2
> installed. For whatever reason it refuses to allow me to change
> anything, even run as root. Nor, does synaptic allow me to
> re-install it. Vey strange. If anyone else has it installed,

Jessie doen't have galternatives, so it cannot be installed from
the archives.

> with that version, would you give it a whirl for me to see if the
> same happens? Then I could file a big report.

Sounds like fixing your system first would be the first step.
 
> Running it as user doesn't bring up the dialog to enter the root
> passwd, either. Thanx! I love this app. Ric

This doesn't happen to me on Sid.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/15032014230134.c1889c446...@desktop.copernicus.demon.co.uk

Re: Notebook don't hibernate anymore

[xyz134268]

On Fri, 14 Mar 2014 16:13:32 + (UTC)
Marcelo  wrote:

> Notebook don't hibernate anymore
>
> Problem: My laptop does not hibernate when the battery is only 4%!
> Furthermore, it
> does not warn nor beeps when the battery drops to 10% (setted limit
> for low battery). What else should I look? Where?
>
> I am a gnome guy!
>
> If I select Hibernate from the shutdown menu, it usually hibernates.
> Similarly, if I run, in the terminal:
>
> :-# pm-hibernate
>
> system hibernate, too.
>
> On the dconf-editor, the configiration are
> (org/gnome/settings-daemon/plugins/power):
>
> active checked
> button-hibernate hibernate
> button-power suspend - when I press the power button, the screen
> gives off and, in a few seconds, back to the login screen. It's like
> I've switched user. Everything is still open and running as before I
> pressing the button. button-sleep hibernate
> button-supend suspend
> critical-battery-action hibernate
> idle-brigthness 30
> idel-dim checked
> idle-dim-ac não checked
> idle-dim-battery checked
> notify-perhaps-recall checked
> percentagem-action 4
> percentagem-critical 5
> percentage-low 10 when it reaches 10%, the battery light turns red
> and a message appears warning you that the battery is low.
> priority 0
> sleep-inactive-ac-timeout 3600
> sleep-inactive-ac-type nothing
> sleep-inactive-battery checked
> sleep-inactive-battery-timeout 1800
> sleep-inactive-battery-type nothing
> time-action 120
> time-critical 300
> time-low 1200
> use-time-for-policy unchecked
>
> I have dconf and gconf installed. Can I remove the gconf?
>
> :-# aptitude search dconf
> i A dconf-cli   - simple configuration storage
> system - util i A dconf-editor- simple
> configuration storage system - util i A
> dconf-gsettings-backend - simple configuration storage system
> - GSet i A dconf-service   - simple configuration
> storage system - D-Bu i A dconf-tools -
> transitional dummy package p   libdconf-dbg-
> simple configuration storage system - debu i
> libdconf-dbus-1-0   - simple configuration storage system
> - D-Bu p   libdconf-dbus-1-dbg - simple configuration
> storage system - D-Bu p   libdconf-dbus-1-dev - simple
> configuration storage system - D-Bu p
> libdconf-dev- simple configuration storage system
> - deve p   libdconf-doc- simple configuration
> storage system - docu c   libdconf0   - simple
> configuration storage system - runt i A
> libdconf1   - simple configuration storage system
> - runt p   upstart-dconf-bridge- DConf bridge for upstart
> p   xnetcardconfig  - A simple network card
> configuration wizard :-# :-# aptitude search gconf p
> gconf-cleaner   - GConf database cleaner p
> gconf-defaults-service  - GNOME configuration database system
> (syste p   gconf-editor- editor for the GConf
> configuration system p   gconf-gsettings-backend - GNOME
> configuration database system - GSet i
> gconf-service   - GNOME configuration database system
> (D-Bus i A gconf2  - GNOME configuration
> database system (suppo i A gconf2-common   - GNOME
> configuration database system (commo i A
> gir1.2-gconf-2.0- GNOME configuration database system
> (GObje i A gstreamer0.10-gconf - GStreamer plugin for
> getting the sink/sour p   guile-gnome2-gconf  - Guile
> bindings for GConf p   libextutils-pkgconfig-perl  - Perl
> interface to the pkg-config utility i A
> libgconf-2-4- GNOME configuration database system
> (share p   libgconf-bridge-dev - Bind GObject properties
> to GConf keys (dev p   libgconf-bridge0- Bind GObject
> properties to GConf keys i A libgconf2-4 - GNOME
> configuration database system (dummy p
> libgconf2-dev   - GNOME configuration database system
> (devel p   libgconf2-doc   - GNOME configuration
> database system (API r i A libgconf2.0-cil - CLI
> binding for GConf 2.24 p   libgconf2.0-cil-dev - CLI
> binding for GConf 2.24 p   libgconfmm-2.6-1c2  - C++
> wrappers for GConf (shared library) p
> libgconfmm-2.6-dev  - C++ wrappers for GConf (development
> files) p   libgconfmm-2.6-doc  - C++ wrappers for GConf
> (documentation) p   libghc-gconf-dev- Binding to the
> GNOME configuration databas v   libghc-gconf-dev-0.12.1.1-7007e - p
> libghc-gconf-doc- Binding to the GNOME configuration
> databas p   libghc-gconf-prof   - Binding to the GNOME
> configuration databas v   libghc-gconf-prof-0.12.1.1-7007 - p
> libgnome2-gconf-perl- Perl interface to the GNOME GConf
>

galternatives

[Ric Moore]

I am currently running Jessie with galternatives 0.13.5+nmu2 installed. 
For whatever reason it refuses to allow me to change anything, even run 
as root. Nor, does synaptic allow me to re-install it. Vey strange. 
If anyone else has it installed, with that version, would you give it a 
whirl for me to see if the same happens? Then I could file a big report.


Running it as user doesn't bring up the dialog to enter the root passwd, 
either. Thanx! I love this app. Ric


--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
/https://linuxcounter.net/cert/44256.png /


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/5324c06c.1000...@gmail.com

Re: systemd - boot messages

[Brian]

On Sat 15 Mar 2014 at 18:25:54 +0100, Hans wrote:

> I understand, systemd is still beta, and things will not work as expected 
> from 
> the beginning on, so I can live with this problem at the moment. When I will 
> understand systemd better in the future, maybe I can solve problems on my 
> own. 

This could help:

  http://lists.freedesktop.org/archives/systemd-devel/2013-March/009991.html


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/15032014174754.72042e07e...@desktop.copernicus.demon.co.uk

Re: [Fwd: Re: systemd - boot messages]

[Tom Furie]

On Sat, Mar 15, 2014 at 05:35:18PM +0100, Ralf Mardorf wrote:

> I could write what ever I want to send to this list, but as soon
> "systemd" is part of the subject, my mails are delayed or won't come
> through the list.

It isn't only you this happens to. *All* messages with systemd in the
subject get delayed by the system. Remember the recent threads?

Cheers,
Tom

-- 
Rebellion Postponement:
The tendency in one's youth to avoid traditionally youthful
activities and artistic experiences in order to obtain serious career
experience.  Sometimes results in the mourning for lost youth at about
age thirty, followed by silly haircuts and expensive joke-inducing
wardrobes.
-- Douglas Coupland, "Generation X: Tales for an Accelerated
   Culture"


signature.asc
Description: Digital signature

Re: systemd - boot messages

[Hans]

Am Samstag, 15. März 2014, 17:22:34 schrieb Ralf Mardorf:
> Take a look at all services, perhaps a service want's to start _after_
> and _before_ another service.

Hmm, I am  a liitle bit overstrained.  I do not know, how to change the order 
of the services. On the other hand, these messages appear at once, just before 
/var, /usr and /home are mounted (I must unlock them manually, as they are 
luks encrypted).

And yes, I looked into the documentations, but it is still not cclear for me, 
hwo systemd is working, hot it is starting services if any, or if it is 
directly controilled by the kernel, whatever.

I understand, systemd is still beta, and things will not work as expected from 
the beginning on, so I can live with this problem at the moment. When I will 
understand systemd better in the future, maybe I can solve problems on my own. 

For now, I am very confuscated do not know, where to start optimising. 

So I think, I should wait a little time and learn more. Then I will ask again, 
and due to your help a solution will be found easier.

So, at the moment let us just pause with this problem until I am more 
experienced.

Thanks for trying to help anyway!

Best regards

Hans


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/4702724.KhvlIKbp7u@protheus2

Re: When fogetting assigned login name rather than password

[Ralf Mardorf]

On Sat, 2014-03-15 at 17:28 +, Tom Furie wrote:
> systemd will replace the current init system but will still
> require a /sbin/init.

[rocketmouse@archlinux ~]$ ls -hAl /sbin/init
lrwxrwxrwx 1 root root 22 Mar  6 23:22 /sbin/init -> ../lib/systemd/systemd

My Debian install still does use SysVinit.

[rocketmouse@archlinux ~]$ ls -hAl /mnt/debi386/sbin/init
-rwxr-xr-x 1 root root 35K Jul 18  2013 /mnt/debi386/sbin/init


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1394905086.3587.218.camel@archlinux

Re: When fogetting assigned login name rather than password

[Tom Furie]

On Sat, Mar 15, 2014 at 11:25:41AM -0400, Steve Litt of
Troubleshooters.Com wrote:
> On Sat, 15 Mar 2014 11:01:15 + Tom Furie  wrote:

> > The classic approach to this problem is to pass 'init=/bin/sh' to
> > the kernel.

> Do you think this is going to continue working when we switch to
> systemd?

Absolutely. systemd will replace the current init system but will still
require a /sbin/init. By default, once the kernel loads it looks for an
executable located at /sbin/init, this can be anything that is
executable by the system. By passing 'init=...' to the kernel you
override this behaviour and the kernel loads whatever you pass in the
parameter. 

Cheers,
Tom

-- 
Don't quit now, we might just as well lock the door and throw away the key.


signature.asc
Description: Digital signature

My experiences with three CD players on Gnome

[Patrick Chkoreff]

I don't play music very much on the computer, so I'm new to this
subject.  I just tried three different players, RhythmBox, SoundJuicer,
and Gnome Player.

RhythmBox has a problem.  Press Play to begin playing a CD.  Press Play
again to Pause.  Press Play again to resume playing.  Nothing happens.

SoundJuicer has a problem.  The Help says: "While playing, Sound Juicer
displays a slider showing the position on the current track. To seek to
another part of the track, drag the handle along the slider and
release."  However, I do not see any such slider control.  I see the
horizontal track where the slider is supposed to be, just nothing to
grab, and clicking in the track does nothing.

Gnome Player does what I expect.  I can play, pause, and resume playing
again.  It has a functioning slider.

Conclusion:  Gnome Player wins.


-- Patrick


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/532484fc.10...@rayservers.net

Re: [Fwd: Re: systed - boot messages]

[Brian]

On Sat 15 Mar 2014 at 17:35:18 +0100, Ralf Mardorf wrote:

> I could write what ever I want to send to this list, but as soon
> "systemd" is part of the subject, my mails are delayed or won't come
> through the list.

The first is by design, The second is your problem and between you and
your ISP.

> I don't remember that I ever trolled about systemd on this list.

Do you rememember reading all of this thread which you started?

  Date: Sun, 2 Mar 2014 01:41:48 +0100
  From: Ralf Mardorf 
  To: debian-user 
  Subject: Test


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140315170037.gc26...@copernicus.demon.co.uk

[Fwd: Re: systemd - boot messages]

[Ralf Mardorf]

I could write what ever I want to send to this list, but as soon
"systemd" is part of the subject, my mails are delayed or won't come
through the list.

I don't remember that I ever trolled about systemd on this list.

 Forwarded Message 
From: Ralf Mardorf 
To: debian-user@lists.debian.org
Subject: Re: systemd - boot messages
Date: Sat, 15 Mar 2014 17:22:34 +0100
Mailer: Evolution 3.10.4 

Take a look at all services, perhaps a service want's to start _after_
and _before_ another service.



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1394901318.3587.178.camel@archlinux

Re: When fogetting assigned login name rather than password

[Brian]

On Sat 15 Mar 2014 at 11:25:41 -0400, Steve Litt of Troubleshooters.Com wrote:

> On Sat, 15 Mar 2014 11:01:15 +
> Tom Furie  wrote:
> 
> > The classic approach to this problem is to pass 'init=/bin/sh' to the
> > kernel. The method for doing so depends on which boot manager you
> > might be using.
> 
> That's really cool, and I'm going to remember it. Before this, I've
> always booted a live CD for stuff like this.
> 
> Do you think this is going to continue working when we switch to
> systemd?

Definitely.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/15032014164620.751d6d0ac...@desktop.copernicus.demon.co.uk

Re: systemd - boot messages

[Ralf Mardorf]

Take a look at all services, perhaps a service want's to start _after_
and _before_ another service.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1394900554.3587.172.camel@archlinux

Re: [Resolved] Re: When fogetting assigned login name rather than password

[Ralf Mardorf]

On Sat, 2014-03-15 at 09:08 -0500, Richard Owlett wrote:
> 4. Ralf was correct saying "IOW the OP remembers the password 
> for UID 1000, but not the name for UID".

:D



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1394900380.3587.171.camel@archlinux

Re: When fogetting assigned login name rather than password

[Ralf Mardorf]

On Sat, 2014-03-15 at 15:01 +0200, Andrei POPESCU wrote:
> We are close to taking bets :)

Now you're mistaken, we already were taking bets.



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1394900281.3587.170.camel@archlinux

Re: When fogetting assigned login name rather than password

[Steve Litt of Troubleshooters.Com]

On Sat, 15 Mar 2014 09:34:22 -0500
Richard Owlett  wrote:

> Andrei POPESCU wrote:

> > [1] not sure how this works with a disabled root account though, in
> > case you chose this during installation. Would a kind list
> > subscriber with such a setup please test and clarify this for us?
> 
> I'm about to do one of my routine disk wipes. Tell me what 
> initial conditions you wish and what test procedure and I'll be 
> happy to do it. The install medium will be Debian 6.0.5 DVD 1 of 
> 8 with no internet connection.

Before wiping, just for the fun of it, use either a live CD or Tom's
pass 'init=/bin/sh' to the kernel method to access the hard drive,
mount the normal root partition of your machine, edit /etc/passwd, and
erase the x that's the second field (fields are delineated by colons)
in your regular login. This leaves your regular name without password,
meaning you can just press Enter when queried for a password.

Disconnect from the network (for security, you now have no
password), reboot, and immediately, use the passwd command to give your
regular login a password. When asked for your current password, just
press Enter.

Once you're in, type

su -

and you can have your way with the machine.

HTH,

SteveT

Steve Litt*  http://www.troubleshooters.com/
Troubleshooting Training  *  Human Performance


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140315114844.747c167a@mydesk

Re: When fogetting assigned login name rather than password

[Steve Litt of Troubleshooters.Com]

On Sat, 15 Mar 2014 12:38:48 +
Tom Furie  wrote:


> Having gone back to re-read Richard's original post, he does state
> that he was bringing up an install without GUI. Which poses the
> question "why not just log in as root to get the user name?" unless
> root logins are disabled, which leads us back to how he has a root
> password in that case.

One possible explanation might be that he disabled root login by having
a blank /etc/securetty file, which disallows root login on a tty, but
you still have a root account you can su to after logging in as a
regular user.

SteveT

Steve Litt*  http://www.troubleshooters.com/
Troubleshooting Training  *  Human Performance


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140315113739.360a49dc@mydesk

Re: When fogetting assigned login name rather than password

[Steve Litt of Troubleshooters.Com]

On Sat, 15 Mar 2014 11:01:15 +
Tom Furie  wrote:

> On Sat, Mar 15, 2014 at 05:45:14AM -0500, Richard Owlett wrote:
> 
> > If another OS had not been available but I knew the root password,
> > is there some way I could have gained access as root?
> 
> The classic approach to this problem is to pass 'init=/bin/sh' to the
> kernel. The method for doing so depends on which boot manager you
> might be using.
> 
> Cheers,
> Tom

That's really cool, and I'm going to remember it. Before this, I've
always booted a live CD for stuff like this.

Do you think this is going to continue working when we switch to
systemd?

Thanks for the info.

SteveT

Steve Litt*  http://www.troubleshooters.com/
Troubleshooting Training  *  Human Performance


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140315112541.7dd313a5@mydesk

systemd - boot messages

[Hans]

Hi folks, 

at boot I get lotsa of messages of this kind:

 6.782635] systemd[1]: Job setserial.service/start deleted to break ordering 
cycle starting with basic.target/start

   6.782433] systemd[1]: Breaking ordering cycle by deleting job 
sockets.target/start
[6.782438] systemd[1]: Job sockets.target/start deleted to break ordering 
cycle starting with basic.target/start

and so on.

Can you tell me, what they do mean and why they are produced? How can I get 
rid of these if possible?

I already deinstalled and purged "hal" and "hal-info" as well as deinstalled 
orphaned libs. This reduced some messages, but not all.

I installed systemd and systemd-sysv.

Thanks for enlightening me.

Best regards

JHans


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1448573.9luCBaJWIb@protheus2

Re: When fogetting assigned login name rather than password

[Richard Owlett]

Andrei POPESCU wrote:

On Sb, 15 mar 14, 05:45:14, Richard Owlett wrote:


If another OS had not been available but I knew the root password, is there
some way I could have gained access as root?


- Debian installer rescue mode


I was thinking of that as an instance of "having another OS 
available".



- boot in recovery mode[1]

Could you please clarify for us how you "know the root password", but
can't "gain access as root"?

 see https://lists.debian.org/53245ef4.2050...@cloud85.net



We are close to taking bets :)


The winner will be someone claiming I have faulty recall of what 
I tried ;/





[1] not sure how this works with a disabled root account though, in case
you chose this during installation. Would a kind list subscriber with
such a setup please test and clarify this for us?


I'm about to do one of my routine disk wipes. Tell me what 
initial conditions you wish and what test procedure and I'll be 
happy to do it. The install medium will be Debian 6.0.5 DVD 1 of 
8 with no internet connection.




--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/532464ee.1040...@cloud85.net

Re: When fogetting assigned login name rather than password (and disabling root login)

[Scott Ferguson]

On 15/03/14 23:38, Tom Furie wrote:
> On Sat, Mar 15, 2014 at 12:21:27PM +, Tom Furie wrote:
> 
>> It does seem much more likely that Scott is correct and root
>> logins are only disabled at the graphical login - as Scott says,
>> that is the default configuration - in which case Richard should
>> be able to ctrl-alt-Fn to a virtual console, ctrl-alt-bspace to
>> kill the X server (though I think that's disabled since the last
>> few releases)

"dontzap" disabling Terminate_Server XKB??

That was one thing I ran out of time to try (visitors staying and
yapping in my ear).

Maybe it works if done twice??

There's also the possibility of Alt-Sysrq-K (?)



> 
> Having gone back to re-read Richard's original post, he does state
> that he was bringing up an install without GUI. Which poses the
> question "why not just log in as root to get the user name?" unless
> root logins are disabled, which leads us back to how he has a root
> password in that case.
> 
> Without further input from Richard we have no way of knowing for
> certain what the exact situation is.

Sound logic, until then we're just speculating.


> 
> Cheers, Tom
> 

In the spirit of investigation I tried testing a few methods of
disabling root login (there are likely other methods)

Expiring the root password:-
# chage -E 0 root
This prohibits login to a console as root, but...
Booting into single-mode still allows login as root

Editing /etc/passwd:-
!root $TheUsualStuff

Results in:-
"sulogin: cannot open password database"
segfault

Disallows root login even in single user-mode. Probably not a good idea.

Editing /etc/password:-
root $TheUsualStuff :/bin/false

Disallows root login even in single user-mode. "Seems" to work fine,
as long as; you're happy not running as root (just running commands as
root); you have an alternative to rescue mode available (there are at
least two I know of).


Kind regards


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53246283.5020...@gmail.com

Re: When fogetting assigned login name rather than password

[Brian]

On Sat 15 Mar 2014 at 15:01:26 +0200, Andrei POPESCU wrote:

> On Sb, 15 mar 14, 05:45:14, Richard Owlett wrote:
> > 
> > If another OS had not been available but I knew the root password, is there
> > some way I could have gained access as root?
> 
> - Debian installer rescue mode
> - boot in recovery mode[1]
> 
> Could you please clarify for us how you "know the root password", but 
> can't "gain access as root"? We are close to taking bets :)
> 
> [1] not sure how this works with a disabled root account though, in case 
> you chose this during installation. Would a kind list subscriber with 
> such a setup please test and clarify this for us?

sulogin: root account is locked, starting shell
root@localhost:~#


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/15032014140455.8936e6ad9...@desktop.copernicus.demon.co.uk

[Resolved] Re: When fogetting assigned login name rather than password

[Richard Owlett]

Scott Ferguson wrote:

On 15/03/14 22:29, Tom Furie wrote:

On Sat, Mar 15, 2014 at 10:09:33PM +1100, Scott Ferguson wrote:

On 15/03/14 21:45, Richard Owlett wrote:



If another OS had not been available but I knew the root
password, is there some way I could have gained access as
root?



# passwd `grep 1000 /etc/passwd | cut -d : -f1`


That doesn't help him until he's logged into the system.


Richard has clearly said "if I knew the root password" "as root"
So he *can* login to the system.
Why he didn't, is the question. ;)

Perhaps he tried from a GUI login which only permitted a userlogin
(but didn't prompt with the username and didn't, or couldn't
(Crtl+backspace etc) didn't work - still wouldn't explain why he
didn't just boot into the rescue console. Perhaps his fu was low?



"Fu"? Evidently I had no fu to be low on.

Sequence was:
  Do full install install of Squeeze to sda1. Only non-default was
 size of install partition.
  Do very minimal install to sda7 - i.e. no GUI, CLI only.
  Do nothing for a week thus forgetting the "user name" 
associated with install on sda7.


I thought I had tried to respond "root" at the "login:" prompt 
and not being surprised that it didn't work. I thought that was 
what happened several months ago in a similar situation - that 
time I just wiped the disk and started over.


To other questions raised explicitly/implicitly:
  1. I accept all defaults except allowing networks, 
size/location of

 install partition, and what packages installed.
  2. The user name for the install on sda1 is always "richard". 
I "users"
 share the same password. "root" on all partitions share the 
same password.

 I'm the only one to have physical or electronic access ;)
  3. My boot system is Grub 1.98 .
  4. Ralf was correct saying "IOW the OP remembers the password 
for UID 1000,

 but not the name for UID".


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/53245ef4.2050...@cloud85.net

Re: Apache default directories

[Tony Baldwin]

On Sat, Mar 15, 2014 at 01:54:41PM +1100, Scott Ferguson wrote:
> On 15/03/14 12:20, Peter Michaux wrote:
> > Hi,
> > 
> > The default virtual host when Apache is installed on Debian has
> > document root /var/www and a cgi-bin directory /usr/lib/cgi-bin. These
> > directories do not make intuitive sense to me. 
> 
> That's the problem with intuition (instant understanding). ;)
> 
> > If I have static HTML
> > pages and some Perl CGI scripts, I would expect they go somewhere
> > under /usr/share/. 
> 
> root "owns" /usr/share
> 
> Would you want your web server running as root?
> 
> 
> > What is the rational behind the chosen default
> > directories?
> 
> 
> /var/www is owned by the webserver and the server group (www-data)
> ls -al /var/www

Actually, what's typical in there is
-rwxr-xr-x  1 root root

But you can put stuff wherever you want, so long as you tell apache
where it is with a vhost.
I put some directories in users' homes on servers:
/home/user/www/
then point a vhost there
You just have to be sure and give the server permissions where needed,
like, if you install a dokuwiki in there, make the data and upload
directories writeable to the server, 
or if you put a wordpress, drupal, joomla, piwigo, or whatever else in there, 
similarly,
there are directories that the server must be able to write in.
But I tend to NOT install stuff like wp or dokuwiki from debian
packages, rather using the upstream packages, since I use stable on
servers, and stable packages tend not to keep up with upstream packages
so well.
I especially prefer upstream packages with git repos, where I can update
them with a pull, like redmatrix (which isn't in debian, yet, anyway).

Tony
-- 
https://tonybaldwin.info
art, music, software by me, tony
3F330C6E


signature.asc
Description: Digital signature

Re: When fogetting assigned login name rather than password

[Andrei POPESCU]

On Sb, 15 mar 14, 05:45:14, Richard Owlett wrote:
> 
> If another OS had not been available but I knew the root password, is there
> some way I could have gained access as root?

- Debian installer rescue mode
- boot in recovery mode[1]

Could you please clarify for us how you "know the root password", but 
can't "gain access as root"? We are close to taking bets :)

[1] not sure how this works with a disabled root account though, in case 
you chose this during installation. Would a kind list subscriber with 
such a setup please test and clarify this for us?

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: When fogetting assigned login name rather than password

[Tom Furie]

On Sat, Mar 15, 2014 at 05:45:14AM -0500, Richard Owlett wrote:
 
> The complete hard drive is wiped at least once a month. I
> consistently use my name as the login on the first install of any
> series. The login of any subsequent install will be a mnemonic
> associated associated with the current experiment.
> 
> I just tried to bring up an install without a GUI. I had forgotten
> the login name I had assigned a week ago. I solved the immediate
> problem by rebooting to the install on sda1 and using it to examine
> /etc/passwd on sda7.

On further thinking about this I have some questions.

You say "I just tried to bring up an install...", by this do you mean you
*have* installed and are trying to log in, or that you are now doing a
text mode install but have forgotten the previous username you used
so don't know what this username should be?

Cheers,
Tom

-- 
Without love intelligence is dangerous;
without intelligence love is not enough.
-- Ashley Montagu


signature.asc
Description: Digital signature

Re: When fogetting assigned login name rather than password

[Ralf Mardorf]

On Sat, 2014-03-15 at 12:38 +, Tom Furie wrote:
> Without further input from Richard we have no way of knowing for
> certain what the exact situation is.

We have got ;).

You are right, Mrs. L, Mr. S and I'm mistaken. You are only mistaken to
your self-doubts.

Richard has got no root password.
The password of the first user, for Linux distros it's likely UID 1000,
this password quasi is the "root" password.




-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1394887655.3587.156.camel@archlinux

Re: When fogetting assigned login name rather than password

[Tom Furie]

On Sat, Mar 15, 2014 at 12:21:27PM +, Tom Furie wrote:

> It does seem much more likely that Scott is correct and root logins are
> only disabled at the graphical login - as Scott says, that is the
> default configuration - in which case Richard should be able to
> ctrl-alt-Fn to a virtual console, ctrl-alt-bspace to kill the X server
> (though I think that's disabled since the last few releases), or boot
> into recovery mode.

Having gone back to re-read Richard's original post, he does state that
he was bringing up an install without GUI. Which poses the question "why
not just log in as root to get the user name?" unless root logins are
disabled, which leads us back to how he has a root password in that
case.

Without further input from Richard we have no way of knowing for certain
what the exact situation is.

Cheers,
Tom

-- 
Once upon a time there was a kingdom ruled by a great bear.  The peasants
were not very rich, and one of the few ways to become at all wealthy was
to become a Royal Knight.  This required an interview with the bear.  If
the bear liked you, you were knighted on the spot.  If not, the bear would
just as likely remove your head with one swat of a paw.  However, the family
of these unfortunate would-be knights was compensated with a beautiful
sheepdog from the royal kennels, which was itself a fairly valuable
possession.  And the moral of the story is:

The mourning after a terrible knight, nothing beats the dog of the bear that
hit you.


signature.asc
Description: Digital signature

Semi-OT: When fogetting assigned login name rather than password

[Ralf Mardorf]

On Sat, 2014-03-15 at 12:21 +, Tom Furie wrote:
> ctrl-alt-bspace

By default it's disabled, not only for Debian :D, only dinos know this
shortcut.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1394887067.3587.148.camel@archlinux

Re: When fogetting assigned login name rather than password

[Tom Furie]

On Sat, Mar 15, 2014 at 12:58:59PM +0100, Ralf Mardorf wrote:

> Tom is smarter than we are, it's likely that his guess is correct. The
> OP confused the term for

I am far from it, and Lisi and Scott have both made excellent points
that illustrate that.

> no root account, but the first user has got sudo admin super cow powers,
> with a pure and clean enabled root account.

With the information supplied by Richard, I jumped to the conclusion
that he had disabled root logins - failing to consider that if such was
the case then root wouldn't have a password for him to know.

It does seem much more likely that Scott is correct and root logins are
only disabled at the graphical login - as Scott says, that is the
default configuration - in which case Richard should be able to
ctrl-alt-Fn to a virtual console, ctrl-alt-bspace to kill the X server
(though I think that's disabled since the last few releases), or boot
into recovery mode.

Without further input from Richard we have no way of knowing for certain
what the exact situation is.

Cheers,
Tom

-- 
All the men on my staff can type.
-- Bella Abzug


signature.asc
Description: Digital signature

Re: When fogetting assigned login name rather than password

[Ralf Mardorf]

On Sat, 2014-03-15 at 23:08 +1100, Scott Ferguson wrote:
> On 15/03/14 22:58, Ralf Mardorf wrote:
> > On Sat, 2014-03-15 at 22:53 +1100, Scott Ferguson wrote:
> >> On 15/03/14 22:43, Lisi Reisz wrote:
> >>> On Saturday 15 March 2014 11:33:50 Tom Furie wrote:
>  On Sat, Mar 15, 2014 at 12:22:10PM +0100, Ralf Mardorf wrote:
> > On Sat, 2014-03-15 at 05:45 -0500, Richard Owlett wrote:
> >> If another OS had not been available but I knew the root
> >> password, is there some way I could have gained access as root?
> >
> > If you remember the root password, than I don't understand your
> > problem.
> 
>  My first instinct would be to suppose that he's disabled root
>  logins.
> >>>
> >>> Then, Tom, why has Richard got a root password for the system?  Surely 
> >>> Debian only gives you the chance to set a root password if you enable 
> >>> root?
> >>
> >> 1++
> > 
> > Tom is smarter than we are, it's likely that his guess is correct. The
> > OP confused the term for
> > 
> > no root account, but the first user has got sudo admin super cow powers,
> > with a pure and clean enabled root account.
> > 
> > 
> 
> No root account?  (Is that a joke?)
> 
> I'm always learning and I'm keen to know how that is achieved - it
> sounds very unlikely
> 
> Would the rescue console still work?
> 
> I suspect you mean "no root login to the GUI" - which still leaves
> stopping the X Server with Ctrl+Alt+Backspace and logging in as root to
> the console - or Ctrl+Alt+F2 and logging in as root to the vconsole.

:D

I don't remember, perhaps I enabled a root account for this *buntu
install:

[rocketmouse@archlinux ~]$ sudo systemd-nspawn -D /mnt/saucy
Spawning container saucy on /mnt/saucy. Press ^] three times within 1s
to abort execution.
root@saucy:~# id rocketmouse
uid=1000(rocketmouse) gid=1000(rocketmouse)
groups=1000(rocketmouse),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),112(lpadmin),123(sambashare)
root@saucy:~# id root
uid=0(root) gid=0(root) groups=0(root)

However, there might always be a root account, but login, even to a
non-GUI terminal might be disabled ;).

I don't know if my saucy install has got root login enabled, but I
suspect I kept the *buntu defaults, without a root login.

Take an educated guess, IMO Tom's assumption is correct.



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1394886003.3587.144.camel@archlinux

Re: When fogetting assigned login name rather than password

[Scott Ferguson]

On 15/03/14 22:58, Ralf Mardorf wrote:
> On Sat, 2014-03-15 at 22:53 +1100, Scott Ferguson wrote:
>> On 15/03/14 22:43, Lisi Reisz wrote:
>>> On Saturday 15 March 2014 11:33:50 Tom Furie wrote:
 On Sat, Mar 15, 2014 at 12:22:10PM +0100, Ralf Mardorf wrote:
> On Sat, 2014-03-15 at 05:45 -0500, Richard Owlett wrote:
>> If another OS had not been available but I knew the root
>> password, is there some way I could have gained access as root?
>
> If you remember the root password, than I don't understand your
> problem.

 My first instinct would be to suppose that he's disabled root
 logins.
>>>
>>> Then, Tom, why has Richard got a root password for the system?  Surely 
>>> Debian only gives you the chance to set a root password if you enable 
>>> root?
>>
>> 1++
> 
> Tom is smarter than we are, it's likely that his guess is correct. The
> OP confused the term for
> 
> no root account, but the first user has got sudo admin super cow powers,
> with a pure and clean enabled root account.
> 
> 

No root account?  (Is that a joke?)

I'm always learning and I'm keen to know how that is achieved - it
sounds very unlikely

Would the rescue console still work?

I suspect you mean "no root login to the GUI" - which still leaves
stopping the X Server with Ctrl+Alt+Backspace and logging in as root to
the console - or Ctrl+Alt+F2 and logging in as root to the vconsole.

Kind regards


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/532442aa.5010...@gmail.com

Re: When fogetting assigned login name rather than password

[Ralf Mardorf]

On Sat, 2014-03-15 at 12:58 +0100, Ralf Mardorf wrote:
> On Sat, 2014-03-15 at 22:53 +1100, Scott Ferguson wrote:
> > On 15/03/14 22:43, Lisi Reisz wrote:
> > > On Saturday 15 March 2014 11:33:50 Tom Furie wrote:
> > >> On Sat, Mar 15, 2014 at 12:22:10PM +0100, Ralf Mardorf wrote:
> > >>> On Sat, 2014-03-15 at 05:45 -0500, Richard Owlett wrote:
> >  If another OS had not been available but I knew the root
> >  password, is there some way I could have gained access as root?
> > >>>
> > >>> If you remember the root password, than I don't understand your
> > >>> problem.
> > >>
> > >> My first instinct would be to suppose that he's disabled root
> > >> logins.
> > > 
> > > Then, Tom, why has Richard got a root password for the system?  Surely 
> > > Debian only gives you the chance to set a root password if you enable 
> > > root?
> > 
> > 1++
> 
> Tom is smarter than we are, it's likely that his guess is correct. The
> OP confused the term for
> 
> no root account, but the first user has got sudo admin super cow powers,
> with a pure and clean enabled root account.

IOW the OP remembers the password for UID 1000, but not the name for UID
1000 :D.



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1394884822.3587.140.camel@archlinux

Re: When fogetting assigned login name rather than password

[Ralf Mardorf]

On Sat, 2014-03-15 at 22:53 +1100, Scott Ferguson wrote:
> On 15/03/14 22:43, Lisi Reisz wrote:
> > On Saturday 15 March 2014 11:33:50 Tom Furie wrote:
> >> On Sat, Mar 15, 2014 at 12:22:10PM +0100, Ralf Mardorf wrote:
> >>> On Sat, 2014-03-15 at 05:45 -0500, Richard Owlett wrote:
>  If another OS had not been available but I knew the root
>  password, is there some way I could have gained access as root?
> >>>
> >>> If you remember the root password, than I don't understand your
> >>> problem.
> >>
> >> My first instinct would be to suppose that he's disabled root
> >> logins.
> > 
> > Then, Tom, why has Richard got a root password for the system?  Surely 
> > Debian only gives you the chance to set a root password if you enable 
> > root?
> 
> 1++

Tom is smarter than we are, it's likely that his guess is correct. The
OP confused the term for

no root account, but the first user has got sudo admin super cow powers,
with a pure and clean enabled root account.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1394884739.3587.139.camel@archlinux

Re: When fogetting assigned login name rather than password

[Scott Ferguson]

On 15/03/14 22:33, Tom Furie wrote:
> On Sat, Mar 15, 2014 at 12:22:10PM +0100, Ralf Mardorf wrote:
>> On Sat, 2014-03-15 at 05:45 -0500, Richard Owlett wrote:
> 
>>> If another OS had not been available but I knew the root 
>>> password, is there some way I could have gained access as
>>> root?
>> 
>> If you remember the root password, than I don't understand your
>> problem.
> 
> My first instinct would be to suppose that he's disabled root
> logins.

For the GUI perhaps - that's the default for the DE's I'm familiar
with - but it in no way prohibits logins to a vconsole. And AFAIK you
can simply kill the X server and login to the console that way.

> 
> Cheers, Tom
> 

Kind regards


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53244070.4040...@gmail.com

Re: When fogetting assigned login name rather than password

[Scott Ferguson]

On 15/03/14 22:43, Lisi Reisz wrote:
> On Saturday 15 March 2014 11:33:50 Tom Furie wrote:
>> On Sat, Mar 15, 2014 at 12:22:10PM +0100, Ralf Mardorf wrote:
>>> On Sat, 2014-03-15 at 05:45 -0500, Richard Owlett wrote:
 If another OS had not been available but I knew the root
 password, is there some way I could have gained access as root?
>>>
>>> If you remember the root password, than I don't understand your
>>> problem.
>>
>> My first instinct would be to suppose that he's disabled root
>> logins.
> 
> Then, Tom, why has Richard got a root password for the system?  Surely 
> Debian only gives you the chance to set a root password if you enable 
> root?

1++

> 
> Lisi
> 
> 


Kind regards


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53243f2d.5020...@gmail.com

Re: When fogetting assigned login name rather than password

[Ralf Mardorf]

On Sat, 2014-03-15 at 12:38 +0100, Ralf Mardorf wrote:
> On Sat, 2014-03-15 at 11:33 +, Tom Furie wrote:
> > On Sat, Mar 15, 2014 at 12:22:10PM +0100, Ralf Mardorf wrote:
> > > On Sat, 2014-03-15 at 05:45 -0500, Richard Owlett wrote:
> > 
> > > > If another OS had not been available but I knew the root 
> > > > password, is there some way I could have gained access as root?
> > > 
> > > If you remember the root password, than I don't understand your problem.
> > 
> > My first instinct would be to suppose that he's disabled root logins.
> 
> My apologise, that's a good thought. For my Debian and Arch installs I
> have a root account + the ability to use sudo.

PS:

That explains the reason for this:

> I solved the immediate problem by rebooting to the install on sda1 and
> using it to examine /etc/passwd on sda7.

I was completely wrong, while Scott at least had no doubts about UID
1000 :D. JFTR the default UID for the first user, when using FreeBSD is
1001, however, for all Linux distros I ever used it was 1000.

But Tom seems to be the only smart person among us :(, so an abuse to
the OT: NEXT TIME DON'T CALL THE FIRST USER "ROOT" :(. Especially not
when it's weekend and people tend to turn of their brains.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1394884358.3587.136.camel@archlinux

Re: When fogetting assigned login name rather than password

[Scott Ferguson]

On 15/03/14 22:29, Tom Furie wrote:
> On Sat, Mar 15, 2014 at 10:09:33PM +1100, Scott Ferguson wrote:
>> On 15/03/14 21:45, Richard Owlett wrote:
> 
>>> If another OS had not been available but I knew the root
>>> password, is there some way I could have gained access as
>>> root?
> 
>> # passwd `grep 1000 /etc/passwd | cut -d : -f1`
> 
> That doesn't help him until he's logged into the system.

Richard has clearly said "if I knew the root password" "as root"
So he *can* login to the system.
Why he didn't, is the question. ;)

Perhaps he tried from a GUI login which only permitted a userlogin
(but didn't prompt with the username and didn't, or couldn't
(Crtl+backspace etc) didn't work - still wouldn't explain why he
didn't just boot into the rescue console. Perhaps his fu was low?

> 
> Cheers, Tom
> 


Kind regards


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53243ec2.7060...@gmail.com

Re: Debian + Dell + double screen

[Lisi Reisz]

On Saturday 15 March 2014 02:37:10 Chris Bannister wrote:
> On Fri, Mar 14, 2014 at 09:30:48AM +0400, Dmitrii Kashin wrote:
> > Didn't I ask you not to send me a carbon copy? :/
>
> http://www.debian.org/MailingLists/#codeofconduct
>
> " * If you want to complain to someone who sent you a carbon copy
> when you did not ask for it, do it privately."

It was - probably in error - addressed to the list, with no indication 
of who had perpetrated the crime. :-/  It read as though the whole 
list had.

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201403151146.32317.lisi.re...@gmail.com

Re: When fogetting assigned login name rather than password

[Scott Ferguson]

On 15/03/14 22:29, Ralf Mardorf wrote:
> On Sat, 2014-03-15 at 22:09 +1100, Scott Ferguson wrote:
>> passwd `grep 1000 /etc/passwd | cut -d : -f1`
> 
> Likely that it's 1000, but it could be another uid ;p.
> 
> 
> 


Could be, but very unlikely - it's the default first UID, and will be
Richard's "user" (his posting history suggest he meant singular) unless
he did something strange e.g. set UID 1000 to /bin/false as the login.

This is Debian, Arch may be different (I don't know).

Kind regards


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53243d7d.1070...@gmail.com

Re: When fogetting assigned login name rather than password

[Lisi Reisz]

On Saturday 15 March 2014 11:33:50 Tom Furie wrote:
> On Sat, Mar 15, 2014 at 12:22:10PM +0100, Ralf Mardorf wrote:
> > On Sat, 2014-03-15 at 05:45 -0500, Richard Owlett wrote:
> > > If another OS had not been available but I knew the root
> > > password, is there some way I could have gained access as root?
> >
> > If you remember the root password, than I don't understand your
> > problem.
>
> My first instinct would be to suppose that he's disabled root
> logins.

Then, Tom, why has Richard got a root password for the system?  Surely 
Debian only gives you the chance to set a root password if you enable 
root?

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201403151143.20275.lisi.re...@gmail.com

Re: When fogetting assigned login name rather than password

[Ralf Mardorf]

On Sat, 2014-03-15 at 11:33 +, Tom Furie wrote:
> On Sat, Mar 15, 2014 at 12:22:10PM +0100, Ralf Mardorf wrote:
> > On Sat, 2014-03-15 at 05:45 -0500, Richard Owlett wrote:
> 
> > > If another OS had not been available but I knew the root 
> > > password, is there some way I could have gained access as root?
> > 
> > If you remember the root password, than I don't understand your problem.
> 
> My first instinct would be to suppose that he's disabled root logins.

My apologise, that's a good thought. For my Debian and Arch installs I
have a root account + the ability to use sudo.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1394883514.3587.129.camel@archlinux

Re: When fogetting assigned login name rather than password

[Ralf Mardorf]

On Sat, 2014-03-15 at 11:29 +, Tom Furie wrote:
> On Sat, Mar 15, 2014 at 10:09:33PM +1100, Scott Ferguson wrote:
> > On 15/03/14 21:45, Richard Owlett wrote:
> 
> > > If another OS had not been available but I knew the root password, is
> > > there some way I could have gained access as root?
> 
> > # passwd `grep 1000 /etc/passwd | cut -d : -f1`
> 
> That doesn't help him until he's logged into the system.

On Sat, 2014-03-15 at 05:45 -0500, Richard Owlett wrote:
> I knew the root password

It likely does help him, my hint anyway is better than Scott's, because
it's possible that the UID isn't 1000.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1394883193.3587.127.camel@archlinux

Re: When fogetting assigned login name rather than password

[Tom Furie]

On Sat, Mar 15, 2014 at 12:22:10PM +0100, Ralf Mardorf wrote:
> On Sat, 2014-03-15 at 05:45 -0500, Richard Owlett wrote:

> > If another OS had not been available but I knew the root 
> > password, is there some way I could have gained access as root?
> 
> If you remember the root password, than I don't understand your problem.

My first instinct would be to suppose that he's disabled root logins.

Cheers,
Tom

-- 
For every action, there is an equal and opposite criticism.
-- Harrison


signature.asc
Description: Digital signature

Re: When fogetting assigned login name rather than password

[Tom Furie]

On Sat, Mar 15, 2014 at 10:09:33PM +1100, Scott Ferguson wrote:
> On 15/03/14 21:45, Richard Owlett wrote:

> > If another OS had not been available but I knew the root password, is
> > there some way I could have gained access as root?

> # passwd `grep 1000 /etc/passwd | cut -d : -f1`

That doesn't help him until he's logged into the system.

Cheers,
Tom

-- 
Love is staying up all night with a sick child, or a healthy adult.


signature.asc
Description: Digital signature

Re: When fogetting assigned login name rather than password

[Ralf Mardorf]

On Sat, 2014-03-15 at 22:09 +1100, Scott Ferguson wrote:
> passwd `grep 1000 /etc/passwd | cut -d : -f1`

Likely that it's 1000, but it could be another uid ;p.



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1394882958.3587.124.camel@archlinux

Re: When fogetting assigned login name rather than password

[Ralf Mardorf]

On Sat, 2014-03-15 at 05:45 -0500, Richard Owlett wrote:
> If another OS had not been available but I knew the root 
> password, is there some way I could have gained access as root?

If you don't remember the root's password you need to chroot or
systemd-nspawn -D. A hint that very often is censored by German forum
admins :D.

If you remember the root password, than I don't understand your problem.

An idiotic script I don't use, but I wrote to reply to a different, but
similar question:

[rocketmouse@archlinux ~]$ cat /usr/local/bin/chpassword 
#!/bin/sh

echo -n "Change password of user: "
read username
echo -n "Do it being user: "
read su_user
if [ "$(id -u)" != "0" ]; then echo -n "$su_user's "; fi
su $su_user -c "passwd $username"
echo "Push enter to quit."
read push_rtn

exit

IOW if you could become root, you could do what ever you want. Take a
look at what users have an account and change the password of the user
you want. You can see all users by   $ cat /etc/passwd   assumed you
forget a username.

You can't see the password a user used, but you can change the password,
without knowing the user's password.



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1394882530.3587.122.camel@archlinux

Re: When fogetting assigned login name rather than password

[Scott Ferguson]

On 15/03/14 21:45, Richard Owlett wrote:
> I'm running a series of experiments installing multiple versions of
> Squeeze on a dedicated machine. The machine is dedicated to
> experimentation and the lifetime of any install may intentionally be
> only hours or days.
> 
> The complete hard drive is wiped at least once a month. I consistently
> use my name as the login on the first install of any series. The login
> of any subsequent install will be a mnemonic associated associated with
> the current experiment.
> 
> I just tried to bring up an install without a GUI. I had forgotten the
> login name I had assigned a week ago. I solved the immediate problem by
> rebooting to the install on sda1 and using it to examine /etc/passwd on
> sda7.
> 
> If another OS had not been available but I knew the root password, is
> there some way I could have gained access as root?
> 
> TIA
> 
> 
> 
> 
> 

# passwd `grep 1000 /etc/passwd | cut -d : -f1`


Kind regards






-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/532434ed.5000...@gmail.com

Re: When fogetting assigned login name rather than password

[Tom Furie]

On Sat, Mar 15, 2014 at 05:45:14AM -0500, Richard Owlett wrote:

> If another OS had not been available but I knew the root password,
> is there some way I could have gained access as root?

The classic approach to this problem is to pass 'init=/bin/sh' to the
kernel. The method for doing so depends on which boot manager you might
be using.

Cheers,
Tom

-- 
To be a kind of moral Unix, he touched the hem of Nature's shift.
-- Shelley


signature.asc
Description: Digital signature

When fogetting assigned login name rather than password

[Richard Owlett]

I'm running a series of experiments installing multiple versions 
of Squeeze on a dedicated machine. The machine is dedicated to 
experimentation and the lifetime of any install may intentionally 
be only hours or days.


The complete hard drive is wiped at least once a month. I 
consistently use my name as the login on the first install of any 
series. The login of any subsequent install will be a mnemonic 
associated associated with the current experiment.


I just tried to bring up an install without a GUI. I had 
forgotten the login name I had assigned a week ago. I solved the 
immediate problem by rebooting to the install on sda1 and using 
it to examine /etc/passwd on sda7.


If another OS had not been available but I knew the root 
password, is there some way I could have gained access as root?


TIA





--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/53242f3a.7070...@cloud85.net

Re: On what is helpful and what is not [was: Re: Wifi]

[Ralf Mardorf]

On Fri, 2014-03-14 at 23:07 -0700, Robert Holtzman wrote:
> On Sat, Mar 15, 2014 at 10:35:03AM +1100, Zenaan Harkness wrote:
> > [snip]
> 
> +1
> 
> I remember reading some advice to a new internet user: "grow a thick
> skin".

+1

But that doesn't solve some serious issues Zenaan, some others and I
dislike, where ever we live on that planet.

For good reason's some of us are talking about it off-list, by a group
of people from this list and also "between you and me and the gatepost",
sometimes using the annoying openPGP.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1394875670.3587.76.camel@archlinux

Re: how to change double click as the middle button

[lina]

> 
> Here I upload the log file
> 
> https://drive.google.com/file/d/0B5Gxp2s4pGp8YjlPRmp3Z2txMjA/edit?usp=sharing
> 
> I have problem figuring out which configures files it used, I tested it
> is unlikely it uses what is inside the xorg.conf.d in the end.
> 
> Thanks,
> 

It is likely that some default xfce configuration has overridden the
synaptic configuration in /etc/X11/xorg.conf.d/

Setting -> Mouse and Touchpad ->  lack the setting for the two taps and
three taps.

Just in this couple of days, my finger has been trained to adapt this
new way of doing things. haha ... seems lack the needs to change it
back. But still good to know how to set the two taps and three taps in
xfce.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53241939.4010...@gmail.com

Re: running qemu and gns3 on debian

[Fatemeh m]

Hi all,

I still can't solve my problem completely. In GNS3 environment, I managed
to run Qemu node console without KVM only option but If I check the KVM
only box, console section won't work for my qemu node.

These are the steps I followed on Debian wheezy:
1. Install gns3 0.8.2 using tar.gz file
2. Install qemu 0.11.0 using using tar.gz file
3. test connection for dynamips and qemu---> start
4. In qemu guest: I set a vyatta image and check the "Use kvm".
5- Drag a qemu guest and connect it to a cisco router, and start them all.

When I click on console of qemu node to set ip and alike, it flashes
suddenly and disappeared.

I searched for it a lot but I couldn't solve this problem; I need your
help, any hints are really appriciated by me. Thanks for your time.


On Thu, Mar 13, 2014 at 9:53 AM, Fatemeh m  wrote:

> Hi,
> I installed *gns3* and *qemu* from this 
> site
> .
>
> I want to run a topology on *gns3*. the topology is:
> Qemu Host1---R1(3600)---Qemu host 2
>
> The problem is when I want to open console for *Qemu* it flashes and
> doesn't open at all!
>
> I', soory if I shouldn't ask this kind f qestion here.
>
> Thanks.
>
>

Re: On what is helpful and what is not [was: Re: Wifi]

[Robert Holtzman]

On Sat, Mar 15, 2014 at 10:35:03AM +1100, Zenaan Harkness wrote:
> On 3/15/14, John L. Ries  wrote:
> > On Fri, 14 Mar 2014, Tom H wrote:
> >
> >> On Tue, Mar 11, 2014 at 3:42 AM, Jonathan Dowland 
> >> wrote:
> >>> On Tue, Mar 11, 2014 at 01:10:11PM +1100, Charlie Schroeder wrote:
> 
>  Life isn't about second guessing if you write or speak to someone if
>  they will take offence surely? Isn't it so that you say your piece and
>  people can take it or leave it. It's up to them.
> >>>
> >>> "Life" and the Debian user mailing list are not the same thing. You can
> >>> make your own rules as to how you life and act within your own life, but
> >>> within a community one must abide the community rules. At the moment,
> >>> there's nothing explicitly written that dictates that one should be
> >>> polite, respectful, avoid causing offence, etc., for the Debian
> >>> community nor this mailing list. This is a bug which should be fixed and
> >>> the project is considering the adoption of a 'code of conduct' which
> >>> will replace the existing mailing list CoC. The text of the proposal is
> >>> here[1]. Of particular relevance here is, I think, "a community in which
> >>> people feel threatened is not a healthy community".
> >>>
> >>> [1] https://lists.debian.org/debian-project/2014/02/msg00069.html
> >>
> >> It's sad that Debian's demeaning itself with this politically-correct
> >> rubbish.
> >
> > Would "politically correct" in this context be a perjorative for "polite"?
> >
> > It's one thing to complain about efforts to accomodate the political
> > sensibilities of others and to hide one's own, but quite a few people now
> > seem to regard courtesy itself as a vice.

  ..snip..
> 
> 
> 
> I think that in the long term, as the debian community (developers)
> formalise things like this, there are certain definite potential
> problems (in the long term), and frankly, I think it will be a very
> good thing for the community to go through those problems, because
> evidently it is only in the hindsight of actually experiencing such
> problems that many people can realise those problems, or see the folly
> of the things they do now - like formalising politeness into
> legislation (Debian policy) and formalising and condoning activities
> such as clandestine censorship (sorry, 'moderation') in the name of
> not offending the person who has apparently so offended the community
> that they ought be not offended by any public record of the moderation
> of them or their post(s).
> 
> I predict the following, and mark my words: future and greater
> problems will arise directly from this policy (if this policy gets
> voted in by the developers) which future problems will only be seen by
> many through the experience of those problems (as in, bigger problems
> than the ones supposedly being 'solved' today).

+1

I remember reading some advice to a new internet user: "grow a thick
skin". Don't remember but it remains damned good advice.

In any event I strongly suggest reading/rereading

http://www.catb.org/~esr/faqs/smart-questions.html 

before rushing the publication of anything formal. Perhaps citing that
to problem posters might help, perhaps not. In any event, in my not so
humble opinion, thin skinned people have no business on the internet. 

-- 
Bob Holtzman
Your mail is being read by tight lipped 
NSA agents who fail to see humor in Doctor 
Strangelove 
Key ID 8D549279


signature.asc
Description: Digital signature