Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
You're right. It goes much faster like that. But it also introduces extra complications.
Now I have quite a few pages done on my local fork (the documentation main page and most of the pages that directly open from it). I shall need to sync the online fork with it, and there is no room for trial and error; if I sync it in the wrong direction, I will lose all the work I have done over the last three days. In which case, I shall probably curse you and all your advice in language unbecoming to a woman of my age!
So please give clear instructions. Then, when my online fork is updated, presumably you can do some kind of diff operation with the main fork and pull through the edited pages.
I haven't touched the manual yet. I assume there are many pages in that. And there are one or two specific documentation pages where the English and the French texts diverge notably, which may call for some discussion between us. I have been using the French text as a guide because there were some English sentences that I just couldn't make sense of.
I'm working through the manual now (it's actually a specific manual for post-install configuration and I think that ought to be made clear). And under Setting the Clock, it suggests that you can tell whether your hardware clock is set to UTC or local time by giving the command "hwclock -r" and seeing if the result agrees with wall time. Now that will not work because hwclock corrects the time silently according to your Linux time setting before displaying it. Consequently a match between the displayed time and the wall clock does not necessarily mean that the hardware clock is set to local time. It simply means that Linux and the hardware clock agree about what kind of time is being shown.
I think a better way would be to use "hwclock -r --debug". This will run hwclock in debug mode and it will show the actual time on the clock as well as any corrected time. If the corrected time does not match wall time, you can then decide whether to use hwclock to reset the clock or whether to modify /etc/sysconfig/clock to match the actual clock setting.
4. Whenever you want, you can "push" your job to YOUR copy of your work. The command is very simple if your git config is correctly configure:
Code:
git push
and you're done. Means you're job is safe and I can already used it (by creating a pull request)
I recommand you some reading if you've never use this tool. It won't be waste of time as it's indeed become a wide used tool for tracking files changes:
Now I'm quite sure you're getting a message says you don't have write access. If that's the case No panic.
You just have to adjust your .git/config file. Everything related to your account is set in that one. If you have writing problems just paste me your core/.git/config file
Last edited by tnut; 07-16-2016 at 10:20 AM.
Reason: Adding a few commands
OK, pushed to github. No errors. All these files are in their final form, so if you like them, you can put them up. There are a couple of pages that I'm still working on and I haven't added those. And of course there are files I haven't touched yet.
PS: Is there some way we can discuss specific editing problems privately without boring everyone else on this forum?
You can post on github.com/NuTyX/core/commits for example
I haven't found an on-screen button for doing that. I find the github site impossibly complex and difficult to navigate, and the online help is bloody useless too. I think I'm really too old for this game.
In the meantime, I have completed translations for the five scenarios and the "Build your own NuTyX" page that they all link to and I've pushed them up for you to look at.
I've also noticed something strange on my NuTyX system. When I used the command sudo cards install cards.devel, it appeared to install all the dependencies (I could see a lot of glibc header files scrolling past) but not the cards.devel package itself. I had to unpack and install it by hand. I wonder why.
I find the github site impossibly complex and difficult to navigate
You absolutely right. Very frustrating in the beginning. Maybe as a tip. Check your mail and you receive one everytime somebody commit or comment yours. If you click on "respond on git.hub" might be a good way to start to become a bit familiar.
When I used the command sudo cards install cards.devel, it appeared to install all the dependencies...not the cards.devel package itself.
If you decide to make some development like build some packages or whatever, you need a compiler, glibc headers, automake, autoconf etc. That's exactly the idea of the cards.devel package. I think you didn't see it but I'm 99 % sure it was installed. If you want to see what's installed:
Code:
cards list
If you want to have info about a package:
Code:
cards info cards.devel
will give you all the infos about the cards.devel package
Last edited by tnut; 07-19-2016 at 01:05 PM.
Reason: Add link
Yes, of course I expected a lot of dependencies - basically everything that Debian puts into its build-essential package. But the actual cards.devel package should have been installed right at the end of the installation sequence and it wasn't. I know that because the pkgmk and pkgadd commands were not available until I unpacked cards.develnnnnnnnn.cards.tar.xz and copied the contents by hand to their appropriate locations.
So here's the question: what would cause the installation sequence to be interrupted before its last step? Just curious!
But the actual cards.devel package should have been installed right at the end of the installation sequence and it wasn't.
You miss something here:
The package cards is made of two parts:
- the /bin/cards binary for a "normal" user who's not interested in compilation and so on (scenario A). It care about downloads, dependencies for all your binaries packages you need but no compilation (pure binary distro)
- the /usr/bin/pkgadd, /usr/bin/pkgrm, /usr/bin/pkginfo, /usr/bin/pkgmk binaries and various scripts for a user who want to start with compilation. Those directs commands don't knows anything about downloading binaries. It up to you compile whatever you want from sources (pure sources distro)
Means, ... yes you get actually TWO Type of distros in one. Thats the reason of thoses scenarios and collections organisation
Unfortunatly I cannot tell you as they is no install.log (yet). Do you remember some printout message ?
With the comming NuTyX 8.2 version, I will be able to answer you better because a install.log will be available. This log will track all actions regarding configuration and installation of your NuTyX. Right from the beginning
Last edited by tnut; 07-19-2016 at 02:01 PM.
Reason: Some message from cards ?
Your distro looks really interesting, not to say about its systemd-freedom that I've been seeking for a long time.
I have one question though: do you plan to generate new version i686 images ? Version 9.91 is only x86_64 as I see
P.S. I have some troubles installing mate. I've read your Documentation. After installing NuTyX_i686-9.1.iso I did:
get xorg
get mate mate-extra
get lxdm / slim (tried both of them)
Rebooted. But after entering user/password at the login prompt I'm getting something like "Failed blah blah..." on a black screen. Sorry, I can't remember what it was exactly (I tried it a week ago at work and then I deleted this virtual machine). After seeing this video on YouTube (watch?v=6A7lMsHmpoY) I'm stuck because he didn't install lxdm/slim at all. Just mate and voila... If you need some details I will install it again and give you the needed output or logs etc. (you just name them). I'd really like to use this distro and help develop it!
Also, what is this graphical environment I get when I do 'startx' ? And why is started at F1 ? And how to kill it ?
Sorry for a lot of questions I get used to Debian (been using it since 2007).
Thank you!
Last edited by TheExplorer; 11-20-2017 at 12:31 PM.
Wow, I reinstalled it and now it works...
But only when I choose 'MATE' instead of 'Default'.
1) How can I make MATE the default one?
2) Do I really need lxdm if there is xdm already? If yes, how can I tell it to run MATE?
3) How can I tell if I need 'base', 'gui', 'gui-extra' and other groups of packages installed and what do they include?
4) How can I clean packages cache after installing? Well, it consumes disk space.
Thank you for your feedback! Hope to get to know your distro and help with Documentation etc. on your site (English, checking/correcting mistakes). Well, if you want.
Last edited by TheExplorer; 11-20-2017 at 12:52 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.