Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

2021-04-09 Thread Marco Ippolito
> Yes, and my impression/guess is that because 'apt' docs describe it
> as being basically a front end with more convenient defaults for
> interactive use, what happens when 'apt' is given these (or other
> similar) options that it does not recognise as its own as documented
> in the 'apt' man page, it behaves the same as if it handed these
> options off to whatever command it runs as its back-end.

I wonder if documentation for options like -s belongs only in apt-get, both in
apt-get and apt or something else. Currenly, the option is accepted by apt but
not documented in the man page I have on my system for apt.



Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

2021-04-08 Thread Marco Ippolito
> > Where would I put the -s please?
> 
> Explanation of how to find the answer:
> He was talking about 'apt' commands.
> If you read 'man apt' it hints that it is a front-end to
> various 'apt-*' commands like 'apt-get'.
> The hints look like "apt-get(8)" which is a reference
> to the 'apt-get' man page in Section 8, which can
> be read using the command:
>   man 8 apt-get
> And if you read that man page, you can find an
> explanation of the -s option when used with a
> 'apt-get' command.

Gotcha. I like the long option names there, almost all of which are immediately
suggestive of what the change of behaviour might be:

--simulate, --just-print, --dry-run, --recon, --no-act

Especially: --simulate and --dry-run (for users of rsync and other commands
that use the same long option name)



Re: Boot better have mounted on root or /boot ?

2021-04-08 Thread Marco Ippolito
> Eventually it all boils down to one's ability to predict the future or
> at least a subset thereof.

What would you consider in your future planning regarding sizing /boot?

e.g. how many kernels (with how many built-in modules and with what
compression) to keep around for alternate booting or reuse elsewhere...

... what else?



Re: .profile not being src'd at login on uptodate buster

2021-04-08 Thread Marco Ippolito
> >> Where I want output, I protect it with:
> >>
> >> [ -n "$PS1" ] && printf …
> >
> > Maybe consider:
> >
> > [[ -t 1 ]] && printf ...
> 
> Until your script that was started via crontab silently fails.  I
> *like* always having error messages enabled.

I like logs too but -t was in the spirit of -n $PS1, only slightly more robust,
I think.



Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

2021-04-08 Thread Marco Ippolito
> And I'm a big fan of -s with commands like these, so that
> you know what's going to be changed. Then recall the command
> and remove the -s.

Where would I put the -s please?



Re: .profile not being src'd at login on uptodate buster

2021-04-07 Thread Marco Ippolito
> Where I want output, I protect it with:
> 
> [ -n "$PS1" ] && printf …

Maybe consider:

[[ -t 1 ]] && printf ...



Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

2021-04-07 Thread Marco Ippolito
> I decided to let MY initramfs images go on diet
> and added a little script which removes a few drivers that I certainly
> don't need (checked with lsmod) and which contained lots of firmwares
> and similar stuff.

Creative. I liked it. Indeed the ``most'' strategy produces large files.



Re: Firefox profiles on fresh install: default{-esr}

2021-04-07 Thread Marco Ippolito
> Which Firefox do you have installed?

ii  firefox-esr78.8.0esr-1~deb10u1 amd64Mozilla
Firefox web browser - Extended Support Release (ESR)

ii  firefox-esr-l10n-en-gb 78.8.0esr-1~deb10u1 all  English
(United Kingdom) language package for Firefox ESR



Firefox profiles on fresh install: default{-esr}

2021-04-07 Thread Marco Ippolito
I reinstalled Buster (basic installation with GUI, no additional packages
chosen) and typed "about:profiles" in Firefox's URL bar.

It shows two profiles:

* Profile: default-esr
* Profile: default

with different Root Directories.

What is the purpose of this duality and which Profile should I use?


Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

2021-04-07 Thread Marco Ippolito
> Hi Marco, 

Hi Hans :)

> aptitude purge ~n4.9.10-amd64-* 

Hadn't thought of matching a pattern, thanks.



Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

2021-04-07 Thread Marco Ippolito
> Recently that was fixed at unstable [1]

I thought I had noticed a warning about this clean-up, but it does not happen
during the upgrade so I run out of space.

> I found a interesting manpage for this issue [2]

Good catch. Functionality now in apt and purge-old-kernels got deprecated.



Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

2021-04-07 Thread Marco Ippolito
> where `MODULES=dep` and `COMPRESS=lzma` have made a big difference for
> me (more or less shrunk the initrd images by a factor 3-4).

Thank you.

Why did you choose lzma Vs xz or zstd, by the way? Measured diff?

> > Doubt: after this, by default old kernels will be cleaned up in Bullseye Vs
> >Buster?
> I don't think APT ever cleans up old kernels for you (at least in its
> default configuration).

Read something about it during the upgrade.. was checking here.



No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

2021-04-07 Thread Marco Ippolito
Was upgrading from buster to bullseye. Space ran out, UI crashed, restarted in
recovery mode and cleaned up space. Restarted and run:

# dpkg --configure -a
Setting up initramfs-tools (0.139) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.139) ...
update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64
cat: write error: No space left on device
update-initramfs: failed for /boot/initrd.img-5.10.0-5-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned
 error exit status 1
 Errors were encountered while processing:
  initramfs-tools

# df -h /boot
Filesystem  Size  Used Avail Use% Mounted on
/dev/nvme0n1p1  236M  233M 0 100% /boot

What do you recommend I do?

Doubt: after this, by default old kernels will be cleaned up in Bullseye Vs
   Buster?



Re: How to `echo' the core # a bash script is running on?

2014-02-15 Thread Marco Ippolito
On 11 Feb 2014, at 04:09, Joel Rees joel.r...@gmail.com wrote:

 On Tue, Feb 11, 2014 at 9:03 AM, Chris Davies ch...@roaima.co.uk wrote:
 Marco Ippolito maroloc...@gmail.com wrote:
 How can I `echo', in `bash', the core # the current script is running on?
 
 This will probably do it for you
awk '{print $39}' /proc/$$/stat
 
 See proc(5) for details, including the 39. Please also note that unless
 you've set the task affinity (see taskset(1) for details) the process
 can - and will - be reassigned different cores during its lifetime.
 
 Heh. What odds do you give it that the processor will be running on a
 different core by the time his script has IDed the core? Or maybe even
 cycled back again?
 
 But, I guess if the OP's purpose is just to prove that scripts are not
 confined to a single core, I guess it doesn't matter. (I can't say
 that I can think of any other reason for the question, now that I
 think of it. Hmm)
 
 -- 
 Joel Rees
 
 Be careful where you see conspiracy.
 Look first in your own heart.

Appreciated the discussion, thanks. Yes, I was trying to verify some behaviour, 
a bit like the following Bash one-liner, but in another context, and `taskset' 
helped me more than looking at `printf' as an aftermath:

bash4$ f=/tmp/delme; printf '%s\n' '#include stdio.h' '#include sched.h' 
'int main(int argc, const char* argv[]) { printf(job: %s; sched_getcpu(): 
%d\n, argv[1], sched_getcpu()); return 0; }' | gcc -x c -o $f -  parallel 
-j 0 $f {#} -- {1..9}

job: 1; sched_getcpu(): 0
job: 2; sched_getcpu(): 1
job: 3; sched_getcpu(): 1
job: 4; sched_getcpu(): 1
job: 5; sched_getcpu(): 1
job: 6; sched_getcpu(): 1
job: 7; sched_getcpu(): 1
job: 8; sched_getcpu(): 0
job: 9; sched_getcpu(): 1

Printing job IDs, cpu numbers, etc.

In the end I just rewrote my script in C.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/c60264b9-1349-428c-878b-f4283bdb7...@gmail.com



Re: Recomendacion de diccionario offline

2014-02-12 Thread Marco Ippolito
On 10 Feb 2014, at 15:22, Camaleón noela...@gmail.com wrote:

 El Mon, 10 Feb 2014 09:00:58 -0400, luis escribió:
 
 Buenos días a todos
 
 Tengo instalado debian 7 a 64 bit y necesito tner un diccionario, cual
 me recomiendan instalar y que a su vez pueda descargar los diccionarios
 para usarlo OFFLINE.
 
 StarDict, GoldenDict o Babiloo.
 
 La base de datos de diccionarios creo que se descarga aparte.
 
 Saludos,
 
 -- 
 Camaleón

`apt-get install packagesearch' oferece una interfaz gráfica de usuario con la 
que puedes buscar por tag (e.g. categoría/Debtags).. 


--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/edbac4be-a76b-4d55-8b35-f49a44132...@gmail.com



How to `echo' the core # a bash script is running on?

2014-02-09 Thread Marco Ippolito
How can I `echo', in `bash', the core # the current script is running on?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/9d338da3-13ad-468f-840a-8dd11f881...@gmail.com