Am 04.04.2014 23:24, schrieb Rodrigo Rivas:
> On Thu, Apr 3, 2014 at 9:12 PM, Lukas Jirkovsky wrote:
>> If you have enough time, I would try using pkgfile to recover the
>> installed packages. I thing something like this should suffice:
>> # update the pkgfile database
>> pkgfile -u
>> # find the
On Thu, Apr 3, 2014 at 9:12 PM, Lukas Jirkovsky wrote:
> If you have enough time, I would try using pkgfile to recover the
> installed packages. I thing something like this should suffice:
> # update the pkgfile database
> pkgfile -u
> # find the package names for all binaries
> find /usr/bin -typ
On Thu, Apr 3, 2014 at 11:22 AM, Marek Otahal wrote:
> Hello,
>
> I've lost content of /var, other partitions are ok, so system somewhat
> boots up (to recovery mode).
> What is the less pain method to get it again up and running? The problem I
> see are pacman list of installed packages? Any othe
On 03/04/14 01:36 PM, Nowaker wrote:
>> The pacman database was in /var so there's little point in trying to
>> reinstall the same packages
>
> What about software updates, security fixes, etc? ;-)
Which is why I'm suggesting a reinstall with pacstrap.
>> What is the less pain method to get it a
The pacman database was in /var so there's little point in trying to reinstall
the same packages
What about software updates, security fixes, etc? ;-)
What is the less pain method to get it again up and running? The problem I
see are pacman list of installed packages?
Although you don't kno
On 03/04/14 05:22 AM, Marek Otahal wrote:
> Hello,
>
> I've lost content of /var, other partitions are ok, so system somewhat
> boots up (to recovery mode).
> What is the less pain method to get it again up and running? The problem I
> see are pacman list of installed packages? Any other notes on
On Thu, Apr 3, 2014 at 11:43 AM, Thomas Bächler wrote:
> Am 03.04.2014 11:28, schrieb Martti Kühne:
>> Or better, check with the command that tests all packages' files for
>> presence.
>>
>> # pacman -Qk | grep -v '0 missing files'
>
> LOL. Where do you think that information is stored? I'll give
On Thu, Apr 3, 2014 at 11:38 AM, Jeff Daniel Rollin-Jones
wrote:
> It might actually be easier to reinstall than to go through "pacmanning"
> everything that's been lost, individually.
>
Do you mean `pacman -S $(pacman -Qq)`?
cheers!
mar77i
Am 03.04.2014 11:28, schrieb Martti Kühne:
> Or better, check with the command that tests all packages' files for presence.
>
> # pacman -Qk | grep -v '0 missing files'
LOL. Where do you think that information is stored? I'll give you a
subtle hint: It's /var.
OP is basically screwed. There is n
It might actually be easier to reinstall than to go through "pacmanning"
everything that's been lost, individually.
Sent from my iPhone
> On 3 Apr 2014, at 10:28, Martti Kühne wrote:
>
> Or better, check with the command that tests all packages' files for presence.
>
> # pacman -Qk | grep -v
Or better, check with the command that tests all packages' files for presence.
# pacman -Qk | grep -v '0 missing files'
cheers!
mar77i
In a slim install, you're unlikely to have lost much due to the nature
of /var (only variable data, aka no "installed files"). If you had a
database on disk you did lose that, eg postgres. Also firewall rules
and all logs.
Try pacman -Ql | grep /var to see what owns stuff in there.
J. Leclanche
Hello,
I've lost content of /var, other partitions are ok, so system somewhat
boots up (to recovery mode).
What is the less pain method to get it again up and running? The problem I
see are pacman list of installed packages? Any other notes on what
important things could be missing?
Thank you ver
13 matches
Mail list logo
