Re: [gentoo-user] Hard drive and PWDIS or pin 3 power disable/reset.

2024-05-09 Thread Dale
Mark Knecht wrote:
>
>
> On Thu, May 9, 2024 at 6:35 PM Mark Knecht  > wrote:
> >
> >
> > >
> > >
> > > I've looked for a adapter.  I couldn't find one.  That's why I
> connected to a old rig that had a set of molex cables I could use. 
> Luckily I had a molex to sata adapter.  Do you know what they are
> called so I know what to search for?  I'd buy a dozen or so just to
> have extras laying around.  I just can't find them.  I suspect I'm
> using the wrong search terms.
> > >
> > > Do new motherboards support that PWDIS feature?  I'm looking at
> the ASUS Prime X670-P mobo and I can't find anything that says what
> version of SATA it has or about the PWDIS option.  I assume it doesn't
> have it but assuming means you can be wrong.  I haven't looked at the
> new power supply cables yet.  I've bought ATX style ones recently
> tho.  Look the same as old ones to me.
> > >
> > > Dale
> > >
> > > :-)  :-)
> >
> > I am not sure but I think Molex to SATA Power gets you in the ballpark?
> >
> > https://www.amazon.com/Power-Cable-Adapter-Female-8-inch/dp/B07BQFKTG7
> >
> >
> https://www.amazon.com/Duttek-Female-Adapter-Connector-Drives/dp/B09BJ1J24M
> >
> > If these are close then it wouldn't cost a lot to try one out. (<$10)
>
>
> Sorry, I forgot to address your second question.
>
> It is my understanding - good or bad I'll leave it to you - that newer
> motherboards
> are moving toward drive power supplied through the motherboard and not
> through our old-style power supply cables. I don't think this is in
> the market
> yet in any big way, but when it arrives it would allow PWDIS to be
> controlled through
> software which then makes it easier to do 'hot swap' because the drive
> isn't hot
> when power is disabled. I suspect this is more of a server farm type
> issue and 
> desktop machine users wouldn't be doing this because the form factor
> of the 
> machine itself isn't set up for that. However if you were to get some
> sort of a 
> drive cage which you connected to using wider SATA specifications then
> you could
> disable power to one drive and swap it out without having to power the
> machine down.
>
> All supposition on my part. I'll leave it to you to dig deeper if you
> care. (I don't !)
>
> Best wish, good luck and happy hunting,
> Mark


I've got some of the cables like in your links.  I was hoping they made
a little short thing like in your second link that I can plug into the
drive then plug a SATA power connector to but it doesn't connect pin 3
to anything.  It stays SATA basically, no molex needed.  To be honest, I
only have 4 wires on my power cable going to the SATA connector.  The
ones I see with the 5th wire are the ones with PWDIS.  Thing is, I'd
don't know how it is connected inside the connector.  From my
understanding, the 5v wire is connected to several pins including 1
through 3.  That's what makes it not work.  I think.  That may vary from
one power supply maker to another and may even vary between models of
the same maker. 

In a way, that sounds interesting about the new way.  For those who like
to show off their rigs, they would like that because it would result in
less cable clutter.  To be honest, I'm not against the PWDIS feature. 
For some use cases, it is a good idea.  It just should have been made
backward compatible.  Right now, I have one case with about 10 drives in
it.  I'd like to be able to disable a drive before unplugging it.  If my
system supported PWDIS, I'd sure use it and be glad to have it.  My new
Fractal case holds 18 drives I think.  I can add cages which may make it
hold even more drives.  Having the PWDIS feature would be nice.  I could
unmount a drive, disable it, then unplug and remove it and be almost the
same as doing so when the system is shutdown completely.  It's a good
idea, just needed to be implemented better. 

For those following this, the hard drive made it back to the seller. 
When they tested the drive, it was bad.  They got the same as I did in
the very old rig with the molex to SATA cable.  I suspect it was a drive
with the PWDIS feature and it turned out it was also bad.  I did order
another drive.  I ordered one I got before that works but I also
included a note that if the drive has the PWDIS feature, to cancel the
order and let me know what drives they carry that don't have that feature. 

I just wish there was a very easy way to find out which drives have the
PWDIS feature and which ones don't.  I'm beginning to wonder if there
really is a way other than plugging it up and seeing of it comes on. 

All this because they didn't make something backward compatible.  o_O

Dale

:-)  :-)


Re: [gentoo-user] Hard drive and PWDIS or pin 3 power disable/reset.

2024-05-09 Thread mad . scientist . at . large
I have a lot of drives like that.  Simplest solution is to cut the orange wire 
on the drive power cable.  Only down side is that some ssd may require the 3.3V 
power so you might not want to modify all the power cables.  I just had to do 
this so my sas drives would spin up.  Before I did it the drives didn't even 
show up in the bios.  (and I just got 10 of these used, they are going into a 
raid 6 array+spares).  I've been making this mod for over 10 years.

--"Fascism begins the moment a ruling class, fearing the people may use their 
political democracy to gain economic democracy, begins to destroy political 
democracy in order to retain its power of exploitation and special privilege." 
Tommy Douglas




May 9, 2024, 15:12 by rdalek1...@gmail.com:

> Dale wrote:
>
>>
>> Now to avoid buying another one of these drives again.  I really wish
>> sellers who should know would put in the description or list of features
>> that the drive has PWDIS.  After all, most buyers of small quantities of
>> drives likely can't use that feature.  The ones who do likely buy in
>> bulk since they putting them in large systems. 
>>
>> Thanks to all.  I knew there would be someone on this list who actually
>> had one of these things. 
>>
>> Dale
>>
>> :-)  :-) 
>>
>
>
> I'm looking at buying another drive.  I'm trying to avoid buying one
> with the PWDIS pin.  I'm looking at the specs to see if it says anything
> about the feature, there or not there.  I'm not seeing anything.  This
> is what I'm looking at. 
>
> https://www.seagate.com/files/www-content/datasheets/pdfs/exos-x16-DS2011-1-1904US-en_US.pdf
>
> Can someone tell me how to know when a drive has PWDIS and when it
> doesn't?  Is there some term for it that shows in the specs and I'm
> missing it?  Or is there no way to really know? 
>
> Thanks. 
>
> Dale
>
> :-)  :-) 
>




Re: [gentoo-user] Hard drive and PWDIS or pin 3 power disable/reset.

2024-05-09 Thread Mark Knecht
On Thu, May 9, 2024 at 6:35 PM Mark Knecht  wrote:
>
>
> >
> >
> > I've looked for a adapter.  I couldn't find one.  That's why I
connected to a old rig that had a set of molex cables I could use.  Luckily
I had a molex to sata adapter.  Do you know what they are called so I know
what to search for?  I'd buy a dozen or so just to have extras laying
around.  I just can't find them.  I suspect I'm using the wrong search
terms.
> >
> > Do new motherboards support that PWDIS feature?  I'm looking at the
ASUS Prime X670-P mobo and I can't find anything that says what version of
SATA it has or about the PWDIS option.  I assume it doesn't have it but
assuming means you can be wrong.  I haven't looked at the new power supply
cables yet.  I've bought ATX style ones recently tho.  Look the same as old
ones to me.
> >
> > Dale
> >
> > :-)  :-)
>
> I am not sure but I think Molex to SATA Power gets you in the ballpark?
>
> https://www.amazon.com/Power-Cable-Adapter-Female-8-inch/dp/B07BQFKTG7
>
>
https://www.amazon.com/Duttek-Female-Adapter-Connector-Drives/dp/B09BJ1J24M
>
> If these are close then it wouldn't cost a lot to try one out. (<$10)

>
Sorry, I forgot to address your second question.

It is my understanding - good or bad I'll leave it to you - that newer
motherboards
are moving toward drive power supplied through the motherboard and not
through our old-style power supply cables. I don't think this is in the
market
yet in any big way, but when it arrives it would allow PWDIS to be
controlled through
software which then makes it easier to do 'hot swap' because the drive
isn't hot
when power is disabled. I suspect this is more of a server farm type issue
and
desktop machine users wouldn't be doing this because the form factor of the
machine itself isn't set up for that. However if you were to get some sort
of a
drive cage which you connected to using wider SATA specifications then you
could
disable power to one drive and swap it out without having to power the
machine down.

All supposition on my part. I'll leave it to you to dig deeper if you care.
(I don't !)

Best wish, good luck and happy hunting,
Mark


Re: [gentoo-user] Hard drive and PWDIS or pin 3 power disable/reset.

2024-05-09 Thread Mark Knecht
>
>
> I've looked for a adapter.  I couldn't find one.  That's why I connected
to a old rig that had a set of molex cables I could use.  Luckily I had a
molex to sata adapter.  Do you know what they are called so I know what to
search for?  I'd buy a dozen or so just to have extras laying around.  I
just can't find them.  I suspect I'm using the wrong search terms.
>
> Do new motherboards support that PWDIS feature?  I'm looking at the ASUS
Prime X670-P mobo and I can't find anything that says what version of SATA
it has or about the PWDIS option.  I assume it doesn't have it but assuming
means you can be wrong.  I haven't looked at the new power supply cables
yet.  I've bought ATX style ones recently tho.  Look the same as old ones
to me.
>
> Dale
>
> :-)  :-)

I am not sure but I think Molex to SATA Power gets you in the ballpark?

https://www.amazon.com/Power-Cable-Adapter-Female-8-inch/dp/B07BQFKTG7

https://www.amazon.com/Duttek-Female-Adapter-Connector-Drives/dp/B09BJ1J24M

If these are close then it wouldn't cost a lot to try one out. (<$10)


Re: [gentoo-user] Hard drive and PWDIS or pin 3 power disable/reset.

2024-05-09 Thread Dale
Mark Knecht wrote:
>
>
> On Thu, May 9, 2024 at 4:31 PM Dale  > wrote:
> >
> > Dale wrote:
> >
> > Mark Knecht wrote:
> >
> >
> >
> > On Thu, May 9, 2024 at 2:12 PM Dale  > wrote:
> > 
> > > Can someone tell me how to know when a drive has PWDIS and when it
> > > doesn't?  Is there some term for it that shows in the specs and I'm
> > > missing it?  Or is there no way to really know?
> >
> > I believe PWDIS is part of the SATA 3.3 spec so first filter would be
> > don't buy a SATA 3.3 drive for an old PC.
> >
> > I have done NO online research to take this with less than a
> > grain of salt.
> >
> > Mark
> >
> >
> >
> > Your reply gave me a clue.  I did a search for sata in the docs and
> found this for both drives I linked to in other post.
> >
> >
> > Exos X18 SATA drives incorporate connectors which enable users to
> hot plug these drives in accordance with the
> > Serial ATA Revision 3.3 specification.
> >
> >
> > I suspect that means it has the PWDIS pin.  You agree?  If you open
> the links to pdf docs in other reply, search for "Hot-Plug
> compatibility" and see what it says.  It was the second hit for me.
> >
> > Why can't they label those drives with something that makes it
> clear.  Print 'SATA V3.3', 'hardware reset enabled' or something that
> makes it easy instead of sticking it in a 50 something page document. 
> At least we have the "find" feature on most pdf viewers.  Another
> option, throw a adapter in the box for those who can't have that feature.
> >
> > Looks like both drives I'm looking at might not work for me.  My
> goal in this thread, figure out what to look for so that I avoid
> buying a drive that don't work.  I got the difference in the power
> cable at least.  Now to figure it out without being able to see the drive.
> >
> > Thoughts?
> >
> > Dale
> >
> > :-)  :-)
> >
> >
> >
> > I thought of something else.  I looked at drives I bought in the
> past.  I have a model ST16000NM000J and it works but it says it is
> SATA v3.3.  So, saying it is SATA v3.3 doesn't distinguish between
> having or not having the PWDIS feature.  It just means it is possible.
> >
> > Crap.  I thought I was onto something.  :(
> >
> > Dale
> >
> > :-)  :-)
> >
> > P. S.  Since I have one of those already, I'll buy that one again. 
> ROFL
>
> Dale,
>    You have raised a number of issues. I will speak as a retired Silicon 
> Valley engineer who worked on IEEE and PCI-related specifications.
> (PCI-X, 1394b and a few things that never made it to market)
>
> 1) Probably most important, the disk drive manufacturers are not 
> focused on those of us who fiddle with old hardware. They are 
> designing and developing products for the mass market which 
> basically means new machines. These drives do into data farms
> and new computers. 
>

This is very true.  If they were going to change the SATA power
connector pin assignment, they should have made it backward compatible. 
It would be easy enough.  Pin high, as it is when hooked to a old cable,
enables the drive.  Pin low disables or resets the drive.  That way no
matter what you connect it to, it works.  Why they didn't think of that,
I'd think it is about making money.  Just a thought.


> 2) The next issue is whether a new SATA-3.3 drive is even intended
> to work in a machine running old SATA spec. In the case of these
> SATA-3.3 drives there is a kluge connector/adapter cable that hooks
> to your existing SATA controller but has a PC power supply dongle
> so that the SATA-3.3 drive's PWDIS pin is 'hopefully' driven
> correctly. Whether that works does depend on the timing of your
> motherboard and the power supply, but it 'hopefully' works.
>
>    I don't know if this information is going to be helpful to your 
> immediate situation but possibly it will help you going forward
> when you are considering upgrading an old machine vs what
> I have done a couple of times is to purchase a new or used
> low-end motherboard so that my peripheral choices were 
> easier. (Such as now all of my DNS and Pi-Hole stuff running
> on an RP-5 vs an old x86-64 machine.)
>
> Best wishes and good luck,
> Mark


I've looked for a adapter.  I couldn't find one.  That's why I connected
to a old rig that had a set of molex cables I could use.  Luckily I had
a molex to sata adapter.  Do you know what they are called so I know
what to search for?  I'd buy a dozen or so just to have extras laying
around.  I just can't find them.  I suspect I'm using the wrong search
terms. 

Do new motherboards support that PWDIS feature?  I'm looking at the ASUS
Prime X670-P mobo and I can't find anything that says what version of
SATA it has or about the PWDIS option.  I assume it doesn't have it but
assuming means you can be wrong.  I haven't looked at the new power
supply cables yet.  I've bought ATX style ones recently tho.  Look the
same as old ones to me. 

Dale

:-)  :-) 


Re: [gentoo-user] Hard drive and PWDIS or pin 3 power disable/reset.

2024-05-09 Thread Mark Knecht
On Thu, May 9, 2024 at 4:31 PM Dale  wrote:
>
> Dale wrote:
>
> Mark Knecht wrote:
>
>
>
> On Thu, May 9, 2024 at 2:12 PM Dale  wrote:
> 
> > Can someone tell me how to know when a drive has PWDIS and when it
> > doesn't?  Is there some term for it that shows in the specs and I'm
> > missing it?  Or is there no way to really know?
>
> I believe PWDIS is part of the SATA 3.3 spec so first filter would be
> don't buy a SATA 3.3 drive for an old PC.
>
> I have done NO online research to take this with less than a
> grain of salt.
>
> Mark
>
>
>
> Your reply gave me a clue.  I did a search for sata in the docs and found
this for both drives I linked to in other post.
>
>
> Exos X18 SATA drives incorporate connectors which enable users to hot
plug these drives in accordance with the
> Serial ATA Revision 3.3 specification.
>
>
> I suspect that means it has the PWDIS pin.  You agree?  If you open the
links to pdf docs in other reply, search for "Hot-Plug compatibility" and
see what it says.  It was the second hit for me.
>
> Why can't they label those drives with something that makes it clear.
Print 'SATA V3.3', 'hardware reset enabled' or something that makes it easy
instead of sticking it in a 50 something page document.  At least we have
the "find" feature on most pdf viewers.  Another option, throw a adapter in
the box for those who can't have that feature.
>
> Looks like both drives I'm looking at might not work for me.  My goal in
this thread, figure out what to look for so that I avoid buying a drive
that don't work.  I got the difference in the power cable at least.  Now to
figure it out without being able to see the drive.
>
> Thoughts?
>
> Dale
>
> :-)  :-)
>
>
>
> I thought of something else.  I looked at drives I bought in the past.  I
have a model ST16000NM000J and it works but it says it is SATA v3.3.  So,
saying it is SATA v3.3 doesn't distinguish between having or not having the
PWDIS feature.  It just means it is possible.
>
> Crap.  I thought I was onto something.  :(
>
> Dale
>
> :-)  :-)
>
> P. S.  Since I have one of those already, I'll buy that one again.  ROFL

Dale,
   You have raised a number of issues. I will speak as a retired Silicon
Valley engineer who worked on IEEE and PCI-related specifications.
(PCI-X, 1394b and a few things that never made it to market)

1) Probably most important, the disk drive manufacturers are not
focused on those of us who fiddle with old hardware. They are
designing and developing products for the mass market which
basically means new machines. These drives do into data farms
and new computers.

2) The next issue is whether a new SATA-3.3 drive is even intended
to work in a machine running old SATA spec. In the case of these
SATA-3.3 drives there is a kluge connector/adapter cable that hooks
to your existing SATA controller but has a PC power supply dongle
so that the SATA-3.3 drive's PWDIS pin is 'hopefully' driven
correctly. Whether that works does depend on the timing of your
motherboard and the power supply, but it 'hopefully' works.

   I don't know if this information is going to be helpful to your
immediate situation but possibly it will help you going forward
when you are considering upgrading an old machine vs what
I have done a couple of times is to purchase a new or used
low-end motherboard so that my peripheral choices were
easier. (Such as now all of my DNS and Pi-Hole stuff running
on an RP-5 vs an old x86-64 machine.)

Best wishes and good luck,
Mark


Re: [gentoo-user] Hard drive and PWDIS or pin 3 power disable/reset.

2024-05-09 Thread Dale
Dale wrote:
> Mark Knecht wrote:
>>
>>
>> On Thu, May 9, 2024 at 2:12 PM Dale > > wrote:
>> 
>> > Can someone tell me how to know when a drive has PWDIS and when it
>> > doesn't?  Is there some term for it that shows in the specs and I'm
>> > missing it?  Or is there no way to really know?
>>
>> I believe PWDIS is part of the SATA 3.3 spec so first filter would be
>> don't buy a SATA 3.3 drive for an old PC.
>>
>> I have done NO online research to take this with less than a 
>> grain of salt.
>>
>> Mark
>
>
> Your reply gave me a clue.  I did a search for sata in the docs and
> found this for both drives I linked to in other post.
>
>
> Exos X18 SATA drives incorporate connectors which enable users to hot
> plug these drives in accordance with the
> Serial ATA Revision 3.3 specification. 
>
>
> I suspect that means it has the PWDIS pin.  You agree?  If you open
> the links to pdf docs in other reply, search for "Hot-Plug
> compatibility" and see what it says.  It was the second hit for me. 
>
> Why can't they label those drives with something that makes it clear. 
> Print 'SATA V3.3', 'hardware reset enabled' or something that makes it
> easy instead of sticking it in a 50 something page document.  At least
> we have the "find" feature on most pdf viewers.  Another option, throw
> a adapter in the box for those who can't have that feature. 
>
> Looks like both drives I'm looking at might not work for me.  My goal
> in this thread, figure out what to look for so that I avoid buying a
> drive that don't work.  I got the difference in the power cable at
> least.  Now to figure it out without being able to see the drive.
>
> Thoughts?
>
> Dale
>
> :-)  :-) 


I thought of something else.  I looked at drives I bought in the past. 
I have a model ST16000NM000J and it works but it says it is SATA v3.3. 
So, saying it is SATA v3.3 doesn't distinguish between having or not
having the PWDIS feature.  It just means it is possible.

Crap.  I thought I was onto something.  :(

Dale

:-)  :-) 

P. S.  Since I have one of those already, I'll buy that one again.  ROFL 


Re: [gentoo-user] Hard drive and PWDIS or pin 3 power disable/reset.

2024-05-09 Thread Dale
Mark Knecht wrote:
>
>
> On Thu, May 9, 2024 at 2:12 PM Dale  > wrote:
> 
> > Can someone tell me how to know when a drive has PWDIS and when it
> > doesn't?  Is there some term for it that shows in the specs and I'm
> > missing it?  Or is there no way to really know?
>
> I believe PWDIS is part of the SATA 3.3 spec so first filter would be
> don't buy a SATA 3.3 drive for an old PC.
>
> I have done NO online research to take this with less than a 
> grain of salt.
>
> Mark


Your reply gave me a clue.  I did a search for sata in the docs and
found this for both drives I linked to in other post.


Exos X18 SATA drives incorporate connectors which enable users to hot
plug these drives in accordance with the
Serial ATA Revision 3.3 specification. 


I suspect that means it has the PWDIS pin.  You agree?  If you open the
links to pdf docs in other reply, search for "Hot-Plug compatibility"
and see what it says.  It was the second hit for me. 

Why can't they label those drives with something that makes it clear. 
Print 'SATA V3.3', 'hardware reset enabled' or something that makes it
easy instead of sticking it in a 50 something page document.  At least
we have the "find" feature on most pdf viewers.  Another option, throw a
adapter in the box for those who can't have that feature. 

Looks like both drives I'm looking at might not work for me.  My goal in
this thread, figure out what to look for so that I avoid buying a drive
that don't work.  I got the difference in the power cable at least.  Now
to figure it out without being able to see the drive.

Thoughts?

Dale

:-)  :-) 


Re: [gentoo-user] Hard drive and PWDIS or pin 3 power disable/reset.

2024-05-09 Thread Mark Knecht
On Thu, May 9, 2024 at 2:12 PM Dale  wrote:

> Can someone tell me how to know when a drive has PWDIS and when it
> doesn't?  Is there some term for it that shows in the specs and I'm
> missing it?  Or is there no way to really know?

I believe PWDIS is part of the SATA 3.3 spec so first filter would be
don't buy a SATA 3.3 drive for an old PC.

I have done NO online research to take this with less than a
grain of salt.

Mark


Re: [gentoo-user] Hard drive and PWDIS or pin 3 power disable/reset.

2024-05-09 Thread Dale
Rich Freeman wrote:
> On Thu, May 9, 2024 at 5:12 PM Dale  wrote:
>> I'm looking at buying another drive.  I'm trying to avoid buying one
>> with the PWDIS pin.  I'm looking at the specs to see if it says anything
>> about the feature, there or not there.  I'm not seeing anything.  This
>> is what I'm looking at.
>>
>> https://www.seagate.com/files/www-content/datasheets/pdfs/exos-x16-DS2011-1-1904US-en_US.pdf
>>
>> Can someone tell me how to know when a drive has PWDIS and when it
>> doesn't?  Is there some term for it that shows in the specs and I'm
>> missing it?  Or is there no way to really know?
> I think it would be labeled as such.  That is for a genuine retail
> version of the drive with retail labeling.
>
> So if you get the drive and it has the pretty Exos logo and green
> colors and the model number that matches the datasheet and all that
> stuff, then it probably won't have issues.
>
> However, if you're buying something off ebay, and the drive just has a
> plain white label, and a model number that doesn't actually match the
> datasheet, but some random webpage or reddit post assures you that it
> is the same thing, well, it probably is the same thing, but it might
> very well have that power issue.
>
> Those shucked drives generally come from USB enclosures, and the drive
> on the inside might be a rebranded Exos with alternative firmware/etc,
> but the label isn't going to actually say that, and the package will
> say "EasyStore USB Drive" or whatever it is sold as.  If you use it
> the way it is sold, then you again won't have issues since its
> internal USB HBA will do the right thing.  It is just that when you
> rip open the box that all bets are off.
>
> The actual drives sold for enterprise use generally aren't sold in
> retail packaging as I understand it.  To get one of those officially
> you need to buy them through a server vendor or some other
> enterprise-oriented partner, who probably has a nice sales person who
> will treat you to a free lunch while you talk about the PWDIS
> requirements of the $10M pallet of drives you're about to buy.
>


I found this. 

https://www.seagate.com/www-content/product-content/enterprise-hdd-fam/exos-x-16/en-us/docs/100845789j.pdf

If you scroll down to page 29, or search for Table 11, it says it has a
3.3V for pin 1 to pin 3.  Does that indicate it has the PWDIS feature? 
I'm buying these from a company that has server in the name.  I buy
drives of this type because of the way I use it.  It runs 24/7. 
Downtime is minimal here.  This is a link to the drives I'm looking at. 
I'm not sure which is best to be honest.  Opinions??

https://www.ebay.com/itm/124627725410

https://www.ebay.com/itm/304194684486

I'm interested in your thoughts on the PWDIS and if one of those drives
would be better for my use case.  Biggest thing, runs 24/7. 

Oh, is there a adapter that I can buy that fixes this?  I did a ebay
search but didn't find anything.  Maybe I used the wrong terms.

Dale

:-)  :-) 

P. S.  I'm considering using SAS controllers again.  Do you have links
that explains how drives are connected and such?  I'll likely continue
to use SATA drives since I have so many but may start buying SAS
drives.  I think both can be used depending on the cable.  From what
I've read, there is more than one way for a SAS controller to work. 
It's confusing at times. 



Re: [gentoo-user] Hard drive and PWDIS or pin 3 power disable/reset.

2024-05-09 Thread Rich Freeman
On Thu, May 9, 2024 at 5:12 PM Dale  wrote:
>
> I'm looking at buying another drive.  I'm trying to avoid buying one
> with the PWDIS pin.  I'm looking at the specs to see if it says anything
> about the feature, there or not there.  I'm not seeing anything.  This
> is what I'm looking at.
>
> https://www.seagate.com/files/www-content/datasheets/pdfs/exos-x16-DS2011-1-1904US-en_US.pdf
>
> Can someone tell me how to know when a drive has PWDIS and when it
> doesn't?  Is there some term for it that shows in the specs and I'm
> missing it?  Or is there no way to really know?

I think it would be labeled as such.  That is for a genuine retail
version of the drive with retail labeling.

So if you get the drive and it has the pretty Exos logo and green
colors and the model number that matches the datasheet and all that
stuff, then it probably won't have issues.

However, if you're buying something off ebay, and the drive just has a
plain white label, and a model number that doesn't actually match the
datasheet, but some random webpage or reddit post assures you that it
is the same thing, well, it probably is the same thing, but it might
very well have that power issue.

Those shucked drives generally come from USB enclosures, and the drive
on the inside might be a rebranded Exos with alternative firmware/etc,
but the label isn't going to actually say that, and the package will
say "EasyStore USB Drive" or whatever it is sold as.  If you use it
the way it is sold, then you again won't have issues since its
internal USB HBA will do the right thing.  It is just that when you
rip open the box that all bets are off.

The actual drives sold for enterprise use generally aren't sold in
retail packaging as I understand it.  To get one of those officially
you need to buy them through a server vendor or some other
enterprise-oriented partner, who probably has a nice sales person who
will treat you to a free lunch while you talk about the PWDIS
requirements of the $10M pallet of drives you're about to buy.

-- 
Rich



Re: [gentoo-user] Hard drive and PWDIS or pin 3 power disable/reset.

2024-05-09 Thread Dale
Dale wrote:
>
> Now to avoid buying another one of these drives again.  I really wish
> sellers who should know would put in the description or list of features
> that the drive has PWDIS.  After all, most buyers of small quantities of
> drives likely can't use that feature.  The ones who do likely buy in
> bulk since they putting them in large systems. 
>
> Thanks to all.  I knew there would be someone on this list who actually
> had one of these things. 
>
> Dale
>
> :-)  :-) 
>


I'm looking at buying another drive.  I'm trying to avoid buying one
with the PWDIS pin.  I'm looking at the specs to see if it says anything
about the feature, there or not there.  I'm not seeing anything.  This
is what I'm looking at. 

https://www.seagate.com/files/www-content/datasheets/pdfs/exos-x16-DS2011-1-1904US-en_US.pdf

Can someone tell me how to know when a drive has PWDIS and when it
doesn't?  Is there some term for it that shows in the specs and I'm
missing it?  Or is there no way to really know? 

Thanks. 

Dale

:-)  :-) 



Re: [gentoo-user] PERL_FEATURES

2024-05-07 Thread Helmut Jarausch

Many thanks, that helped a lot!
Now I have set only those features in the PERL_FEATURES entry that were  
installed before -
the warning has gone and I hoped the correct version of perl is  
installed now.

Helmut


On 05/07/2024 08:29:28 PM, Jack wrote:

On 2024.05.07 12:33, Helmut Jarausch wrote:

Hi,

according to the NEWS from today one has to set PERL_FEATURES in  
/etc/portage/make.conf.

But how to do that?

I've tried

PERL_FEATURES="debug ithreads quadmath"

but emerging  dev-lang/perl-5.38.2-r3  I get


 * As of dev-lang/perl-5.38.2-r3, the useflags debug, ithreads,  
quadmath move into
 * a use-expand variable PERL_FEATURES, which should be set globally  
in make.conf.

 * It appears that you have not set this variable properly yet.

Many thanks for hint,
Helmut


The section of the ebuild that decides whether or not to issue that  
warning is:


pkg_pretend() {
if \
		 (   use perl_features_ithreads && has_version  
'		 ( ! use perl_features_ithreads && has_version  
'		 (   use perl_features_quadmath && has_version  
'		 ( ! use perl_features_quadmath && has_version  
'		 (   use perl_features_debug&& has_version  
'		 ( ! use perl_features_debug&& has_version  
'
then
 (issue the warning)

As I read it (which may well be wrong) it is looking to see whether  
the value for each of the three items is the same by the old use flag  
and by the new PERL_FEATURES.   Check how those three use flags are  
set for -r2 and that the value for PERL_FEATURES for -r3 matches for  
each.






Re: [gentoo-user] Hard drive and PWDIS or pin 3 power disable/reset.

2024-05-07 Thread Dale
Rich Freeman wrote:
> On Tue, May 7, 2024 at 6:04 AM Michael  wrote:
>> On Tuesday, 7 May 2024 08:50:26 BST Dale wrote:
>>> I'm aware of what it is and the cable part.  I was curious what it looks
>>> like to BIOS and the OS when one is connected and that pin has the drive
>>> disabled.  From what I've read in some places, the drive doesn't power
>>> up at all.
>> I don't have a drive like this, but as I understand it when the drive 
>> receives
>> voltage on pin 3 it powers down.  This requires a MoBo and firmware which
>> supports such a function - probably unlikely to be found on consumer kit.
> I have had these drives.  If the drive is connected to many ATX power
> supplies via a standard cable, the drive simply will not be detected
> by the computer.  With some power supplies it will work fine.  It all
> depends on whether the power supply follows the original SATA spec, or
> was designed to be compatible with enterprise drives which use the
> revised spec, which isn't backwards compatible (I don't know who the
> genius was who had that idea).
>
> In order to actually toggle the reset line you need SOMETHING able to
> switch the line in-between the drive and the PSU.  That might be a
> motherboard (especially with the newer trend towards running all the
> power through the motherboard), or some other accessory card.  Unless
> the HBA provides the power it won't be there.
>
> However, you don't need any fancy hardware for the drive to just work
> - that is only needed to send the hardware reset to the drive.  All
> you need is to not have that pin powered.  That just means the right
> power supply, the right cable, the right adapter, or some improvised
> solution (tape over the pin is a common one).
>
> In any case, if the pin is the problem, the drive simply won't be
> detected.  Your SATA issues are due to something else.  It might be a
> bad drive, an incompatibility (maybe the drive isn't in the
> smartmontools database yet), or maybe an issue with the HBA (for USB
> HBAs in particular you often need to pass command line parameters as
> there apparently isn't a standard way to pass these commands over
> USB).  I doubt the power line is your problem.
>
> As far as shucked drives go - that is typically indicated by the
> label/model.  If it isn't branded in any way it may have been shucked.
> That shouldn't be a problem as long as you don't have the power issue
> - the drive might simply be bad.
>


So, since the drive wasn't seen at all on my main rig or the NAS box,
with a straight sata power connector, then it likely has the PWDIS pin. 
On those two rigs, the drive wasn't seen at all not even in the BIOS. 
Since it was seen on the old Dell rig with a molex  sata adapter but
SMART spit out a lot of errors, then the drive is bad.  Now that makes
sense and was kinda what I was thinking but not sure about.  Not only
did I get a drive with the PWDIS feature, I got a bad drive as well. 
While the box had no damage at all, it doesn't mean it didn't get hit or
dropped and was damaged or went bad some other way. 

My take on this for future reference.  If a drive isn't seen at all even
by BIOS, either the drive is completely dead or it has the PWDIS feature. 

Oh, I wonder to about the genius who forgot to make this new feature
backward compatible.  I hope someone Gibbs smacks him real good.  Maybe
twice. 

Now to avoid buying another one of these drives again.  I really wish
sellers who should know would put in the description or list of features
that the drive has PWDIS.  After all, most buyers of small quantities of
drives likely can't use that feature.  The ones who do likely buy in
bulk since they putting them in large systems. 

Thanks to all.  I knew there would be someone on this list who actually
had one of these things. 

Dale

:-)  :-) 



Re: [gentoo-user] PERL_FEATURES

2024-05-07 Thread Jack

On 2024.05.07 12:33, Helmut Jarausch wrote:

Hi,

according to the NEWS from today one has to set PERL_FEATURES in  
/etc/portage/make.conf.

But how to do that?

I've tried

PERL_FEATURES="debug ithreads quadmath"

but emerging  dev-lang/perl-5.38.2-r3  I get


 * As of dev-lang/perl-5.38.2-r3, the useflags debug, ithreads,  
quadmath move into
 * a use-expand variable PERL_FEATURES, which should be set globally  
in make.conf.

 * It appears that you have not set this variable properly yet.

Many thanks for hint,
Helmut


The section of the ebuild that decides whether or not to issue that  
warning is:


pkg_pretend() {
if \
		 (   use perl_features_ithreads && has_version  
'		 ( ! use perl_features_ithreads && has_version  
'		 (   use perl_features_quadmath && has_version  
'		 ( ! use perl_features_quadmath && has_version  
'		 (   use perl_features_debug&& has_version  
'		 ( ! use perl_features_debug&& has_version  
'
then
 (issue the warning)

As I read it (which may well be wrong) it is looking to see whether the  
value for each of the three items is the same by the old use flag and  
by the new PERL_FEATURES.   Check how those three use flags are set for  
-r2 and that the value for PERL_FEATURES for -r3 matches for each.




[gentoo-user] PERL_FEATURES

2024-05-07 Thread Helmut Jarausch

Hi,

according to the NEWS from today one has to set PERL_FEATURES in  
/etc/portage/make.conf.

But how to do that?

I've tried

PERL_FEATURES="debug ithreads quadmath"

but emerging  dev-lang/perl-5.38.2-r3  I get


 * As of dev-lang/perl-5.38.2-r3, the useflags debug, ithreads,  
quadmath move into
 * a use-expand variable PERL_FEATURES, which should be set globally  
in make.conf.

 * It appears that you have not set this variable properly yet.

Many thanks for hint,
Helmut



Re: [gentoo-user] bad $PATH

2024-05-07 Thread Jorge Almeida
On Tue, 7 May 2024 at 15:37, Neil Bothwick  wrote:

> On Tue, 7 May 2024 13:22:47 +0100, Jorge Almeida wrote:
>
> > > Yes, of course.  When I said "emerge -c doesn't clean it"  I meant
> > > "emerge
> > -c" (without arguments). I know how to unmerge a package, which in this
> > particular case I should have done years ago, but didn't, and forgot
> > about it.
>
> Right, so we were talking at cross purposes. Apologies for the line noise.
>
> No problem. Cheers


Re: [gentoo-user] bad $PATH

2024-05-07 Thread Neil Bothwick
On Tue, 7 May 2024 13:22:47 +0100, Jorge Almeida wrote:

> > Yes, of course.  When I said "emerge -c doesn't clean it"  I meant
> > "emerge  
> -c" (without arguments). I know how to unmerge a package, which in this
> particular case I should have done years ago, but didn't, and forgot
> about it.

Right, so we were talking at cross purposes. Apologies for the line noise.


-- 
Neil Bothwick

without C people would code in Basi, Pasal and Obol


pgpGh2LN46Zaj.pgp
Description: OpenPGP digital signature


Re: [gentoo-user] bad $PATH

2024-05-07 Thread Jorge Almeida
On Tue, 7 May 2024 at 13:10, Neil Bothwick  wrote:

> On Tue, 7 May 2024 11:32:43 +0100, Jorge Almeida wrote:
>
>
>
> Files in @world should only be wanted because you put them in there, so
> you should be able to remove them.
>
> Yes, of course.  When I said "emerge -c doesn't clean it"  I meant "emerge
-c" (without arguments). I know how to unmerge a package, which in this
particular case I should have done years ago, but didn't, and forgot about
it.

Jorge


Re: [gentoo-user] bad $PATH

2024-05-07 Thread Neil Bothwick
On Tue, 7 May 2024 11:32:43 +0100, Jorge Almeida wrote:

> > > I seem to remember I installed a long time ago. It is in the world
> > > file, hence emerge -c wouldn't clean it. I don't have csh but think
> > > I had it  
> >
> > emerge -c will remove packages that are in @world. It was probably
> > also a dependency of something else when you tried before.
> >
> Hmmm... This  would seem to contradict the man page. 

From man emerge

   --depclean, -c 
   Cleans the system by removing packages that are not
   associated with explicitly merged packages. Depclean works by
   creating the full dependency tree from the @world set, then
   comparing  it to installed packages. Packages installed, but not
   part of the dependency tree, will be uninstalled by depclean.

It is a little ambiguous in that does the dependency tree from the world
set include the world set itself?

> How would emerge -c  
> decide which packages in the world file were unwanted? Maybe you're
> thinking of slotted packages?

No, just tried it. Pick a file from @world and emerge -cpv it.

[root@phoucgh ~ 0]% grep x11vnc /var/lib/portage/world
x11-misc/x11vnc
[root@phoucgh ~ 0]% emerge -cpv x11vnc

Calculating dependencies... done!
>>> Calculating removal order...

>>> These are the packages that would be unmerged:

 x11-misc/x11vnc
selected: 0.9.16-r8 
   protected: none 
 omitted: none 

All selected packages: =x11-misc/x11vnc-0.9.16-r8

>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.

Packages installed:   2083
Packages in world:350
Packages in system:   49
Required packages:2082
Number to remove: 1

Files in @world should only be wanted because you put them in there, so
you should be able to remove them.


-- 
Neil Bothwick

"What I need is a list of specific unknown problems we will encounter."


pgpJ1zRxuqJO9.pgp
Description: OpenPGP digital signature


Re: [gentoo-user] Hard drive and PWDIS or pin 3 power disable/reset.

2024-05-07 Thread Rich Freeman
On Tue, May 7, 2024 at 6:04 AM Michael  wrote:
>
> On Tuesday, 7 May 2024 08:50:26 BST Dale wrote:
> >
> > I'm aware of what it is and the cable part.  I was curious what it looks
> > like to BIOS and the OS when one is connected and that pin has the drive
> > disabled.  From what I've read in some places, the drive doesn't power
> > up at all.
>
> I don't have a drive like this, but as I understand it when the drive receives
> voltage on pin 3 it powers down.  This requires a MoBo and firmware which
> supports such a function - probably unlikely to be found on consumer kit.

I have had these drives.  If the drive is connected to many ATX power
supplies via a standard cable, the drive simply will not be detected
by the computer.  With some power supplies it will work fine.  It all
depends on whether the power supply follows the original SATA spec, or
was designed to be compatible with enterprise drives which use the
revised spec, which isn't backwards compatible (I don't know who the
genius was who had that idea).

In order to actually toggle the reset line you need SOMETHING able to
switch the line in-between the drive and the PSU.  That might be a
motherboard (especially with the newer trend towards running all the
power through the motherboard), or some other accessory card.  Unless
the HBA provides the power it won't be there.

However, you don't need any fancy hardware for the drive to just work
- that is only needed to send the hardware reset to the drive.  All
you need is to not have that pin powered.  That just means the right
power supply, the right cable, the right adapter, or some improvised
solution (tape over the pin is a common one).

In any case, if the pin is the problem, the drive simply won't be
detected.  Your SATA issues are due to something else.  It might be a
bad drive, an incompatibility (maybe the drive isn't in the
smartmontools database yet), or maybe an issue with the HBA (for USB
HBAs in particular you often need to pass command line parameters as
there apparently isn't a standard way to pass these commands over
USB).  I doubt the power line is your problem.

As far as shucked drives go - that is typically indicated by the
label/model.  If it isn't branded in any way it may have been shucked.
That shouldn't be a problem as long as you don't have the power issue
- the drive might simply be bad.

-- 
Rich



Re: [gentoo-user] bad $PATH

2024-05-07 Thread Jorge Almeida
On Tue, 7 May 2024 at 10:36, Neil Bothwick  wrote:

> On Thu, 2 May 2024 16:37:24 +0100, Jorge Almeida wrote:
>
> >
> > I seem to remember I installed a long time ago. It is in the world file,
> > hence emerge -c wouldn't clean it. I don't have csh but think I had it
>
> emerge -c will remove packages that are in @world. It was probably also a
> dependency of something else when you tried before.
>
> Hmmm... This  would seem to contradict the man page. How would emerge -c
decide which packages in the world file were unwanted? Maybe you're
thinking of slotted packages?

Jorge


Re: [gentoo-user] Hard drive and PWDIS or pin 3 power disable/reset.

2024-05-07 Thread Michael
On Tuesday, 7 May 2024 08:50:26 BST Dale wrote:
> William Kenworthy wrote:
> > See https://www.disctech.com/powerdisable
> > 
> > BillK
> 
> I'm aware of what it is and the cable part.  I was curious what it looks
> like to BIOS and the OS when one is connected and that pin has the drive
> disabled.  From what I've read in some places, the drive doesn't power
> up at all.  I've seen some claim it shows up but you can't access it. 
> I've read different explanations of what the drive does and maybe it
> varies from one maker to another.  What I was hoping for, someone on
> this list has connected a drive with that pin disabling the drive and
> can confirm what I posted is what it looks like or explain what the
> system does when one is connected. 
> 
> When I connected that drive to my NAS box, it was very slow to go
> through the BIOS post and where it usually lists the connected drives,
> only the drive with the OS showed up.  When connected to the older Dell
> rig, it booted up normally.  It doesn't list connected drives like the
> NAS box does.  It did show up in /proc/partitions.  The SMART command
> showed a different story.  It makes it look like the drive has power but
> may not be spinning up.  It can get the info such as model number,
> serial number, capacity and other info but can't read the SMART data,
> which I assume is written to the platter part of the drive.  I'm not
> sure on that tho.  What I don't know, is that because of the PWDIS pin
> or has nothing to do with it. 
> 
> As it is, the seller agreed to take the drive back.  If the seller says
> the drive works for them, I guess it has that PWDIS feature.  If it
> doesn't work for them, just a bad drive, perhaps damaged in shipping or
> something.  I'm just curious as to how a drive behaves when it has that
> PWDIS pin and the drive is disabled. 
> 
> I did notice in the pic on your link that the new power connector has 5
> wires.  It has the PWDIS ability.  Mine has 4 wires.  However, I've read
> that on the older systems, the pins inside the connector apply power to
> pin 3 which disables the drives.  Mine doesn't have that extra wire but
> I don't think that really matters.  Maybe I need to put a voltmeter on
> the connector and see if there is anything on pin 3 or not.  I suspect
> there is tho. 
> 
> Has anyone had one of these drives connected and remember what the
> system reports when disabled??  What clues it gives that shows it is
> disabled if any??
> 
> Dale
> 
> :-)  :-) 

I don't have a drive like this, but as I understand it when the drive receives 
voltage on pin 3 it powers down.  This requires a MoBo and firmware which 
supports such a function - probably unlikely to be found on consumer kit.

https://documents.westerndigital.com/content/dam/doc-library/en_us/assets/
public/western-digital/collateral/tech-brief/tech-brief-western-digital-power-
disable-pin.pdf

If the drive does not spin up, you could try to insulate pin 3 with 
electrician's tape and see if the disk spins up, or use a molex power adaptor 
as already discussed.  Usually you can feel the disk vibrating when powering 
up.

Since you managed to make it spin but smartclt barfs, I would think there is 
something wrong with it.  Either way, life is too short to bother with disks 
which do not work as you reasonably expect them to work.  RMA it and/or buy a 
different disk after you confirm its replacement does not come with a PWDIS 
feature.


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] bad $PATH

2024-05-07 Thread Neil Bothwick
On Thu, 2 May 2024 16:37:24 +0100, Jorge Almeida wrote:

> So, it seems I have at least one package which I wouldn't expect to
> have: app-admin/xstow
> 
> I seem to remember I installed a long time ago. It is in the world file,
> hence emerge -c wouldn't clean it. I don't have csh but think I had it
> once upon a time. Removing...

emerge -c will remove packages that are in @world. It was probably also a
dependency of something else when you tried before.


-- 
Neil Bothwick

"Mmmm, trouble with grammer have I, yes?" - Yoda


pgp4VKqIbtUUd.pgp
Description: OpenPGP digital signature


Re: [gentoo-user] Hard drive and PWDIS or pin 3 power disable/reset.

2024-05-07 Thread Dale
William Kenworthy wrote:
> See https://www.disctech.com/powerdisable
>
> BillK
>

I'm aware of what it is and the cable part.  I was curious what it looks
like to BIOS and the OS when one is connected and that pin has the drive
disabled.  From what I've read in some places, the drive doesn't power
up at all.  I've seen some claim it shows up but you can't access it. 
I've read different explanations of what the drive does and maybe it
varies from one maker to another.  What I was hoping for, someone on
this list has connected a drive with that pin disabling the drive and
can confirm what I posted is what it looks like or explain what the
system does when one is connected. 

When I connected that drive to my NAS box, it was very slow to go
through the BIOS post and where it usually lists the connected drives,
only the drive with the OS showed up.  When connected to the older Dell
rig, it booted up normally.  It doesn't list connected drives like the
NAS box does.  It did show up in /proc/partitions.  The SMART command
showed a different story.  It makes it look like the drive has power but
may not be spinning up.  It can get the info such as model number,
serial number, capacity and other info but can't read the SMART data,
which I assume is written to the platter part of the drive.  I'm not
sure on that tho.  What I don't know, is that because of the PWDIS pin
or has nothing to do with it. 

As it is, the seller agreed to take the drive back.  If the seller says
the drive works for them, I guess it has that PWDIS feature.  If it
doesn't work for them, just a bad drive, perhaps damaged in shipping or
something.  I'm just curious as to how a drive behaves when it has that
PWDIS pin and the drive is disabled. 

I did notice in the pic on your link that the new power connector has 5
wires.  It has the PWDIS ability.  Mine has 4 wires.  However, I've read
that on the older systems, the pins inside the connector apply power to
pin 3 which disables the drives.  Mine doesn't have that extra wire but
I don't think that really matters.  Maybe I need to put a voltmeter on
the connector and see if there is anything on pin 3 or not.  I suspect
there is tho. 

Has anyone had one of these drives connected and remember what the
system reports when disabled??  What clues it gives that shows it is
disabled if any??

Dale

:-)  :-) 



Re: [gentoo-user] Hard drive and PWDIS or pin 3 power disable/reset.

2024-05-06 Thread William Kenworthy

See https://www.disctech.com/powerdisable

BillK


On 7/5/24 09:00, Dale wrote:

Howdy,

I ordered another hard drive, yup, I keep filling them up.  Anyway, it
looks like a shucked drive but may not be.  I tried to find out if there
is a way to know if a drive has that pin 3 problem or not but no luck.
It did power up after I hooked it to a old system with a molex to sata
power adapter.  Then the SMART tests went wonky, bad wonky.  This is
what it showed.


NAS2 ~ # smartctl -a /dev/sdb
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.8.7-gentoo] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model: ST16000NM000D
Serial Number:    ZVTC8V09
LU WWN Device Id: 5 000c50 0e79eb73e
Firmware Version: SN03
User Capacity:    16,000,900,661,248 bytes [16.0 TB]
Sector Size:  512 bytes logical/physical
Rotation Rate:    7200 rpm
Device is:    Not in smartctl database 7.3/5528
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s
Local Time is:    Mon May  6 15:51:00 2024 CDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Read SMART Data failed: scsi error device not ready

=== START OF READ SMART DATA SECTION ===
SMART Status command failed: scsi error badly formed scsi parameters
SMART overall-health self-assessment test result: UNKNOWN!
SMART Status, Attributes and Thresholds cannot be read.

Read SMART Log Directory failed: scsi error device not ready

Read SMART Error Log failed: scsi error device not ready

Read SMART Self-test Log failed: scsi error device not ready

Selective Self-tests/Logging not supported

NAS2 ~ #


Does anyone know what it looks like when a drive has that PWDIS feature
and the drive is disabled?  Does it look like that?  The drive would not
power up at all on my main rig or my NAS box but with the molex to sata
cable on the old Dell Inspiron, NAS@ box, it did power up but was really
slow to be seen and SMART shows the above.  Either way, PWDIS feature or
just a DOA drive, it won't work in my main rig which is where I want it
to go.  I requested a refund.  I'll buy one I can do more research on
next time.

I'm mostly just curious on this.  I've never actually had a drive with
the PWDIS pin.  Other than I've read they don't power up at all, I have
no idea how they respond or if they respond at all.  I figure someone on
the list has seen one.  If this is how they behave, I'll know next
time.  If they just off period, then a bad drive.

Thanks.

Dale

:-)  :-)







[gentoo-user] Hard drive and PWDIS or pin 3 power disable/reset.

2024-05-06 Thread Dale
Howdy,

I ordered another hard drive, yup, I keep filling them up.  Anyway, it
looks like a shucked drive but may not be.  I tried to find out if there
is a way to know if a drive has that pin 3 problem or not but no luck. 
It did power up after I hooked it to a old system with a molex to sata
power adapter.  Then the SMART tests went wonky, bad wonky.  This is
what it showed. 


NAS2 ~ # smartctl -a /dev/sdb
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.8.7-gentoo] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model: ST16000NM000D
Serial Number:    ZVTC8V09
LU WWN Device Id: 5 000c50 0e79eb73e
Firmware Version: SN03
User Capacity:    16,000,900,661,248 bytes [16.0 TB]
Sector Size:  512 bytes logical/physical
Rotation Rate:    7200 rpm
Device is:    Not in smartctl database 7.3/5528
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s
Local Time is:    Mon May  6 15:51:00 2024 CDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Read SMART Data failed: scsi error device not ready

=== START OF READ SMART DATA SECTION ===
SMART Status command failed: scsi error badly formed scsi parameters
SMART overall-health self-assessment test result: UNKNOWN!
SMART Status, Attributes and Thresholds cannot be read.

Read SMART Log Directory failed: scsi error device not ready

Read SMART Error Log failed: scsi error device not ready

Read SMART Self-test Log failed: scsi error device not ready

Selective Self-tests/Logging not supported

NAS2 ~ #


Does anyone know what it looks like when a drive has that PWDIS feature
and the drive is disabled?  Does it look like that?  The drive would not
power up at all on my main rig or my NAS box but with the molex to sata
cable on the old Dell Inspiron, NAS@ box, it did power up but was really
slow to be seen and SMART shows the above.  Either way, PWDIS feature or
just a DOA drive, it won't work in my main rig which is where I want it
to go.  I requested a refund.  I'll buy one I can do more research on
next time. 

I'm mostly just curious on this.  I've never actually had a drive with
the PWDIS pin.  Other than I've read they don't power up at all, I have
no idea how they respond or if they respond at all.  I figure someone on
the list has seen one.  If this is how they behave, I'll know next
time.  If they just off period, then a bad drive.

Thanks.

Dale

:-)  :-) 



Re: [gentoo-user] Grub, gpt partitions and BIOS, not uefi thing.

2024-05-05 Thread Dale
Dale wrote:
> Michael wrote:
>> On Sunday, 28 April 2024 13:57:23 BST Dale wrote:
>>
>>> I just got to figure out how to make it so I can login as root via ssh
>>> again.  I set PermitRootLogin to yes in ssh config but still refuses.  I
>>> did it on my NAS box but can't recall what else I had to do.
>> Just checking the obvious, did you start sshd?
>>
>> Is a port open and listening for ssh connections (use nc, telnet, nmap to 
>> find 
>> out).
>>
>> Will it let you login as a plain user, then 'su' to run as root?
>>
>> Make sure the plain user is in the wheel group.
>
> Right now, I can login as a user then su to root, and password.  I just
> can't login as root directly.  I use Dolphin and the fish thingy to
> access config files etc so I can use Kwrite to edit files etc.  Thing
> is, I have to login as root for some files.  No way to su to root with
> Dolphin, that I know of anyway. 
>
> I'm pretty sure I set this up on the old NAS box.  My searches shows the
> PermitRootLogin set to yes should do it but I guess I missed something. 
>
> Any ideas?  I did search old threads but only found the option above,
> mentioned by Neil I think. 
>
> Dale
>
> :-)  :-) 
>


I figured it out.  I was editing ssh_config when I should be editing
sshd_config.  Note the "d" in there.  After doing some digging, a lot of
digging, I finally noticed that extra "d" in there.  Now it works and I
can use a file manager like Dolphin or something and fish to edit files,
move them around etc. 

Amazing how one letter can really mess things up.  ;-) 

Dale

:-)  :-) 



Re: [gentoo-user] bad $PATH

2024-05-02 Thread Jorge Almeida
On Thu, 2 May 2024 at 14:09, Peter Humphrey  wrote:

> On Thursday, 2 May 2024 13:55:42 BST Jorge Almeida wrote:
> > I have
> > /var/lib/bin
> > in my $PATH (both as root and as normal user)
>
> > Anyone with the same problem/weirdness?
>
> Nope. Have you tried 'grep -r var/lib/bin /etc' ?
>
> I tried now:
/etc/profile.env:export
PATH='/usr/local/sbin:/usr/local/bin:/usr/bin:/opt/bin:/usr/lib/llvm/17/bin:/var/lib/bin'
/etc/environment.d/10-gentoo-env.conf:PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/opt/bin:/usr/lib/llvm/17/bin:/var/lib/bin
/etc/env.d/99xstow:PATH=/var/lib/bin
/etc/csh.env:setenv PATH
'/usr/local/sbin:/usr/local/bin:/usr/bin:/opt/bin:/usr/lib/llvm/17/bin:/var/lib/bin'

So, it seems I have at least one package which I wouldn't expect to
have: app-admin/xstow

I seem to remember I installed a long time ago. It is in the world file,
hence emerge -c wouldn't clean it. I don't have csh but think I had it once
upon a time. Removing...

Ok, done, and the PATH is fine now.

Thanks,

Jorge


Re: [gentoo-user] bad $PATH

2024-05-02 Thread Jorge Almeida
On Thu, 2 May 2024 at 15:07, Petr Vaněk  wrote:

> On Thu, May 02, 2024 at 01:55:42PM +0100, Jorge Almeida wrote:
> > I have /var/lib/bin in my $PATH (both as root and as normal user)
> >
> Do you have app-admin/xstow installed? This seems to be the (only)
>
Indeed, I had it in the world file, currently unused and long forgotten.
Solved..

Thanks,
Jorge


Re: [gentoo-user] bad $PATH

2024-05-02 Thread Petr Vaněk
On Thu, May 02, 2024 at 01:55:42PM +0100, Jorge Almeida wrote:
> I have /var/lib/bin in my $PATH (both as root and as normal user)
> 
> [snip] What could be setting this?  (grep /var/lib/bin /etc/conf.d/*
> returns nothing)

Do you have app-admin/xstow installed? This seems to be the (only)
package which adds /var/lib/bin to the PATH, see [1]. At least, I was
able to grep -F var/lib/bin pattern only in this package in ::gentoo
overlay.

[1] 
https://github.com/gentoo/gentoo/blob/c2fb597e863fb296b5cdaf36e8b258b20c47d4a1/app-admin/xstow/xstow-1.1.0.ebuild#L51-L52

Petr



Re: [gentoo-user] bad $PATH

2024-05-02 Thread Peter Humphrey
On Thursday, 2 May 2024 13:55:42 BST Jorge Almeida wrote:
> I have
> /var/lib/bin
> in my $PATH (both as root and as normal user)
> 
> That directory does not exist. Should it exist!?
> What could be setting this?
> (grep /var/lib/bin /etc/conf.d/* returns nothing)
> 
> Anyone with the same problem/weirdness?

Nope. Have you tried 'grep -r var/lib/bin /etc' ?

-- 
Regards,
Peter.


signature.asc
Description: This is a digitally signed message part.


[gentoo-user] bad $PATH

2024-05-02 Thread Jorge Almeida
I have
/var/lib/bin
in my $PATH (both as root and as normal user)

That directory does not exist. Should it exist!?
What could be setting this?
(grep /var/lib/bin /etc/conf.d/* returns nothing)

Anyone with the same problem/weirdness?

Thanks

Jorge Almeida


Re: [gentoo-user] Re: Grub, gpt partitions and BIOS, not uefi thing.

2024-05-02 Thread Peter Humphrey
On Thursday, 2 May 2024 00:45:29 BST Dale wrote:
> Grant Edwards wrote:
> > OK, so 'boot' is for the Linux /boot directory.  I was just curious
> > since I had never used one.

When I started using Linux, the received wisdom was to keep a separate /boot, 
and leave it unmounted during normal operation. The idea was that a successful 
hacker would not, supposedly, be able to corrupt the kernel ready for a reboot 
into their system.

Old habits die hard, though, and besides, a separate /boot has been handy in 
the copious reinstallations I've been through.

> I've used one ever since I started using Linux and it's as much habit as
> anything.  Given the size of drives nowadays, I have started putting
> /usr and /var on the root partition.  When I build my new rig tho, odds
> are /var will be on its own partition.  That way if a log file goes
> wonky, it can fill it up and not really do any harm. 

I do that too. It also helps with backups and new installations.

-- 
Regards,
Peter.


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Re: Grub, gpt partitions and BIOS, not uefi thing.

2024-05-02 Thread Dale
Michael wrote:
> On Thursday, 2 May 2024 00:45:29 BST Dale wrote:
>> Grant Edwards wrote:
>>> On 2024-05-01, Dale  wrote:
 Grant Edwards wrote:
> The partition type code for 'swap' is wrong -- it should be
> 8200. According to the gdisk help info Linux /home is supposed to be
> 8302, but I've always used the same generic "Linux filesystem" type
> for both /home and root.
>
> Is the 'boot' partition for future possible UEFI use, for Linux /boot,
> or both?  [I've never used a separate partition for Linux /boot, I
> just use a /boot directory on the root FS.]
 I noticed the other day that some new ones was added.  I always leave it
 as 8300 and it works.  It even works for swap.  I dunno. 
> In the legacy DOS partition tables the space available was limited to 32 
> bits, 
> while the GPT table specification provides 128 bytes for each block entry.  
> The extra space can be used to store information related to the intended OS 
> usage of each partition, by adding the corresponding Partition Type UUID.
>
> This has a number of benefits, described here:
>
> https://uapi-group.org/specifications/specs/
> discoverable_partitions_specification/
>
> Besides the automation this feature affords, I find it useful to know what a 
> partition contains without having to mount it.  On GPT labelled disks I make 
> use both of the Partition Type UUID and the Partition Name.  A quick glance 
> at 
> the gdisk output and if need be its 'i' option has saved my day from 
> formatting the wrong partition more than once!  ;-)


I always use labels which show up with cgdisk.  If I'm unsure how I
partitioned a drive for some reason, I just check it with cgdisk to see
what is what.  I use labels even tho a lot of the time I put UUIDs in
fstab.  I do similar when using LVM as well. 

There is more than one way to organize things tho.  ;-) 

Dale

:-)  :-) 



Re: [gentoo-user] Re: Grub, gpt partitions and BIOS, not uefi thing.

2024-05-02 Thread Michael
On Thursday, 2 May 2024 00:45:29 BST Dale wrote:
> Grant Edwards wrote:
> > On 2024-05-01, Dale  wrote:
> >> Grant Edwards wrote:
> >>> The partition type code for 'swap' is wrong -- it should be
> >>> 8200. According to the gdisk help info Linux /home is supposed to be
> >>> 8302, but I've always used the same generic "Linux filesystem" type
> >>> for both /home and root.
> >>> 
> >>> Is the 'boot' partition for future possible UEFI use, for Linux /boot,
> >>> or both?  [I've never used a separate partition for Linux /boot, I
> >>> just use a /boot directory on the root FS.]
> >> 
> >> I noticed the other day that some new ones was added.  I always leave it
> >> as 8300 and it works.  It even works for swap.  I dunno. 

In the legacy DOS partition tables the space available was limited to 32 bits, 
while the GPT table specification provides 128 bytes for each block entry.  
The extra space can be used to store information related to the intended OS 
usage of each partition, by adding the corresponding Partition Type UUID.

This has a number of benefits, described here:

https://uapi-group.org/specifications/specs/
discoverable_partitions_specification/

Besides the automation this feature affords, I find it useful to know what a 
partition contains without having to mount it.  On GPT labelled disks I make 
use both of the Partition Type UUID and the Partition Name.  A quick glance at 
the gdisk output and if need be its 'i' option has saved my day from 
formatting the wrong partition more than once!  ;-)


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] cross-compiling environment for Rapberry

2024-05-01 Thread Alexandru N. Barloiu

On 4/30/2024 12:26 AM, ralfconn wrote:
The crossdev environment on the desktop knows nothing about the packages 
installed on the Pi, so I copied /var/db/pkg from Pi to 
/usr/aarch64-unknown-linux-gnu/var/db/pkg on the desktop. I ran emerge 
--sync on the Pi and on the desktop approximatively at the same time.



this is wrong. so ima gonna assume we talking about crossdev. and 
cross-emerge. which should be the go to tool for this.


but here is the problem. you cant just "mimic" fake packages. which is 
wht you did is.


3 different systems. host system, prolly x86/64. then virtual system. 
then the actual pi. do not confuse them.


profiles are less important. dependencies are important however.

lets say you do USE="xz" ROOT="/someplace" SYSROOT=$ROOT ARCH=$whatever 
cross-emerge gcc. you would need headers and libs not just in the target 
system, but in the building systems as well. not just in the main 
building system, the host system, but based on how and what you are 
doing, you might need to build, dependencies, including in that 
intermediary /usr/$arch.






Re: [gentoo-user] Re: Grub, gpt partitions and BIOS, not uefi thing.

2024-05-01 Thread Dale
Grant Edwards wrote:
> On 2024-05-01, Dale  wrote:
>> Grant Edwards wrote:
>>
>>> The partition type code for 'swap' is wrong -- it should be
>>> 8200. According to the gdisk help info Linux /home is supposed to be
>>> 8302, but I've always used the same generic "Linux filesystem" type
>>> for both /home and root.
>>>
>>> Is the 'boot' partition for future possible UEFI use, for Linux /boot,
>>> or both?  [I've never used a separate partition for Linux /boot, I
>>> just use a /boot directory on the root FS.]
>> I noticed the other day that some new ones was added.  I always leave it
>> as 8300 and it works.  It even works for swap.  I dunno. 
> If you have an entry in /etc/fstab for swap, it might not matter if
> the partition type is set to 'Linux swap' or not. I always set the
> swap parition type to 'Linux swap', and then it doesn't seem to matter
> if there's a swap entry in the fstab or not.

I tend to put everything in fstab.  It's the way it was when I started
and I just keep doing it that way.  It could be that it isn't needed
anymore tho. 


>> The /boot is where kernels and init thingys go.  Keep in mind, this is
>> on a old rig that has no idea what UEFI is.  When I build my new rig
>> later, I'll do a install from scratch anyway.  Also, it will go on a SSD. 
> OK, so 'boot' is for the Linux /boot directory.  I was just curious
> since I had never used one. 
>

I've used one ever since I started using Linux and it's as much habit as
anything.  Given the size of drives nowadays, I have started putting
/usr and /var on the root partition.  When I build my new rig tho, odds
are /var will be on its own partition.  That way if a log file goes
wonky, it can fill it up and not really do any harm. 


>> I mostly want to post so that a person can see the layout.  Really, the
>> first one is what a person wanting to use GPT on a old BIOS system needs
>> to see.  After that, they can do partitions anyway they want.
> Right.


I'm to the good part of the install now.  With the partition layout
shown earlier, I get this. 


(chroot) livecd / # grub-install /dev/sda
Installing for i386-pc platform.
Installation finished. No error reported.
(chroot) livecd / #


When I did that before, it puked on my keyboard.  This time with that
little unformatted partition, it just installed it.  So, muddy waters
pretty clear now.  :-D 

Dale

:-)  :-) 



Re: [gentoo-user] cross-compiling environment for Rapberry

2024-05-01 Thread ralfconn

Il 01/05/24 19:54, ralfconn ha scritto:

Il 01/05/24 19:05, Michael ha scritto:

I've built the cross toolchain with 'crossdev --taget

aarch64-unknown-linux-gnu' per wiki [2]. I've selected a 23.0-split-usr
profile on the Pi since this is the one supported by the crossdev 
(or so

I understood from the error message when I tried with the non-split-usr
profile on the desktop).
Did you download the correct stage3?  There are split-usr and 
merged-usr tar
archives.  Since split-usr is or will be soon deprecated you better 
start with

merged-usr.
I wasn't clear: when I tried to select the merged-usr profile on the 
host and on the target I got an error invoking 
emerge-aarch64-unknown-linux-gnu on the _host_  telling me that the 
profile was 'merged-usr' but the directory layout wasn't. So the 
problem is in the directory layout created by crossdev on the host.The 
host has a merged-usr profile, I believe the problem is in crossdev 
itself. I tried to manually copy files in the crossdev environment to 
recreate the merged-usr layout but then the error on the host was even 
worse (I forgot what it was) so I went back to split.


Update: stage3 on the pi is merge-usr so the above is bound to fail 
sooner or later (as I discovered trying to emerge 
app-misc/resolve-march-native on the pi). But, the sys-apps/merge-usr 
script accepts a --root parameter, so it is possible to issue, on the host:


# merge-usr --root /usr/aarch64-unknown-linux-gnu

# PORTAGE_CONFIGROOT=/usr/aarch64-unknown-linux-gnu eselect profile set 
default/linux/arm64/23.0


and have on the host the same directory layout and profile of the ARM 
stage3 installed on the pi.


raffaele





[gentoo-user] Re: Grub, gpt partitions and BIOS, not uefi thing.

2024-05-01 Thread Grant Edwards
On 2024-05-01, Dale  wrote:
> Grant Edwards wrote:
>
>> The partition type code for 'swap' is wrong -- it should be
>> 8200. According to the gdisk help info Linux /home is supposed to be
>> 8302, but I've always used the same generic "Linux filesystem" type
>> for both /home and root.
>>
>> Is the 'boot' partition for future possible UEFI use, for Linux /boot,
>> or both?  [I've never used a separate partition for Linux /boot, I
>> just use a /boot directory on the root FS.]
>
> I noticed the other day that some new ones was added.  I always leave it
> as 8300 and it works.  It even works for swap.  I dunno. 

If you have an entry in /etc/fstab for swap, it might not matter if
the partition type is set to 'Linux swap' or not. I always set the
swap parition type to 'Linux swap', and then it doesn't seem to matter
if there's a swap entry in the fstab or not.

> The /boot is where kernels and init thingys go.  Keep in mind, this is
> on a old rig that has no idea what UEFI is.  When I build my new rig
> later, I'll do a install from scratch anyway.  Also, it will go on a SSD. 

OK, so 'boot' is for the Linux /boot directory.  I was just curious
since I had never used one. 

> I mostly want to post so that a person can see the layout.  Really, the
> first one is what a person wanting to use GPT on a old BIOS system needs
> to see.  After that, they can do partitions anyway they want.

Right.





Re: [gentoo-user] Re: Grub, gpt partitions and BIOS, not uefi thing.

2024-05-01 Thread Dale
Grant Edwards wrote:
> On 2024-05-01, Dale  wrote:
>
>> OK.  One last update in case someone googles and runs up on this
>> thread.  I'm using gdisk to display this, because I think it will do
>> better in email.  If I use cgdisk, it is wider and will wrap more. 
>> This is what the partition table looks like for GPT, old BIOS and no
>> uefi thingy.  Just a straight forward and simple old school setup. 
>> Once the first one is done, the rest can be anything.
>>
>>
>> Number  Start (sector)    End (sector)  Size   Code Name
>>    1    2048 10239  4.0 MiB EF02  BIOS-boot
>>    2   10240    4204543  2.0 GiB 8300  boot
>>    3 4204544  12593151    4.0 GiB 8300  swap
>>    4    12593152    327165951   150.0 GiB   8300  root
>>    5   327165952   625141759   142.1 GiB   8300  home
> The partition type code for 'swap' is wrong -- it should be
> 8200. According to the gdisk help info Linux /home is supposed to be
> 8302, but I've always used the same generic "Linux filesystem" type
> for both /home and root.
>
> Is the 'boot' partition for future possible UEFI use, for Linux /boot,
> or both?  [I've never used a separate partition for Linux /boot, I
> just use a /boot directory on the root FS.]
>
> --
> Grant

I noticed the other day that some new ones was added.  I always leave it
as 8300 and it works.  It even works for swap.  I dunno. 

The /boot is where kernels and init thingys go.  Keep in mind, this is
on a old rig that has no idea what UEFI is.  When I build my new rig
later, I'll do a install from scratch anyway.  Also, it will go on a SSD. 

I mostly want to post so that a person can see the layout.  Really, the
first one is what a person wanting to use GPT on a old BIOS system needs
to see.  After that, they can do partitions anyway they want.  I just
hope I got it right.  Right now, I'm to the stage where I do a emerge
-auDN world.  On that old rig, may take a little bit.  It's not bad
tho.  Old rig has 6 cores now. 

Dale

:-)  :-) 



[gentoo-user] Re: Grub, gpt partitions and BIOS, not uefi thing.

2024-05-01 Thread Grant Edwards
On 2024-05-01, Dale  wrote:

> OK.  One last update in case someone googles and runs up on this
> thread.  I'm using gdisk to display this, because I think it will do
> better in email.  If I use cgdisk, it is wider and will wrap more. 
> This is what the partition table looks like for GPT, old BIOS and no
> uefi thingy.  Just a straight forward and simple old school setup. 
> Once the first one is done, the rest can be anything.
>
>
> Number  Start (sector)    End (sector)  Size   Code Name
>    1    2048 10239  4.0 MiB EF02  BIOS-boot
>    2   10240    4204543  2.0 GiB 8300  boot
>    3 4204544  12593151    4.0 GiB 8300  swap
>    4    12593152    327165951   150.0 GiB   8300  root
>    5   327165952   625141759   142.1 GiB   8300  home

The partition type code for 'swap' is wrong -- it should be
8200. According to the gdisk help info Linux /home is supposed to be
8302, but I've always used the same generic "Linux filesystem" type
for both /home and root.

Is the 'boot' partition for future possible UEFI use, for Linux /boot,
or both?  [I've never used a separate partition for Linux /boot, I
just use a /boot directory on the root FS.]

--
Grant




Re: [gentoo-user] Re: Grub, gpt partitions and BIOS, not uefi thing.

2024-05-01 Thread Dale
Dale wrote:
> One last update.  I found a video.  They were using gdisk but the
> crucial part, he got it to display the partition layout.  It was like I
> described as for as the alignment thing, tiny partition with ef02 and
> then carry on as usual from there. 
>
> I need to do this on a disk complete with notes, so I don't forget.  My
> brain is going fast.  One day, I'll forget how to turn the puter on. 
> :'(  I already forget what I went to the kitchen for, it's only 20 feet
> away.  :/
>
> Thanks again. 
>
> Dale
>
> :-)  :-)
>


OK.  One last update in case someone googles and runs up on this
thread.  I'm using gdisk to display this, because I think it will do
better in email.  If I use cgdisk, it is wider and will wrap more.  This
is what the partition table looks like for GPT, old BIOS and no uefi
thingy.  Just a straight forward and simple old school setup.  Once the
first one is done, the rest can be anything.


Number  Start (sector)    End (sector)  Size   Code Name
   1    2048 10239  4.0 MiB EF02  BIOS-boot
   2   10240    4204543  2.0 GiB 8300  boot
   3 4204544  12593151    4.0 GiB 8300  swap
   4    12593152    327165951   150.0 GiB   8300  root
   5   327165952   625141759   142.1 GiB   8300  home


I'm about to start a fresh install on this so if it isn't right, let me
know soon.  I did make it a little larger than everyone says it needs to
be since grub does seem to grow.  That should be bigger than I'll ever
need in the lifetime of this old rig anyway. 

Dale

:-)  :-) 



Re: [gentoo-user] cross-compiling environment for Rapberry

2024-05-01 Thread ralfconn

Il 01/05/24 19:05, Michael ha scritto:

I've built the cross toolchain with 'crossdev --taget

aarch64-unknown-linux-gnu' per wiki [2]. I've selected a 23.0-split-usr
profile on the Pi since this is the one supported by the crossdev (or so
I understood from the error message when I tried with the non-split-usr
profile on the desktop).

Did you download the correct stage3?  There are split-usr and merged-usr tar
archives.  Since split-usr is or will be soon deprecated you better start with
merged-usr.
I wasn't clear: when I tried to select the merged-usr profile on the 
host and on the target I got an error invoking 
emerge-aarch64-unknown-linux-gnu on the _host_  telling me that the 
profile was 'merged-usr' but the directory layout wasn't. So the problem 
is in the directory layout created by crossdev on the host.The host has 
a merged-usr profile, I believe the problem is in crossdev itself. I 
tried to manually copy files in the crossdev environment to recreate the 
merged-usr layout but then the error on the host was even worse (I 
forgot what it was) so I went back to split.

The crossdev environment on the desktop knows nothing about the packages
installed on the Pi, so I copied /var/db/pkg from Pi to
/usr/aarch64-unknown-linux-gnu/var/db/pkg on the desktop. I ran emerge
--sync on the Pi and on the desktop approximatively at the same time.

 Now If I try a @system update on the Pi I get: 

pihole ~ # emerge -uDvN --ask @system

Why didn't you try '--usepkg y', or '--usepkgonly y' to emerge the precompiled
binaries on the pi?
That is the intention, after I'll manage to set up a workflow to 
crossbuild binary packages on the host :-)

 What am I missing to make the desktop use the same list of packages
to be upgraded as the Pi? 

thanks,

raffaele

[1] https://pi-hole.net/
[2] https://wiki.gentoo.org/wiki/Crossdev

Check the selected make.profile and the stage3 fs are the same on both
buildhost and guest.  Also diff the two /var/lib/portage/world and don't
forget to compare/grep for different USE flags between the two systems.
/etc/portage/make.conf on the pi and in 
/usr/aarch64-unknown-linux-gnu/etc/portage/make.conf on the host are 
almost identical except for host-only feature (e.g. buildpkg is only 
specified on the host side) and number of emerge jobs.

Finally, if nothing works as intended consider compiling in QEMU:

https://wiki.gentoo.org/wiki/Embedded_Handbook/General/
Compiling_with_QEMU_user_chroot


For the moment I am trying a different approach: create a list of 
packages to be updated on the pi and use it as input to 
the emerge-aarch64-unknown-linux-gnu command on the host.


Wow, even an emerge --sync takes forever on the pi, I was no longer used 
to such long delays!


raffaele




Re: [gentoo-user] cross-compiling environment for Rapberry

2024-05-01 Thread Michael
On Monday, 29 April 2024 22:26:49 BST ralfconn wrote:
> Hello,
> 
> I recently got me a Raspberry Pi4b to use as a PiHole [1]. As a first
> step I put user-space Gentoo (i.e. aarch64 stage3) on it and now I am
> trying to set up my desktop to cross-compile binary packages for the PI,
> to keep the Pi up-to-date in reasonable computing time.

TBH I've had limited success with cross-compiling and this was for an x86 
guest on amd64 buildhost, but I have not tried aarch64 (yet).


> I've built the cross toolchain with 'crossdev --taget
> aarch64-unknown-linux-gnu' per wiki [2]. I've selected a 23.0-split-usr
> profile on the Pi since this is the one supported by the crossdev (or so
> I understood from the error message when I tried with the non-split-usr
> profile on the desktop).

Did you download the correct stage3?  There are split-usr and merged-usr tar 
archives.  Since split-usr is or will be soon deprecated you better start with 
merged-usr.


> The crossdev environment on the desktop knows nothing about the packages
> installed on the Pi, so I copied /var/db/pkg from Pi to
> /usr/aarch64-unknown-linux-gnu/var/db/pkg on the desktop. I ran emerge
> --sync on the Pi and on the desktop approximatively at the same time.
> 
>  Now If I try a @system update on the Pi I get: 
> 
> pihole ~ # emerge -uDvN --ask @system

Why didn't you try '--usepkg y', or '--usepkgonly y' to emerge the precompiled 
binaries on the pi?


> These are the packages that would be merged, in order:
> 
> Calculating dependencies... done!
> Dependency resolution took 31.91 s (backtrack: 0/20).
> 
> [ebuild U  ] sys-libs/ncurses-6.4_p20240414:0/6::gentoo
> [6.4_p20230401:0/6::gentoo] USE="cxx (split-usr*) (tinfo) -ada -debug
> -doc -gpm -minimal -profile (-stack-realign) -static-libs -test -trace
> -verify-sig" 7647 KiB
> [ebuild U  ] sys-apps/baselayout-2.15::gentoo [2.14-r2::gentoo]
> USE="(split-usr*) -build" 30 KiB
> [ebuild U  ] dev-util/re2c-3.1::gentoo [2.2::gentoo] USE="-debug
> -test" 1415 KiB
> [ebuild U  ] dev-util/pkgconf-2.2.0:0/5::gentoo [2.1.1:0/4::gentoo]
> USE="(native-symlinks) -test" 305 KiB
> [ebuild U  ] app-portage/elt-patches-20240415::gentoo
> [20240315::gentoo] 46 KiB
> [ebuild   R] app-alternatives/awk-4::gentoo  USE="gawk (split-usr*)
> -busybox -mawk -nawk" 0 KiB
> [ebuild   R] app-alternatives/bzip2-1::gentoo USE="reference
> (split-usr*) -lbzip2 -pbzip2" 0 KiB
> [ebuild   R] app-alternatives/tar-0::gentoo  USE="gnu (split-usr*)
> -libarchive" 0 KiB
> [ebuild   R] app-alternatives/gzip-1::gentoo  USE="reference
> (split-usr*) -pigz" 0 KiB
> [ebuild U  ] dev-libs/libxml2-2.12.6:2::gentoo [2.12.5:2::gentoo]
> USE="ftp python readline -debug -examples -icu -lzma -static-libs -test"
> PYTHON_TARGETS="python3_11 -python3_10 -python3_12" 2582 KiB
> [ebuild U  ] sys-devel/gettext-0.22.5::gentoo [0.22.4::gentoo]
> USE="acl cxx ncurses nls openmp* (xattr) -doc -emacs -git -java
> -static-libs -verify-sig" 10031 KiB
> [ebuild  N ] app-arch/libarchive-3.7.4:0/13::gentoo USE="acl bzip2
> e2fsprogs iconv lzma xattr zstd -blake2 -expat -lz4 -lzo -nettle
> -static-libs -test -verify-sig" 5291 KiB
> [ebuild U  ] sys-apps/shadow-4.14.6:0/4::gentoo [4.14.2:0/4::gentoo]
> USE="acl nls pam (split-usr*) xattr -audit -cracklib (-selinux) -skey
> -su -systemd -verify-sig" 1764 KiB
> [ebuild  N ] app-crypt/rhash-1.4.4-r1:0/1::gentoo  USE="nls ssl
> -debug -static-libs" 426 KiB
> [ebuild U  ] dev-python/platformdirs-4.2.1::gentoo [4.2.0::gentoo]
> USE="-test" PYTHON_TARGETS="python3_11 -pypy3 -python3_10 -python3_12"
> 20 KiB
> [ebuild  N ] dev-python/backports-tarfile-1.1.1::gentoo USE="-test"
> PYTHON_TARGETS="python3_11 -pypy3 -python3_10" 83 KiB
> [ebuild U  ] dev-python/trove-classifiers-2024.4.10::gentoo
> [2024.3.25::gentoo] USE="-test" PYTHON_TARGETS="python3_11 -pypy3
> -python3_10 -python3_12" 16 KiB
> [ebuild U  ] dev-python/jaraco-context-5.3.0::gentoo [5.1.0::gentoo]
> USE="-test" PYTHON_TARGETS="python3_11 -pypy3 -python3_10 -python3_12"
> 14 KiB
> [ebuild U  ] dev-python/jaraco-functools-4.0.1::gentoo
> [4.0.0::gentoo] USE="-test" PYTHON_TARGETS="python3_11 -pypy3
> -python3_10 -python3_12" 18 KiB
> [ebuild U  ] sys-apps/coreutils-9.5::gentoo [9.4-r1::gentoo]
> USE="acl nls openssl (split-usr*) xattr -caps -gmp -hostname -kill
> -multicall (-selinux) -static -test -vanilla -verify-sig" 5873 KiB
> [ebuild  NS] dev-build/autoconf-2.72-r1:2.72::gentoo
> [2.71-r6:2.71::gentoo] USE="-emacs -verify-sig%" 1358 KiB
> [ebuild U  ] app-eselect/eselect-pinentry-0.7.4::gentoo
> [0.7.3::gentoo] 0 KiB
> [ebuild U  ] dev-perl/XS-Parse-Keyword-0.410.0::gentoo
> [0.380.0::gentoo] USE="-test" 87 KiB
> [ebuild U  ] sys-apps/kmod-32-r1::gentoo [31::gentoo] USE="lzma
> (split-usr%*) (tools) zlib zstd -debug -doc -pkcs7 -static-libs
> (-python%)" PYTHON_TARGETS="(-python3_10%) (-python3_11%*)" 500 KiB
> [ebuild U  ] 

Re: [gentoo-user] cross-compiling environment for Rapberry

2024-05-01 Thread Frank Steinmetzger
Am Mon, Apr 29, 2024 at 11:26:49PM +0200 schrieb ralfconn:
> Hello,
> 
> I recently got me a Raspberry Pi4b to use as a PiHole [1]. As a first step I
> put user-space Gentoo (i.e. aarch64 stage3) on it and now I am trying to set
> up my desktop to cross-compile binary packages for the PI, to keep the Pi
> up-to-date in reasonable computing time.
> [...]
> /usr/aarch64-unknown-linux-gnu/var/db/pkg on the desktop. I ran emerge
> --sync on the Pi and on the desktop approximatively at the same time.

You could simply rsync the portage tree from one host to the other to get an 
identical state on both.

> [different emerge -u on both hosts]
>
>  What am I missing to make the desktop use the same list of packages to
> be upgraded as the Pi? 

Do you have the same use flags? I’ve never really dealt with crosscompiling. 
Maybe somewhere deep in the system the use flags are changed. Try comparing 
the output of emerge --info from both hosts.

-- 
Grüße | Greetings | Salut | Qapla’
Please do not share anything from, with or about me on any social network.

Development aid is to give money from the poor of rich countries
to the rich of poor countries.


signature.asc
Description: PGP signature


Re: [gentoo-user] dhcp error. No network. Address family not supported.

2024-04-30 Thread Sergey Filatov

On 30.04.2024 0:35, Michael wrote:

On Monday, 29 April 2024 21:28:35 BST Dale wrote:

Peter Humphrey wrote:

On Monday, 29 April 2024 16:11:31 BST Dale wrote:

Only bad side of IPv6, it's a lot of typing for all that.  o_O


There's a worse aspect: you have to undersand what you're doing. Or you
can
just tell your firewall not to allow any IPv6 packets in or out at all.


When I said a lot of typing, I was thinking about if one has to use IPv6
to ssh into a rig.  As it is here, ssh dale@10.0.0.6 is it.  Now replace
that IP with a IPv6 address.  I'm hoping for a copy and paste option or
tab completion would be nice.  Let's not even get into the increased
odds of a typo.  After all, one wrong character, no worky.  :/

Given that we running out of IPv4 tho, IPv6 it is.  Something had to
change.  I guess IPv6 was the best long term option.  Still, gonna be a
head scratcher for some of us.

Dale

:-)  :-)


If we're talking about connecting regularly to the same IP you can set it up
as an alias in your ~/.ssh/config and not have to invoke IP addresses on the
CLI at all.


In my case, given that it's publicly routable anyway I just set the  
records on my DNS server for my IPv6 enabled servers.




[gentoo-user] cross-compiling environment for Rapberry

2024-04-29 Thread ralfconn

Hello,

I recently got me a Raspberry Pi4b to use as a PiHole [1]. As a first 
step I put user-space Gentoo (i.e. aarch64 stage3) on it and now I am 
trying to set up my desktop to cross-compile binary packages for the PI, 
to keep the Pi up-to-date in reasonable computing time.


I've built the cross toolchain with 'crossdev --taget 
aarch64-unknown-linux-gnu' per wiki [2]. I've selected a 23.0-split-usr 
profile on the Pi since this is the one supported by the crossdev (or so 
I understood from the error message when I tried with the non-split-usr 
profile on the desktop).


The crossdev environment on the desktop knows nothing about the packages 
installed on the Pi, so I copied /var/db/pkg from Pi to 
/usr/aarch64-unknown-linux-gnu/var/db/pkg on the desktop. I ran emerge 
--sync on the Pi and on the desktop approximatively at the same time.


 Now If I try a @system update on the Pi I get: 

pihole ~ # emerge -uDvN --ask @system

These are the packages that would be merged, in order:

Calculating dependencies... done!
Dependency resolution took 31.91 s (backtrack: 0/20).

[ebuild U  ] sys-libs/ncurses-6.4_p20240414:0/6::gentoo 
[6.4_p20230401:0/6::gentoo] USE="cxx (split-usr*) (tinfo) -ada -debug 
-doc -gpm -minimal -profile (-stack-realign) -static-libs -test -trace 
-verify-sig" 7647 KiB
[ebuild U  ] sys-apps/baselayout-2.15::gentoo [2.14-r2::gentoo] 
USE="(split-usr*) -build" 30 KiB
[ebuild U  ] dev-util/re2c-3.1::gentoo [2.2::gentoo] USE="-debug 
-test" 1415 KiB
[ebuild U  ] dev-util/pkgconf-2.2.0:0/5::gentoo [2.1.1:0/4::gentoo] 
USE="(native-symlinks) -test" 305 KiB
[ebuild U  ] app-portage/elt-patches-20240415::gentoo 
[20240315::gentoo] 46 KiB
[ebuild   R    ] app-alternatives/awk-4::gentoo  USE="gawk (split-usr*) 
-busybox -mawk -nawk" 0 KiB
[ebuild   R    ] app-alternatives/bzip2-1::gentoo USE="reference 
(split-usr*) -lbzip2 -pbzip2" 0 KiB
[ebuild   R    ] app-alternatives/tar-0::gentoo  USE="gnu (split-usr*) 
-libarchive" 0 KiB
[ebuild   R    ] app-alternatives/gzip-1::gentoo  USE="reference 
(split-usr*) -pigz" 0 KiB
[ebuild U  ] dev-libs/libxml2-2.12.6:2::gentoo [2.12.5:2::gentoo] 
USE="ftp python readline -debug -examples -icu -lzma -static-libs -test" 
PYTHON_TARGETS="python3_11 -python3_10 -python3_12" 2582 KiB
[ebuild U  ] sys-devel/gettext-0.22.5::gentoo [0.22.4::gentoo] 
USE="acl cxx ncurses nls openmp* (xattr) -doc -emacs -git -java 
-static-libs -verify-sig" 10031 KiB
[ebuild  N ] app-arch/libarchive-3.7.4:0/13::gentoo USE="acl bzip2 
e2fsprogs iconv lzma xattr zstd -blake2 -expat -lz4 -lzo -nettle 
-static-libs -test -verify-sig" 5291 KiB
[ebuild U  ] sys-apps/shadow-4.14.6:0/4::gentoo [4.14.2:0/4::gentoo] 
USE="acl nls pam (split-usr*) xattr -audit -cracklib (-selinux) -skey 
-su -systemd -verify-sig" 1764 KiB
[ebuild  N ] app-crypt/rhash-1.4.4-r1:0/1::gentoo  USE="nls ssl 
-debug -static-libs" 426 KiB
[ebuild U  ] dev-python/platformdirs-4.2.1::gentoo [4.2.0::gentoo] 
USE="-test" PYTHON_TARGETS="python3_11 -pypy3 -python3_10 -python3_12" 
20 KiB
[ebuild  N ] dev-python/backports-tarfile-1.1.1::gentoo USE="-test" 
PYTHON_TARGETS="python3_11 -pypy3 -python3_10" 83 KiB
[ebuild U  ] dev-python/trove-classifiers-2024.4.10::gentoo 
[2024.3.25::gentoo] USE="-test" PYTHON_TARGETS="python3_11 -pypy3 
-python3_10 -python3_12" 16 KiB
[ebuild U  ] dev-python/jaraco-context-5.3.0::gentoo [5.1.0::gentoo] 
USE="-test" PYTHON_TARGETS="python3_11 -pypy3 -python3_10 -python3_12" 
14 KiB
[ebuild U  ] dev-python/jaraco-functools-4.0.1::gentoo 
[4.0.0::gentoo] USE="-test" PYTHON_TARGETS="python3_11 -pypy3 
-python3_10 -python3_12" 18 KiB
[ebuild U  ] sys-apps/coreutils-9.5::gentoo [9.4-r1::gentoo] 
USE="acl nls openssl (split-usr*) xattr -caps -gmp -hostname -kill 
-multicall (-selinux) -static -test -vanilla -verify-sig" 5873 KiB
[ebuild  NS    ] dev-build/autoconf-2.72-r1:2.72::gentoo 
[2.71-r6:2.71::gentoo] USE="-emacs -verify-sig%" 1358 KiB
[ebuild U  ] app-eselect/eselect-pinentry-0.7.4::gentoo 
[0.7.3::gentoo] 0 KiB
[ebuild U  ] dev-perl/XS-Parse-Keyword-0.410.0::gentoo 
[0.380.0::gentoo] USE="-test" 87 KiB
[ebuild U  ] sys-apps/kmod-32-r1::gentoo [31::gentoo] USE="lzma 
(split-usr%*) (tools) zlib zstd -debug -doc -pkcs7 -static-libs 
(-python%)" PYTHON_TARGETS="(-python3_10%) (-python3_11%*)" 500 KiB
[ebuild U  ] app-crypt/pinentry-1.3.0-r2::gentoo [1.2.1-r4::gentoo] 
USE="ncurses -X -caps -efl -emacs -gtk -keyring -qt5 (-qt6) -verify-sig 
-wayland" 597 KiB
[ebuild U  ] dev-lang/tcl-8.6.14:0/8.6::gentoo 
[8.6.13-r1:0/8.6::gentoo] USE="threads -debug" 6916 KiB
[ebuild  N ] dev-libs/libuv-1.48.0:0/1::gentoo USE="-verify-sig" 
1285 KiB
[ebuild U  ] dev-perl/Syntax-Keyword-Try-0.290.0::gentoo 
[0.280.0::gentoo] USE="-test" 45 KiB
[ebuild U  ] app-text/po4a-0.71::gentoo [0.69::gentoo] USE="-test" 
4747 KiB
[ebuild U  ] app-portage/portage-utils-0.97::gentoo [0.96.1::gentoo] 
USE="openmp* 

Re: [gentoo-user] dhcp error. No network. Address family not supported.

2024-04-29 Thread Dale
Michael wrote:
> On Monday, 29 April 2024 21:28:35 BST Dale wrote:
>> Peter Humphrey wrote:
>>> On Monday, 29 April 2024 16:11:31 BST Dale wrote:
 Only bad side of IPv6, it's a lot of typing for all that.  o_O
>>> There's a worse aspect: you have to undersand what you're doing. Or you
>>> can
>>> just tell your firewall not to allow any IPv6 packets in or out at all.
>> When I said a lot of typing, I was thinking about if one has to use IPv6
>> to ssh into a rig.  As it is here, ssh dale@10.0.0.6 is it.  Now replace
>> that IP with a IPv6 address.  I'm hoping for a copy and paste option or
>> tab completion would be nice.  Let's not even get into the increased
>> odds of a typo.  After all, one wrong character, no worky.  :/ 
>>
>> Given that we running out of IPv4 tho, IPv6 it is.  Something had to
>> change.  I guess IPv6 was the best long term option.  Still, gonna be a
>> head scratcher for some of us. 
>>
>> Dale
>>
>> :-)  :-) 
> If we're talking about connecting regularly to the same IP you can set it up 
> as an alias in your ~/.ssh/config and not have to invoke IP addresses on the 
> CLI at all.


I'd likely just add it to the host file thing and then type in the
name.  Right now it is NAS or NAS2.  Pretty short. 

While I'm sure whoever came up with IPv6 tried to keep it simple, I
suspect they also wanted to make the newer method work long term.  Quite
often, long term solutions get complicated.  If that is the case, it
explains a lot.  10.0.0.6 is way simple.  fe80::1eef:2ca0:c378:2eec is
anything but simple.  Now try being a admin and having to remember a few
dozen of those.  ROFL  Poor thang.  It's a good thing there are options
like your alias one or the hosts file one.  We'd have a lot of bald
people running around.  Admins and some other geeky types would be
pulling out their hair.  :/ 

Dale

:-)  :-) 

P. S.  the perl cleaner thing fixed the whole problem.  Everything is as
it should be, I think. 


Re: [gentoo-user] dhcp error. No network. Address family not supported.

2024-04-29 Thread Michael
On Monday, 29 April 2024 21:28:35 BST Dale wrote:
> Peter Humphrey wrote:
> > On Monday, 29 April 2024 16:11:31 BST Dale wrote:
> >> Only bad side of IPv6, it's a lot of typing for all that.  o_O
> > 
> > There's a worse aspect: you have to undersand what you're doing. Or you
> > can
> > just tell your firewall not to allow any IPv6 packets in or out at all.
> 
> When I said a lot of typing, I was thinking about if one has to use IPv6
> to ssh into a rig.  As it is here, ssh dale@10.0.0.6 is it.  Now replace
> that IP with a IPv6 address.  I'm hoping for a copy and paste option or
> tab completion would be nice.  Let's not even get into the increased
> odds of a typo.  After all, one wrong character, no worky.  :/ 
> 
> Given that we running out of IPv4 tho, IPv6 it is.  Something had to
> change.  I guess IPv6 was the best long term option.  Still, gonna be a
> head scratcher for some of us. 
> 
> Dale
> 
> :-)  :-) 

If we're talking about connecting regularly to the same IP you can set it up 
as an alias in your ~/.ssh/config and not have to invoke IP addresses on the 
CLI at all.

signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] dhcp error. No network. Address family not supported.

2024-04-29 Thread Dale
Peter Humphrey wrote:
> On Monday, 29 April 2024 16:11:31 BST Dale wrote:
>
>> Only bad side of IPv6, it's a lot of typing for all that.  o_O
> There's a worse aspect: you have to undersand what you're doing. Or you can 
> just tell your firewall not to allow any IPv6 packets in or out at all.
>


When I said a lot of typing, I was thinking about if one has to use IPv6
to ssh into a rig.  As it is here, ssh dale@10.0.0.6 is it.  Now replace
that IP with a IPv6 address.  I'm hoping for a copy and paste option or
tab completion would be nice.  Let's not even get into the increased
odds of a typo.  After all, one wrong character, no worky.  :/ 

Given that we running out of IPv4 tho, IPv6 it is.  Something had to
change.  I guess IPv6 was the best long term option.  Still, gonna be a
head scratcher for some of us. 

Dale

:-)  :-) 



Re: [gentoo-user] dhcp error. No network. Address family not supported.

2024-04-29 Thread Peter Humphrey
On Monday, 29 April 2024 16:11:31 BST Dale wrote:

> Only bad side of IPv6, it's a lot of typing for all that.  o_O

There's a worse aspect: you have to undersand what you're doing. Or you can 
just tell your firewall not to allow any IPv6 packets in or out at all.

-- 
Regards,
Peter.






Re: [gentoo-user] dhcp error. No network. Address family not supported.

2024-04-29 Thread Dale
Michael wrote:
> On Sunday, 28 April 2024 03:29:09 BST Dale wrote:
>> Michael wrote:
>>> On Saturday, 27 April 2024 23:30:46 BST Dale wrote:
> [snip ...]
>
 Anyone ever seen this?  Searching didn't help.  This is a new kernel so
 maybe I missed something in there?
>>> Yes, most likely.
>>>
>>> What does this show:
>>>
>>> grep SOCKET /usr/src/linux/.config
>>>
>>> or this:
>>>
>>> grep PACKET /usr/src/linux/.config
>> OK.  Some of those were turned off.  I cut on anything that looked like
>> something I'd need.  Recompiled the kernel and rebooted.  What do you
>> know, it worked. 
> Cool :-)
>
>
>> Now some questions, why is something that most anyone would need turned
>> off by default?  Why is it not mentioned along with other things in the
>> install docs?  I went through the install docs for those options needed,
>> I don't recall seeing those.
> I don't know what the devs' thinking on this has been, but it could be such 
> options are not enabled by default because the network configuration can 
> affect security.  For a binary desktop distro, more generic options would be 
> preconfigured, as I expect is the case with genkernel.
>
>
>> The only things I left out were the UEFI
>> thingy stuff.  I so dread that UEFI thingy on the new build.  o_O
> I think UEFI is rather simpler to set up, no "BIOS Boot Partition" required.  
> Just create a partition with type ef00 (GUID type C12A7328-F81F-11D2-
> BA4B-00A0C93EC93B - EFI system partition) and format it as FAT32, before you 
> mount it as /efi.
>
> The handbook details how to set up a UEFI system with ESP, so spend some time 
> reading through the docs before you jump in and consider options and 
> permutations if you will be using openrc or systemd.
>

I saw the instructions when doing the old Dell install.  My dread is,
I've never done one before.  One good thing tho, it's been around a good
while now.  All the bugs and kinks in the install docs have been worked
out by now.  Follow the docs and it should work. 


>> Thanks to all.  It running, apparently with IPv6 at that.  O_O 
> Consider your firewall settings to include IPv6, if IPv6 is enabled.
>

When I was on DSL, no IPv6 at all.  New fiber has it tho.  Of course, it
is all new down to the cables.  Kinda be stupid not to include something
that will be a necessity before to long anyway.  Almost feel sorry for
the DSL folks.  I tried to tell them competition was going to come and
clean their clock.  They lost almost all their customers to fiber within
two months.  Cheaper and around 20 times faster.  I might add, down time
for maintenance is announced in advance.  Even that is rare.  The DSL
folks, it just went down.  No warning or anything.  Only bad side of
IPv6, it's a lot of typing for all that.  o_O

Dale

:-)  :-) 



Re: [gentoo-user] frei0r-plugins opencv ffmpeg Error: circular dependencies

2024-04-29 Thread Dale
Michael wrote:
> On Monday, 29 April 2024 06:07:04 BST Dale wrote:
>> Dale wrote:
>>> Howdy,
>>>
>>> I'm installing Gentoo on that old Dell Inspiron still.  I'm getting
>>> close.  I'm now at this. 
>>>
>>>
>>>  * Error: circular dependencies:
>>>
>>> (media-plugins/frei0r-plugins-1.8.0:0/0::gentoo, ebuild scheduled for
>>> merge) depends on
>>>  (media-libs/opencv-4.9.0:0/4.9.0::gentoo, ebuild scheduled for merge)
>>> (buildtime_slot_op)
>>>   (media-video/ffmpeg-6.1.1-r5:0/58.60.60::gentoo, ebuild scheduled for
>>> merge) (buildtime_slot_op)
>>>(media-plugins/frei0r-plugins-1.8.0:0/0::gentoo, ebuild scheduled for
>>> merge) (buildtime)
>>>
>>> It might be possible to break this cycle
>>> by applying any of the following changes:
>>> - media-video/ffmpeg-6.1.1-r5 (Change USE: -frei0r)
>>> - media-plugins/frei0r-plugins-1.8.0 (Change USE: -facedetect)
>>> - media-libs/opencv-4.9.0 (Change USE: -ffmpeg)
>>>
>>> Note that this change can be reverted, once the package has been
>>> installed.
>>> NAS2 ~ #
>>>
>>>
>>> Earlier, I added those USE flags so that it could continue on with the
>>> install.  I figured it was like that harfbuzz and something else thing. 
>>> Now that everything else is done, I want to go back to the default USE
>>> flags, like it said I could.  Thing is, when I remove the ones it wants
>>> above, it still complains.  It either fails to build or spits out
>>> something like above. 
>>>
>>> Has anyone doing a recent new install ran into this and know how to get
>>> around it?  I've tried different options but they either fail or tell me
>>> to change back to the settings it suggests above.  I searched the forums
>>> but didn't find anything.  Google didn't find anything either.  I may
>>> have found something new.  ROFL
>>>
>>> Thoughts??
>>>
>>> Dale
>>>
>>> :-)  :-)
>> Found a solution for most of it.  When I did my install, I added a line
>> for CFLAGS but failed to comment out the other line.  It seems to have
>> confused either emerge or that package or maybe both.  Basically, it
>> left it empty, no setting at all. 
>>
>> Now I'm left with a failure for net-dns/avahi which gives me this: 
>>
>>
>> sed -e 's,@pkgsysconfdir\@,/etc/avahi,g' \
>> -e 's,@servicedir\@,/etc/avahi/services,g' \
>> -e 's,@PACKAGE_BUGREPORT\@,avahi (at) lists (dot) freedesktop
>> (dot) org,g' \
>> -e 's,@PACKAGE_URL\@,http://avahi.org/,g'
>> avahi-discover.1.xml.in > avahi-discover.1.xml
>> sed -e 's,@pkgsysconfdir\@,/etc/avahi,g' \
>> -e 's,@servicedir\@,/etc/avahi/services,g' \
>> -e 's,@PACKAGE_BUGREPORT\@,avahi (at) lists (dot) freedesktop
>> (dot) org,g' \
>> -e 's,@PACKAGE_URL\@,http://avahi.org/,g'
>> avahi-bookmarks.1.xml.in > avahi-bookmarks.1.xml
>> sed -e 's,@pkgsysconfdir\@,/etc/avahi,g' \
>> -e 's,@servicedir\@,/etc/avahi/services,g' \
>> -e 's,@PACKAGE_BUGREPORT\@,avahi (at) lists (dot) freedesktop
>> (dot) org,g' \
>> -e 's,@PACKAGE_URL\@,http://avahi.org/,g' bssh.1.xml.in > bssh.1.xml
>> xmltoman avahi-daemon.8.xml > avahi-daemon.8
>> Can't locate XML/Parser.pm in @INC (you may need to install the
>> XML::Parser module) (@INC entries checked: /etc/perl
> This message above looks suspicious:
>
> "Can't locate XML/Parser.pm in @INC (you may need to install the
> XML::Parser module) (@INC entries checked: /etc/perl"
>
> In the first instance I'd throw 'perl-cleaner --reallyall' at it and see if 
> the situation improves.


I wasn't sure if the two were related but it seems they are.  I was also
running into a error with genlop.  I'm pretty sure genlop uses perl.  It
would spit this out each time I tried to use it. 



NAS2 ~ # genlop -c
Can't locate Clone.pm in @INC (you may need to install the Clone module)
(@INC entries checked: /etc/perl
/usr/local/lib64/perl5/5.38/x86_64-linux-thread-multi
/usr/local/lib64/perl5/5.38
/usr/lib64/perl5/vendor_perl/5.38/x86_64-linux-thread-multi
/usr/lib64/perl5/vendor_perl/5.38
/usr/lib64/perl5/5.38/x86_64-linux-thread-multi /usr/lib64/perl5/5.38)
at /usr/lib64/perl5/vendor_perl/5.38/HTTP/Headers.pm line 8.
BEGIN failed--compilation aborted at
/usr/lib64/perl5/vendor_perl/5.38/HTTP/Headers.pm line 8.
Compilation failed in require at
/usr/lib64/perl5/vendor_perl/5.38/HTTP/Message.pm line 8.
Compilation failed in require at /usr/lib64/perl5/5.38/parent.pm line 16.
BEGIN failed--compilation aborted at
/usr/lib64/perl5/vendor_perl/5.38/HTTP/Request.pm line 8.
Compilation failed in require at
/usr/lib64/perl5/vendor_perl/5.38/LWP/UserAgent.pm line 9.
BEGIN failed--compilation aborted at
/usr/lib64/perl5/vendor_perl/5.38/LWP/UserAgent.pm line 9.
Compilation failed in require at
/usr/lib64/perl5/vendor_perl/5.38/LWP/Simple.pm line 25.
BEGIN failed--compilation aborted at
/usr/lib64/perl5/vendor_perl/5.38/LWP/Simple.pm line 25.
Compilation failed in require at /usr/bin/genlop line 29.
BEGIN failed--compilation aborted at /usr/bin/genlop line 29.
NAS2 ~ #


I had already emerged the main perl 

Re: [gentoo-user] frei0r-plugins opencv ffmpeg Error: circular dependencies

2024-04-29 Thread Dale
Hi,

What it did, it caused a package to fail that the others depended on. 
Once it failed, the others failed as well.  I did a search on the forum
and found one thread that had the problem.  I do wish people would use
better topic tittles than 'my emerge failed' or oh my upgrade stopped'
or some other equally uninformative title.  Anyway, when I found that I
had forgot to comment out the wrong line, I fixed it.  Then it moved
on.  Weird but hey, it worked. 

Now I'm working on Michael's solution to the other problem.

Dale

:-)  :-) 


Waldo Lemmer wrote:
> Hi Dale,
>
> CFLAGS can't have an effect on dependencies. It is passed to make;
> emerge doesn't use it. Emerge does use CPU_FLAGS_*, but I don't know
> if those flags are used for any conditional dependencies.
>
> Regards,
> Waldo
>
> On Mon, Apr 29, 2024, 07:07 Dale  > wrote:
>
> Dale wrote:
> > Howdy,
> >
> > I'm installing Gentoo on that old Dell Inspiron still.  I'm getting
> > close.  I'm now at this. 
> >
> >
> >  * Error: circular dependencies:
> >
> > (media-plugins/frei0r-plugins-1.8.0:0/0::gentoo, ebuild
> scheduled for
> > merge) depends on
> >  (media-libs/opencv-4.9.0:0/4.9.0::gentoo, ebuild scheduled for
> merge)
> > (buildtime_slot_op)
> >   (media-video/ffmpeg-6.1.1-r5:0/58.60.60::gentoo, ebuild
> scheduled for
> > merge) (buildtime_slot_op)
> >    (media-plugins/frei0r-plugins-1.8.0:0/0::gentoo, ebuild
> scheduled for
> > merge) (buildtime)
> >
> > It might be possible to break this cycle
> > by applying any of the following changes:
> > - media-video/ffmpeg-6.1.1-r5 (Change USE: -frei0r)
> > - media-plugins/frei0r-plugins-1.8.0 (Change USE: -facedetect)
> > - media-libs/opencv-4.9.0 (Change USE: -ffmpeg)
> >
> > Note that this change can be reverted, once the package has been
> installed.
> > NAS2 ~ #
> >
> >
> > Earlier, I added those USE flags so that it could continue on
> with the
> > install.  I figured it was like that harfbuzz and something else
> thing. 
> > Now that everything else is done, I want to go back to the
> default USE
> > flags, like it said I could.  Thing is, when I remove the ones
> it wants
> > above, it still complains.  It either fails to build or spits out
> > something like above. 
> >
> > Has anyone doing a recent new install ran into this and know how
> to get
> > around it?  I've tried different options but they either fail or
> tell me
> > to change back to the settings it suggests above.  I searched
> the forums
> > but didn't find anything.  Google didn't find anything either. 
> I may
> > have found something new.  ROFL
> >
> > Thoughts??
> >
> > Dale
> >
> > :-)  :-)
>
>
> Found a solution for most of it.  When I did my install, I added a
> line
> for CFLAGS but failed to comment out the other line.  It seems to have
> confused either emerge or that package or maybe both.  Basically, it
> left it empty, no setting at all. 
>
> Now I'm left with a failure for net-dns/avahi which gives me this: 
>
>
> sed -e 's,@pkgsysconfdir\@,/etc/avahi,g' \
>     -e 's,@servicedir\@,/etc/avahi/services,g' \
>     -e 's,@PACKAGE_BUGREPORT\@,avahi (at) lists (dot) freedesktop
> (dot) org,g' \
>     -e 's,@PACKAGE_URL\@,http://avahi.org/,g'
> avahi-discover.1.xml.in  >
> avahi-discover.1.xml
> sed -e 's,@pkgsysconfdir\@,/etc/avahi,g' \
>     -e 's,@servicedir\@,/etc/avahi/services,g' \
>     -e 's,@PACKAGE_BUGREPORT\@,avahi (at) lists (dot) freedesktop
> (dot) org,g' \
>     -e 's,@PACKAGE_URL\@,http://avahi.org/,g'
> avahi-bookmarks.1.xml.in  >
> avahi-bookmarks.1.xml
> sed -e 's,@pkgsysconfdir\@,/etc/avahi,g' \
>     -e 's,@servicedir\@,/etc/avahi/services,g' \
>     -e 's,@PACKAGE_BUGREPORT\@,avahi (at) lists (dot) freedesktop
> (dot) org,g' \
>     -e 's,@PACKAGE_URL\@,http://avahi.org/,g' bssh.1.xml.in
>  > bssh.1.xml
> xmltoman avahi-daemon.8.xml > avahi-daemon.8
> Can't locate XML/Parser.pm in @INC (you may need to install the
> XML::Parser module) (@INC entries checked: /etc/perl
> /usr/local/lib64/perl5/5.38/x86_64-linux-thread-multi
> /usr/local/lib64/perl5/5.38
> /usr/lib64/perl5/vendor_perl/5.38/x86_64-linux-thread-multi
> /usr/lib64/perl5/vendor_perl/5.38
> /usr/lib64/perl5/5.38/x86_64-linux-thread-multi /usr/lib64/perl5/5.38)
> at /usr/bin/xmltoman line 22.
> BEGIN failed--compilation aborted at /usr/bin/xmltoman line 22.
> make[2]: *** [Makefile:861: avahi-daemon.8] Error 2
> make[2]: Leaving directory
> 
> 

Re: [gentoo-user] frei0r-plugins opencv ffmpeg Error: circular dependencies

2024-04-29 Thread Michael
On Monday, 29 April 2024 06:07:04 BST Dale wrote:
> Dale wrote:
> > Howdy,
> > 
> > I'm installing Gentoo on that old Dell Inspiron still.  I'm getting
> > close.  I'm now at this. 
> > 
> > 
> >  * Error: circular dependencies:
> > 
> > (media-plugins/frei0r-plugins-1.8.0:0/0::gentoo, ebuild scheduled for
> > merge) depends on
> >  (media-libs/opencv-4.9.0:0/4.9.0::gentoo, ebuild scheduled for merge)
> > (buildtime_slot_op)
> >   (media-video/ffmpeg-6.1.1-r5:0/58.60.60::gentoo, ebuild scheduled for
> > merge) (buildtime_slot_op)
> >(media-plugins/frei0r-plugins-1.8.0:0/0::gentoo, ebuild scheduled for
> > merge) (buildtime)
> > 
> > It might be possible to break this cycle
> > by applying any of the following changes:
> > - media-video/ffmpeg-6.1.1-r5 (Change USE: -frei0r)
> > - media-plugins/frei0r-plugins-1.8.0 (Change USE: -facedetect)
> > - media-libs/opencv-4.9.0 (Change USE: -ffmpeg)
> > 
> > Note that this change can be reverted, once the package has been
> > installed.
> > NAS2 ~ #
> > 
> > 
> > Earlier, I added those USE flags so that it could continue on with the
> > install.  I figured it was like that harfbuzz and something else thing. 
> > Now that everything else is done, I want to go back to the default USE
> > flags, like it said I could.  Thing is, when I remove the ones it wants
> > above, it still complains.  It either fails to build or spits out
> > something like above. 
> > 
> > Has anyone doing a recent new install ran into this and know how to get
> > around it?  I've tried different options but they either fail or tell me
> > to change back to the settings it suggests above.  I searched the forums
> > but didn't find anything.  Google didn't find anything either.  I may
> > have found something new.  ROFL
> > 
> > Thoughts??
> > 
> > Dale
> > 
> > :-)  :-)
> 
> Found a solution for most of it.  When I did my install, I added a line
> for CFLAGS but failed to comment out the other line.  It seems to have
> confused either emerge or that package or maybe both.  Basically, it
> left it empty, no setting at all. 
> 
> Now I'm left with a failure for net-dns/avahi which gives me this: 
> 
> 
> sed -e 's,@pkgsysconfdir\@,/etc/avahi,g' \
> -e 's,@servicedir\@,/etc/avahi/services,g' \
> -e 's,@PACKAGE_BUGREPORT\@,avahi (at) lists (dot) freedesktop
> (dot) org,g' \
> -e 's,@PACKAGE_URL\@,http://avahi.org/,g'
> avahi-discover.1.xml.in > avahi-discover.1.xml
> sed -e 's,@pkgsysconfdir\@,/etc/avahi,g' \
> -e 's,@servicedir\@,/etc/avahi/services,g' \
> -e 's,@PACKAGE_BUGREPORT\@,avahi (at) lists (dot) freedesktop
> (dot) org,g' \
> -e 's,@PACKAGE_URL\@,http://avahi.org/,g'
> avahi-bookmarks.1.xml.in > avahi-bookmarks.1.xml
> sed -e 's,@pkgsysconfdir\@,/etc/avahi,g' \
> -e 's,@servicedir\@,/etc/avahi/services,g' \
> -e 's,@PACKAGE_BUGREPORT\@,avahi (at) lists (dot) freedesktop
> (dot) org,g' \
> -e 's,@PACKAGE_URL\@,http://avahi.org/,g' bssh.1.xml.in > bssh.1.xml
> xmltoman avahi-daemon.8.xml > avahi-daemon.8
> Can't locate XML/Parser.pm in @INC (you may need to install the
> XML::Parser module) (@INC entries checked: /etc/perl

This message above looks suspicious:

"Can't locate XML/Parser.pm in @INC (you may need to install the
XML::Parser module) (@INC entries checked: /etc/perl"

In the first instance I'd throw 'perl-cleaner --reallyall' at it and see if 
the situation improves.


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] frei0r-plugins opencv ffmpeg Error: circular dependencies

2024-04-28 Thread Waldo Lemmer
Hi Dale,

CFLAGS can't have an effect on dependencies. It is passed to make; emerge
doesn't use it. Emerge does use CPU_FLAGS_*, but I don't know if those
flags are used for any conditional dependencies.

Regards,
Waldo

On Mon, Apr 29, 2024, 07:07 Dale  wrote:

> Dale wrote:
> > Howdy,
> >
> > I'm installing Gentoo on that old Dell Inspiron still.  I'm getting
> > close.  I'm now at this.
> >
> >
> >  * Error: circular dependencies:
> >
> > (media-plugins/frei0r-plugins-1.8.0:0/0::gentoo, ebuild scheduled for
> > merge) depends on
> >  (media-libs/opencv-4.9.0:0/4.9.0::gentoo, ebuild scheduled for merge)
> > (buildtime_slot_op)
> >   (media-video/ffmpeg-6.1.1-r5:0/58.60.60::gentoo, ebuild scheduled for
> > merge) (buildtime_slot_op)
> >(media-plugins/frei0r-plugins-1.8.0:0/0::gentoo, ebuild scheduled for
> > merge) (buildtime)
> >
> > It might be possible to break this cycle
> > by applying any of the following changes:
> > - media-video/ffmpeg-6.1.1-r5 (Change USE: -frei0r)
> > - media-plugins/frei0r-plugins-1.8.0 (Change USE: -facedetect)
> > - media-libs/opencv-4.9.0 (Change USE: -ffmpeg)
> >
> > Note that this change can be reverted, once the package has been
> installed.
> > NAS2 ~ #
> >
> >
> > Earlier, I added those USE flags so that it could continue on with the
> > install.  I figured it was like that harfbuzz and something else thing.
> > Now that everything else is done, I want to go back to the default USE
> > flags, like it said I could.  Thing is, when I remove the ones it wants
> > above, it still complains.  It either fails to build or spits out
> > something like above.
> >
> > Has anyone doing a recent new install ran into this and know how to get
> > around it?  I've tried different options but they either fail or tell me
> > to change back to the settings it suggests above.  I searched the forums
> > but didn't find anything.  Google didn't find anything either.  I may
> > have found something new.  ROFL
> >
> > Thoughts??
> >
> > Dale
> >
> > :-)  :-)
>
>
> Found a solution for most of it.  When I did my install, I added a line
> for CFLAGS but failed to comment out the other line.  It seems to have
> confused either emerge or that package or maybe both.  Basically, it
> left it empty, no setting at all.
>
> Now I'm left with a failure for net-dns/avahi which gives me this:
>
>
> sed -e 's,@pkgsysconfdir\@,/etc/avahi,g' \
> -e 's,@servicedir\@,/etc/avahi/services,g' \
> -e 's,@PACKAGE_BUGREPORT\@,avahi (at) lists (dot) freedesktop
> (dot) org,g' \
> -e 's,@PACKAGE_URL\@,http://avahi.org/,g'
> avahi-discover.1.xml.in > avahi-discover.1.xml
> sed -e 's,@pkgsysconfdir\@,/etc/avahi,g' \
> -e 's,@servicedir\@,/etc/avahi/services,g' \
> -e 's,@PACKAGE_BUGREPORT\@,avahi (at) lists (dot) freedesktop
> (dot) org,g' \
> -e 's,@PACKAGE_URL\@,http://avahi.org/,g'
> avahi-bookmarks.1.xml.in > avahi-bookmarks.1.xml
> sed -e 's,@pkgsysconfdir\@,/etc/avahi,g' \
> -e 's,@servicedir\@,/etc/avahi/services,g' \
> -e 's,@PACKAGE_BUGREPORT\@,avahi (at) lists (dot) freedesktop
> (dot) org,g' \
> -e 's,@PACKAGE_URL\@,http://avahi.org/,g' bssh.1.xml.in >
> bssh.1.xml
> xmltoman avahi-daemon.8.xml > avahi-daemon.8
> Can't locate XML/Parser.pm in @INC (you may need to install the
> XML::Parser module) (@INC entries checked: /etc/perl
> /usr/local/lib64/perl5/5.38/x86_64-linux-thread-multi
> /usr/local/lib64/perl5/5.38
> /usr/lib64/perl5/vendor_perl/5.38/x86_64-linux-thread-multi
> /usr/lib64/perl5/vendor_perl/5.38
> /usr/lib64/perl5/5.38/x86_64-linux-thread-multi /usr/lib64/perl5/5.38)
> at /usr/bin/xmltoman line 22.
> BEGIN failed--compilation aborted at /usr/bin/xmltoman line 22.
> make[2]: *** [Makefile:861: avahi-daemon.8] Error 2
> make[2]: Leaving directory
> '/var/tmp/portage/net-dns/avahi-0.8-r7/work/avahi-0.8-abi_x86_64.amd64/man'
> make[1]: *** [Makefile:826: all-recursive] Error 1
> make[1]: Leaving directory
> '/var/tmp/portage/net-dns/avahi-0.8-r7/work/avahi-0.8-abi_x86_64.amd64'
> make: *** [Makefile:736: all] Error 2
>  * ERROR: net-dns/avahi-0.8-r7::gentoo failed (compile phase):
>  *   emake failed
>
>
>
> I'll go dig, maybe try another version or something.
>
> I wonder why emerge or something didn't point out basically a empty
> setting for CFLAG.  Odd.
>
> Dale
>
> :-)  :-)
>
>


Re: [gentoo-user] frei0r-plugins opencv ffmpeg Error: circular dependencies

2024-04-28 Thread Dale
Dale wrote:
> Howdy,
>
> I'm installing Gentoo on that old Dell Inspiron still.  I'm getting
> close.  I'm now at this. 
>
>
>  * Error: circular dependencies:
>
> (media-plugins/frei0r-plugins-1.8.0:0/0::gentoo, ebuild scheduled for
> merge) depends on
>  (media-libs/opencv-4.9.0:0/4.9.0::gentoo, ebuild scheduled for merge)
> (buildtime_slot_op)
>   (media-video/ffmpeg-6.1.1-r5:0/58.60.60::gentoo, ebuild scheduled for
> merge) (buildtime_slot_op)
>    (media-plugins/frei0r-plugins-1.8.0:0/0::gentoo, ebuild scheduled for
> merge) (buildtime)
>
> It might be possible to break this cycle
> by applying any of the following changes:
> - media-video/ffmpeg-6.1.1-r5 (Change USE: -frei0r)
> - media-plugins/frei0r-plugins-1.8.0 (Change USE: -facedetect)
> - media-libs/opencv-4.9.0 (Change USE: -ffmpeg)
>
> Note that this change can be reverted, once the package has been installed.
> NAS2 ~ #
>
>
> Earlier, I added those USE flags so that it could continue on with the
> install.  I figured it was like that harfbuzz and something else thing. 
> Now that everything else is done, I want to go back to the default USE
> flags, like it said I could.  Thing is, when I remove the ones it wants
> above, it still complains.  It either fails to build or spits out
> something like above. 
>
> Has anyone doing a recent new install ran into this and know how to get
> around it?  I've tried different options but they either fail or tell me
> to change back to the settings it suggests above.  I searched the forums
> but didn't find anything.  Google didn't find anything either.  I may
> have found something new.  ROFL
>
> Thoughts??
>
> Dale
>
> :-)  :-) 


Found a solution for most of it.  When I did my install, I added a line
for CFLAGS but failed to comment out the other line.  It seems to have
confused either emerge or that package or maybe both.  Basically, it
left it empty, no setting at all. 

Now I'm left with a failure for net-dns/avahi which gives me this: 


sed -e 's,@pkgsysconfdir\@,/etc/avahi,g' \
    -e 's,@servicedir\@,/etc/avahi/services,g' \
    -e 's,@PACKAGE_BUGREPORT\@,avahi (at) lists (dot) freedesktop
(dot) org,g' \
    -e 's,@PACKAGE_URL\@,http://avahi.org/,g'
avahi-discover.1.xml.in > avahi-discover.1.xml
sed -e 's,@pkgsysconfdir\@,/etc/avahi,g' \
    -e 's,@servicedir\@,/etc/avahi/services,g' \
    -e 's,@PACKAGE_BUGREPORT\@,avahi (at) lists (dot) freedesktop
(dot) org,g' \
    -e 's,@PACKAGE_URL\@,http://avahi.org/,g'
avahi-bookmarks.1.xml.in > avahi-bookmarks.1.xml
sed -e 's,@pkgsysconfdir\@,/etc/avahi,g' \
    -e 's,@servicedir\@,/etc/avahi/services,g' \
    -e 's,@PACKAGE_BUGREPORT\@,avahi (at) lists (dot) freedesktop
(dot) org,g' \
    -e 's,@PACKAGE_URL\@,http://avahi.org/,g' bssh.1.xml.in > bssh.1.xml
xmltoman avahi-daemon.8.xml > avahi-daemon.8
Can't locate XML/Parser.pm in @INC (you may need to install the
XML::Parser module) (@INC entries checked: /etc/perl
/usr/local/lib64/perl5/5.38/x86_64-linux-thread-multi
/usr/local/lib64/perl5/5.38
/usr/lib64/perl5/vendor_perl/5.38/x86_64-linux-thread-multi
/usr/lib64/perl5/vendor_perl/5.38
/usr/lib64/perl5/5.38/x86_64-linux-thread-multi /usr/lib64/perl5/5.38)
at /usr/bin/xmltoman line 22.
BEGIN failed--compilation aborted at /usr/bin/xmltoman line 22.
make[2]: *** [Makefile:861: avahi-daemon.8] Error 2
make[2]: Leaving directory
'/var/tmp/portage/net-dns/avahi-0.8-r7/work/avahi-0.8-abi_x86_64.amd64/man'
make[1]: *** [Makefile:826: all-recursive] Error 1
make[1]: Leaving directory
'/var/tmp/portage/net-dns/avahi-0.8-r7/work/avahi-0.8-abi_x86_64.amd64'
make: *** [Makefile:736: all] Error 2
 * ERROR: net-dns/avahi-0.8-r7::gentoo failed (compile phase):
 *   emake failed



I'll go dig, maybe try another version or something. 

I wonder why emerge or something didn't point out basically a empty
setting for CFLAG.  Odd. 

Dale

:-)  :-)



[gentoo-user] frei0r-plugins opencv ffmpeg Error: circular dependencies

2024-04-28 Thread Dale
Howdy,

I'm installing Gentoo on that old Dell Inspiron still.  I'm getting
close.  I'm now at this. 


 * Error: circular dependencies:

(media-plugins/frei0r-plugins-1.8.0:0/0::gentoo, ebuild scheduled for
merge) depends on
 (media-libs/opencv-4.9.0:0/4.9.0::gentoo, ebuild scheduled for merge)
(buildtime_slot_op)
  (media-video/ffmpeg-6.1.1-r5:0/58.60.60::gentoo, ebuild scheduled for
merge) (buildtime_slot_op)
   (media-plugins/frei0r-plugins-1.8.0:0/0::gentoo, ebuild scheduled for
merge) (buildtime)

It might be possible to break this cycle
by applying any of the following changes:
- media-video/ffmpeg-6.1.1-r5 (Change USE: -frei0r)
- media-plugins/frei0r-plugins-1.8.0 (Change USE: -facedetect)
- media-libs/opencv-4.9.0 (Change USE: -ffmpeg)

Note that this change can be reverted, once the package has been installed.
NAS2 ~ #


Earlier, I added those USE flags so that it could continue on with the
install.  I figured it was like that harfbuzz and something else thing. 
Now that everything else is done, I want to go back to the default USE
flags, like it said I could.  Thing is, when I remove the ones it wants
above, it still complains.  It either fails to build or spits out
something like above. 

Has anyone doing a recent new install ran into this and know how to get
around it?  I've tried different options but they either fail or tell me
to change back to the settings it suggests above.  I searched the forums
but didn't find anything.  Google didn't find anything either.  I may
have found something new.  ROFL

Thoughts??

Dale

:-)  :-) 

P. S.  I'll be glad when I can put a larger CPU cooler on that old
Dell.  I got the side off with a wall powered fan blowing on it.  ROFL 
With side on, dang near fry a egg on that poor old thing. 



Re: [gentoo-user] Re: Grub, gpt partitions and BIOS, not uefi thing.

2024-04-28 Thread Wol

On 28/04/2024 17:40, Grant Edwards wrote:

On 2024-04-28, Grant Edwards  wrote:


With DOS disk lables, Grub uses empty space between the boot sector
and the first partition as a location to store it's core image file.
That empty space does not exist when using GPT disk label. When using
a GPT disk label, Grub requires that you need to create a "BIOS Boot"
or "Grub Boot" partition so that Grub has somwhere to store it's core
image[1].

And it bears repeating that the bios/grub boot partition only needs to
be 1 or 2MB in size, is _not_ formatted with a filesystem, and is
_not_ the same as either

  1) The "boot" directory where the kernel images and grubs other files
 are installed within a Linux filesystem. [Which you still need
 when booting in Legacy/BIOS mode.]

   or

  2) The UEFI partition that's formated with a FAT filesystem and used
 in UEFI boot mode [which you don't need when booting in
 Legacy/BIOS mode.]

Note that, for new installs, I generally say always create a decent 
sized partition for UEFI, so if you want to change you can, although it 
sounds like in your case it probably doesn't matter :-)



Cheers,

Wol




Re: [gentoo-user] Re: Grub, gpt partitions and BIOS, not uefi thing.

2024-04-28 Thread Dale
Dale wrote:
> Michael wrote:
>> On Sunday, 28 April 2024 19:39:16 BST Dale wrote:
>>> Grant Edwards wrote:
 On 2024-04-28, Grant Edwards  wrote:
> With DOS disk lables, Grub uses empty space between the boot sector
> and the first partition as a location to store it's core image file.
> That empty space does not exist when using GPT disk label. When using
> a GPT disk label, Grub requires that you need to create a "BIOS Boot"
> or "Grub Boot" partition so that Grub has somwhere to store it's core
> image[1].
 And it bears repeating that the bios/grub boot partition only needs to
 be 1 or 2MB in size, is _not_ formatted with a filesystem, and is
 _not_ the same as either

  1) The "boot" directory where the kernel images and grubs other files
  
 are installed within a Linux filesystem. [Which you still need
 when booting in Legacy/BIOS mode.]
   
   or
  
  2) The UEFI partition that's formated with a FAT filesystem and used
  
 in UEFI boot mode [which you don't need when booting in
 Legacy/BIOS mode.]
>>> I think I got a grasp on this now.  Basically, partitions should be like
>>> this. 
>>>
>>>
>>> First spot is the alignment thing.  Usually a few MBs or so and unused.
>> This is created automatically by the partitioning tool, in your case cgdisk, 
>> when you create the first partition on the disk and accept the default 
>> starting sector.
>>
>>
>>> Grub boot partition with ef02 setting, not to be formatted.
>>>
>>> /boot partition for kernel and init thingy.  Usually 1GB or so, enough
>>> for memtest, bootable rescue image etc. 
>>>
>>> / or root partition that is around 150GBs or so.  Enough to expand a bit
>>> and includes /usr and /var.
>>>
>>> /home  rest of disk unless some needed for something else.
>>>
>>>
>>> Do you recall when running grub-install what that command looks like? 
>>> Lets say the Grub partition with ef02 setting is sda1, would it be
>>> grub-install /dev/sda1 or just sda and it finds the empty partition on
>>> its own?
>> The unformatted and empty /dev/sda1 'BIOS Boot Partition' will be found by 
>> GRUB when you run grub-install and it will store its core.img in there.
>>
>> You install GRUB's boot.img in the MBR and therefore you have to specify the 
>> disk, NOT a partition, e.g.:
>>
>> grub-install /dev/sda
>>
>> This command should:
>>
>> 1. Install GRUB's boot.img in the MBR of /dev/sda.
>> 2. Install GRUB's core.img in /dev/sda1 which you created as a 'BIOS boot 
>> partition', type EF02.
>> 3. Create directory /boot/grub to install all the grub fs drivers and files.
>>
>> If you have mounted /boot, all is well.  If you are repairing an 
>> installation 
>> from a liveUSB you can mount the /boot partition, e.g. /mnt/gentoo/boot and 
>> specify this in the CLI:
>>
>> grub-install --boot-directory=/mnt/gentoo/boot /dev/sda
>>
>> NOTE:  As per the link Grant helpfully posted you can create the 'BIOS boot 
>> partition' with cgdisk "... by setting the partition type to 0xEF02 and 
>> giving 
>> it a label of gptbios".
>>
>> https://wiki.gentoo.org/wiki/GRUB#BIOS_with_GPT
>>
> That's what I was thinking.  I think I got it.  I need to make notes of
> this tho.  Before I forget.  :/ 
>
> Thanks to all.
>
> Dale
>
> :-)  :-) 
>


One last update.  I found a video.  They were using gdisk but the
crucial part, he got it to display the partition layout.  It was like I
described as for as the alignment thing, tiny partition with ef02 and
then carry on as usual from there. 

I need to do this on a disk complete with notes, so I don't forget.  My
brain is going fast.  One day, I'll forget how to turn the puter on. 
:'(  I already forget what I went to the kitchen for, it's only 20 feet
away.  :/

Thanks again. 

Dale

:-)  :-)



Re: [gentoo-user] Re: Grub, gpt partitions and BIOS, not uefi thing.

2024-04-28 Thread Dale
Michael wrote:
> On Sunday, 28 April 2024 19:39:16 BST Dale wrote:
>> Grant Edwards wrote:
>>> On 2024-04-28, Grant Edwards  wrote:
 With DOS disk lables, Grub uses empty space between the boot sector
 and the first partition as a location to store it's core image file.
 That empty space does not exist when using GPT disk label. When using
 a GPT disk label, Grub requires that you need to create a "BIOS Boot"
 or "Grub Boot" partition so that Grub has somwhere to store it's core
 image[1].
>>> And it bears repeating that the bios/grub boot partition only needs to
>>> be 1 or 2MB in size, is _not_ formatted with a filesystem, and is
>>> _not_ the same as either
>>>
>>>  1) The "boot" directory where the kernel images and grubs other files
>>>  
>>> are installed within a Linux filesystem. [Which you still need
>>> when booting in Legacy/BIOS mode.]
>>>   
>>>   or
>>>  
>>>  2) The UEFI partition that's formated with a FAT filesystem and used
>>>  
>>> in UEFI boot mode [which you don't need when booting in
>>> Legacy/BIOS mode.]
>> I think I got a grasp on this now.  Basically, partitions should be like
>> this. 
>>
>>
>> First spot is the alignment thing.  Usually a few MBs or so and unused.
> This is created automatically by the partitioning tool, in your case cgdisk, 
> when you create the first partition on the disk and accept the default 
> starting sector.
>
>
>> Grub boot partition with ef02 setting, not to be formatted.
>>
>> /boot partition for kernel and init thingy.  Usually 1GB or so, enough
>> for memtest, bootable rescue image etc. 
>>
>> / or root partition that is around 150GBs or so.  Enough to expand a bit
>> and includes /usr and /var.
>>
>> /home  rest of disk unless some needed for something else.
>>
>>
>> Do you recall when running grub-install what that command looks like? 
>> Lets say the Grub partition with ef02 setting is sda1, would it be
>> grub-install /dev/sda1 or just sda and it finds the empty partition on
>> its own?
> The unformatted and empty /dev/sda1 'BIOS Boot Partition' will be found by 
> GRUB when you run grub-install and it will store its core.img in there.
>
> You install GRUB's boot.img in the MBR and therefore you have to specify the 
> disk, NOT a partition, e.g.:
>
> grub-install /dev/sda
>
> This command should:
>
> 1. Install GRUB's boot.img in the MBR of /dev/sda.
> 2. Install GRUB's core.img in /dev/sda1 which you created as a 'BIOS boot 
> partition', type EF02.
> 3. Create directory /boot/grub to install all the grub fs drivers and files.
>
> If you have mounted /boot, all is well.  If you are repairing an installation 
> from a liveUSB you can mount the /boot partition, e.g. /mnt/gentoo/boot and 
> specify this in the CLI:
>
> grub-install --boot-directory=/mnt/gentoo/boot /dev/sda
>
> NOTE:  As per the link Grant helpfully posted you can create the 'BIOS boot 
> partition' with cgdisk "... by setting the partition type to 0xEF02 and 
> giving 
> it a label of gptbios".
>
> https://wiki.gentoo.org/wiki/GRUB#BIOS_with_GPT
>

That's what I was thinking.  I think I got it.  I need to make notes of
this tho.  Before I forget.  :/ 

Thanks to all.

Dale

:-)  :-) 



Re: [gentoo-user] Re: Grub, gpt partitions and BIOS, not uefi thing.

2024-04-28 Thread Michael
On Sunday, 28 April 2024 19:39:16 BST Dale wrote:
> Grant Edwards wrote:
> > On 2024-04-28, Grant Edwards  wrote:
> >> With DOS disk lables, Grub uses empty space between the boot sector
> >> and the first partition as a location to store it's core image file.
> >> That empty space does not exist when using GPT disk label. When using
> >> a GPT disk label, Grub requires that you need to create a "BIOS Boot"
> >> or "Grub Boot" partition so that Grub has somwhere to store it's core
> >> image[1].
> > 
> > And it bears repeating that the bios/grub boot partition only needs to
> > be 1 or 2MB in size, is _not_ formatted with a filesystem, and is
> > _not_ the same as either
> > 
> >  1) The "boot" directory where the kernel images and grubs other files
> >  
> > are installed within a Linux filesystem. [Which you still need
> > when booting in Legacy/BIOS mode.]
> >   
> >   or
> >  
> >  2) The UEFI partition that's formated with a FAT filesystem and used
> >  
> > in UEFI boot mode [which you don't need when booting in
> > Legacy/BIOS mode.]
> 
> I think I got a grasp on this now.  Basically, partitions should be like
> this. 
> 
> 
> First spot is the alignment thing.  Usually a few MBs or so and unused.

This is created automatically by the partitioning tool, in your case cgdisk, 
when you create the first partition on the disk and accept the default 
starting sector.


> Grub boot partition with ef02 setting, not to be formatted.
> 
> /boot partition for kernel and init thingy.  Usually 1GB or so, enough
> for memtest, bootable rescue image etc. 
> 
> / or root partition that is around 150GBs or so.  Enough to expand a bit
> and includes /usr and /var.
> 
> /home  rest of disk unless some needed for something else.
> 
> 
> Do you recall when running grub-install what that command looks like? 
> Lets say the Grub partition with ef02 setting is sda1, would it be
> grub-install /dev/sda1 or just sda and it finds the empty partition on
> its own?

The unformatted and empty /dev/sda1 'BIOS Boot Partition' will be found by 
GRUB when you run grub-install and it will store its core.img in there.

You install GRUB's boot.img in the MBR and therefore you have to specify the 
disk, NOT a partition, e.g.:

grub-install /dev/sda

This command should:

1. Install GRUB's boot.img in the MBR of /dev/sda.
2. Install GRUB's core.img in /dev/sda1 which you created as a 'BIOS boot 
partition', type EF02.
3. Create directory /boot/grub to install all the grub fs drivers and files.

If you have mounted /boot, all is well.  If you are repairing an installation 
from a liveUSB you can mount the /boot partition, e.g. /mnt/gentoo/boot and 
specify this in the CLI:

grub-install --boot-directory=/mnt/gentoo/boot /dev/sda

NOTE:  As per the link Grant helpfully posted you can create the 'BIOS boot 
partition' with cgdisk "... by setting the partition type to 0xEF02 and giving 
it a label of gptbios".

https://wiki.gentoo.org/wiki/GRUB#BIOS_with_GPT



signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Re: Grub, gpt partitions and BIOS, not uefi thing.

2024-04-28 Thread Dale
Grant Edwards wrote:
> On 2024-04-28, Grant Edwards  wrote:
>
>> With DOS disk lables, Grub uses empty space between the boot sector
>> and the first partition as a location to store it's core image file.
>> That empty space does not exist when using GPT disk label. When using
>> a GPT disk label, Grub requires that you need to create a "BIOS Boot"
>> or "Grub Boot" partition so that Grub has somwhere to store it's core
>> image[1].
> And it bears repeating that the bios/grub boot partition only needs to
> be 1 or 2MB in size, is _not_ formatted with a filesystem, and is
> _not_ the same as either
>
>  1) The "boot" directory where the kernel images and grubs other files
> are installed within a Linux filesystem. [Which you still need
> when booting in Legacy/BIOS mode.]
>
>   or
>
>  2) The UEFI partition that's formated with a FAT filesystem and used
> in UEFI boot mode [which you don't need when booting in
> Legacy/BIOS mode.]
>


I think I got a grasp on this now.  Basically, partitions should be like
this. 


First spot is the alignment thing.  Usually a few MBs or so and unused.

Grub boot partition with ef02 setting, not to be formatted.

/boot partition for kernel and init thingy.  Usually 1GB or so, enough
for memtest, bootable rescue image etc. 

/ or root partition that is around 150GBs or so.  Enough to expand a bit
and includes /usr and /var.

/home  rest of disk unless some needed for something else.


Do you recall when running grub-install what that command looks like? 
Lets say the Grub partition with ef02 setting is sda1, would it be
grub-install /dev/sda1 or just sda and it finds the empty partition on
its own?  That's the only thing I'm not real sure of at this point.  I
think it is sda.  Maybe. ;-)

Or is all that above just plain wrong?  O-o 

Dale

:-)  :-) 

P. S.  Been on tractor with a box blade.  Did three very long driveways
and a couple short ones.  My neighbors have smooth driveways again.  :-D 



[gentoo-user] Re: Grub, gpt partitions and BIOS, not uefi thing.

2024-04-28 Thread Grant Edwards
On 2024-04-28, Grant Edwards  wrote:

> With DOS disk lables, Grub uses empty space between the boot sector
> and the first partition as a location to store it's core image file.
> That empty space does not exist when using GPT disk label. When using
> a GPT disk label, Grub requires that you need to create a "BIOS Boot"
> or "Grub Boot" partition so that Grub has somwhere to store it's core
> image[1].

And it bears repeating that the bios/grub boot partition only needs to
be 1 or 2MB in size, is _not_ formatted with a filesystem, and is
_not_ the same as either

 1) The "boot" directory where the kernel images and grubs other files
are installed within a Linux filesystem. [Which you still need
when booting in Legacy/BIOS mode.]

  or

 2) The UEFI partition that's formated with a FAT filesystem and used
in UEFI boot mode [which you don't need when booting in
Legacy/BIOS mode.]





[gentoo-user] Re: Grub, gpt partitions and BIOS, not uefi thing.

2024-04-28 Thread Grant Edwards
On 2024-04-27, Michael  wrote:
> On Saturday, 27 April 2024 17:53:25 BST Dale wrote:
>> Howdy,
>> 
>> I'm installing Gentoo on another old box.  To be consistent I like
>> to use cgdisk, GPT I think it is called, to partition all my
>> drives, regardless of size.
>
> GPT is the partition table structure, which is more advanced than
> the old DOS partition table structure.
>
>> Thing is, Grub works differently with GPT than it does with the old
>> DOS or whatever it is called, like fdisk does in the old days.
>
> GRUB works the same, but the disk/partition table structure is different.

No, grub doesn't work the with GPT disk labels as it did with DOS disk
labels.

With DOS disk lables, Grub uses empty space between the boot sector
and the first partition as a location to store it's core image file.
That empty space does not exist when using GPT disk label. When using
a GPT disk label, Grub requires that you need to create a "BIOS Boot"
or "Grub Boot" partition so that Grub has somwhere to store it's core
image[1].

https://wiki.gentoo.org/wiki/GRUB#BIOS_with_GPT
https://wiki.archlinux.org/title/GRUB#BIOS_systems


[1] There is an alternative installation method where Grub will record
the disk block numbers occupied by the core image files as they
reside in the normal filesystem.  That's extra work to maintain
and might not be reliable for some filesystem types, so it's not
recommended.




Re: [gentoo-user] Grub, gpt partitions and BIOS, not uefi thing.

2024-04-28 Thread Dale
Michael wrote:
> On Sunday, 28 April 2024 13:57:23 BST Dale wrote:
>
>> I just got to figure out how to make it so I can login as root via ssh
>> again.  I set PermitRootLogin to yes in ssh config but still refuses.  I
>> did it on my NAS box but can't recall what else I had to do.
> Just checking the obvious, did you start sshd?
>
> Is a port open and listening for ssh connections (use nc, telnet, nmap to 
> find 
> out).
>
> Will it let you login as a plain user, then 'su' to run as root?
>
> Make sure the plain user is in the wheel group.


Right now, I can login as a user then su to root, and password.  I just
can't login as root directly.  I use Dolphin and the fish thingy to
access config files etc so I can use Kwrite to edit files etc.  Thing
is, I have to login as root for some files.  No way to su to root with
Dolphin, that I know of anyway. 

I'm pretty sure I set this up on the old NAS box.  My searches shows the
PermitRootLogin set to yes should do it but I guess I missed something. 

Any ideas?  I did search old threads but only found the option above,
mentioned by Neil I think. 

Dale

:-)  :-) 



Re: [gentoo-user] Grub, gpt partitions and BIOS, not uefi thing.

2024-04-28 Thread Michael
On Sunday, 28 April 2024 13:57:23 BST Dale wrote:

> I just got to figure out how to make it so I can login as root via ssh
> again.  I set PermitRootLogin to yes in ssh config but still refuses.  I
> did it on my NAS box but can't recall what else I had to do.

Just checking the obvious, did you start sshd?

Is a port open and listening for ssh connections (use nc, telnet, nmap to find 
out).

Will it let you login as a plain user, then 'su' to run as root?

Make sure the plain user is in the wheel group.


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Grub, gpt partitions and BIOS, not uefi thing.

2024-04-28 Thread Dale
Mickaël Bucas wrote:
> Hi
>
> Le sam. 27 avr. 2024 à 18:53, Dale  a écrit :
>> Howdy,
>>
>> I'm installing Gentoo on another old box.
> I was wondering how old this box could be and if it had a BIOS with
> UEFI and GPT.
>
> I didn't find a precise date for BIOS, but Wikipedia[1] shows that the
> first version of Windows for x64 that can read and write GPT was
> published on 2005-04-25. To boot with UEFI, a later version was
> published on 2006-07-22.
> I think this means most BIOSes were compatible to various degrees at this 
> time.
>
> So if your box is less than 20 years old, it should be OK !
> I don't remember how powerful the boxes were at this time, but they
> still had floppy disk drives :)
>
>> Thanks to anyone who has a link, some notes or something.  :-D
>>
>> Dale
>>
>> :-)  :-)
> Good luck
>
> Mickaël Bucas
>
> [1] 
> https://en.wikipedia.org/wiki/GUID_Partition_Table#Windows:_64-bit_versions
>
> .
>


Well, this thing is old enough it is only BIOS.  It's a old Dell
Inspiron 546.  It has a AMD Phenom II X4 955 CPU in it.  I upgraded it a
bit.  It is maxed out at 8GBs of memory.  No floppy but I wouldn't be
surprised to see a connector on the mobo for one tho. 

I mostly use these as rigs to do backups with but could serve as a rig
to watch TV with if my main rig goes to puter heaven.  This one is in a
case at least.  My usual NAS/backup box rig sits on a piece of plywood. 
Good ventilation during compiles tho.  ROFL 

I just got to figure out how to make it so I can login as root via ssh
again.  I set PermitRootLogin to yes in ssh config but still refuses.  I
did it on my NAS box but can't recall what else I had to do.  No
monitor, power plug or anything for it right now.  I moved it to the
kitchen table so I could hook this old Dell to the router. 

Now to see what else I can get into. 

Dale

:-)  :-) 



Re: [gentoo-user] dhcp error. No network. Address family not supported.

2024-04-28 Thread Michael
On Sunday, 28 April 2024 03:29:09 BST Dale wrote:
> Michael wrote:
> > On Saturday, 27 April 2024 23:30:46 BST Dale wrote:
[snip ...]

> >> Anyone ever seen this?  Searching didn't help.  This is a new kernel so
> >> maybe I missed something in there?
> > 
> > Yes, most likely.
> > 
> > What does this show:
> > 
> > grep SOCKET /usr/src/linux/.config
> > 
> > or this:
> > 
> > grep PACKET /usr/src/linux/.config
> 
> OK.  Some of those were turned off.  I cut on anything that looked like
> something I'd need.  Recompiled the kernel and rebooted.  What do you
> know, it worked. 

Cool :-)


> Now some questions, why is something that most anyone would need turned
> off by default?  Why is it not mentioned along with other things in the
> install docs?  I went through the install docs for those options needed,
> I don't recall seeing those.

I don't know what the devs' thinking on this has been, but it could be such 
options are not enabled by default because the network configuration can 
affect security.  For a binary desktop distro, more generic options would be 
preconfigured, as I expect is the case with genkernel.


> The only things I left out were the UEFI
> thingy stuff.  I so dread that UEFI thingy on the new build.  o_O

I think UEFI is rather simpler to set up, no "BIOS Boot Partition" required.  
Just create a partition with type ef00 (GUID type C12A7328-F81F-11D2-
BA4B-00A0C93EC93B - EFI system partition) and format it as FAT32, before you 
mount it as /efi.

The handbook details how to set up a UEFI system with ESP, so spend some time 
reading through the docs before you jump in and consider options and 
permutations if you will be using openrc or systemd.


> Thanks to all.  It running, apparently with IPv6 at that.  O_O 

Consider your firewall settings to include IPv6, if IPv6 is enabled.



signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Grub, gpt partitions and BIOS, not uefi thing.

2024-04-28 Thread Michael
On Sunday, 28 April 2024 06:24:09 BST Dale wrote:
> Michael wrote:
> > On Saturday, 27 April 2024 17:53:25 BST Dale wrote:
[snip ...]

> >> I did some research but still find myself in some muddy
> >> waters.  My take on some things I've read, I need a boot partition, not
> >> to be confused with the /boot for kernels, init thingys and such.  Where
> >> I get lost, most use gdisk.  I like cgdisk.  Before that I liked
> >> cfdisk.  Anyway, how do I set up that partition with cgdisk?  Any
> >> minimum size requirements or tiny is enough?
> > 
> > 1MB
> 
> OK.  You know that "alignment" thing that is always on the beginning of
> a drive, could it use it?  I think it is like 2MBs or something. 

It should be 1MB, sector 2048.  For 512 byte sector size you'd get:

2048 x 512 = 1,048,576 bytes

This is coded in on modern partitioning tools to ensure alignment of logical 
and physical sectors by default.  This alignment is critical for the 
performance of so called "Advanced Format" disks with 4096 byte size of 
physical sectors.  Therefore I strongly suggest you let the partitioning tool 
align its logical partitions where it feels best - at the 1MB boundary and not 
change it.

HOWEVER ...

If you are partitioning an old disk on a BIOS MoBo with logical/physical 
sector sizes both at 512/512 bytes, then you can take matters into your own 
hands and force it to start your 'BIOS Boot Partition' at sector 34.  Sectors 
0-33 are used by the MBR and the GPT headers, so leave these alone.

Start sector 34
End sector 2047


> >> Does it have to be a
> >> specific type?
> > 
> > Yes, it has to be set up as a "BIOS Boot Partition", with the "ef02", or
> > GUID 21686148-6449-6E6F-744E-656564454649.
> 
> Light bulb moment.  I've seen 8300 and friends, 8200 etc but never seen
> EF02 before.  Now I see what that type means.  That cleared up some
> muddy water.  That lead me to finding this, it has a nice table of
> common codes. 
> 
> https://wiki.archlinux.org/title/GPT_fdisk

If you select [Type] in cgdisk and then press "L" it will list all the 
partition types available.

I suggest you familiarise yourself with gdisk, which has more options, or as 
already suggested GParted has an easy GUI to navigate through.

signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Grub, gpt partitions and BIOS, not uefi thing.

2024-04-28 Thread Mickaël Bucas
Hi

Le sam. 27 avr. 2024 à 18:53, Dale  a écrit :
> Howdy,
>
> I'm installing Gentoo on another old box.
I was wondering how old this box could be and if it had a BIOS with
UEFI and GPT.

I didn't find a precise date for BIOS, but Wikipedia[1] shows that the
first version of Windows for x64 that can read and write GPT was
published on 2005-04-25. To boot with UEFI, a later version was
published on 2006-07-22.
I think this means most BIOSes were compatible to various degrees at this time.

So if your box is less than 20 years old, it should be OK !
I don't remember how powerful the boxes were at this time, but they
still had floppy disk drives :)

> Thanks to anyone who has a link, some notes or something.  :-D
>
> Dale
>
> :-)  :-)

Good luck

Mickaël Bucas

[1] https://en.wikipedia.org/wiki/GUID_Partition_Table#Windows:_64-bit_versions



Re: [gentoo-user] Grub, gpt partitions and BIOS, not uefi thing.

2024-04-27 Thread Dale
Michael wrote:
> On Saturday, 27 April 2024 17:53:25 BST Dale wrote:
>> Howdy,
>>
>> I'm installing Gentoo on another old box.  To be consistent I like to
>> use cgdisk, GPT I think it is called, to partition all my drives,
>> regardless of size.
> GPT is the partition table structure, which is more advanced than the old DOS 
> partition table structure.
>

I just wasn't 100% sure what it was called. 

>> Thing is, Grub works differently with GPT than it
>> does with the old DOS or whatever it is called, like fdisk does in the
>> old days.
> GRUB works the same, but the disk/partition table structure is different.
>
>
>> I did some research but still find myself in some muddy
>> waters.  My take on some things I've read, I need a boot partition, not
>> to be confused with the /boot for kernels, init thingys and such.  Where
>> I get lost, most use gdisk.  I like cgdisk.  Before that I liked
>> cfdisk.  Anyway, how do I set up that partition with cgdisk?  Any
>> minimum size requirements or tiny is enough?
> 1MB

OK.  You know that "alignment" thing that is always on the beginning of
a drive, could it use it?  I think it is like 2MBs or something. 

>> Does it have to be a
>> specific type?
> Yes, it has to be set up as a "BIOS Boot Partition", with the "ef02", or GUID 
> 21686148-6449-6E6F-744E-656564454649.
>

Light bulb moment.  I've seen 8300 and friends, 8200 etc but never seen
EF02 before.  Now I see what that type means.  That cleared up some
muddy water.  That lead me to finding this, it has a nice table of
common codes. 

https://wiki.archlinux.org/title/GPT_fdisk



>> Does it need to be in a specific place?  
> Not necessarily, but since you're not booting this disk on a UEFI MoBo and 
> consequently won't be using an EFI System Partition (ESP), the very first 
> partition is fine and will be out of the way of the remaining disk.
>
>
>> Formatted with a file system?
> Do not format it.  The raw 1MB partition will be used by GRUB to install its 
> core.img file.
>
>
>> Also, when I do grub-install, do I still point to
>> /dev/sda or to /dev/sda1, if sda1 is the special boot partition?
> Sector 0 of your disk /dev/sda is where GRUB will drop its boot loader image 
> 'boot.img'.  This is the Master Boot Record region.
>
> Normally, with a DOS partition table, GRUB's core.img would be dropped in the 
> empty space of sector 1, following sector 0.  However, in the GPT structure 
> sector 1 is where the GPT partition array data is stored.  You don't want 
> GRUB 
> making a mess by dropping it's core.img on top of it!
>
> So, from what I recall you'd install GRUB like so:
>
> grub-install --boot-directory=/mnt/gentoo/boot --force /dev/sda
>
> If this won't do it, I'll have to boot an old system of mine to check the 
> disk 
> layout in more detail.
>
>

I may look on youtube and see if I can find someone setting up a disk. 
It may have a video, old one for sure.  Maybe that will help me make
sense of it even more.  I think I got figured out how to use cgdisk now
but installing grub may require some more details. 

What I find odd, most of the howtos I found don't show example outputs. 
Then again, it could just work.  O_o

Thanks to all. 

Dale

:-)  :-)



Re: [gentoo-user] dhcp error. No network. Address family not supported.

2024-04-27 Thread Dale
Michael wrote:
> On Saturday, 27 April 2024 23:30:46 BST Dale wrote:
>> Howdy,
>>
>> I finally got Gentoo on the old rig I had laying around.  This is not
>> the one I usually refer to as NAS box.  I named this one NAS2.  LOL  I
>> got one problem that is confusing me.  I've compared it to my main rig
>> and the install guide and I think I got everything right but maybe I
>> have a typo, missed something or got some other issue.  This is what the
>> screen says, typing by hand so I hope I don't insert a typo. 
>>
>>
>> Bringing up interface enp3s0
>> dhcp ...
>> Running dhcpcd ...
>> dhcpcd-10.0.6 starting
>> main: if_opensockets: address family not supported by protocol
>> dhcpcd exited. 
>>
>>
>> At first I thought that 10.0.6 was a typo on my part in some config
>> file.  The usual IP address for that port is 10.0.0.6.  Eventually I
>> figured out it was the version of dhcp.  So, after getting past that, I
>> started checking everything network related in the install guide. 
>> Basically, set it to use dhcp and let er rip.  Well, this is the first
>> time dhcp has gave me any grief, which is why I think I did something
>> wrong. 
>>
>> Anyone ever seen this?  Searching didn't help.  This is a new kernel so
>> maybe I missed something in there?
> Yes, most likely.
>
> What does this show:
>
> grep SOCKET /usr/src/linux/.config
>
> or this:
>
> grep PACKET /usr/src/linux/.config

OK.  Some of those were turned off.  I cut on anything that looked like
something I'd need.  Recompiled the kernel and rebooted.  What do you
know, it worked. 

Now some questions, why is something that most anyone would need turned
off by default?  Why is it not mentioned along with other things in the
install docs?  I went through the install docs for those options needed,
I don't recall seeing those.  The only things I left out were the UEFI
thingy stuff.  I so dread that UEFI thingy on the new build.  o_O

Thanks to all.  It running, apparently with IPv6 at that.  O_O 

Dale

:-)  :-) 



Re: [gentoo-user] dhcp error. No network. Address family not supported.

2024-04-27 Thread Daniel Frey

On 4/27/24 15:30, Dale wrote:

Howdy,

I finally got Gentoo on the old rig I had laying around.  This is not
the one I usually refer to as NAS box.  I named this one NAS2.  LOL  I
got one problem that is confusing me.  I've compared it to my main rig
and the install guide and I think I got everything right but maybe I
have a typo, missed something or got some other issue.  This is what the
screen says, typing by hand so I hope I don't insert a typo.


Bringing up interface enp3s0
     dhcp ...
         Running dhcpcd ...
dhcpcd-10.0.6 starting
main: if_opensockets: address family not supported by protocol
dhcpcd exited.



Another thought: did you miss CONFIG_PACKET in networking options? That 
possibly could spit that error out too.


Dan




Re: [gentoo-user] dhcp error. No network. Address family not supported.

2024-04-27 Thread Michael
On Saturday, 27 April 2024 23:30:46 BST Dale wrote:
> Howdy,
> 
> I finally got Gentoo on the old rig I had laying around.  This is not
> the one I usually refer to as NAS box.  I named this one NAS2.  LOL  I
> got one problem that is confusing me.  I've compared it to my main rig
> and the install guide and I think I got everything right but maybe I
> have a typo, missed something or got some other issue.  This is what the
> screen says, typing by hand so I hope I don't insert a typo. 
> 
> 
> Bringing up interface enp3s0
> dhcp ...
> Running dhcpcd ...
> dhcpcd-10.0.6 starting
> main: if_opensockets: address family not supported by protocol
> dhcpcd exited. 
> 
> 
> At first I thought that 10.0.6 was a typo on my part in some config
> file.  The usual IP address for that port is 10.0.0.6.  Eventually I
> figured out it was the version of dhcp.  So, after getting past that, I
> started checking everything network related in the install guide. 
> Basically, set it to use dhcp and let er rip.  Well, this is the first
> time dhcp has gave me any grief, which is why I think I did something
> wrong. 
> 
> Anyone ever seen this?  Searching didn't help.  This is a new kernel so
> maybe I missed something in there?

Yes, most likely.

What does this show:

grep SOCKET /usr/src/linux/.config

or this:

grep PACKET /usr/src/linux/.config

signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] dhcp error. No network. Address family not supported.

2024-04-27 Thread Daniel Frey

On 4/27/24 15:30, Dale wrote:

Howdy,

I finally got Gentoo on the old rig I had laying around.  This is not
the one I usually refer to as NAS box.  I named this one NAS2.  LOL  I
got one problem that is confusing me.  I've compared it to my main rig
and the install guide and I think I got everything right but maybe I
have a typo, missed something or got some other issue.  This is what the
screen says, typing by hand so I hope I don't insert a typo.


Bringing up interface enp3s0
     dhcp ...
         Running dhcpcd ...
dhcpcd-10.0.6 starting
main: if_opensockets: address family not supported by protocol
dhcpcd exited.


At first I thought that 10.0.6 was a typo on my part in some config
file.  The usual IP address for that port is 10.0.0.6.  Eventually I
figured out it was the version of dhcp.  So, after getting past that, I
started checking everything network related in the install guide.
Basically, set it to use dhcp and let er rip.  Well, this is the first
time dhcp has gave me any grief, which is why I think I did something
wrong.



You probably don't have ipv6 enabled in the kernel.

There are more and more packages that will not compile with ipv6 
disabled. (Or just do not provide the option to disable ipv6.)


I do not know if dhcpcd is one of them though.

Dan



[gentoo-user] dhcp error. No network. Address family not supported.

2024-04-27 Thread Dale
Howdy,

I finally got Gentoo on the old rig I had laying around.  This is not
the one I usually refer to as NAS box.  I named this one NAS2.  LOL  I
got one problem that is confusing me.  I've compared it to my main rig
and the install guide and I think I got everything right but maybe I
have a typo, missed something or got some other issue.  This is what the
screen says, typing by hand so I hope I don't insert a typo. 


Bringing up interface enp3s0
    dhcp ...
        Running dhcpcd ...
dhcpcd-10.0.6 starting
main: if_opensockets: address family not supported by protocol
dhcpcd exited. 


At first I thought that 10.0.6 was a typo on my part in some config
file.  The usual IP address for that port is 10.0.0.6.  Eventually I
figured out it was the version of dhcp.  So, after getting past that, I
started checking everything network related in the install guide. 
Basically, set it to use dhcp and let er rip.  Well, this is the first
time dhcp has gave me any grief, which is why I think I did something
wrong. 

Anyone ever seen this?  Searching didn't help.  This is a new kernel so
maybe I missed something in there?  All options on the table.  New
install and all.  Oh, network works from from boot media thingy.  

Thanks for any ideas.  Maybe telling me where I boo boo'd.  ROFL

Dale

:-)  :-) 



Re: [gentoo-user] Grub, gpt partitions and BIOS, not uefi thing.

2024-04-27 Thread Wols Lists

On 27/04/2024 17:53, Dale wrote:

Howdy,

I'm installing Gentoo on another old box.  To be consistent I like to
use cgdisk, GPT I think it is called, to partition all my drives,
regardless of size.  Thing is, Grub works differently with GPT than it
does with the old DOS or whatever it is called, like fdisk does in the
old days.  I did some research but still find myself in some muddy
waters.  My take on some things I've read, I need a boot partition, not
to be confused with the /boot for kernels, init thingys and such.  Where
I get lost, most use gdisk.  I like cgdisk.  Before that I liked
cfdisk.  Anyway, how do I set up that partition with cgdisk?  Any
minimum size requirements or tiny is enough?  Does it have to be a
specific type?  Does it need to be in a specific place?  Formatted with
a file system?  Also, when I do grub-install, do I still point to
/dev/sda or to /dev/sda1, if sda1 is the special boot partition?

I tried to find a step by step howto with this info but the ones I find
either don't work or leaves me more confused.  Given that the method is
also aging out, it's hard to find good guides.  I'd be real happy just
to have a link to a good howto that I can make sense of.  I can save a
copy local and even print it.  Maybe someone has some notes that will
help.  I just need something to help clear up the muddy waters.


Hmm ...

Michael's version does not ring any bells with me, and indeed my system 
is *not* set up that way. It's UEFI-capable, but at the time I didn't 
have a clue what I was doing, so the mobo dumped me into BIOS, and I 
just installed everything the old way I knew.


I do, however, have a 512MB partition configured as type "Microsoft 
basic data". This is meant to be for the UEFI partition if I get round 
to converting the system.


If you want to "suck it and see", just install grub to /dev/sda. All 
your GPT disks, by default, leave the first 2MB empty, and grub will 
stick itself in there I believe.


Cheers,
Wol



Re: [gentoo-user] Grub, gpt partitions and BIOS, not uefi thing.

2024-04-27 Thread Michael
On Saturday, 27 April 2024 17:53:25 BST Dale wrote:
> Howdy,
> 
> I'm installing Gentoo on another old box.  To be consistent I like to
> use cgdisk, GPT I think it is called, to partition all my drives,
> regardless of size.

GPT is the partition table structure, which is more advanced than the old DOS 
partition table structure.


> Thing is, Grub works differently with GPT than it
> does with the old DOS or whatever it is called, like fdisk does in the
> old days.

GRUB works the same, but the disk/partition table structure is different.


> I did some research but still find myself in some muddy
> waters.  My take on some things I've read, I need a boot partition, not
> to be confused with the /boot for kernels, init thingys and such.  Where
> I get lost, most use gdisk.  I like cgdisk.  Before that I liked
> cfdisk.  Anyway, how do I set up that partition with cgdisk?  Any
> minimum size requirements or tiny is enough?

1MB

> Does it have to be a
> specific type?

Yes, it has to be set up as a "BIOS Boot Partition", with the "ef02", or GUID 
21686148-6449-6E6F-744E-656564454649.


> Does it need to be in a specific place?  

Not necessarily, but since you're not booting this disk on a UEFI MoBo and 
consequently won't be using an EFI System Partition (ESP), the very first 
partition is fine and will be out of the way of the remaining disk.


> Formatted with a file system?

Do not format it.  The raw 1MB partition will be used by GRUB to install its 
core.img file.


> Also, when I do grub-install, do I still point to
> /dev/sda or to /dev/sda1, if sda1 is the special boot partition?

Sector 0 of your disk /dev/sda is where GRUB will drop its boot loader image 
'boot.img'.  This is the Master Boot Record region.

Normally, with a DOS partition table, GRUB's core.img would be dropped in the 
empty space of sector 1, following sector 0.  However, in the GPT structure 
sector 1 is where the GPT partition array data is stored.  You don't want GRUB 
making a mess by dropping it's core.img on top of it!

So, from what I recall you'd install GRUB like so:

grub-install --boot-directory=/mnt/gentoo/boot --force /dev/sda

If this won't do it, I'll have to boot an old system of mine to check the disk 
layout in more detail.


> I tried to find a step by step howto with this info but the ones I find
> either don't work or leaves me more confused.  Given that the method is
> also aging out, it's hard to find good guides.  I'd be real happy just
> to have a link to a good howto that I can make sense of.  I can save a
> copy local and even print it.  Maybe someone has some notes that will
> help.  I just need something to help clear up the muddy waters. 
> 
> Thanks to anyone who has a link, some notes or something.  :-D 
> 
> Dale
> 
> :-)  :-) 



signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Grub, gpt partitions and BIOS, not uefi thing.

2024-04-27 Thread Mark Knecht
On Sat, Apr 27, 2024 at 9:53 AM Dale  wrote:
>
> Howdy,
>
> I'm installing Gentoo on another old box.  To be consistent I like to
> use cgdisk, GPT I think it is called, to partition all my drives,
> regardless of size.  Thing is, Grub works differently with GPT than it
> does with the old DOS or whatever it is called, like fdisk does in the
> old days.  I did some research but still find myself in some muddy
> waters.  My take on some things I've read, I need a boot partition, not
> to be confused with the /boot for kernels, init thingys and such.  Where
> I get lost, most use gdisk.  I like cgdisk.  Before that I liked
> cfdisk.  Anyway, how do I set up that partition with cgdisk?  Any
> minimum size requirements or tiny is enough?  Does it have to be a
> specific type?  Does it need to be in a specific place?  Formatted with
> a file system?  Also, when I do grub-install, do I still point to
> /dev/sda or to /dev/sda1, if sda1 is the special boot partition?
>
> I tried to find a step by step howto with this info but the ones I find
> either don't work or leaves me more confused.  Given that the method is
> also aging out, it's hard to find good guides.  I'd be real happy just
> to have a link to a good howto that I can make sense of.  I can save a
> copy local and even print it.  Maybe someone has some notes that will
> help.  I just need something to help clear up the muddy waters.
>
> Thanks to anyone who has a link, some notes or something.  :-D
>
> Dale
>
> :-)  :-)

I think I'm not really understanding your request because I only
remember fdisk from the old days, and none of your cfdisk and
cgdisk apps.

If you're working with disk in your new old-box machine then
I'd suggest trying gparted as it pretty much does everything
I've ever needed. It's minimally graphical, can changes the
partition type and boot flags.

This is just one of a billion pages you might look at:

https://linuxiac.com/how-to-use-gparted-to-create-and-resize-partitions/

Wishing you the best of luck,
Mark


Re: [gentoo-user] Grub, gpt partitions and BIOS, not uefi thing.

2024-04-27 Thread Wojciech Kuzyszyn
On Sat, 27 Apr 2024 11:53:25 -0500
Dale  wrote:

> Howdy,
> 
> I'm installing Gentoo on another old box.  To be consistent I like to
> use cgdisk, GPT I think it is called, to partition all my drives,
> regardless of size.  Thing is, Grub works differently with GPT than it
> does with the old DOS or whatever it is called, like fdisk does in the
> old days.  I did some research but still find myself in some muddy
> waters.  My take on some things I've read, I need a boot partition,
> not to be confused with the /boot for kernels, init thingys and such.
>  Where I get lost, most use gdisk.  I like cgdisk.  Before that I
> liked cfdisk.  Anyway, how do I set up that partition with cgdisk?
> Any minimum size requirements or tiny is enough?  Does it have to be a
> specific type?  Does it need to be in a specific place?  Formatted
> with a file system?  Also, when I do grub-install, do I still point to
> /dev/sda or to /dev/sda1, if sda1 is the special boot partition?
> 
> I tried to find a step by step howto with this info but the ones I
> find either don't work or leaves me more confused.  Given that the
> method is also aging out, it's hard to find good guides.  I'd be real
> happy just to have a link to a good howto that I can make sense of.
> I can save a copy local and even print it.  Maybe someone has some
> notes that will help.  I just need something to help clear up the
> muddy waters. 
> 
> Thanks to anyone who has a link, some notes or something.  :-D 
> 
> Dale
> 
> :-)  :-) 
> 

I don't use cgdisk nor gdisk. Here's a link to Arch's wiki about GPT on
BIOS systems:

https://wiki.archlinux.org/title/GRUB#GUID_Partition_Table_(GPT)_specific_instructions

I guess you need to set the same code as in gdisk, or something similar
to BIOS boot or bios_grub as are in other such tools.

Good luck!

Wojciech

-- 
xWK


pgphv3vlrm34X.pgp
Description: Podpis cyfrowy OpenPGP


[gentoo-user] Grub, gpt partitions and BIOS, not uefi thing.

2024-04-27 Thread Dale
Howdy,

I'm installing Gentoo on another old box.  To be consistent I like to
use cgdisk, GPT I think it is called, to partition all my drives,
regardless of size.  Thing is, Grub works differently with GPT than it
does with the old DOS or whatever it is called, like fdisk does in the
old days.  I did some research but still find myself in some muddy
waters.  My take on some things I've read, I need a boot partition, not
to be confused with the /boot for kernels, init thingys and such.  Where
I get lost, most use gdisk.  I like cgdisk.  Before that I liked
cfdisk.  Anyway, how do I set up that partition with cgdisk?  Any
minimum size requirements or tiny is enough?  Does it have to be a
specific type?  Does it need to be in a specific place?  Formatted with
a file system?  Also, when I do grub-install, do I still point to
/dev/sda or to /dev/sda1, if sda1 is the special boot partition?

I tried to find a step by step howto with this info but the ones I find
either don't work or leaves me more confused.  Given that the method is
also aging out, it's hard to find good guides.  I'd be real happy just
to have a link to a good howto that I can make sense of.  I can save a
copy local and even print it.  Maybe someone has some notes that will
help.  I just need something to help clear up the muddy waters. 

Thanks to anyone who has a link, some notes or something.  :-D 

Dale

:-)  :-) 



[gentoo-user] nullmailer error

2024-04-27 Thread ralfconn

Hello,

after a recent world update nullmailer stopped working. 
/var/log/nullmailer/nullmailer.log shows for every message send attempt:


"smtp: Failed: Error completing TLS handshake: The encryption algorithm 
is not supported."


Downgrading gnutls to 3.8.3 fixed the issue for me. I opened a bug 
(https://bugs.gentoo.org/930752).


Does anybody see the same?

raffaele




Re: [gentoo-user] Hibernation without initramfs

2024-04-26 Thread Michael
On Friday, 26 April 2024 10:23:28 BST Wojciech Kuzyszyn wrote:
> On Fri, 26 Apr 2024 09:40:54 +0100
> 
> Michael  wrote:
> > [*] Hibernation (aka 'suspend to disk')
> > [*]   Userspace snapshot device
> > (/dev/sdb6)Default resume partition
> 
> My swap partition is /dev/nvme0n1p2 - this would work I assume, right?

Yes, it is a block device accessed via the PCIe bus.


> > However, if you are using RAM heavily when you try to hibernate, e.g.
> > because you are compiling some large package, have many memory hungry
> > applications open, etc., you may find hibernation fails due to lack
> > of space.  This would be more acute if your RAM is not large enough
> > and swap is used on a regular basis.  With large enough RAM less swap
> > space will be used, since swap would be virtually empty.  Therefore
> > size your swap device accordingly.
> 
> I have oldschool swap - 2x RAM.

OK, with this much space you'd have at least 2x more hibernation storage space 
than you will need.  :-)

signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Hibernation without initramfs

2024-04-26 Thread Wojciech Kuzyszyn
On Fri, 26 Apr 2024 09:40:54 +0100
Michael  wrote:

> [*] Hibernation (aka 'suspend to disk')
> [*]   Userspace snapshot device
> (/dev/sdb6)Default resume partition 

My swap partition is /dev/nvme0n1p2 - this would work I assume, right?

> However, if you are using RAM heavily when you try to hibernate, e.g.
> because you are compiling some large package, have many memory hungry
> applications open, etc., you may find hibernation fails due to lack
> of space.  This would be more acute if your RAM is not large enough
> and swap is used on a regular basis.  With large enough RAM less swap
> space will be used, since swap would be virtually empty.  Therefore
> size your swap device accordingly.

I have oldschool swap - 2x RAM.


-- 
xWK


pgpoV0GlBa6Gb.pgp
Description: Podpis cyfrowy OpenPGP


Re: [gentoo-user] Hibernation without initramfs

2024-04-26 Thread Michael
On Thursday, 25 April 2024 22:29:01 BST Wojciech Kuzyszyn wrote:
> Hello!
> 
> Quick question: is it possible to use hibernation (suspend to disk)
> with no initramfs?

Yes.

> I don't have one and don't want to have one. So I'd
> rather disable hibernate in kernel (so I won't do this by accident) or
> leave it to use it happily when needed.

You have to specify a swap block device - a swap partition, or a preconfigured 
swap file on an already mounted partition - in your kernel configuration, for 
hibernation to work, e.g.:

[*] Hibernation (aka 'suspend to disk')
[*]   Userspace snapshot device
(/dev/sdb6)Default resume partition 

This swap device will be used at hibernation time to compress and store what 
is running in your RAM.  Since the contents of your RAM will be compressed 
less space will be required than the size of your RAM.

However, if you are using RAM heavily when you try to hibernate, e.g. because 
you are compiling some large package, have many memory hungry applications 
open, etc., you may find hibernation fails due to lack of space.  This would 
be more acute if your RAM is not large enough and swap is used on a regular 
basis.  With large enough RAM less swap space will be used, since swap would 
be virtually empty.  Therefore size your swap device accordingly.

signature.asc
Description: This is a digitally signed message part.


[gentoo-user] Hibernation without initramfs

2024-04-25 Thread Wojciech Kuzyszyn
Hello!

Quick question: is it possible to use hibernation (suspend to disk)
with no initramfs? I don't have one and don't want to have one. So I'd
rather disable hibernate in kernel (so I won't do this by accident) or
leave it to use it happily when needed.

-- 
xWK


pgpeMbvAVQkat.pgp
Description: Podpis cyfrowy OpenPGP


[gentoo-user] Permanent workaround for x11-libs/libxcb build problem

2024-04-23 Thread Walter Dnes
  Some machines (e.g. my laptop) experience problems when building the
package x11-libs/libxcb

=
Traceback (most recent call last):
  File 
"/var/tmp/portage/x11-libs/libxcb-1.16.1/work/libxcb-1.16.1/src/c_client.py", 
line 3395, in 
module.generate()
  File "/usr/lib/python3.11/site-packages/xcbgen/state.py", line 131, in 
generate
item.out(name)
  File 
"/var/tmp/portage/x11-libs/libxcb-1.16.1/work/libxcb-1.16.1/src/c_client.py", 
line 3212, in c_request
_man_request(self, name, void=not self.reply, aux=False)
  File 
"/var/tmp/portage/x11-libs/libxcb-1.16.1/work/libxcb-1.16.1/src/c_client.py", 
line 2676, in _man_request
f.write('%s \\- %s\n' % (func_name, brief))
UnicodeEncodeError: 'latin-1' codec can't encode character '\u201c' in position 
68: ordinal not in range(256)
make[1]: *** [Makefile:1425: composite.c] Error 1
make[1]: *** Waiting for unfinished jobs
make[1]: Leaving directory 
'/var/tmp/portage/x11-libs/libxcb-1.16.1/work/libxcb-1.16.1-abi_x86_64.amd64/src'
make: *** [Makefile:799: all-recursive] Error 1
  ERROR: x11-libs/libxcb-1.16.1::gentoo failed (compile phase):
  emake failed
=

  Every so often libxcb gets (re)built and this error pops up.  It's
always vaguely familiar, so I dig through my gentoo list email, and
figure out that libxcb wants 'LC_ALL="C"' and set it for that one time.
I got tired of re-doing this all the time.  This problem is a textbook
example for package.env.  Two one-line files solve the error permanently. 
Make sure that you've created directories "/etc/portage/package.env/"
and "/etc/portage/env/".  Here are the two one-line files.

[thimk2][root][~] cat /etc/portage/env/libxcb.conf 
LC_ALL="C"

[thimk2][root][~] cat /etc/portage/package.env/package.env 
x11-libs/libxcb libxcb.conf

  If you're already using package.env, add the line...
x11-libs/libxcb libxcb.conf
...to your existing package.env file.

-- 
Roses are red
Roses are blue
Depending on their velocity
Relative to you



Re: [gentoo-user] Handbook and question about manual network setup

2024-04-22 Thread Dale
Michael wrote:
> Hi Dale,
>
> On Sunday, 21 April 2024 03:32:32 BST Dale wrote:
>
>> OK.  I did my weekend OS updates on my main rig, fireball.  That
>> involves me switching to boot runlevel and back again.  When the network
>> started, no message about going to default.  It just showed it starting
>> up and using DHCP.   Looks like this: 
>>
>>
>>  * Bringing up interface enp3s0
>>  *   dhcp ...
>>  * Running dhcpcd ...
>>
>>
>>
>> I thought of something.  My NAS box is shutdown right now so can't
>> check.  I bet DHCP is set to start in the default runlevel.  On my main
>> rig it is not set to start the DHCP service at all.  I suspect the NAS
>> box finds the DHCP service first and starts the network and then finds
>> the network service but it is already started.  When it starts the
>> network with the DHCP service, it does the default thing.  I'll test
>> that next time I boot up the NAS box. 
> On one box here I have neither netifrc configured, nor dhcpcd, although both 
> are installed.  I have also made sure networkmanager is not installed.
>
> However, netmount is in the default runlevel and netmount has the default net 
> dependency enabled:
>
> $ grep -v "^#" /etc/conf.d/netmount
> rc_need="net"
>
> $ rc-update show -v | grep -i net
> local |  default nonetwork 
>net-online |
>net.lo |
>  netmount |  default
>
> I believe this is what kicks in on my system first and brings up dhcpcd, 
> which 
> in turn obtains an IP address from my router.  I mostly configure static IP 
> addresses for known devices in my LAN on the router.
>
> You can compare which network services are configured to come up on your NAS 
> Vs your main PC and also check any differences in /etc/rc.conf.  Finally 
> search for "rc_need=" dependencies defined in your /etc/conf.d/*.
>
> https://wiki.gentoo.org/wiki/OpenRC#Dependency_behavior
>
>
>> I guess no one else found a way to get the install handbook on a single
>> page.  I'll have to copy and paste I guess.  That's gonna take a while. 
>> O_O 
>>
>> Dale
>>
>> :-)  :-) 
> To save you copying:
>
> https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation
>
> but note the warning about links redirecting to individual pages:
>
> https://wiki.gentoo.org/wiki/Handbook:AMD64/Full


My thought was right.  My main rig does not have dhcpcd in any
runlevel.  I booted up the NAS box and checked to see if dhcpcd was
listed anywhere.  Sure enough, it was in the default runlevel.  I
removed it and then rebooted.  There was no mention of defaulting to
anything, the network just came up.  So, I guess dhcpcd was trying to
start the network first which means it never really saw any of the
config files I was adding info too.  It was starting before those came
into the picture.  So, now both rigs work the same and I can
start/stop/restart the network on both machines the same way. 

I suspect if I edited some dhcp config file and set up the ethernet the
proper way, it would just come up like it does now, after the change. 
Also, nothing against dhcp on my part.  My main rig uses it.  I wanted
the NAS box to use it as well, just the same as my main rig.  It works
great, even if one doesn't do anything to it.  Having it set up tho does
give more consistent results, as in the same IP address.  I can't recall
the last time I had dhcp to fail actually. 

Thanks for the links on the full docs on one page.  I already copy and
pasted it to a LOo doc and am editing out parts I won't ever use.  It's
116 pages and I'm sure there are parts in there that won't ever apply to
me, systemd for example.  Maybe I can get the page count down to 100 or
so.  If I'm lucky. 

Is there anyway to know when the doc changes and what changes?  And how
did you find that link?  I looked everywhere.  :/

Dale

:-)  :-) 


Re: [gentoo-user] Handbook and question about manual network setup

2024-04-22 Thread Michael
On Sunday, 21 April 2024 20:36:56 BST J. Roeleveld wrote:
> On Friday, 19 April 2024 16:05:47 CEST Dale wrote:
> > Howdy,
> > 
> > I'm playing around with my NAS box again.  I ran into a network issue.
> > I sorta forgot I unplugged the network cable so obviously, it made it
> > difficult to ssh into the thing from my main rig.  After hooking up a
> > monitor and keyboard, I found the problem and plugged the network cable
> > back in.  ROFLMBO  Told y'all I forget stuff.
> > 
> > Anyway, while investigating this, I realized the network setup is not
> > like on my old rig.  Heck, I couldn't even figure out how to restart it
> > other than switching to the boot runlevel and back to default, or
> > rebooting.  After a bit, I think I can restart DHCP and it restart the
> > network.  I figured out the cable was unplugged before trying that.  I'm
> > wanting to set up the NAS box network the same way as my main rig.
> > That's the old manual way.  I went back to the install handbook, that's
> > what I followed when installing on my main rig.  Thing is, it has been
> > updated and the old way isn't all there.  I followed what little bit is
> > there but it defaults back to the new way.  I'm sure I'm missing some
> > file I need to edit but I can't figure out which one it is.  So, is
> > there a way to get the old instructions again?  The ones I followed
> > several years ago for my main rig?  I tried searching but it seems they
> > all gone.  Maybe there is a place I'm not aware of tho.  Basically, I
> > want to be able to start/stop/restart enp3s0 as a service and have it in
> > a runlevel.
> > 
> > Also, I'd like to get the install handbook as one large page.  My
> > intention is to save it locally for future reference as it is now.  I
> > may even print a copy.  I looked at all the places that have different
> > options but can't find the whole thing as one large page.  I looked
> > under several drop down menus and such.  A long time ago, it was a
> > option.  I just can't find it now.  May that option isn't available
> > anymore.  I wish I had a copy of the one from several years ago.  Back
> > when I installed on my main rig.
> > 
> > Some network info.  Lines that are commented out are options I tried but
> > didn't work.  It was worth a shot.  o_O
> > 
> > 
> > nas / # grep -r '!net' /etc/
> > /etc/rc.conf:rc_hotplug="!net.*"
> > nas / # grep -r 'enp3s0' /etc/
> > /etc/resolv.conf:# Generated by dhcpcd from enp3s0.dhcp
> > /etc/conf.d/net:config_enp3s0="dhcp"
> > /etc/conf.d/net:dns_servers_enp3s0="8.8.8.8 8.8.4.4"
> > /etc/conf.d/net:#config_enp3s0="10.0.0.5"
> > nas / #nas / # ifconfig -s enp3s0
> > Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP
> > TX-OVR Flg
> > enp3s0   150016802  0  0 0 17196  0
> > 0  0 BMRU
> > nas / #
> > 
> > 
> > Thoughts?  If I had the old install info, I think I could get it to
> > work.  I did last time.  ;-)
> 
> Yes, try:
> config_enp3s0="10.0.0.5/24"
> routes_enp3s0="default gw "
> 
> Changes to what I see:
> 1) You forgot the netmask ( /24 ) for the network
> 2) I don't see a default route
> 
> --
> Joost

That'll certainly work to specify a static IP address on the PC, but I 
understood Dale wanted to use DHCP to obtain an IP dynamically from the router 
and only use netifrc to set up DNS resolvers.

signature.asc
Description: This is a digitally signed message part.


Re: SOLVED: Re: [gentoo-user] Getting WiFi to work

2024-04-21 Thread Peter Humphrey
On Sunday, 21 April 2024 23:30:54 BST Wol wrote:
> On 19/04/2024 17:02, Peter Humphrey wrote:
> > 
> > Just reporting back.
> > 
> > I built a new system - using NetworkManager (after all I've said about
> > it!) - now that it's so much quicker using binpkgs.
> > 
> > It all went fairly smoothly, taking one step at a time through changing
> > several USE flags, installing various tools, and finally, adding the new
> > wlan0 interface to shorewall.
> > 
> > The machine can now boot with either wired or wireless network, or both.
> > 
> > Thank you, all who helped.
> 
> Any chance you can document those steps?

Yes, I ought to do that. I just need to remember...   ;-)

> I'm struggling to get wireless working on my laptop - the statement in the
> handbook Wireless networking on Linux is usually pretty straightforward.
> There are three ways of configuring wifi: graphical clients, text-mode
> interfaces, and command-line interfaces.
> 
> just seems to be complete rubbish :-(

It does seem that way, indeed. It was certainly no use to me.

> As far as I can tell, my kernel is bringing up the hardware fine - dmesg
> tells me my wireless interface has come up fine with iwlwifi, and has
> been renamed from wlan0 to wlo1. Network manager detects the ethernet
> connection but can't even see the wireless connection.
> 
> Ummm ... of course, sod has just struck, I've rebooted, started Network
> Manager (which I thought I'd uninstalled) and wonder of wonders I have
> internet!
> 
> But some documentation would certainly be appreciated.

I'll see what I can do in the next day or two.

-- 
Regards,
Peter.






Re: SOLVED: Re: [gentoo-user] Getting WiFi to work

2024-04-21 Thread Wol

On 19/04/2024 17:02, Peter Humphrey wrote:

On Tuesday, 9 April 2024 14:23:31 BST I wrote:




Just reporting back.

I built a new system - using NetworkManager (after all I've said about it!) -
now that it's so much quicker using binpkgs.

It all went fairly smoothly, taking one step at a time through changing
several USE flags, installing various tools, and finally, adding the new wlan0
interface to shorewall.

The machine can now boot with either wired or wireless network, or both.

Thank you, all who helped.

Any chance you can document those steps? I'm struggling to get wireless 
working on my laptop - the statement in the handbook


> Wireless networking on Linux is usually pretty straightforward. There 
are three ways of configuring wifi: graphical clients, text-mode 
interfaces, and command-line interfaces.


just seems to be complete rubbish :-(

As far as I can tell, my kernel is bringing up the hardware fine - dmesg 
tells me my wireless interface has come up fine with iwlwifi, and has 
been renamed from wlan0 to wlo1. Network manager detects the ethernet 
connection but can't even see the wireless connection.


Ummm ... of course, sod has just struck, I've rebooted, started Network 
Manager (which I thought I'd uninstalled) and wonder of wonders I have 
internet!


But some documentation would certainly be appreciated.

Cheers,
Wol



Re: [gentoo-user] Handbook and question about manual network setup

2024-04-21 Thread J. Roeleveld
On Friday, 19 April 2024 16:05:47 CEST Dale wrote:
> Howdy,
> 
> I'm playing around with my NAS box again.  I ran into a network issue. 
> I sorta forgot I unplugged the network cable so obviously, it made it
> difficult to ssh into the thing from my main rig.  After hooking up a
> monitor and keyboard, I found the problem and plugged the network cable
> back in.  ROFLMBO  Told y'all I forget stuff. 
> 
> Anyway, while investigating this, I realized the network setup is not
> like on my old rig.  Heck, I couldn't even figure out how to restart it
> other than switching to the boot runlevel and back to default, or
> rebooting.  After a bit, I think I can restart DHCP and it restart the
> network.  I figured out the cable was unplugged before trying that.  I'm
> wanting to set up the NAS box network the same way as my main rig. 
> That's the old manual way.  I went back to the install handbook, that's
> what I followed when installing on my main rig.  Thing is, it has been
> updated and the old way isn't all there.  I followed what little bit is
> there but it defaults back to the new way.  I'm sure I'm missing some
> file I need to edit but I can't figure out which one it is.  So, is
> there a way to get the old instructions again?  The ones I followed
> several years ago for my main rig?  I tried searching but it seems they
> all gone.  Maybe there is a place I'm not aware of tho.  Basically, I
> want to be able to start/stop/restart enp3s0 as a service and have it in
> a runlevel. 
> 
> Also, I'd like to get the install handbook as one large page.  My
> intention is to save it locally for future reference as it is now.  I
> may even print a copy.  I looked at all the places that have different
> options but can't find the whole thing as one large page.  I looked
> under several drop down menus and such.  A long time ago, it was a
> option.  I just can't find it now.  May that option isn't available
> anymore.  I wish I had a copy of the one from several years ago.  Back
> when I installed on my main rig. 
> 
> Some network info.  Lines that are commented out are options I tried but
> didn't work.  It was worth a shot.  o_O 
> 
> 
> nas / # grep -r '!net' /etc/
> /etc/rc.conf:rc_hotplug="!net.*"
> nas / # grep -r 'enp3s0' /etc/
> /etc/resolv.conf:# Generated by dhcpcd from enp3s0.dhcp
> /etc/conf.d/net:config_enp3s0="dhcp"
> /etc/conf.d/net:dns_servers_enp3s0="8.8.8.8 8.8.4.4"
> /etc/conf.d/net:#config_enp3s0="10.0.0.5"
> nas / #nas / # ifconfig -s enp3s0
> Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP
> TX-OVR Flg
> enp3s0   150016802  0  0 0 17196  0 
> 0  0 BMRU
> nas / #
> 
> 
> Thoughts?  If I had the old install info, I think I could get it to
> work.  I did last time.  ;-)

Yes, try:
config_enp3s0="10.0.0.5/24"
routes_enp3s0="default gw "

Changes to what I see:
1) You forgot the netmask ( /24 ) for the network
2) I don't see a default route

--
Joost





Re: [gentoo-user] Handbook and question about manual network setup

2024-04-21 Thread Michael
Hi Dale,

On Sunday, 21 April 2024 03:32:32 BST Dale wrote:

> OK.  I did my weekend OS updates on my main rig, fireball.  That
> involves me switching to boot runlevel and back again.  When the network
> started, no message about going to default.  It just showed it starting
> up and using DHCP.   Looks like this: 
> 
> 
>  * Bringing up interface enp3s0
>  *   dhcp ...
>  * Running dhcpcd ...
> 
> 
> 
> I thought of something.  My NAS box is shutdown right now so can't
> check.  I bet DHCP is set to start in the default runlevel.  On my main
> rig it is not set to start the DHCP service at all.  I suspect the NAS
> box finds the DHCP service first and starts the network and then finds
> the network service but it is already started.  When it starts the
> network with the DHCP service, it does the default thing.  I'll test
> that next time I boot up the NAS box. 

On one box here I have neither netifrc configured, nor dhcpcd, although both 
are installed.  I have also made sure networkmanager is not installed.

However, netmount is in the default runlevel and netmount has the default net 
dependency enabled:

$ grep -v "^#" /etc/conf.d/netmount
rc_need="net"

$ rc-update show -v | grep -i net
local |  default nonetwork 
   net-online |
   net.lo |
 netmount |  default

I believe this is what kicks in on my system first and brings up dhcpcd, which 
in turn obtains an IP address from my router.  I mostly configure static IP 
addresses for known devices in my LAN on the router.

You can compare which network services are configured to come up on your NAS 
Vs your main PC and also check any differences in /etc/rc.conf.  Finally 
search for "rc_need=" dependencies defined in your /etc/conf.d/*.

https://wiki.gentoo.org/wiki/OpenRC#Dependency_behavior


> I guess no one else found a way to get the install handbook on a single
> page.  I'll have to copy and paste I guess.  That's gonna take a while. 
> O_O 
> 
> Dale
> 
> :-)  :-) 

To save you copying:

https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation

but note the warning about links redirecting to individual pages:

https://wiki.gentoo.org/wiki/Handbook:AMD64/Full


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Handbook and question about manual network setup

2024-04-20 Thread Dale
Michael wrote:
> On Friday, 19 April 2024 18:04:57 BST Dale wrote:
>
>> I'm missing something.
> I don't think you are.  Shutdown your main rig.  Pull the ethernet cable. 
> Reboot.  If the main rig's config is the same as the old rig,
>
> AND
>
> the router addressing is analogous on both PCs, 
>
> THEN
>
> their behaviour and messages ought to be the same.
>
>> Dale
>>
>> :-)  :-) 
>>
>> P. S. Back to mowing grass. 


OK.  I did my weekend OS updates on my main rig, fireball.  That
involves me switching to boot runlevel and back again.  When the network
started, no message about going to default.  It just showed it starting
up and using DHCP.   Looks like this: 


 * Bringing up interface enp3s0
 *   dhcp ...
 * Running dhcpcd ...



I thought of something.  My NAS box is shutdown right now so can't
check.  I bet DHCP is set to start in the default runlevel.  On my main
rig it is not set to start the DHCP service at all.  I suspect the NAS
box finds the DHCP service first and starts the network and then finds
the network service but it is already started.  When it starts the
network with the DHCP service, it does the default thing.  I'll test
that next time I boot up the NAS box. 

I guess no one else found a way to get the install handbook on a single
page.  I'll have to copy and paste I guess.  That's gonna take a while. 
O_O 

Dale

:-)  :-) 


Re: [gentoo-user] Handbook and question about manual network setup

2024-04-19 Thread Michael
On Friday, 19 April 2024 18:04:57 BST Dale wrote:

> I'm missing something.

I don't think you are.  Shutdown your main rig.  Pull the ethernet cable. 
Reboot.  If the main rig's config is the same as the old rig,

AND

the router addressing is analogous on both PCs, 

THEN

their behaviour and messages ought to be the same.

> 
> Dale
> 
> :-)  :-) 
> 
> P. S. Back to mowing grass. 



signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Handbook and question about manual network setup

2024-04-19 Thread Dale
Michael wrote:
> On Friday, 19 April 2024 17:20:44 BST Dale wrote:
>> Matt Connell wrote:
>>> On Fri, 2024-04-19 at 09:05 -0500, Dale wrote:
 Basically, I want to be able to start/stop/restart enp3s0 as a
 service and have it in a runlevel. 
>>> You should just need to create a symlink at /etc/init.d/net.enp3s0 that
>>> points to /etc/init.d/net.lo and then you can do the usual rc-service
>>> stuff with it.
>> I did that and went from default to boot runlevel and back to default
>> again but I still couldn't restart with the net.enp3s0 file.  Luckily, I
>> shut the rig down a bit ago.  I went to mow some grass.  Using push
>> mower since battery went bad on riding mower.  Anyway, when I booted it
>> back up just now, it worked.  I can start/stop/restart with the enp3s0
>> file like on my main rig.  It still says it is defaulting to DHCP which
>> makes me think I'm still missing something.  It says, I'm typing this in
>> manually. 
>>
>>
>> Bringing up interface enp3s0
>> config_enp3s0 not specified; defaulting to DHCP
>>
>>
>> Then it continues bringing up the network.  I have this set:
>>
>> nas / # cat /etc/conf.d/net
>> config_enp3s0="dhcp"
>> dns_servers_enp3s0="8.8.8.8 8.8.4.4"
>> nas / #
>>
>>
>> Since I have it set to use DHCP already, why is it saying it is
>> defaulting to it?  Did I miss a file or something?   Shouldn't it just
>> use it without saying it is defaulting to it?  I don't recall seeing
>> this on my main rig. 
>>
>> Dale
>>
>> :-)  :-) 
> Normally you would use netifrc to configure a gateway and static IP address.  
> DHCP is a fallback, in case the static IP subnet has changed - e.g. because 
> you changed your home router.
>
> If you *are* using dhcpcd to obtain an IP address from the router then 
> arguably your don't need netifrc at all, as I explained in my other message 
> earlier.
>
> Regarding the messages you see on your main rig Vs the old rig, you can 
> compare the two PC's conf.net files for any differences.


That's thing.  I think they are the same.  Here is my main rig, fireball. 


root@fireball / # cat /etc/conf.d/net
config_enp3s0="dhcp"
dns_servers_enp3s0="8.8.8.8 8.8.4.4"
root@fireball / #


NAS box:

nas / # cat /etc/conf.d/net
config_enp3s0="dhcp"
dns_servers_enp3s0="8.8.8.8 8.8.4.4"
nas / #


One says it is defaulting, the other doesn't.  I've used grep to search,
I've looked everywhere I can think of that even might have some config
file for network stuff and I can't find any difference. 

On your other reply.  I think I did set up the router to set IP
addresses.  I know I did for my phone and printer.  That printer used to
drive me nuts.  Every time the power would blink, it wouldn't print.  No
IP address so can't access it except through that tiny little display
and the buttons on the printer.  What a drag.  o_O 

I'm missing something.  I set up the network on this rig almost a decade
ago.  I have very little memory of how I did it.  I always thought I
could just refer back to the install guide.  Didn't occur to me they
would remove stuff. 

Dale

:-)  :-) 

P. S. Back to mowing grass. 



Re: [gentoo-user] Handbook and question about manual network setup

2024-04-19 Thread Matt Connell
On Fri, 2024-04-19 at 17:34 +0100, Michael wrote:
> Configure static IP addresses for all your LAN devices on your home
> router.  Then set your devices to use DHCP to obtain an address from
> the router when they come up.  With a large number of devices which
> often change (e.g. guests in a hotel) this is inadvisable, but with a
> home LAN with a handful of devices  this is not too much of a chore.

This is what I do, for the sake of the argument. I never touch client
configuration on anything; the router is the boss. Much easier that way
in my experience.



Re: [gentoo-user] Handbook and question about manual network setup

2024-04-19 Thread Michael
On Friday, 19 April 2024 17:20:44 BST Dale wrote:
> Matt Connell wrote:
> > On Fri, 2024-04-19 at 09:05 -0500, Dale wrote:
> >> Basically, I want to be able to start/stop/restart enp3s0 as a
> >> service and have it in a runlevel. 
> > 
> > You should just need to create a symlink at /etc/init.d/net.enp3s0 that
> > points to /etc/init.d/net.lo and then you can do the usual rc-service
> > stuff with it.
> 
> I did that and went from default to boot runlevel and back to default
> again but I still couldn't restart with the net.enp3s0 file.  Luckily, I
> shut the rig down a bit ago.  I went to mow some grass.  Using push
> mower since battery went bad on riding mower.  Anyway, when I booted it
> back up just now, it worked.  I can start/stop/restart with the enp3s0
> file like on my main rig.  It still says it is defaulting to DHCP which
> makes me think I'm still missing something.  It says, I'm typing this in
> manually. 
> 
> 
> Bringing up interface enp3s0
> config_enp3s0 not specified; defaulting to DHCP
> 
> 
> Then it continues bringing up the network.  I have this set:
> 
> nas / # cat /etc/conf.d/net
> config_enp3s0="dhcp"
> dns_servers_enp3s0="8.8.8.8 8.8.4.4"
> nas / #
> 
> 
> Since I have it set to use DHCP already, why is it saying it is
> defaulting to it?  Did I miss a file or something?   Shouldn't it just
> use it without saying it is defaulting to it?  I don't recall seeing
> this on my main rig. 
> 
> Dale
> 
> :-)  :-) 

Normally you would use netifrc to configure a gateway and static IP address.  
DHCP is a fallback, in case the static IP subnet has changed - e.g. because 
you changed your home router.

If you *are* using dhcpcd to obtain an IP address from the router then 
arguably your don't need netifrc at all, as I explained in my other message 
earlier.

Regarding the messages you see on your main rig Vs the old rig, you can 
compare the two PC's conf.net files for any differences.

signature.asc
Description: This is a digitally signed message part.


  1   2   3   4   5   6   7   8   9   10   >