You are not logged in.

#1 2013-06-03 16:54:09

jason_gates
Member
Registered: 2013-02-12
Posts: 7

Typo in Intervention Instructions?

Hi,
I think there is typo in the "intervention" instructions posted here: https://www.archlinux.org/news/binaries … ervention/

What does this sentence mean?   
"1) Fix any non-official packages with files in /bin, /sbin or /usr/sbin to put those files in /usr/bin." 

Specifically, what does "/usr/sbin to put those files in /usr/bin" mean? 

Does that mean "move" files located in  /bin, /sbin or /usr/sbin to /usr/bin ? Isn't there some words missing in that sentence?

Sorry, I know this is a dumb question, the context implies there is a typo in the instruction. Just want to be safe, can someone either elaborate or correct step 1 (sentence I quoted above),

Again, my apologies, I know folks have put a lot of work in to this. I just don't want to assume anything. Rather be safe than sorry smile

Thank you for your help.

Jason

Last edited by jason_gates (2013-06-03 16:55:09)

Offline

#2 2013-06-03 16:58:01

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,727

Re: Typo in Intervention Instructions?

Anything in /bin, /sbin, or /usr/sbin needs to be addressed. If these are files owned by a package, the package needs modified to put all files in /usr/bin. This is what that sentence means. All packages in the official repos have been fixed, it's warning you that any packages outside the official repos are outside their control and you need to make sure that they've been modified to put everything in /usr/bin.

Last edited by Scimmia (2013-06-03 17:00:58)

Offline

#3 2013-06-03 16:59:59

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: Typo in Intervention Instructions?

It means you should fix (update PKGBUILDs and reinstall) the non-official packages that install files in /bin, /sbin or /usr/sbin so they install files in /usr/bin.

Offline

#4 2013-06-03 17:08:10

Morn
Member
Registered: 2012-09-02
Posts: 886

Re: Typo in Intervention Instructions?

Well whoever wrote those instructions for the front page should read about the serial comma and why it's a good idea to use it to avoid precisely this kind of ambiguity:

1) Fix any non-official packages with files in /bin, /sbin, or /usr/sbin to put those files in /usr/bin.

"Fix…to put" still sounds fairly strange and ungrammatical to me however.

Offline

#5 2013-06-03 17:11:20

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: Typo in Intervention Instructions?

I agree, but news items go through RFC stage, so you can always comment on them and suggest a better wording.

Offline

#6 2013-06-03 17:43:50

ANOKNUSA
Member
Registered: 2010-10-22
Posts: 2,141

Re: Typo in Intervention Instructions?

Just replace "non-official packages" in the instructions with "non-official PKGBUILDs." 

Morn wrote:

Well whoever wrote those instructions for the front page should read about the serial comma and why it's a good idea to use it to avoid precisely this kind of ambiguity:

1) Fix any non-official packages with files in /bin, /sbin, or /usr/sbin to put those files in /usr/bin.

The serial comma only applies to conjunctive statements, not disjunctive ones.  In the case of disjunction, the "or" covers all possible cases; i.e. "If 'A', 'B' or 'C' is the case, take measure 'X'; otherwise, take measure 'Y'."  Even if the sentence had no commas at all, it may be grammatically ugly, but it would still be semantically valid, since whatever the case may be---binaries in any one of those directories, or two of the three, or all three at once---the outcome (and thus the meaning) remains the same.  And that's my logic rant for the day. wink

Offline

#7 2013-06-03 23:30:11

jason_gates
Member
Registered: 2013-02-12
Posts: 7

Re: Typo in Intervention Instructions?

Hi All,
Thank you for the elaboration.

I have a related issue. Not sure if I should start a new post.

I'll mention the issue here,  briefly.

Per the Arch Wiki here https://wiki.archlinux.org/index.php/GR … cessary.3F, I am still using Grub "Legacy".

Thus I have a working a boot loader that is not going to be updated by pacman. However, the grub legacy files reside in "/sbin".
So, if manually move the grub legacy  files from "/sbin" to "/usr/bin", will I be able boot? Sorry, I know, I now have an "unsupported" configuration.  I thought I'd ask anyway smile

Does this really mean, the Arch Wiki needs to be updated. Per today's upgrade, we no longer have the option of running grub legacy.

Any advice greatly appreciated.
Thank you
Jason

Offline

#8 2013-06-04 03:39:40

shariebeth
Member
From: South Florida
Registered: 2010-04-27
Posts: 77

Re: Typo in Intervention Instructions?

jason_gates wrote:

Hi All,
Thank you for the elaboration.

I have a related issue. Not sure if I should start a new post.

I'll mention the issue here,  briefly.

Per the Arch Wiki here https://wiki.archlinux.org/index.php/GR … cessary.3F, I am still using Grub "Legacy".

Thus I have a working a boot loader that is not going to be updated by pacman. However, the grub legacy files reside in "/sbin".
So, if manually move the grub legacy  files from "/sbin" to "/usr/bin", will I be able boot? Sorry, I know, I now have an "unsupported" configuration.  I thought I'd ask anyway smile

Does this really mean, the Arch Wiki needs to be updated. Per today's upgrade, we no longer have the option of running grub legacy.

Any advice greatly appreciated.
Thank you
Jason

Jason, try this thread here.  A few of us did exactly this just fine.
https://bbs.archlinux.org/viewtopic.php?id=164456

Offline

#9 2013-06-04 03:53:07

dudefellaguy
Member
Registered: 2012-02-08
Posts: 21

Re: Typo in Intervention Instructions?

Running grub-legacy is definitely still an option. Users are supposed to modify the PKGBUILD / source files for any packages which aren't in the offical repos that have files in /usr/sbin, /bin, or /sbin, to make them install to /usr/bin. Someone (simon04) already posted a new PKGBUILD in the comments on grub-legacy's AUR page (although I can not personally confirm that it works). Try downloading the tarball, replacing the PKGBUILD file with the new one and rebuilding/reinstalling the package.

Offline

Board footer

Powered by FluxBB