[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Debmirror



Hi,

On 2021-07-27 10:45 a.m., Gunnar Gervin wrote:
> Just a Linux advice/s I read 10years ago + -.
Time goes by and things change.
Advice from 10 years ago can even be bad when applied today.

I used to create multiple partitions that were needed years ago. But by
doing so today, I don't gain much and just add problems.

And this also apply to other things too...

Today's there is enough processing power that encrypting a disk doesn't
put a overhead that will make your system much slower. This wasn't true
10 years ago. So if I follow what was done 10 years ago, I'll be
restraining from encrypting my disk for the laptop. And this may cause
me more problem because today's market for stolen data is very big when
compared to 2010...

> It probably don't apply to experienced users. 
> That advisable to backup to external device, & do install from newest
> distro release. 
> Why is that a non-sense?
> Seems logical to me. A newbie.
Yes, may seem logical to you a "newbie" and there's no danger of doing a
backup.

But if you read what I was talking about...
First you it was a really different context than doing a system update.
I wasn't even talking about doing the update yet, but only knowing
what's available.
2nd, I was talking about updating the list of software available and
receiving the new version, so the package manager knows which one have
gotten new release out.
3rd, This type of check if done everyday and package installation are
also done at the same time (can be done in automatic fashion).

Don't you think it would be somewhat painful for a server operator to
backup his whole system everyday only for this purpose ? Because yes,
most server have the backup of user data and program data done everyday.
But what you seem to talk about was doing a backup by hand.

Like I said earlier, time goes by and evolves...

> Not even sure what "cache" means/definition of it.
Could be useful to learn what the word means before going into answering
question or ask people what's the context.
You'll save your time and also get a chance to learn.

> Temporary storage?
Mostly mean to store some frequently accessed data at a place where it's
faster to get it.
In this situation, the list of package available is stored in
/var/cache/apt instead of reading off the network each time it is needed.

Can also apply to your computer processor, 1st and 2nd level (even 3d
level) cache. A special part of the processor that has really fast
memory and keep data frequently used.

Your browser has a cache to keep some image of website you frequently
visit so it doesn't need to download them every time you load the page
(save some time).

In computing, word goes in hand with context to make sense...

If you'd have took a minute to do a search on Google for "apt cache
update" you'd have gotten many answers on Stackoverflow that would have
gave you the context for this type of cache.

Just a hint.

It comes with time.

Hope this help you somehow.

Sincerely,

> Geg
> 
> 
> On Sun, 25 Jul 2021, 16:37 Polyna-Maude Racicot-Summerside,
> <debian@polynamaude.com <mailto:debian@polynamaude.com>> wrote:
> 
>     Hi,
> 
>     On 2021-07-25 3:42 a.m., Gunnar Gervin wrote:
>     > Polyna.
>     > I always have heard it's better to put all documents, files,
>     photos etc
>     > in a usb or external harddisk. And do a clean reinstall of the updated
>     > distro.
>     Can you explain a bit further... ?
> 
>     If I follow what I read in your message...
>     You are telling me that :
>     It is recommended to backup user's personal data
>     Do a clean reinstall
>     When Debian publishes update ?
> 
>     What type of update ?
>     Point release ?
>     Release ?
> 
>     This look pretty heavy to me...and sounds much more like something that
>     is done on the Windows world.
> 
>     Why would it be needed to do a clean reinstall ?
>     If you work properly and don't litter around then everything in your
>     system is registered as file in the package manager and the
>     configuration are preserved thru configuration file litigation (ask you
>     what to do when a config file has been changed from default).
> 
>     Would you have the reference regarding this ?
> 
>     Are talking about clean the apt cache before doing upgrade ?
> 
>     Explain more because this smell like non-sense to me.
>     > BR,
>     > geg
>     >
>     > On Sun, 25 Jul 2021, 04:41 Polyna-Maude Racicot-Summerside,
>     > <debian@polynamaude.com <mailto:debian@polynamaude.com>
>     <mailto:debian@polynamaude.com <mailto:debian@polynamaude.com>>> wrote:
>     >
>     >     Hi,
>     >
>     >     On 2021-07-24 9:33 p.m., David Wright wrote:
>     >     > On Sat 24 Jul 2021 at 19:52:36 (-0400), Polyna-Maude
>     >     Racicot-Summerside wrote:
>     >     >> Here are the message I get after my debmirror when I do apt-get
>     >     update
>     >     >>
>     >     >> Err:31 file:/mnt/mirror/debian buster-updates/main amd64
>     Contents
>     >     (deb)
>     >     >>   File not found -
>     >     >> /mnt/mirror/debian/dists/buster-updates/main/Contents-amd64 (2:
>     >     No such
>     >     >> file or directory)
>     >     >> Reading package lists... Done
>     >     >> E: Failed to fetch
>     >     >> file:/mnt/mirror/debian/dists/buster/main/Contents-amd64  File
>     >     not found
>     >     >> - /mnt/mirror/debian/dists/buster/main/Contents-amd64 (2:
>     No such
>     >     file
>     >     >> or directory)
>     >     >> E: Failed to fetch
>     >     >>
>     file:/mnt/mirror/debian/dists/buster-updates/main/Contents-amd64 
>     >     File
>     >     >> not found -
>     >     /mnt/mirror/debian/dists/buster-updates/main/Contents-amd64
>     >     >> (2: No such file or directory)
>     >     >>
>     >     >> The command I used for creating the mirror is
>     >     >>
>     >     >> debmirror --all --progress --verbose --method=http
>     >     >> --dist=buster,buster-updates,buster-backports
>     >     >> --section=main,contrib,non-free --arch=amd64,i386
>     --rsync-extra=none
>     >     >> --source --i18n --keyring
>     >     /usr/share/keyrings/debian-archive-keyring.gpg
>     >     >> --root=debian --host=debian.mirror.iweb.ca
>     <http://debian.mirror.iweb.ca>
>     >     <http://debian.mirror.iweb.ca <http://debian.mirror.iweb.ca>>
>     /mnt/mirror/debian
>     >     >>
>     >     >> Got idea ?
>     >     >
>     >     > --getcontents ?
>     >     >
>     >     Giving this one a try....
>     >
>     I'm not sure you have close to a clue what my problem is.
>     Because when I simply change my repository to the usual Debian one, I
>     can do my apt cache update properly.
> 
>     >
>     >     > Cheers,
>     >     > David.
>     >     >
>     >
>     >     Thanks
>     >
>     >     --
>     >     Polyna-Maude R.-Summerside
>     >     -Be smart, Be wise, Support opensource development
>     >
> 
>     -- 
>     Polyna-Maude R.-Summerside
>     -Be smart, Be wise, Support opensource development
> 

-- 
Polyna-Maude R.-Summerside
-Be smart, Be wise, Support opensource development

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


Reply to: