https://wiki.gentoo.org/wiki/Elogv
On Fri, Nov 13, 2020 at 12:27 AM Jude DaShiell wrote:
> About 6 different complaints about my kernel configuration that blew off
> the screen as packages were being emerged. Does any way exist to have
> emerge write these to a log file of some sort for later
On Thursday, 12 November 2020 23:40:38 GMT William Kenworthy wrote:
> Hi,
>
> I am trying to change the mac address of a realtek wifi card using
> either mac_wlan0="" in /etc/conf.d/net (which is in
> the handbook) or manually using ifconfig wlan0 hw ether address> and its not working.
Hi,
I am trying to change the mac address of a realtek wifi card using
either mac_wlan0="" in /etc/conf.d/net (which is in
the handbook) or manually using ifconfig wlan0 hw ether and its not working. Is there another way or am I stuck?
BillK
I did some portage configuration and the kernel configuration items that
are missing got saved in that log file!
-- United States has 633 Billionaires with only 10 doing any annual
significant giving.
About 6 different complaints about my kernel configuration that blew off
the screen as packages were being emerged. Does any way exist to have
emerge write these to a log file of some sort for later checking and
action?
-- United States has 633 Billionaires with only 10 doing any annual
On 11/11/20 10:10 AM, Neil Bothwick wrote:
On Wed, 11 Nov 2020 08:31:07 -0800, Daniel Frey wrote:
Or is this because nvidia-drivers depends on virtual/linux-sources?
Even so, the presence of the single slotted version in world should be
enough to satisfy the dependency.
Exactly, and emerge
I discovered that I had significant filesystem corruption.
On 11/12/20 10:47 AM, n952162 wrote:
So, /usr/lib/firefox/firefox runs, and is writable only by root. But
it can't be that the full firefox functionality gets executed in
239364 bytes!
$ type firefox
firefox is
So, /usr/lib/firefox/firefox runs, and is writable only by root. But it
can't be that the full firefox functionality gets executed in 239364 bytes!
$ type firefox
firefox is /usr/bin/firefox
$ which -a firefox
/usr/bin/firefox
$ ll /usr/bin/firefox
lrwxrwxrwx 1 root root
Hmm, interesting that it shows not the full path on one machine. This
should always show you the full path:
for p in `pgrep firefox` ; do ls -lh /proc/${p}/exe ; done
You could also check with the following command what will be executed:
which firefox
Use `which -a firefox` to see all possible
Ah, that is a good point ... assuming there's not an suid-updater
squirreled away somewhere. I'm pretty sure that I've run firefox (lots)
since last rebuilding it on the machine in question.
Your test is good, but yields new questions:
- machine 1:
$ pgrep -a firefox
*2829
I get notifications from firefox that an updates are available.
Once I wondered if it would be able to update and I pushed the update
button, it failed (likely in escalading the auths, as Andreas pointed).
To get rid of long compilation of firefox, I use www-client/firefox-bin.
The emerged
11 matches
Mail list logo
