date:20170720

Re: Apt-get Upgrade Problem in Stretch?

2017-07-20 Thread Dejan Jocic

On 20-07-17, Patrick Bartek wrote:
> On Thu, 20 Jul 2017 08:48:17 +0200 Dejan Jocic 
> wrote:
> 
> > 
> > If you have minimal install, why do you suspect that something is
> > wrong, rather to suppose that all is fine and that simply there was
> > no security updates for your install? It is stable now, and as far as
> > i can remember, all those security updates we did have of lately were
> > somehow tied for graphical part, plus apache and ngninx. Apart for
> > security updates, tough luck of getting some other updates on stable.
> > And "everything worked fine" on your install of Stretch RC2 because
> > it was still testing and there was much more updates then?
> 
> That was my first thought.  And as I used a Stable net-install disk
> for my first tests of Stable, the system would have been up-to-date
> after the install. But it's been two weeks since that time.  I've added
> X, a window manager, utilities, apps, etc.  Based on my past
> experience, historically, there should have been some fixes.  I've
> never come across any such new release -- Debian or others -- that
> didn't need a plethora of fixes in those few days to a month after.  Or
> perhaps Stretch is bug free.  Or as I said in another post: Maybe the
> maintainers are taking a vacation.
> 
> As far as RC2:  I dist-upgraded it to Stable in the course of my tests.
> And as soon as it hit stable, apt-get upgrades ceased producing
> anything for a week.  So, I downloaded the Stable net-install CD for a
> new install to see if there was any differences.
> 
> B
> 

Yes, but did you really check if security updates debian stable had
during those 2 weeks included packages that you have installed, or not?
Your past experience is past, this is another install. Just take look at
security updates and compare, there is no much philosophy there:

https://www.debian.org/security/

Look under recent advisories.

Re: Setup Grub-Legacy on Jessie

2017-07-20 Thread Felix Miata

Jimmy Johnson composed on 2017-07-20 2:13 (UTC-0700):

> Felix Miata wrote:

> ...I wanted Jessie on sda1 where I keep my 
> menu.lst and keep things simple.

"Simple" I find impossible in multiboot of any serious extent. Closest thing
there can be to simple is a master bootloader on a primary partition which only
the admin ever touches, and is never ever mounted to /boot.

>> All my PCs are multiboot.

> Do you test operating systems?

Yes. I have two functional PCs with as few as 4 OS installed, both using
software RAID. Most PCs here have upwards of 10 OS, at least two with upwards of
25, of which one has more than 40.

>> None of my PCs have any incarnation of Grub* installed on any MBR. Generic 
>> MBR
>> code works.[1]

> And you can still use a menu to boot your systems?

Given multiboot, I can't imagine why you would ask.

> Why do you think it would have been better to have used grub from SUSE 
> than from Ubuntu?

Grub Legacy? Grub2? When, 7-10 years ago? Trusty's? (and why did you choose
Jessie for a Haswell?)

I thought Grub Legacy was last available from Ubuntu too many moons ago to
consider for any recent distros. OTOH, Grub Legacy with Gfxboot from openSUSE is
a dream for multiboot, and supports EXT4, which Debian's does not, which in turn
probably means Ubuntu's does not. With a new HD and a new PC, I initialize Grub
using Knoppix, but once I have an openSUSE on it, I switch it.

Since I rarely actually use Grub2, I have no basis to suggest whether openSUSE's
might be preferable to Ubuntu's. Does Ubuntu's have something Jessie's doesn't
that you need?

To be clear, in MBR systems I only ever install DOS or OS/2 on a primary
partition. All other OS go on logicals. Except for one ancient PC that has only
WinXP on it (which I did not install), at least one primary is always EXT2 with
Grub Legacy and little else, unless the disk is a pure data-only disk, in which
case its MBR sector is empty but for the partition table.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: cups

2017-07-20 Thread Erik Christiansen

On 20.07.17 19:51, Pol Hallen wrote:
> From client I print (ie: a 300Kb of pdf), in log cups server I see that file
> size about 4/5Mb (why?), so the printer before print it I've to wait also 15
> minutes :-/

Is the file for the printer postscript? That is always bigger than the
pdf equivalent, even before you get to the fancy compression of images
that Gene mentions.

A printer with a slow processor can take many minutes to process large
volumes of postscript. I have a small HP 3-in-1 laserprinter, and it can
be slow. I don't remember how PCL5 compares to postscript for speed.

> This happens only with a client with debian testing (and latest update of
> cups) before this updates no problem.

That may be "why", but the file format will elucidate "how", which is the
technically revealing bit.

Erik

Re: Setup Grub-Legacy on Jessie

2017-07-20 Thread Jimmy Johnson


On 07/20/2017 02:46 PM, Pascal Hambourg wrote:


You don't have to use the auto-generated grub.cfg. You can write and
maintain your own one manually.


You can! Good for you!

Cheers,
--
Jimmy Johnson

Debian Jessie - KDE 4.14.2 - Intel G3220 - EXT4 at sda1
Registered Linux User #380263

Re: Apt-get Upgrade Problem in Stretch?

2017-07-20 Thread Patrick Bartek

On Thu, 20 Jul 2017 05:55:15 + (UTC) david...@freevolt.org wrote:

> On Wed, 19 Jul 2017, Patrick Bartek wrote:
> 
> > Getting no results from apt-get upgrade after a week.  Can install
> > apps, etc., but get no security or stretch-update "fixes," etc.  I
> > find this unusual.
> 
> And so, understandably, you feel prompted to seek confirmation that
> there have, in fact, been no updates applicable to your system.

Of course.  But I did do searches to see if something like this has
occured before,

> I have a somewhat minimal[1] amd64 stretch system too, and examining
> /var/log/apt/history.log indicates that the most recent date there
> were upgrades available for an already installed package was on
> 2017-07-09:
> 
>Start-Date: 2017-07-09  hh:mm:ss
>Commandline: /usr/bin/apt-get upgrade
>Upgrade: libdns-export162:amd64 (1:9.10.3.dfsg.P4-12.3,
> [snip]
> In principle, the fewer packages you have installed, the more likely
> there will be such apparent "dry spells".

This was my first thought, too.  But after installing X, window
manager, utilities, apps, and two weeks with nothing, it struck my
"this is out of the ordinary" bone.  Never have any of my Debian
installs gone that long without some upgrade activity, particularly
after an initial Stable release.

> > Did a mail list archive search for this, but didn't find
> > anything specific. Or did I miss the solution?
> 
> It seems to me that the first step is determining whether there exists
> a problem to be solved.

Hence, my contacting the list. Right now, even with the advice I've
gotten, I can't find anything wrong system or configure-wise.

> Hope this helps.

Thanks for your response.

B

Re: Setup Grub-Legacy on Jessie

2017-07-20 Thread Jimmy Johnson

On 07/19/2017 11:33 AM, Felix Miata wrote:

Jimmy Johnson composed on 2017-07-19 02:30 (UTC-0700):

Some of you may already know that setting up grub-legacy on Debian can
be imposable, I've been thinking about this for awhile now and how to
solve this problem that Ubuntu does not have.

So I added trusty main to my Jessie repos and installed trusty grub and
trusty grub-common, I had to do a force-install and an apt-hold on
grub-common to keep it from getting upgraded.

And then I started grub and ran
#find /boot/grub/stage1
#root (hd0,0)
#setup (hd0)

I was half expecting it not to work cause I don't know anyone else who
has tried this, but it worked and I booted it a few times until I was
convinced it was working. :)

Questions or suggestions?

I don't like that kind of repo mixing.

I didn't care for doing it..But I wanted Jessie on sda1 where I keep my
menu.lst and keep things simple.

All my PCs are multiboot.

Do you test operating systems?

None of my PCs have any incarnation of Grub* installed on any MBR. Generic MBR
code works.[1]

And you can still use a menu to boot your systems?

The only OS installations here with Grub2 installed are *buntus, and I don't use
them much. I equate Grub2 to systemd, except that Grub2 is easier to avoid
having contaminate user experience.

All my other Linux installations have Grub Legacy installed to their /
filesystems, manually by me from openSUSE packages where the OS does not offer a
working package of it.

That's what I did..You said you didn't like it and I agree.

Grub Legacy requires no scripts or filesystem mounting to
setup, and its menu.lst is magnitudes easier than Grub2's grub.cfg to manually
maintain. The / bootloader installations are mainly only used for loading
previous or test kernel versions.

All my PCs have a master boot partition, where Grub Legacy from openSUSE is
installed. openSUSE's Grub Legacy has been kept adequately maintained for my
needs, which means EXT4 filesystems are fully supported. OTOH, Debian's Grub
Legacy is broken WRT EXT4, OK with EXT2/3. These master boot partitions are
configured manually to load every Linux installation's default kernel, plus
chainloading each, and chainloading DOS/OS2/Windows (if applicable), plus
memtest.

IOW, where Grub Legacy can still be used, it's far preferable. If it works for
you, enjoy. :-)

[1]
https://old-en.opensuse.org/Bugs/grub#How_does_a_PC_boot_.2F_How_can_I_set_up_a_working_GRUB.3F

I don't have anything against SUSE, but not something I would bother
with at this time, it was the first Linux I installed back in '94 after
installing DOS, Windows, SCO and Novell, I was installing every piece of
software I could get my hands on, I installed my first boot sector virus
then and learned how to remove them too in '94.

74 matches

Mail list logo