Hi Chris,
Chris Cappuccio wrote on Thu, May 02, 2019 at 12:08:07PM -0700:
> Ingo Schwarze [schwa...@usta.de] wrote:
>> It might be a good idea to do
>>
>> # rm -rf /usr/share/man/* /usr/X11R6/man/*
>>
>> immediately before an upgrade.
> I go one step further, and rm -rf /usr/include
SYMPTOM: Soon after a fresh OpenBSD install intended to use as a
laptop / work engine, and consequently a few uses of a graphical
session, suddenly the X session cannot start anymore : logging
in with a correct user/passwd pair provokes a crash and restart of the
X Display Manager, displaying the
On 5/2/19 8:04 AM, Ted Unangst wrote:
> Nick Holland wrote:
>> > In a shell script invoked by doas, is it possible to find which user
>> > invoke the script? my search a the moment has come up empty.
>>
>> most likely place would be an environment variable, right?
>
>>
>> # echo "I started
Ingo Schwarze [schwa...@usta.de] wrote:
>
> It might be a good idea to do
>
> # rm -rf /usr/share/man/* /usr/X11R6/man/*
>
> immediately before an upgrade.
>
I go one step further, and rm -rf /usr/include /usr/share /usr/X11R6
before a new snapshot is applied. This is a bit overkill but
On Thu, May 02, 2019 at 04:29:20AM +, Adam Steen wrote:
>
> Hi
>
> In a shell script invoked by doas, is it possible to find which user
> invoke the script? my search a the moment has come up empty.
>
> Cheers Adam
>
Hi Adam,
Nowadays, I think the POSIX way is considered to be id(1) with
Dan Shechter writes:
> Greetings of the day!!
Spam giveaway. No recruiter in the USA would use that phrase. That and
the other grammatical and sentence structure errors are red flags.
Allan
I’ve got it as well from a different random recruiter and it was addressed to
the wrong name.
I doubt that Apple is doing such unprofessional recruiting - It looks like some
scam.
Reyk
> Am 02.05.2019 um 16:56 schrieb Dan Shechter :
>
> Got approached by a head hunter.
>
> If anyone in the
Got approached by a head hunter.
If anyone in the community is interested and read it as is, I am just copy
pasting, and I know NOTHING about this job or the head hunter that sent me
the bellow email:
Hii There!
Greetings of the day!!
I found your resume from one of the job portal and just
Nick Holland wrote:
> > In a shell script invoked by doas, is it possible to find which user
> > invoke the script? my search a the moment has come up empty.
>
> most likely place would be an environment variable, right?
>
> # echo "I started out as $LOGNAME"
> I started out as nick
Hi Nick,
Nick Holland wrote on Thu, May 02, 2019 at 08:04:32AM -0400:
> There is no promise that an upgraded machine will be file-for-file
> identical to a fresh install. Here is the list of problems this might
> cause you, as you can see, it's a long list and quite horrible:
>
> * If you use
On Thu, May 2, 2019 at 20:17, Nick Holland wrote:
> On 5/1/19 10:28 PM, Adam Steen wrote:
>> Hi
>>
>> In a shell script invoked by doas, is it possible to find which user
>> invoke the script? my search a the moment has come up empty.
>
> most likely place would be an environment variable,
On 2019-05-02 11:46, Noth wrote:
> I set up a script for sysclean:
>
> cat sysclean65.txt | while read line ; do rm -rf "${line}" ; done
Nitpick, but this could be shortened to:
xargs rm -rf < sysclean??.txt
Just tested this on my server, so it should work fine.
--
Stephen Gregoratto
PGP:
On 09:42 Thu 02 May, Stuart Henderson wrote:
> The upgrade notes only list files which are likely to cause a problem
> if they're left lying around.
Oh, okay.
On 5/1/19 10:28 PM, Adam Steen wrote:
> Hi
>
> In a shell script invoked by doas, is it possible to find which user
> invoke the script? my search a the moment has come up empty.
most likely place would be an environment variable, right?
So ...
$ whoami
nick
$ doas -s
#
On 5/2/19 1:52 AM, Consus wrote:
> Hi,
>
> I've upgraded my systems from 6.4 to 6.5 without a glitch, but I see
> that /etc/networks and some other files (like malloc.conf.5) are still
> present, although there is no use for them in the new release.
>
> Is there a reason why these files are not
On 02/05/2019 11:02, Consus wrote:
On 10:27 Thu 02 May, Markus Hennecke wrote:
Am 02.05.2019 um 09:52 schrieb Consus:
I've upgraded my systems from 6.4 to 6.5 without a glitch, but I see
that /etc/networks and some other files (like malloc.conf.5) are still
present, although there is no use
On 2019-05-02, Consus wrote:
> On 10:27 Thu 02 May, Markus Hennecke wrote:
>> Am 02.05.2019 um 09:52 schrieb Consus:
>> > I've upgraded my systems from 6.4 to 6.5 without a glitch, but I see
>> > that /etc/networks and some other files (like malloc.conf.5) are still
>> > present, although there
On 10:27 Thu 02 May, Markus Hennecke wrote:
> Am 02.05.2019 um 09:52 schrieb Consus:
> > I've upgraded my systems from 6.4 to 6.5 without a glitch, but I see
> > that /etc/networks and some other files (like malloc.conf.5) are still
> > present, although there is no use for them in the new
On Tue, 30 Apr 2019 13:29:47 -0700 Lyndon Nerenberg wrote:
> > But I should be able to accomplish what I need using rc.firsttime
> > and a tiny bit of hackery.
>
> Sadly, no :-(
How about partition as /var/temp/ & autoinstall Lyndon?
Then in rc.firsttime:-
*) umount /var/temp/
*) check
Am 02.05.2019 um 09:52 schrieb Consus:
> I've upgraded my systems from 6.4 to 6.5 without a glitch, but I see
> that /etc/networks and some other files (like malloc.conf.5) are still
> present, although there is no use for them in the new release.
>
> Is there a reason why these files are not
Hi,
I've upgraded my systems from 6.4 to 6.5 without a glitch, but I see
that /etc/networks and some other files (like malloc.conf.5) are still
present, although there is no use for them in the new release.
Is there a reason why these files are not listed in "FIles to remove"?
Is there a way to
21 matches
Mail list logo
