This was a simple matter of sound card settings. After upgrade, sound
is defaulting to a different port than before--"headphones" rather
than "line out". changing selection to "line out" enables sound.
However, the settings change does not survive rebooting. Silly, I
know. Just wanted to clean up
Hi all,
After distribution upgrade to jessie sound no longer works.
If user kills pulseaudio process, these warnings appear in "messages"
log when pulseaudio respawns:
gnome-session: (gnome-settings-daemon:1466): media-keys-plugin-WARNING
**: Unable to get default sink
and
gnome-session: (gnom
There has been some mention of booting UEFI systems in
this thread. This appears to be a comprehensive resource:
http://www.rodsbooks.com/efi-bootloaders/index.html
Many bootloaders are covered, and the author also
mentions his own project, rEFInd
http://www.rodsbooks.com/refind/
cheers,
--
On Sun 10 Jul 2016 at 08:38:15 -0500, Richard Owlett wrote:
> On 7/9/2016 4:00 PM, Stephen Powell wrote:
> >[snip]
> >>What I'd like to find which I've had no luck with so far, is finding a
> >>Debian
> >>installer cmdline option to skip the waste of time that is installation of
> >>any bootloade
On 7/9/2016 4:00 PM, Stephen Powell wrote:
[snip]
What I'd like to find which I've had no luck with so far, is finding a Debian
installer cmdline option to skip the waste of time that is installation of
any bootloader. My disks get generic MBR code and Grub installed by me before
any OS gets ins
On Sun, Jul 10, 2016, at 03:31, Pascal Hambourg wrote:
>
> AFAICS, elilo is not available any more in stretch and sid.
>
I'm sorry to hear that. I don't have any UEFI-based systems right now, so
it's not an issue for me -- yet. But it may be someday. On the other hand,
CSM-less UEFI systems ma
On Sun 10 Jul 2016 at 10:31:38 +0200, to...@tuxteam.de wrote:
> On Sat, Jul 09, 2016 at 11:15:08PM +0100, Brian wrote:
>
> [...]
>
> > This is a common misconception. Debian is about providing the best free
> > operating system possible.
>
> In your humble opinion.
>
> (sorry, I know I'm feedi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Jul 09, 2016 at 11:15:08PM +0100, Brian wrote:
[...]
> This is a common misconception. Debian is about providing the best free
> operating system possible.
In your humble opinion.
(sorry, I know I'm feeding it, but I couldn't resist).
- --
Le 09/07/2016 à 22:41, Stephen Powell a écrit :
So I'm not concerned about it's maintenance status. As long as there are
PCs with a BIOS, or a CSM, lilo will remain usable. If the BIOS/CSM goes,
lilo goes with it. lilo can't function without a BIOS/CSM. But for UEFI-only
systems, there's elil
Le 09/07/2016 à 22:00, Brian a écrit :
All well and good but the installer inexplicably offers a choice between
GRUB and LILO. The installer manual is unhelpful on which to choose. A
newcomer wouldn't have a clue. We do them no service with this retrograde
offering. Get rid of it.
What is the p
Stephen Powell wrote:
> As far as LILO being unmaintained is concerned, I wouldn't be too concerned
> about that. I've been thinking about offering to maintain it myself. I
> haven't
> heard from Joachim lately. Maybe I'll drop him another line.
I think LILO is an important part of Linux infra
On Sat, Jul 9, 2016, at 18:25, Brian wrote:
> On Sat 09 Jul 2016 at 16:41:24 -0400, Stephen Powell wrote:
>>
>> Long live choice!
>
> For choice to exist it does not have to be presented as such in the
> installer.
>
Your point is well taken. The installer does not offer choice in everything,
j
Brian composed on 2016-07-09 21:00 (UTC+0100):
...the installer inexplicably offers a choice between
GRUB and LILO. The installer manual is unhelpful on which to choose. A
newcomer wouldn't have a clue. We do them no service with this retrograde
offering. Get rid of it.
Probably a Bad idea. Ap
On Sat 09 Jul 2016 at 16:41:24 -0400, Stephen Powell wrote:
> On Sat, Jul 9, 2016, at 16:00, Brian wrote:
> >
> > All well and good but the installer inexplicably offers a choice between
> > GRUB and LILO. The installer manual is unhelpful on which to choose. A
> > newcomer wouldn't have a clue.
On Sat 09 Jul 2016 at 22:05:45 +0200, Erwan David wrote:
> Le 09/07/2016 à 22:00, Brian a écrit :
> >
> > What is the point of a choice? Just offer GRUB; it is the bootloader for
> > Debian and has many advantages over LILO in todayss Linux ecosystem.
> > People who have a great desire to use LIL
On Sat, Jul 9, 2016, at 16:33, Felix Miata wrote:
>
> All that's well and good, but I see nothing there that equates to my
> understanding of the meaning of "editing", which includes removal as well as
> appending.
Oh, I see what you're saying. Well, the Linux kernel generally does it's own
ov
On Sat, Jul 9, 2016, at 16:00, Brian wrote:
>
> All well and good but the installer inexplicably offers a choice between
> GRUB and LILO. The installer manual is unhelpful on which to choose. A
> newcomer wouldn't have a clue. We do them no service with this retrograde
> offering. Get rid of it.
>
Erwan David composed on 2016-07-09 22:05 (UTC+0200):
Brian composed:
What is the point of a choice? Just offer GRUB; it is the bootloader for
Debian...
What is the point of a choice, just use the windows provided with your PC...
:-D
Linux and debian is just about choice given to the us
Stephen Powell composed on 2016-07-09 13:19 (UTC-0400):
Felix Miata wrote:
Stephen Powell composed on 2016-07-09 08:58 (UTC-0400):
As for features, LILO has all the features that I need.
One feature it never acquired AFAIK, which Grub shares with Syslinux, is the
Le 09/07/2016 à 22:00, Brian a écrit :
>
> What is the point of a choice? Just offer GRUB; it is the bootloader for
> Debian and has many advantages over LILO in todayss Linux ecosystem.
> People who have a great desire to use LILO can search it out.
>
> Unmaintained in Debian, The bit-rot starts
On Sat 09 Jul 2016 at 13:19:08 -0400, Stephen Powell wrote:
> On Sat, Jul 9, 2016, at 10:53, Felix Miata wrote:
> > Stephen Powell composed on 2016-07-09 08:58 (UTC-0400):
> >
> >> As for features, LILO has all the features that I need.
> >
> > One feature it never acquired AFAIK, which Grub sha
On Sat, Jul 9, 2016, at 10:53, Felix Miata wrote:
> Stephen Powell composed on 2016-07-09 08:58 (UTC-0400):
>
>> As for features, LILO has all the features that I need.
>
> One feature it never acquired AFAIK, which Grub shares with Syslinux, is the
> ability to edit the kernel cmdline at boot t
Stephen Powell composed on 2016-07-09 08:58 (UTC-0400):
As for features, LILO has all the features that I need.
One feature it never acquired AFAIK, which Grub shares with Syslinux, is the
ability to edit the kernel cmdline at boot time, before kernel load. With
problematic hardware, problem
On Thu, Jul 7, 2016, at 20:53, Felix Miata wrote:
> Stephen Powell composed on 2016-07-07 20:30 (UTC-0400):
>
> > If your system has a BIOS and a traditional DOS-style partition table,
> > there's no reason not to use LILO, unless you just don't want to.
>
> Or, if you like to be able to boot wit
On 08/07/16 07:06 PM, Brian wrote:
On Fri 08 Jul 2016 at 18:13:01 -0400, Gary Dale wrote:
On 08/07/16 02:19 PM, Brian wrote:
If you have some way of easily adjusting files in /etc/grub.d to the
needs of a user I wish you would say.
So that's the problem. You never took the time to RTFM. See
h
On Fri 08 Jul 2016 at 18:13:01 -0400, Gary Dale wrote:
> >>On 08/07/16 02:19 PM, Brian wrote:
> >
> >If you have some way of easily adjusting files in /etc/grub.d to the
> >needs of a user I wish you would say.
> So that's the problem. You never took the time to RTFM. See
> https://help.ubuntu.com
On Fri 08 Jul 2016 at 16:57:30 -0500, David Wright wrote:
> On Fri 08 Jul 2016 at 21:16:00 (+0100), Brian wrote:
>
> > Stop moaning. Do it or file file a bug, Then stop moaning and do it.
>
> I'm the person without a complaint about Grub2, not the one moaning.
Apologies. I was intending to talk
On 08/07/16 03:51 PM, Brian wrote:
On Fri 08 Jul 2016 at 15:08:21 -0400, Gary Dale wrote:
On 08/07/16 02:19 PM, Brian wrote:
On Thu 07 Jul 2016 at 23:34:11 -0400, Gary Dale wrote:
On 07/07/16 05:12 PM, Brian wrote:
On Thu 07 Jul 2016 at 15:18:05 -0400, Gary Dale wrote:
On 07/07/16 02:55
On Fri 08 Jul 2016 at 21:16:00 (+0100), Brian wrote:
> On Fri 08 Jul 2016 at 14:23:01 -0500, David Wright wrote:
> > On Fri 08 Jul 2016 at 19:19:00 (+0100), Brian wrote:
> > > On Thu 07 Jul 2016 at 23:34:11 -0400, Gary Dale wrote:
> > > > On 07/07/16 05:12 PM, Brian wrote:
> > > > >On Thu 07 Jul 20
On Fri 08 Jul 2016 at 14:23:01 -0500, David Wright wrote:
> On Fri 08 Jul 2016 at 19:19:00 (+0100), Brian wrote:
> > On Thu 07 Jul 2016 at 23:34:11 -0400, Gary Dale wrote:
> > > On 07/07/16 05:12 PM, Brian wrote:
> > > >On Thu 07 Jul 2016 at 15:18:05 -0400, Gary Dale wrote:
> > > >>On 07/07/16 02:
On Fri 08 Jul 2016 at 15:08:21 -0400, Gary Dale wrote:
> On 08/07/16 02:19 PM, Brian wrote:
> >On Thu 07 Jul 2016 at 23:34:11 -0400, Gary Dale wrote:
> >
> >>On 07/07/16 05:12 PM, Brian wrote:
> >>>On Thu 07 Jul 2016 at 15:18:05 -0400, Gary Dale wrote:
> >>>
> On 07/07/16 02:55 PM, David Wrigh
On Fri 08 Jul 2016 at 19:19:00 (+0100), Brian wrote:
> On Thu 07 Jul 2016 at 23:34:11 -0400, Gary Dale wrote:
> > On 07/07/16 05:12 PM, Brian wrote:
> > >On Thu 07 Jul 2016 at 15:18:05 -0400, Gary Dale wrote:
> > >>On 07/07/16 02:55 PM, David Wright wrote:
> > >>>On Thu 07 Jul 2016 at 14:39:51 (-04
On 08/07/16 02:19 PM, Brian wrote:
On Thu 07 Jul 2016 at 23:34:11 -0400, Gary Dale wrote:
On 07/07/16 05:12 PM, Brian wrote:
On Thu 07 Jul 2016 at 15:18:05 -0400, Gary Dale wrote:
On 07/07/16 02:55 PM, David Wright wrote:
On Thu 07 Jul 2016 at 14:39:51 (-0400), Gary Dale wrote:
The big sel
On Thu 07 Jul 2016 at 23:34:11 -0400, Gary Dale wrote:
> On 07/07/16 05:12 PM, Brian wrote:
> >On Thu 07 Jul 2016 at 15:18:05 -0400, Gary Dale wrote:
> >
> >>On 07/07/16 02:55 PM, David Wright wrote:
> >>>On Thu 07 Jul 2016 at 14:39:51 (-0400), Gary Dale wrote:
> The big selling feature of Gru
Gary Dale composed on 2016-07-07 14:39 (UTC-0400):
It also has a "rescue shell" that I've never been able to do anything
useful with. When grub fails, I boot from a rescue cd instead. That way
I get a real working environment.
The Grub shell works the same whether in boot rescue mode or run fr
On 07/07/16 05:12 PM, Brian wrote:
On Thu 07 Jul 2016 at 15:18:05 -0400, Gary Dale wrote:
On 07/07/16 02:55 PM, David Wright wrote:
On Thu 07 Jul 2016 at 14:39:51 (-0400), Gary Dale wrote:
The big selling feature of Grub over Lilo was that it didn't need to
updated each time you changed somet
Stephen Powell composed on 2016-07-07 20:30 (UTC-0400):
If your system has a BIOS and a traditional DOS-style partition table,
there's no reason not to use LILO, unless you just don't want to.
Or, if you like to be able to boot without hunting down rescue media even
though you forgot to "reru
On Thu, Jul 7, 2016, at 10:57, Giovanni Gigante wrote:
>
> At the end, I decided to try the upgrade to jessie with LiLo (24.1) in
> place. I thought that the probability of hitting some bug caused by the
> interaction between LiLo and the upgraded distribution was less than the
> probabily of c
On 07/07/2016 05:47 PM, rhkra...@gmail.com wrote:
I'll take advantage of this thread to ask a question / express my frustration
with grub:
The thing that always frustrated me about grub is that, iirc, they counted
disks / partitions different than lilo and the rest of Linux--they start
countin
On 07/07/2016 05:47 PM, rhkra...@gmail.com wrote:
I'll take advantage of this thread to ask a question / express my frustration
with grub:
The thing that always frustrated me about grub is that, iirc, they counted
disks / partitions different than lilo and the rest of Linux--they start
countin
I'll take advantage of this thread to ask a question / express my frustration
with grub:
The thing that always frustrated me about grub is that, iirc, they counted
disks / partitions different than lilo and the rest of Linux--they start
counting at 1 (like Windows, iirc), and lilo and Linux sta
On Thu 07 Jul 2016 at 15:18:05 -0400, Gary Dale wrote:
> On 07/07/16 02:55 PM, David Wright wrote:
> >On Thu 07 Jul 2016 at 14:39:51 (-0400), Gary Dale wrote:
> >>The big selling feature of Grub over Lilo was that it didn't need to
> >>updated each time you changed something. That fell by the ways
On 07/07/2016 01:55 PM, David Wright wrote:
On Thu 07 Jul 2016 at 14:39:51 (-0400), Gary Dale wrote:
The big selling feature of Grub over Lilo was that it didn't need to
updated each time you changed something. That fell by the wayside
with Grub 2. Now the big selling feature is that it works
On Thu 07 Jul 2016 at 15:18:05 (-0400), Gary Dale wrote:
> On 07/07/16 02:55 PM, David Wright wrote:
> >On Thu 07 Jul 2016 at 14:39:51 (-0400), Gary Dale wrote:
> >>The big selling feature of Grub over Lilo was that it didn't need to
> >>updated each time you changed something. That fell by the way
On 07/07/16 02:55 PM, David Wright wrote:
On Thu 07 Jul 2016 at 14:39:51 (-0400), Gary Dale wrote:
The big selling feature of Grub over Lilo was that it didn't need to
updated each time you changed something. That fell by the wayside
with Grub 2. Now the big selling feature is that it works with
On Thu 07 Jul 2016 at 14:39:51 (-0400), Gary Dale wrote:
> The big selling feature of Grub over Lilo was that it didn't need to
> updated each time you changed something. That fell by the wayside
> with Grub 2. Now the big selling feature is that it works with more
> than just Linux.
I guess I don
On 05/07/16 09:38 AM, Giovanni Gigante wrote:
Hello,
I am preparing my system for the upgrade from wheezy to jessie.
Since ancient ages, this system has been using LILO as the bootloader,
because, long ago, it was the only bootloader that was recommended for
my setup: this machine has two SATA
On Thu 07 Jul 2016 at 08:33:57 (+0200), to...@tuxteam.de wrote:
> On Wed, Jul 06, 2016 at 02:23:39PM -0500, Don Armstrong wrote:
> > On Wed, 06 Jul 2016, Jonathan Dowland wrote:
> > > YMMV, I find it impenetrable.
> >
> > I'm assuming you mean the generated configuration? It's literally just
> > s
Brian wrote:
Giovanni Gigante seems happy enough with LiLo and there appears to be
no definite indication that it would fail to boot an upgraded machine.
He could consider leaving it in place, reading the bug reports and
having a plan to install GRUB should something go wrong afterwards.
At t
On Thu 07 Jul 2016 at 12:44:40 +0200, to...@tuxteam.de wrote:
> On Thu, Jul 07, 2016 at 11:32:42AM +0100, Brian wrote:
> > On Thu 07 Jul 2016 at 10:35:47 +0100, Lisi Reisz wrote:
> >
> > > On Thursday 07 July 2016 07:33:57 to...@tuxteam.de wrote:
> > > > Let's make it (GRUB2) impenetrable boilerp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jul 07, 2016 at 11:32:42AM +0100, Brian wrote:
> On Thu 07 Jul 2016 at 10:35:47 +0100, Lisi Reisz wrote:
>
> > On Thursday 07 July 2016 07:33:57 to...@tuxteam.de wrote:
> > > Let's make it (GRUB2) impenetrable boilerplate, then.
> >
> > :-)
On Thu 07 Jul 2016 at 10:35:47 +0100, Lisi Reisz wrote:
> On Thursday 07 July 2016 07:33:57 to...@tuxteam.de wrote:
> > Let's make it (GRUB2) impenetrable boilerplate, then.
>
> :-) +1!
It doesn't need to be penetrable, does it? The generated grub.cfg just
needs to boot the machine. In any case
On Thursday 07 July 2016 07:33:57 to...@tuxteam.de wrote:
> Let's make it (GRUB2) impenetrable boilerplate, then.
:-) +1!
Lisi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Jul 06, 2016 at 02:23:39PM -0500, Don Armstrong wrote:
> On Wed, 06 Jul 2016, Jonathan Dowland wrote:
> > YMMV, I find it impenetrable.
>
> I'm assuming you mean the generated configuration? It's literally just
> some boilerplate [...]
Let's
On Wed, 06 Jul 2016, Jonathan Dowland wrote:
> YMMV, I find it impenetrable.
I'm assuming you mean the generated configuration? It's literally just
some boilerplate for fancy splash screens, and then menu entries. Each
entry containing appropriate module loading, root configuration, kernel
and ini
On Tue, Jul 05, 2016 at 04:46:32PM -0500, Don Armstrong wrote:
> On Tue, 05 Jul 2016, Marc Shapiro wrote:
> > I finally switched to Jessie (but still using SysV Init) a few months
> > ago. This box and its predecessors have uses lilo (and SysV Init)
> > since Bo was a pup. I have yet to see any rea
On Tue, 05 Jul 2016, Marc Shapiro wrote:
> I finally switched to Jessie (but still using SysV Init) a few months
> ago. This box and its predecessors have uses lilo (and SysV Init)
> since Bo was a pup. I have yet to see any real reason to switch from
> lilo to grub. I have never had a problem with
On 07/05/2016 10:10 AM, Don Armstrong wrote:
On Tue, 05 Jul 2016, Giovanni Gigante wrote:
I am preparing my system for the upgrade from wheezy to jessie.
Since ancient ages, this system has been using LILO as the bootloader,
because, long ago, it was the only bootloader that was recommended for
On Tue, 05 Jul 2016, Giovanni Gigante wrote:
> I am preparing my system for the upgrade from wheezy to jessie.
> Since ancient ages, this system has been using LILO as the bootloader,
> because, long ago, it was the only bootloader that was recommended for my
> setup: this machine has two SATA disk
Hello,
I am preparing my system for the upgrade from wheezy to jessie.
Since ancient ages, this system has been using LILO as the bootloader,
because, long ago, it was the only bootloader that was recommended for
my setup: this machine has two SATA disks in a software RAID 1 & LVM;
that is, in
Joel Rees wrote:
> Ric Moore wrote:
> > There ya go, install the good stuff directories to /opt// (on an
> > /opt partition) and after create links to them in your new /home//
> > directory. Just don't blow up /opt by re-formating it. :) Ric
>
> Hasn't /opt been traditionally used for installing (
On Du, 21 sep 14, 02:19:08, Chris Bannister wrote:
> On Sat, Sep 20, 2014 at 01:48:41PM +0300, Andrei POPESCU wrote:
> > P.S. please note the 'apt' command is only available since apt 1.0.0
>
> bash completion isn't working for me. Is it for you?
>
> bash completion works fine for apt-get and dp
On Sat, Sep 20, 2014 at 01:48:41PM +0300, Andrei POPESCU wrote:
> P.S. please note the 'apt' command is only available since apt 1.0.0
bash completion isn't working for me. Is it for you?
bash completion works fine for apt-get and dpkg.
--
"If you're not careful, the newspapers will have you h
On 09/20/2014 03:18 PM, Martin Read wrote:
> On 20/09/14 13:01, softwatt wrote:
>> So, to sum it up: In my particular situation where I have a separate
>> partition for /home/ , the best "upgrade" would be:
>>
>> 1. Installing a brand new Debian but leaving /home/ intact.
>> 2. Deleting all the con
On 20/09/14 13:01, softwatt wrote:
So, to sum it up: In my particular situation where I have a separate
partition for /home/ , the best "upgrade" would be:
1. Installing a brand new Debian but leaving /home/ intact.
2. Deleting all the config stuff with `rm -rf /home//.[a-z0-9]*`
3. Done.
Have
So, to sum it up: In my particular situation where I have a separate
partition for /home/ , the best "upgrade" would be:
1. Installing a brand new Debian but leaving /home/ intact.
2. Deleting all the config stuff with `rm -rf /home//.[a-z0-9]*`
3. Done.
Have I missed anything?
signature.asc
D
On Jo, 18 sep 14, 16:54:23, Gary Dale wrote:
>
> I personally prefer to always do a dist-upgrade since it is a more
> complete upgrade than the normal one. If your repositories always
> point to testing, this will keep you current. Other people prefer to
> just do an upgrade, claiming it is safer.
On Sat, 20 Sep 2014 12:57:25 +0300
softwatt wrote:
> Thanks! But will they be recreated after the installation?
>
Right after the installation - of course not. No sane package manager
should change any file in the user's $HOME.
But, if we count the first launch of installed programs - it could
Thanks! But will they be recreated after the installation?
signature.asc
Description: OpenPGP digital signature
Hi.
On Sat, 20 Sep 2014 12:48:33 +0300
softwatt wrote:
> Can't I just do an rm -f -r /home//.* to get rid of hidden
> config? Will they be recreated?
>
Don't do this *ever*. It's not obvious, but your command will happily
remove /home//.. , so everything in /home/ will evaporate.
This is mo
Can't I just do an rm -f -r /home//.* to get rid of hidden
config? Will they be recreated?
signature.asc
Description: OpenPGP digital signature
On Fri, 19 Sep 2014 16:37:29 -0700
Don Armstrong wrote:
> On Fri, 19 Sep 2014, David Christensen wrote:
> > On 09/18/2014 10:54 PM, softwatt wrote:
> > >Also, does a clean install offer any advantage over an upgrade?
> >
> > Yes, because:
> >
> > 1. You get a systems programming product that ha
On Saturday 20 September 2014 05:40:40 softwatt wrote:
> I do not intend to upgrade now. I ask in order to learn. (:
At that rate, wait and read the release notes before upgrading. Sometimes it
is slightly more complicated than that. E.g., I think, Squeeze to Wheezy.
Lisi
--
To UNSUBSCRIBE,
I do not intend to upgrade now. I ask in order to learn. (:
signature.asc
Description: OpenPGP digital signature
softwatt wrote:
I knew that one day I'd have to upgrade so I put my home folder on a
different partition.
The 'unclean partition' install, not much info out there, but with
Debian you can delete system files and keep what you want, using the
same 'user' name do the install but do not format
On Fri, 19 Sep 2014, David Christensen wrote:
> On 09/18/2014 10:54 PM, softwatt wrote:
> >Also, does a clean install offer any advantage over an upgrade?
>
> Yes, because:
>
> 1. You get a systems programming product that has been through a
> quality assurance process.
Users of debian test both
On Sat, Sep 20, 2014 at 4:25 AM, Ric Moore wrote:
> On 09/19/2014 05:07 AM, softwatt wrote:
>>
>> Perfect. Thanks :)
>>
>> Assume this fails. What's the worst case scenario? I don't mind a broken
>> system, I *do* mind losing my /home/ folder.
>
>
>
> There ya go, install the good stuff directorie
On 09/18/2014 10:54 PM, softwatt wrote:
Also, does a clean install offer any advantage over an upgrade?
Yes, because:
1. You get a systems programming product that has been through a
quality assurance process.
2. It is easier to trouble-shoot if you run into problems -- both for
you and
On 09/19/2014 12:20 PM, Ric Moore wrote:
I always keep a rather large /opt directory on it's own partition. There
I keep all the personal stuff that has nothing to do with the install of
the / directory/partition. All of the usual user directories, such as
Documents, Downloads, Music, Videos and
On 09/19/2014 02:54 AM, Reco wrote:
On Fri, 19 Sep 2014 09:51:30 +0300
softwatt wrote:
Can Jessie keep my home partition intact and just overwrite the other
partition?
Current Debian installer can be persuaded to do so, sure. You can do
even better - co-install Jessie with the current Wheezy
On 09/19/2014 01:54 AM, softwatt wrote:
Also, does a clean install offer any advantage over an upgrade? It's
really a pain and I prefer to avoid it, but if there are good reasons
I'll do it.
For me, it is less likely to blow up and leave you with something you
didn't bargain for. If it does blo
On 09/19/2014 05:07 AM, softwatt wrote:
Perfect. Thanks :)
Assume this fails. What's the worst case scenario? I don't mind a broken
system, I *do* mind losing my /home/ folder.
There ya go, install the good stuff directories to /opt// (on
an /opt partition) and after create links to them in
On 09/18/2014 09:30 PM, David Christensen wrote:
On 09/18/2014 11:50 AM, Haines Brown wrote:
I normally
reinstall the operating system on a refreshed HD with a Debian Installer
each time there is an upgrade.
+1
Then I copy over my custom directories
(such as /usr/local/share)
Assuming /us
On 09/18/2014 01:30 PM, softwatt wrote:
Hello. How does one upgrade the distro? I have searched the web but I am
getting some contradictions, and I am hesitant to mess things up.
All websites suggest updating the /etc/apt/sources.list file. This makes
a lot of sense. However, the consensus ends
On Fri, 19 Sep 2014 12:07:57 +0300
softwatt wrote:
> Perfect. Thanks :)
>
> Assume this fails. What's the worst case scenario? I don't mind a
> broken system, I *do* mind losing my /home/ folder.
>
Back it up.
SteveT
Steve Litt* http://www.troubleshooters.com/
Troubleshootin
On Fri, 19 Sep 2014 10:54:49 +0400
Reco wrote:
> On Fri, 19 Sep 2014 09:51:30 +0300
> softwatt wrote:
>
> > Can Jessie keep my home partition intact and just overwrite the
> > other partition?
>
> Current Debian installer can be persuaded to do so, sure. You can do
> even better - co-install
On Fri, Sep 19, 2014 at 08:52:55AM +0300, softwatt wrote:
> On 09/18/2014 11:54 PM, Gary Dale wrote:
> > If you didn't do a dist-upgrade since Jessie came out, you could be
> > running the older wheezy packages as part of your system. Not recommended.
>
> What about the claim that it's best to do
On Fri, Sep 19, 2014 at 08:36:53AM +0300, softwatt wrote:
> On 09/18/2014 08:50 PM, Sven Hartge wrote:
> > On some systems it has been necessary (during the Squeeze to Wheezy
> > upgrade) to first use only "apt-get upgrade" after upgrading apt and
> > dpkg and then issuing the full dist-upgrade as
softwatt wrote:
> Perfect. Thanks :)
> Assume this fails. What's the worst case scenario? I don't mind a
> broken system, I *do* mind losing my /home/ folder.
Worst case scenario? Depends on how you define such a thing and on your
skills in asessing and fixing the situation.
During an upgrade
I'm not sure what you mean by "it was also hooked up to wheezy updates".
Keeping both sets of repositories would be useful if a package you require
was dropped from the current "testing" and even then you might be better
off compiling it for your current system. If the wheezy package has
dependenci
Perfect. Thanks :)
Assume this fails. What's the worst case scenario? I don't mind a broken
system, I *do* mind losing my /home/ folder.
signature.asc
Description: OpenPGP digital signature
softwatt wrote:
> Also, does a clean install offer any advantage over an upgrade? It's
> really a pain and I prefer to avoid it, but if there are good reasons
> I'll do it.
After an upgrade you have to do some manual housekeeping to remove old
cruft like no longer existing packages, leftover con
softwatt wrote:
> On 09/18/2014 08:50 PM, Sven Hartge wrote:
>> On some systems it has been necessary (during the Squeeze to Wheezy
>> upgrade) to first use only "apt-get upgrade" after upgrading apt and
>> dpkg and then issuing the full dist-upgrade as final step to get a
>> smoother upgrade. Th
I knew that one day I'd have to upgrade so I put my home folder on a
different partition.
signature.asc
Description: OpenPGP digital signature
On Friday 19 September 2014 07:52:33 softwatt wrote:
> I knew*
You knew what??
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/201409190850.08157.lisi.re...@gm
On Fri, 19 Sep 2014 09:51:30 +0300
softwatt wrote:
> Can Jessie keep my home partition intact and just overwrite the other
> partition?
Current Debian installer can be persuaded to do so, sure. You can do
even better - co-install Jessie with the current Wheezy just in case
something will go wro
I knew*
signature.asc
Description: OpenPGP digital signature
Thanks you.
When I first installed Wheezy, I've knew this day would come, and since
my home directory is basically the only thing I need, I put my home
directory in one partition and the rest of the system in another.
Can Jessie keep my home partition intact and just overwrite the other
partition
Hi.
On Fri, 19 Sep 2014 08:54:51 +0300
softwatt wrote:
> Also, does a clean install offer any advantage over an upgrade? It's
> really a pain and I prefer to avoid it, but if there are good reasons
> I'll do it.
Let's see:
A clean install of Jessie may be preferred as you'll get systemd out
o
Also, does a clean install offer any advantage over an upgrade? It's
really a pain and I prefer to avoid it, but if there are good reasons
I'll do it.
signature.asc
Description: OpenPGP digital signature
1 - 100 of 110 matches
Mail list logo
