Re: Debian Install

[chrisb]

On Wed, Apr 06, 2016 at 07:25:25PM -0400, Ethan Rosenberg wrote:
> 
> DVD

Set the bios to first try and boot from the DVD.


-- 
The media's the most powerful entity on earth. 
They have the power to make the innocent guilty 
and to make the guilty innocent, and that's power.
 -- Malcolm X

Re: How to debug systemd script?

[chrisb]

On Mon, Mar 28, 2016 at 04:02:20PM +0100, Oliver Elphick wrote:
> On Tue, 2016-03-29 at 02:33 +1300, chrisb@localhost.localdomain wrote:
> > On Mon, Mar 28, 2016 at 01:00:35PM +0100, Oliver Elphick wrote:
> > > How can I find out what is going on to stop the normal init script
> > > from
> > > working? Is there some way to force systemctl to log what it is
> > > doing?
> > > If it does log, where does it put the log?
> > See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731862
> > 
> > Near the very end it suggests:
> > strace -f -o /tmp/strace.log -s 2048 -p 1 & systemctl restart
> > postgresql.service
> 
> In fact the other suggestion there, of suppressing the redirect to
> systemctl, proved helpful. the problem is actually in postgresql-
> common, in a Perl script.

Could you be more specific? Someone else may come across the same 
problem.

-- 
The media's the most powerful entity on earth. 
They have the power to make the innocent guilty 
and to make the guilty innocent, and that's power.
 -- Malcolm X

Re: How to debug systemd script?

[chrisb]

On Mon, Mar 28, 2016 at 01:00:35PM +0100, Oliver Elphick wrote:
> I have installed Debian alongside Linux Mint and wish to have
> PostgreSQL use the same database.  So I have copied the system
> configuration files in /etc/postgresql from the Linux Mint partition.
> They point to the PostgreSQL data files in /lvhome/postgresql.  
> 
> This works in Linux Mint but not in Debian; PostgreSQL does not start.
> There is nothing in the logs of either system or PostgreSQL. It works
> if I call pg_ctl or if I run postgres directly.
> 
> I put set -x in the init script. When it is run, we see:
> 
> # /etc/init.d/postgresql start
> ...
> + echo -n Starting postgresql (via systemctl): postgresql.service
> Starting postgresql (via systemctl): postgresql.service+
> log_daemon_msg_post Starting postgresql (via systemctl)
> postgresql.service
> + :
> + /bin/systemctl start postgresql.service
> + rc=0
> ...
> 
> 
> There is a long pause at /bin/systemctl, but no error is indicated.
> However, the server is not started.
> 
> How can I find out what is going on to stop the normal init script from
> working? Is there some way to force systemctl to log what it is doing?
> If it does log, where does it put the log?

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731862

Near the very end it suggests:
strace -f -o /tmp/strace.log -s 2048 -p 1 & systemctl restart postgresql.service

Then, after a couple of seconds, fg into the strace process, cancel it, and then
see it the strace.log helps.

-- 
The media's the most powerful entity on earth. 
They have the power to make the innocent guilty 
and to make the guilty innocent, and that's power.
 -- Malcolm X

Re: Changing Boot Order

[chrisb]

On Sat, Mar 26, 2016 at 06:35:36PM +0100, jdd wrote:
> Le 26/03/2016 17:11, Alan McConnell a écrit :
> 
> >  Press  to run BIOS setup, or  to run boot menu
^^^
Weird ... I guess that is supposed to be F11, which makes me wonder 
is the shift key held down or what?

-- 
The media's the most powerful entity on earth. 
They have the power to make the innocent guilty 
and to make the guilty innocent, and that's power.
 -- Malcolm X

Re: systemd troubleshooting (was ... Re: computer cann't shut down)

[chrisb]

On Wed, Mar 23, 2016 at 10:00:53AM -0500, David Wright wrote:
> Now, every time there's a security fix, you're going to be quizzed
> over what to do about your modified configuration file because Debian
> wants to overwrite your modified /etc/systemd/system/foo.target.

Umm, guess what the normal current behaviour is.

> Or at some time in the future, you decide to revert to the Debian
> version. 

It's more often than not a particular feature or option you want to 
change, right? 

> You have to juggle the files /etc/systemd/system/foo.target
> and /etc/systemd/system/foo.target.orig instead of just removing
> the link /etc/systemd/system/foo.target -> /lib/systemd/system/foo.target
> 
> > or
> > /usr/share/doc/systemd/system/halt.target.default ?

You do comment your configuration files, right? 
Also do you delete old configuration options or comment out the line?

[snipped personal preference stuff]

-- 
The media's the most powerful entity on earth. 
They have the power to make the innocent guilty 
and to make the guilty innocent, and that's power.
 -- Malcolm X

Re: Installing newer kernels

[chrisb]

On Thu, Mar 24, 2016 at 08:29:40AM +, Curt wrote:
> On 2016-03-24, David Christensen  wrote:
> > On 03/23/2016 07:46 PM, John Hasler wrote:
> >> David Christensen writes:
> >>> If I am running version N, have changed the configuration file to M',
> >>> and then upgrade to version N+1, you're saying dist-upgrade throws
> >>> away +X and -Y.  I may want or need those.
> >>
> >> The package management system will notice that you have changed the
> >> file.  You will be asked if you want to keep the old version, install
> >> the new one, look at a diff, or shell out and do something else.
> >
> > Okay -- not as grim as I thought.
> 
> Yeah, it's like there are people behind the scenes thinking these things
> out ahead of time or something! 

Yeah, it's a scary thought! Takes a bit of time to get used to if you migrate 
here from *another* OS. :)

-- 
The media's the most powerful entity on earth. 
They have the power to make the innocent guilty 
and to make the guilty innocent, and that's power.
 -- Malcolm X

systemd troubleshooting (was ... Re: computer cann't shut down)

[chrisb]

On Mon, Mar 21, 2016 at 10:44:24AM -0700, Lotek wrote:
> On 03/19/2016 05:40 AM, lina wrote:
> >Every time since I installed the system,
> >
> >every time I tried Shut Down, it mainly restart again.
> >
> >I checked online and tried several methods but still don't work.
> >
> >Can anyone suggest me how to solve it.
> >
> >Thanks,
> 
> The problem might be with systemd.  Check the link
> "/lib/systemd/system/@ctrl-alt-del.target".  If it points to
> "reboot.target", copy the "@ctrl-alt-del.target" link to
> "/etc/systemd/system".  Then point the new link to
> "/lib/systemd/system/halt.target".

*groan* so configuration is not confined to /etc/ anymore?
If everything works with systemd it's great, but otherwise 
it is a PITA esp, with Debian only changes where the normal
info doesn't apply. 

-- 
The media's the most powerful entity on earth. 
They have the power to make the innocent guilty 
and to make the guilty innocent, and that's power.
 -- Malcolm X

Re: Installing newer kernels

[chrisb]

On Fri, Mar 18, 2016 at 10:52:25PM +, Brian wrote:
> William Lee Valentine's only post is about installing newer kernels and
> has nothing to with booting a Debian image.

Which probably means he wasn't subscribed. :(

-- 
The media's the most powerful entity on earth. 
They have the power to make the innocent guilty 
and to make the guilty innocent, and that's power.

Re: Installing newer kernels

[chrisb]

On Fri, Mar 18, 2016 at 06:40:18PM -0700, David Christensen wrote:
> On 03/18/2016 02:13 PM, Curt wrote:
> >I have never had a failed dist-upgrade. Of course, you gotta follow the
> >goddamn directions, do about five or ten minutes of reading of the
> >appropriate material, which isn't too much to ask I wouldn't think.
> >
> >This wipe business strikes me as vaguely scatological.  Clean and
> >cruftless and wiped (and do they wash their hands fifty times a day
> >too, just to be impeccable)?
> 
> I'm not a good Debian owner.  I download and install 3rd party software.  I
> modify system configuration files.

As do most of us. An upgrade won't overwrite configuration file changes whereas 
with
a new install you do lose them!

-- 
The media's the most powerful entity on earth. They have the power
to make the innocent guilty and to make the guilty innocent, and that's power.