Adding this up here as a quick read: If this was installation via
debs, I'm out of the conversation. If it was about untarring [zipped
files] and you can repeatedly reproduce the issue now that you have
seen this, PLEASE don't share the package name(s) publicly. They could
be... dissected and then
On 7/21/21, Tixy wrote:
> On Wed, 2021-07-21 at 12:04 -0400, Frank McCormick wrote:
>> On 2021-07-21 10:52 a.m., Kushal Kumaran wrote:
>>
>> frank@fedora ~$ stat /
>>File: /
>>Size: 4096Blocks: 8 IO Block: 4096 directory
>> Device: 806h/2054d Inode: 2
On 7/21/21 12:24 PM, Greg Wooledge wrote:
On Wed, Jul 21, 2021 at 12:04:13PM -0400, Frank McCormick wrote:
frank@fedora ~$ stat /
File: /
Size: 4096 Blocks: 8 IO Block: 4096 directory
Device: 806h/2054d Inode: 2 Links: 18
Access: (0555/dr-xr-xr-x)
On Wed, Jul 21, 2021, 12:57 PM Greg Wooledge wrote:
> On Wed, Jul 21, 2021 at 12:39:49PM -0400, Kenneth Parker wrote:
>
> > > Access: (0555/dr-xr-xr-x) Uid: (0/root) Gid: ( 1000/ frank)
>
> > Actually, access 555 means everyone can Read and Execute, but nobody can
> > Update.
> >
> >
On Wed, Jul 21, 2021 at 12:39:49PM -0400, Kenneth Parker wrote:
> > Access: (0555/dr-xr-xr-x) Uid: (0/root) Gid: ( 1000/ frank)
> Actually, access 555 means everyone can Read and Execute, but nobody can
> Update.
>
> Root usually overrides that, which could explain why it still
On Wed, Jul 21, 2021, 12:12 PM Frank McCormick
wrote:
> On 2021-07-21 10:52 a.m., Kushal Kumaran wrote:
>
> > On Wed, Jul 21 2021 at 09:26:41 AM, Frank McCormick <
> debianl...@videotron.ca> wrote:
> >> Got a bunch of strange errors during this morning upgrade of Bullseye.
> >>
> >>
> >> Setting
On Wed, 2021-07-21 at 12:04 -0400, Frank McCormick wrote:
> On 2021-07-21 10:52 a.m., Kushal Kumaran wrote:
>
> > On Wed, Jul 21 2021 at 09:26:41 AM, Frank McCormick
> > wrote:
> > > Got a bunch of strange errors during this morning upgrade of Bullseye.
> > >
> > >
> > > Setting up systemd
On Wed, Jul 21, 2021 at 12:04:13PM -0400, Frank McCormick wrote:
> frank@fedora ~$ stat /
> File: /
> Size: 4096 Blocks: 8 IO Block: 4096 directory
> Device: 806h/2054d Inode: 2 Links: 18
> Access: (0555/dr-xr-xr-x) Uid: ( 0/ root) Gid: ( 1000/
On 2021-07-21 10:52 a.m., Kushal Kumaran wrote:
On Wed, Jul 21 2021 at 09:26:41 AM, Frank McCormick
wrote:
Got a bunch of strange errors during this morning upgrade of Bullseye.
Setting up systemd (247.3-6) ... Detected unsafe path transition / →
/run during canonicalization of /run.
On Wed, Jul 21 2021 at 09:26:41 AM, Frank McCormick
wrote:
> Got a bunch of strange errors during this morning upgrade of Bullseye.
>
>
> Setting up systemd (247.3-6) ... Detected unsafe path transition / →
> /run during canonicalization of /run. Detected unsafe path transition
> / → /run during
Hi
jpff wrote:
> 1) Why will vmlinuz-3.16.0-4-amd64 not load (says loading and the does
> nothing for over 30mins) when vmlinuz-3.2.0-4-amd64 does load?
>
don't know - I had same issue
In my case I found out that initrd was broken. I still have to unpack the
initrd copy /sbin/switch_root and
On 09/20/17 08:32, jpff wrote:
I seem to need to upgrade to Debian stretch to install my printer as
it needs hplip 3.16.11, ad I was running wheezy. ...
While some people succeed at major version upgrades, the few times I
have attempted it resulted in breakage, frustration, and lots of wasted
[Kevin Mark]
I thought that 'reinstall' seems very time consuming and thought
that there may be a diffent way to do it. Would this work for
(most|all)? cheers,
Yes, I believe so. So the latest incarnation of the script to fix
this problem uses this apporach. It is in sysv-rc version
[Bastian Venthur]
Looks like there is still something left to do for the user after this
step. Eg, on my machine KDM did not start up automatically anymore, as
well as WLAN. Those are two things I encountered directly and are
probably easy to fix, but I'm quite uncertain if there is something
On Sat, Sep 09, 2006 at 17:25:41 -0700, Paul Scott wrote:
Petter Reinholdtsen wrote:
Sorry for the noise. Here is yet another script fragment, this time
to extract the list of installed and upgraded packages in the
dangerous period. I did not know about the /var/log/dpkg.log file
before
Petter Reinholdtsen wrote:
Sorry for the noise. Here is yet another script fragment, this time
to extract the list of installed and upgraded packages in the
dangerous period. I did not know about the /var/log/dpkg.log file
before this morning.
sed -n /installed sysvinit
Hi Petter,
On Fri, Sep 08, 2006 at 07:22:53PM +0200, Petter Reinholdtsen wrote:
In version 2.86.ds1-16 of the sysv-rc package released 2006-09-06, the
update-rc.d script was broken. When used to to update symlinks it
would remove all symlinks for a init.d script if such symlinks
existed,
Sorry for the noise. Here is yet another script fragment, this time
to extract the list of installed and upgraded packages in the
dangerous period. I did not know about the /var/log/dpkg.log file
before this morning.
sed -n /installed sysvinit 2.86.ds1-16/,/installed sysvinit 2.86.ds1-18/p
[Petter Reinholdtsen]
A quick way out is to reinstall all the packages with scripts in
/etc/init.d/.
This way proved to be too quick, trying to reinstall removed but not
purged packages with init.d scripts left behind in /etc/init.d/. I
recommend using something like this instead, to only
Petter Reinholdtsen wrote:
Those with packages being broken from this bug can fix it by using
'apt-get --reinstall install package' on the affected packages. A
quick way out is to reinstall all the packages with scripts in
/etc/init.d/.
for p in `dpkg -S /etc/init.d/*|cut -d: -f1|sort
On Sun, 28 Jun 1998, Gregory Guthrie wrote:
I just did an upgrade bo -- hamm using autoup.sh.
Amazing. But, there are a number of steps which left me cold; and flipping
a coin for the right action.
1) during the autoup it had several conflicts, adn it was not clear to me
if I needed to
On Thu, 9 Jul 1998, Gregory Guthrie wrote:
Bob, thanks for the information..
I wish this was in the autoup.sh documentation!
In addition to autoup.sh, there is the libc5-libc6 mini-HOWTO, which
should be required reading, even for those using the script.
Watching the recent traffic on
Bob, thanks for the information..
I wish this was in the autoup.sh documentation!
Watching the recent traffic on upgrade problems, and issues makes me wonder..
One concluded that it isin't automatic, and you really have to know all the
dependencies, that dselect will only have shallow knowledge
2) After update, it says now use dselect to upgrade the rest of your
system, then reboot.
?? How do I know what to upgrade? I would like to say; whatever needs an
upgrade, if I have it installed, do it.
Instead, I had to go through dselect, look at hundreds of packages, try to
remember
When Tod Detre wrote, I replied:
Are you using apt as your access method? I've started using this and
specifying a list of sites to use for access and am delighted with the
results. I recently ran dselafter not having done so for an extended
period. I downloaded something (I forget just what)
On Sat, 27 Jun 1998, Tod Detre wrote:
Ok I upgraded to Hamm, but now dselevt is unhappy. It's probubly my config
error but I don't know what. When ever I try to install stuff it wants to
upgrade alot of stuff (expected it wants to put newer versions on.) but
when it trys to get the file it
26 matches
Mail list logo
