On Sat, Mar 24, 2001 at 07:26:11PM -0600, JonesMB wrote:
>
> >I do find their command keys unintuitive (or at least contrary to current
> >programming) and puzzling but I am not complaining or anything :).
>
> I think it is all a ploy to make sure that people still read and follow
> instruction
On Sat, Mar 24, 2001 at 11:41:38PM -0800, Tim Uckun wrote:
>
> Now any idea what this could mean? I am pretty sure a cron job is spitting
> out these errors into the log but what cron job and why?
>
> iput: device 03:01 inode 110047 still has aliases!
> iput: device 03:01 inode 65988 still has a
On Sat, Mar 24, 2001 at 07:26:11PM -0600, JonesMB wrote:
>
> >I do find their command keys unintuitive (or at least contrary to current
> >programming) and puzzling but I am not complaining or anything :).
>
> I think it is all a ploy to make sure that people still read and follow
> instructio
Tim Uckun wrote:
> >for pkg in `dpkg-awk "Status:.* installed$" -- Package \
> > | grep -v '^$' | sed 's/^Package: //'`; do echo $pkg install ; done \
> > | dpkg --set-selections
> >
> >for pkg in `dpkg-awk "Status:.* not-installed$" -- Package \
> > | grep -v '^$' | sed 's/^Package: //'`; do e
On Sat, Mar 24, 2001 at 11:41:38PM -0800, Tim Uckun wrote:
>
> Now any idea what this could mean? I am pretty sure a cron job is spitting
> out these errors into the log but what cron job and why?
>
> iput: device 03:01 inode 110047 still has aliases!
> iput: device 03:01 inode 65988 still has
Tim Uckun wrote:
> >for pkg in `dpkg-awk "Status:.* installed$" -- Package \
> > | grep -v '^$' | sed 's/^Package: //'`; do echo $pkg install ; done \
> > | dpkg --set-selections
> >
> >for pkg in `dpkg-awk "Status:.* not-installed$" -- Package \
> > | grep -v '^$' | sed 's/^Package: //'`; do
for pkg in `dpkg-awk "Status:.* installed$" -- Package \
| grep -v '^$' | sed 's/^Package: //'`; do echo $pkg install ; done \
| dpkg --set-selections
for pkg in `dpkg-awk "Status:.* not-installed$" -- Package \
| grep -v '^$' | sed 's/^Package: //'`; do echo $pkg purge ; done \
| dpkg --se
At 10:11 PM 3/24/2001 -0800, Brian Frederick Kimball wrote:
Tim Uckun wrote:
> I do not seem to have dpkg-awk on my system do you know where I could
get it?
Did you try "apt-get install dpkg-awk"? :-)
DOH!. I didn't see it in dselect but apt-get install worked!. Apt is truly
awsome.
Tim Uckun wrote:
> I do not seem to have dpkg-awk on my system do you know where I could get it?
Did you try "apt-get install dpkg-awk"? :-)
At 09:49 PM 3/24/2001 -0800, Tal Danzig wrote:
On Sat, Mar 24, 2001 at 10:39:24PM -0800, Tim Uckun wrote:
>
> I do not seem to have dpkg-awk on my system do you know where I could
get it?
IIRC it's in the dpkg-dev package.
Apt says I already have dpkg-dev installed but I still can't find apt
On Sat, Mar 24, 2001 at 10:39:24PM -0800, Tim Uckun wrote:
>
> I do not seem to have dpkg-awk on my system do you know where I could get it?
IIRC it's in the dpkg-dev package.
- Tal
--
---
Tal Danzig: [EMAIL PROTECTED] | Libranet Lin
I do find their command keys unintuitive (or at least contrary to current
programming) and puzzling but I am not complaining or anything :).
I think it is all a ploy to make sure that people still read and follow
instructions :-)
my early days with dselect sometimes resulted in some painfu
for pkg in `dpkg-awk "Status:.* installed$" -- Package \
| grep -v '^$' | sed 's/^Package: //'`; do echo $pkg install ; done \
| dpkg --set-selections
for pkg in `dpkg-awk "Status:.* not-installed$" -- Package \
| grep -v '^$' | sed 's/^Package: //'`; do echo $pkg purge ; done \
| dpkg --
>for pkg in `dpkg-awk "Status:.* installed$" -- Package \
> | grep -v '^$' | sed 's/^Package: //'`; do echo $pkg install ; done \
> | dpkg --set-selections
>
>for pkg in `dpkg-awk "Status:.* not-installed$" -- Package \
> | grep -v '^$' | sed 's/^Package: //'`; do echo $pkg purge ; done \
> |
Tim Uckun wrote:
> > Something went horribly wrong I think I might have hit the wrong key on
> > deselect but whenever I quit dselect it wants to remove about 270 packages
> > and hold three of them. Is there a way to rebuild the package database?
You need to get your selections back to a sane
At 10:11 PM 3/24/2001 -0800, Brian Frederick Kimball wrote:
>Tim Uckun wrote:
>
> > I do not seem to have dpkg-awk on my system do you know where I could
> get it?
>
>Did you try "apt-get install dpkg-awk"? :-)
DOH!. I didn't see it in dselect but apt-get install worked!. Apt is truly
awsome.
Tim Uckun wrote:
> I do not seem to have dpkg-awk on my system do you know where I could get it?
Did you try "apt-get install dpkg-awk"? :-)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
At 09:49 PM 3/24/2001 -0800, Tal Danzig wrote:
>On Sat, Mar 24, 2001 at 10:39:24PM -0800, Tim Uckun wrote:
> >
> > I do not seem to have dpkg-awk on my system do you know where I could
> get it?
>
>IIRC it's in the dpkg-dev package.
Apt says I already have dpkg-dev installed but I still can't fi
On Sat, Mar 24, 2001 at 10:39:24PM -0800, Tim Uckun wrote:
>
> I do not seem to have dpkg-awk on my system do you know where I could get it?
IIRC it's in the dpkg-dev package.
- Tal
--
---
Tal Danzig: [EMAIL PROTECTED] | Libranet Li
>I do find their command keys unintuitive (or at least contrary to current
>programming) and puzzling but I am not complaining or anything :).
I think it is all a ploy to make sure that people still read and follow
instructions :-)
my early days with dselect sometimes resulted in some painfu
>
>
>for pkg in `dpkg-awk "Status:.* installed$" -- Package \
> | grep -v '^$' | sed 's/^Package: //'`; do echo $pkg install ; done \
> | dpkg --set-selections
>
>for pkg in `dpkg-awk "Status:.* not-installed$" -- Package \
> | grep -v '^$' | sed 's/^Package: //'`; do echo $pkg purge ; done \
Tim Uckun wrote:
> > Something went horribly wrong I think I might have hit the wrong key on
> > deselect but whenever I quit dselect it wants to remove about 270 packages
> > and hold three of them. Is there a way to rebuild the package database?
You need to get your selections back to a sane
Upgrading to woody would probably be a good idea but I don't
think it would solve your problem. You seem to be having trouble
running dselect (as many people do since the interface is
confusing).
Thanks for the tips. It'll try them.
I guess I have been programmed by years of computer use to
>
>Upgrading to woody would probably be a good idea but I don't
>think it would solve your problem. You seem to be having trouble
>running dselect (as many people do since the interface is
>confusing).
Thanks for the tips. It'll try them.
I guess I have been programmed by years of computer use
On Sat, Mar 24, 2001 at 12:25:52AM -0800, Tim Uckun wrote:
> Something went horribly wrong I think I might have hit the wrong key on
> deselect but whenever I quit dselect it wants to remove about 270 packages
> and hold three of them. Is there a way to rebuild the package database?
I don't thin
On Sat, Mar 24, 2001 at 12:25:52AM -0800, Tim Uckun wrote:
> Something went horribly wrong I think I might have hit the wrong key on
> deselect but whenever I quit dselect it wants to remove about 270 packages
> and hold three of them. Is there a way to rebuild the package database?
I don't thi
Hello everybody.
Something went horribly wrong I think I might have hit the wrong key on
deselect but whenever I quit dselect it wants to remove about 270 packages
and hold three of them. Is there a way to rebuild the package database?
I don't know if it's related or not but I am also having
Hello everybody.
Something went horribly wrong I think I might have hit the wrong key on
deselect but whenever I quit dselect it wants to remove about 270 packages
and hold three of them. Is there a way to rebuild the package database?
I don't know if it's related or not but I am also having a
28 matches
Mail list logo
